Before signing off a bank reconciliation working paper, a reviewer should check five concrete things: that the reconciliation covers the full statement period and not a sample, that the match rule (exact amount, a stated date window) is documented rather than implied, that every unmatched item is listed individually with a stated explanation rather than netted into a balancing figure, that stale or recurring items are flagged rather than silently rolled forward, and that the closing reconciled balance actually ties to both the general ledger and the bank confirmation or statement closing balance independently.
The five checks, in order
- 01Full population, not a sampleConfirm the working paper states it covers every transaction in the period, not a selection. If it's a sample, the sampling basis and why it was considered sufficient needs to be documented separately — it shouldn't be assumed.
- 02The match rule is written downThe working paper should state what counted as a match — exact amount, and the date window applied (and why that window was chosen for this client). If the only evidence is a tied-out total with no stated rule, you can't tell whether the matching was consistent or just happened to balance.
- 03Every unmatched item is individually listed and explainedEach outstanding cheque, deposit in transit, or discrepancy should appear as its own line with a stated explanation and, where relevant, evidence it cleared in the subsequent period. A single 'other reconciling items' line covering several transactions is a documentation gap, not a reconciliation.
- 04Recurring or stale items are flagged, not just rolled forwardCompare this period's outstanding list against the prior period's. An item that's reappeared for the third consecutive month needs a specific note on why it's still there — rolling it forward unchanged is a sign nobody re-examined it.
- 05The closing balance ties two waysThe reconciled balance should tie to the general ledger cash account and separately to the bank's own closing balance (statement or confirmation) — not just internally consistent within the working paper itself.
Specific traps worth looking for
| What it looks like | Why it's a trap | What to ask for instead |
|---|---|---|
| A perfectly clean reconciliation with zero outstanding items | Real bank accounts almost always have at least a small timing difference at any cut-off; a flawless tie is more often evidence of a forced balance than a genuinely clean account | Ask the preparer to walk through how the zero was achieved — specifically whether anything was written off or netted to get there |
| A large reconciling item explained only as 'timing difference' | This phrase explains nothing on its own — it describes a category, not a reason | Ask for the specific transaction, its date, and evidence of when it cleared |
| Outstanding items dated more than 90 days before period end | A cheque genuinely outstanding that long is unusual and often means it should be reissued, voided, or investigated as something else entirely | Ask the client directly why it's still outstanding, and document the answer |
| A reconciliation prepared by the same person who also posts bank entries, with no independent review evident | Removes the segregation-of-duties benefit the control is supposed to provide | Confirm, separately from the reconciliation itself, who reviewed it and when |
| A date window wide enough that unrelated transactions could plausibly pair on amount alone | A loose window can produce matches that look fine in the summary but are wrong at the transaction level | Spot-check a handful of matched pairs individually, not just the match count |
The riskiest working paper to sign off isn't the one with a long list of unresolved exceptions — at least those are visible and demand attention. It's the one that ties exactly with nothing left over, because that's the one a reviewer is most tempted to approve without actually checking how it got there.
Documentation standard worth holding the file to
SA 230 requires working papers to be sufficient for an experienced auditor with no prior connection to the engagement to understand the work performed and the conclusions reached. A bank reconciliation working paper that shows only a final tied-out number, without the match rule, the individual exceptions, and their resolution, does not meet that bar — regardless of whether the number itself happens to be correct.
Regulatory requirement
SA 230 requires audit documentation to be sufficient to enable an experienced auditor, having no previous connection with the engagement, to understand the nature, timing, and extent of procedures performed and the results obtained.
How we think about this
Lekhya's bank reconciliation leaves the match rule, the full matched population, and every individual exception visible on the same working paper — so a reviewer checking this list isn't reconstructing what happened from a single tied-out total, they're looking at the actual record of 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 & treasuryBank confirmation letters: what to request and verifyWhat a bank confirmation covers beyond the balance, how to keep the request genuinely independent, and what to do when the bank is late.
- Bank, cash & treasuryA bank reconciliation workflow for audit firms, not just a procedureMatching the ledger against the bank statement is mechanical. Doing it the same way across every client file, with every unmatched item actually explained, is the part firms get wrong.
- 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.
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.