Testing expected credit loss under Ind AS 109 means testing three distinct layers: first, whether financial assets were correctly allocated to Stage 1 (12-month ECL), Stage 2 (lifetime ECL, where credit risk has increased significantly since initial recognition) or Stage 3 (credit-impaired, lifetime ECL); second, whether the probability of default, loss given default and exposure at default inputs used to compute the ECL are supportable and consistent with the entity's own historical loss experience adjusted for forward-looking information; and third, whether any management overlay applied on top of the model's raw output is separately justified, since overlays are where unsupported judgement most often hides.
Testing the stage allocation
- 01Recompute days-past-due triggers against the entity's own policyConfirm the rebuttable presumption that significant increase in credit risk occurs at 30 days past due (and default at 90 days past due) is applied as stated, and any rebuttal of that presumption is specifically documented and supportable.
- 02Test qualitative triggers for stage migration, not just quantitative onesA customer in financial distress, a covenant breach, or a credit rating downgrade should move a receivable or loan to Stage 2 or 3 even where days-past-due alone would not — check these aren't being missed because the model is purely aging-based.
- 03Sample-test individual large exposures for stage 3 identificationA material receivable or loan with objective evidence of impairment (restructuring, significant financial difficulty, breach of contract) should be in Stage 3 regardless of what an aggregate provisioning matrix would otherwise compute.
Testing the ECL computation itself
- 01Trace the historical loss rate used to actual collection/write-off dataRecompute the loss rate from the entity's own aged receivables and actual historical write-offs over a representative period, rather than accepting a provision matrix rate without recalculation.
- 02Test the forward-looking adjustmentMacroeconomic overlays (GDP growth, sector-specific outlook) applied to historical loss rates should be based on reasonable and supportable information available without undue cost or effort at the reporting date — a generic adjustment with no link to the entity's actual exposure sector should be challenged.
- 03Test any post-model management overlay separately from the model outputAn overlay added or removed at management's discretion at period end needs its own rationale and evidence trail — recompute the model's unadjusted output first, then evaluate the overlay as a distinct estimate.
An ECL provision that has stayed at almost the same percentage of receivables for several consecutive periods, despite a changing customer mix or deteriorating ageing profile, usually means the model is not actually being recalibrated each period — treat a static rate as a sign the underlying data refresh needs to be tested, not assumed.
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-offInd AS 109: financial instruments and the expected credit loss modelThe old model waited for a loss to be incurred before providing for it. ECL is built the opposite way — provide for the loss you expect, before it happens.
- 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-offDebtors confirmation procedure: balance confirmation in practicePositive versus negative confirmation, selection criteria, handling non-responses and disputes, and the alternative procedures that cover the gap when confirmations fail.
- Audit workflow & automationSA 540: auditing accounting estimates, where judgment replaces a verifiable numberAn estimate can't be vouched to a source document the way an invoice can. SA 540 is about what replaces vouching when there's no single right answer to check against.
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.