A debtors confirmation procedure obtains direct written evidence from customers of the amount they owe at the balance sheet date, using either a positive request, which asks the customer to reply whether or not they agree, or a negative request, which asks them to reply only if they disagree. Because response rates on positive requests in Indian mid-market practice are often well below full, the procedure is incomplete without a defined plan for non-responses and disputed balances, built around alternative procedures such as testing subsequent cash receipts and matching invoice-level detail, rather than treating a low response rate as an unresolved gap in the file.
Positive versus negative confirmation
| Positive confirmation | Negative confirmation | |
|---|---|---|
| What it asks | Confirm the balance, or state the amount you believe is correct, and reply either way | Reply only if you disagree with the stated balance |
| Evidence if no reply | No evidence obtained; triggers alternative procedures | Treated as implicit agreement, which is weaker evidence by its nature |
| When it is preferred | Larger balances, balances in dispute, and where detection risk is assessed as higher | Larger populations of small, homogeneous balances where the combined risk is low |
| Practical note | Needs active follow-up; a plan for chasing non-responses must exist before letters go out | Silence proves nothing about whether the customer actually checked the statement |
Common practice, not a requirement
In most Indian mid-market engagements, positive confirmation is used for the larger individual balances and a sample of the remainder, rather than negative confirmation across the full ledger, because response rates to negative requests tend to be low enough that silence carries little weight either way.
Selecting which debtors to confirm
Selection should combine risk and coverage rather than picking the largest balances alone, which is the single most common shortcut that weakens the exercise.
- All individually material balances above a stated threshold
- A sample from the remainder, selected to give reasonable coverage of total receivables by value, not just by count
- Balances that are old, disputed, or have unusual activity such as a large credit note or a round-sum adjustment during the year
- Related-party balances, which usually warrant confirmation regardless of size because of the separate disclosure and pricing questions they raise
- Debit balances in creditor accounts and credit balances in debtor accounts, both of which are easy to miss if selection is driven purely by a sorted balance list
- Zero or fully provided balances that were large during the year, where the movement to zero is itself worth confirming
Running the exercise
- 01Control the despatchConfirmation requests should be prepared and sent (or the request put on the client's letterhead but despatched) with the audit team retaining control of the mailing list and the reply address, so that a response cannot be intercepted or redirected by client staff before it reaches the auditor.
- 02Set a realistic reply window and follow upA single mailing with no follow-up predictably produces a low response rate. Build at least one reminder round into the plan from the start rather than treating follow-up as a fallback once responses are seen to be thin.
- 03Reconcile each response receivedA response rarely agrees to the paisa, because the customer's own ledger reflects goods in transit, invoices raised near year end that have not reached them, or payments sent but not yet recorded by the client. Reconcile the difference item by item rather than accepting a response as a match because the headline figure is close.
- 04Chase every non-response before moving to alternative proceduresAlternative procedures substitute for a response that genuinely cannot be obtained, not for one that was never actually followed up.
Handling non-responses
Where a second request also gets no reply, the balance moves to alternative procedures rather than being left unaudited. Standard alternative procedures for a receivable balance include checking subsequent cash receipts against the invoices that made up the balance, and examining the underlying sales invoices, dispatch evidence and acknowledged delivery documents that support the recorded amount.
- 01Test subsequent receiptsMatch cash or bank receipts after the year end to the specific invoices they settle, not just to the customer account in aggregate, so that a receipt against an invoice raised after year end is not wrongly used to support a pre-year-end balance.
- 02Vouch the invoice-level detail making up the balanceWhere receipts are insufficient or delayed, trace the invoices comprising the outstanding balance to dispatch evidence and customer purchase orders, the same evidence chain used in recognition testing.
- 03Consider the ageingA non-responding customer with a balance that has since been fully or substantially settled is a weaker concern than one with a balance that remains outstanding and ageing further, which should feed directly into the provisioning assessment.
Disputed balances
A customer who replies disagreeing with the stated balance has given you more useful evidence than one who agrees, because the dispute itself needs resolving. Document the reason given, reconcile the difference, and establish whether it reflects a timing difference, a genuine error in the client's records, or a substantive dispute over goods or pricing that may indicate a need for a credit note or a provision.
A pattern of disputes clustering around a particular product line, branch, or salesperson is worth escalating on its own, separately from resolving each individual difference, since it can point to a systemic billing or dispatch problem rather than isolated customer error.
How we think about this
Reconciling a confirmation reply against the ledger, matching subsequent receipts to specific invoices, and flagging balances that are old or unusual for selection are all rule-based matching that should run across the full receivables population rather than a sampled subset. Deciding what a disputed reply actually means for the financial statements is a judgement call that depends on facts outside the ledger, and that has to stay with the auditor.
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
- Revenue, receivables & cut-offCommon exceptions in revenue and receivables testingA reference catalogue of the exceptions that recur most often across revenue and receivables testing, why each happens, and what to do about it.
- Revenue, receivables & cut-offAuditing bad debts and the provision for doubtful debtsThe expected credit loss model at a practical level, how it compares to ageing-based provisioning, testing management's assumptions, and the write-off authorisation trail.
- Revenue, receivables & cut-offTesting related-party sales and transfer-pricing flagsIdentifying related-party customers from the sales register, assessing pricing against arm's-length comparables at a practical level, and the audit approach that ties it together.
- 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.
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.