Outstanding items in a bank reconciliation are a genuine risk-assessment signal, not just a mechanical reconciling balance, because the pattern across periods — what stays outstanding, for how long, in which direction, and whether the same items recur — tells you things about a client's cash management that the reconciliation's bottom-line balance never will. A reconciliation that ties to zero every month while carrying the same three stale cheques forward is not evidence of good cash control; it's evidence no one is looking at the detail behind the number.
The mechanical view vs the pattern view
Most working papers treat outstanding items as a point-in-time list: these cheques haven't cleared, these deposits haven't landed, the total nets to the reconciling difference, done. That's necessary but not sufficient. The more useful question is what the list looks like across the last six or twelve month-ends, laid side by side — because a single outstanding item is almost never meaningful on its own, and a recurring one almost always is.
| Pattern across periods | What it typically signals | Why it matters beyond the reconciliation |
|---|---|---|
| Same cheque numbers outstanding for 3+ consecutive month-ends | Stale cheques the client hasn't cancelled or re-issued, or a payee that isn't banking them | May indicate the payable is effectively settled in substance but still carried as a liability, or a control gap in cheque cancellation |
| Deposits in transit consistently larger near month-end than mid-month | Collections are being timed or batched around the reporting date | Worth checking whether this reflects genuine business rhythm or a cut-off management practice around receivables |
| A growing number of small, unexplained bank-side credits/debits | Bank charges, TDS on interest, or minor corrections not being posted promptly | Points to a weak month-end close process on the cash side, which often correlates with weak close discipline elsewhere |
| Outstanding items that reverse and reappear (cleared one month, back the next) | Post-dated cheques, or cheques being recalled and reissued | Can indicate liquidity management under strain — delaying presentation of payments rather than genuine timing lag |
| A reconciling difference that's consistently resolved by a single large plug | A client-side adjustment not independently traced | This is the one that most often turns out to be masking something, not explaining it |
Why this belongs in risk assessment, not just substantive testing
SA 315 asks the auditor to understand the entity and its environment, including its financial reporting and, by extension, how it actually manages cash — not just to confirm the year-end cash balance is correct. A pattern of recurring stale items or recalled cheques is a data point about how the client runs its treasury function day to day, which is exactly the kind of thing risk assessment is meant to pick up. Treating outstanding items purely as a substantive-testing artefact, disconnected from the risk assessment that was done earlier in the engagement, means the same evidence gets looked at twice without either look benefiting from the other.
Regulatory requirement
SA 315 requires the auditor to obtain an understanding of relevant controls over financial reporting, which for cash includes how the client monitors and clears reconciling items — not merely that a reconciliation exists.
A practical way to use this across the engagement
- 01Pull the exception list across periods, not just the current oneCompare outstanding items month over month (or at minimum, quarter over quarter) rather than reviewing each period's reconciliation in isolation.
- 02Flag recurrence, not just magnitudeA small item that's recurred five times is a more interesting finding than a large item that appeared once and cleared normally.
- 03Ask the client about recurring items directlyThis is one of the few areas where a direct, specific question — "why has this cheque been outstanding since June?" — tends to get a genuinely informative answer, because it's concrete rather than a general control inquiry.
- 04Feed what you find back into the risk assessmentA pattern that suggests liquidity pressure or weak treasury discipline should inform judgements elsewhere in the audit — going concern considerations, related-party funding arrangements, or the reliability of management's cash-flow projections.
Don't let a reconciliation that ties exactly to zero read as a clean bill of health. A perfectly balanced reconciliation with the same stale items quietly carried forward every month is often worse evidence than one with a small, genuinely unexplained difference that the client is actively chasing.
How we think about this
Lekhya keeps every unmatched item visible, by period, rather than folding it into a single reconciling balance — specifically so a pattern across periods is something you can actually see and use, not something buried inside a working paper that gets rebuilt from scratch every month.
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 & 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 & 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 & treasuryPetty cash audit: controls and common failuresThe imprest system, voucher-level testing, the split-purchase trick used to dodge approval limits, and reconciliation frequency.
- Audit documentationHow to test bank overdraft classification between cash equivalents and borrowingsThe same overdraft facility can be a cash equivalent in the cash flow statement and a borrowing on the balance sheet. Testing it means checking both treatments separately, against different rules.
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.