To import a bank statement into Sage Accounting, the cloud product, open the bank account you want to fill, choose its statement import option and upload a transaction file, usually a CSV. Map the columns if asked, then review the lines. They arrive as bank transactions waiting to be matched or categorised, not as finished entries.
Which statement files will Sage Accounting take?
The statement files Sage Accounting takes are listed on its own import screen, and that screen is the only list worth trusting. Sage runs separate editions for different countries, and help pages move often. A CSV is the format almost every bank can produce and every spreadsheet can save, so this post assumes one.
Some banks also offer bank-data downloads such as OFX or QIF. If the import screen names one of those and your bank offers it, try it first, because those files need no column mapping. If the screen does not name it, convert the download to CSV or export a CSV from online banking instead.
Expect a PDF statement to need converting before it goes in. A file import reads rows of data, and a PDF is a printed page. It has to become a CSV first, by hand, in a spreadsheet, or with a converter. SimpleBankConvert is being built to do that step for QuickBooks and Xero files, with one date format and one signed amount column, and the same CSV can be reshaped for Sage's mapping screen.
Laying out a CSV for a Sage Accounting bank import
A CSV for a Sage Accounting bank import should hold one transaction per row, a header row naming each column, and at least a date, a description and an amount. The mapping screen then asks which column is which. A clean, consistent file matters more than the exact column names.
Pre-upload checklist
Run through this list before every upload. Each point is a common cause of a refused or garbled file in any accounting import.
- One header row, then data. Delete bank logos, account summaries and blank lines above the headers.
- One date format. Pick day first or month first and use it on every row. Mixed formats push lines into the wrong month.
- One amount column, or two clean ones. Either a single column with a minus for money out, or separate money in and money out columns with no signs. Never both styles in one file.
- No currency symbols or thousands separators. Write 1250.00, not $1,250.00.
- No running balance column, unless asked for. It can confuse the mapping.
- Dates inside one statement period. Check that the first and last rows match the statement you are importing.
- Saved as CSV. An Excel workbook saved with a .csv name is not a CSV.
An example file
Here is an example of a minimal file. The values are made up:
Date,Description,Amount
02/03/2026,Client payment Northgate Ltd,1500.00
05/03/2026,Stationery World,-42.10
11/03/2026,Broadband March,-35.00
This example uses day-first dates, as a UK edition would expect. A US file would write the first row as 03/02/2026. Whatever you choose, tell the import screen the same thing.
Where do imported lines appear in Sage Accounting?
Imported lines should appear on the bank account you chose during the upload, among the bank transactions that still need attention. Expect them to be statement lines rather than finished entries. Each one is matched to an invoice or bill, or given a category, before it counts in your reports. Check your edition's screen to confirm.
That two-step design catches mistakes. If the file had the wrong sign on every line, you see payments listed as money in before any of them reach your profit and loss. If dates moved by a month, the lines show up outside the period you expected.
Check three things once the lines are in:
- Count. The number of new lines should equal the number of rows in your file.
- Range. The first and last dates should match the statement.
- Balance. After you process the lines, the account balance in Sage should equal the statement's closing balance. A difference equal to one transaction's amount points straight at the missing or doubled line.
If the lines went into the wrong bank account, remove them and import again into the right one, rather than recoding each line.
Sage Accounting and Sage 50: two different bank imports
Sage Accounting and Sage 50 are separate products with different bank imports. Sage Accounting is the cloud product used in a browser. Sage 50 is a desktop program with its own screens and its own file rules. Help written for one rarely fits the other, so check which product an article covers.
The mix-up is common because both carry the Sage name, and search results blend them. If the steps you are following mention installing software, opening a company file on your computer, or menu bars, they are almost certainly for Sage 50. The Sage 50 route has its own walkthrough in importing a bank statement into Sage 50.
The same split appears elsewhere. QuickBooks has an online product and a desktop one with different file types, and small-business tools aimed at sole traders often have yet another route. Importing bank transactions into QuickBooks Solopreneur and importing a bank statement into MYOB show how two other products handle the same job.
A Sage Accounting import that overlaps the bank feed
A Sage Accounting import that overlaps the bank feed brings the same transactions in twice: once from the feed and once from your file. The fix is to import only the dates the feed does not cover. Find the oldest line the feed delivered, and end your file the day before it.
This matters most when you start using Sage partway through a year. The feed fills recent weeks, and statement files fill the months before it. Writing down the boundary date before you build the file is the simplest safeguard.
If the overlap has already happened, compare each pair against the statement before deleting anything. Two identical lines can be genuine, such as two equal parking charges on the same day. Delete a line only when the statement shows it once.
Files arriving from older software sometimes bring their own format problems. A QuickBooks Desktop IIF export, for example, is not a bank statement file at all, and converting IIF to QBO explains what that format holds and why it rarely suits a bank import.