Convert PDF Statements for Xero

That last part is the bit most people skip. Converting a PDF is easy. Knowing the converted file is *complete* — that nothing was dropped at a page break or misread by a column off — is the part that actually protects your books.

What Xero needs in the CSV

Xero doesn't ask for much, but it's exact about what it asks for. When you run Import a Statement, it reads a CSV and lets you map your columns to its fields. The fields it works with are:

• Date — the transaction date.
• Amount — money in or out, as a single signed number; or
• Payee — who the money went to or came from.
• Description — what the transaction was.
• Reference — optional, for a cheque number or transaction ref.

At a minimum you need a Date, an Amount, and a Payee or Description. Reference is nice to have and safe to leave out. The whole job of converting a PDF for Xero is producing a file with those columns filled correctly.

Two decisions trip people up more than anything else.

The date format. Xero asks you, on the import screen, which format the file uses — DD/MM/YYYY, MM/DD/YYYY, and so on. It doesn't guess. If your statement reads 03/04/2024 and you're in the UK, that's 3 April; tell Xero MM/DD by mistake and it becomes 4 March, shifting your whole period. Pick the format your statement actually prints.

Signed amount versus separate debit and credit. Xero takes either one Amount column — money out as a negative, money in as a positive — or two separate columns, one debit and one credit. Both import fine. What you mustn't do is mix the two approaches in one file, or map a money-out figure as a positive amount, which quietly inflates your balance.

Convert any bank's PDF to a Xero-ready CSV

The process is the same whether the statement came from Barclays, HSBC, Monzo or a bank in another country. The labels on the page change; the steps don't.

1. Open the PDF in Export Bank Statement. Text-based downloads work, and so do scanned or photographed statements — scans go through OCR to read the text before anything else happens.
2. Let it extract every line. It pulls the date, description, money out, money in and the running balance for each transaction, and carries blank-date rows down to the correct day where a bank prints the date only once.
3. Read the reconciliation result. It recomputes opening balance plus transactions and checks that against the printed closing balance. Tie out, and you get a tick. Off by anything, and the statement is flagged before you download it.
4. Export in Xero's bank-import format. The file comes out with the Date, Amount, Payee and Description columns Xero reads, ready for Import a Statement.

Catching a misread figure here — a "1,180" that should read "1,780" — costs you a few seconds while you're still converting. Chasing that 600 hole through an already-reconciled month a fortnight later costs you an afternoon. The order matters: verify, then import.

Why the reconciliation check is the part that matters

Pull text out of a PDF and most tools hand you a grid and call it done. You're left trusting that everything came across. It usually does. The trouble is the time it doesn't, because a PDF is a layout, not a table — columns wrap, dates blank out, a page break lands mid-transaction — and a missing line doesn't announce itself. Your closing total just ends up quietly wrong.

A running balance is the built-in defence against that. Every statement shows opening balance, the transactions, and a closing balance, and the maths has to hold: opening, plus money in, minus money out, equals closing. If the converted file doesn't reconcile, a transaction was misread or dropped, full stop.

Export Bank Statement runs that check for you on every file and flags any statement that doesn't reconcile — so you catch a gap before it reaches Xero, not three months later when the numbers are reconciled and trusted. Most converters just extract the figures rather than verifying them. On a PDF, where what's *absent* is exactly what you can't see by eye, that's the difference between an import you can rely on and one you'll be unpicking.

Import the CSV into Xero

Once the file reconciles, the Xero side is short:

1. Open the bank account in Xero — import into the account the statement belongs to, one account per file.
2. Choose Manage Account → Import a Statement and upload the CSV.
3. Map your columns to Xero's fields and confirm the date format when prompted.
4. Import. The rows land as bank statement lines, the same as a feed would deliver, ready to reconcile against your bills, invoices and spend money.

Map the columns once and Xero remembers the layout for that account, so the next import for the same bank is faster.

A couple of honest limits worth stating plainly. This is convert, then import the CSV — it is not a one-click sync. Export Bank Statement does not push transactions into Xero through a live bank-feed API; that's a separate, certified integration. And Xero's own feeds only fetch recent activity, roughly the last 90 days, so anything older has to come in as a file regardless. If you're loading several past months, the historical-import approach covers ordering and overlapping periods. Still unsure whether Xero takes a PDF at all? The short answer is in can Xero import PDF bank statements.