Xero Bank Reconciliation: Match, Review and Report

Xero bank reconciliation pairs each imported bank statement line with a transaction in Xero, by accepting a suggested match, applying a bank rule or creating the entry. Reconciling every line is only half the job. You then compare the balance in Xero with the closing balance on the bank's own statement, and explain any difference before the month is closed.

Xero statement lines and what reconciling one means

A Xero statement line is a single transaction that arrived from the bank, through a bank feed or an imported file. Reconciling it means telling Xero which ledger transaction it represents. The line then leaves the to-do list, and the cash account in Xero reflects it. Nothing about the bank's own statement changes.

Xero's page on reconciling bank transactions describes both sources of lines. Business accounts can connect so transactions are pulled in automatically, and an account that does not connect can be filled by importing transaction data by hand.

That distinction matters for what reconciliation proves. In Xero, the outside record you compare against is the feed or the import. If the feed is incomplete, duplicated or late, every line can be reconciled and the books can still disagree with the statement the bank sends at month-end. Treat the feed as a convenient copy of the bank's data and the statement PDF as the record a reviewer will ask for.

Each line gets one of a few treatments:

• Matched to a transaction already in Xero, such as an invoice payment or a bill payment.
• Created as a new transaction from the line, coded to an account, when nothing in Xero represents it yet.
• Treated as a transfer when money moved between two of the organisation's own accounts.
• Left unreconciled with a note, when you need information from someone before deciding.

Should you accept Xero's suggested matches?

Accept Xero's suggested matches when the amount, date and contact all agree with what you know happened, and look harder whenever any of the three is only close. A suggestion is a guess built from patterns. It saves typing, and it can pair a line with the wrong invoice when two customers pay the same amount in the same week.

Xero's page says its matching assistant, JAX, works from rules, matches, memory of past choices and predictions drawn from how other Xero users reconciled similar transactions. It reconciles automatically only when confident, and otherwise suggests a match and leaves the final say to you. The same page lists automatic reconciliation on the Growing and Established plans, not the entry plan.

Automatic reconciliation shifts the review from before the entry to after it. That is fine for a high-volume account with repetitive lines, as long as someone reviews what was reconciled. A quick monthly test:

1. Open the list of reconciled transactions for the month. Xero's page says the list can be filtered to find items that need attention.
2. Pick a sample across contacts and amounts, weighted toward larger lines.
3. For each, compare the bank description with the invoice or bill it was matched to.
4. Note any mismatch and the rule or suggestion behind it.

If a sample turns up two or more wrong pairings, stop relying on automatic reconciliation for that account until the cause is fixed. Companies with documented controls over cash will want this sample written up as a review step; SOX controls for cash and the evidence they need describes how such reviews are usually documented.

Xero bank rules that save time without hiding errors

Xero bank rules apply a fixed treatment to every statement line that meets their conditions, such as coding a monthly fee to bank charges. A safe rule is narrow: it names one payee, one kind of transaction, and an account that would never be wrong for it. Broad rules quietly code exceptions as routine.

Xero's page describes rules as a way to treat groups of similar transactions the same way every time, and says they work alongside JAX in bulk reconciliation. That is exactly why they need care. A rule runs on every line that fits, including the one that should have been questioned.

Guidelines for rules that stay safe:

• Match on the payee text and the direction, not on amount ranges alone. "Contains MONTHLY SERVICE FEE, spend money" is narrow. "Under $50" is not.
• Avoid rules that code to suspense or owner accounts. Those are the accounts where errors and personal spending hide.
• Do not write rules for intercompany or loan payments. Those need a matching entry elsewhere, which a rule cannot make.
• Review the rule list quarterly. Delete rules for vendors you no longer use, so a new payee with similar text is not caught by an old rule.
• Keep a note of who created each rule and why. A reviewer will ask.

Other systems call the same idea a matching rule or a posting rule. Business Central bank reconciliation and Dynamics GP Electronic Reconcile each have their own version, and the cautions carry over.

Reading the Xero bank reconciliation summary

The Xero bank reconciliation summary compares the balance Xero holds for an account with the bank's balance, and lists the items that explain the difference. Xero's page says that when the two balances do not match, the summary helps you find missing, deleted or duplicated transactions. It is the report to run and file at every month-end.

Read it the way you would read any bank reconciliation. One side starts from the ledger balance in Xero. The other starts from the bank. Between them sit two kinds of items: transactions entered in Xero that have not yet appeared on the bank side, and bank lines that have arrived but are not yet reconciled. Labels can vary by region and version, so check the wording on your own screen.

What the summary proves:

• That the ledger balance and the imported bank balance are explained by a listed set of items.
• Which of those items are still waiting, and for how long.

What it does not prove:

• That the imported bank balance equals the closing balance printed on the bank's statement.
• That each reconciled line was matched to the right transaction.

Run the summary as at the statement's closing date, not today's date. Then write the bank statement's printed closing balance beside it. If those two figures differ, the feed and the statement disagree, and the next section is where to look.

Why does Xero still differ from the bank statement after reconciling?

Xero still differs from the bank statement after reconciling when the feed or import does not contain exactly the lines the bank printed. Common causes are a duplicated feed line, a line missing during a feed outage, a reconciliation dated after the statement period, or an opening balance that never matched the first statement.

Work through them in order of likelihood:

1. Duplicate statement lines. Feeds occasionally deliver the same transaction twice. Both copies get reconciled, and cash in Xero is overstated or understated by that amount.
2. Missing lines. A gap in the feed means a transaction never arrived. Compare the count of lines in Xero for the period with the count on the statement.
3. Date cut-off. A line dated the 1st of next month reconciled into this month moves the balance. Run the summary as at the statement end date.
4. Opening balance. If the account's starting balance in Xero did not equal the first statement, every month carries the difference.
5. Deleted transactions. A reconciled transaction deleted later leaves its statement line orphaned.

The size of the difference is a clue. A difference equal to one line suggests a duplicate or a gap. A constant difference that never changes month to month suggests the opening balance.

Fixing a reconciled line usually means unreconciling it and reconciling it again correctly. The trade-offs are similar to those in unreconciling in QuickBooks Online without damage: change only the lines you must, and record why.

A Xero reconciliation worked for one month with a duplicate feed line

A worked example shows how a duplicate surfaces. A small agency's checking account has 42 lines on its June statement. All figures are example values, made up for illustration.

Every line in Xero is reconciled, so the to-do list is empty. The summary looks clean. The difference only appears when the printed closing balance is written beside it.

The line count gives it away: 43 in Xero against 42 on the statement. Money out is $620.00 higher in Xero, and the difference is exactly $620.00. Searching June for that amount finds a software subscription delivered twice by the feed on consecutive days and reconciled both times to two separate spend transactions.

The fix: unreconcile the second line, delete the duplicate spend transaction it created, and remove the duplicate statement line if your setup allows. Rerun the summary at June 30 and confirm the closing balance equals $34,740.47.

Counting and footing the statement first would have caught this before any ticking. PreciseBankFlow foots each statement PDF, flags possible duplicates by payee, amount and date, and exports the exceptions; it is opening to CPA and audit firms in small groups.

Xero reconciliation habits that fail a reviewer

Xero reconciliation habits fail a reviewer when they treat an empty to-do list as proof that cash is right. The empty list only shows that every imported line has a partner. A reviewer wants to see the bank's own statement balance agreed to Xero, the open items explained, and some check on automatic matching.

The habits that cause the most trouble:

• Never comparing to the statement PDF. The feed balance is not the bank's statement. File the PDF with each month's summary.
• Reconciling into the wrong month. A line dated July 2 matched to a June transaction makes both months wrong.
• Coding unknown lines to suspense to clear the list. It empties the to-do list and moves the problem to the balance sheet, where it is easier to forget.
• Leaving old outstanding items. A payment entered in Xero that never appeared at the bank after three months is either a lost check or an error. Investigate it.
• No sign-off. The month should carry the preparer's name and date, and ideally a second reviewer's.

None of these takes long to fix. The habit worth building is a short month-end pack: the statement, the summary at the statement date, a note on any difference, and a sample check on automatic matches.