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 10 / IAS 10 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 10 Events after the Reporting Period (equivalent to IAS 10) 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.
When a “Later” Event Changes an Earlier Year
Imagine this very typical situation at work. Your company has just finished drafting the financial statements for the year ended 31 March 2026, and the audit is almost done. Then in mid‑May you receive news that your largest trade receivable customer has gone bankrupt. You immediately wonder: “Do we need to reflect this bad debt in the 2026 financial statements?” This judgment suddenly becomes critical because it affects profit, asset fairness and possibly the audit opinion.
This is exactly the kind of question that HKAS 10 Events after the Reporting Period (equivalent to IAS 10) is designed to answer. Which events that happen after the reporting period should change the numbers in the financial statements, and which should not? If accountants cannot make this distinction, they may wrongly adjust the figures or forget required disclosures, leading to misleading financial statements and even compliance risk.
What You Should Be Able To Do After Reading?
By the end, you should be able to:
- Build a clear mental framework for HKAS 10: understand its objective, scope and key judgment mindset.
- Understand the time line of events after the reporting period and the critical dates involved.
- Distinguish between the two big categories of events: adjusting events and non‑adjusting events.
- See how HKAS 10 connects with other standards such as HKAS 1, HKAS 37 and HKFRS 3.
- Make quick, structured decisions about how to handle post‑year‑end events in practice, and avoid common mistakes.
1.What is HKAS 10 really trying to do?
The core purpose of HKAS 10 is to give a consistent framework for deciding whether events that occur between the end of the reporting period and the date the financial statements are authorized for issue must be reflected in that period’s financial statements. The standard applies to all entities that prepare financial statements under Hong Kong Financial Reporting Standards, whether listed, private or not‑for‑profit.
Another key idea is the link to the date when the financial statements are authorized for issue. Completing the numbers does not mean the financial statements are “official” yet. Only when management or the board approves them for issue do they become the responsibility of the entity to present externally. HKAS 10 is therefore focused on events between the reporting period end and this authorization date.
Here is a simple, common example.
- The entity’s financial year ends on 31 March 2026.
- Management approves and authorizes the financial statements for issue on 15 May 2026.
All events that occur from 1 April 2026 up to 15 May 2026 fall within the scope of “events after the reporting period” for HKAS 10 purposes. By defining this window clearly, the standard gives accountants a stable “observation period” to decide whether a post‑year‑end event should affect the financial statements.
2.Get the time line and key dates clear
Understanding the time line is the foundation for mastering HKAS 10. The end of the reporting period is usually the statement of financial position date, for example 31 March. The date when the financial statements are authorized for issue depends on the entity’s governance structure:
- If the board of directors has the final authority to approve the financial statements for issue, the authorization date is the board approval date.
- If shareholders’ approval is also required (e.g. in some public sector or fund structures), the authorization date is still the date on which the board approves the financial statements for issue to the shareholders, not the date when shareholders formally adopt them.
A common misunderstanding is that the date when shareholders “receive” or “adopt” the financial statements at the annual general meeting is the authorization date. HKAS 10 makes it clear that this is not the case. As soon as the body that has the power to approve the financial statements for issue has done so, that is the authorization date.
You can picture the time line like this (using the earlier example):
Reporting period end (31/3/2026) ↓ audit and review period ↓ Management / board approves financial statements for issue (15/5/2026) ↓ Shareholders’ meeting adoption (not a key date for HKAS 10)
Everything that happens between 1 April and 15 May 2026 is what HKAS 10 is interested in.
3. Formal definition of “events after the reporting period”
HKAS 10 defines events after the reporting period as:
Events, both favourable and unfavourable, that occur between the end of the reporting period and the date when the financial statements are authorized for issue.
There are several important points wrapped up in this definition:
- Clear time element – the event must occur between the reporting period end and the authorization date.
- Neutral view – both “good news” and “bad news” events fall within the scope.
- Not just any news – not every piece of information about the entity counts. Matters that relate only to long‑term plans or market expectations, and not to an event that actually happened in this window, are not “events after the reporting period”.
For example:
- In April, the entity receives a court judgment confirming a legal obligation that already existed before 31 March.
- In May, the entity sells a major asset in a transaction that did not exist at 31 March.
These two events are both within the time window, but they are very different in nature. HKAS 10 helps us decide which type requires an adjustment of the financial statement amounts and which type only needs disclosure.
4. The heart of HKAS 10 – adjusting vs non‑adjusting events
This is the core of HKAS / IAS 10, and also where many people get confused in exams and in practice.
Adjusting events: when later evidence confirms an existing condition
Adjusting events are those that provide additional evidence of conditions that already existed at the end of the reporting period. In other words, the underlying situation was present at year‑end, but the outcome or the final information only became known afterwards. Because they relate to the existing year‑end condition, these events generally lead to adjustments to the amounts recognized in the financial statements.
A classic example is:
- After year‑end, a major debtor is declared bankrupt.
- The bankruptcy shows that at the reporting date, the trade receivable was already impaired and not recoverable, even though this was not certain at that time.
In this case, the entity should recognize an impairment loss (or increase the loss allowance) in the financial statements for the reporting period, because the event confirms the condition that existed at year‑end.
Non‑adjusting events: when something genuinely new happens after year‑end
Non‑adjusting events represent conditions that arose after the end of the reporting period. They were not present at year‑end, so they do not affect the entity’s financial position at that date. Therefore, the amounts in the financial statements are not adjusted for these events. However, if the effect is material, the entity must still disclose the nature of the event and an estimate of its financial effect, or state that such an estimate cannot be made.
Example:
- After year‑end, a fire destroys a factory, and the cause is not something that existed at the reporting date.
- The destruction of the factory does not change the fact that at year‑end, the factory was in use and intact.
Here, the entity should not adjust the carrying amount of the factory in the reporting period’s financial statements. But if the impact is significant, the event and its expected financial effect should be disclosed in the notes.
A simple question to test yourself
In practice, the hardest part is deciding whether “the condition already existed at the reporting date”. For beginners, a simple self‑check question helps:
“Was the root cause of this event already in place before the year‑end date?”
- If your honest answer is “yes”, the event is likely to be an adjusting event.
- If the answer is “no”, it is probably a non‑adjusting event.
You can use this simple question whenever you see a new post‑year‑end event during audit or month‑end reviews.
5. Where HKAS 10 fits into the bigger financial reporting picture
HKAS 10 does not operate in isolation. It interacts with several other key standards:
- HKAS 1 Presentation of Financial Statements (equivalent to IAS 1) – requires appropriate disclosure of events after the reporting period, particularly material non‑adjusting events that could influence users’ decisions.
- HKAS 37 Provisions, Contingent Liabilities and Contingent Assets (equivalent to IAS 37) – provides further guidance for post‑year‑end events involving legal disputes, guarantees and other contingent obligations, including when to recognize provisions and when to disclose contingent liabilities.
- HKFRS 3 Business Combinations (equivalent to IFRS 3) – if the entity obtains control of another entity after the reporting period, that business combination is not an adjusting event. The recognition and measurement follow HKFRS / IFRS 3, but disclosure about such post‑year‑end acquisitions is required.
Once you understand HKAS 10, you have essentially built the “central judgment hub” for the period between year‑end and authorization of the financial statements. Every time you see new information during this window—whether in audit working papers, management reporting or board packs—the first mental steps should be:
- Is this an event after the reporting period?
- If yes, is it adjusting or non‑adjusting?
- Do I need to adjust the numbers, disclose the event, or both?
6. Final thoughts: HKAS 10 as your “time boundary” guide
Let’s go back to the opening question: your customer goes bankrupt in May—do you adjust the March financial statements?
Under HKAS / IAS 10, the answer is yes. The customer’s financial difficulties existed at year‑end; the bankruptcy is simply the later confirmation of that condition. The receivable should be written down (or further written down) in the reporting period.
On the other hand, if in May the entity signs a major new contract that will bring significant future revenue, this is a non‑adjusting event. The new contract did not exist at the reporting date, so you do not adjust the reported figures for this new business. You may, however, need to disclose it if it is significant to users’ understanding.
Mastering HKAS 10 is really about mastering a “time boundary” mindset. Financial statements are not a mix of past and future. They present the position at the reporting date, enriched by later evidence that sheds light on that date—but not by events that belong purely to the future. This way of thinking is essential whenever you handle information that arrives after year‑end, respond to audit queries, or prepare reports for directors and investors.
If you want to go further, the natural next step is to explore detailed case studies on classifying post‑year‑end events, and to see how disclosure and audit procedures are designed around this framework.
Key Takeaways For Students And Junior Accountants
- When you see any “news” after year‑end (lawsuits, customer failures, big contracts, accidents), immediately place it on the HKAS / IAS 10 time line and ask whether it is inside the reporting‑date‑to‑authorization window.
- For each event in that window, ask the root‑cause question: “Did this condition already exist at the reporting date?”—use this to decide adjusting vs non‑adjusting before you even open the standard.
- In exams and in real working papers, clearly document: the dates involved, your classification (adjusting / non‑adjusting) and the impact on recognition, measurement and disclosure.
- Watch out for common traps: treating shareholder‑approval dates as the authorization date, adjusting for new contracts or new business that did not exist at year‑end, or forgetting to disclose major non‑adjusting events.
- When reading contracts, drafting journal entries or preparing audit working papers, always anchor your analysis to the reporting date first, then use post‑year‑end evidence only to confirm or clarify that date—not to mix future events into past financial statements.
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/
