For years, UAE employers who ran a few days late on payroll had breathing room — a 15-day grace period before the Wage Protection System flagged anything. That cushion is gone. Under the enhanced WPS, wages have to land on time, every time, or enforcement starts within days.
What's changing
Ministerial Resolution No. 0340 of 2026 replaces the previous WPS resolution (No. 598 of 2022) and takes effect on 1 June 2026. The core change is a single, unified deadline: wages for a given Gregorian month must be paid no later than the first day of the following month, processed through the WPS or another MOHRE-approved system, with proof of payment submitted to MOHRE.
There is a compliance threshold — an employer is considered compliant if at least 85% of total wages due are paid on time, which accounts for legitimate deductions or withholdings under UAE labour law. But there is no longer a grace period once that threshold is missed. Enforcement now runs on a fixed timetable set out in the resolution's annex: electronic monitoring starts on the due date, alerts and notifications from day 2, and suspension of new work permits from day 5. For repeat violations within six months, administrative fines and reclassification to the Third Category follow from day 11. From day 16, employers with 25 or more workers (and same-owner groups in sectors such as construction, security and cleaning) face automatic labour-dispute registration and wider permit suspension. From day 21, measures can include an executive instrument for wage payment, precautionary attachment and a travel ban on the person in charge, with referral to the Public Prosecution for larger repeat offenders.
The rule applies to all private sector employers, with limited exceptions for certain sectors and worker categories. Delegating payroll to a provider or third party doesn't shift the accountability — the employer remains responsible for timely payment regardless of who processes it.
Why this matters if payroll runs close to the deadline
Most businesses that miss a WPS deadline aren't trying to avoid paying staff — they're waiting on a client invoice, reconciling a bank transfer, or catching a data entry error in someone's salary structure. Under the old rules, that kind of short delay usually resolved itself inside the grace period without consequence.
Under the enhanced WPS, the same delay now starts a countdown from the due date. A payroll run that slips by a week — because a director was travelling and couldn't approve the file, or because the WPS file had a mismatched IBAN — can move from "processing" to "new work permits suspended" before anyone notices there's a problem. For a small or mid-sized business, new-permit suspensions and, for repeat offenders, category downgrades aren't abstract penalties; they affect the ability to hire, renew visas, and operate normally.
The businesses most exposed are the ones running payroll manually or semi-manually — spreadsheets feeding a WPS file, salary changes tracked separately from the file that gets submitted, no single record of who approved what and when. When there's no room left for a delay, the process needs to be reliable before the deadline, not fixed after it's missed.
Where automation actually helps
This is squarely a process problem, not a technology-solves-everything problem, so it's worth being specific about what automation can and can't do.
What it can do: keep salary structures, leave, deductions and new hires in one place instead of scattered across spreadsheets and email threads, so the WPS file being generated each month reflects what actually happened that month. It can generate the WPS-format file automatically from that data instead of a manual re-entry step, which is where IBAN mismatches and rounding errors tend to creep in. It can flag, ahead of the deadline, which employees are missing bank details or have an unresolved discrepancy, instead of that surfacing on submission day. And it can keep an audit trail of approvals, so "who signed off on this payroll run" isn't a question anyone has to reconstruct after the fact.
To be clear about the limits here: Diadyn is not a MOHRE-approved payment service and Payroll360 does not submit WPS files or verify wage payments to the government on a business's behalf — the payment still runs through a bank or MOHRE-approved system, and WPS compliance itself does not come from software alone. Using Diadyn 360 doesn't by itself make a business WPS-compliant; it reduces the chance that the file going into your bank or WPS-approved channel is late or wrong. For the specifics of the resolution, exemptions, and how they apply to your business, MOHRE's own guidance or your labour law advisor is the authoritative source, not this post.
What to do next
- Confirm your current payroll cycle actually lands wages on or before the first day of the following month, not just "by month end"
- Check where your process has manual handoffs — spreadsheet to WPS file, HR to finance, approval by email — and note which ones could slip a few days
- Verify every employee record has correct, current bank details before the run, not during it
- Build in an internal buffer of at least a few working days before the WPS deadline, given enforcement begins within days of it
- Confirm directly with MOHRE or your advisor how the new resolution applies to your specific sector and worker categories
If payroll at your business still depends on someone manually assembling a file the night before it's due, that's the part worth fixing before 1 June 2026, not after. HRM360 and Payroll360 keep employee, salary and leave data in one system so the payroll run reflects reality without a manual re-entry step, and Finance360 keeps the bank side of that process visible alongside the rest of your books.
