[Concept 024] HKAS 8 / IAS 8 Prior Period Errors in Plain English: Retrospective Restatement, Impracticability and How to Tell an Error from an Estimate Change

[Concept 024] HKAS 8 / IAS 8 Prior Period Errors in Plain English: Retrospective Restatement, Impracticability and How to Tell an Error from an Estimate Change

Note: This article provides a focused explanation and extended discussion on a specific standard. If you’d like to see the full list of articles and short summaries for this standard, please visit the “Series Overview” page.

Since 2025, most standard‑related articles on this site have been available in both Chinese and English versions. If you’d like to read the Chinese explanation, please visit the 「系列總覽」 page and look for the corresponding article.

Plain‑English explainer of HKAS 8 / IAS 8 for students, junior accountants and non‑specialists who find official standards too dense to read.


This article is based on Hong Kong Accounting Standards (HKAS / HKFRS), which are fully aligned with IAS / IFRS except for minor local tweaks, so the same principles generally apply under IAS / IFRS unless noted otherwise. The goal is to unpack HKAS 8 Accounting Policies, Changes in Accounting Estimates and Errors (equivalent to IAS 8) using plain English and practical, real‑life examples instead of technical jargon. It is written for students, junior accountants, audit juniors and finance professionals who want to understand not just “what the standard says” but how to actually read and prepare financial statements in line with it.

When you see “the company” or “the entity” below, you can think of any entity that prepares general purpose financial statements under HKFRS / IFRS.


Why Prior Period Errors Are a High-Stakes Topic

Anyone who has worked through a year-end close or an audit will recognise moments like these: while reviewing inventory records, you discover that a batch of goods received two years ago was never recorded; a fresh look at a depreciation schedule reveals that the wrong useful life has been applied throughout; or it emerges that revenue was recognised too early across multiple prior periods.

When something like this surfaces, the immediate questions tend to be the same: does this qualify as a prior period error? Can the adjustment simply be posted to this year’s profit or loss? Or must prior period comparatives be restated? And if the original records are incomplete, can the company claim that full restatement is not practicable?

HKAS 8 provides a structured path through all of these questions — from identifying whether something is actually an error, to determining how far back restatement must go, to understanding the limits of the impracticability exception, and finally to getting the disclosures right. Working through this path systematically, rather than taking the path of least resistance, is what separates solid technical accounting from guesswork.


What You Should Be Able To Do After Reading?

By the end, you should be able to:

  • Explain what a prior period error is under HKAS 8 / IAS 8, and recognise the most common types in practice.
  • Understand why retrospective restatement is required for material errors — and why absorbing the cumulative impact into the current year’s profit or loss is not acceptable.
  • Apply the impracticability exception correctly: know what “impracticable” genuinely means, and what to do when full retrospective restatement is not feasible.
  • Know what the notes need to disclose when a prior period error is corrected, including the impact on individual line items, earnings per share and opening equity.
  • Distinguish prior period errors from estimate changes and policy changes — a classification that drives the entire accounting treatment and is frequently tested in professional exams.

1. What Is a “Prior Period Error”? Definition and Common Types

HKAS 8 defines prior period errors as omissions or misstatements in one or more prior periods’ financial statements, arising from the failure to use — or the incorrect use of — information that was available and could reasonably have been obtained at the time.

Two conditions must both be met:

  1. The information needed to do it correctly existed at the time; and
  2. Had that information been properly used, the error would not have occurred.

This is an important boundary. A prior period error is not simply a number that turns out to be different from what was reported — it is a case where the company had what it needed to get it right, and did not.

The most common types include:

  • Mathematical mistakes — arithmetic errors, incorrect formula references, or data entry problems.
  • Misapplication of an accounting policy — for example, applying fair value when the cost model was required, or the reverse.
  • Omissions — failing to record a liability, a batch of inventory, or an impairment loss that should have been recognised.
  • Misunderstanding of facts — for example, misreading contract terms in a way that led to revenue being recognised in the wrong period.
  • Fraud — deliberate concealment of liabilities, fabrication of revenue, or systematic understatement of costs.

Materiality still applies

Not every error requires retrospective restatement. HKAS 8 is clear that materiality applies to error assessments just as it does elsewhere. If an error is immaterial — meaning that correcting it would not affect users’ economic decisions — retrospective restatement is not necessarily required.

Once an error crosses the materiality threshold, however, it cannot simply be absorbed into the current year. The full retrospective restatement process must be followed.

A very common mistake among those new to this area is to instinctively reach for an “adjust it this year” solution whenever a number looks wrong, without first asking whether the issue is actually a material prior period error. The equally common opposite mistake is to label a revised estimate as an error — when it was actually a reasonable judgement that has since been updated. Before deciding on any accounting treatment, the right first question is always: what is the nature of this issue?


2. The Correct Accounting Treatment — Retrospective Restatement

When a material prior period error is confirmed, HKAS 8 requires it to be corrected by retrospective restatement — not by recognising the cumulative effect in the current period’s profit or loss.

Restating prior period comparatives

In the first financial statements authorised for issue after the error is discovered, the company must:

  • Correct the comparative amounts for each prior period presented, as if the error had never occurred; and
  • Where the error originated before the earliest period presented in the financial statements, adjust the opening balances of assets, liabilities and equity for that earliest period accordingly.

A worked example. Suppose Company A is preparing its 20X4 financial statements and discovers that a significant liability has been omitted since 20X2. The 20X3 financial statements have already been published to the public.

In the 20X4 financial statements, the company would generally need to:

  • Restate the 20X3 comparative figures — adjusting the liability, any associated expense, the tax effect, and closing equity — as if the liability had been correctly recorded all along; and
  • If 20X2 is also presented as a comparative period, restate those figures as well; or if 20X2 is the earliest period presented, adjust the opening equity of that period.

Why the error cannot simply go through the current year’s profit or loss

HKAS 8 is explicit: the cumulative correction of a material prior period error must not be recognised in the current period’s income statement.

The reason is straightforward. If several years’ worth of errors are compressed into a single line in the current year, users of the financial statements cannot separate genuine current-period trading performance from the correction of past mistakes. Current-year results become distorted, and the trend analysis that investors and other stakeholders rely on becomes unreliable.

By restating prior periods instead, each year’s reported results reflect the actual performance of that year — which is precisely what financial statements are supposed to convey.

In practice, you may encounter management who prefer to run the correction through “other income / expense” or describe it as a “prior year adjustment” within the current year’s income statement. Under HKAS 8, this approach is not acceptable for material errors, except where the impracticability exception genuinely applies.


3. The Impracticability Exception — How Far Back Must You Actually Go?

In principle, error corrections should be traced all the way back to the period in which the error first occurred. In practice, HKAS 8 acknowledges that for some errors — particularly those affecting periods far in the past — full retrospective restatement may genuinely not be feasible.

What “impracticable” actually means

This is not a low bar, and it is not satisfied simply because restatement would be inconvenient or would require substantial effort. The impracticability exception applies only where the company has made every reasonable attempt to reconstruct the prior period figures and still cannot do so reliably.

Circumstances that may constitute genuine impracticability include:

  • The company cannot reasonably determine what the financial effect of the error was in each individual prior period;
  • Reconstructing the impact would require making assumptions about management’s intentions in those earlier periods, and those intentions can no longer be objectively verified; or
  • The necessary estimates would require distinguishing between information that was available at the time and information that only became available later — a distinction that is impossible to make reliably after the fact.

Only after exhausting every reasonable option can a company legitimately conclude that retrospective restatement is impracticable.

What to do when full restatement is not feasible

Where retrospective restatement all the way back to the original error period is genuinely impracticable, HKAS 8 allows the company to identify the earliest practicable date — the earliest period from which the impact of the error can be reliably reconstructed — and restate from that point forward. The cumulative effect prior to that date is not separately allocated to individual years.

This is not a complete abandonment of retrospective treatment. It represents the most thorough restatement the circumstances permit, accompanied by transparent disclosure of why the correction does not go further back.

A practical scenario. Suppose you are helping a long-established company that has been misclassifying a category of assets for more than a decade, and the original records from those early years simply no longer exist. The key question is: from which point can the figures be reliably reconstructed? If records from, say, five years ago are intact and reliable, that year-end becomes the earliest practicable date. Restatement proceeds from that opening balance, and the notes explain clearly why the correction does not extend further back and what effect this has.


4. Disclosure — What the Notes Must Say

The quality of disclosure around a prior period error correction is critical. Users of financial statements need enough information to understand what went wrong, how significant it was, and how the comparatives have been adjusted. HKAS 8 requires disclosure of:

  1. The nature of the error — what happened and why;
  2. The correction amount for each prior period presented, broken down by affected line item;
  3. The effect on earnings per share (where applicable);
  4. The adjustment to opening equity for the earliest period presented; and
  5. If retrospective restatement was not fully practicable, the reasons why and an explanation of how the correction has been applied instead.

Continuing the earlier example. If Company A discovers in 20X4 that inventory was understated by $5 million at the end of 20X2 — because a batch of received goods was never recorded, and those goods were sold during 20X3 — the notes in the 20X4 financial statements should:

  • Explain that the error relates to goods received in 20X2 that were not entered into the inventory records at the time;
  • Present the restated 20X3 comparative figures, showing the effect on opening inventory, cost of sales, the tax charge, and closing retained earnings; and
  • Disclose the impact on earnings per share for the restated period.

Through this level of disclosure, users can clearly see how much of any movement in reported results reflects genuine performance and how much reflects the correction of a historical mistake.


5. Why the Old “Allowed Alternative” and “Fundamental Errors” Were Removed

Earlier versions of both IAS 8 and HKAS 8 contained a concept called “fundamental errors” and permitted an “allowed alternative” treatment: in certain circumstances, the effect of correcting a significant error could be recognised directly in the current period’s profit or loss, rather than through retrospective restatement of prior periods.

In practice, this created several problems:

  • The line between a “fundamental” error and an ordinary error was poorly defined and inconsistently applied across entities;
  • Allowing errors to flow through the current period’s income statement undermined the reliability and comparability of reported results over time; and
  • Management had scope to use the alternative treatment selectively in ways that made current-year results look better.

When the standard was revised, both the “fundamental errors” category and the allowed alternative treatment were removed. The current version of HKAS 8 takes a simpler, more principled position: a material error requires retrospective restatement, unless genuine impracticability applies. There is no tiered classification of errors, and no option to take the cumulative correction through current-year profit or loss.

The result is cleaner trend analysis, stronger comparability across entities, and significantly less room for management to exercise discretion in ways that obscure the true financial picture.


6. Common Pitfall: Confusing Errors with Estimate Changes or Policy Changes

In practice, the most frequent problem is not failing to spot an error — it is misclassifying an error as either an estimate change or a policy change, and thereby sidestepping the retrospective restatement requirement altogether. Three diagnostic questions help cut through the ambiguity.

“Was it wrong before, or has the view simply changed?”

An error means the company had sufficient information to do it correctly at the time, and failed to do so. An estimate change means the company made a reasonable judgement based on available information, and that judgement is being updated as new information emerges.

Two contrasting examples make this concrete:

  • Last year, the company estimated a warranty provision based on reasonable historical data. This year, actual claims are higher than expected. → Estimate change. The original estimate was reasonable given what was known at the time.
  • Last year, the company already had clear evidence of significant product defects, but made no warranty provision at all. → Error. The information was available; the company failed to act on it.

Error vs. policy change

A policy change involves moving from one acceptable accounting treatment to another — either because a new standard requires it, or because the new approach provides more relevant and reliable information. The previous policy was permissible; it was not wrong. An error means the original treatment was not compliant with the applicable standard or basic accounting principles in the first place — regardless of whether any new standard has since been issued.

A practical illustration. Suppose a company has been consistently recognising the full gross transaction amount as revenue in arrangements where, under HKFRS 15 Revenue from Contracts with Customers (equivalent to IFRS 15), the company was clearly acting as an agent — meaning only the net commission should have been recognised. If the information needed to make the principal-versus-agent assessment was available at the time, and the company simply applied the standard incorrectly, this is a prior period error — not a policy change discovered after the fact.

By contrast, if the company had been using one permissible method of allocating the transaction price across performance obligations and — with proper justification — decides to adopt a different permissible method that better reflects the pattern of performance, that is a policy change, not an error correction.

The three-way diagnostic

Whenever you need to classify a change or correction:

  • Did it arise because something was done incorrectly before, using information that was available at the time? → Likely an error. Retrospective restatement required (if material and practicable).
  • Did it arise because an accounting principle is being changed to one that is more relevant or reliable? → Likely a policy change. Retrospective application generally required.
  • Did it arise because an assumption or input is being updated based on new information or developments? → Likely an estimate change. Prospective application only.

Writing these three questions into a working paper checklist or review note is one of the most practical things you can do to make sure classification is addressed explicitly — before anyone starts drafting journal entries.


7. Closing Thoughts: When You Find a Mistake, the First Step Is Classification, Not Concealment

The rules around prior period errors and retrospective restatement can feel daunting, especially when the practical implications are significant — restating published comparatives, explaining the issue to auditors and management, updating disclosures. But the underlying principle is straightforward: financial statements should reflect each period’s results as accurately as possible, and errors that distort that picture need to be put back where they belong.

The next time you encounter something that looks like a historical mistake, work through these four questions before doing anything else:

  1. Is this genuinely an error, or is it a legitimate estimate update or a policy change?
  2. If it is an error, is it material enough to require retrospective restatement?
  3. Can the correction be traced back to the period when the error originated? If not, what is the earliest practicable date?
  4. What disclosures do users of the financial statements need in order to understand what happened and how it has been corrected?

Once you have clear answers to those four questions, the accounting path forward becomes much easier to defend — to auditors, to management, and to anyone else who asks.


Key Takeaways for Students and Junior Accountants

  • Classify before you journal. Before deciding how to book anything, first determine whether the issue is an error, an estimate change, or a policy change. Each has a completely different treatment. Getting the classification wrong means everything that follows will be wrong too.
  • Material errors require retrospective restatement — not a current-year catch-all adjustment. If you see a large “prior year adjustment” sitting in the current year’s income statement without clear justification, treat it as a red flag.
  • “Impracticable” is a high bar. It is not satisfied by inconvenience or incomplete records alone. If a company claims impracticability, there must be documented evidence that every reasonable attempt to reconstruct the figures was made and failed.
  • Use the three-way diagnostic every time: Was it done incorrectly before? → Error (retrospective restatement). Was a principle changed? → Policy change (retrospective application). Was an assumption updated? → Estimate change (prospective only). Write this analysis into your working papers explicitly.
  • For exam technique: Identify the type of issue, state the required treatment, show which periods are affected, and briefly address disclosure. Watch out for scenarios that blur the boundary between errors and estimate changes — that is where marks are won or lost.

If this article was helpful, you’re very welcome to subscribe to my Substack for free:

  • All full articles are published on my website first.
  • Whenever I finish a mini‑series on a standard, I’ll send one email that pulls the whole series together and links everything in one place, so you can revise without hunting around.
  • I occasionally share small, practical tips from real‑life accounting work.
  • When I release new PDF notes, in‑depth case studies or paid content in the future, email subscribers will be the first to know.

If you’d like to ask me questions or chat about your learning, you can follow me on Threads / IG and send me a DM — I’ll reply as far as I can.
And if you feel these resources have helped you, you can also buy me a coffee to support me in writing more.

[Concept 024] HKAS 8 / IAS 8 Prior Period Errors in Plain English: Retrospective Restatement, Impracticability and How to Tell an Error from an Estimate Change

罔相心室: https://chinese.iamdelusionman.com/
Zero-to-Acct Substack: https://zerotoacct.substack.com/
Thread: https://www.threads.com/@yickki_mong
IG: https://www.instagram.com/yickki_mong/

Comments

No comments yet. Why don’t you start the discussion?

    Leave a Reply