Bank Statement Converter for Xero: Import Any PDF Statement

Xero can pull transactions from thousands of banks through live feeds — but the feed only starts from the day you connect it. Historical months, statements from unsupported banks, and PDF-only records from clients all have to come in another way. That's where a bank statement converter for Xero comes in: it turns any PDF statement into a CSV that Xero imports cleanly, so your reconciliation history is complete.

Why Xero Users Need a Statement Converter

Xero's bank feeds are excellent when they work, but four situations leave you with a PDF and no feed:

• Historical data. Feeds don't backfill. If you connect a feed in July, January–June has to be imported manually — and most banks only offer those older months as PDF statements.
• Unsupported banks. Smaller credit unions, neobanks, and many international banks don't have Xero feed coverage at all.
• Broken or lapsed feeds. Feeds occasionally disconnect and leave gaps of days or weeks that need to be patched with a manual import.
• Client records. Accountants and bookkeepers onboarding a new client often receive a folder of PDF statements — sometimes scans — covering a year or more of activity.

In every case the fix is the same: convert the PDF to a properly formatted CSV and import it. The catch is the phrase "properly formatted" — Xero is strict about what it accepts.

What Xero Requires From an Imported CSV

Xero's manual statement import accepts CSV files with, at minimum, a Date and Amount column, plus optional Payee, Description, Reference, and Cheque Number columns. The rules that cause most failed imports:

• One header row, then data — no title rows, page numbers, or bank logos above it.
• Consistent dates. Every row must use the same format (e.g. DD/MM/YYYY or MM/DD/YYYY), and it must match what your Xero organisation expects.
• Signed amounts in a single column. Money out is negative, money in is positive. Separate debit/credit columns must be merged into one signed Amount column.
• Plain numbers. No currency symbols, no thousands separators that conflict with your locale, no parentheses for negatives.
• No summary rows. Opening balance, closing balance, and "Total" lines from the statement must not appear as transactions, or your reconciliation will be off.

Hand-cleaning a copy-pasted PDF to meet those rules is where most of the time goes. A purpose-built converter outputs a table that already satisfies them.

Step-by-Step: PDF Statement Into Xero

1. Convert the PDF. Upload the statement to the converter and download the result as CSV. Every transaction comes out with a clean date, description, and amount — validated against the statement's running balance.
2. Check the totals. Open the CSV and confirm the sum of the Amount column equals the net change on the statement (closing balance minus opening balance). This 30-second check guarantees the import will reconcile.
3. Import in Xero. Go to the bank account in Xero, then Manage account → Import a statement, and upload the CSV. Xero shows a column-mapping screen — confirm Date, Amount, and Description are mapped correctly and check the date format matches.
4. Reconcile as usual. The imported lines appear on the Reconcile tab exactly like feed transactions. Xero's bank rules and suggested matches work on them normally.

Converter Options Compared

For a broader look at the tools in the first row, see our 2026 comparison of bank statement converters.

Common Xero Import Errors (and Fixes)

"Import failed" or rows rejected

Almost always a date-format mismatch — the CSV says 07/03/2026 meaning March 7th, but Xero reads July 3rd, or vice versa. Set the correct format on the mapping screen, or standardize the CSV to an unambiguous format before importing.

Duplicated transactions

Happens when an import overlaps a live feed period. Delete the duplicated statement lines in Xero (Manage account → Bank statements), or trim the overlap out of the CSV before importing.

Balances don't reconcile after import

Usually a stray summary row imported as a transaction, or a missed page of transactions. Because our converter validates every row against the statement's own running balance, both problems are caught before the CSV ever reaches Xero — the same balance-check discipline we recommend in our bank statement reconciliation guide.

For Accountants: Batch Onboarding Client Statements

Onboarding a client with 12–24 months of PDF-only history is the classic use case. Convert the statements in a batch, spot-check opening and closing balances per month, then import into Xero oldest-first. What used to be a day of data entry becomes under an hour — and the same workflow applies to QuickBooks clients, as covered in our QuickBooks converter guide. If you handle client documents regularly, make sure your tooling meets the security bar described in how to securely handle client bank statements: encrypted uploads, automatic deletion, and no training on your data.

Get the missing months into Xero today — convert your first statement free on the homepage, no signup required.

Frequently Asked Questions