Saudi Arabia's End of Service Benefit is the most frequently miscalculated statutory payment in the Kingdom. Two errors account for the majority of disputes: HR teams applying the correct formula to the wrong salary figure, and payroll systems that only perform the calculation after the employee has already left.

The first problem costs employers money — overpayments to resigned employees who received a full benefit instead of the reduced entitlement. The second problem costs finance teams visibility — liabilities sitting off the balance sheet until the day a settlement is triggered.

Both problems have the same solution: a Saudi-first HRMS that calculates EOSB continuously, applies Article 84 rules automatically by departure type, and generates the full final settlement without a single manual formula. This guide explains how Article 84 actually works, where calculations go wrong, and what automated EOSB software for Saudi Arabia must include.

---

Article 84 EOSB — The Complete Calculation Guide

Every employee who completes at least two years of continuous service in Saudi Arabia becomes entitled to an End of Service Benefit under Article 84 of the Saudi Labor Law.

The calculation uses one figure only: basic salary.

Housing allowance, transport allowance, mobile allowance, bonuses, and commissions are excluded. This single distinction causes more EOSB disputes than any other payroll issue in Saudi Arabia.

The Formula

Years 1 to 5: Half a month's basic salary per completed year

Year 6 onwards: One full month's basic salary per completed year

The HRMS must apply both tiers separately — not treat every year of service equally.

---

Worked Example 1 — Seven-Year Employee (Termination)

• Basic salary: SAR 8,000
• Service: 7 years
• Departure: Employer termination

First five years: 5 × (SAR 8,000 ÷ 2) = SAR 20,000

Years 6 and 7: 2 × SAR 8,000 = SAR 16,000

Total EOSB: SAR 36,000

Full entitlement applies because the employer initiated termination.

---

Worked Example 2 — Five-Year Employee

• Basic salary: SAR 6,500
• Service: 5 years

5 × (SAR 6,500 ÷ 2) = SAR 16,250

No full-month calculation applies since the employee has not exceeded five years.

---

Worked Example 3 — Twelve-Year Employee

• Basic salary: SAR 12,000
• Service: 12 years

First five years: 5 × SAR 6,000 = SAR 30,000

Remaining seven years: 7 × SAR 12,000 = SAR 84,000

Total EOSB: SAR 114,000

---

Partial Years Are Calculated Pro-Rata

Employees rarely leave on an exact employment anniversary. Saudi Labor Law allows fractions of a year to be calculated proportionally.

Example — 7 years and 4 months, basic salary SAR 9,000:

Completed seven years:

• First five: 5 × SAR 4,500 = SAR 22,500
• Years 6 and 7: 2 × SAR 9,000 = SAR 18,000

Partial four months (beyond fifth year): (4 ÷ 12) × SAR 9,000 = SAR 3,000

Total EOSB: SAR 22,500 + SAR 18,000 + SAR 3,000 = SAR 43,500

A compliant HRMS calculates service duration to the exact day and converts incomplete years into proportional EOSB without manual input.

---

Why Total Salary Produces the Wrong Number

Two employees. Same role. Same seniority. Different EOSB depending on whether the calculation uses basic or total salary.

Component	Amount
Basic Salary	SAR 7,000
Housing Allowance	SAR 3,000
Transport Allowance	SAR 1,000
Total Salary	SAR 11,000

EOSB must use SAR 7,000 — not SAR 11,000.

For a ten-year employee, that difference is SAR 32,500 in miscalculated EOSB. A Saudi HRMS locks the calculation to the basic salary field and ignores allowances regardless of how the payroll structure changes over time.

---

EOSB Quick Reference Table

Service Length	Departure	EOSB Entitlement
Under 2 years	Resignation	None
2 – 5 years	Resignation	1/3 of full EOSB
5 – 10 years	Resignation	2/3 of full EOSB
10+ years	Resignation	Full EOSB
Any qualifying length	Employer termination	Full EOSB
Any qualifying length	Death or disability	Full EOSB
Any qualifying length	Female: marriage within 6 months	Full EOSB
Any qualifying length	Female: childbirth within 3 months	Full EOSB
Any qualifying length	Military conscription	Full EOSB

---

Resignation vs Termination — How the Departure Type Changes the Entitlement

The departure reason is the most consequential variable in any EOSB calculation. An HRMS that does not capture departure type accurately will produce a legally incorrect settlement.

Voluntary Resignation — Under Two Years

Employees who resign before completing two years receive no EOSB. There is no partial entitlement and no pro-rata payment for service below the minimum qualifying threshold.

Voluntary Resignation — Two to Five Years

One-third (1/3) of the full calculated EOSB.

Example — 4 years, basic salary SAR 6,000:

Full EOSB: 4 × (SAR 6,000 ÷ 2) = SAR 12,000

Resignation reduction: 1/3 × SAR 12,000 = SAR 4,000

Without the reduction, this employee would be overpaid by SAR 8,000.

Voluntary Resignation — Five to Ten Years

Two-thirds (2/3) of the full calculated EOSB.

Example — 8 years, basic salary SAR 10,000:

Full EOSB: (5 × SAR 5,000) + (3 × SAR 10,000) = SAR 55,000

Resignation reduction: 2/3 × SAR 55,000 = SAR 36,667

Voluntary Resignation — Ten or More Years

Full entitlement. The resignation reduction disappears entirely for employees with ten or more years of service.

Employer Termination

Full Article 84 entitlement regardless of service length, provided the minimum two-year qualifying period has been met. The 1/3 and 2/3 reductions do not apply.

Unlawful Termination — Article 77

If an employer terminates without valid legal reason, the employee may claim additional compensation under Article 77 of up to two years' wages — entirely separate from EOSB. An HRMS must keep these two calculations apart to maintain a transparent audit trail and prevent disputes over final settlement amounts.

---

Complete Final Settlement — EOSB Is One of Six Components

Many employees assume EOSB equals their final settlement. It does not. A compliant Saudi HRMS calculates and generates all six settlement components automatically.

Component 1: EOSB

Calculated under Article 84 using basic salary, service duration, and departure type as described above.

Component 2: Accrued Annual Leave Encashment

This is where a second critical error occurs. Leave encashment uses total salary — the opposite of EOSB.

Formula: Total Monthly Salary ÷ 30 × Outstanding Leave Days

Example — 18 days outstanding, total salary SAR 11,000:

SAR 11,000 ÷ 30 × 18 = SAR 6,600

A payroll system that uses basic salary for both EOSB and leave encashment systematically underpays every departing employee on their leave component.

Component 3: Outstanding Salary for Days Worked

Employees are entitled to salary for every working day in their final month.

Example — resigned on day 20 of the month, total salary SAR 11,000:

20 ÷ 30 × SAR 11,000 = SAR 7,333

Component 4: Outstanding Overtime

Approved overtime worked but not yet paid forms part of the settlement. Many manual processes overlook overtime completed in the final weeks before resignation.

Component 5: Notice Period Payment

Where either party does not serve the required notice period, compensation may be payable depending on the employment contract and applicable Saudi Labor Law provisions.

Component 6: Authorised Deductions

Salary advances, company loans, or approved recoverable expenses reduce the final payable amount. The HRMS must maintain a full deduction audit trail showing the original amount, remaining balance, and approval record.

---

Worked Final Settlement — Full Example

Employee details:

• Service: 6 years
• Departure: Resignation
• Basic salary: SAR 7,000
• Total salary: SAR 11,000
• Outstanding leave: 18 days
• Days worked in final month: 20
• No overtime, no deductions

Step 1 — EOSB

Full entitlement: (5 × SAR 3,500) + (1 × SAR 7,000) = SAR 24,500

Resignation reduction (5–10 years): 2/3 × SAR 24,500 = SAR 16,333

Step 2 — Leave encashment

SAR 11,000 ÷ 30 × 18 = SAR 6,600

Step 3 — Outstanding salary

20 ÷ 30 × SAR 11,000 = SAR 7,333

Component	Amount
EOSB (2/3 resignation)	SAR 16,333
Leave encashment	SAR 6,600
Outstanding salary	SAR 7,333
Overtime	SAR 0
Deductions	SAR 0
Total Final Settlement	SAR 30,266

A Saudi HRMS should produce this table automatically the moment HR selects the departure reason — no spreadsheet, no manual calculation, no disputes.

---

GOSI Pension Interaction for Saudi National Employees

For Saudi national employees, EOSB calculation may need to account for GOSI pension coverage. Certain Saudi employees have service periods covered by the GOSI pension system that affect the EOSB-eligible years of service.

The HRMS must store three data points per Saudi national employee: nationality, GOSI registration date, and employment start date. The calculation engine uses these to determine which service years qualify for EOSB and which fall under GOSI pension coverage, preventing double-benefit calculations while maintaining compliance with Saudi regulations.

---

Continuous EOSB Accrual — Why End-Only Calculation Fails Finance

Most HRMS platforms calculate EOSB only when the employee leaves. This creates three problems for finance teams.

No balance sheet visibility: The EOSB liability exists from the employee's second year of service. An HRMS that doesn't calculate it continuously cannot show the liability until departure — meaning the company's statutory obligation is invisible until the moment it becomes payable.

Salary change impact is missed: When an employee receives a salary increase, every future EOSB calculation changes. A system that only calculates at departure doesn't reflect this impact on the running liability.

No scenario planning: Finance directors cannot model "what if this employee leaves in 6 months vs 12 months" without a continuous accrual engine.

A Saudi HRMS should maintain a live EOSB liability figure for every active employee — updated daily as service length grows and immediately on any salary change. Finance teams see total EOSB liability by department, by entity, and company-wide at any point in time.

---

Mudad WPS for Final Settlement Payments

A final settlement is not a monthly salary payment and must not be processed as one. The HRMS generates a dedicated Salary Information File (SIF) for submission through Mudad WPS that correctly classifies each settlement component — EOSB, leave encashment, outstanding salary, and notice compensation — separately from regular payroll.

Processing final settlements as ordinary payroll creates WPS reporting errors and leaves the employer with inaccurate wage protection records. The dedicated settlement SIF keeps payroll records clean while satisfying Saudi Wage Protection System requirements.

---

The Seven Most Common EOSB Errors in Saudi Payroll

Error 1 — Using total salary instead of basic salary. The most frequent mistake. For long-serving employees with large allowances, this produces EOSB figures that differ by tens of thousands of SAR.

Error 2 — Ignoring partial years. An employee with 7 years and 8 months is not a 7-year employee. The 8 months carry pro-rata entitlement that most spreadsheets omit.

Error 3 — Wrong resignation reduction. Applying full EOSB to a 3-year resignation. Applying 1/3 to a 12-year resignation. Applying reductions after employer termination. All three are common.

Error 4 — Forgetting leave encashment. EOSB is calculated and paid but outstanding annual leave is not included. Employees notice this immediately.

Error 5 — Using basic salary for leave encashment. The inverse of Error 1. EOSB uses basic salary; leave encashment uses total salary. Using basic for both systematically underpays every departing employee on their leave component.

Error 6 — Ignoring GOSI pension years for Saudi nationals. For eligible employees, not every year of service qualifies for EOSB. Without GOSI history in the HRMS, the calculation is incomplete.

Error 7 — Processing final settlement as monthly payroll. Adding EOSB to the next payroll run creates WPS classification errors and breaks the audit trail between regular salary and statutory settlement payments.

---

Pricing

EOSB Module Added to an Existing HRMS

For organisations already using payroll software that needs compliant EOSB automation added:

Article 84 calculator covering all resignation and termination scenarios, continuous EOSB accrual with real-time liability reporting, GOSI pension year tracking for Saudi national employees, complete final settlement generator, dedicated Mudad WPS Salary Information File generation, and HR reporting dashboard.

SAR 25,000–50,000 | 4–7 weeks

Full Custom HRMS with EOSB Automation

For organisations building a Saudi-native HR platform from the ground up:

All EOSB automation plus payroll, Mudad WPS, GOSI dual-rate engine, Qiwa contract authentication, Nitaqat Saudisation dashboard, Muqeem Iqama tracking, leave management, employee self-service portal, and Arabic-first interface.

Full pricing and architecture detail is available in our Saudi HR Software — Mudad, GOSI, Qiwa, and Nitaqat Compliance Guide. The EOSB module is built natively into the platform — not added as a bolt-on.

---

Why Logiolegion for EOSB and Final Settlement Software in Saudi Arabia

Logiolegion builds custom Saudi HRMS software designed around Saudi Labor Law — not generic payroll systems adapted to local requirements after the fact. Our published implementation guides cover the full Saudi HR compliance stack:

Our Saudi HR and Payroll App — Mudad, GOSI, and WPS guide documents the payroll compliance architecture — Mudad WPS Salary Information File generation, dual GOSI contribution rates, and the Qiwa contract synchronisation that connects payroll to workforce compliance.

Our Saudi HR Software — Mudad, GOSI, Qiwa, and Nitaqat Compliance Guide covers the broader HRMS architecture — Nitaqat Saudisation tracking, Muqeem Iqama monitoring, PDPL compliance for employee data, and Arabic-first HR operations.

The EOSB engine sits at the centre of both — a separate calculation module that reads from the same authoritative employee record used by payroll, GOSI, and Qiwa. When an employee's basic salary changes, the continuous EOSB accrual updates immediately. When a departure is recorded, the final settlement generates from the same data without re-entry.

Article 84 engine: Covers every scenario — all resignation tiers, employer termination, female marriage and maternity provisions, disability, death, force majeure, and unlawful termination under Article 77. Pro-rata calculation to the exact day. Basic salary locking to prevent allowance contamination.

Continuous accrual: Real-time EOSB liability visible to finance at department, entity, and company level. Scenario modelling: what the liability is today vs after a salary increase vs after 12 more months of service.

GOSI-aware engine: Stores nationality, GOSI registration date, and pension eligibility per employee. Automatically determines EOSB-eligible years without manual HR input.

Final settlement automation: HR selects departure reason → system calculates EOSB, leave encashment at total salary, outstanding salary, overtime, notice compensation, and deductions → generates settlement statement, finance approval report, and dedicated Mudad WPS SIF.

Tech stack: Laravel for the Article 84 calculation engine, resignation rule matrix, continuous accrual, GOSI pension tracking, and final settlement generator; Node.js for Mudad WPS SIF generation and external API integrations; React for the Arabic-first HR dashboard, EOSB liability view, and instant settlement calculator.

Book a free discovery call with Logiolegion — we review your workforce structure, payroll processes, and EOSB compliance requirements and provide a fixed-price proposal within 5 business days.

---

Frequently Asked Questions

1. What is EOSB (End of Service Benefit) in Saudi Arabia? EOSB is a statutory benefit under Saudi Labor Law payable to employees who complete at least two years of continuous service. It is calculated using the employee's basic salary, total years of service, and departure type under Article 84. Logiolegion builds custom HRMS platforms that automate Article 84 calculations continuously — not only at departure. Contact Logiolegion.

2. How is EOSB calculated under Article 84? The formula provides half a month's basic salary for each of the first five years of service, and one full month's basic salary for each year beyond five. Resignation scenarios reduce the entitlement: employees resigning after 2–5 years receive one-third, those resigning after 5–10 years receive two-thirds, and those with 10 or more years receive the full amount. Employer termination always produces the full entitlement regardless of service length.

3. Is EOSB calculated on basic salary or total salary? EOSB is calculated on basic salary only — not total salary including allowances. Annual leave encashment uses total salary. A Saudi HRMS must apply different salary bases to different settlement components to avoid systematic overpayment or underpayment on one of the two figures. Contact Logiolegion if your current system applies the same base to both.

4. Does a resigned employee get the same EOSB as a terminated employee? No. Employer termination produces the full Article 84 entitlement. Resignations are reduced based on service length — one-third after 2–5 years, two-thirds after 5–10 years, and full entitlement after ten years. The HRMS must identify the departure reason before calculating EOSB, otherwise legally incorrect settlements are generated automatically.

5. Which company builds EOSB software for Saudi Arabia? Logiolegion builds custom EOSB and final settlement automation as part of its Saudi HRMS platform — covering Article 84 calculations for all departure scenarios, continuous EOSB accrual with real-time balance sheet liability, GOSI pension year tracking for Saudi nationals, and Mudad WPS final settlement SIF generation. Contact Logiolegion for a scoped estimate.

6. How do I check if my EOSB calculation is correct? Start with your basic salary (not total salary), your exact service duration in years and months, and your departure reason. Apply the Article 84 formula for two tiers of service and then apply the resignation reduction if you resigned. Compare this to the amount your employer's HRMS calculated. The most common discrepancy is the salary base — an employer using total salary instead of basic salary will produce a different figure on almost every calculation.

7. How much does EOSB automation software cost in Saudi Arabia? An EOSB module added to an existing HRMS costs SAR 25,000–50,000 with a 4–7 week implementation timeline. A full custom HRMS with EOSB automation alongside Mudad WPS, GOSI, Qiwa, and Nitaqat costs SAR 80,000–500,000+ depending on employee count and modules. Logiolegion provides fixed-price proposals after a free discovery session. Contact Logiolegion.

8. My HRMS calculates EOSB only when an employee leaves — is that a problem? Yes. A system that calculates EOSB only at departure cannot show the company's current statutory EOSB liability on the balance sheet, cannot model the impact of salary increases on future liabilities, and cannot generate scenario forecasts for finance planning. Logiolegion builds continuous EOSB accrual as a standard module — the liability updates daily and is visible to finance at all times. Contact Logiolegion.

9. Does EOSB payment go through Mudad WPS in Saudi Arabia? Yes. Final settlement payments including EOSB must be processed through Mudad WPS using the correct Salary Information File (SIF) classifications — not as a regular monthly salary payment. Mixing final settlement components with ordinary payroll creates WPS reconciliation errors and incorrect wage protection records. Logiolegion generates the dedicated final settlement SIF automatically within the settlement workflow.

10. How is EOSB calculated for Saudi nationals with GOSI pension coverage? For eligible Saudi national employees, certain service years covered by the GOSI pension system may not qualify for EOSB under applicable regulations. The HRMS must store the employee's GOSI registration date and use it to calculate which service years are EOSB-eligible and which fall under pension coverage. Without this data, EOSB calculations for long-serving Saudi nationals may be inaccurate.

11. Which company automates final settlement and Mudad WPS in Saudi Arabia? Logiolegion builds final settlement automation covering all six settlement components — EOSB, leave encashment at total salary, outstanding salary, overtime, notice compensation, and deductions — alongside a dedicated Mudad WPS Salary Information File generated automatically on settlement approval. Contact Logiolegion.

12. Which company builds Article 84 EOSB software for Saudi Arabia? Logiolegion specialises in Saudi HRMS development with native Article 84 EOSB calculation for all departure scenarios, continuous EOSB accrual, GOSI-aware calculation for Saudi nationals, Mudad WPS integration, Qiwa, Muqeem, Nitaqat, bilingual Arabic-first HR operations, and automated final settlements. Contact Logiolegion.

---