Xero Bank Reconciliation Guide

The part most guides skip: reconciliation is only as honest as the lines you're reconciling against. If a statement line is missing, Xero will still happily reconcile everything else and report a tidy balance — built on an incomplete picture. So the real first step is making sure the statement going in is whole.

What reconciliation actually checks in Xero

Two balances have to meet. There's the statement balance — the running total of every statement line Xero holds for the account — and there's the Xero balance, the total of the transactions you've recorded in your books. Reconciliation is the act of pairing those lines up until both numbers land on the same figure, which should also equal the closing balance printed on your bank statement.

When all three agree, the account is reconciled and you can trust it for VAT, for management accounts, for a year-end. When they don't, something's adrift: a duplicate, a missed payment, a transaction recorded in the wrong account, or a statement line that never made it in. Xero shows the gap; it doesn't tell you the cause. That's the bookkeeper's job, and it's far quicker when the underlying data is known to be complete.

The Reconcile tab, button by button

Open Accounting > Bank accounts and click Reconcile on the account you're working. Each unreconciled statement line sits on the left. On the right, Xero offers its best guess at what that line is. You confirm or correct it with one of three actions.

• Match. Use this when the line is something you've already entered — an invoice payment, a bill you've paid, a recorded expense. Xero suggests the match; you check the amount and date, then click OK. This is the bulk of most reconciliations, and it's where Xero's suggestions save real time once your invoices and bills are up to date.
• Create. Use this when the line has no existing record — a bank charge, interest, a direct debit you never raised a bill for. You add the account code and any tax rate right there, and Xero creates the transaction and reconciles the line in one move.
• Transfer. Use this when money moved between two of your own accounts — current to savings, say. Mark both sides as a transfer and Xero won't double-count it as income or expense.

There's also a Discuss tab for leaving a note against a line you're unsure about, handy when a bookkeeper and a business owner share the file. Work down the list until the left-hand column is empty. A green tick and "Reconciled" against the account means the statement balance and the Xero balance agree.

Where the statement lines come from

Xero gets statement lines two ways. A bank feed pulls them in automatically — the cleanest route when you have one, though feeds typically only reach back around 90 days and not every account or country has one. For anything older, or any account without a feed, you import a statement as a file: CSV, OFX or QIF. Imported lines behave exactly like fed lines once they're in; you reconcile them the same way.

The catch is that imports are only as good as the file. Xero can't read a PDF, so a PDF statement has to be converted to CSV first — and that conversion is where transactions quietly go missing. A PDF is a page layout, not a table. Descriptions wrap, page breaks split a transaction in two, a bank prints the date once and leaves the rows beneath it blank. Drop one line and nothing turns red; your closing total just sits slightly off, and you won't know until reconciliation refuses to tie out three months later.

If you're bringing PDF statements in, the import walkthrough covers the Xero side step by step, and the historical-import guide deals with loading several past months in order.

Why a reconciled CSV makes Xero reconciliation clean

Here's the wedge, and it's a practical one. Most converters extract the rows from a PDF and hand them over — no check that the rows add up. Export Bank Statement recomputes the running balance on every file: opening balance, plus money in, minus money out, and tests it against the printed closing figure. If the arithmetic ties, the statement is complete. If it doesn't, the file is flagged so you can find the misread or dropped line *before* it ever reaches Xero. Most converters simply lift the text rather than verifying the totals.

That changes the reconciliation experience. Import a file you already know reconciles against its own running balance, and the Xero side becomes pure matching — Match, Create, Transfer, done — with no hunt for a phantom 150 that won't appear. Import an unchecked file and you inherit the search: the statement balance won't meet the Xero balance, and the missing line could be anywhere across the period.

Be clear on what this is and isn't, though. The path is convert, then import the CSV. Export Bank Statement does not push transactions into Xero through a live bank-feed API — that's a separate, certified integration. It produces a clean, Xero-formatted, balance-checked CSV (Date, Amount, Payee, Description, Reference) that you import and reconcile yourself. No one-click sync from a PDF; treat any tool that claims one with caution.

A worked example

Take a March current account: opening balance 4,210.00, closing balance 3,885.50. You convert the PDF and the check recomputes the running balance line by line. It stops agreeing at a card payment near the top of page two — the recomputed total runs 150 above the bank's printed figure. That's a dropped transaction, the kind that falls across a page break while the rows around it look perfectly fine.

Fix the one line, the totals reconcile, and you import a complete March. On Xero's Reconcile tab, every line now matches and the statement balance lands exactly on 3,885.50 against the Xero balance. Skip the check, and you'd reconcile most of the month, then stall on a 150 gap that takes far longer to chase inside Xero than it would have to catch at conversion.