Under UAE Ministerial Resolution No. 340 of 2026, effective 1 June 2026, private-sector employers must pay the previous month's wages through the Wage Protection System (WPS) by the first day of each Gregorian month.
The resolution removes the former 15-day grace period, raises the compliance threshold to 85% of wages due at both company and employee level, and brings new hires into scope immediately. Enforcement is automated from the due date, escalating through warnings, work-permit suspension, fines, and asset measures.
Every advisory on the UAE's new Wage Protection System rules arrives at the same conclusion – 'Pay salaries by the first of the month. Here is the penalty timeline if you are late.' The reading is accurate, and it is also incomplete. A fixed payday is the most visible thing Resolution 340 changed, which is exactly why it absorbs all the attention. Underneath the new deadline sits a quieter change with a longer reach. The UAE has redefined what counts as wage compliance and when it is measured. Treat 340 as a date to reschedule, and you will keep tripping an enforcement system that no longer waits for month-end to look.
Why everyone reads Ministerial Resolution No. 340 of 2026 as a date change, and why that reading quietly fails
The deadline framing is the natural one. Under the previous rules, Ministerial Resolution No. 598 of 2022, due dates were tied to each company's contract terms and a 15-day grace period buffered late runs. A payroll team could close the cycle in the first week of the month and still be inside the window. Resolution 340 replaces that with a single fixed obligation: the previous month's wages, paid through the WPS, by the first day of the new month, every month, for every employer registered with MOHRE.
That is a real change, and naming it is not wrong. The problem is what the framing leaves out. A deadline is a point in time. What 340 actually moved is not a point but a surface. The 15-day grace period was never just slack. It was where reconciliation lived, where a payroll team caught a misclassified deduction or a missing new-hire record and fixed it before anyone official saw the number. Remove the window and you do not simply shift the date earlier. You remove the place where errors were quietly repaired. Compliance stops being something you assemble once a month and becomes something you have to hold true on any given day.
Reason from the rule itself: four things the "new payday" framing hides
The clearest way to see the shift is to read the resolution's mechanics rather than its headline. Four structural changes sit underneath the new deadline, and a cut-off-date adjustment answers none of them.
No grace period turns reconciliation into a same-day discipline
Electronic monitoring begins on the due date itself. From the second day, MOHRE may issue warnings. By the fifth day, new work-permit issuance is suspended. By the eleventh, administrative fines apply and the establishment is reclassified. There is no longer a fortnight in which to find and correct an error before it is flagged. Month-end manual reconciliation, built from spreadsheets and chased by email, was designed for a deadline that no longer exists. The work that used to happen after the run now has to be finished before it.
The 85% threshold makes compliance something you prove, not just achieve
The previous framework treated an employee as paid once 80% of wages cleared the WPS. Resolution 340 raises that to 85%, and it applies at both the company level and the individual level. In practice, this caps WPS-relevant deductions at roughly 15% of an employee's monthly wage, against the wider limits the Labour Law allows in other circumstances. The consequence is documentary, not just arithmetic. Every deduction that takes an employee below the full wage now has to be lawful, recorded, and reconcilable on demand. Achieving the threshold is not enough. You have to be able to show your working.
Non-delegable liability means outsourcing the payroll moves the work, not the risk
The resolution permits employers to delegate wage payment to a third-party provider, provided MOHRE is informed of the arrangement. It is equally explicit that responsibility for timely, compliant payment stays with the employer regardless. Delegation moves the processing. It does not move the exposure. When the enforcement clock starts, every escalation step lands on the establishment, not the vendor running its file. An outsourced payroll without employer-side visibility into compliance is a risk an enterprise carries blind.
Day-one scope collapses the gap between onboarding and first payroll
The earlier 30-day exemption for new joiners is gone. New hires are inside the WPS from their first day of employment. That removes a buffer most onboarding processes were built around, where a joiner's first salary could wait for the next clean cycle. Onboarding-to-payroll can no longer be a next-month task handled by hand. The employee's record, bank details, and wage data have to be complete and feeding payroll from the start, because the system is already counting them.
The reframe: UAE payroll just became a continuous compliance surface
Read together, the four mechanics describe one change, not four. The UAE has moved private-sector payroll from a periodic event to a continuous compliance surface. Compliance is no longer assembled at month-end and submitted. It is monitored from the due date, measured at the individual level, owned by the employer whoever runs the file, and live from a new hire's first day. The enforcement layer is automated, and it counts in days, not weeks.
Enterprises that respond to this with a calendar change will solve the wrong problem. Moving the cut-off earlier buys time for the same monthly process. It does not give that process the daily accuracy the new surface demands. What the rule rewards is an operation where payroll data is correct and provable on any day of the month, not just reconciled on one.
This is where the system you run starts to matter. Darwinbox automates WPS compliance for the UAE from within its native payroll, drawing wage, attendance, and deduction data from a single Core HR record of employment rather than stitching it together at cut-off. WPS file generation and the reconciliation behind it run against current, audit-ready data, so the 85% threshold and the deduction record are provable rather than reconstructed.
For enterprises running multi-country payroll across the Middle East, the same logic holds in each jurisdiction, with local rules applied on shared infrastructure. The point is not the file. The point is that continuous compliance becomes the default state of the system, not a monthly effort to reach it.
What CHROs should change before the framing catches them out
The practical work is less about June and more about posture. Three moves matter.
Bring the payroll cut-off forward enough that the cycle closes with room to verify, not just to submit. The aim is not an earlier deadline for the same manual scramble. It is a process that finishes before the first, with time to check.
Make deductions audit-ready by default. Every deduction that affects the 85% threshold should be documented at the moment it is applied, with a lawful basis attached, so the record exists before anyone asks for it. This is the difference between achieving compliance and being able to demonstrate it.
Build daily compliance visibility regardless of who runs payroll. Whether the file is generated in-house or by a provider, the employer needs a live view of where it stands against the rule. Liability does not move with delegation, so neither should visibility. The payroll software for the UAE that an enterprise relies on should make that view a standing feature, not a month-end report.
None of this is a one-time fix for the June change. The grace period is not coming back. Continuous wage compliance is the permanent shape of UAE payroll now, and the enterprises that treat it as a posture rather than a deadline will be the ones not reading the enforcement timeline in real time.
References
FAQs
When do UAE private-sector salaries have to be paid under the new rules?
Under Ministerial Resolution No. 340 of 2026, the previous month's wages must be paid through the WPS by the first day of each Gregorian month. This replaces the contract-based due dates and 15-day grace period that applied under Resolution 598 of 2022. Any payment made after the first is treated as delayed, with enforcement beginning automatically from the due date.
What happens if an employer pays salaries late in the UAE?
Late payment triggers an automated escalation that begins on the due date with electronic monitoring. Reported steps include warnings from the second day, suspension of new work permits from the fifth day, administrative fines and reclassification from the eleventh, dispute registration on employees' behalf from the sixteenth, and referral to public prosecution with asset and travel measures from the twenty-first for serious or repeated cases. This is operational risk guidance, not legal advice; specifics should be confirmed with counsel.
Does using a payroll outsourcing provider make an employer WPS-compliant?
No. Employers may delegate wage payment to a third party, but Resolution 340 keeps ultimate responsibility for timely, compliant payment with the employer. If a delegated payroll misses the threshold or the deadline, the enforcement steps fall on the establishment, not the provider. This is why employers need daily compliance visibility even when payroll is delegated. Darwinbox gives the employer that visibility against the rule, whoever generates the WPS file.
