UAE WPS in 2026: what Resolution 340 changes for your payroll run

Ministerial Resolution 340 of 2026 replaced the rules UAE payroll has run on since 2022. Here is the new deadline, the 85 percent threshold that decides compliance, and the escalation that now ends at the Public Prosecution.

On 1 June 2026, Ministerial Resolution No. 340 of 2026 came into force and repealed Resolution No. 598 of 2022. If your payroll calendar, your escalation runbook or your internal policy still describes the old regime, it describes rules that no longer apply. The change is not cosmetic. It sets a firmer deadline, introduces a percentage threshold for what counts as compliant, and ends its escalation ladder at the Public Prosecution rather than at a fine.

This guide covers what actually changed, what the new threshold means in practice, and the specific points in a payroll process where an establishment tends to fall behind the clock. It is written for the person who owns the pay run, not for a legal filing.

The deadline is now the first of the month

Under Resolution 340, wages must be paid no later than the first day of each Gregorian month for the preceding Gregorian month. That wording matters for two reasons. It fixes the calendar to Gregorian months, and it removes the softer reading some establishments applied to the old fifteen day grace period, which was widely treated as the real deadline rather than the point at which wages became overdue.

In practice this compresses the window that payroll teams had been working to. If your process depends on attendance closing on the last day of the month, exceptions being reviewed the following week, and payment going out mid month, that process is now built around a deadline that has already passed.

The 85 percent threshold

The most consequential new idea in Resolution 340 is that compliance is measured proportionally. An establishment is treated as compliant when at least 85 percent of total wages are paid on time, after accounting for deductions that are permitted under the labour law.

This is not a licence to pay 15 percent of your people late. It is a tolerance designed to absorb genuine edge cases: a terminated employee whose final settlement is under calculation, a bank rejection on a single account, a new joiner whose details have not yet cleared. The risk is treating the tolerance as headroom. It is measured on value, not headcount, so a handful of senior salaries can consume the entire margin on their own.

What happens when you miss it

The escalation under Resolution 340 is staged and automatic. What follows is the sequence as set out in published analysis of the resolution. The important structural point is that it runs on elapsed days rather than on a caseworker opening a file.

The day 5 stage is the one that turns a finance problem into an operations problem. An establishment that cannot issue new work permits cannot onboard, which means a late pay run in one month constrains hiring in the next. The day 21 stage is the one that changes the personal calculus for whoever signs off the run, because referral to the Public Prosecution carries exposure for authorised signatories, not only for the entity.

Where establishments actually lose the days

Almost nobody misses the WPS deadline because they decided not to pay. They miss it because the pay run could not be finalised in time, and the reasons are consistent across establishments of very different sizes.

• Attendance for the final days of the month is still being corrected when payroll needs to close, so the run waits on a handful of disputed timesheets.
• A leaver's final settlement is unresolved, and the whole file is held rather than submitted without them.
• Bank details changed in the HR record but not in the payroll sheet, so a transfer bounces and the correction misses the window.
• Variable pay, overtime or commission arrives from another department as a spreadsheet, late, and has to be keyed in and checked.
• The approver is travelling, and the run has a single approval path with no delegate.

A practical checklist for the new regime

1. Move your internal payroll cut-off earlier than the statutory deadline, so the buffer absorbs exceptions rather than consuming your tolerance.
2. Model the 85 percent threshold against your real wage distribution and identify which individual salaries could breach it alone.
3. Give every approval step a named delegate, so one person travelling cannot hold a run.
4. Reconcile bank details from the HR record at the point the file is generated, not from a separate sheet.
5. Decide in advance how an unresolved final settlement is handled, so a single leaver does not hold the whole submission.
6. Keep each submission with its validation result, so a dispute can be answered with a record rather than a recollection.

Why this favours integrated systems

A tighter deadline punishes handoffs. Every point where data moves between systems by export and import is a place where the run can stall, and the new calendar leaves less room to recover. When attendance, leave, final settlements and payroll read from the same record, the pay run stops being an assembly job and becomes a review job, which is a task that fits inside a shorter window.

The establishments that stay compliant under a tighter deadline are not working faster. They removed the steps where the run could wait on somebody else.

If you are reviewing your process against Resolution 340, start by asking how many distinct systems a single payslip depends on, and how many of those hops involve a human moving a file. That number is a better predictor of whether you will make the first of the month than the size of your payroll team.

Keep reading