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 Does HKAS 8 Even Exist? Setting the Scene
If you’ve spent any time reviewing financial statements, you’ve probably come across situations like this: last year the company recognised revenue one way, but this year the method has quietly changed. Or the depreciation period for a major asset has been shortened — and the notes don’t clearly explain whether this was a policy change or an updated estimate.
These seemingly small differences can significantly affect how readers understand a company’s financial performance and the quality of management’s judgements.
HKAS 8 Accounting Policies, Changes in Accounting Estimates and Errors (equivalent to IAS 8 under IFRS) exists precisely to address this kind of inconsistency. It sets out clear rules for how companies should select and apply accounting policies, handle changes to those policies or estimates, and correct past mistakes — so that financial statements remain comparable and reliable across periods.
What You Should Be Able To Do After Reading?
By the end, you should be able to:
- Understand the core purpose of HKAS 8 / IAS 8 and where it sits in the broader framework of accounting standards.
- Clearly distinguish between accounting policies, accounting estimates, and prior period errors — and know how each is treated.
- Recognise which situations fall under HKAS 8 and which are governed by other standards.
- Apply the underlying logic of all three concepts using practical, workplace-style examples.
- Have a working awareness of how HKAS 8 has evolved over time, and why certain debates still exist.
1. What Is HKAS 8 Actually About?
HKAS 8 Accounting Policies, Changes in Accounting Estimates and Errors (equivalent to IAS 8) governs three areas:
- How to select and apply appropriate accounting policies;
- How to account for changes in accounting policies or accounting estimates;
- How to correct prior period errors.
All three work toward the same goal: ensuring that financial statements are consistent and comparable over time. Without HKAS 8, management could quietly shift accounting methods to make results look better — and nobody would have a clear basis to challenge it.
Within the broader standards framework, think of it this way:
- The Conceptual Framework sets out the underlying principles of financial reporting — it’s the philosophy.
- HKAS 1 (Presentation of Financial Statements) governs the structure and format of financial statements.
- HKAS 8 controls what happens behind the numbers — how figures are arrived at, and how changes to those methods must be disclosed and accounted for.
In short, HKAS 8 is what keeps the numbers trustworthy from one year to the next.
2. When Does HKAS 8 Apply?
HKAS 8 applies in four situations:
- Selecting and applying accounting policies
- Changes in accounting policies
- Changes in accounting estimates
- Correction of prior period errors
Simple enough on the surface — but in practice, the trickiest part is knowing where HKAS 8 ends and where another standard begins.
For example:
- Tax accounting falls under HKAS 12 (Income Taxes / IAS 12).
- Lease accounting follows HKFRS 16 (Leases / IFRS 16).
However, when those specific standards don’t address how to choose between alternative treatments, HKAS 8 steps in as the fallback — guiding the entity back to first principles.
Think of it as a division of responsibilities, not a replacement of other standards. In day-to-day work, if you spot a change in depreciation method or a shift in when revenue is recognised, the first question to ask isn’t “is this right or wrong?” — it’s: “Which category under HKAS 8 does this change fall into?” That answer determines everything that follows.
3. Key Definitions — Clear Them Up Once and For All
Before diving deeper, it helps to lock in these core terms:
- Accounting Policies: The specific principles, bases, conventions and practices a company applies when preparing financial statements. Think of these as the rules of the game — for example, how inventory is valued, how revenue is recognised, or which depreciation model is used for property, plant and equipment.
- Accounting Estimates: Judgements made under uncertainty, using the best available information at the time. Examples include the expected useful life of an asset, a provision for bad debts, or a fair value measurement. Estimates are not errors — they are inherently imprecise and will be refined as new information becomes available.
- Prior Period Errors: Omissions or misstatements in previously published financial statements, resulting from mathematical mistakes, misapplication of policies, or overlooked facts. If confirmed as errors, they require retrospective restatement.
- Retrospective Application: When an accounting policy changes, the entity applies the new policy as if it had always been in place — restating prior period figures accordingly to maintain comparability.
- Retrospective Restatement: Used specifically for error corrections — prior period statements are restated to reflect what they should have shown in the first place.
- Prospective Application: Used for changes in accounting estimates — only current and future periods are affected. No prior period adjustments are made.
- Impracticable: Where it is genuinely not feasible to obtain the information needed to apply a retrospective treatment — for example, because historical data is simply unavailable. An entity may be exempt from retrospective application in such cases, but must disclose the reason.
One simple way to keep these straight:
Policy = the principle. Estimate = the number. Error = a mistake.
4. The Big Three — Policies vs Estimates vs Errors
These three concepts look similar on the surface, but they work very differently in practice:
When a company changes an accounting policy — meaning it adopts a different principle or basis for recording a type of transaction — the change must be applied retrospectively. In other words, the company restates prior period figures as if the new policy had always been in place. This is the most demanding treatment of the three, and it exists for good reason: it ensures that readers can compare this year’s numbers with last year’s on a like-for-like basis.
A change in accounting estimate works differently. Because estimates are inherently uncertain and should be updated as new information comes in, the standard does not require any adjustment to prior periods. Instead, the revised estimate is applied prospectively — only the current and future periods are affected. This reflects the practical reality that changing an estimate is not an admission that something was wrong before; it simply means the company now has better information to work with.
Prior period errors are treated the most strictly of all. If a company discovers that a previous period’s financial statements contained a mistake — whether due to a calculation error, a misapplication of policy, or an overlooked fact — it must correct that error through retrospective restatement. The prior period figures are restated to show what they should have looked like all along. Unlike an estimate revision, an error correction carries the implication that something was genuinely wrong, and the financial statements must be corrected accordingly.
A workplace example to make this concrete:
Suppose a company previously depreciated a piece of equipment over 10 years. This year, based on updated usage data, it revises that to 6 years.
- This is a change in accounting estimate — the company hasn’t changed its depreciation method; it has simply updated its assumption based on new information. → Apply prospectively: adjust the current and future periods only.
But what if last year the company had mistakenly classified that equipment as inventory instead of a fixed asset?
- That is a prior period error — an incorrect classification. → Retrospective restatement required.
And if the company decides to switch from the cost model to the revaluation model for its entire class of property, plant and equipment?
- That is a change in accounting policy. → Retrospective application required.
The quick test:
Changed the principle? → Policy change. Updated an assumption? → Estimate change. Got it wrong before? → Error.
5. How HKAS 8 Has Evolved — And Why It Still Sparks Debate
HKAS 8 has been revised over the years as the profession has pushed for greater clarity and consistency. A few notable developments:
- Removal of the “fundamental errors” category: Earlier versions of the standard created a separate tier for particularly serious errors. This distinction was removed — now, any material error, regardless of its nature, is subject to the same retrospective restatement requirements. Less ambiguity, more consistency.
- Elimination of the “benchmark” vs “allowed alternative” structure: Previously, some entities could choose to recognise the effect of an accounting policy change directly in profit or loss in the current period. That option is gone. Retrospective application is now the required treatment, strengthening comparability across entities and over time.
- Refined definition of accounting estimates and measurement uncertainty: The standard now places greater emphasis on the fact that estimates are not one-off calculations — they are an ongoing, judgement-based process that should be updated as new information becomes available.
One persistent debate: is retrospective application too demanding, particularly for smaller entities that may not have easy access to historical data? HKAS 8 takes the view that — unless retrospective treatment is genuinely impracticable — it must be applied. The rationale is that this requirement is precisely what maintains the credibility and continuity of financial statements over time.
6. Closing Thoughts: HKAS 8 Is About Trust in the Numbers
Think back to that scenario at the start — a change in revenue recognition buried in the notes, with no clear explanation of whether it was a policy change or an estimate revision.
After reading this, you now know the right questions to ask:
- Is this a change in accounting policy, a revised estimate, or a correction of an error?
- Has the company applied the change retrospectively or prospectively — and is that treatment correct under HKAS 8?
- Is there sufficient disclosure in the notes to understand the basis and impact of the change?
HKAS 8 gives you a principled framework for thinking through these questions systematically. Once you have this mental model, it becomes much easier to explain — to a client, an auditor, or an examiner — why a particular accounting treatment was chosen and what rules govern it.
Key Takeaways for Students and Junior Accountants
- The “big three” test: Every time you see a number change in financial statements, ask which of the three categories it belongs to — policy, estimate, or error. The answer drives everything else: retrospective vs prospective treatment, disclosure requirements, and how prior periods are affected.
- Watch out for the policy vs estimate trap: This is one of the most commonly tested distinctions in professional exams — and one of the most common misclassifications in practice. A change in depreciation method (e.g., straight-line to reducing balance) is a policy change. A change in useful life is an estimate change. These two look similar but are treated completely differently.
- Errors always require retrospective restatement — there is no prospective shortcut for a confirmed prior period error, unless retrospective treatment is genuinely impracticable.
- When reviewing contracts or working papers: If you encounter a note saying “change in accounting policy” or “revision of estimates,” don’t just accept it at face value. Check whether the classification is correct and whether the required treatment has actually been applied.
- In audit or review work: Focus on whether management’s disclosures clearly explain what changed, why it changed, and what the financial impact is. Vague or incomplete disclosures are a red flag.
- For exam preparation: HKAS 8 / IAS 8 is a high-frequency topic. Make sure you can (a) classify a change correctly, (b) state the correct accounting treatment, and (c) describe the disclosure requirements — all in one clean answer.
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.
罔相心室: 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/
