Bank reconciliation should explain the difference - not make it disappear

Begin with the accounting question

Bank reconciliation compares statement lines with internal bank-register transactions. Timing differences can be legitimate: an issued payment may not have cleared, or a deposit may appear after period-end. Other differences reveal missing fees, duplicate receipts, incorrect amounts, wrong dates, or transactions posted to the wrong account.

The goal is a documented explanation and a controlled correction - not a forced zero difference.

How matching works

Rule order matters. A narrow exact-reference rule should normally run before a broad amount-and-date rule. Tolerances that are too strict leave routine timing differences unresolved, while tolerances that are too wide can pair unrelated transactions. Every automatic match should remain explainable after the fact.

What reconciliation must not conceal

Unmatched lines are not automatically errors. They may be deposits in transit, outstanding cheques, fees, interest, returned payments, recording delays, or genuinely missing ERP activity. The difference should remain visible until someone assigns a defensible resolution. Creating a balancing entry merely to reach zero defeats the control.

Bank-originated items may require a new authorized journal entry. Reversals need to connect opposite statement lines or canceled ERP transactions. Small differences may use a configured tolerance and correction account, but reviewers should still see the amount and rule responsible.

Close, approval, and measurement

A completed reconciliation should capture cut-off date, statement balance, book balance, matched totals, outstanding items, preparer, reviewer, and completion time. Reopening requires a reason and retained history. Measures can include automatic-match rate by rule, aged exceptions, matches later reversed, entries created during review, and time to close.

Simor ERP connects reconciliation to Bank Statements, Bank Register, Customer Receipts, Supplier Payments, transfers, and Journal Entries. An exception can therefore be corrected at its source rather than edited inside an isolated worksheet.

Background reading: Microsoft guidance on advanced bank reconciliation.

Potential matches can use amount, date tolerance, reference, transaction type, customer or supplier context, and bank account. One-to-one matches are only one scenario. One statement line may summarize multiple internal payments, and one receipt may relate to several invoices.

Simor ERP reconciliation capability

Simor ERP connects bank accounts, the bank register, imported or entered statements, customer receipts, supplier payments, journal entries, and the general ledger. Users can review statement activity against internal transactions and preserve the status of matched and outstanding items.

The workflow can be customized for file formats, matching tolerances, approval, role separation, dashboards, exception categories, and organization-specific close procedures.

Why reconciliations fail

Transactions are summarized differently

The bank may combine a payment batch while ERP retains individual supplier payments. Matching must support the relationship without destroying detail.

Corrections bypass the source process

Posting a journal solely to clear a difference may hide an unapplied customer receipt or duplicate supplier payment. Correct the originating workflow when possible.

Old exceptions remain open

Uncleared items require an owner and ageing. Repeatedly carrying the same difference weakens the control.

Month-end review checklist

Accounts should be prioritized by risk and activity rather than treated identically. High-volume operating accounts, payroll accounts, merchant settlement accounts, and accounts with frequent manual entries may need different frequency, rules, reviewers, and escalation thresholds.

Ownership of every unresolved item should be assigned before sign-off, together with an expected resolution date and follow-up route.

• Confirm statement account, period, and opening balance.
• Investigate duplicate and missing statement lines.
• Review matched items above risk thresholds.
• Classify deposits in transit and outstanding payments.
• Resolve fees, interest, returns, and unidentified activity.
• Reconcile the bank register to the general ledger.
• Lock or approve the completed period according to policy.

Example: the ledger and bank disagree at month-end

Consider a cheque recorded in the ERP but not yet cleared, a customer deposit appearing at the bank one day later, a monthly service fee missing from the ledger, and one duplicated receipt. The reconciliation should separate legitimate timing items from errors. Marking everything as matched would hide the very differences the review is meant to expose.

The reconciler needs the statement line, candidate ERP transactions, dates, references, currencies, amounts, and prior matching decisions in one view. A service fee may require an approved journal entry; an outstanding cheque remains an explained difference; the duplicate receipt requires correction through its source workflow. Each resolution should retain who made it and when.

Completion should be based on evidence: statement opening balance, closing balance, reconciled book balance, listed outstanding items, and a controlled sign-off. Reopening a completed reconciliation should require an explicit reason so later reviewers can distinguish a normal correction from an unexplained change.

Evidence to test before approving a reconciliation

Build a test account containing exact matches, date differences, repeated amounts, a grouped deposit, several invoices paid by one withdrawal, an outstanding cheque, bank fee, interest, reversal, and a legitimate penny difference. Run narrow matching rules first and confirm that broad rules do not steal transactions from stronger candidates.

Review every automatic match using the evidence available to a month-end preparer. Then unmatch and correct selected items, post an authorized bank-originated entry, and complete the reconciliation with outstanding timing items. Totals must remain explainable before and after each action.

Finally, reopen the completed period using an authorized role. The system should preserve the original completion, reason for reopening, changed matches, reviewer identity, and new result. That history matters more than a green completion indicator because it shows whether the control remained effective after close.

Connect the evidence

Start with bank-statement intake, review period and lock-date controls, or inspect Simor ERP Accounting.