Ind AS 8 requires three fundamentally different accounting treatments depending on the actual nature of a change: a change in accounting policy is applied retrospectively, restating prior periods as if the new policy had always been used; a change in accounting estimate is applied prospectively, affecting only current and future periods with no restatement of the past; and a prior-period error is corrected retrospectively, as if it had never occurred. The classification decision — which of the three this actually is — matters more than the arithmetic, because a misclassified change produces financial statements that are internally consistent but wrong in a way that's hard to spot without knowing the standard's test.
The classification test
| Nature of the change | Classification | Treatment |
|---|---|---|
| A different accounting policy is adopted (e.g. switching from cost model to revaluation model for PPE) | Change in accounting policy | Retrospective — restate opening balances and comparative figures |
| New information becomes available that revises an estimate (e.g. a revised useful life based on new usage data) | Change in accounting estimate | Prospective — no restatement; affects the current and future periods only |
| A mistake is found — a calculation error, a misapplication of an existing policy, an omitted transaction | Prior-period error | Retrospective restatement, as if the error had never been made |
A change that's genuinely hard to classify between a policy change and an estimate change is treated as a change in estimate — Ind AS 8's own default rule for ambiguous cases, specifically because prospective treatment is simpler and the standard favours it when the distinction itself is unclear.
Why the classification is where misstatements actually hide
A company that quietly reclassifies what is actually a correction of last year's error as a "change in accounting estimate" avoids restating the prior year and avoids the more visible disclosure a correction requires — the current year's numbers look the same either way, but the comparative figures and the transparency around what happened are very different. This is exactly why an auditor reviewing any significant change in a client's numbers between periods should ask "what kind of change is this, really" rather than accepting the label management has put on it.
What has to be disclosed for each
- A voluntary change in accounting policy: the nature of the change, the reasons it provides more relevant and reliable information, and the amount of the adjustment for each line item affected, for the current period and each prior period presented.
- A change in accounting estimate: the nature and amount of the change, and its effect in the current period (and expected effect in future periods, if practicable to estimate).
- A prior-period error: the nature of the error, the amount of the correction for each line item and each prior period presented, and the amount of correction at the beginning of the earliest prior period presented.
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 documentationInd AS 1: presentation of financial statements, and what a complete set actually requiresFour statements plus notes isn't optional structure — Ind AS 1 defines exactly what counts as a complete set, and a financial statement missing one piece isn't compliant regardless of how good the other three look.
- Audit data & extractsTrial balance mapping for audit softwareMapping a client's idiosyncratic ledgers to a standard chart of accounts is the step that decides whether analytics and disclosures work at all, and the one most firms rush.
- 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.