How to import a bank statement into Sage Accounting (UK)
By Arron Child, reviewed by Arron Child. Updated 23 July 2026.
Sage cannot read a PDF. To get a statement into Sage you first turn the PDF into a CSV, then use Sage's own statement import. This guide covers the import that works first time in Sage Accounting (the cloud product, formerly Sage Business Cloud), the differences in Sage 50 desktop, and the errors that reject a file.
Sage Accounting: the import Sage actually runs
Sage Accounting imports a statement per bank account and maps your columns as it goes, so the layout is forgiving as long as the content is clean. From Sage's own help, the flow is:
- Go to Banking and select the bank account the statement belongs to.
- Select Actions, then Import statement.
- Browse to or drag in your file, then select Review transactions.
- Sage asks you to select the date format used in your file so it reads dates correctly; choose it and continue.
- Check the reviewed rows for errors, then select Confirm import.
Sage accepts a statement as "a QIF, CSV or other file types" (Sage's wording). CSV is the format a converter produces, and because Sage lets you set the date format at step 4, you do not have to match a fixed UK date pattern in the file itself.
The CSV to give Sage
There is no dedicated Sage preset in the converter; you do not need one. The default (generic) export emits every column Sage maps from:
| Column | What Sage does with it |
|---|---|
| Date | Mapped to the transaction date; you confirm the format on import |
| Description | Mapped to the details or reference of each line |
| Money out / Money in | Two-column money, if your Sage import expects separate columns |
| Amount | One signed column (money in positive, money out negative), if Sage expects signed money |
| Balance | Ignored by the import; useful for your own reconciliation check |
Because the generic export carries both the two-column money (Money out, Money in) and a single signed Amount, it maps cleanly whether your Sage screen asks for separate columns or one signed figure. Every value is generated locally in your browser; the statement PDF is never uploaded.
Sage 50 desktop is different
Sage 50 (the installed desktop product) is stricter than Sage Accounting. It expects a CSV whose columns match its import template rather than mapping them for you, and it is unforgiving about date format (DD/MM/YYYY), stray header rows, and currency symbols in the amount column. If you are on Sage 50, download the import template from inside Sage first, match your exported columns to it, and remove any second header row before importing.
Errors that reject or corrupt a Sage import
- Date format mismatch. The single most common failure. 03/04 read as 4 March instead of 3 April is silent and wrong; set the date format deliberately at the review step, and spot-check any day above the 12th.
- Currency symbols or thousands separators in the money column. Sage wants plain decimals; £1,234.56 should be 1234.56.
- A second header row midway through the file, common when statements were stitched together in a spreadsheet first. One header row, at the top, only.
- Everything imported as money in. The sign is missing. This is the tell that a converter did not sign the amounts; the export here signs them.
Verify after importing
Compare the balance Sage shows after import against the closing balance printed on the original PDF. If they differ, the file is incomplete or mis-signed; delete the imported statement and find the break before you reconcile, not after it has entered the ledger. The converter proves this arithmetic on the document before you ever open Sage, so a mismatch should be caught earlier than this.
Import steps checked against Sage Accounting's own help pages on 23 July 2026. Sage is a trademark of The Sage Group plc; ukbankconv is not affiliated with Sage. Sage's screens change; if a step name differs, follow the equivalent option in your version.