Understanding EOSB Compliance: Legal vs. Accounting Roles

Why this topic matters for companies preparing financial statements and applying IAS 19

For finance directors, payroll managers, HR heads and auditors, distinguishing legal obligations from accounting obligations is essential to ensure EOSB compliance, avoid penalties, and present accurate financial statements. Misclassification affects profit or loss, the balance sheet, tax planning and stakeholder confidence. Many organisations also confuse “statutory payables” with the actuarial liabilities required under IAS 19 — the consequence can be inadequate disclosures or unexpected cash calls.

Early-stage work on EOSB compliance helps organisations reduce audit friction, strengthen internal controls, and explain movements in liabilities (Annual Movement of Liabilities) to investors and boards. For an understanding of how awareness of these issues drives policy change and stakeholder communication, see our article on EOSB awareness.

Core concept: legal vs accounting EOSB obligations (definition, components, examples)

Definitions

Legal obligation: a contractual or statutory requirement obliging the employer to pay a defined amount when employment terminates. This is enforceable in a court or by labour authorities.

Accounting obligation (IAS 19): the present value of future benefits that the employer is obliged to provide as a result of past service. Recognition, measurement and disclosure follow IAS 19 even where the legal entitlement differs or where obligations are conditional.

Key components

• Plan rules and end-of-service policies — how EOSB is calculated in practice.
• Statutory law and collective agreements — source of legal obligations.
• Actuarial assumptions — discount rate, salary growth, turnover, mortality.
• Accounting treatment — recognition of defined benefit obligations, remeasurements, and Employee Benefits Disclosures.

Clear example: one employee, two views

Assume Employee A earns 10,000 monthly. Company policy: 1 month EOSB per year for first 5 years, then 2 months per year thereafter. Employee A has 8 years’ service and voluntary termination occurs.

Legal payable on termination (simple): first 5 years = 5 months; next 3 years = 6 months; total payable = 11 months x 10,000 = 110,000 (paid now).

IAS 19 perspective at previous year-end: the company must measure present value of expected future EOSB for all active employees. That may include probability-weighted assumptions about when someone leaves, salary progression (linking salaries and allowances), discounting to present value, and remeasurement patterns. The IAS 19 obligation might be larger or smaller than the legal payable expected at a point in time.

Actuarial reports reconcile legal formulas and IAS 19 assumptions so accountants can justify recorded liabilities and the Annual Movement of Liabilities shown in notes.

Practical use cases and scenarios for this audience

Scenario 1 — Routine year-end measurement

A UAE-based mid-size manufacturer runs annual actuarial valuations to support IAS 19 disclosures. The valuation reconciles the legal EOSB formula with the expected economic obligation across the workforce, and produces sensitivity analysis on discount rate changes. For practical guidance on common problems encountered during valuations, review typical EOSB challenges companies face.

Scenario 2 — Restructuring or mass termination

In a restructuring, legal payouts are immediate. Accounting may require recognising termination benefits earlier or reclassifying liabilities from actuarial to short-term, depending on the terms. This is when clear end-of-service policies, documented assumptions, and HR-Accounting coordination are critical.

Scenario 3 — Multi-jurisdiction workforce

Different labor laws create mixed legal obligations. Actuarial models must disaggregate by jurisdiction and link local salary and allowance patterns. Implementation often uncovers hidden inconsistencies between contracts and practice — see our notes on EOSB implementation challenges.

Scenario 4 — Benefits not legally required but consistently paid

If a company habitually pays a termination supplement without a contractual obligation, IAS 19 may require recognition if past practice creates a constructive obligation. Such cases are accounting obligations but could be argued as legally non-binding; documentation and governance are decisive.

Impact on decisions, performance, or outcomes

Understanding legal versus accounting duties changes corporate decisions in several ways:

• Profitability: actuarial remeasurements hit OCI or profit and loss depending on plan type, affecting reported profits.
• Liquidity planning: legal payouts drive immediate cash needs; actuarial liabilities inform longer-term funding strategies.
• Talent and retention: disclosed EOSB obligations influence perceived employee value and can be a component of compensation strategy — read about how EOSB affects hiring and retention in our piece on EOSB & talent attraction.
• Auditability: strong actuarial reports and clear Employee Benefits Disclosures reduce audit adjustments and accelerate sign-off.

Robust EOSB compliance also supports stakeholder confidence, reduces the risk of regulatory scrutiny, and makes cost projections more accurate when linking salaries and allowances across benefit calculations.

Common mistakes and how to avoid them

1. Confusing statutory payout with IAS 19 obligation. Remedy: maintain separate schedules — legal payable schedule and actuarial measurement with documented assumptions.
2. Using incorrect discount rates or salary growth. Remedy: adopt rates consistent with IAS 19 guidance and the entity’s currency and duration profile; disclose sensitivity analysis.
3. Poor documentation of assumptions and policy changes. Remedy: formal minutes approving assumptions and copies of actuarial reports to auditors.
4. Failing to disclose Annual Movement of Liabilities. Remedy: reconcile opening and closing balances with current service cost, interest, contributions, remeasurements and settlements; sample disclosure guidance appears in our EOSB disclosure example.
5. Ignoring governance and segregation of duties in HR. Remedy: implement controls for salary changes, allowance linkage and termination approvals; see guidance on improving EOSB supervision.
6. Over-reliance on a single actuarial scenario. Remedy: present multi-scenario sensitivity analysis to demonstrate range and limitations — understand model EOSB limitations and disclose them.

Practical, actionable tips and checklists

Before the actuarial valuation — data & controls

• Gather employee-level data: start date, salary history, average allowances, contract terms, termination outcomes.
• Reconcile payroll and HR lists to the general ledger; resolve unmatched records (>1% headcount triggers inquiry).
• Document end-of-service policies and any discretionary practices affecting payouts (e.g., service awards, severance top-ups).
• Set up Internal Controls for HR: dual approval for terminations, independent review of salary increases, and periodic payroll audits.

During the actuarial report — assumptions and outputs

• Agree discount rate methodology, salary growth (linking salaries and allowances), and turnover assumptions with finance and auditors.
• Request sensitivity analysis on discount rate ±1%, salary growth ±1%, and turnover ±10%.
• Obtain a reconciliation for Annual Movement of Liabilities showing current service cost, past service cost, interest cost, remeasurements and benefits paid.

After the actuarial report — accounting & disclosures

• Record journal entries for service cost and interest cost per IAS 19; post remeasurements to OCI or P&L according to guidance.
• Include Employee Benefits Disclosures with narrative on key assumptions, sensitivity analysis, and the Annual Movement of Liabilities table.
• Maintain an issues log for any dataset limitations or model assumptions, and update controls to close gaps before the next valuation.

Example checklist (pre-financial close)

1. Receive actuarial report at least 4 weeks before close.
2. Finance to reconcile actuarial opening balance to previous financial statements.
3. HR to confirm any policy changes affecting EOSB during the year.
4. Audit committee to review major assumption changes and sensitivity analysis.
5. Publish Employee Benefits Disclosures consistent with the actuarial outputs and IAS 19 requirements; further guidance on disclosure specifics is in our IAS 19 disclosures article.

KPIs / success metrics

• Timeliness of actuarial deliverable: actuarial report provided ≥4 weeks before financial close.
• Data completeness: <90% data reconciliation exceptions resolved pre-valuation.
• Disclosure accuracy: zero audit adjustments to Employee Benefits Disclosures in the previous two audits.
• Liability volatility: year-on-year change in actuarial DBO explained ≥95% by documented drivers (service cost, interest, remeasurements).
• Control effectiveness: percentage of payroll/termination transactions reviewed under Internal Controls for HR (target ≥95%).
• Sensitivity coverage: present analysis for at least three key assumptions (discount rate, salary growth, turnover).

FAQ

Reference pillar article

This article is part of a content cluster on labor laws and EOSB. Read the pillar article: The Ultimate Guide: Labor laws and their impact on EOSB calculation in Saudi Arabia – key provisions of the Saudi Labor Law on end‑of‑service and how they connect to IAS 19.