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 19 / IAS 19 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 19 Employee Benefits (equivalent to IAS 19) 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 employee benefits really matter
When people open a listed company’s annual report, they often jump straight to revenue, profit or EBITDA. But once you start working in accounting or audit, you quickly see that “staff costs” are often one of the biggest expenses on the statement of profit or loss.
In Hong Kong, many industries are people‑heavy: financial services, professional firms, tech companies and so on. Staff costs are not just monthly salaries; they include annual leave, sick leave, bonuses, MPF or pension schemes, medical benefits and even long‑service awards that sit in the numbers year after year.
So three practical questions come up again and again:
- How should these employee benefits be split between the statement of financial position and the statement of profit or loss and other comprehensive income?
- When is it just a simple accrual, and when do you suddenly need discounting, actuarial calculations and long‑term allocation of costs?
- Why does the standard insist on splitting benefits into four categories: short‑term, post‑employment, other long‑term and termination benefits?
HKAS 19 Employee Benefits (equivalent to IAS 19) tries to give one unified framework for all these employee‑related benefits, so that the entity does not understate liabilities or “hide” staff obligations, and so users of the financial statements can see the real economic cost of employees. This article helps you build that framework as a foundation before going deeper into post‑employment benefits and the defined contribution / defined benefit distinction.
What You Should Be Able To Do After Reading?
By the end, you should be able to:
- Explain the core objective and basic principles of HKAS 19, and where it sits relative to other standards like HKFRS 2 Share‑based Payment and HKAS 26 Accounting and Reporting by Retirement Benefit Plans.
- Clearly distinguish the four types of employee benefits: short‑term, post‑employment, other long‑term and termination benefits, and understand that the key is expected settlement timing and nature of the benefit, not just the label.
- Identify common examples of short‑term employee benefits (salaries, annual leave, sick leave, short‑term bonuses) and understand the usual accounting treatment, including undiscounted accruals and expense recognition.
- Grasp the basic idea of other long‑term employee benefits and termination benefits: when they arise, when they are recognised, and why they often involve discounting, estimation and more professional judgement.
- Place all of these into the overall structure of HKAS 19, so you know how to progress next into detailed measurement of defined contribution (DC) and defined benefit (DB) post‑employment plans.
1. What HKAS 19 / IAS 19 is really about
Before memorising lists, it helps to answer one simple question: what problem is HKAS 19 trying to solve?
The core idea of HKAS 19 can be summarised in one sentence: when employees provide services, the entity should recognise the related employee benefit liabilities and expenses.
In standard language, the entity needs to:
- Recognise a liability when employees have already rendered service but the related benefits have not yet been paid, because the entity now has an obligation to provide those future benefits.
- Recognise an expense when it consumes the economic benefits arising from employee services, so that staff costs are matched to the period that benefits from the work.
In simple terms, HKAS 19 is about matching and no under‑statement: do not delay recognising staff obligations and do not push employee costs into future periods just to make current profit look nicer.
Scope: what HKAS 19 covers (and what it does not)
HKAS 19 (IAS 19) applies to how employers account for all types of employee benefits. But there are two important “hand‑offs” to other standards:
- Share‑based payments: staff share options, restricted shares, share appreciation rights and similar arrangements go to HKFRS 2 Share‑based Payment / IFRS 2, not HKAS 19.
- Financial statements of the benefit plan itself: if a pension fund or retirement benefit plan prepares its own set of financial statements as an entity, that reporting is governed by HKAS 26 / IAS 26, not HKAS 19.
So, in daily work, whenever you see “employer gives employees cash or non‑cash benefits” and it is not a share‑based payment, you are almost certainly in HKAS 19 / IAS 19 territory.
What counts as “employee benefits”?
HKAS 19 uses a deliberately broad definition of employee benefits: any form of consideration given by an entity in exchange for employee service, whether:
- Cash (wages, salaries, bonuses).
- Non‑cash (medical benefits, company cars, staff housing, subsidies).
- Provided during employment or after employment.
- Arising from legal obligations, contractual terms, company policies, established practice or collective agreements.
This broad definition lets the standard group many different schemes under one umbrella, and then classify them by timing and nature into four main categories.
2. The four big buckets of employee benefits
To really understand HKAS 19 / IAS 19, you must be comfortable with how the standard splits employee benefits into four buckets:
- Short‑term employee benefits.
- Post‑employment benefits.
- Other long‑term employee benefits.
- Termination benefits.
Lens 1 – When are benefits expected to be settled?
The first lens is expected timing of settlement:
- Short‑term employee benefits: expected to be settled in full within 12 months after the end of the annual reporting period in which employees render the related service, and they are not termination benefits. Typical examples: wages, salaries, annual leave, sick leave (when used within a short horizon), short‑term bonuses and non‑monetary benefits provided to current staff.
- Post‑employment benefits: benefits payable after the completion of employment, other than termination benefits, such as pensions, lump‑sum retirement payments, post‑retirement medical or insurance coverage.
- Other long‑term employee benefits: benefits that are not short‑term, not post‑employment and not termination benefits, and are usually settled over a longer period while employees are still in service. Common examples: long‑service awards, long‑service leave, long‑term disability benefits, long‑term profit‑sharing or bonus schemes.
- Termination benefits: a separate category, driven by termination of employment itself rather than how long the benefit runs.
For “short‑term”, the standard focuses on whether the obligation is expected to be fully settled within 12 months after the reporting period, not whether the benefit sounds short‑term from its name. A benefit called “year‑end bonus” can still be long‑term if it is not expected to be fully settled within that 12‑month window.
Lens 2 – Nature of the benefit and what triggers the obligation
The second lens looks at what creates the obligation:
- Post‑employment benefits: obligations typically arise from employment contracts, retirement plan promises or legislation, and employees only enjoy them after completing the required service period or after retirement.
- Other long‑term employee benefits: usually linked to long service or continued employment, such as “10‑year service award” or long‑term sick leave entitlements.
- Termination benefits: the obligation is triggered by the entity’s decision to terminate employment or to offer benefits in exchange for employees accepting termination (for example, restructuring, plant closure or a voluntary redundancy scheme).
In practice, confusion often comes from payments that look similar on the surface but differ in nature. A single lump‑sum paid at year‑end might be a short‑term bonus, or it might be part of a retirement arrangement that is actually a post‑employment benefit. The accounting treatment can be completely different even if the cash flow looks similar.
3. Short‑term employee benefits – the everyday workhorse
Short‑term employee benefits are the benefits most people are already familiar with, and they are usually the starting point when learning HKAS 19 / IAS 19.
What counts as short‑term employee benefits?
HKAS 19 defines short‑term employee benefits as employee benefits that are expected to be settled wholly within 12 months after the end of the reporting period in which employees render the related service, excluding termination benefits. Typical examples include:
- Wages and salaries, and employer contributions to MPF or similar schemes that relate to current service.
- Paid annual leave and paid sick leave, to the extent these are expected to be used within a reasonable period.
- Profit‑sharing schemes and bonuses, if the entity expects to pay them within 12 months after the end of the reporting period.
- Non‑monetary benefits for current employees, such as medical coverage, company cars and staff accommodation.
These items are very common in Hong Kong payroll structures, so understanding their accounting treatment is critical for month‑end, year‑end and audit work.
General rule: accrue the undiscounted amount
For short‑term employee benefits, HKAS 19 requires the entity to recognise liabilities and expenses at undiscounted amounts. More concretely:
- As employees perform services during an accounting period, the entity recognises the expected undiscounted amount of short‑term benefits it will have to pay in exchange for that service.
- That amount is recognised as a liability (for example, accrued salaries or accrued bonuses) and as an expense, unless it qualifies for capitalisation as part of the cost of an asset such as property, plant and equipment or inventory.
Because these benefits are settled in a short time frame, the time value of money is not considered significant, so the standard lets you ignore discounting and simply accrue the nominal amount.
Annual leave and sick leave: accumulative vs non‑accumulative
Annual leave and sick leave are classic exam and audit points under short‑term benefits. HKAS 19 focuses on whether the leave is accumulative:
- Accumulative leave: unused days can be carried forward. The entity must accrue the cost of leave that employees have earned but not yet taken, because this represents an obligation to provide paid time off (or cash compensation) in future periods.
- Non‑accumulative leave: if unused entitlement lapses (for example, some types of sick leave that cannot be carried forward), the entity generally recognises expense only when employees actually take the leave. There is usually no obligation for unused entitlement, so no accrual is needed.
In practice, HR systems often track each employee’s leave balance. At year‑end, the accounting team uses this data to calculate the accrual for unused, accumulative annual leave. This avoids pushing the cost into future periods when the employee eventually takes the leave, which auditors frequently pick up as a common adjustment if it is missed.
Short‑term bonuses and profit‑sharing
Short‑term bonuses and profit‑sharing schemes are another common area where HKAS 19 applies. The standard generally requires an accrual at the reporting date if:
- The entity has a present obligation to pay bonus or profit‑sharing amounts that arises from past employee service (this can be legal, contractual, or a constructive obligation based on established practice and valid expectations of employees).
- The amount can be estimated reliably, for example by reference to profit levels, performance metrics or an approved bonus plan.
Example: Suppose the entity operates an annual profit‑sharing plan: if profit before tax exceeds a threshold, 10% of profit is distributed to staff as bonuses, and historically it pays the bonus by March of the following year. If the threshold is met and management expects to pay bonuses according to the plan, the bonus expense and liability should be recognised at year‑end, not only when cash is paid next year. This reflects that employees have already earned the bonus through current‑year service.
4. High‑level view of post‑employment benefits
Post‑employment benefits are the heavyweight category in HKAS 19 / IAS 19. They include pensions, retirement lump‑sum payments, and post‑retirement medical or life insurance coverage. The common feature is that employees have finished their employment, but the entity still has to provide benefits under earlier promises.
Under HKAS 19, these benefits are usually provided through post‑employment benefit plans, which are split into:
- Defined contribution plans (DC): the entity’s obligation is mainly to pay fixed contributions (for example, a fixed percentage of salary) to a separate fund; once the contributions are paid, there is no further significant obligation regarding future returns.
- Defined benefit plans (DB): the entity is responsible for delivering agreed retirement benefits (for example, a formula based on final salary and years of service), and therefore bears actuarial and investment risk, requiring actuarial valuation, discount rates and various assumptions.
Because the focus of this article is the overall classification framework, we only park post‑employment benefits here at a high level, so you know where they sit within the four categories before diving into DC vs DB measurements later.
5. Other long‑term and termination benefits – what you must know early on
Once you move beyond short‑term benefits, HKAS 19 increasingly involves estimates and discounting. Even without becoming an actuary, you should understand what these benefits look like and why they matter.
Other long‑term employee benefits: long‑run promises during employment
“Other long‑term employee benefits” is the residual category: all employee benefits that are not short‑term benefits, not post‑employment benefits and not termination benefits. Common examples include:
- Long‑service leave or long‑service awards (for example, 10‑year service awards).
- Long‑term disability benefits or long‑term sick leave.
- Long‑term profit‑sharing or bonus plans that are not expected to be fully settled within 12 months after the reporting period.
- Certain anniversary or long‑term incentive schemes.
Typical features of these benefits are:
- They are usually tied to length of service or long‑term performance.
- Settlement happens over a longer horizon, often beyond one year.
- The obligation builds up over the employee’s service period, so cost has to be allocated over that period.
HKAS 19 requires these benefits to be measured using a method similar to defined benefit plans: the projected unit credit method, discounting future cash flows to present value and recognising changes mostly in profit or loss. Unlike some post‑employment DB obligations, actuarial gains and losses for other long‑term employee benefits generally do not go through other comprehensive income; they go straight into profit or loss.
A practical example: if an entity promises a lump‑sum long‑service award when an employee completes 10 years of service, HKAS 19 would expect the entity to recognise a discounted liability and related expense gradually over the service period, even if, operationally, nobody has set up a “provision” internally. This is why auditors ask detailed questions about HR policies and long‑service benefits when understanding employee arrangements.
Termination benefits: tied directly to ending employment
Termination benefits form a separate bucket. HKAS 19 defines them as benefits provided in exchange for the termination of an employee’s employment, either at the entity’s initiative or as an offer to encourage voluntary redundancy.
The key idea is that these benefits arise because of termination, not as part of the normal pattern of accumulating service entitlements. Examples include:
- Redundancy payments when an entity restructures and dismisses staff.
- Special payments under a voluntary departure scheme if employees accept termination within a specified period.
- Additional statutory compensation when a plant or department is closed and staff must be laid off.
Recognition timing is crucial. HKAS 19 generally requires the entity to recognise a termination benefit liability and expense when it can no longer unilaterally withdraw the offer of those benefits, or, in the case of a voluntary scheme, when it has made an offer and it is likely that a significant number of employees will accept.
A common pitfall is misclassifying benefits: if the entity has long‑standing policy that employees receive a long‑service payment when they leave after 10 years, without any special restructuring decision, this looks more like “other long‑term employee benefits” than termination benefits. Only when the termination event itself creates the obligation does it fall into the termination bucket.
6. Building a mental map for HKAS 19 / IAS 19
Now that you have seen the four categories, it is useful to organise HKAS 19 into a simple three‑layer mental map.
Layer 1 – What HKAS 19 is governing
At the widest level, you can remember one sentence: HKAS 19 / IAS 19 governs how employers recognise liabilities and expenses for employee benefits, for almost all staff‑related benefits other than share‑based payments.
This layer connects:
- Objective: employee service leads to recognition of benefit liabilities and expenses.
- Scope: employee benefits, excluding HKFRS 2 share‑based payments and excluding separate reporting by the benefit plan itself under HKAS 26 / IAS 26.
Layer 2 – Classifying into four categories by timing and nature
The second layer is the four categories themselves. A quick question‑based decision tree you can use in practice is:
- Question 1: Is the benefit expected to be wholly settled within 12 months after the end of the reporting period, and is it not a termination benefit?
- If yes, it is likely a short‑term employee benefit.
- Question 2: Is the benefit enjoyed after completion of employment, and not a termination arrangement?
- If yes, it is a post‑employment benefit, which will involve DC vs DB analysis.
- Question 3: If it is not short‑term, not post‑employment and not termination, where does it go?
- It falls into other long‑term employee benefits, measured using a DB‑style approach with all changes in profit or loss.
- Question 4: Is the benefit triggered by termination decisions (redundancy, closure, voluntary departure schemes)?
- If yes, it is a termination benefit, with focus on when the entity’s commitment becomes irrevocable.
This set of questions helps you quickly classify any new benefit scheme you encounter in your job.
Layer 3 – How deep the measurement work goes
The final layer is the level of measurement complexity for each category:
- Short‑term employee benefits: usually only undiscounted accruals. The main risk is missing accruals, mis‑classifying accumulative vs non‑accumulative leave, or failing to accrue bonuses when obligations exist.
- Post‑employment benefits: the “heavy” part of HKAS 19 / IAS 19, especially defined benefit plans, involving actuarial valuations, discount rates, service cost, net interest and treatment of remeasurement through other comprehensive income.
- Other long‑term employee benefits: measured with a similar DB model, but all remeasurements go through profit or loss, which can directly affect reported earnings.
- Termination benefits: often a one‑off recognition when the termination plan is committed and cannot be withdrawn, with emphasis on classification and timing rather than long‑term accumulation.
For beginners, it is more efficient to first master the “map” and short‑term benefits, then move on to the technical parts of post‑employment DB plans.
Key takeaways for students and junior accountants
Here are some practical ways to apply this framework in real work and exam situations:
- When you see any payment or scheme related to employees, ask yourself: which of the four categories does it belong to, when is it expected to be settled, and is it a normal service benefit or triggered by termination?
- When drafting journal entries or working papers, add a short note such as “classified as short‑term employee benefit under HKAS 19, accrued at undiscounted amount” or “classified as other long‑term employee benefit, measured using DB‑style method”. This makes later reviews and audit discussions much easier.
- In exams, do not rush into calculations. First identify whether the question is about short‑term, post‑employment, other long‑term or termination benefits; many marks come from getting the classification and logic right.
- In audits or internal reviews, pay special attention to areas where entities often make mistakes: unaccrued annual leave, bonuses not accrued despite constructive obligations, long‑service schemes ignored as “just HR policy”, and termination packages recognised too early or too late.
- When reading note disclosures in financial statements, compare what the entity says about employee benefits with this framework: ask yourself how you would classify those schemes and whether the disclosure tells a consistent story about timing, measurement and risk.
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/
