The Wage Protection System Explained: What Changed in June 2026, and What It Means for Your Payroll Calendar

Until June 2026, a wage was treated as late once it passed the contractual due date by fifteen days. That grace period is gone. Wages for a month are now due through the system by the first day of the month that follows.

What Ministerial Resolution No. 340 of 2026 Changed

The Wage Protection System is the mandatory electronic channel through which private sector wages must be paid and recorded in the UAE, established under Federal Decree-Law No. 33 of 2021 and operated by the Ministry of Human Resources and Emiratisation together with the Central Bank of the UAE. Every employer registered with MOHRE is in scope, regardless of headcount. Abu Dhabi-based businesses can verify their establishment registration status through TAMM, the emirate’s integrated government services portal.

Ministerial Resolution No. 340 of 2026, effective from 1 June 2026, established two things:

• The payment deadline is now unified: the first day of every Gregorian calendar month is the due date for the preceding month’s wages, regardless of what employment contracts say.
• The fifteen-day grace period that many businesses had built into their payroll timing is abolished.

Why the Change Caught Employers Out

I have not spoken to a single client who received a direct notification that this change affected their payroll cycle. The rule changed. The employer’s behaviour did not. And yet they became non-compliant overnight.

What made this change particularly disruptive is that nothing about an employer’s conduct changed. Businesses that paid on the fifth or seventh were operating exactly as they had for years. The compliance status of that behaviour changed on 1 June 2026 without any action or omission on their part.

Most businesses I have spoken to since June did not know the deadline had unified to the first of the month. The gap is most acute for businesses going through structural change: a corporate tax deregistration, a branch closure, or a restructure. In each case, the MOHRE record for departing employees needs to be clean before the establishment can be wound down.

For mainland employers and most free zone employers, the federal framework applies. I see this pattern in my Abu Dhabi practice every few months: a business that has operated correctly for years, unaware that June 2026 reset the compliance clock. The exception is the financial free zones: the DIFC and ADGM operate their own wage protection frameworks, and the federal WPS system does not apply inside those perimeters.

The new WPS salary deadline is not just a date change: it is a process change. If the payment has to clear by the first, the payroll cycle has to close before the month it covers has finished.

Closing payroll for October requires finalising October attendance, overtime, and any variable pay falling in the final days of October before the close. If payment must clear by 1 November, the SIF file needs to be submitted by the 27th to 28th of October, which means inputs need to be complete by the 20th to the 23rd. The last ten days of the month can no longer be included in the cycle they relate to.

There are three credible approaches to what falls in that final window:

• Cut off variable elements earlier,  accept that the final days are excluded from that cycle, and pay them in the following month’s run.
• Estimate final-period variables  based on averages or approved forecasts, submit on that basis, and true up in the following cycle when actuals are confirmed.
• Restructure what is variable,  moving some elements to a fixed allowance reviewed quarterly, which simplifies the cut-off problem at the cost of some precision.

None of these is inherently right for every business. Whatever route I help a client choose, the accrual must reflect what was earned in the period rather than what was paid. Moving the payment date earlier does not move the expense recognition. I make that point explicitly in every engagement where the payroll close has moved: the bookkeeping discipline of separating the payroll period from the payment date is the accounting change the June 2026 deadline demands.

A composite case from my practice illustrates the cost of getting the underlying compliance wrong. A civil contracting business, Abu Dhabi mainland, thirty-one employees, monthly payroll of approximately AED 185,000. Twenty-five site workers had been paid in cash for three years and eight months, with no SIF submissions.

Six office staff were paid correctly through the WPS channel. When the owner submitted a bid for a government infrastructure contract requiring a MOHRE compliance certificate, the certificate was unavailable: MOHRE showed twenty-five employees on active work permits with no WPS record.

The remediation cost approximately AED 84,700. The cost of WPS compliance from inception would have been approximately AED 16,000 to AED 22,000 over the same period. Government contract qualification increasingly requires audited financial statements alongside the MOHRE compliance certificate: both need to be in place before the bid is submitted, not assembled after it is lost.

The WPS 85 Per Cent Compliance Rule

The 85 per cent threshold is the provision I find most consistently misunderstood in client conversations. An establishment is treated as compliant where at least 85 per cent of total wages are paid on time, and the measure is on value, not headcount.

This matters because a single senior salary representing a large share of the total wage bill weighs more than several junior ones. An individual worker is also not considered underpaid if at least 85 per cent of their entitled wage was transferred on time, with the remainder being legally documented deductions. Those deductions include approved loan repayments, court-ordered withholdings, and unpaid leave correctly processed through MOHRE.

The threshold should not be treated as a buffer. It exists to absorb genuine exceptions. A business that routinely operates close to it has no margin when a real exception arises, and the compliance record logs every month it is triggered regardless of whether a formal action follows. The penalty escalation mechanism for WPS mirrors how VAT penalties in the UAE are structured, automated, staged, and triggered without a prior warning letter.

How MOHRE WPS Enforcement Escalates

Enforcement begins on Day 2 after the deadline, not after a grace period, not after a complaint is filed. The system under Ministerial Resolution No. 340 of 2026 monitors automatically from the second of the month, with clearance tracked through the Central Bank of the UAE‘s payment infrastructure.

Every time I walk a client through this sequence, Day 5 is the consequence that lands hardest. The escalation follows a defined sequence:

• Day 2:  electronic alerts issued; non-compliance permanently logged on the establishment’s MOHRE compliance record.
• Day 5:  all new work permit applications, renewals, and transfers suspended until wages are settled.
• Day 11:  administrative fines applied; company downgraded to the third MOHRE compliance category.
• Day 16:  for establishments with 25 or more workers, MOHRE files a labour dispute on affected employees’ behalf.
• Day 21:  case referred to the Public Prosecution; consequences include executive orders, asset freezing, and travel bans on the person responsible for the company.

The consequence that bites first for most mid-market businesses is Day 5. A payroll that clears on the third does not produce a warning letter. It produces a work permit suspension from the sixth, with no window to correct before the suspension is already in effect.

I describe the enforcement asymmetry this way to every payroll client: there is no letter that arrives saying “your WPS submission is missing; your permits are blocked.” The block exists in the system. The employer discovers it when a permit application stalls, or a contract bid requires a compliance certificate the system cannot issue. The enforcement mechanism does not announce itself.

It surfaces at the commercially sensitive moment when smooth MOHRE access was the prerequisite for something else, and that timing is not incidental. It is how the system is designed.

The salary information file is the document at the centre of every WPS submission. Understanding what it contains, and where it fails, is the difference between a clean MOHRE record and a compliance gap that surfaces at the worst possible moment.

What the WPS SIF File Contains

The WPS SIF file is the mechanism, and it is an output of your employee master data rather than a form somebody fills in.

The SIF file carries a header identifying the employer and the payroll cycle, and a detail line for each employee in a prescribed format, submitted through the approved agent bank or exchange house. The employer identifier in that header draws from the MOHRE establishment register: the same register that needs to be current for UBO registration and other corporate compliance obligations.

Why WPS SIF Files Get Rejected

In my experience across more than 50 businesses in Abu Dhabi, it is almost never the payroll calculation that is wrong when a file is rejected. Rejections trace back to the master data:

• Labour card numbers  containing a digit error, stale from a previous permit, or not updated after a recent renewal
• Bank identifiers  that do not match what the agent holds, usually because a salary account changed without updating the WPS registration
• Employees who left  and were never removed from the submission template
• New joiners  added to payroll but whose labour card details are not yet in the agent’s system
• Partial-month period declarations  defaulting to the full calendar month rather than the actual start or end date for joiners and leavers

That last point trips up employers who are already doing everything else correctly. An employee who joins on the 14th of October on a monthly salary of AED 8,000 is entitled to approximately AED 4,645 for the eighteen days worked. Most employers pay the correct pro-rata amount.

What many do not do is declare the correct period in the SIF file. If the file shows 1 October to 31 October but records only AED 4,645, MOHRE reads an underpayment for the full month rather than a correct pro-rata for a partial period. I have seen this discrepancy produce a gratuity dispute more than once: the MOHRE record implied a different start date than the actual join date, and the calculation diverged by half a month’s salary.

Since December 2025, MOHRE upgraded WPS to near real-time validation. The December 2025 WPS 2.0 upgrade, coordinated with the Ministry of Finance, verifies SIF data against registered employment contracts at the point of submission.

Under the new deadline, there is no longer time to discover a rejection and fix it in the same cycle. The payroll register is also the source document that feeds the UAE Corporate Tax return’s staff cost deductions, another reason to keep it clean. For how gratuity accrues and how to provision for it, that is covered separately in the payroll processing article.

When the cut-off moves earlier, what was a payroll question becomes an accounting question. The period that earnings relate to and the period in which they are paid are no longer the same.

Rebuilding the WPS Payroll Close

Moving the close earlier without losing accuracy on variable pay requires a deliberate choice about where the cut-off falls. Whatever approach a business adopts, journal entries need to track what was earned in the period rather than what cleared the bank. That is the accounting consequence of the deadline change, and it sits alongside the gratuity and provision questions covered in the payroll in the UAE guide. For businesses without a dedicated finance function, outsourced accounting is the most practical way to absorb the added complexity without hiring.

Keeping the WPS SIF File Clean

The discipline that prevents SIF rejections is one master payroll register as the single source of truth: the SIF file, the payroll journal, the employment contract schedule, and the gratuity accrual all flow from it. Every employment change updates the register first. Every submission is generated from the updated register.

When the SIF file, the payroll journal, and the employment contract all draw from the same current source, rejections become detectable before submission rather than discoverable after a dispute. For help mapping this process against your current payroll setup, an advisor in Abu Dhabi can work through the specifics with you.

The myth I most want to go away is this: “as long as I pay my employees on time, I’m WPS compliant.”

It is stated with complete confidence, and it is wrong in the specific way that makes it most dangerous, wrong precisely when it feels most right.

WPS is not a payroll system. It is an employment record system that happens to move money. The payment creates the MOHRE record.

Without the record, the payment has no official existence in MOHRE’s system, regardless of whether every dirham reached every employee. I have seen this in three distinct forms:

• A business that paid every employee correctly for four years with no WPS record for any of it, salaries moved through informal bank transfers rather than through a WPS-approved channel with a SIF submission.
• A retail trading business paying commissions of AED 2,000 to AED 8,000 per month informally, recording only AED 4,500 basic in the SIF file. When the employee resigned and disputed the gratuity, the MOHRE record showed five years at AED 4,500. The employer had to reconstruct actual earnings against a record that said something different.
• A business submitting SIF files every month but never confirming whether those submissions were accepted. Four months of rejected files sat in the portal. The employees had received their money. MOHRE’s system showed four months with no compliant submission.

In every case the employer’s experience was that payroll was working. In every case, MOHRE’s record showed something different. The gap became visible only at the specific commercial moment. A permit application, a contract bid, a labour complaint: when the employer needed the record to confirm compliance rather than expose a gap.

For businesses going through a contract bid qualification, statutory audit readiness and a clean MOHRE record are required together. WPS compliance is enforced through friction at that moment of pressure, not formal advance notice.

After reviewing WPS compliance records for more than 50 businesses across Abu Dhabi, the patterns that cause the most damage are consistent. These are the six disciplines I put in place for every client from day one.

1. My Standing Rule: The 27th, Not the 1st: My standing rule with every payroll client is the 27th, not the 1st, as the internal payroll completion date. By the 27th, the SIF file should be submitted and the confirmation received. That four-day buffer absorbs bank processing time, SIF validation, and the one correction that arises in at least one month of every twelve. The same calendar discipline applies to UAE Corporate Tax filing deadlines: both run on fixed statutory dates with no informal extension.
2. Confirm Submission Acceptance Separately from Payment Confirmation: After each payroll run, log into the WPS portal and confirm the SIF file processed without errors. Retain the confirmation reference number. Twelve months of confirmation records answers any MOHRE query without reconstruction.
3. Declare Partial-Month Dates Precisely for Every Joiner and Leaver: An employee who joins on the 14th of October should have the SIF show 14 October to 31 October, not the full calendar month. Most payroll tools default to the full period. Override that default for any employee whose start or end date does not align with the first or last day of the month. The date mismatch is invisible month to month but compounds into a service-length discrepancy that surfaces at termination.
4. Process Variable Pay Through the WPS Channel in the Month It Is Paid: Commissions, service charges, and any variable element paid in a given month must appear in that month’s SIF file. I tell every client with a commission structure the same thing. An employer paying commissions informally while submitting only basic salary in the SIF is building a multi-year record that understates what employees actually received, the starting point of any MOHRE dispute at termination.
5. Confirm Every Labour Card Number Before the First Submission and After Every Permit Renewal: Since December 2025, SIF data is verified against registered contracts in real time. A number that is one digit off, or that reflects the previous permit after a renewal, produces a rejected submission. My pre-payroll checklist for every new client starts here. Pull every labour card number from the MOHRE portal, compare it field by field against what the agent holds, and confirm any permit renewed in the prior sixty days has the updated number in the system.
6. Reconcile the MOHRE Employer Record Once a Year: I run this check for every client before their CT return is filed. Confirm that every employee on the payroll appears in MOHRE’s register, that salary figures match current employment contracts, and that no outstanding compliance alerts exist. The same discipline applies to VAT compliance records: both are checked at the same moment by any serious counterparty or lender. Approximately thirty minutes annually: the check that catches the silent discrepancy before it surfaces under commercial pressure.

A note on UAE national employees and GPSSA.  UAE national employees are enrolled in the General Pension and Social Security Authority, which requires employer contributions of 12.5 per cent of basic salary and employee contributions of 5 per cent, processed separately from the WPS salary payment. The GPSSA contribution is mandatory from the first month of employment for any UAE national on the establishment’s payroll. Verify current contribution requirements at the GPSSA portal before onboarding the first UAE national employee.