Sage 50 and Sage Accounting
Import bank statements into Sage
Sage 50 and Sage Accounting both import statement files, neither imports an ordinary PDF on its own, and their CSV rules are stricter than most. Here is which file to make for your Sage, and how.
- OFX that imports without editing
- CSV in Sage’s Date, Description, Amount order
- Day-first dates for UK statements
- Each statement checked against its closing balance
<STMTTRN> <TRNTYPE>CREDIT <DTPOSTED>20260302 <TRNAMT>4210.00 <FITID>a3f9c2e81b07 <NAME>ACH DEPOSIT STRIPE PAYOUT</STMTTRN><STMTTRN> <TRNTYPE>CHECK <DTPOSTED>20260305 <TRNAMT>-1250.00 <FITID>5d10e7b4c9a2 <CHECKNUM>1042</STMTTRN><LEDGERBAL><BALAMT>15354.12
The short answer
Can you import a PDF bank statement into Sage?
Not directly as a statement. Sage Accounting imports QIF, OFX, CSV and Excel statement files, and for customers who only have a PDF its help points to AutoEntry, Sage’s separate document-capture product, to turn it into a CSV. Sage 50 Accounts (UK) imports statement files through its Bank Feeds module from version 30.1, and lists CSV, OFX, QIF, QBO, QFX and XLS among the types it reads. Neither treats a bank’s PDF as an import file.
Of those formats, OFX is the one Sage describes as industry standard and safe to upload without opening or editing it. CSV works too, but Sage specifies the exact column order, header names and date separator, and a file that misses any of them is rejected.
VouchRow converts the PDF statement, digital or scanned, into OFX, QIF or a CSV in Sage’s three-column layout, after checking every row against the statement’s running balance and closing balance. You then import the file through Sage’s own Import statement screen.
Which format to use
The file Sage wants
OFX for Sage
Sage 50 and Sage Accounting are not the same product
Step by step
How to import a PDF bank statement into Sage
Check which Sage you run before anything else: Sage 50 Accounts is desktop software, Sage Accounting is online, and their menus differ.
- 1Download the PDF statementsGet the statements for the period Sage is missing, one account at a time. Sage imports one bank account per file; if a file holds more than one, Sage Accounting takes the first account and ignores the rest.
- 2Convert and checkUpload the PDFs after signing in. Every row is checked against the running balance, and the statement as a whole against opening balance plus movement equals closing balance. Fix any flagged row against the highlighted line on the PDF.
- 3Export OFX, or CSV in Sage’s layoutOFX is the simplest: no mapping, no date order to choose. For CSV, use the three-column preset (it is labelled QuickBooks, and writes Date, Description, Amount in that order) with day-first dates such as 04/01/2025, which is exactly Sage’s three-column specification. QIF is there for older setups.
- 4Sage Accounting: Import statementGo to Banking, open the bank account and choose Import statement from its actions. Select the file, and for QIF or CSV choose the date order the file uses (day/month/year for UK files). Check the preview and import.
- 5Sage 50 Accounts: Bank Feeds → Import statementIn Sage 50 Accounts v30.1 or later, open the Bank Feeds module, click Get started against the account (no live feed is needed), then Import statement on the Work with bank transactions window. Choose the date order if prompted, use Switch transaction types if money in and out appear reversed, then Confirm import.
- 6Reconcile to the statement balanceMatch the imported lines to existing entries, create the rest, and reconcile using the statement’s closing balance. Sage’s own advice is to note the statement end balance before importing, because you will need it at this step.
Why it works
Why convert before importing into Sage
A CSV Sage accepts first time
Sage wants Date, Description, Amount in that order, slash-separated dates, a one-line description and numbers only in the amount column. The three-column export already looks like that.
UK dates, stated once
Choose day-first at export and the whole statement uses it. No 1 April turning into 4 January halfway down the file.
Closing balance proven before import
Sage asks for the statement end balance at reconciliation. A statement that already ties out before import makes that step a formality.
Old and scanned statements
Paper statements for a catch-up, or PDFs from a bank with no Sage feed, go through OCR and the same arithmetic checks.
Checked before export
A misread digit is caught on its own row
Every conversion is tested against the statement: the running balance on every row, page subtotals, opening plus movement against closing, the printed credit and debit totals, and the transaction count. When a number does not add up, VouchRow names the row and highlights the line it came from on the PDF.
Arithmetic only: it verifies amounts, balances and totals, not descriptions or dates, and two errors that cancel out would pass. The source-line link covers the rest.
How the checks workRunning balance check
- POS AMAZON MKTPLACE−86.4316,604.12
- CHECK #1042−1,250.0015,354.12
- ZELLE FROM J MORALES+640.0015,994.12
Every row agrees with the balance printed beside it.
Which Sage
Sage 50 Accounts, Sage Accounting and Sage 50 (US/Canada) import differently
Sage sells products under one brand that have different codebases and different import screens. The format you choose should follow the product, not the brand.
| Product | Where to import | Files accepted | Notes |
|---|---|---|---|
| Sage Accounting (UK, Ireland, Canada and others) | Banking → the account → Import statement | OFX, QIF, CSV, XLS (newer regions list more, including QBO and QFX) | 250 MB maximum; one account per file |
| Sage 50 Accounts (UK), v30.1+ | Bank Feeds → Get started → Import statement | CSV, OFX, QIF, QBO, QFX, XLS, BAI, ASO, TXT, XML | Extra CSV template columns not supported |
| Sage 50 (US) | Account Reconciliation → Import | OFX or QFX | Import wizard for downloaded statements |
| Sage 50 (Canada) | File → Import/Export → Import Online Statements | OFX; Bank Services also takes CSV | Version-dependent menus |
CSV rules
The CSV layout Sage requires
Sage publishes two CSV layouts and is literal about both. Most rejected CSV imports break one of these rules.
- Three columns: Date, Description, Amount, labelled exactly like that and in that order. Payments in and out both go in Amount; payments out are negative.
- Four columns: Date, Description, Money in, Money out, in that order. Both money columns contain positive numbers, with the other left blank.
- Dates separated by slashes, for example 04/01/2025. ISO dates with dashes don’t meet the rule, so export day-first or month-first, not ISO.
- Description can’t be blank and must sit on one line. Wrapped statement descriptions are rejoined into one line during conversion.
- Amount cells hold numbers only: no currency symbols, no thousands separators that read as text, no 0.00 in an empty cell.
- Sage 50 Accounts doesn’t read the optional extra columns (cheque number, reference, payee) that Sage’s online templates allow, so keep Sage 50 files to the basic columns.
Date order
Getting the date order right in QIF and CSV imports
OFX writes dates in one fixed form, so Sage reads them without asking. QIF and CSV don’t, which is why Sage’s import asks you to choose day/month/year, month/day/year or year/month/day. Sage’s help suggests opening a QIF in a text editor to check the order before choosing.
A wrong choice doesn’t always fail. Dates up to the 12th import into the wrong month without complaint. For UK statements export day-first and pick day/month/year, or avoid the question by using OFX.
Duplicates
Avoiding duplicates when you also have a bank feed
Sage’s guidance for statement imports alongside a bank feed is to start the import the day after the last transaction the feed downloaded. Treat that as the rule: Sage posts what the file contains, and importing a month the feed already covers leaves you clearing out a second copy of each line.
If a statement spans the boundary, convert it and export only the rows after the feed’s last date, or delete the overlapping lines before importing. A statement checked against its balances first makes any leftover difference easy to trace to a row.
UK notes
Sage in the UK: day-first dates and statement-only history
Most Sage 50 Accounts and Sage Accounting users are in the UK and Ireland, where bank PDFs print day-first dates and online banking often limits CSV downloads to recent months. Older years, closed accounts and statements kept for a year-end or an enquiry are usually PDF-only.
For those, convert the PDF to OFX (or a three-column CSV with day-first dates), import one account and one period at a time, and reconcile each period against the printed closing balance before moving on. GBP amounts are written as plain numbers, which is what Sage’s amount column needs.
Side by side
OFX vs CSV vs QIF for Sage
| OFX | CSV (three-column) | QIF | |
|---|---|---|---|
| Sage Accounting | Yes | Yes | Yes |
| Sage 50 Accounts (UK, v30.1+) | Yes | Yes, basic columns only | Yes |
| Sage 50 (US) | Yes | Not in the statement wizard | Not listed |
| Needs editing before import | No | Must match Sage’s layout | No |
| Date order prompt | No | Yes | Yes |
| Easy to inspect first | No | Yes | Partly |
Who uses it
Who converts statements for Sage
UK bookkeepers with year-end backlogs
A client hands over twelve PDF statements in January. Convert, check each month ties to the next, import into Sage 50 or Sage Accounting and reconcile.
Businesses without a working feed
Not every bank or card has a Sage feed. Monthly statement imports keep those accounts current.
Switching to Sage
History from before the switch exists as statements from the old bank or old software. Import it so the opening position in Sage is supported line by line.
FAQ
Sage imports: questions
Can Sage import a PDF bank statement?
Not as a statement file. Sage Accounting and Sage 50 import OFX, QIF, CSV and similar files. For PDFs, Sage’s help refers users to AutoEntry, a separate Sage product; a converter like this one is the other route.
Which format does Sage 50 accept?
Sage 50 Accounts (UK) from v30.1 imports through Bank Feeds and lists CSV, OFX, QIF, QBO, QFX and XLS among others. Sage 50 in the US imports OFX or QFX. OFX is the safe choice for both.
What CSV format does Sage Accounting need?
Date, Description, Amount in that order (payments out negative), or Date, Description, Money in, Money out. Dates separated by slashes, descriptions not blank and on one line, numbers only in amount columns.
Where is Import statement in Sage 50 Accounts?
In v30.1 and later it is in the Bank Feeds module: Get started against the bank account, then Import statement on the Work with bank transactions window. You don’t need a live bank feed to use it.
Why are my dates wrong after importing into Sage?
The date order chosen on import didn’t match the file. Pick day/month/year for UK files, or import OFX, which has no date order to choose.
Does Sage detect duplicate transactions?
Don’t rely on it. Sage posts what the file contains, so start the import the day after your bank feed’s last transaction and never import the same period twice.
Money in and money out came in reversed. What happened?
The sign convention didn’t match. Sage 50’s import has a Switch transaction types option for this; in a CSV, payments out must be negative in the Amount column.
Can I import several accounts in one file?
No. Sage imports one bank account per file and ignores the others, so convert and import each account separately.
Keep going
Related guides and converters
Every format we write for Sage
Convert your statements for Sage
Upload a PDF statement, confirm it ties to the closing balance, and export OFX or a Sage-ready CSV.