Managing Summer Leave Across the GCC Without Payroll Errors
When staff take long leave over the GCC summer, payroll rarely breaks because the software failed. It breaks because a leave transaction reached the system after the pay cycle it belonged to had already closed. Payroll is a point-in-time snapshot; leave is a running ledger. The two only reconcile if the leave is captured, and the calendar is correct, before the cutoff. This guide is about that gap across the UAE, Saudi Arabia, Qatar and Bahrain, and what the HR teams who never trip on it do differently.
It is not an “error.” It is an imbalance.
Bilal, a Customer Experience Specialist at gulfHR who works with clients through exactly these situations, refuses the word “error” on principle.
“We would eliminate this word ‘error’ and replace it by ‘imbalance.’ If the HR is dedicatedly maintaining balances, and they are well linked and well synced, so they are putting in leaves correctly, it is fine.”
— Bilal, Customer Experience Specialist, gulfHR
That is not semantics. An “error” implies the system computed something wrong. An imbalance means the system computed correctly on incomplete or mis-dated inputs. The distinction tells you where to look, and it is almost never the pay engine.
Here is the mechanism that catches people out. An employee takes leave in June, but the leave is only entered in August, future-dated. June’s payroll was generated with no leave recorded against that employee, so June overpaid. When the leave finally lands, the system applies its “previous days taken” logic and rebalances, but it does so in the cycle that is currently open, not the one that was actually affected. The correction surfaces a month or two late, on an unrelated payslip, which is why it reads as a mystery deduction rather than a late entry.
The practical control is a cutoff, not a plea to be careful. Any leave affecting a given period must be in the system before that period’s payroll is generated. Once the run closes, the same fact becomes a retroactive adjustment, and retro adjustments are what turn a five-minute entry into an afternoon of reconciliation and an awkward conversation about a payslip that already went out.
A quieter version of the same fault is open-ended leave. If a leave is logged with no return-to-work date, the system has no instruction to close it and keeps treating the employee as absent, so the balance keeps moving. The fix is trivial, but only if someone catches it before the cycle closes.
Public holidays: the trap that is set months before it springs
A configured system applies each employee’s entitlement and accrual automatically, which is exactly why manual tracking collapses at scale. Across a few hundred people, one missed transaction a month is enough to put a balance out. But the system does not invent its own calendar. Out of the box it does not know that a date is a public holiday. It knows only what HR has marked.
This is where summer leave quietly goes wrong. Take an employee on leave across a period that includes a public holiday, say the Islamic New Year in July. If the day is marked as a holiday, the system does not spend annual leave on it. If it is not marked, those days are deducted as leave, and the employee comes back short without anyone deciding that on purpose.
Two GCC realities make this sharper in summer than at any other time. First, several public holidays follow the Hijri calendar, shift by roughly eleven days each year, and are often confirmed by moon sighting only days before, so last year’s calendar cannot be reused and even a pencilled-in date can move. Second, under UAE Federal Decree-Law No. 33 of 2021 the default rule is that a public holiday falling within annual leave is counted as part of the leave unless the contract or company policy is more favourable. Many employers do exclude those days by policy, but the system can only enforce the policy it has been told about.
There is also a sequencing trap most teams miss. Marking a holiday after leave has already been booked, or after the cycle has closed, forces a recalculation that only applies cleanly while the payroll cycle is still open. Mark it late and you are back in retro-adjustment territory. The teams that never deal with this mark the whole year in one sitting:
“They would consider all the public holidays they could be having within the calendar for the whole year, and they would mark them in advance.”
— Bilal, Customer Experience Specialist, gulfHR
Different weekends, different entitlements, one pay run
A “15-day leave” does not mean the same thing in every GCC country, and a system that assumes uniformity miscalculates silently. The rest days differ: since 2022 the UAE runs a Saturday–Sunday weekend, while Saudi Arabia, Qatar and Bahrain work Sunday–Thursday with a Friday–Saturday weekend. So do the statutory entitlements: the UAE grants 30 days of annual leave a year after one year of service; Saudi Arabia grants 21 days, rising to 30 after five years; Qatar gives three weeks a year below five years and four weeks at five and above; Bahrain grants 30 days after a year.
The real danger is not that the rest days differ, which is obvious. It is that a single leave type or calendar, copied across entities to save setup time, will accrue and deduct against the wrong baseline for every employee outside the entity it was built for. Nothing throws an error. The numbers are simply, and invisibly, wrong until someone reconciles a leaver’s balance and cannot make it tie out. The competent teams, in Bilal’s words, are the ones who are “not complacent with the policies”: they treat each country’s calendar as its own object, not a duplicate.
The bill you defer to exit: encashment and gratuity
Untracked summer leave costs nothing in July. It crystallises months later, in cash, at settlement. In the UAE, end-of-service gratuity is calculated on the last basic salary, at 21 days’ pay for each of the first five years and 30 days for each year after, capped at two years’ pay and due within 14 days of the end date, with unpaid-leave periods excluded from the service counted. Leave encashment is settled on the closing balance. Both sit downstream of the leave ledger, which is why a casually tracked summer becomes a disputed final settlement.
The reason clean records matter here is not tidiness. It is that they end the argument. When a departing employee claims days the system does not show, the leave detail report is the single source of truth, and any genuine gap can be traced and adjusted against it. A balance nobody maintained is a balance nobody can defend, in either direction.
A myth worth correcting: annual leave and WPS are not linked
HR managers often assume annual leave has to be reconciled against Wage Protection System (WPS) filing dates. It does not. WPS governs how and when wages are paid, not leave; Bilal calls it “a complete different thing.” The only real connection runs the other way: unpaid leave lowers the net payable, and that lower figure is what goes into the salary file.
So leave never moves your WPS deadline, but a leave imbalance can still push a wrong number into a submission you cannot recall. That matters more in 2026 than it did. Under UAE Ministerial Resolution No. 340 of 2026, wages are due at the start of the Gregorian month and the former grace period has effectively been removed, with at least 85% of wages required to transfer on time. The buffer that used to absorb a late leave correction has closed: the file goes out on day one, imbalance and all. Confirm the exact current deadline with MoHRE before relying on a specific date.
The most avoidable failure: everyone is away, including the payroll owner
The summer failure that is entirely preventable is a single point of knowledge going on leave with no cover. Bilal’s rule is worth adopting word for word:
“There must be a formal handover process before the custodian goes on a leave.”
— Bilal, Customer Experience Specialist, gulfHR
For genuine emergencies gulfHR keeps a dedicated support team and documented processes so a run can still be reviewed and completed. But the deeper point is about where knowledge lives. When payroll runs out of one person’s head, their leave, or their exit, takes the pay run with them. Resilient teams keep the process and the data in the system, not in a custodian.
How gulfHR helps keep summer leave in balance
No system removes the need for accurate, timely data entry, but the right configuration makes the disciplined path the easy one. Available functionality should be confirmed during scoping; the following reflects how gulfHR is designed to work.
- Leave workflows and bulk control. Requests route from employee to line manager to HR, and HR can manage many leave types from a single grid, including bulk approve or reject during peak weeks.
- An HR authorise provision when an approver is away. Where the normal approver is unavailable, HR can authorise or reject a leave directly so it still lands in the correct pay cycle. This is an HR override, not automatic reassignment; confirm any automated delegation or escalation routing during scoping.
- Calendar day-type control. Any date can be set to public holiday or off in advance, per calendar, which is what closes the holiday trap above.
- An audit trail. Leave detail reports evidence exactly what the system holds, which is what a settlement or an audit is judged against.
On multi-country payroll there is a decision most buyers make too late. Running several countries under one entity to save on setup will, in gulfHR’s client experience, jumble the calculations, because one entity carries one set of baseline rules. Running them as separate entities keeps each country’s rules, calendar and pay elements clean, but that is a configuration step and a chargeable one. Either way it is settled at implementation, not toggled on the day of a run. Decide your country structure during scoping, not in your first difficult July.
gulfHR expert view: the imbalance you discover in August was almost always created in June, before anyone left their desk. The trigger is rarely the leave itself. It is an unmarked holiday, an open-ended leave with no return date, or a payroll cutoff that passed before the entry was made. By the time payroll surfaces it, the cycle that should have caught it has already closed. In practice, summer payroll is won or lost in spring.
What gulfHR sees in practice
Table: recurring summer leave imbalances and the response, based on gulfHR customer-operations experience.
| Operational area | Common issue | Business consequence | System or governance response |
|---|---|---|---|
| Leave logging | Leave entered late or future-dated | Correction lands in the wrong, later cycle | A published payroll cutoff; reconcile before the run |
| Open leave | No return-to-work date set | Balance keeps moving; employee stays “absent” | Require a return date on every leave request |
| Public holidays | Holidays not marked per entity calendar | Holiday days deducted as annual leave | Mark the whole year, per country, before leave is booked |
| Approver away | Approvals sit unactioned | Leave missing from that cycle’s pay | Formal handover plus the HR authorise provision |
| Multi-country | One calendar copied across entities | Wrong accrual baseline, invisible until reconciliation | A separate entity and calendar configured per country |
| Exit settlement | Untracked leave surfaces at end of service | Encashment and gratuity disputes | Keep the ledger clean year-round, not just at exit |
Why this matters beyond the payroll desk
A leave imbalance is a Finance, compliance and trust problem, not a filing nuisance. Over- and under-payments trigger correction runs; a misstated unpaid-leave figure can push a wrong WPS submission; and trust on pay is thin, external research (EY) puts typical employer payroll accuracy at around 80%, and finds a large share of employees will start looking elsewhere after just two pay mistakes. Those figures are global rather than GCC-specific, but the asymmetry holds everywhere: getting a leave into the system on time costs minutes, and not doing so is paid back in corrections, disputes and, at the sharp end, regulatory penalties.
From chaotic to controlled: one client’s summer
A long-standing enterprise client shows both the risk and the recovery. Its two payroll custodians left the business overnight. An IT specialist stepped in as custodian and the pay runs fell behind, processed only through January 2026, a gap of four to five months. The client came to gulfHR in late June.
“We aligned their leave balances by sitting with them together. We had overnight calls with them, and we had the calculations updated. Now they have their payrolls processed up until June and are looking forward to processing July as usual.”
— Bilal, Customer Experience Specialist, gulfHR
A five-month gap closed in about three weeks. The recovery is the headline, but the reason it was possible matters more: the underlying leave data still existed to rebuild from. Had those balances lived only in the two departed custodians’ spreadsheets, there would have been nothing to reconstruct. The gap was a people problem. The fix was a data one.
Your pre-summer checklist (do it in April and May, not July)
The work that keeps July calm happens in spring, before a single summer leave is booked:
- Mark the full year’s public holidays and rest days in every country calendar, and treat Hijri dates as provisional until confirmed by official announcement.
- Set and publish a payroll cutoff for each cycle: the date by which all leave affecting that period must be in the system.
- Reconcile opening balances and carry-over now, while there is still time to investigate a discrepancy rather than inherit it.
- Require a return-to-work date on every leave request, so nothing stays open.
- Name a backup and write a handover for every payroll and approval role, and enable the HR authorise route for emergencies.
- Confirm in writing who owns calendar and configuration, your team or your service provider, so nothing falls between the two.
Frequently asked questions
Do public holidays during annual leave count as leave in the UAE?
Under the default federal rule, a public holiday falling within annual leave is counted as part of the leave unless the contract or company policy provides more favourable terms. If your policy excludes public holidays from leave, the holiday must be marked in the system for that policy to actually apply.
Does annual leave affect WPS filing?
There is no direct link. WPS governs how and when wages are paid, not leave. The only connection is indirect: unpaid leave lowers the amount payable, and that lower figure is what you file.
How does summer leave affect end-of-service and encashment?
Leave encashment is based on the closing leave balance, and UAE gratuity is based on last basic salary with unpaid-leave periods excluded from the service counted. Both depend on an accurate leave ledger, so untracked summer leave often becomes a settlement dispute later.
Can one system run payroll for several GCC countries at once?
Yes. gulfHR can run multiple entities in parallel, with each country’s rules and calendar configured separately. Because running distinct country rules cleanly is an implementation-time configuration, scope your country structure early rather than assuming it on the day of a run.
Speak to gulfHR about your multi-country HR and payroll requirements and go into summer with leave and payroll in balance.
Sources
- UAE annual leave, Federal Decree-Law No. 33 of 2021 — u.ae.
- UAE WPS 2025–2026 rules and penalties — u.ae, payment of wages.
- UAE midday break, 15 June–15 September — MoHRE.
- Saudi annual leave, Article 109 — Ministry of Human Resources and Social Development.
- GCC leave policy comparison — Gulf Business.
- UAE and GCC weekend structures — reference guide.
- Payroll accuracy and correction rates — EY, via HR Dive.