Getting old bank statements into Xero, QuickBooks, FreeAgent or Sage.
Bank feeds cover the present. For the rest — periods before the feed started, a closed account, a bank with no feed, statements a client sends as PDFs — you need to import a statement file.
Updated 20 October 2026
What each package accepts
Each package imports bank statements from a CSV file, but each wants its own layout: Xero wants one signed Amount column and its own headings; QuickBooks a strict three- or four-column file without certain characters; FreeAgent no header row at all; Sage four columns in a fixed order. A file that's nearly right often fails, or worse, imports with money in and out the wrong way round.
From PDF to import file
StatementPro reads the PDF statement, checks it against the statement's own totals and running balance, and gives you a download laid out exactly as the package asks — one file per statement, for one bank account.
Xero · QuickBooks · FreeAgent · Sage
Avoiding duplicates
- Import each statement once, into the right bank account.
- Watch for overlap: a transaction list and a statement often share a few days. StatementPro warns when two statements converted together cover the same days.
- Check the dates: every date should be day/month/year. A statement that prints no year needs its year from the statement period; StatementPro refuses to make the file rather than guess.
Questions
Will imported lines be reconciled automatically?
No. They arrive as bank statement lines, the same as a feed or any statement import, and you reconcile them as usual.
Can StatementPro send the lines straight into Xero?
Not yet. Today you download the file and import it.