What is WPS and why has the pressure on payroll increased?
The Wage Protection System (WPS) is MOHRE’s electronic monitoring mechanism, jointly run with the Central Bank of the UAE, that requires private-sector employers to pay wages through registered banks or exchange houses and to submit a Salary Information File (SIF) each cycle. MOHRE reconciles that file against its own labour records; the moment it doesn’t match, the file is rejected and the clock on compliance keeps running regardless.
What changed under Ministerial Resolution No. 340 of 2026, effective 1 June 2026:
- One unified due date. Wages for the preceding month are now due on the first day of each calendar month — no more 15-day grace window.
- An 85% minimum transfer threshold. Employers must pay at least 85% of total wages due on time, even where lawful deductions apply, or the payment is treated as non-compliant.
- New hires are in scope immediately. The old 30-day exemption for new employees has been removed, so onboarding payroll now carries first-cycle WPS risk from day one.
None of this changes the mechanics of building a SIF. What it changes is the cost of getting the file wrong. A rejection that used to be absorbed inside a 15-day cushion now has to be caught and fixed before the first of the month — full stop.
MOHRE itself has been explicit about the intent behind the update. In an official statement carried by the state news agency WAM in June 2026, the Ministry said:
“An establishment is considered compliant if it transfers at least 85% of the total wages due within the specified timeframe. This reflects a flexible and balanced approach that takes into account the operational realities of businesses while ensuring the protection of workers’ rights.”
— MOHRE (Ministry of Human Resources and Emiratisation), official statement via WAM, June 2026
MOHRE also confirmed the system processes more than AED 37 billion in wage payments every month, and described its enforcement approach as “gradual and balanced”: electronic monitoring and notifications first, giving employers time to rectify their status, before administrative measures apply. That sequencing is worth noting — it doesn’t remove the risk, but it does mean the first sign of trouble is usually a system notification, not a penalty. Payroll teams that treat that first notice as the moment to fix the underlying control (not just resubmit the file) are the ones who stay off MOHRE’s radar for repeat violations.
Where WPS submissions actually go wrong
Most SIF rejections are not compliance failures in the legal sense — they’re control failures in the process. In our experience running monthly payroll for employers across the UAE, the same five issues account for the overwhelming majority of rejected or delayed files:
- SCR-to-EDR mismatches. The Salary Control Record (SCR) totals — record count and total amount — must equal the sum of the Employee Detail Records (EDR) exactly. A one-dirham rounding difference is enough to bounce the entire file, not just the affected line.
- Labour card and Establishment ID errors. An extra leading zero, a stray space, or a labour card number that hasn’t been updated after a status change will fail MOHRE’s registry match.
- IBAN and bank routing errors. Wrong or outdated IBANs — common after an employee switches banks and doesn’t notify payroll in time — cause silent rejections that surface only after the deadline has passed.
- Filename and date mismatches. The date or time embedded in the filename has to match the SCR data inside it; a copy-paste from a template file is a frequent, entirely avoidable cause.
- Deduction logic that quietly breaches the 85% threshold. Loan repayments, penalties, or advances applied without checking the net effect against total wages due can push a payslip below the new minimum-payment rule without anyone noticing until after submission.
None of these are exotic. They’re the kind of error that a rushed, end-of-month, single-reviewer process reliably produces — which is exactly why a structured pre-submission checklist matters more than a smart SIF-generation tool on its own. Our earlier guide on UAE WPS payroll risks every employer should know covers how these control gaps build up.
A rejected SIF is rarely just a paperwork problem. Each bounce pushes the payroll deadline closer to (or past) the unified due date, forces a same-day correction and resubmission cycle, and pulls payroll, HR, and often finance into unplanned remediation work. The knock-on effects are operational as much as regulatory: delayed salary payments, employees chasing HR for answers, and a payroll team firefighting instead of running the next cycle’s controls. Treating rejected SIFs purely as a compliance issue misses the business cost sitting underneath it.
The WPS pre-submission checklist (UAE 2026) for payroll accuracy before submission
Run this before every SIF leaves the building, not after a rejection notice comes back.
Seven checks to run before every SIF
1. Reconcile totals, not line items
Confirm the SCR total and record count match the EDR sum precisely — to the fils, not just approximately. Automate this reconciliation where possible; it is the single highest-value control in the whole process.
2. Cross-check every labour card number against the current MOHRE registry
Do this for every employee whose status changed in the cycle — new joiners, label/role changes, offer letter amendments — not just as a one-time onboarding step.
3. Validate IBANs against the bank’s own confirmation
Validate against the bank’s confirmation, not payroll master data alone. Bank changes are an HR notification problem as much as a payroll one. Build a monthly IBAN-change report into the pre-submission cycle.
4. Test every deduction against the 85% rule before finalising the payslip
Run the check at the individual employee level, not just at company-wide average. A single high-deduction case can breach the threshold even when the overall payroll looks compliant.
5. Lock the filename convention to the SCR content
Generate filenames programmatically from the same data source as the SCR — never manually typed, never copied from a prior month’s file.
6. Confirm new joiners are included in the current cycle, not deferred
With the 30-day exemption gone, any employee active before the cycle cutoff needs to be in this month’s SIF — treat “not yet fully onboarded in the system” as a payroll risk, not an HR delay.
7. Submit ahead of the first-of-month deadline, with a buffer for one resubmission cycle
Because there is no grace period anymore, the practical deadline for internal sign-off should be several working days before the 1st — not on it.
A simple pre-submission workflow
The checklist above maps to a straightforward sequence — useful as a visual reference for the payroll team or as a control map to sit alongside the SIF process:
- Payroll inputs received
- Labour card & IBAN validation
- SCR vs EDR reconciliation
- 85% threshold testing
- Final approval
- SIF submission
What OPS sees in practice
OPS expert view: The real vulnerability in WPS compliance isn’t the SIF format — most payroll systems generate that correctly. It’s the gap between when payroll thinks the data is final and when it actually is: a late bank change, an unconfirmed new joiner, a deduction added after the last review. The unified due date removes the safety margin that used to absorb those late changes. Payroll teams that treat “input freeze” as a hard, enforced deadline — not a suggestion — are the ones who stop rebuilding SIFs at 11pm on the 30th.
In our experience, most WPS issues originate from process discipline failures rather than payroll calculation errors. Organisations that establish formal payroll cut-off dates, enforce data-freeze controls, and reconcile payroll inputs before SIF generation experience significantly fewer compliance incidents.
| Area | Common issue | Operational risk | Control |
|---|---|---|---|
| SIF reconciliation | SCR/EDR totals reconciled manually, late in the cycle | Full-file rejection close to the deadline | Automated reconciliation run before final approval |
| New joiner data | Labour card/status not confirmed before first payroll | Registry mismatch, rejected file | New-joiner data lock at input cut-off |
| Bank details | IBAN changes reported informally or late | Silent transfer failure | Monthly bank-detail verification report |
| Deductions | Loan/advance deductions applied without a threshold check | Breach of the 85% minimum-payment rule | Per-employee 85% test before payslip lock |
| Submission timing | File built and submitted close to the due date | No time to fix a rejection before non-compliance | Internal deadline set days ahead of the statutory date |
Manual review vs a controlled pre-submission process
| Approach | What it catches | What it misses |
|---|---|---|
| Manual, single-reviewer check | Obvious data-entry errors, gross total mismatches | Threshold breaches at individual level, late bank-detail changes, filename drift |
| Automated SIF generation only | Formatting and file-structure errors | Business-logic errors: deduction thresholds, missing new joiners, stale labour card data |
| Structured pre-submission checklist with reconciliation controls | Both format and business-logic errors, before submission | Requires discipline to run every cycle, on time, without shortcuts |
Frequently asked questions
What is the WPS deadline in the UAE now?
Under Ministerial Resolution No. 340 of 2026, effective 1 June 2026, wages for the preceding month are due on the first day of each calendar month — a single unified date for private-sector employers, with no 15-day grace period.
What happens if a SIF is rejected after the deadline has passed?
The rejection doesn’t pause the compliance clock. If the corrected file and payment aren’t completed by the statutory due date, the employer is exposed to the same enforcement risk as a late payment — including permit suspensions, fines, and potential travel-ban measures against the establishment, per MOHRE’s enforcement framework. Compliance check required: confirm current enforcement sequencing and any cure period with MOHRE guidance at time of use.
Does the 85% rule apply even when deductions are lawful?
Yes — the resolution requires at least 85% of total wages due to reach the employee on time even where lawful deductions (loans, advances, penalties) apply. Payroll needs to test this per employee, not on a company-wide average.
Are new employees exempt from WPS in their first month?
No, not anymore. The previous 30-day exemption for new hires has been removed, so first-cycle payroll for new joiners is now in scope from the start.
What your payroll team should do differently this month
The June 2026 changes don’t require a new payroll system. They require tighter timing and a pre-submission control that catches errors before MOHRE does. That means moving the SIF reconciliation earlier in the cycle, treating new-joiner data as submission-critical from day one, and testing deduction logic against the 85% rule at the individual employee level — every cycle, not just when something has already gone wrong.
This is exactly the kind of control-and-timing discipline that managed payroll outsourcing is built around: not replacing the calculation, but removing the gap between “the file looks right” and “the file is right.” If payroll currently rests on one person or a stack of manual workarounds, our note on the signs it’s time to outsource your payroll is a useful next read.
OPS helps UAE employers implement payroll risk management controls that reduce WPS submission risk, improve payroll accuracy, and support ongoing WPS compliance for UAE employers. Speak to OPS about a payroll compliance review before your next payroll cycle. Visit ops.ae.
Short answer: This WPS pre-submission checklist for UAE employers in 2026 matters because a payroll file is ready for WPS submission only when the Salary Information File (SIF) totals reconcile exactly with the payroll register, every labour card number and IBAN matches MOHRE and bank records, at least 85% of gross wages due are covered by the transfer, and the file will land before the unified due date — now the first day of the following month under Ministerial Resolution No. 340 of 2026, effective 1 June 2026. Miss any one of these, and the file either bounces or triggers a compliance breach that follows the company, not just the payroll cycle.
Since 1 June 2026, that last sentence has more teeth than it used to. MOHRE’s overhaul of the Wage Protection System removed the old 15-day grace period, introduced a single unified payment date across the private sector, and closed the 30-day exemption that used to give new hires a buffer. For payroll specialists, this is the update that matters most this year — and it changes what “good enough” pre-submission review looks like. If you have not yet mapped the new timeline, our UAE WPS Update 2026 payroll checks guide covers the change in detail.
Key takeaways
- Unified salary due date: wages are now due on the 1st of the following month, with no grace period.
- The old 15-day grace period has been removed entirely.
- An 85% minimum payment threshold now applies at the individual employee level, even where lawful deductions apply.
- New hires are covered from their first payroll cycle — the 30-day exemption no longer exists.
- A structured pre-submission review process is now the main safeguard against rejection and compliance exposure.
Sources
MOHRE / Ministerial Resolution No. 340 of 2026 — reported via Khaleej Times, Morgan Lewis legal briefing, and Deloitte Middle East. MOHRE official statement via WAM (UAE state news agency), June 2026 — reported by Emirates 24|7. SIF rejection mechanics — cross-checked across multiple UAE payroll providers (Zoho Payroll, Yomly, HR Chronicle). Compliance check required: direct MOHRE circular text for Resolution No. 340 of 2026, and current enforcement/cure-period sequencing for late or rejected SIFs, should be confirmed against primary MOHRE guidance before external publication.