Retrospective accounting rewrites past financial statements to reflect a new policy, whereas prospective accounting leaves history untouched and applies the change only to future periods.
How retrospective application works
When a company adopts a new accounting policy, US GAAP (ASC 250) and IFRS (IAS 8) generally require it to restate the earliest presented period. The opening balance of retained earnings is adjusted, and every prior period’s income statement, balance sheet, and related tax calculations are recomputed as if the new policy had always been in effect. This ensures comparability across periods.
Typical triggers for retrospective changes
Common reasons include:
- Voluntary shift from one GAAP method to another, such as LIFO to FIFO.
- Adoption of a new standard that changes measurement or recognition, e.g., ASC 606 for revenue.
- Correction of an error that affected previously issued statements.
Consequences of restating the past
Restatements affect not only the income statement but also tax liabilities, deferred tax assets, and any performance‑based compensation tied to prior results. Investors often view restatements as a red flag, so companies use this approach only when it provides more reliable information.
How prospective application works
Prospective treatment leaves all historical figures unchanged. The new policy or estimate is applied only to transactions occurring on or after the effective date, and any current‑period effects are recognized in the period of change. This method is the default for changes in accounting estimates.
When prospective treatment is appropriate
Examples include:
- Revising the useful life of a fixed asset, which changes depreciation expense going forward.
- Updating the allowance for doubtful accounts based on new credit information.
- Adjusting warranty liability estimates as experience data improve.
Impracticability exception
If reconstructing historical data is impossible or excessively costly, both US GAAP and IFRS permit a prospective approach even for a policy change. The company must document why the data are unavailable and apply the new method from the earliest date feasible.
Policy change vs. estimate change
A policy change alters the accounting framework itself (e.g., switching inventory valuation methods). An estimate change refines a judgment within an existing framework (e.g., revising depreciation life). The former typically triggers retrospective treatment; the latter is handled prospectively.
Common pitfalls
Practitioners often confuse the two categories, leading to inappropriate restatements or missed disclosures. Ensuring the correct classification avoids audit issues and maintains investor confidence.