This is a composite, illustrative scenario built from how a bank guarantee disclosure gap typically surfaces, not an account of a named client. A routine bank confirmation letter listed a performance guarantee outstanding on the client's behalf, issued to a government department as part of a tender, but the client's draft notes to accounts carried no corresponding contingent liability disclosure. The guarantee itself was legitimate and properly authorised — the gap was in the client's own financial-reporting close process, which tracked guarantees operationally but had no step feeding them into the disclosure checklist.
Why the bank confirmation caught it and the client's own records didn't
A bank confirmation letter is independent evidence — it comes directly from the bank, not filtered through the client's own records, which is exactly why it is required rather than optional. The client's internal guarantee register, maintained by the treasury team, did show the guarantee. What it lacked was any link to the finance team's year-end disclosure checklist, so the item existed in one part of the business and simply never reached the part responsible for the notes to accounts.
Common practice, not a requirement
This kind of gap is common at companies where guarantee issuance sits with treasury or a business-development team rather than finance, and no single checklist forces a reconciliation between “guarantees issued this year” and “guarantees disclosed in the contingent liability note.”
What was checked
- 01Confirmed the guarantee was genuine and still outstandingChecked the underlying tender documents and the bank's own confirmation date and amount, ruling out a stale or already-expired guarantee being confirmed in error.
- 02Checked whether a liability, not just a disclosure, was actually at riskReviewed the tender's performance terms. No breach had occurred and none was indicated — this stayed a contingent liability, not a provision.
- 03Checked the full guarantee register against the draft notesFound two guarantees in total missing from the disclosure note, not just the one the bank confirmation happened to surface.
- 04Asked why the process had missed themConfirmed the guarantee register and the disclosure checklist were maintained by two different teams with no reconciliation step between them — a process gap, not a one-off oversight.
What went into the file
- The bank confirmation evidence, cross-referenced to the client's internal guarantee register.
- Both missing guarantees added to the contingent liability note before the financial statements were finalised.
- A note that no actual liability had crystallised — this was a disclosure gap, not a misstatement of a recognised amount.
- A management letter point recommending the guarantee register reconcile to the disclosure checklist at each quarter-end, not only at year end.
How we think about this
A bank confirmation is one of the few procedures in an audit that is genuinely independent of the client's own records end to end, which is exactly why it keeps surfacing disclosure gaps that an internally sourced schedule would not. Treating it as a formality once the balance ties is how this kind of gap gets missed.
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 guarantee verification in a statutory auditWhy BGs are off-balance-sheet contingent liabilities, confirming with the bank, tracking expiry, and verifying the margin money behind each one.
- 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 & treasuryTreasury controls audit checklist for mid-market companiesSegregation of duties over payments, dual signatories, bank mandate review frequency, and whether cash flow forecasting is real or decorative.
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.
- 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.