Your Annual Leave Records and Your WPS File Now Have to Agree — Here's Where UAE Employers Get Caught Out
As Q4 leave-settlement season arrives, a quiet compliance trap is widening: leave encashment calculated off a payroll salary that never matched the MOHRE contract creates a WPS mismatch. The leave rules, the basic-salary basis, and a Q4 reconciliation checklist.
A practical guide for HR and payroll teams heading into year-end leave settlements. Last updated: September 2026.
Annual leave rules in the UAE are well understood. What far fewer employers have noticed is how the 2026 WPS framework has quietly connected leave administration to payroll compliance — so that a leave settlement calculated the wrong way no longer just overpays or underpays an employee, it can also produce a payroll-record mismatch that monitoring picks up. As Q4 arrives and leave-balance and end-of-service settlements pile up, that intersection is a genuine, expanding source of exposure. This guide walks through the leave rules that matter, the basic-salary basis they run on, and the specific 2026 trap where leave and WPS collide — with a reconciliation checklist to close it before year-end.
Informational only — not legal advice. This article is point-in-time (last updated September 2026). Leave and WPS rules are set under Federal Decree-Law No. 33 of 2021 and MOHRE regulations and are subject to change. Verify your position with MOHRE (mohre.gov.ae) or a qualified adviser before acting.
The leave rules that drive the numbers
Before the compliance angle, the entitlements the settlement rests on. Under Federal Decree-Law No. 33 of 2021:
- Annual leave accrues at 30 calendar days per year once an employee has completed one year of service, and at two days per month for those with between six months and a year of service.
- Unused leave is not forfeited on termination. An employee who leaves with an accrued balance is entitled to be paid for it — leave encashment is a statutory settlement item, not a discretionary one.
- These are minimums; a contract can be more generous, but not less.
Get the accrual right and the balance is defensible. Get it loose — untracked, estimated, reconstructed at exit — and the settlement becomes a negotiation.
Carry-forward: what actually rolls over
Employees do not always take leave in the year they earn it, and the carry-forward rule is where balances quietly build. In broad terms, an employee may carry forward up to half of their unused annual leave, subject to employer agreement, and leave should not be allowed to accumulate indefinitely — the common position is that it cannot be carried beyond about two consecutive years before it must be taken or paid out.
For HR, the practical implication is that carry-forward is not automatic and unlimited. Left unmanaged, it produces large accrued balances that land as expensive encashment liabilities at exit — and the bigger the balance, the more it matters that it is calculated on the correct wage.
The basic-salary basis — the point everything turns on
Here is the number that decides the size of every leave payout: leave encashment and end-of-service leave settlements are calculated on basic salary only — not the full salary including allowances — unless the employment contract explicitly says otherwise.
This is the same basic-vs-allowance distinction that governs gratuity and overtime, and it is where two things converge. The leave payout depends on the basic wage. The basic wage the law recognises is the one on the MOHRE-registered contract. So the moment your payroll system's basic-salary figure and your registered contract's basic-salary figure disagree, every leave settlement you calculate is potentially calculated off the wrong number.
The 2026 trap: two discrepancies, not one
This is the fresh angle, and it is where employers get caught out. The 2026 WPS framework (widely described by advisory firms as "WPS 2.0") introduced tighter, faster validation — reporting indicates that the basic salary reported in the WPS Salary Information File is now cross-checked against the basic salary on the MOHRE-registered contract, with mismatches surfaced automatically rather than discovered in a periodic audit.
Now trace what happens when a leave settlement is calculated off a payroll-system salary that was never formally updated in the MOHRE contract:
- Discrepancy one — the settlement itself. The leave encashment is calculated on a basic wage that does not match the employee's legally recognised (contract) wage, so the payout figure is arguably wrong and disputable.
- Discrepancy two — the WPS record. The same mismatched basic salary flows into the SIF, where it no longer agrees with the registered contract, and the cross-validation flags it.
One loose number has created two live problems: a contestable settlement and a payroll-compliance flag. And they share a single root cause — a salary figure that changed in the payroll system but was never reconciled to the MOHRE contract. (This specific real-time cross-validation mechanism is described in industry reporting on the 2026 WPS upgrade rather than a bare official MOHRE technical spec; the underlying requirement — that the SIF basic salary must match the registered contract — is long-standing and firm. Verify the current technical behaviour with MOHRE.)
The lesson is the same either way: reconcile the contract, the payroll system, and the WPS record to a single basic-salary figure before you run leave settlements off it.
Why Q4 is when this surfaces
Three things pile up at year-end: employees rushing to use or bank leave before it expires, carry-forward limits forcing balances to be taken or paid out, and end-of-year exits triggering final settlements. Each one runs a leave calculation off a basic-salary figure. If those figures were never reconciled to the contract during the year, Q4 is when the gaps all cash out at once — as disputed settlements and as a cluster of WPS mismatches at exactly the busiest payroll moment of the year. The reconciliation is far cheaper done in October than discovered in December.
Q4 leave-and-payroll reconciliation checklist
Run this before your year-end leave settlements:
- Reconcile basic salary across all three records — the MOHRE contract, the payroll system, and the WPS/SIF — for every employee, and resolve any mismatch at the source (update the contract, don't just edit payroll).
- Confirm leave balances are accurate and tracked, not reconstructed at exit, for everyone with an accrued balance.
- Apply the carry-forward rule — check who is over the carry-forward limit and must take or be paid out before year-end.
- Calculate encashment on the correct basic wage — basic salary only, unless the contract says otherwise, using the reconciled figure.
- Check any recent salary changes were documented — a raise or cut reflected in payroll but never registered in the MOHRE contract is a mismatch waiting to be flagged.
- Sequence exits and settlements so final leave payouts use the reconciled wage and the WPS record agrees.
- Keep the documentation trail linking each settlement to the contract figure it was calculated on.
The bottom line
Leave rules on their own are not the risk — the risk is the seam between leave and payroll that the 2026 WPS framework has tightened. Leave encashment runs on basic salary; basic salary is defined by the MOHRE contract; and the SIF must now agree with that contract. So a leave settlement calculated off an unreconciled payroll figure creates two problems at once — a contestable payout and a flagged WPS mismatch. Heading into Q4, the single most valuable thing an HR team can do is reconcile every employee's basic salary across the contract, the payroll system, and the WPS file, and settle leave off that one agreed number. Do it now, and year-end leave season is routine. Leave it, and the gaps all surface together at the worst possible time.
For the mechanics behind this, see our UAE WPS compliance guide, our UAE payslips and salary structure guide, and our annual leave encashment guide. Official leave guidance is on the UAE Government Portal at u.ae; the WPS framework is administered by MOHRE and the Central Bank of the UAE.
Settle year-end leave on one agreed number
RadixHR keeps leave balances, contract salaries, and WPS records in sync, so year-end leave settlements are calculated on one agreed figure that matches everywhere.
This article is for general information only and does not constitute legal advice, and is point-in-time (last updated September 2026). Leave, encashment, and WPS requirements are set under Federal Decree-Law No. 33 of 2021 and its Executive Regulations and MOHRE regulations, and are subject to change. The described real-time SIF/contract cross-validation reflects industry reporting on the 2026 WPS upgrade and should be verified against current MOHRE technical guidance. Verify current requirements with MOHRE or a qualified adviser before acting.
Related Articles
The ILOE Line Most UAE Payroll Runs Get Wrong: Employer Compliance, Not Employee Claims
Most ILOE content tells employees how to claim. This is the employer's side: your actual compliance exposure under Federal Decree-Law No. 13 of 2022, the AED 16,000 Category A/B split, the manual tier update a raise triggers, and termination documentation — with a quarterly ILOE payroll checklist.
MoHRE's Fake Emiratisation Crackdown: What "Genuine Employment" Actually Means for Your Payroll Records
MoHRE is using AI to detect fake Emiratisation — 377 cases across 266 firms in H1 2026. This is an audit-readiness guide: the two penalty tracks, how detection works, and the exact documentation you should already have on file for every Emirati hire.
WPS Now Covers Domestic Workers in the UAE (2026): What Sponsors Must Do
In 2026 the UAE Wage Protection System was extended to domestic workers — maids, drivers, nannies, cooks. Sponsors must now pay salaries through an approved channel, not cash in hand. Here is exactly what households must do, with a sponsor checklist.