Why Standardization Matters
Imagine two employees with the same salary, the same hire date, and the same termination date.
Now imagine two different companies calculating two different End of Service (EOS) benefits for those employees.
Surprisingly, until recently, this was entirely possible.
The difference wasn't the Saudi Labor Law—it was how the employee's service period was calculated. Some organizations based their calculations on actual calendar days (365/366 days), others adopted a 360-day year, while many implemented customer-specific calculation logic to satisfy their business requirements.
SAP Payroll was intentionally designed to provide this flexibility, allowing organizations to configure the calculation methodology that best suited their needs. While this approach served customers well for many years, it also meant that organizations often relied on customized configurations to achieve their desired calculation method.
To provide a more consistent and compliant approach, SAP now delivers a standard enhancement that adopts the 360-day service period calculation. This enables customers to move away from customer-specific implementations and benefit from a standardized solution that is easier to maintain, easier to implement, and consistently applied across SAP Payroll.
This enhancement is available through SAP Note 3769652 – KSA End of Service Based on 30/360 Days, which contains the required corrections and implementation instructions.
Understanding the Legal Framework
The Saudi Labor Law distinguishes between two primary End of Service scenarios, each with its own calculation methodology.
Employee Resignation – Article 85
When an employee resigns, the End of Service entitlement depends on the employee's completed years of service. Rather than maintaining custom logic, SAP now provides a standard configuration that automatically applies the correct entitlement based on the employee's service period.
The standard configuration supports the following entitlement rules:
| Completed Service | EOS Entitlement |
| Less than 2 years | No entitlement |
| 2 to 5 years | One-third of the calculated EOS benefit |
| More than 5 up to 10 years | Two-thirds of the calculated EOS benefit |
| 10 years and above | Full EOS benefit |
Employer Termination or End of Contract – Article 84
When employment ends due to termination or contract completion, a different calculation applies. Under Article 84, the employee is entitled to the full End of Service Benefit based on the statutory formula.
SAP applies the calculation as follows:
- Half a month's wage for each of the first five years of service.
- One month's wage for each additional year thereafter.
With these two standard configurations, SAP Payroll can determine the appropriate calculation based on the employee's termination reason without requiring additional custom development.
Let's See the Difference
Configuration is only one part of the story. The real question is:
Does the calculation behave as expected?
To answer that, let's look at a few practical examples.
Example 1 – Less Than Two Years of Service
An employee resigns one day before completing two years of service.
Expected Result
No End of Service Benefit is payable.
SAP Payroll correctly identifies that the employee has not completed the minimum service period required under Article 85.
Example 2 – Exactly Five Years of Service
The employee resigns after completing exactly five years of service.
Expected Result
- The employee receives one-third of the calculated End of Service Benefit.
- The service period is calculated using the standardized 360-day methodology.
Example 3 – Five Years and One Day
Sometimes, a single day changes everything.
Once the employee completes more than five years of service, the entitlement changes from one-third to two-thirds of the calculated End of Service Benefit.
This example demonstrates how the enhancement correctly handles legal boundary conditions.
Example 4 – Ten Years of Service
After completing ten years of service, the employee becomes entitled to the full End of Service Benefit.
SAP Payroll automatically applies the appropriate calculation based on the completed service period.
When Unpaid Leave Impacts the EOS Calculation
Service duration is influenced not only by hire and termination dates, but also by unpaid leave.
According to Saudi Labor Law, the first 20 calendar days of unpaid leave continue to count towards the employee's EOS service period. Any unpaid leave exceeding 20 calendar days, whether consecutive or non-consecutive, must be excluded from the EOS service calculation.
Business Scenario
An employee has 30 calendar days of unpaid leave recorded during the service period.
Expected Result
The first 20 calendar days of unpaid leave are included in the employee's EOS service period.
Any unpaid leave exceeding 20 calendar days is excluded from the EOS service calculation.
In this scenario:
- 30 calendar days of unpaid leave are recorded.
- 20 days are counted towards the employee's EOS service period.
- 10 days are deducted from the employee's EOS service period.
- The employee's EOS service years and gratuity amount are reduced accordingly.
- The payroll results reflect the adjusted EOS calculation automatically.
The payroll log clearly demonstrates this behavior:
- Wage Type /846: records the total unpaid leave.
- Wage Type /847: records the unpaid leave excluded from the EOS service calculation.
- Wage Type /675: displays the adjusted EOS service years.
- Wage Type /650: reflects the recalculated gratuity amount based on the adjusted service period.
Confidence Through Validation
The examples above represent only a small subset of the validation performed during development.
To ensure complete alignment with the standardized calculation methodology, SAP validated the solution across a comprehensive set of scenarios, including:
- Service periods below the legal thresholds
- Exact legal boundary conditions (2, 5, and 10 years)
- Boundary transitions (for example, 5 years and 1 day)
- Random service durations
- Resignation scenarios
- Termination scenarios
A detailed validation document containing all tested scenarios is attached to this blog for customers and partners who would like to reproduce the tests in their own systems.
Conclusion
The move to a standardized 360-day service period calculation represents an important step toward simplifying End of Service Benefit calculations in Saudi Arabia.
By replacing customer-specific calculation approaches with a standard SAP solution, organizations can reduce implementation complexity, minimize custom development, and adopt a consistent calculation methodology that is easier to maintain over time.
Whether the employee leaves through resignation or termination, SAP Payroll now provides a standard approach that helps customers implement End of Service calculations with greater confidence, consistency, and simplicity.
Stay Updated
To stay informed about upcoming updates, enhancements, and discussions related to this topic, we recommend visiting the MENA SAP User Group space, where we will be sharing the latest developments and guidance
Source link
