Bank statement reconciliation: balances, matches and exceptions

Reconcile a bank statement by checking the correct account and cutoff, associating each statement movement with supported book entries, and explaining the remaining balance differences. A CSV import, a proposed match or a zero difference alone does not establish that every transaction is correct. This workflow covers one checking or savings asset account in one currency.

Use a suitable bank export when available. If the source is PDF, LocalExtract can prepare transaction CSV on your device; the issued statement remains the source for balances and review.

Establish the account, cutoff and starting point

Keep the issued statement, the relevant cash-account ledger and the previous reconciliation together. Record the account, currency, statement start/end dates and opening/closing balances. Use the statement cutoff rather than assuming every statement follows a calendar month. Bring forward prior outstanding items; filtering the ledger to only this month can hide a check issued earlier that clears now.

The IRS recordkeeping guidance illustrates bank reconciliation by distinguishing outstanding checks, deposits not yet credited and bank charges. Its example is US guidance, not a jurisdiction-independent tax rule. Here those distinctions support an explicitly synthetic review exercise.

Verify the prior reconciled starting point before investigating this period’s transactions. If a previously reconciled entry changed, investigate its history rather than overwriting the opening balance to make the current period work. Intuit’s beginning-balance guidance explains why edits and deletions can affect it.

Associate occurrences, not just equal values

Give bank and book rows their own source references in a working review. Compare direction, amount, actual payment/reference information and dates in context. A posting date can differ from the date entered in the books. Equal date and amount can also describe separate payments.

Each row used in a confirmed association must remain accounted for. Do not let the first result of a lookup reuse one book entry for several bank rows. Grouped deposits, fees deducted from receipts and transfers may require a documented one-to-many or many-to-one explanation; do not invent a rounding entry to fit them. Hold an association when the evidence is insufficient.

Use the overlapping-export guide for repeated observations within source files. That task differs from associating a genuine bank movement with an existing ledger entry. An imported row can already exist in the books even when it appears only once in your CSV.

Work through a synthetic cutoff example

The following invented USD checking account has a verified opening balance of 1,000.00 USD on both sides. Receipts increase the asset balance; payments decrease it. The statement ends October 31, 2026. References C201 and C202 deliberately identify different checks in this exercise; a real reference must be verified, not assumed unique.

B2 has two same-date, same-amount candidates in the books, L2 and L3, if you look only at the issue date and value. The scenario’s check evidence associates B2 with L2, leaving L3 outstanding. If that evidence were missing, both candidates would stay unresolved; choosing the first row would not establish a match.

The bank closes at 1,290.00 USD: opening 1,000.00 + receipt 500.00 − cleared check 200.00 − fee 10.00. The unadjusted books close at 1,180.00 USD: opening 1,000.00 + receipt 500.00 − two checks totaling 400.00 + deposit 80.00.

The outstanding check and deposit explain timing differences; they are not new transactions to enter again. The fee calls for a supported book entry under your review process. A suspected bank error instead needs investigation with the bank. Apply corrections in the appropriate system only with the required authorization, then retain the resulting references.

Download the synthetic reconciliation cases for both source lists, explicit associations and a control where missing check evidence blocks confirmation. Python and Decimal verify the defined balances and one-use reference checks; this is not a spreadsheet or accounting-software execution test.

Review exceptions before signing off

Keep an exception register with the bank/book references, evidence, decision, responsible person and status. Carry forward supported timing items and follow up their subsequent clearing. Distinguish them from unexplained differences, missing statements, unknown signs or uncertain account scope, which keep the affected reconciliation open.

Do not change an amount, discard a row or add a balancing adjustment merely to reach zero. Intuit’s ending-balance troubleshooting starts with statement information and transaction errors. A summary can locate differences, but equal totals cannot prove transaction identities: an omitted +25.00 receipt and an omitted −25.00 payment cancel numerically while both remain missing.

When the evidence is complete, retain the statement, ledger version, reviewed associations, supported corrections, carried items and reconciliation report. Use the accounting product’s own completion workflow. The GnuCash guide explains why imported “cleared” status is different from completed statement reconciliation; other products have their own states.

Payoneer: request evidence appropriate to the processing state

A platform withdrawal can require several source objects before it can be associated with the bank receipt. In Payoneer, first identify the actual currency balance and period in Transactions. The Transactions FAQ distinguishes Upcoming activity that has not affected the balance from completed balance-affecting activity. Filtered exports cover the selected population; an early blank fee is not zero. Withdrawal fees are updated in transaction details after the withdrawal is sent to the bank and completed.

The reports FAQ describes a monthly report for a specified currency balance and month; another period calls for a filtered transaction summary. Its CSV includes source/target/reference information absent from the shorter PDF presentation. Keep those native fields when available, together with the particular withdrawal confirmation. Do not assume every account has the same bank/card/balance selector.

The withdrawal FAQ distinguishes an indicative conversion quote from the actual processed rate. Where the conversion fee is included in that rate, do not invent a second subtraction from the confirmed target amount. A separate bank/intermediary deduction still needs its own evidence; the withdrawal’s internal description is not a universal bank-statement joining key. Leave missing receipt, fee and reference evidence open in the exception register rather than explaining a difference solely by its size. Payoneer sources checked October 17, 2026.

Record the evidence object before allocating or reversing a receipt

A bank movement and its supporting record are different objects. For a UK rental receipt covering two tenants, retain the single bank reference, tenancy/rent period, remittance evidence and supported portion for each tenant. GOV.UK’s rental-record guidance calls for rent records, receipts, invoices and bank statements; it does not allocate a particular combined receipt for you. If remittance support is missing, leave the allocation open rather than duplicating the entire receipt for each tenant. The FreeAgent rental-statement guide covers a different, product-specific letting-agent statement route.

For a payment later returned, preserve separate original, return and evidenced charge references, each with its own currency and posting date. Link the events only where their relationship is supported. Do not erase the first receipt or call the difference a fee merely because the arithmetic fits. A charge without its own evidence stays unresolved.

As a source-specific illustration, Wise Platform’s developer status documentation distinguishes outgoing_payment_sent from beneficiary-bank posting, and bounced_back from a completed funds_refunded result. These are API status names, not universal bank-statement fields or identical consumer-app labels. The refund guide also distinguishes refund destinations by funding model. Neither source supplies your customer’s actual returned-payment reference or authorises a new payment.

This is an evidence register, not a posting template. The authorised reviewer decides allocation or correction from the retained records; the existence of an original receipt must remain visible even when a later event changes its economic outcome.

Keep extraction and time measurement separate

LocalExtract processes one PDF at a time with local parsing and OCR, exporting date,description,amount CSV. It has no desktop batch queue, automatic transaction matching or accounting synchronization. Balances, counterparty evidence and reconciliation decisions require their own sources and review. Account access and periodic Pro verification need a network; PDF conversion does not require uploading the file. Download LocalExtract for PDF preparation.

To evaluate your process, record preparation, extraction, corrections, import, exception investigation and review time separately for comparable documents. Keep failed attempts in the measurement. This guide supplies no verified time-saving percentage, expected minutes per statement or bank-format compatibility guarantee.

Updated October 15, 2026: replaced unsupported efficiency claims, lookup-based confirmation and batch recommendations with evidence-based reconciliation and a bounded example. Official sources checked on that date.

Updated October 17, 2026: added supporting-record and returned-payment exception relations. No particular rental allocation, return or fee is established by the examples.