You’ve approved a month of expense claims and now someone has to type them into Sage, line by line, with the right nominal code and VAT on each. If you import expenses into Sage instead, the job is a CSV file and five minutes of checking. This post covers Sage 50 Accounts (the desktop product, UK), which imports transactions from a spreadsheet or CSV through its audit trail import.

It isn’t advice on how your books should be set up. Your accountant decides which nominal codes and which posting suit your business; the steps below are Sage’s own.

Can you import expenses into Sage 50?

Yes. Sage 50 Accounts imports audit trail transactions from an Excel or CSV file. In a CSV, “each line of the CSV file represents one record”, with commas between the fields, quotes around any field that contains a comma, and no quotation marks inside the data itself (Sage, Import file format rules, last modified 24 September 2025, checked 27 October 2026). Sage also warns that values longer than a field’s maximum length are cut off without an error, so a long description can quietly lose its end.

Sage ships templates for this. Its journal guide says to open Help > About, choose Program Directory, open Import Templates and use “Audit Trail Transaction Full template.xls” (Sage, Import journals, last modified 11 March 2026, checked 27 October 2026).

Which Sage columns an expenses import uses

Sage lists the fields you can import, in order: Transaction Type, Account, Nominal Code, Department, Date, Reference, Details, Net, Tax Code, Tax, Exchange Rate, Extra Reference, User Name, Project Reference and a few more (Sage, Audit trail transactions data fields you can import, modified 21 March 2025, checked 27 October 2026). Transaction Type, Nominal Code, Net and Exchange Rate are compulsory; Date defaults to the program date and Tax Code to T0 if you leave them blank.

For expenses, a sensible mapping is:

Sage column What goes in it
Type JD and JC for a journal, or BP for a bank payment
Nominal Code the expense account for the line (travel, subsistence, and so on)
Date the line’s date
Reference the claim number, so every line of a claim links up
Details claimant, merchant and description
Net, Tax Code, Tax the line’s net amount, its VAT code and the VAT
Exchange Rate 1 for sterling
Extra Reference the claimant
Project Reference the client, if the cost is being recharged

Every nominal code must already exist in Sage. The safest way to guarantee that is to take the codes from Sage in the first place: export the chart of accounts and use that list in your expenses tool, rather than letting anyone type a code.

Journal or bank payment: two ways to post expenses into Sage

How you post depends on how you pay.

If claims are paid through payroll, a journal suits: a journal debit (JD) per expense line to its nominal code, and a journal credit (JC) to an “expenses payable” control account for the claim’s total. The payroll payment then clears that control account. Sage’s journal guide says to leave Account reference blank on journal lines, use the same date on every line of the journal, and check that debits and credits balance (Sage, Import journals, checked 27 October 2026).

If claims are paid straight from the bank, a bank payment (BP) per line, from the bank account you pay from, does the job in one step.

Which one is right for you, and which control account to use, is a question for whoever keeps your books.

VAT and tax codes on imported expenses

Each line needs a tax code. Sage’s UK defaults are T0 for zero-rated, T1 for standard-rated, T2 for exempt, and T9 for non-vatable, which doesn’t appear on the VAT return (Sage, UK default tax codes, checked 27 October 2026). Your own Sage may have been set up differently, so check.

In practice, for expenses:

  • a line with a valid VAT receipt and VAT you can reclaim: T1, with the VAT amount;
  • mileage, and anything without a VAT receipt: T9, VAT nil;
  • client entertainment: recorded, but its VAT isn’t reclaimable, so don’t post it as reclaimable VAT.

Sage’s journal guide adds a warning: “If tax is included in the transactions, post separate journals to the Sales or Purchase tax control accounts.” If your journals carry VAT, ask your accountant how they want it posted before the first import. The rules on what makes a valid VAT receipt are in the finance guide to expense claims and VAT.

How to import expenses into Sage, step by step

From Sage’s journal guide:

  1. Back up first. Use the backup option in the import wizard, close Excel and make sure no one else is working in the company.
  2. Go to File > Import, click Next, choose Audit Trail Transactions.
  3. Choose Comma-separated (or Excel), browse to the file, and click through to Import.

Then check the result: the nominal activity for your expense codes and the control account should match the claims you exported.

Test once before your first month end

Every Sage import guide says the same thing in different words: try it on something that doesn’t matter. Restore a backup into a test company, import a single claim, and check the postings. Confirm the column headings against a sample exported from your own Sage, because templates differ between versions. It takes half an hour once and saves a month of correcting journals.

How Sign2Approve Expenses exports to Sage

Finance imports the nominal codes from Sage 50’s chart of accounts (saved from Excel), so claimants pick a code from a list and never type one. Each category carries a default code and a VAT treatment, so the tax code on each line follows from the receipt: T1 with VAT where there’s a VAT receipt, T9 for mileage and anything without one.

The export produces the Sage 50 import file, as journals (the default) or bank payments, chosen in Settings. The claim number goes in Reference, claimant and merchant in Details, and the client in Project Reference where a line is recharged. Alongside it you get a detail CSV and a PDF pack of receipts. Each export is stored as a record, and a paid claim can’t be exported again by mistake. There’s more on the routine around it in month-end expenses without the chase.

Sign2Approve Expenses exports approved claims ready for Sage, free for up to 3 claimants with no card: see Expenses.