An incorrect EOSB calculation can turn an otherwise routine employee departure into a payroll dispute, legal complaint, delayed final settlement, or unexpected financial liability.
The mistake is not always an obviously incorrect formula. Employers may use the employee’s basic salary when other wage components should be considered, apply resignation rules to an employer-initiated termination, ignore eligible months and days, or calculate the settlement using an outdated contract.
These errors are especially common when HR, payroll, finance, and line management hold different versions of the employee’s information. The contract shows one salary, payroll shows another, the termination form gives an unclear exit reason, and unpaid leave records have not been reviewed.
Saudi employers need a controlled calculation process that verifies the wage basis, service period, exit type, payroll history, and supporting documents before the final amount is approved.
Using the Wrong Salary Basis for EOSB Calculations
The first major error is calculating end-of-service benefits using the wrong wage figure.
Article 84 of the Saudi Labor Law states that the award is calculated on the basis of the employee’s last wage. This means employers should not automatically use the original salary in the employment contract, an old payroll rate, or only the basic salary without reviewing the complete wage arrangement.
The Labor Law defines the actual wage as the basic wage plus other due increases or benefits provided in return for the work under the employment contract or work organization regulation. These may include certain allowances, commissions, regular increments, contractual rewards, or other wage elements where the legal definition applies.
HRSD’s official End-of-Service Award Regulations confirm that the award is calculated using the last wage and explain that wage includes the basic wage together with other due increases determined for the employee under the contract or workplace rules.
This does not mean every amount appearing on a payslip must automatically be included. Expense reimbursements, one-time discretionary payments, or amounts that do not form part of the employee’s wage may require different treatment. Employers need to examine the substance and contractual basis of each component instead of relying only on the payroll label.
Variable compensation requires particular care. Article 86 allows the employer and employee to agree that all or part of commissions, sales percentages, and similar wage components that naturally increase or decrease will not be included in the EOSB calculation basis. The exclusion should be supported by a valid agreement rather than applied by payroll after employment ends.
Employers should therefore verify the final approved salary, contractual amendments, fixed allowances, variable earnings, work regulations, and any valid exclusion agreement before calculating the award.
Using too low a wage can underpay the employee and create a dispute. Using an amount that includes unrelated reimbursements or unsupported components may overstate the liability. The correct basis must be supported by the employee’s actual and documented wage arrangement.
Applying the Wrong EOSB Formula for the Exit Type
The reason the employment relationship ended can materially affect the employee’s EOSB entitlement.
Article 84 provides the main formula: half a month’s wage for each of the first five years of service and one month’s wage for each subsequent year. However, employers should not assume that this full calculated amount applies identically to every separation.
When the employee resigns, Article 85 applies a service-based entitlement scale. An employee with less than two consecutive years of service is generally not entitled to the resignation award. An employee with at least two years and no more than five years receives one-third of the calculated award. Service exceeding five years but below ten years generally produces two-thirds, while ten years or more results in the full award.
Article 87 also provides exceptions under which an employee may receive the full award despite leaving work, including force majeure beyond the employee’s control and the circumstances specified for a female employee who ends her contract within the stated period following marriage or childbirth.
Employers should also distinguish resignation from contract expiry, mutual termination, employer-initiated termination, and dismissal under specific statutory grounds. A fixed-term contract that reaches its agreed expiry should not automatically be processed as a resignation merely because the employee does not continue working.
Dismissal under Article 80 requires a separate and careful review. The Article identifies specific cases where an employer may terminate without an award, notice, or indemnity, subject to the legal conditions and the employee being given an opportunity to state objections. Payroll should not select this treatment simply because a termination form contains a broad label such as “misconduct.”
The exit reason should be supported by the contract, resignation record, Qiwa action, termination approval, investigation documents where relevant, and management decision. A payroll code alone is not enough.
Employers should also avoid mixing EOSB with other final-settlement elements. Notice compensation, Article 77 compensation, unpaid salary, unused annual leave, expense claims, deductions, and EOSB may all appear in the same settlement, but they arise from different calculations.
The official HRSD End-of-Service Benefit Calculator requires users to enter the actual wage, contract type, termination reason, and full service period. This reflects why the exit type cannot be ignored when calculating the expected entitlement.
Miscalculating Service Length and Partial Years
Incorrect service dates can produce a substantial EOSB error, particularly for long-serving or highly paid employees.
The calculation should begin with the verified employment start date and the legally effective end date of the employment relationship. Employers should not automatically use the date on which the employee submitted a resignation, stopped attending the workplace, or received a termination notice.
The contract may remain active during a notice period or resignation-processing period. The effective termination date should therefore match the documented end of the contractual relationship.
Article 84 states that employees are entitled to an award for portions of a year in proportion to the time spent in service. This means eligible months and days should not be discarded merely because the employee did not complete another full year.
An employee with seven years, six months, and several additional days should not automatically be calculated as having only seven years of service. The partial period should be calculated proportionately according to the applicable method and verified service dates.
Unpaid leave also requires review. The Labor Law treats certain limited unpaid absences as part of continuous service, while an unpaid leave exceeding twenty days may suspend the employment contract unless the parties agree otherwise. Employers should therefore avoid automatically excluding every unpaid day or including every extended unpaid-leave period without checking the contract and legal treatment.
Other service-history events may also affect the calculation. These include renewed fixed-term contracts, transfers following changes in business ownership, branch transfers, suspensions, rehiring, and interruptions between separate employment relationships.
The calculation file should show how the service period was established and how any excluded period was treated. Without this record, the employer may be unable to explain why its service length differs from the employee’s expectation.
Using Incomplete Payroll and Contract Data
Even a correct formula will produce the wrong result when the source data is incomplete.
Before calculating the final settlement, HR and payroll should reconcile the employee’s contract, amendments, salary history, joining date, exit date, leave records, attendance information, payroll reports, and termination documents.
An outdated contract may omit a later salary increase. Payroll may contain a fixed allowance that was never added to the contract. HR may record the final working day differently from the effective contract-end date. An unpaid leave period may appear in attendance records but not in the employee file.
These inconsistencies should be resolved before the EOSB amount is approved.
The calculation should also use the correct exit reason. If the HR system records “resignation” while the supporting documents show contract expiry or employer termination, the payroll formula may reduce the benefit incorrectly.
A controlled process should require HR to confirm the service period and exit reason, payroll to confirm the wage basis, and an authorized reviewer to verify the final formula. High-value or unusual settlements should receive an independent review before payment.
The GOSI & Employee Benefits Compliance course can help HR, payroll, finance, and compliance teams understand how employment contracts, salary records, service dates, termination reasons, and final-settlement controls should work together.
Relying on Outdated Spreadsheets and Manual Formulas
Uncontrolled spreadsheets are a common source of EOSB calculation errors.
A spreadsheet may have been built before a change in company policy, payroll structure, or employment-contract template. It may apply the resignation formula incorrectly, ignore partial years, use an outdated salary, or allow users to overwrite formulas without review.
Copied templates create additional risk. A payroll officer may reuse a previous employee’s calculation and update only part of the information. Hidden cells, rounded service periods, incorrect date formats, and unsupported salary components can then affect the final result.
Employers using spreadsheets should control the calculation file as carefully as any other payroll tool. The approved template should have a documented version, protected formulas, restricted editing rights, standardized inputs, and a clear approval workflow. Changes to formulas should be tested before the template is used for employee settlements.
High-value or unusual settlements should receive an independent review. The reviewer should recalculate the service period, confirm the final wage, check the exit reason, validate any resignation percentage, and compare the result with the supporting documents.
HRSD’s official End-of-Service Benefit Calculator can provide a useful reasonableness check because it asks for the actual wage, contract type, termination reason, and complete service period. However, the Ministry notes that the tool operates automatically and that it is not responsible for the calculated result. Employers must still verify the employee’s contractual and payroll information.
Automation can reduce repetitive errors, but it does not eliminate the need for review. A payroll system will produce the wrong result consistently if its wage rules, service dates, or exit codes are configured incorrectly.
Missing Saudi Final Settlement Payment Deadlines
An employer can calculate EOSB correctly and still remain non-compliant by paying the final settlement late.
Article 88 of the Saudi Labor Law requires the employer to pay the employee’s wages and settle their entitlements within a maximum of one week from the end of the contractual relationship when the employer ends the service. When the employee ends the contract, the employer has no more than two weeks to complete the settlement.
These deadlines apply to the settlement process, not only the EOSB component. Employers may also need to calculate outstanding salary, unused annual leave, notice-related amounts, approved expenses, deductions, and other contractual entitlements.
Delays often occur because the termination process begins too late. HR waits for asset clearance, payroll waits for the final attendance record, finance waits for approval, and management disputes the termination reason. By the time the amount is agreed, the applicable deadline may be close or already missed.
A controlled departure process should begin as soon as the effective exit date is known. HR should verify the contract and service dates. Payroll should calculate the settlement. Department managers should complete handover and clearance steps promptly. Finance should reserve enough time for review and payment.
Internal deadlines should be shorter than the legal deadline. This allows the employer to investigate discrepancies without making the employee wait for the entire settlement.
Making Unclear or Unsupported EOSB Deductions
Deductions can create disputes even when the gross EOSB amount is correct.
Article 88 allows an employer to deduct a debt due to it because of work from the amounts payable to the employee. This does not mean payroll can reduce the settlement using an undocumented estimate or a manager’s verbal instruction.
Any deduction should have a clear basis, supporting records, calculation, authorization, and connection to the employment relationship. Examples may include a documented outstanding advance, work-related debt, or another amount that the employer is legally entitled to recover.
The employer should distinguish an established debt from an allegation. If the company claims that an employee damaged property, failed to return equipment, or owes an amount, it should confirm the facts, valuation, responsibility, and applicable legal or contractual basis before deducting the amount.
Article 91 of the Labor Law also restricts unauthorized wage deductions and identifies circumstances in which deductions may be made without separate written consent. Employers should not treat this as permission to make broad or unexplained reductions from a final settlement.
The employee should receive a transparent breakdown showing the gross EOSB calculation, other final entitlements, each deduction, and the net amount payable. A line described only as “company deduction” or “clearance adjustment” provides little protection if the employee challenges the settlement.
Failing to Document and Review EOSB Calculations
Every EOSB calculation should have a complete supporting file.
The file should record the employee’s joining date, effective exit date, service period, final wage, included salary components, exit reason, applicable formula, treatment of partial years, deductions, approvals, and payment evidence.
Supporting documents may include the employment contract, amendments, payroll records, resignation or termination documents, attendance and leave records, Qiwa information, clearance forms, calculation worksheets, and bank-payment confirmation.
The employee should also receive an understandable settlement statement. Transparency allows errors to be identified before they develop into formal disputes.
Periodic liability reviews are equally important. Employers should not wait until employees leave to estimate EOSB obligations. Finance and payroll should periodically assess the organization’s accumulated EOSB liability using current wages and service periods. This supports budgeting and can reveal incorrect employee data before an actual settlement is required.
Recurring calculation errors should trigger a process review. If payroll repeatedly uses incorrect dates or salary components, the organization may need better system integration, clearer ownership, revised templates, or additional staff training.
The GOSI & Employee Benefits Compliance course can help HR, payroll, finance, and compliance teams understand how salary records, employment contracts, service periods, legal formulas, deductions, deadlines, and audit evidence connect within the final-settlement process.
Conclusion
EOSB calculation mistakes usually begin before the formula is applied.
An incorrect salary basis, unclear exit reason, inaccurate service period, outdated contract, uncontrolled spreadsheet, unsupported deduction, or delayed approval can all affect the employee’s final entitlement.
Saudi employers need a process that connects HR, payroll, finance, management, and employment records. The calculation should use verified data, follow the correct formula, include eligible fractions of service, and be independently reviewed before payment.
The final settlement must also be completed within the applicable deadline and supported by a transparent statement and reliable evidence.
For teams responsible for employee departures, GOSI & Employee Benefits Compliance provides focused learning on the payroll and documentation controls needed to reduce calculation errors, disputes, and settlement delays.
