- Leave generates more disputes than payroll because entitlement is calculated from rules while employees experience it as a promised balance.
- Three configuration decisions cause most disagreements: mid-year accrual, carry-forward rules, and which salary components are payable during leave.
- Leave moves money four ways: leave salary and encashment, sick-leave banding, unpaid leave affecting service length, and accrual as a balance-sheet liability.
- Unused leave is an obligation that most organisations fail to carry as a provision, understating cost.
- Document the position per entity before configuring, then tell employees their balance before they discover it in self-service.
Leave management sounds like one of the simpler parts of HR administration, until a company starts operating across more than one GCC country and discovers that "30 days of annual leave" does not mean the same thing, or come with the same conditions, everywhere. Getting leave entitlements wrong is rarely a dramatic compliance failure, but it steadily erodes employee trust and creates avoidable disputes at exactly the moments, illness, childbirth, family emergencies, when a company most needs to get things right.
Annual Leave Across the Region
The UAE grants employees who have completed one year of service 30 calendar days of annual leave. Employees with between six months and one year of service are entitled to a prorated two days per month. Saudi Arabia sets a statutory minimum of 21 days of annual leave, rising to 30 days once an employee has completed five years of continuous service with the same employer. Qatar's Labour Law provides three weeks of annual leave for employees with one to five years of service, and four weeks for those with more than five years. Bahrain grants 30 days of annual leave per year. Oman provides 30 days per year as well, while Kuwait grants 30 days of annual leave after the first year of service, with a prorated allocation of two and a half days per month during the first year.
Sick Leave: Where the Real Complexity Lives
Sick leave is where most cross-border HR teams get tripped up, because nearly every GCC country uses a tiered pay structure rather than a flat entitlement. The UAE, for example, entitles an employee (after completing a probation period) to 90 days of sick leave per year, but the first 15 days are paid at full salary, the next 30 days at half salary, and the remaining 45 days unpaid. Saudi Arabia follows a broadly similar tiered structure: the first 30 days at full pay, the next 60 days at 75% pay, and up to 30 further days unpaid. Qatar provides two weeks of full pay followed by four weeks at half pay, once an employee has completed the applicable service period. Bahrain, Oman, and Kuwait each apply their own variations on this tiered principle, generally with a period of full pay, a period of reduced pay, and a final unpaid period, but the exact day counts and percentages differ meaningfully from one country to the next.
The operational risk here is straightforward: a payroll system that applies one country's tiered sick pay formula to an employee actually covered by a different country's law will either overpay or underpay that employee for an extended sick leave period, an error that is often only caught when the employee, or their manager, notices the payslip does not match expectations.
Maternity Leave
Maternity leave entitlements have been extended across several GCC markets in recent years, and continue to evolve. The UAE currently provides 60 calendar days of maternity leave, with the first 45 days at full pay and the remaining 15 at half pay, alongside specific provisions for a shortened working day for a defined period after returning to work. Saudi Arabia provides 10 weeks of maternity leave, with pay proportions depending on length of service. Qatar provides 50 days of maternity leave at full pay for employees who have completed one year of continuous service. Bahrain, Oman, and Kuwait each have their own specific durations and pay structures, generally in a similar range, but again, not identical.
A detail worth flagging specifically: several GCC countries also provide specific protections against termination during pregnancy or shortly after return from maternity leave, and some provide additional nursing breaks for a defined period after the employee returns to work. These are easy to overlook in a standard leave management system that only tracks the leave duration itself, rather than the surrounding protections and entitlements.
Public and Religious Holidays
Beyond annual, sick, and maternity leave, every GCC country observes a set of public holidays, including Eid al-Fitr, Eid al-Adha, and national days, that shift in the Gregorian calendar each year because they follow the lunar Hijri calendar. A company operating across multiple GCC countries needs to track slightly different holiday calendars for each entity, since the exact number of days granted for a holiday like Eid can vary by country and even by year, based on moon sighting confirmations.
Documentation and Approval Requirements
Each leave type typically comes with its own documentation requirement, a medical certificate for sick leave beyond a certain number of days, a specific notice period for maternity leave, proof of relationship for bereavement leave, and these requirements are not always identical across countries even when the underlying leave type looks similar on paper. A manual, paper-based leave approval process struggles to keep track of which documentation is actually required for which country's employees, which leads to either overly strict requests for paperwork that is not actually mandated, or gaps where required documentation is never collected at all.
What Good Leave Management Looks Like Across Borders
- Leave policies are configured per country automatically, not managed through a single generic policy applied everywhere.
- Sick leave pay tiers calculate automatically based on the employee's actual country of employment and days already used in the current cycle.
- Public holiday calendars are maintained per country and updated as Hijri calendar dates are confirmed each year.
- Maternity leave includes the surrounding entitlements, nursing breaks, termination protection windows, not just the leave days themselves.
- Required documentation for each leave type is tracked per country, prompting the right request without over-collecting paperwork.
How AmalOps Handles This
AmalOps applies country-specific leave policies automatically as part of the core HR record, so annual, sick, and maternity leave calculate correctly per employee without HR needing to manually track which formula applies to which country. Public holiday calendars are maintained centrally and updated as Hijri dates are confirmed, and required documentation for each leave type is built into the request workflow itself.
The Bottom Line
Why leave configuration causes more disputes than payroll
Leave generates more employee disputes than almost any other HR process, and the reason is that entitlement is calculated from rules while employees experience it as a promised balance. When the two disagree, the employee is not making a technical argument, they are pointing at something they believed they had.
Three configuration decisions cause most of the disagreements. How entitlement accrues for employees who join or leave mid-year. Whether unused leave carries forward, and if so how much and for how long. And which salary components are payable during leave, which matters because a GCC package is usually split across basic and several allowances.
Each of these has a legal minimum and a contractual position that may be more generous. Problems arise where the contract, the policy document, and the system configuration state three different things, which is more common than it sounds in organisations that have grown through acquisition.
The payroll consequences of leave
Leave is not only an HR record; it moves money, and in four ways that need to be configured deliberately.
- Leave salary and encashment. Payment in advance of annual leave, and the treatment of unused balance at exit, both of which require a defined salary base.
- Sick leave banding. Where entitlement is paid in full, then partially, then unpaid, the transition points must be tracked per employee across a rolling period.
- Unpaid leave and service. Whether an unpaid period counts toward service length, which flows directly into end-of-service entitlement.
- Accrual as a liability. Unused leave is an obligation, and organisations that do not carry it as a provision are understating cost.
The fourth point is routinely missed. A group with several hundred employees carrying substantial unused balances has a material liability that appears nowhere until people take the leave or leave the company.
Operational realities the statute does not address
Beyond entitlement, three practical problems recur in GCC organisations and are worth designing for rather than handling case by case.
Departmental coverage. Approving leave without visibility of who else is off produces coverage gaps that operational managers then solve with overtime, converting a leave decision into a payroll cost.
Payroll cutoff collisions. Leave applied for or approved after the payroll cutoff creates retrospective adjustments. Flagging the collision at the point of approval prevents it.
Peak clustering. Long-haul travel and school calendars concentrate annual leave into predictable windows across expatriate workforces. Forecasting the cluster is more useful than managing the resulting shortage.
Getting configuration right once
The sequence that avoids disputes is to document the position per entity before configuring anything: the accrual basis, the carry-forward rule, the salary components payable, and the treatment of unpaid periods. Then reconcile migrated balances to that documented basis and, critically, tell employees what their balance is before they discover it in self-service, as discussed in why self-service adoption stalls.
Where a migrated balance cannot be reproduced from any documented rule, decide a defensible position, record the basis, and communicate it. An employee informed of a correction with an explanation is a manageable conversation; the same employee finding a reduced balance in an app is not.
Verifying the current entitlements
Statutory leave entitlements across the six GCC states are subject to periodic amendment, and specific circumstances, including probation, fixed-term contracts, part-time arrangements, and parental leave provisions, turn on facts and jurisdiction. The comparison here is intended to show the structure of the obligations and where employers commonly go wrong. Confirm the current entitlement applicable to each of your entities and obtain professional advice before relying on any figure for a specific case.
Leave law across the GCC shares a broadly similar structure, but the details that actually matter in practice, pay tiers, service thresholds, and documentation, differ enough between countries that treating them as interchangeable is a reliable source of payroll errors and employee disputes. Getting this right is less about legal expertise and more about making sure the underlying system actually applies the correct country-specific rule every time, automatically.