Xero Statement balance differs from the bank: find the interval
Updated · 4 min read
If Xero’s Statement balance differs from the bank’s balance for the same account and date, first verify the opening balance, then narrow the period in which the imported statement history diverged. Do not start by changing invoice matches or entering a balancing transaction. Those actions may affect the books without fixing a missing or duplicated bank statement line.
This guide concerns the statement layer, not every difference between the accounting ledger and the bank. When the reference statement is PDF-only, LocalExtract can prepare rows for comparison; retain the issued document as the balance evidence.
The desktop apps export date, description, and amount as CSV. Open CSV in Excel to save an XLSX workbook. Statement support varies: verify the result against your own PDF.
Compare the same kind of balance
Xero’s official diagnostic guide separates a wrong opening balance from problems in bank statement lines. Statement balance reflects the statement history held in Xero. Balance in Xero is a different accounting measure; its disagreement with Statement balance calls for a separate investigation.
Write down the account, currency, comparison date and the two values being compared. A bank’s current available balance is not automatically the historical closing balance on the PDF. If either value’s meaning or date is unclear, establish it before treating the difference as a missing transaction.
Check Xero’s saved opening balance against the bank’s actual closing balance for the day before starting in Xero. Where conversion or uncleared items are involved, use the relevant Xero guidance and the responsible bookkeeper rather than adding an adjustment purely to force agreement.
Narrow the first differing interval
Once the opening point is established, follow the official guide’s report-based approach:
- Identify a date when Xero’s Statement balance and the actual bank balance were known to agree.
- Run Bank Reconciliation Summary for a later cutoff with bank evidence available for that same cutoff.
- Compare the report’s Statement balance with the bank’s balance. If they agree, move to the next evidenced cutoff; if not, the intervening period needs inspection.
- Test closer dates inside that interval. Record each comparison instead of overwriting the previous result.
You have not located the first differing day while untested days remain between a matching and non-matching cutoff. For a fluctuating difference, do not assume a single error persists unchanged; inspect the full interval. Equal balances at two endpoints can conceal opposite-sign omissions inside it.
Read a synthetic difference trail
The invented USD example below deliberately omits one 40.00 USD debit from the statement layer. That cause is supplied by the exercise, not inferred from the balance difference alone.
| Evidenced cutoff | Actual bank | Xero statement layer | Xero minus bank |
|---|---|---|---|
| September 30 | 1,000.00 USD | 1,000.00 USD | 0.00 USD |
| October 4 | 1,100.00 USD | 1,100.00 USD | 0.00 USD |
| October 5 | 1,060.00 USD | 1,100.00 USD | +40.00 USD |
| October 6 | 1,050.00 USD | 1,090.00 USD | +40.00 USD |
October 5 is the first differing observed cutoff. Compare the underlying statement lines around the last matching cutoff and that date to establish what actually happened. In another case, a 40.00 USD excess could result from different errors; the number does not uniquely identify the cause.
The synthetic statement-layer exercise preserves these comparisons and a control where +25.00 and −25.00 USD are both missing. Python checks the arithmetic. It does not run a Xero report, import a bank file or establish a real account’s cause.
Investigate the statement lines before repairing them
The official guide points to the Bank Statement and Statement Exceptions reports in the Bank Reconciliation report pack. Compare the source lines and inspect missing, deleted, duplicate or manually created lines. A transaction manually marked reconciled can create a manual statement line; a later bank import can then produce another observation of the event.
| Evidence found | Next investigation |
|---|---|
| A real bank movement is absent from the statement history | Establish the exact missing scope before importing |
| Two statement lines appear to describe one movement | Verify their sources and actual event before removal |
| A line was deleted | Establish whether deletion was intentional or mistaken |
| A manual line and imported line coexist | Inspect why the manual line was created and any existing reconciliation |
Use Xero’s linked, error-specific correction instructions and appropriate permissions. This diagnostic is not permission to delete a reconciled record or change the opening balance to absorb an unexplained difference.
Close this layer, then review the books
Repeat the same evidenced cutoffs after an authorized correction and retain the line-level explanation. Agreement of statement balances does not prove that every invoice or account transaction is correctly reconciled. Continue with the separate bank reconciliation guide for that work. If a file is genuinely needed, use the Xero CSV import guide rather than re-uploading the entire period.
LocalExtract processes one PDF locally into date,description,amount; it does not inspect or repair Xero’s statement history. Download LocalExtract for a PDF source.
Official Xero guidance checked on October 15, 2026. Report availability and labels should be confirmed in your organisation.
LocalExtract Team
We build LocalExtract, a desktop bank statement converter. Questions or corrections? Contact · Editorial policy