This is a composite, illustrative scenario, not an account of a named client. The company's warranty provision had been calculated at a flat 1.5% of product sales value for three consecutive years, a rate set once and simply rolled forward each year without recalculation. The middle of those three years included a product recall on one appliance line, after which actual warranty claims paid that year ran at roughly 6% of sales for that line — four times the rate still being used to provide for future claims the following year, with no adjustment made to reflect the higher claims experience the recall had just demonstrated.
Why a flat rate survived a year that should have broken it
The finance team treated the 1.5% rate as a fixed policy rather than an estimate that had to be revisited each year against actual experience. The recall itself was expensed as it happened, through separate recall cost lines, which meant the warranty provision calculation — a mechanical multiplication of current-year sales by the historical rate — never ran into the recall data directly. Nobody connected the two numbers because they sat in different sections of the working papers.
What the provision reasonableness test found
- 01Compared the provision movement to actual claims paid, product line by product line, for each of the three yearsFor every line except the recalled one, actual claims tracked close to the 1.5% rate. For the recalled line, actual claims had run at roughly 6% in the recall year and remained elevated at around 3% the following year as residual claims continued coming in.
- 02Asked why the rate used for the provision had not been updated for that lineThere was no formal basis — it was simply the same rate applied company-wide, with no line-level differentiation at all.
- 03Recalculated the provision for the recalled product line using its own actual claims experienceThis increased the required provision for that line materially above what the flat rate produced.
- 04Checked whether the recall's root cause had been fixed or was still a live exposureManagement confirmed a design fix had been implemented from a specific production batch onward, which supported using the post-fix claims rate going forward rather than assuming the elevated rate would persist indefinitely.
| Year | Provision rate used | Actual claims as % of sales |
|---|---|---|
| Year 1 (pre-recall) | 1.5% | 1.4% |
| Year 2 (recall year) | 1.5% | 6.1% |
| Year 3 (this audit) | 1.5% | 3.0% (residual claims) |
What went into the file
- The claims-versus-provision comparison by product line across three years, isolating the recalled line from the rest.
- The recalculated provision for that line and management's revised estimate going forward, with the design-fix evidence supporting a tapering rate rather than a permanently elevated one.
- A note on why the generic company-wide rate was an inappropriate basis once one product line had a materially different claims profile.
A provision estimate that uses the same rate year after year without being tested against actual outcomes is not conservative by default — it is simply untested. A rate that happened to be reasonable before a recall is not automatically still reasonable after one, and the only way to know is to compare it to what was actually paid.
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
- Audit documentationHow to test warranty provisions against historical claim experienceRebuild the claims-experience model from actual claim data rather than the client's rate, test the assumptions, and check the prior provision against what was actually claimed.
- Audit documentationInd AS 37: provisions, contingent liabilities and contingent assets — the three-way splitThree categories, three completely different treatments — recognise it, disclose it, or say nothing. Getting the category wrong is the whole misstatement.
- Audit documentationHow to test litigation contingency disclosures against the legal case fileGet the full legal case file independently of management's summary, test the probability and measurement judgement on each matter, and confirm it externally with counsel.
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.