Bank statement to Sage.
.csv built in your browser, 5 pages free.
Convert a PDF bank statement into a CSV that Sage Accounting and Sage 50 import as a bank statement, with every row checked against the printed opening and closing balances first, so the reconciliation in Sage starts from figures that already agree with the bank.
Drop a statement to get .csv
PDF, scan or photo. Up to 12 files at a time.
Not ready to upload your own? See a sample result
5 pages free, no account. The CSV download appears on the results page.
Last updated
- Tally XML. TallyPrime XML export: Receipt and Payment vouchers for Alt+O import, alongside Excel, CSV, QuickBooks and Xero.
- Non-expiring pack. $19 buys 100 pages that never expire, and no statement is charged more than 15 pages.
- API and email-in. REST API and email-in on every plan, including the free one.
- Your file. Deletion of your file starts when processing ends; results are kept 7 days with an account, 1 day without.
- Balance check. There is no per-bank template: every row is added up against the opening and closing balances printed on the statement, and a misread is flagged, not hidden. How the balance check works
Step by step: PDF statement to Sage
- Drop the statement on the home page and wait for the balance check to turn green.
- Click CSV. The file has Date, Description, Money Out, Money In, Amount, Balance and Category columns, one row per transaction, with plain decimals and no currency symbols.
- Sage Accounting (the cloud product): go to Banking, open the bank account and choose Import Statement (some regions show Import under the Connect menu). Pick the CSV, then match Date, Description and either the single Amount column or the Money In and Money Out pair to the fields Sage lists. Sage also accepts OFX and QIF here.
- Sage 50 (US and Canada): the Bank Services page has an Upload a Bank Statement option that takes a CSV or OFX file; older releases use Tasks, then Import Statement.
- Check the preview Sage shows before confirming. If dates have been read the wrong way round, open the CSV in Excel, format the Date column to your region's order, save and import again.
- Match the imported lines to your Sage transactions as usual. The closing balance Sage shows should equal the printed closing balance on the statement.
What usually goes wrong, and how this avoids it
- Sage is strict about the header row and rejects a file whose columns it cannot name. The CSV has a single header row and nothing above it, so the mapping step is straightforward.
- A bank's own CSV export often has money out as positive figures in one column and money in as positive in another, with no sign convention stated. Here Money Out and Money In are separate columns and Amount is signed, so you can map whichever pair Sage expects.
- Importing a month twice creates duplicates, because a CSV carries no transaction IDs. Check the date range in Sage before you import the next file.
Sage questions
Which Sage products does this work with?
Sage Accounting (formerly Sage Business Cloud and Sage One) imports CSV, OFX and QIF bank statements in the UK, Ireland, Canada and the US. Sage 50 in the US and Canada imports a CSV or OFX through Bank Services. Sage 50 Accounts in the UK has its own bank feed and import tools; if yours accepts a CSV bank import, the same file applies.
Should I use the plain CSV or the QuickBooks CSV for Sage?
The plain CSV. It keeps the running balance and both money columns, which gives Sage's mapping screen every layout it might ask for. The QuickBooks CSV is a three-column file with US-style dates and is meant for QuickBooks Online only.
Can I import a whole year into Sage at once?
Yes. Convert up to 12 statements together and download the merged CSV, which has every transaction in date order with a Statement column saying which file each row came from. Delete that column before importing if Sage objects to it, or import one statement at a time.