IAS 19 is the international accounting standard for employee benefits. In practical terms, it tells companies how to recognize, measure, present, and disclose costs and obligations related to salaries, bonuses, leave, gratuity, pensions, post-retirement medical benefits, and termination pay. If a business promises employees benefits now or in the future, IAS 19 helps turn those promises into proper financial reporting.

1. Term Overview

• Official Term: IAS 19
• Common Synonyms: IAS 19 Employee Benefits, Employee Benefits Standard
• Alternate Spellings / Variants: IAS-19, IAS 19
• Domain / Subdomain: Finance / Accounting Standards and Frameworks
• One-line definition: IAS 19 is the IFRS accounting standard that prescribes how entities account for employee benefits.
• Plain-English definition: It is the rulebook that says when a company must record employee-related expenses and liabilities, including benefits that will be paid later, such as pensions or gratuity.
• Why this term matters:
  IAS 19 affects profit, liabilities, equity, cash planning, disclosures, and investor interpretation. For companies with large workforces or retirement plans, it can materially change reported earnings and financial position.

2. Core Meaning

At its core, IAS 19 exists because employee services are often received today, while payment may happen later.

A company may pay: – immediately, like monthly salary, – shortly after year-end, like bonuses, – many years later, like pension benefits, – or upon exit, like severance.

Without a standard, companies could delay recognizing costs until cash is paid. That would understate current expenses and liabilities. IAS 19 solves this by requiring recognition when employees earn the benefit, not merely when cash leaves the bank.

What it is

IAS 19 is an accounting standard in the IFRS/IAS framework dealing with employee benefits.

Why it exists

It exists to: – match employee cost with the period in which employees provide service, – make liabilities visible before settlement, – improve comparability across companies, – standardize measurement of long-term obligations such as pensions and gratuity.

What problem it solves

It solves problems such as: – under-reporting future employee obligations, – inconsistent treatment of retirement and leave benefits, – poor disclosure of actuarial assumptions, – weak comparability between companies with different benefit structures.

Who uses it

IAS 19 is used by: – preparers of financial statements, – accountants and finance teams, – auditors, – actuaries, – CFOs and controllers, – investors and analysts, – lenders and rating agencies, – regulators reviewing financial reporting.

Where it appears in practice

You typically see IAS 19 in: – annual report notes on employee benefits, – pension and gratuity disclosures, – bonus and leave accrual calculations, – OCI disclosures for defined benefit remeasurements, – restructuring and severance accounting, – audit workpapers and actuarial valuation reports.

3. Detailed Definition

Formal definition

IAS 19 prescribes the accounting and disclosure for employee benefits. It requires an entity to recognize: 1. a liability when an employee has provided service in exchange for benefits to be paid in the future, and 2. an expense when the entity consumes the economic benefit arising from service provided by an employee.

Technical definition

Technically, IAS 19 governs recognition, measurement, presentation, and disclosure of: – short-term employee benefits, – post-employment benefits, – other long-term employee benefits, – termination benefits.

For defined benefit arrangements, it requires actuarial measurement of the present value of obligations, recognition of plan assets at fair value, and specific presentation of service cost, net interest, and remeasurements.

Operational definition

In day-to-day finance work, IAS 19 is the standard used to: – accrue salaries and bonuses, – estimate leave encashment, – measure gratuity and pension liabilities, – account for employer contributions to retirement plans, – recognize severance obligations, – explain pension-related profit or OCI movements to management and investors.

Context-specific definitions

Under IFRS / international usage

“IAS 19” usually means the standard Employee Benefits.

In India

Professionals often discuss the equivalent or closely aligned local framework, most commonly Ind AS 19, when referring to IFRS-style employee benefit accounting. Some entities outside Ind AS may instead follow local GAAP rules, so the exact applicable text should be verified.

In the US

“IAS 19” is not the governing standard under US GAAP. Comparable topics are covered mainly under ASC 715 and related US guidance.

4. Etymology / Origin / Historical Background

“IAS” stands for International Accounting Standard. These standards were originally issued in the international accounting framework before the widespread use of the “IFRS” label for newer standards.

Origin of the term

• IAS = International Accounting Standard
• 19 = the standard number assigned to employee benefits

Historical development

International accounting needed a consistent way to report retirement and employee benefit costs, especially where obligations stretched decades into the future.

Earlier international guidance focused more narrowly on retirement benefit accounting. Over time, the scope broadened to include a fuller range of employee benefits such as paid leave, bonuses, post-employment medical plans, and termination benefits.

How usage changed over time

The most important shift was from simpler cash-based thinking toward: – accrual accounting, – actuarial valuation, – explicit recognition of pension deficits, – more robust disclosure of assumptions and risks.

Important milestones

Key milestones commonly associated with IAS 19 include: – development of international guidance for retirement and employee benefit accounting, – issue of the modern IAS 19 Employee Benefits standard, – later revisions that significantly changed defined benefit accounting, – removal of the old “corridor” approach, – immediate recognition of past service cost, – stronger disclosure requirements, – updates for plan amendments, curtailments, and settlements.

Why the history matters

The historical evolution explains why IAS 19 is now much stricter and more transparent than older pension accounting models. It reflects a policy choice: employee obligations should not stay hidden.

5. Conceptual Breakdown

IAS 19 is easiest to understand if you break it into six layers.

5.1 Recognition principle

Component	Meaning	Role	Interaction with other components	Practical importance
Service creates obligation	Employees earn benefits by working	Triggers accounting recognition	Drives classification and measurement	Prevents delay of expense recognition
Liability recognition	Future payment obligation is recorded	Shows unpaid benefits on balance sheet	Links to measurement rules	Important for leverage and covenant analysis
Expense recognition	Cost is recognized as service is consumed	Affects profit or asset cost	May go to P&L, OCI, or asset cost depending on nature	Essential for period matching

5.2 Benefit categories

IAS 19 divides employee benefits into four major categories.

Category	Meaning	Typical examples	Measurement basis	Practical importance
Short-term employee benefits	Expected to be settled wholly within 12 months after the reporting period in which service is rendered	salaries, wages, annual bonus, paid leave, medical benefits, non-cash perks	Usually undiscounted	Common and frequent
Post-employment benefits	Payable after completion of employment	pension, gratuity, post-retirement medical care	Defined contribution or defined benefit rules	Often financially significant
Other long-term employee benefits	Long-term but not post-employment or termination	long-service leave, jubilee awards, deferred bonus beyond 12 months	Similar to DB measurement, but gains/losses usually go to profit or loss	Often overlooked
Termination benefits	Benefits provided in exchange for termination	severance, voluntary retirement package	Recognized when the offer can no longer be withdrawn or restructuring is recognized	Important in restructurings

5.3 Plan type: defined contribution vs defined benefit

Plan type	Meaning	Role	Interaction	Practical importance
Defined contribution (DC)	Employer pays fixed contributions and normally has no further obligation beyond that	Simpler accounting	Usually expense = contributions due	Common in modern retirement plans
Defined benefit (DB)	Employer promises a specific benefit formula or bears actuarial/investment risk	More complex accounting	Requires actuarial assumptions, plan asset measurement, OCI treatment	Can create large liabilities and volatility

5.4 Measurement mechanics

For long-term and post-employment defined benefit obligations, IAS 19 relies on: – present value concepts, – discount rates, – actuarial assumptions, – employee demographics, – salary growth, – expected benefit formula, – fair value of plan assets.

These pieces interact tightly: – changing the discount rate changes the obligation, – changing salary growth assumptions changes future benefit estimates, – changing asset values affects the net funded position, – all of this can affect profit, OCI, and disclosures.

5.5 Presentation buckets

IAS 19 does not send every movement to the same place.

For defined benefit plans, the accounting is commonly split into: – service cost: usually in profit or loss, – net interest: usually in profit or loss, – remeasurements: in OCI, not recycled to profit or loss.

This presentation is one of the most tested and most misunderstood parts of the standard.

5.6 Disclosure layer

IAS 19 also requires disclosures that help users understand: – the nature of benefit plans, – the risks involved, – movements in obligations and assets, – major assumptions, – sensitivity to assumptions, – timing of future cash flows.

Two practical sub-points students often miss

Accumulating vs non-accumulating paid absences

• Accumulating: unused leave carries forward; obligation builds over time.
• Non-accumulating: unused leave lapses; expense is recognized when absence occurs.

Constructive obligation

A company may have an obligation not only because of law or contract, but also because past practice creates a valid expectation, such as a recurring bonus pattern.

6. Related Terms and Distinctions

Related Term	Relationship to Main Term	Key Difference	Common Confusion
Ind AS 19	Local Indian equivalent or near-equivalent in IFRS-converged reporting	Applies under Indian accounting framework, not automatically under IFRS text	People often use IAS 19 and Ind AS 19 interchangeably without checking local applicability
ASC 715	US GAAP counterpart for pension and other benefit accounting	Different detailed rules and presentation conventions	Users assume US accounting works exactly like IAS 19
IAS 26	Related to retirement benefit plans	IAS 26 deals with reporting by retirement benefit plans themselves, not employer accounting like IAS 19	Confused because both involve retirement benefits
IFRS 2	Related because both concern compensation	IFRS 2 covers share-based payment, not normal employee benefits	Employee stock options are not an IAS 19 item
IAS 37	Related in obligations/provisions	IAS 37 covers broader provisions and contingencies; IAS 19 specifically governs employee benefits	Termination and restructuring costs can overlap conceptually
Defined contribution plan	Sub-concept within IAS 19	Employer obligation is usually limited to contributions	Sometimes wrongly treated like defined benefit plans
Defined benefit plan	Sub-concept within IAS 19	Employer bears actuarial/investment risk	Often confused with any retirement plan
Defined benefit obligation (DBO)	Core measurement concept under IAS 19	The present value of promised defined benefits	Confused with cash funding requirement
Plan assets	Assets set aside to pay benefits	Reduce the net liability or create a surplus	Not every company-designated investment qualifies as plan assets
OCI	Presentation category used in IAS 19	Certain remeasurements go to OCI, not profit or loss	Many readers expect all pension changes in profit or loss
Asset ceiling	Restricts recognition of surplus as an asset	Even if a plan has a surplus, not all of it may be recognized	Users assume surplus always becomes a balance sheet asset
Actuarial valuation	Tool used to measure some IAS 19 obligations	It is a measurement process, not the standard itself	Some think the actuary “creates” the liability rather than measures it

Most commonly confused comparisons

IAS 19 vs IFRS 2

• IAS 19: salary, bonus, leave, pension, gratuity, severance
• IFRS 2: stock options, share grants, equity-settled compensation

Defined contribution vs defined benefit

• DC: fixed contribution promise
• DB: fixed benefit promise or employer bears risk

Post-employment benefits vs termination benefits

• Post-employment: normal retirement-related or after-service benefits
• Termination benefits: arise because employment ends

Short-term benefits vs other long-term benefits

• Short-term: settled within the defined 12-month window
• Other long-term: settlement expected beyond that period

7. Where It Is Used

IAS 19 is primarily an accounting standard, but its effects spread across several finance functions.

Accounting and financial reporting

This is the main area of use. IAS 19 appears in: – statement of profit or loss, – balance sheet liabilities or assets, – OCI, – notes to accounts, – actuarial valuation disclosures.

Corporate finance and treasury

It matters for: – cash contribution planning, – pension funding strategy, – working capital forecasting for bonuses and leave, – evaluating long-term obligations.

Equity investing and valuation

Investors use IAS 19 information to: – assess hidden leverage, – compare pension deficits across firms, – adjust enterprise value or debt-like obligations, – judge earnings quality.

Banking and lending

Lenders and credit analysts examine IAS 19 amounts to: – test covenant pressure, – assess solvency risk, – evaluate future cash drain from benefit obligations.

Business operations and HR policy

Companies use IAS 19 outputs when: – designing compensation structures, – shifting from DB to DC plans, – estimating leave liabilities, – assessing the cost of workforce retention or exit.

Regulation and governance

Audit committees, regulators, and stock exchange reviewers may focus on: – adequacy of pension disclosures, – consistency of assumptions, – material severance or restructuring charges, – transparency of OCI movements.

Analytics and research

Analysts use IAS 19 data in: – peer comparison, – trend analysis, – pension sensitivity analysis, – workforce cost modeling.

8. Use Cases

Use Case 1: Accruing monthly salaries and unpaid payroll

• Who is using it: Finance team of any employer
• Objective: Match salary expense to the period employees worked
• How the term is applied: IAS 19 requires recognizing unpaid salary as a liability at period-end
• Expected outcome: Financial statements show full labor cost even if payment happens next month
• Risks / limitations: Errors arise if payroll cut-off is poor or bonus components are omitted

Use Case 2: Recognizing annual bonus obligations

• Who is using it: Controller, HR finance, audit team
• Objective: Record performance bonuses in the correct reporting period
• How the term is applied: If employees rendered service and the entity has a legal or constructive obligation, bonus expense is accrued
• Expected outcome: Better matching of employee cost to the year’s performance
• Risks / limitations: Management optimism, unclear plan rules, or no reliable estimate can distort accruals

Use Case 3: Measuring gratuity or pension obligations

• Who is using it: Large employers, actuaries, listed companies
• Objective: Measure long-term post-employment obligations
• How the term is applied: Defined benefit obligations are valued using actuarial methods and discounted to present value
• Expected outcome: Balance sheet shows current estimate of future retirement-related promises
• Risks / limitations: Highly sensitive to discount rate, salary growth, mortality, and employee turnover assumptions

Use Case 4: Accounting for long-service leave or leave encashment

• Who is using it: Businesses with formal leave benefit programs
• Objective: Recognize employee leave obligations before payment
• How the term is applied: Benefits expected beyond 12 months may be treated as other long-term employee benefits and measured on a discounted basis
• Expected outcome: More accurate liability for leave obligations
• Risks / limitations: Companies often misclassify long-dated leave as a short-term item

Use Case 5: Recording severance in a restructuring

• Who is using it: CFO, restructuring team, external auditors
• Objective: Recognize termination benefits at the right time
• How the term is applied: Liability is recognized when the company can no longer withdraw the offer, or when a related restructuring obligation is recognized
• Expected outcome: Timely recognition of severance cost
• Risks / limitations: Timing is judgment-heavy and often challenged in audits

Use Case 6: Investor analysis of pension risk

• Who is using it: Equity analyst, credit analyst, portfolio manager
• Objective: Understand whether employee benefit obligations weaken financial strength
• How the term is applied: The analyst studies pension deficits, assumptions, OCI volatility, and funding requirements
• Expected outcome: Better valuation and risk-adjusted investment decisions
• Risks / limitations: Cross-company comparison is difficult when plans, assumptions, and local laws differ

9. Real-World Scenarios

A. Beginner scenario

• Background: A small company closes its books on 31 March. Employees have earned one week of salary that will be paid on 5 April.
• Problem: Should the company wait until cash is paid?
• Application of the term: IAS 19 says the service has already been received, so salary expense and liability must be recognized on 31 March.
• Decision taken: The company records salary expense and accrued payroll.
• Result: March profit is not overstated.
• Lesson learned: IAS 19 is not only about pensions; it starts with simple accruals too.

B. Business scenario

• Background: A manufacturing company has 4,000 employees and a gratuity plan.
• Problem: Management has historically focused only on annual cash contributions, not the full actuarial obligation.
• Application of the term: Under IAS 19, the company obtains an actuarial valuation of the defined benefit obligation and compares it with plan assets.
• Decision taken: It recognizes the net liability and discloses assumptions and sensitivity analysis.
• Result: Reported liabilities rise materially, and OCI becomes more volatile.
• Lesson learned: Cash funding and accounting obligation are related but not identical.

C. Investor / market scenario

• Background: An investor compares two listed companies with similar profits.
• Problem: One company has a large defined benefit deficit hidden in the notes, while the other mostly uses defined contribution plans.
• Application of the term: The investor adjusts the analysis for pension liability, future funding pressure, and OCI sensitivity.
• Decision taken: The investor assigns a lower valuation multiple to the more burdened company.
• Result: The analysis better reflects economic obligations, not just headline EPS.
• Lesson learned: IAS 19 can materially affect valuation quality.

D. Policy / government / regulatory scenario

• Background: A regulator reviews annual reports and finds weak pension disclosure quality across issuers.
• Problem: Investors cannot easily understand plan risks or key assumptions.
• Application of the term: IAS 19 requires disclosure of plan characteristics, assumptions, sensitivity, and movement in obligations and assets.
• Decision taken: The regulator emphasizes enforcement of disclosure requirements.
• Result: Reporting becomes more comparable and transparent.
• Lesson learned: IAS 19 supports market discipline through disclosure, not just recognition.

E. Advanced professional scenario

• Background: A company closes a business unit and offers enhanced early retirement to affected staff.
• Problem: The accounting impact may involve termination benefits, plan amendments, remeasurement, and possible settlement effects.
• Application of the term: Finance and actuarial teams reassess the defined benefit obligation using current assumptions and recognize relevant effects immediately where required.
• Decision taken: Management books a one-time charge, updates disclosures, and revises future service cost.
• Result: Current earnings fall, but future periods better reflect the changed workforce structure.
• Lesson learned: In complex restructurings, IAS 19 requires careful separation of service cost, termination cost, and remeasurement effects.

10. Worked Examples

10.1 Simple conceptual example

A company owes employees salary of 80,000 for the last week of March, payable in April.

Step 1: Identify service rendered
Employees already worked in March.

Step 2: Apply IAS 19
Recognize expense in March, not April.

Accounting effect – Employee benefit expense: 80,000 – Liability for accrued salaries: 80,000

Meaning:
The company cannot delay recognition just because cash is paid later.

10.2 Practical business example

A company promises: – annual bonuses estimated at 1,200,000, payable in June, – leave encashment of 300,000 expected to be paid next year.

Application – Bonus: usually short-term employee benefit if expected to be settled within 12 months after the reporting period – Leave encashment: classification depends on expected settlement timing; if beyond 12 months, it may fall into other long-term employee benefits

Result – Recognize a bonus liability now if a present obligation exists and can be estimated reliably – Classify and measure leave obligation based on expected settlement timing

Non-numerical lesson:
The same payroll family can contain different IAS 19 categories.

10.3 Numerical example: defined benefit plan

Assume the following for a year:

• Opening defined benefit obligation (DBO): 10,000
• Opening fair value of plan assets: 9,200
• Discount rate: 5%
• Current service cost: 600
• Employer contributions: 500
• Benefits paid: 400
• Actuarial loss on obligation: 300
• Actual return on plan assets: 560

Step 1: Calculate interest on opening balances

• Interest cost on DBO = 10,000 × 5% = 500
• Interest income on plan assets = 9,200 × 5% = 460

Step 2: Calculate closing DBO

Closing DBO:

• Opening DBO = 10,000
• Add current service cost = 600
• Add interest cost = 500
• Add actuarial loss = 300
• Less benefits paid = 400

Closing DBO = 11,000

Step 3: Calculate closing plan assets

Closing plan assets:

• Opening plan assets = 9,200
• Add employer contributions = 500
• Add actual return = 560
• Less benefits paid = 400

Closing plan assets = 9,860

Step 4: Compute closing net defined benefit liability

Net liability = Closing DBO – Closing plan assets
= 11,000 – 9,860
= 1,140

Step 5: Identify profit or loss and OCI components

Profit or loss – Current service cost = 600 – Net interest = 500 – 460 = 40

Total in profit or loss = 640

OCI – Actuarial loss on DBO = 300 – Return on plan assets excluding interest = 560 – 460 = 100 gain

Net OCI loss = 300 – 100 = 200 loss

Interpretation

• Profit or loss shows service cost and financing effect
• OCI captures remeasurement volatility
• Balance sheet shows the funded status at year-end

10.4 Advanced example: asset ceiling

Suppose: – DBO = 800 – Plan assets = 900

So the plan has a surplus of 100.

However, the company can only access economic benefit of 30 through refunds or reduced future contributions.

Recognized asset = lower of surplus (100) and asset ceiling (30) = 30

Key point:
Even if the plan is overfunded, the full surplus may not be recognized as an asset.

11. Formula / Model / Methodology

IAS 19 does not revolve around a single ratio like a market indicator. Instead, it uses a set of measurement formulas and actuarial methods.

11.1 Net defined benefit liability or asset

Formula

Net defined benefit liability = Present value of defined benefit obligation – Fair value of plan assets

If plan assets exceed the obligation, the recognized net asset is generally limited by the asset ceiling.

Meaning of each variable

• Present value of defined benefit obligation (DBO): discounted estimate of future promised benefits earned to date
• Fair value of plan assets: value of assets held to settle those benefits
• Asset ceiling: present value of economic benefits available as refunds or reductions in future contributions

Interpretation

• Positive amount: net liability
• Negative amount: potential net asset, but only to the extent recoverable

Sample calculation

Using the earlier example:

• DBO = 11,000
• Plan assets = 9,860

Net liability = 11,000 – 9,860 = 1,140

Common mistakes

• treating funding contribution as the same as annual expense,
• recognizing full surplus without testing the asset ceiling,
• confusing DBO with legal funding requirement.

Limitations

This number depends heavily on assumptions and market values, so it can change significantly even if the underlying plan design does not.

11.2 Net interest on the net defined benefit position

Formula

A simplified expression is:

Net interest = Discount rate × Opening net defined benefit liability (or asset)

In practice, timing of contributions and benefit payments may require refinement.

Meaning of each variable

• Discount rate: rate used to measure the obligation
• Opening net defined benefit liability/asset: funded status at start of the period

Interpretation

• If opening position is a liability, net interest usually increases expense
• If opening position is an asset, net interest may reduce expense or create income

Sample calculation

Opening DBO = 10,000
Opening plan assets = 9,200
Opening net liability = 800

Net interest = 800 × 5% = 40 expense

This matches: – interest cost on DBO = 500 – less interest income on plan assets = 460 – net = 40

Common mistakes

• using expected long-term asset return instead of the IAS 19 discount rate,
• ignoring the opening funded position,
• mixing actual plan asset return into profit or loss.

Limitations

The simplified formula is a reporting tool, not a full economic funding model.

11.3 Present value building block

A simple present value building block is:

PV = FV / (1 + r)^n

Where: – PV = present value – FV = future benefit payment – r = discount rate – n = number of periods until payment

Sample calculation

If a future benefit of 100,000 will be paid in 5 years and the discount rate is 6%:

PV = 100,000 / (1.06)^5
PV ≈ 74,726

Interpretation

A future obligation is worth less today because of the time value of money.

Limitation

Actual IAS 19 actuarial measurement usually includes: – salary growth, – mortality, – employee turnover, – retirement timing, – benefit formula terms.

So this simple formula is only a building block.

11.4 Projected Unit Credit method

For many defined benefit obligations, IAS 19 uses the projected unit credit method.

What it is

An actuarial attribution method that: 1. projects future benefit payments, 2. estimates how much benefit is earned for each period of service, 3. allocates that benefit to service periods, 4. discounts the allocated amount to present value.

Why it matters

It prevents crude accounting and gives a structured estimate of long-term promises.

Common mistakes

• applying a crude cash estimate instead of actuarial attribution,
• ignoring vesting or salary progression,
• failing to update assumptions.

Limitation

It requires actuarial expertise and can be complex for large plans.

12. Algorithms / Analytical Patterns / Decision Logic

IAS 19 is not a trading algorithm or chart-pattern concept. Its “algorithm” is really a decision framework.

12.1 Scope test

Decision logic	What it is	Why it matters	When to use it	Limitations
Is this an employee benefit?	Test whether the payment is consideration for employee service or termination	Determines whether IAS 19 applies	At the start of analysis	Borderline cases may require contract review

12.2 Classification test

Decision logic	What it is	Why it matters	When to use it	Limitations
Which category applies?	Decide between short-term, post-employment, other long-term, or termination	Category drives measurement and presentation	For every benefit type	Timing assumptions can change classification

12.3 Plan type test

Decision logic	What it is	Why it matters	When to use it	Limitations
DC or DB?	Determine whether obligation is limited to contributions or extends to promised outcomes	This is the core complexity split	For retirement and similar plans	Legal terms may look simple but contain guarantees

12.4 Measurement path

A useful practical sequence is:

1. Identify the benefit and related employees.
2. Determine whether IAS 19 applies or another standard applies.
3. Classify the benefit category.
4. For post-employment, determine DC or DB.
5. Measure liability/asset.
6. Decide what goes to profit or loss and what goes to OCI.
7. Prepare required disclosures.
8. Reassess assumptions at each reporting date.

12.5 Investor analysis pattern

Analysts often use a simple screen:

1. Read the employee benefit note.
2. Identify whether the company has DB exposure.
3. Compare net liability with equity, EBITDA, and market value.
4. Review discount rate and sensitivity analysis.
5. Check whether contributions are rising faster than operating cash flow.
6. Assess whether pension deficit behaves like debt-like risk.

12.6 Limitations of decision logic

• Complex plan terms may require legal interpretation.
• Local employment law may create obligations not obvious from payroll records.
• Some plans require actuarial support.
• Cross-border comparison is imperfect.

13. Regulatory / Government / Policy Context

13.1 IFRS and IAS framework

IAS 19 is part of the international financial reporting architecture used in many jurisdictions. It sets accounting requirements for employee benefits in IFRS-based financial statements.

13.2 Accounting standard relevance

IAS 19 affects: – recognition of liabilities, – expense reporting, – OCI presentation, – note disclosures, – audit evidence, – governance oversight.

13.3 Disclosure relevance

Entities applying IAS 19 usually need to disclose, especially for defined benefit plans: – description of plans, – amounts recognized in statements, – reconciliation of obligations and plan assets, – actuarial assumptions, – sensitivity analysis, – maturity profile or timing information, – asset allocation information.

13.4 Regulatory relevance for listed companies

Listed entities reporting under IFRS or adopted IFRS frameworks are often scrutinized on: – pension deficits, – changes in assumptions, – severance