When accounting standards change, companies must decide whether to adjust past records or start fresh. Retrospective application means restating historical financial statements as if the new rule had always existed. Prospective application applies the new rule only to future transactions, leaving prior periods untouched.
Core definitions and mechanics
Retrospective application is effectively financial time travel. The company recalculates prior period results, adjusting the opening balance of retained earnings for the earliest period presented. This ensures that comparative figures across years are calculated using the same method, preserving trend line integrity for investors.
Prospective application is a clean break. Historical figures remain exactly as they were reported. The new policy takes effect from the date of change onward. This method is often used when reconstructing the past is too costly or impossible, or when the change involves an estimate rather than a policy.
When to use which method
Regulatory frameworks like IAS 8 (International Financial Reporting Standards) and ASC 250 (US GAAP) provide strict rules. Companies cannot simply choose the method that makes their current earnings look better.
- Change in Accounting Policy: Generally requires retrospective application. You must restate prior periods unless it is impracticable to determine the period-specific effects.
- Change in Accounting Estimate: Always requires prospective application. Since estimates involve judgment (like asset useful life), you apply the new estimate to the current and future periods only. You do not go back and adjust past depreciation.
Impact on financial statements
The choice significantly affects how a company’s performance appears to analysts. Retrospective application can cause a sudden shift in historical data. A company that looked stable might appear volatile if past profits are restated downward. However, it maintains comparability, which is crucial for calculating metrics like compound annual growth rate.
Prospective application protects the historical record but introduces a structural break. Profit margins or revenue figures might jump or drop in the year of the change simply because the accounting rule shifted, not because operations improved or worsened. Analysts must adjust for this discontinuity when comparing year-over-year performance.
The impracticability exception
Even when retrospective application is the default, there is an escape valve. If determining the period-specific effects is impracticable, the company may apply the change prospectively from the earliest date practicable. This might happen if historical data was lost in a disaster or if the necessary assumptions cannot be verified. However, claiming impracticability is not a way to avoid work; the company must demonstrate that it made reasonable efforts to reconstruct the data and failed.
Practical examples
Consider a shift in inventory valuation from FIFO to weighted-average cost. Without retrospective adjustment, comparing last year’s cost of goods sold to this year’s would be misleading because they were calculated differently. Restating the prior year ensures the trend line is accurate.
In contrast, if a company re-estimates that a machine will last five more years instead of ten, it does not change the depreciation recorded in previous years. It simply spreads the remaining cost over the new, shorter timeline. This distinction prevents companies from rewriting history to smooth out earnings fluctuations caused by estimation errors.