Name the two balances, align their cutoff, and build a transaction bridge. Most mismatches stay confusing because a closed statement, live account, bookkeeping ledger, or extracted spreadsheet is compared without a shared time boundary.
This illustration uses imaginary information. Check actual statement details directly against the source.
Define both sides of the mismatch
Write down the exact balance labels, sources, accounts, currencies, and timestamps. A statement closing balance, online current balance, available balance, bookkeeping bank balance, spreadsheet running balance, and cash-flow total are not interchangeable. State the precise difference and whether one source includes pending or later activity.
Recalculate the statement independently
Rebuild the period from its source opening figure, applying each posted debit and credit under the statement's own sign convention. Check page subtotals, continuation pages, signs, decimal separators, reversals, interest, fees, and adjustments. Verify the recomputed close against the statement's closing figure before investigating another system.
Balance mismatch control sheet
A control sheet turns an unexplained difference into a series of testable timing, scope, and data-quality exceptions.
Balance identities
Record source, label, account, currency, timestamp, cutoff, and exact amount for both sides of the comparison.
Statement proof
Recalculate opening balance through posted movement to printed closing balance, with page and control totals.
Difference schedule
List later activity, timing items, missing entries, extraction corrections, fees, interest, transfers, and currency effects separately.
Closure record
Assign evidence, owner, status, next action, and resolution to every remainder. Reject unexplained plug entries even when totals appear to agree.
Build bridges for timing and scope
For a live balance, add later posted credits and subtract later posted debits from the statement close using the correct sign convention. Keep pending holds separate. For a bookkeeping comparison, list outstanding payments, deposits in transit, bank fees, interest, direct debits, transfers, and book entries that have not reached the bank.
Close exceptions without plug entries
Give each remaining difference a date, amount, category, owner, evidence reference, and closure action. Age unresolved items from their original date. A repeated unexplained difference can indicate a stale payment, duplicated import, missing page, wrong opening balance, or entry posted to another account.
To reproduce the closing balance from the source rows, use the bank statement analyzer and keep any unexplained difference visible rather than forcing an adjustment.
The issued statement fixes a balance at its closing boundary. Later current and available figures answer different questions because postings, authorizations, deposit holds, and bank rules operate at different times.
A transaction expected in one statement can post in another period, remain pending, appear under a different description, belong to another account, reverse, or never complete. Test those possibilities before treating the statement as incomplete.
Apply this guide to a statement
Review a traceable ledger that separates extracted facts, calculated totals, suggested categories, recurring candidates, and unresolved data concerns.
