Xero displays imported bank statement lines on one side of reconciliation and Xero accounting transactions on the other. A statement line can arrive from a bank feed or manual statement import; the accounting record can be an invoice payment, bill payment, transfer, expense claim, spend money, receive money, overpayment, or prepayment. Reconciliation links them or creates the needed accounting transaction. Recovery fails when a team treats these different records as interchangeable and deletes whatever looks duplicated first.
The word balance also needs a qualifier. Statement Balance is driven by the opening bank balance and statement lines imported into Xero. Balance in Xero is driven by account transactions. The Bank Reconciliation Summary adds calculated statement balance, outstanding payments and receipts, unreconciled statement lines, imported statement balance, and a user-entered bank statement ending balance. A dashboard difference can therefore originate in the feed, the statement history, the ledger, the conversion boundary, the report date, or the reconciliation link.
The recovery method below preserves evidence and narrows the fault before rework. It uses Xero's find and match, Create, Transfer, Discuss, bank-rule suggestions, Statement Exceptions, reconciliation details, Unreconcile, Remove & Redo, statement-line deletion and restoration, and close-period controls in their specific roles. The objective is a defensible chain from the source bank statement to Xero's reports, not a forced zero produced by an unexplained adjustment.
Key decisions at a glance
- In Xero, a bank statement line and an account transaction are separate records joined by reconciliation; diagnose which side is missing, duplicated, or wrong before editing.
- A suggested match, bank rule, memory result, or prediction is a proposal that a reviewer must inspect before clicking OK; it is not proof of the accounting treatment.
- Delete a statement line only when evidence proves it is a duplicate, and use unreconcile versus remove and redo according to whether the match or the underlying transaction is wrong.
- Run the Bank Reconciliation report pack at a fixed date because future-dated matches, deleted lines, user-created lines, and different balance definitions can explain an apparent mismatch.
Freeze Evidence and Classify the Broken Xero Layer
Set a recovery cutoff and stop broad edits, bulk imports, new bank rules, feed resets, and historical cleanup until evidence is captured. Save the source bank statement or online-bank export, masked account identity, Xero bank-account screen, statement-line range, Account Transactions range, reconciliation details, Bank Reconciliation report pack, History & Notes where relevant, feed status, conversion date, opening balance, lock dates, and a list of recent imports or app changes. Record the exact report date because Xero evaluates balances and future-dated matches against it.
Classify the symptom before choosing a tool. Missing statement lines point toward a feed delay, start-date gap, unsupported period, or failed manual import. A wrong Statement Balance points toward opening balance, missing, duplicate, deleted, or user-created statement lines. A wrong Balance in Xero points toward missing, duplicated, misdated, or miscoded account transactions. A line reconciled to the wrong item is a link problem. A correct current screen with a bad historical report may be a future-date or prior-period issue rather than a current-feed failure.
Start at the earliest date where the source statement, Xero statement lines, account transactions, and report pack stop agreeing. Work one account and one bounded period at a time. Compare counts, dates, signed amounts, source fields, and import origin, but mask real identifiers in the case record. Do not disconnect a healthy feed merely because a balance is wrong; disconnection changes future flow and can complicate ownership without repairing an old duplicate or incorrect reconciliation.
- Preserve source statements, Xero statement lines, account transactions, reconciliation details, report pack, feed status, conversion settings, and lock dates.
- Label the failure as feed coverage, statement history, opening balance, account transaction, reconciliation link, rule or suggestion, report date, or close control.
- Identify the earliest affected line and the last date where Statement Balance, Balance in Xero, source bank, and report evidence all agreed.
- Record every recent CSV import, Conversion Toolbox run, feed reconnect, connected-app change, manual mark-as-reconciled action, and bulk edit.
- Assign a recovery owner and independent accounting reviewer; prohibit unlogged deletions, forced adjustments, and whole-account experimentation.
Review Match, Create, Transfer, Rules, and Duplicates Deliberately
For each unreconciled statement line, first ask whether the economic event already exists in Xero. If it does, use the suggested match or Find & Match and confirm the contact, document, date, amount, currency, tax, and account context. If it does not, Create can record a spend or receive money transaction, while Transfer handles movement between Xero bank accounts. Discuss is the safer destination when evidence is incomplete. Creating a second cash transaction for an existing invoice or bill payment produces duplicate revenue, expense, receivable, or payable effects.
Treat automation as review assistance. Xero may suggest an existing transaction based on similarities, propose a new transaction from a bank rule, reuse a prior reconciliation pattern, or make a prediction from statement details. A bank rule creates a suggested transaction only after a person reviews and accepts it. Inspect the Who, What, Why, tax rate, tracking, description, currency, and transfer implications before selecting OK. Disable or refine a rule that repeatedly suggests the wrong treatment and document any batch corrected under the old logic.
Delete a statement line only after proving it duplicates another line for the same bank event. Xero warns that deletion changes Statement Balance and recommends categorising a personal transaction to drawings rather than deleting it. Deleted statement lines remain restorable. If a whole statement was imported twice, use the supported statement-level cleanup after preserving counts and dates. Keep one evidence row connecting the source event, retained line, deleted line, linked Xero transaction, action, approver, and post-change report result.
- Match an existing invoice, bill, payment, transfer, overpayment, prepayment, or cash transaction before considering creation of a new record.
- Use Find & Match when the right transaction exists but Xero's leading suggestion is incomplete or wrong; verify every component before acceptance.
- Review bank-rule, memory, and prediction results as proposals, with special attention to transfers, tax, tracking, processor deposits, and unfamiliar contacts.
- Prove duplicates with the source statement, import origin, date, signed amount, reference, and retained counterpart before deleting a statement line.
- Route personal activity to an approved drawings or equivalent account and send ambiguous lines to Discuss instead of removing authentic bank evidence.
Use the Report Pack to Find Exceptions and Date Effects
Run the Bank Reconciliation report pack for the earliest affected period and a current comparison period. The Summary shows Balance in Xero, outstanding payments or receipts, unreconciled statement lines, calculated Statement Balance, bank statement ending balance, and sometimes imported statement balance. Enter the actual online-bank ending balance for the report date when appropriate, then interpret each difference separately. Do not transpose the source statement's closing balance into a ledger field simply to make one total agree.
Use the Bank Statement report to inspect line date, import date, reconciliation state, and source. User-created statement lines can reveal manual Mark as Reconciled activity. Use Statement Exceptions to find potential duplicates, deleted lines, and lines created by manually marking account transactions as reconciled. Xero notes that a reconciled statement line or account transaction matched to a future-dated item can appear unreconciled when the report date precedes the later item, so align the pack date before treating that result as a broken link.
Trace anomalies into reconciliation details and the underlying accounting transaction. A manually marked transaction creates a Xero statement line; if the authentic bank line later imports, the account can contain a duplicate statement line. A line matched to a spend or receive money transaction instead of the intended invoice or bill payment can duplicate the accounting effect even though the line shows reconciled. Build a chronological exception table and obtain approval for the smallest correction that restores both the historical report and the current ledger.
- Run Summary, Bank Statement, and Statement Exceptions for the same account and pack date, then preserve the exact filters and exports.
- Compare Balance in Xero, calculated Statement Balance, imported Statement Balance, entered bank ending balance, and actual online-bank balance by definition.
- Investigate future-dated pairs, outstanding account transactions, unreconciled lines, deleted lines, potential duplicates, and User-sourced statement lines.
- Trace every exception through reconciliation details to the invoice, bill, cash transaction, transfer, overpayment, prepayment, or manually created line.
- Separate a display or date-range issue from a real statement, ledger, or link defect before approving any rework.
Apply the Smallest Rework and Reconcile Forward
Choose Unreconcile when the accounting transaction is valid but connected to the wrong statement line. Xero normally keeps both records and removes the connection, allowing the statement line to be matched correctly. A manually marked-as-reconciled transaction is a special case because unreconciling it can remove the corresponding Xero-created statement line. Capture the origin first. Choose Remove & Redo when the account transaction itself is wrong and should be deleted so the authentic statement line returns to an unreconciled state.
Use statement-line deletion for a proven duplicate and Restore when a line was deleted incorrectly. If an invoice or bill payment was replaced by an incorrect spend or receive money transaction, Remove & Redo can delete the incorrect cash record; if the valid payment is merely linked to the wrong statement line, Unreconcile preserves that payment. Avoid a generic reconciliation adjustment whose only purpose is to force the difference to zero. Escalate tax, locked-period, conversion, multicurrency, payroll, or material financial-statement effects to an Advisor and the responsible accountant.
Reconcile from the corrected earliest period forward, rerunning the same report pack after each controlled batch. Compare aged receivables and payables, cash, transfers, tax accounts, income and expense, and any settlement clearing accounts affected by the rework. Close or relock the period only after an independent reviewer ties the result to the source statement and approves the exception log. Prevent recurrence with import boundaries, feed monitoring, rule ownership, reconciliation cadence, restricted manual-mark privileges, and retained monthly report packs.
- Use Unreconcile for a wrong relationship when the underlying account transaction should remain, after checking whether the line was manually created.
- Use Remove & Redo when the created account transaction is wrong and should be deleted before the authentic statement line is reconciled again.
- Delete only a proven duplicate statement line; restore an incorrectly deleted line and preserve the reason, actor, source, and report effect.
- Reconcile forward from the earliest correction and recheck receivables, payables, transfers, cash, tax, settlement, and financial-statement consequences.
- Retain before-and-after reports, approvals, exception evidence, and preventive-control changes before closing or reapplying lock dates.
Vendor documentation and ALLMSP resources
- Xero Central: Bank reconciliation in Xero
- Xero Central: Reconcile your bank account
- Xero Central: About bank rules
- Xero Central: Bank Reconciliation reports
- Xero Central: View bank reconciliation details
- Xero Central: Delete or restore a bank statement line
- Xero Central: Unreconcile an account transaction
- Xero Central: Fix an incorrectly reconciled bank statement line
- Xero Central: Manually mark a transaction as reconciled
- Xero Central: Reconcile and close a period
- Xero Central: Why are the Statement Balance and Balance in Xero different?
- ALLMSP: Xero software support category
- ALLMSP: Software support
- ALLMSP: Managed IT
- ALLMSP: CPA and financial firms
- ALLMSP: Contact the team
Frequently Asked Questions
What is the difference between a bank statement line and a Xero transaction?
A statement line represents bank activity imported by a feed, statement file, or certain Xero actions. A Xero transaction is the accounting record, such as an invoice payment, bill payment, transfer, spend money, or receive money entry. Reconciliation links them or creates the required accounting transaction.
Why can Statement Balance and Balance in Xero be different?
They are calculated from different records. Statement Balance follows the opening bank balance and statement lines, while Balance in Xero follows account transactions. Missing or duplicate lines, outstanding transactions, date differences, conversion errors, manual reconciliation, or incorrect accounting records can make them diverge. Diagnose the layer before editing.
When should a Xero statement line be matched instead of created?
Match when the underlying event already exists as an invoice payment, bill payment, transfer, expense, overpayment, prepayment, or cash transaction. Use Find & Match if the right item is not the leading suggestion. Create a new transaction only when evidence shows no accounting record exists for that bank event.
Do Xero bank rules post transactions without review?
In the standard reconciliation flow, a matching bank rule suggests a new transaction for the statement line. A user reviews the details and selects OK, edits them, or chooses another treatment. Treat the rule as a proposal, validate tax and account coding, and monitor repeated misclassification rather than assuming automation proves accuracy.
When is it safe to delete a Xero bank statement line?
Delete only when source evidence proves the line is a duplicate. Deletion changes Statement Balance. Xero recommends categorising personal activity to drawings rather than deleting an authentic bank event, and deleted lines remain restorable. Preserve the retained counterpart, import origin, approval, and before-and-after report effect.
What if a personal transaction appears in a business bank feed?
Keep the authentic statement line and categorise it to an accountant-approved drawings, owner, or equivalent account instead of deleting it merely because it is personal. Attach or retain evidence, follow tax and entity policy, and escalate uncertain treatment. Removing real bank activity makes statement completeness harder to prove.
What is the difference between Unreconcile and Remove & Redo in Xero?
Unreconcile removes the relationship while normally preserving the account transaction and statement line, so use it when the match is wrong. Remove & Redo deletes the account transaction and returns the statement line for rework, so use it when the created transaction is wrong. Check manually created lines first.
Why does a reconciled Xero item appear unreconciled on an earlier report?
The Bank Reconciliation report evaluates the selected date. Xero notes that a statement line or account transaction matched to a future-dated counterpart can appear unreconciled when that later date falls beyond the report cutoff. Align dates and inspect reconciliation details before changing an otherwise valid current match.
Can Mark as Reconciled create a duplicate bank line?
Yes. Xero creates a statement line when an account transaction is manually marked as reconciled. If the authentic bank-feed or imported line later arrives, both can exist. The User source in report details helps identify the created line. Confirm the duplicate, then follow the supported deletion and reconciliation path.
When should Xero bank-reconciliation recovery be escalated?
Escalate material, tax, multicurrency, conversion, payroll, locked-period, system-account, or prior-financial-statement effects to an Advisor and responsible accountant. Also escalate unexplained deleted lines, broad duplicates, suspected unauthorised activity, or a proposed adjustment used only to force zero. Preserve reports before support or accounting changes begin.
