Chat on WhatsApp
Book a Demo →
← All articles
Payroll

Gratuity and End-of-Service Pay Across the GCC: How the Formulas Actually Differ

Every GCC country requires end-of-service gratuity, but the formulas, caps, and eligibility rules are different in each one. Getting this wrong is one of the most common and most expensive payroll mistakes multinational employers make.

By AmalOps Editorial Team | HR, Payroll & Business Technology·10 min read·March 5, 2026
Key takeaways
  • End-of-service is a liability that accrues from month one, not a calculation performed at exit, and should be reconciled to the finance provision monthly.
  • Four variables differ by market: the salary base, service bands, treatment of resignation versus termination, and interaction with social insurance.
  • Pension contributions do not discharge the end-of-service obligation, and assuming they do leaves an unprovisioned liability.
  • Common errors are wrong service dates from migrated data, inconsistent unpaid-leave treatment, retroactive salary changes, and transfers processed as termination and rehire.
  • Verify current rules per jurisdiction before relying on any calculation, as provisions are periodically amended.

End-of-service gratuity is one of the most legally sensitive calculations in GCC payroll, and one of the easiest to get wrong when a company operates across more than one country. The underlying principle is similar everywhere: employees who complete a minimum period of continuous service are entitled to a lump-sum payment when their employment ends, calculated against their length of service and final salary. But the actual formulas, the caps, the treatment of unlimited versus limited contracts, and what counts as "salary" for the purpose of the calculation, all differ meaningfully from one country to the next.

United Arab Emirates

Under UAE labour law, gratuity is calculated based on the employee's basic salary (not total salary including allowances) and length of service. Employees who complete at least one year of continuous service are entitled to gratuity calculated as 21 days of basic salary per year for the first five years of service, and 30 days of basic salary per year for each year beyond that. The total gratuity payment is generally capped at two years' worth of total salary.

Saudi Arabia

Saudi Arabia's formula is structured differently: employees receive half a month's wage for each of the first five years of service, and a full month's wage for each year after that. Resignation versus termination also matters more in Saudi Arabia than in some neighbouring markets: an employee who resigns before completing a certain length of service may receive a reduced proportion of the full gratuity entitlement, rather than the full amount.

Qatar

Qatar's Labour Law entitles employees to a minimum of three weeks' basic wage for each year of service, for employees who have completed at least one year of continuous employment. Employers can contractually offer more generous terms, but three weeks per year is the statutory floor.

Bahrain

Bahrain applies half a month's wage for each of the first three years of service, and one month's wage for each year after that, calculated against the employee's most recent wage. Bahrain also has specific rules around the Social Insurance Organisation (SIO) that interact with the end-of-service calculation for GCC nationals versus expatriate employees.

Oman

Oman's end-of-service benefit follows a similar tiered structure: 15 days' basic wage for each of the first three years, and one month's wage for each subsequent year, again calculated on basic wage at the time of termination.

Kuwait

Kuwait's formula is structured as 15 days' wage for each of the first five years of service, and one month's wage for each year after that, with the total entitlement capped based on the employee's total years of service. An employee who resigns after between three and five years of service, for example, may only be entitled to a proportion of the full gratuity, rather than the full statutory formula.

The Common Mistakes

  • Using total salary (including housing or transport allowance) instead of basic salary where the law specifies basic salary only.
  • Applying the wrong tiered rate for years of service beyond the first threshold.
  • Failing to adjust the calculation for resignation versus termination, which changes the entitlement in several of these markets.
  • Manually recalculating gratuity in a spreadsheet for each employee at offboarding time, rather than having it tracked and accruing automatically from day one of employment.
  • Applying one country's formula across an entire multi-entity group by mistake, particularly when payroll is centralised.

Why This Matters Beyond Compliance

Gratuity disputes are also one of the most common triggers for labour complaints across the GCC. An employee who receives a final settlement that does not match their own calculation, even if the discrepancy is a genuine formula error rather than intentional underpayment, can escalate the matter through the relevant labour ministry, which creates reputational and administrative cost well beyond the value of the disputed amount itself.

How AmalOps Handles Multi-Country Gratuity

AmalOps applies the correct end-of-service formula automatically per country and contract type the moment an offboarding workflow begins, factoring in basic salary, tenure, resignation versus termination status, and any applicable deductions, with no manual spreadsheet calculation required.

The Bottom Line

Why end-of-service is a balance-sheet problem, not a payroll one

The most common structural error we encounter is treating end-of-service as something calculated when an employee leaves. It is a liability that accrues from the first month of service, and it belongs on the balance sheet whether or not anyone has computed it.

The consequence of the exit-time approach is that the organisation carries an unrecognised and growing obligation. A group with several hundred long-serving employees can be understating a material provision, and the gap is typically discovered during an audit or a due-diligence exercise rather than in the ordinary course of business. Accruing monthly, with the basis documented and reconciled to the finance provision, converts a surprise into a managed number.

The variables that differ between markets

Although each GCC state provides for a terminal benefit, the mechanics differ enough that a single formula applied across a group will be wrong in most of it. Four variables account for nearly all of the divergence.

  • The salary base. Some jurisdictions compute on basic wage, others on a broader definition. Because basic salary is frequently around half of a GCC package, this single choice can double or halve the liability.
  • Service bands. Entitlement commonly steps up after a threshold number of years, and both the threshold and the rate above it vary by market.
  • Resignation versus termination. Several jurisdictions reduce or qualify entitlement where the employee resigns, and the treatment of notice periods differs.
  • Interaction with social insurance. Where a national pension scheme applies, as with GPSSA in the UAE or GOSI in Saudi Arabia, the end-of-service obligation sits alongside it rather than being discharged by it.

The last point deserves emphasis because it is a costly misunderstanding. An employer assuming that pension contributions satisfy the end-of-service obligation for national employees is carrying an unprovisioned liability.

Where calculations go wrong in practice

Beyond jurisdictional differences, the errors we find during implementation cluster in a handful of places, and none of them are arithmetic failures.

Service length computed from the wrong date. Mixed date formats in migrated data silently corrupt service length, which flows directly into entitlement. This is one of the reasons migration discipline matters beyond the project itself.

Unpaid leave treated inconsistently. Whether an unpaid period interrupts or merely pauses service affects the calculation, and organisations frequently have no documented position.

Salary revisions applied retroactively. An increase backdated several months changes accrual for that period. Systems that recalculate silently produce a movement nobody can explain at year-end.

Transfers between group entities. Where a transfer is processed as a termination and rehire, service resets and the employee loses accrued entitlement, which is both a compliance exposure and a dispute waiting to happen.

The controls worth putting in place

Four controls address most of the risk, and none of them require sophisticated technology.

  • Accrue monthly rather than computing at exit, with the basis per entity documented in writing
  • Reconcile the system-calculated accrual to the finance provision every month, not every year
  • Model both resignation and termination scenarios so the exposure range is known in advance
  • Preserve service history on inter-entity transfers rather than terminating and rehiring

Where AI adds value here is narrow but real: accrual movements inconsistent with service progression are exactly the pattern an anomaly scan detects, as covered in AI anomaly detection in payroll. A retroactive salary change that quietly shifted a provision is visible in comparison against history even when every individual record is internally valid.

A note on obtaining advice

End-of-service provisions are amended periodically in every GCC market, and the treatment of specific circumstances, particularly around resignation, fixed-term contracts, and summary dismissal, turns on facts. The guidance here describes the structure of the obligation and where employers commonly go wrong. It is not a substitute for professional advice on a specific case, and you should verify the current position for each jurisdiction in which you operate before relying on a calculation.

What to verify in your own system

A short diagnostic will tell you whether your end-of-service handling is sound. Can you produce the total accrued liability by entity today, without a manual calculation? Does that figure reconcile to the provision finance reports? Is the salary base used for accrual documented per entity, and does it match the contracts? And does an inter-entity transfer preserve service history?

If any answer is no, the exposure is likely larger than the effort required to fix it. Send us a summary of your entity structure and we will identify where the accrual is most likely to be wrong.

End-of-service gratuity is not a single GCC-wide formula with minor local variations, it is six genuinely different calculations that happen to share a common underlying principle. Multinational employers operating across the region need payroll systems that know which formula applies to which employee, automatically.

Questions

Frequently asked questions

When should end-of-service be calculated?+
It should accrue monthly from the first month of service, not be calculated when an employee leaves. End-of-service is a balance-sheet liability, and organisations that compute it only at exit carry an unrecognised and growing obligation that is typically discovered during an audit or due diligence.
No. Where a national pension or social insurance scheme applies, such as GPSSA in the UAE or GOSI in Saudi Arabia, the end-of-service obligation sits alongside it rather than being discharged by it. Assuming otherwise leaves an unprovisioned liability on the books.
Several GCC jurisdictions treat resignation differently from termination, and the treatment of notice periods also varies. Because the rules differ by market and are periodically amended, model both scenarios so the exposure range is known, and verify the current position for each jurisdiction you operate in.
If the transfer is processed as a termination and a rehire, service length resets and the employee loses accrued entitlement, which is both a compliance exposure and a likely dispute. The system should move the employee record between entities while preserving service history.
See it for yourself

Ready to fix this
for your organisation?