Bank reconciliation is the first reconciliation every controller learns and the one that quietly gets harder as the company grows. The bank statement is the easy side. The GL is the messy side. Everything between them — timing differences, in-transit items, payment-type drift — is where close gets stuck.
What bank reconciliation actually does
The mechanic is straightforward: match every transaction on the bank statement to a corresponding GL entry in the cash account. Anything unmatched is either a timing difference (deposit in transit, outstanding check, ACH not yet posted) or a missing entry that needs to be booked — bank fees, interest income, wire fees, returned items, FX adjustments.
The control purpose is more important than the mechanic. Bank rec is the last line of defense against unrecorded liabilities, fraud, and posting errors. If the GL cash balance doesn't tie to the bank's adjusted balance every period, you have a problem you haven't located yet.
Where bank reconciliation breaks
A typical close-week bank rec has one bank statement with a clean ending balance and a GL cash account that looks almost right but isn't quite:
A typical close-week bank rec
The differences aren't random. Four failure modes show up at virtually every company:
Timing differences that compound across periods. Deposits in transit on Day 31 become Day 1 deposits next month. Outstanding checks from prior periods get stale. Without a clean rollforward, last month's timing differences muddy this month's reconciliation, and the reconciler ends up tracing items across three statements instead of one.
Payment types the GL doesn't recognize automatically. Virtual cards, ACH reversals, Plaid-routed transactions, marketplace settlements — the bank feed labels them generically. The GL needs vendor-level coding. The mismatch accumulates in a "to investigate" column until someone codes it manually, often after the close target has passed.
Bank fees, interest, and FX hits that nobody booked. Wire fees from international payments. Lockbox fees deducted on the bank side. Interest on operating accounts. None of these post to the GL automatically unless the bank-to-GL coding map covers them — and the map drifts as banks introduce new fee codes each year.
Multi-bank, multi-account, multi-currency consolidation. At one bank with one currency, the rec is mechanical. At eight accounts across four entities in three currencies, the consolidation work is most of the rec. FX revaluation at month-end spot rates compounds the matching problem: the same transaction sits on each entity's ledger at a different translated amount.
What gets pushed to "next month" — and shouldn't
| Item | Why it gets deferred | What should happen instead |
|---|---|---|
| Aged outstanding checks (90+ days) | "Still might clear" | Void and reclassify |
| Unidentified deposits | No remittance; sits in suspense | Investigate with AR, book or return |
| FX revaluation gaps | Rate source inconsistency | Agree on rate and revalue consistently |
| Intercompany sweep timing | Posted bank side, not GL side | Document as timing, clear Day 1 next period |
APQC's monthly-close benchmark puts the median close at 6.4 calendar days and top-quartile teams at 4.8 or fewer, measured from trial balance to consolidated statements. Bank reconciliation is typically the Day 1 to Day 2 gate — items that get deferred into next month's rec are the primary reason close stretches beyond that. The same unrecognized payment type showing up in three consecutive periods is a process problem, not a one-time exception.
What good looks like
A clean bank rec at any company size has four properties: every transaction is matched or has a documented reason it isn't; the unmatched queue ages and clears (nothing over 60 days without an investigation note); the bank-to-GL coding map updates automatically when banks introduce new transaction codes; and the rollforward of timing items is preserved month-over-month, not rebuilt from scratch.
If your team is still exporting CSVs and reconciling in Excel, the AI-powered bank reconciliation guide covers what the matching logic looks like when it's automated. The structural failures — stale timing diffs, unidentified deposits, FX revaluation gaps — are solvable once the workflow stops requiring a human to rebuild context from last month's workpaper.
See how Cadel handles bank and cash reconciliation end-to-end — or get in touch to walk through your current close workflow.