Loading site navigation and page content
Updated By Ruan van Rensburg
Saudi companies that prepare IFRS financial statements generally need an IAS 19 actuarial valuation when their end-of-service benefit obligations are material. The valuation converts the benefit promised under Saudi labour law and employment contracts into a present-value accounting liability, using assumptions for salary growth, employee turnover, mortality and discount rates. It is not an EOSB calculator or a simple termination-value schedule: it is an audit-ready measurement of the defined benefit obligation, annual expense, remeasurements and disclosures required for financial reporting.
Lux Actuaries performs IAS 19 valuations for Saudi entities and multinational groups with employees in the Kingdom. This guide explains when a valuation is needed, how statutory EOSB differs from the IAS 19 liability, what information your actuary needs, which assumptions matter, and what an auditor-ready report should contain.
If you already know that you require a valuation, review our IAS 19 employee benefits valuation service or contact our team to scope the reporting date, employee data and audit timetable.
An actuarial valuation is normally relevant when an entity reports under IFRS or submits IFRS information to a parent company and has a material obligation for end-of-service benefits or other long-term employee benefits. The precise reporting requirement depends on the accounting framework applied by the entity, materiality and the terms of its benefit arrangements.
Common triggers include:
Saudi labour law determines the benefit employees are entitled to receive. IAS 19 determines how an entity measures and recognises that future obligation in its financial statements. Those are connected calculations, but they are not interchangeable.
| Question | Statutory or payroll EOSB calculation | IAS 19 actuarial valuation |
|---|---|---|
| Purpose | Estimate the benefit payable under the applicable labour-law and contractual formula at a particular date. | Measure the present value and accounting cost of benefits earned by employees for IFRS reporting. |
| Time horizon | Usually focuses on the amount payable if employment ended under a stated scenario. | Projects benefits to expected payment dates over the future service and exit pattern of the workforce. |
| Key inputs | Service, qualifying wage, benefit formula and reason for termination. | The statutory and contractual formula plus salary growth, turnover, mortality, retirement, discount rates and other assumptions. |
| Primary outputs | An employee-level benefit amount or payroll provision. | Defined benefit obligation, service cost, net interest, remeasurements, sensitivities, reconciliation and disclosure schedules. |
| Typical reviewer | Payroll, HR or legal teams. | Finance teams, external auditors, boards and group-reporting teams. |
The Saudi Ministry of Human Resources and Social Development publishes the official labour-law resources and EOSB guidance. Benefit calculations should reflect the law and contractual terms applicable at the reporting date. This article is accounting guidance, not legal advice.
A defensible valuation starts with the actual benefit promise. The actuary should document the Saudi statutory formula, the wage components included in the benefit basis, eligibility and vesting rules, termination and resignation provisions, retirement conditions, and any enhanced benefits provided by employment contracts or company policy.
IAS 19 requires the projected unit credit method for defined benefit obligations. In practical terms, the actuary attributes benefit to employee service, projects the amount expected to be paid, allows for the probability and timing of payment, and discounts the expected cash flows to the reporting date. The IFRS Foundation overview of IAS 19 explains the recognition and measurement principles for employee benefits.
The model should be calibrated to the entity and the Saudi environment rather than copied from a generic regional template. The most important assumptions normally include:
For a deeper discussion, see our guide to setting assumptions for an IAS 19 valuation of EOSB in Saudi Arabia.
General Organization for Social Insurance contributions and an employer’s EOSB obligation serve different purposes. GOSI participation does not automatically replace the need to measure an employer-sponsored end-of-service benefit under IAS 19. The valuation scope should identify each benefit separately and avoid double counting.
Clean employee data is usually the largest determinant of turnaround time. The data request should be agreed before extraction so that HR and finance teams do not spend time rebuilding the file after validation.
| Information | Typical fields | Why it matters |
|---|---|---|
| Employee identifiers | Stable employee number and valuation group or legal entity. | Supports reconciliation, duplicate testing and consistent roll-forward from the prior year. |
| Service data | Date of birth, date of joining, expected retirement date and employee status. | Determines age, past service, future service and expected payment timing. |
| Pay data | Basic salary and any allowance or wage component included in the benefit formula. | Defines the current benefit base and the amount to which salary growth is applied. |
| Movement data | New joiners, exits, transfers, settlements and benefit payments since the prior valuation. | Explains changes in the obligation and supports the IAS 19 reconciliation. |
| Benefit terms | Saudi statutory formula, contracts, policies and enhanced benefit arrangements. | Ensures the model measures the enforceable promise rather than a generic formula. |
| Financial reporting data | Opening balances, prior assumptions, reporting date, currency and disclosure format. | Connects the actuarial results to the financial statements and audit workpapers. |
Before modelling begins, the actuary should reconcile the employee count, total payroll and opening obligation to the employer’s records. Exceptions such as missing join dates, invalid salaries, duplicate employees and unusual service histories should be resolved or explicitly documented.
A good engagement is designed backwards from the reporting and audit deadline. The following stages keep responsibilities clear between the employer, actuary and auditor.
| Stage | Work performed | Main output |
|---|---|---|
| 1. Scope and data specification | Confirm entities, employee groups, benefits, reporting standard, currency, dates and audit requirements. | Agreed scope, timetable and data template. |
| 2. Data validation | Reconcile records, test completeness and investigate material exceptions. | Validated employee census and exception log. |
| 3. Assumption setting | Review economic data, company experience and prior-year assumptions. | Documented assumptions with rationale and sources. |
| 4. Actuarial modelling | Apply the benefit formula and projected unit credit method at employee level. | Defined benefit obligation and annual expense components. |
| 5. Reporting and disclosures | Prepare reconciliations, sensitivities, maturity information and disclosure schedules. | Actuarial report and financial-statement schedules. |
| 6. Audit support | Answer methodology and data questions and provide supporting calculations where appropriate. | Resolved audit queries and final signed results. |
The final report should be understandable without access to the actuarial model. It should state the benefits valued, data used, method, assumptions, results, movements, sensitivities, significant risks and limitations. Finance teams should also receive figures in a format that maps cleanly to their financial statements or group-reporting templates.
The provider should be able to explain both the actuarial mechanics and their financial-statement impact. Ask who will sign the work, whether the team has experience with Saudi EOSB arrangements, how assumptions are selected, how data is validated, what disclosure schedules are included, and whether audit queries are covered by the engagement.
Useful evidence includes professional actuarial qualifications, repeatable quality-control procedures, examples of auditor-ready reporting, capacity around year-end deadlines, and clear ownership of the engagement. Independence also matters: the valuation should be prepared to measure the obligation objectively, not to support the sale of another financial product.
Lux combines a dedicated employee-benefits team with regional experience across Saudi Arabia and the wider Middle East. Our work is structured around transparent assumptions, employee-level modelling, financial-statement reconciliations and direct audit support. Multi-country groups can use one coordinated process while retaining jurisdiction-specific benefit rules and assumptions.
Start by confirming the reporting date, legal entities, approximate employee count, benefit arrangements, prior-year valuation status and audit deadline. From there, the actuary can issue a focused data request and identify any areas that require early agreement with management or the auditor.
For broader background, read What is an actuarial valuation? A guide for Saudi businesses. To commission an audit-ready valuation, visit our IAS 19 valuation service or request a proposal.
Entities that prepare IFRS financial statements generally need to apply IAS 19 to material employee-benefit obligations. Whether a separate actuarial valuation is required depends on the benefit arrangement, reporting framework and materiality. Management and the external auditor should confirm the entity-specific requirement.
An EOSB calculation usually applies the benefit formula to current service and pay under a stated exit scenario. An IAS 19 valuation projects expected future benefits, allows for salary growth and employee exits, discounts expected payments, and produces the expense, liability, reconciliation and disclosures required for financial reporting.
Most entities obtain a valuation for each annual reporting date. An interim update may also be needed when there is a material workforce movement, benefit amendment, settlement, curtailment, acquisition or significant change in financial assumptions.
The core data normally includes employee identifiers, dates of birth and joining, qualifying salary components, employee status, entity or valuation group, benefit terms, and details of joiners, exits, transfers and payments since the previous valuation. Opening balances and prior-year assumptions are also needed for a reliable reconciliation.
IAS 19 sets a hierarchy for determining the discount rate and requires consistency with the currency and duration of the obligation. The actuary should document the market data, yield-curve approach, duration matching and any judgement applied so that management and the auditor can review the basis.
Not automatically. GOSI contributions and an employer’s end-of-service benefit promise are separate arrangements. The accounting assessment should identify each obligation and determine how it is classified and measured without double counting.
Yes. Headcount alone does not determine the requirement. A smaller entity may still have a material EOSB obligation because of employee tenure, salaries, benefit terms or the needs of its reporting group and auditor.
It should identify the benefits and population valued, data and validation performed, methodology, assumptions and sources, defined benefit obligation, expense components, reconciliation, sensitivity analysis, maturity information, significant risks and the disclosure schedules needed for the financial statements.
We combine global expertise with local on-the-ground presence to provide auditor-ready valuations and risk consulting. Explore our core services:
GCC insurers grew revenue and profit in H1 2026, but investment-led earnings, solvency deficits and accounting reclassifications reveal uneven capital resilience across the region.
Comparing actuarial consulting firms across Africa and the Middle East by team size, office footprint, service breadth, independence, resident workforce, qualifications, and multi-standard coverage. A framework for CFOs and Chief Actuaries evaluating external partners.
When hostilities between the US, Israel, and Iran escalated in late February, the fallout for pension funds landed much closer to home than the Strait of Hormuz.
