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.
Retirement Plans and Who Carries the Risk
In Hong Kong accounting and audit work, the most common post‑employment benefits are MPF contributions, staff retirement schemes and some extra retirement compensation arrangements in particular industries. On the surface, they all look similar: “the company pays something every month, and staff will get money when they retire”. But under HKAS 19 / IAS 19, the underlying classification and accounting treatment can be very different.
Consider two typical situations:
- A company has a retirement plan where it pays a fixed percentage of salary each month into a fund. The fund is managed by an external provider. Investment gains and losses go to the employee’s account. The company does not promise any minimum return or fixed retirement payout.
- Another, more “traditional” or overseas‑style plan promises that when an employee retires, they will receive a pension based on a formula such as “final salary × years of service × a certain percentage”. If the fund is not sufficient, the company has to top up.
From the financial reporting perspective:
- The first type is usually a defined contribution (DC) plan.
- The second type is usually a defined benefit (DB) plan, and DB plans under HKAS 19 are much more complex to measure and disclose, often requiring actuarial valuations and discounting.
This article focuses on the questions that matter most for beginners:
- What counts as a post‑employment benefit plan?
- How does HKAS 19 classify these plans into DC and DB based on economic substance, not just labels?
- Why is DC treated as the “simple base case”, and DB as the more exceptional, complex version?
- For DC plans, how should the company account for contributions, employee contributions and multi‑employer schemes in practice?
What You Should Be Able To Do After Reading?
By the end, you should be able to:
- Describe the scope of post‑employment benefits, including pensions, lump‑sum retirement payments and post‑retirement medical coverage, and explain why HKAS 19 / IAS 19 emphasises economic substance when distinguishing DC from DB.
- Decide whether a particular post‑employment arrangement is a defined contribution plan by checking whether the employer’s obligation is limited to agreed contributions and whether actuarial and investment risks sit with the employee.
- Apply the basic accounting treatment for defined contribution plans: when to recognise expenses and liabilities, when contributions can be capitalised, why discounting is needed if settlement is more than 12 months after service, and how to think about the entries.
- Understand the 2013 practical expedient for employee contributions: in what circumstances employees’ contributions can be treated as a straightforward reduction of current service cost, without complex attribution over service lives.
- Appreciate why some multi‑employer plans must be accounted for as if they were DC plans when information is insufficient, and what that means for users trying to understand the company’s real risk exposure, setting the stage for deeper DB study later.
1. What are post‑employment benefits under HKAS 19 / IAS 19?
Within HKAS 19 Employee Benefits (equivalent to IAS 19), post‑employment benefits are one of the main categories of employee benefits. They are benefits payable after completion of employment, excluding short‑term employee benefits and termination benefits. Common examples include:
- Pensions paid monthly or annually after retirement.
- Lump‑sum retirement or severance payments payable when an employee leaves or retires.
- Post‑employment life insurance.
- Post‑employment medical care.
These benefits are usually provided through a post‑employment benefit plan, which may be a straightforward contribution scheme (DC) or a more complex guaranteed benefit scheme (DB).
Why the standard cares about economic substance, not labels
HKAS 19 requires all post‑employment benefit plans to be classified as either:
- Defined contribution plans (DC); or
- Defined benefit plans (DB).
Crucially, classification is based on the economic substance of the plan’s terms, not on the plan’s name or how it is marketed. The reasons are:
- The two types allocate risk differently. In DC plans, investment and actuarial risk mainly sit with employees; in DB plans, those risks sit with the employer.
- Different risk allocation means the employer’s obligation is different:
- If the company only has to pay agreed contributions and does not have to make good any shortfall, the obligation is relatively “short, simple and clear” – accounting focuses on contributions due.
- If the company has promised a guaranteed level of retirement benefit and must top up if plan assets are insufficient, the obligation is long‑term and uncertain and must be measured with actuarial techniques.
Getting the classification right is the starting point for all later accounting. In practice, a company may operate several post‑employment plans; some may be DC, others DB, and they cannot be treated the same just for convenience.
2. Defined contribution plans – definition and who bears the risk
HKAS 19 summarises a defined contribution plan like this: the employer’s obligation is limited to paying agreed contributions into a separate fund (or arrangement), and the employer has no legal or constructive obligation to pay further amounts if the fund does not hold sufficient assets to pay all employee benefits.
In a DC plan:
- The company pays fixed or determinable contributions, usually as a percentage of salary.
- Contributions are typically paid into a separate entity, such as a pension fund.
- The benefits an employee ultimately receives depend on the fund’s investment performance and accumulated contributions.
- The company does not guarantee any particular return or final benefit level.
From the company’s perspective, once the contributions are paid, its obligation is finished; it is not forced to make good poor investment performance.
Who carries actuarial and investment risk?
When explaining the DC–DB split, HKAS 19 highlights two types of risk:
- Actuarial risk: the risk that the ultimate cost of providing benefits is higher than expected (for example, people live longer than assumed).
- Investment risk: the risk that investment returns will be insufficient to fund expected benefits.
In a defined contribution plan, these risks fall mainly on employees:
- If investment performance is weak, the value in the employee’s retirement account is lower.
- The company is generally not required to top up the difference.
So long as the plan does not promise minimum returns, fixed benefit formulas or other features that shift risk back to the employer, it remains a DC plan.
Common real‑life scenario: a typical Hong Kong retirement scheme
A typical Hong Kong arrangement looks like this:
- The company contributes, say, 5% of each employee’s monthly salary into a designated retirement fund.
- Employees can choose among different investment options (conservative, balanced, growth, etc.).
- On retirement, the employee receives whatever has accumulated in their account: contributions plus investment returns.
In such a case:
- The company’s obligation is limited to paying the 5% contributions. It does not have to compensate employees if the fund underperforms.
- The company has not guaranteed any minimum payout on retirement.
This fits HKAS 19’s definition of a defined contribution plan. If, at a later point, the company adds features such as a guaranteed minimum return or a formula like “final salary × years of service × factor”, it would need to reassess whether the plan has turned into a DB plan.
3. Accounting for defined contribution plans in practice
One advantage of defined contribution plans is that their accounting is relatively straightforward compared with DB plans. You can think of DC contributions as a form of “immediate expensing” of staff costs as services are rendered.
Basic principle: contributions are the expense (unless capitalised)
HKAS 19 requires the company to recognise contributions payable to a defined contribution plan as an expense in the period during which employees render the services that give them an entitlement to those contributions. Put simply:
- When employees work in a period, and the company promises to pay retirement contributions for that service, the contribution amount (for example, current salary × fixed percentage) is the employee benefit expense for that period.
- If part of the employee cost relates directly to the construction of an asset or production of inventory, that portion can be capitalised as part of the cost of that asset, in line with other staff costs.
This aligns with the broader HKFRS / IFRS principle of matching staff costs to the period of service while not deferring obvious current obligations.
Recognising the liability: contributions accrued but unpaid
At the end of a reporting period, contributions that relate to employee service already rendered but have not yet been paid must be recognised as a liability, typically labelled “accrued pension contributions” or included within broader “accrued employee benefits”.
Simplified example:
- For a given month, the company is required to pay HK$100,000 of retirement contributions, but this amount remains unpaid at the reporting date. The entries are:
- Dr Staff costs / administrative expenses HK$100,000;
- Cr Contributions payable to retirement plan HK$100,000.
- When the company subsequently pays the contributions:
- Dr Contributions payable HK$100,000;
- Cr Bank HK$100,000.
If some staff costs qualify for capitalisation (for example, directly attributable to construction in progress or development), the corresponding contribution portion would debit “construction in progress” or “development costs” instead of current‑period expense.
When does discounting come into play?
Although defined contribution plans usually feel short‑term, HKAS 19 retains a general rule:
- If contributions are expected to be settled more than 12 months after the end of the period in which employees render the related service, and the amount is fixed or determinable, the obligation should be discounted to present value.
In practice, most DC contributions are settled within a short timeframe (for example, monthly or shortly after year‑end), so the undiscounted amount is normally adequate and discounting is not required. Only when the agreed payment schedule is clearly deferred beyond one year does discounting become relevant.
For learners, it is enough to remember:
- Typical case: expected settlement within 12 months – recognise the nominal (undiscounted) amount.
- Exceptional case: unusual delays beyond 12 months – consider discounting.
4. Employee contributions and the 2013 practical expedient
Defined contribution plans often involve employee contributions as well as employer contributions. HKAS 19 has specific guidance on how employee and third‑party contributions are treated, especially for defined benefit plans, but understanding the principles helps build your intuition.
General thinking around employee contributions
In some post‑employment benefit plans, employees are required to contribute a percentage of their salary. These contributions affect the overall cost of providing benefits because the plan as a whole (not just the employer) funds the retirement benefits.
In a pure DC context, the accounting for employee contributions is less complex, because the employer’s obligation is still just its own contributions. But in DB plans, employee contributions were originally supposed to be treated as “negative benefits” and allocated over the employees’ service lives, which can be operationally painful.
The 2013 practical expedient: when service‑period attribution is not needed
To reduce complexity, IAS 19 and HKAS 19 introduced a practical expedient in the 2013 amendments:
- If employee or third‑party contributions are set out in the formal terms of the plan, and
- Those contributions are independent of the employees’ years of service (for example, “5% of salary” every year, regardless of length of service),
then the entity may treat these contributions as a straightforward reduction in the service cost in the period in which the related service is rendered, without performing detailed attribution over service periods.
In simple language:
- If the contribution pattern is simple and does not vary with seniority, you can treat “what employees pay this year” as reducing “this year’s service cost”.
- If the contribution pattern depends on service length (for example, employees with more than 10 years’ service contribute at a higher rate), then the standard’s general attribution rules still apply and the contributions must be spread over service life appropriately.
In practice, this practical expedient mainly affects DB plan measurements rather than basic DC accounting. For DC purposes, it is enough to note that HKAS 19 recognises the need for operational simplicity where the contribution pattern is simple and stable.
5. Multi‑employer plans and the “forced DC” limitation
Not all retirement schemes are set up by a single employer. Some industries use multi‑employer plans that several unrelated companies participate in, with one fund providing benefits to employees of different employers.
Classification principles for multi‑employer plans
HKAS 19 states that a multi‑employer plan can be either DC or DB, depending on its economic substance:
- If each participating company only has to pay fixed contributions and has no obligation for any deficit in the fund, the plan is treated as DC.
- If the plan guarantees benefits and employers are required to make additional contributions to cover deficits, the plan is DB.
So the same DC vs DB logic applies as for single‑employer plans.
When the plan is DB but the company lacks information
A tricky real‑world situation arises when:
- The legal and practical features of the multi‑employer plan clearly indicate DB characteristics (for example, guaranteed retirement benefits), but
- An individual participating company cannot obtain sufficient information to apply DB accounting (for example, to calculate its share of the defined benefit obligation and plan assets).
In that case, HKAS 19 allows an exception: the company must account for the plan as if it were a defined contribution plan. That means:
- Recognising contributions due as an expense in the period of service.
- Disclosing in the notes that the plan is, in substance, a DB plan, but is being accounted for as DC because adequate information is not available, and explaining the associated risk implications.
This is the “forced DC” situation: from a standard‑setting perspective, it is a practical compromise, not the ideal.
Practical implications and potential controversy
The benefit of this approach is that it avoids freezing reporting simply because the company cannot get full actuarial data. However, it introduces another risk:
- The financial statements may only show the current‑period contributions as expense and not fully reflect the company’s share of the long‑term DB obligation or deficit risk in the multi‑employer plan.
Therefore, HKAS 19 requires robust disclosures when this expedient is used. Users should be told:
- That the plan is DB in nature.
- Why DB accounting cannot be applied.
- How surpluses or deficits might in future affect the company’s contribution levels.
When you read annual reports and see language like “this multi‑employer pension plan is, in substance, a defined benefit plan but is accounted for as a defined contribution plan”, treat it as a warning sign that reported pension expense may not capture all long‑term risk.
6. From DC to DB – why DB is so much more complex
Within the world of post‑employment benefits under HKAS 19 / IAS 19, defined contribution plans are a natural starting point. They are characterised by:
- Relatively simple employer obligations, often involving contributions due within a short timeframe.
- Most actuarial and investment risk resting with employees.
- Accounting based on “contributions equal expense” (subject to capitalisation and any discounting where settlement is significantly delayed).
Once you understand DC, it becomes easier to see why DB plans feel many times more complex:
- In a DB plan, the company promises a result (for example, a pension formula) rather than just a contribution amount.
- Actuarial and investment risks sit with the company, and the obligation changes with time and changes in assumptions.
- HKAS 19 requires use of the projected unit credit method, discounting future cash flows, and splitting the effects into service cost, net interest and remeasurement components.
From a learning path perspective, it is more efficient to build a solid DC foundation first, then move into DB topics such as how to calculate the defined benefit obligation, choose discount rates, treat actuarial gains and losses, and understand the impact of changes in assumptions on profit or loss and other comprehensive income. This step‑by‑step approach fits better with both Hong Kong practice and typical exam progression.
Key takeaways for students and junior accountants
- When you encounter any post‑employment benefit arrangement in work or exam questions, start by asking: “Is this DC or DB? Does the company only promise contributions, or does it also guarantee the outcome?” Use that classification to guide everything else.
- In working papers, explicitly document your judgement: quote the HKAS 19 definition of a defined contribution plan, explain who bears actuarial and investment risk, and state why the plan is treated as DC rather than DB. This makes reviews and audits much smoother.
- For DC plans, watch out for two common pitfalls: failing to accrue contributions earned but unpaid at period‑end, and ignoring the potential need for discounting when settlement is clearly more than 12 months after service.
- When reading plan documents or contracts, highlight any wording about “guaranteed minimum benefits”, “fixed pension formulas” or “top‑up obligations if assets are insufficient”. These are red flags that the plan may be DB, or at least not a straightforward DC arrangement.
- As you move into more advanced HKAS 19 / IAS 19 study, use DC as your anchor: think of DB as “DC plus: promise of outcome, employer‑borne risk, actuarial valuation, discounting and remeasurement”. This mental link helps you avoid getting lost in formulas and focus on the underlying economic story.
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/
