A bank reconciliation workflow matches every ledger entry against the bank statement by amount and a configured date window, across the full period rather than a sample, and treats anything left over — outstanding cheques, deposits in transit, or a genuine discrepancy — as a named item on a register rather than a number buried in a working paper. The test itself is simple. What makes it a workflow rather than a one-off exercise is doing it identically on every engagement and chasing every unmatched item to an actual explanation.
Why a sample is the wrong instinct here
Bank reconciliation is one of the few audit areas where testing the full population costs almost nothing extra. A statement and a ledger are both already in a structured, line-item format — there is no scanning, no manual transcription, no reason to sample down to twenty-five items and extrapolate. Sampling a bank reconciliation is a habit left over from when matching had to be done by eye, not a methodology choice that still earns its place.
Common practice, not a requirement
Testing the full population does not change what the standards require you to conclude. It changes how much of the population you actually looked at before concluding it.
What to match on
- 01Amount, exactlyA ledger entry and a bank line match on amount. Tolerances invite false matches — a ₹0.50 rounding tolerance will happily pair two unrelated transactions that happen to land close together.
- 02A date window, not a dateA cheque issued on the 28th may not clear until the 3rd of the following month. Matching on a window — typically 7 to 15 days either side, set by the engagement team rather than fixed by the tool — catches the normal lag between posting and clearing without widening the window so far that unrelated transactions start pairing up.
- 03One-to-one, not many-to-oneA single ledger entry should match a single bank line. Where a bank genuinely posts in batches — several small deposits swept into one line — that is a data-quality fact worth recording, not a reason to let the matching logic quietly aggregate entries to force a match.
What's left over is the actual audit evidence
Everything that doesn't match falls into one of a small number of categories, and each one means something different for the engagement.
| Unmatched item | What it usually means | What to do with it |
|---|---|---|
| In the ledger, not on the statement | An outstanding cheque or payment not yet presented, or a deposit in transit | Confirm it clears in the subsequent period; if it's old, ask why it's still outstanding |
| On the statement, not in the ledger | A bank charge, interest credit, or dishonoured cheque not yet recorded | Post the missing entry, or confirm the client already corrected it |
| Matched on amount but suspicious | Two unrelated transactions that happen to share an amount and fall inside the date window | Trace both independently rather than accepting the match on amount alone |
| Persistently unmatched across periods | A reconciling item the client has been carrying forward without resolving | This is the one worth a direct question to the client — not a rollforward note |
An unmatched item is a finding to investigate, not a balancing figure to plug. Writing off a stale reconciling item because the amount is immaterial is a judgement about materiality that belongs to the engagement team, made explicitly — not a default the workflow should ever apply on its own.
Running it the same way every time
The value of a workflow over a procedure is that the match rules, the date window, and the categorisation of what's left over are fixed firm-wide rather than reinvented by whoever is on the file this month. That consistency is what lets a reviewer open any engagement's bank reconciliation and immediately understand what they're looking at, instead of first having to work out which matching convention this particular preparer used.
How we think about this
Lekhya runs this matching deterministically — amount and a configured date window, one-to-one, across the full statement period — and leaves everything it can't match as a named exception rather than a cleared balance. The judgement about what an unmatched item means for a specific client stays with the person reviewing it.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- Bank, cash & treasuryBank reconciliation audit procedure for statutory auditWhat a BRS must reconcile, the red flags that separate a timing difference from a cover-up, and how many months you actually need to review.
- Bank, cash & treasuryWhy your cash book balance never exactly matches the bank statementA difference between your books and the bank is the expected state, not the exception. The question is always which specific items explain it.
- Bank, cash & treasuryAuditing foreign currency bank accounts and EEFC balancesRestating EEFC and other foreign currency balances at year end, testing the exchange gain or loss, and the documentation worth sighting.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.