Since 1 June 2026, UAE private sector employers must pay salaries through WPS by the 1st of each month for the previous month's work. Paying at least 85% of wages on time counts as compliant. Late payers get warnings from day 2, a block on new work permits from day 5, fines from day 11 and legal action from day 21.
- From 1 June 2026, salaries are due by the 1st of each month under Ministerial Resolution No. 340 of 2026, with penalties escalating from day 2 to day 21 of a delay.
- WPS requires salaries to be paid through an approved agent using a structured Salary Information File, cross-checked automatically against your registered workforce at MOHRE.
- The most common cause of a failed submission is an employee whose Emirates ID, visa, or labour card lapsed, which excludes them from the file.
- Consequences attach to the establishment, not to the size of the error, so a handful of excluded employees can restrict new work permits for the whole business.
- Five controls prevent nearly all issues: a document expiry pipeline, pre-submission validation, maker-checker approval, timeliness tracking, and bank return-file reconciliation.
- Multi-entity groups carry more risk because exposure is per establishment, and a healthy group view can hide one entity that is late.
Every registered employer in the UAE, private sector, free zone, or mainland, is required to pay salaries through the Wages Protection System (WPS). It sounds like a simple compliance checkbox, but in practice, WPS touches almost every part of how a company runs payroll: which bank accounts are eligible, how salary files are formatted, what counts as a "delay," and what MOHRE does when something goes wrong. In 2026, with tighter enforcement and more automated cross-checking between the Ministry, banks, and the Central Bank, understanding WPS properly is no longer optional for HR and finance teams.
What is the UAE Wage Protection System (WPS)?
WPS is an electronic salary transfer system introduced by the UAE Ministry of Human Resources and Emiratisation (MOHRE) in partnership with the Central Bank. Its purpose is straightforward: make sure employees are paid the correct amount, on time, through a traceable channel. Employers do not hand cash or cheques to staff. Instead, they generate a Salary Information File (SIF), a structured text file listing every employee, their Emirates ID or labour card number, bank or exchange house account, and the exact salary amount, and submit it through an approved agent, typically their bank or an authorised exchange house.
Once submitted, the agent transmits that file to the Central Bank system, which cross-references it against each company's registered labour force in MOHRE's database. If an employee is missing from a payroll run, paid less than their contracted wage, or paid late, the system flags it automatically. There is no manual review step where a discrepancy can quietly slip through.
What is a WPS SIF file, and why do files get rejected?
The SIF file format is unforgiving. It expects a precise structure, exact field lengths, and specific encoding. A single misaligned column, a rounding error in a salary figure, or an employee record using an outdated labour card number can cause the entire file to be rejected, not flagged for correction, rejected outright. When that happens with a manual, spreadsheet-based payroll process, the company has to regenerate and resubmit the file, which can push the transfer date past the compliance deadline even though the original attempt was on time.
This is the single biggest reason companies running payroll through Excel or a generic accounting package fall out of compliance: not because they intended to underpay anyone, but because the file itself failed validation and nobody caught it until after the deadline had passed.
What is the WPS salary deadline in 2026?
From 1 June 2026, private sector employers must pay salaries through WPS, or another system approved by the Ministry of Human Resources and Emiratisation (MOHRE), by the 1st of each Gregorian month for the previous month's work. This comes from Ministerial Resolution No. 340 of 2026, which replaced Resolution No. 598 of 2022.
An employer counts as compliant if it pays at least 85% of total wages due by the deadline. An employee isn't treated as unpaid if they receive at least 85% of their salary and the rest is a legally documented deduction.
Employers can use a payroll provider or other third party to process salaries, but they stay legally responsible for paying on time.
| Excluded from the deadline |
|---|
| Workers in an active labour dispute |
| Employees reported absent from work |
| Employees on unpaid leave |
| Foreign workers paid from overseas by non-UAE entities |
| Short-term work permits under three months |
| Banks, places of worship, fishing boats and citizen-owned public taxis |
Do final settlements and gratuity go through WPS?
WPS compliance does not stop at monthly salary. Final settlements, including end-of-service gratuity, must also be processed and, in most cases, verified through the same wage protection framework before a labour card can be cancelled and an exit permit issued. This means a miscalculated gratuity figure does not just create an HR headache, it can delay an employee's exit process and create a compliance gap on the employer's record at exactly the moment MOHRE is closing out that person's file.
To check an employee's end-of-service amount, use our UAE gratuity calculator.
WPS for multi-entity groups
Groups with multiple trade licences, common in construction, hospitality, and retail, must run WPS compliance separately for each legal entity, even if all entities share one HR team and one bank. That means one payroll error in a five-entity group can technically flag only one entity as non-compliant, while the others remain fine, but from a governance standpoint, most boards want a single, consolidated view of compliance risk across the whole group. Spreadsheet-based processes almost never provide that view in real time; someone has to manually reconcile it entity by entity, usually after the fact.
A single company can manage submission with discipline and a spreadsheet. A group cannot, because the exposure is per establishment: each entity has its own file, its own deadline, and its own consequence, and a group-level view that looks healthy can conceal one entity that is late.
The failure we see most often in groups is an employee transferred between entities who appears in two submissions or neither. Preserving one employee record across entities, rather than terminating and rehiring, prevents it structurally. Our note on consolidating multi-entity payroll covers the operational side, and multi-currency payroll across the GCC covers the cross-border case.
WPS compliance checklist for 2026
Mature payroll operations in the UAE today share a few common traits, regardless of company size:
- SIF file generation is automated directly from the payroll engine, not built manually in a spreadsheet template.
- Every new hire is checked against MOHRE registration status before they are added to a payroll run, so nobody gets missed.
- Payroll teams get an alert days before a submission deadline, not on the day of.
- Gratuity and final settlement calculations are automated per emirate and contract type, removing manual formula errors.
- Compliance status is visible at the group level, across every entity, in one dashboard, not five separate exports.
How AmalOps Handles This
AmalOps generates WPS-certified SIF files directly from live payroll and HR data, so the file that gets submitted to your bank is built from the same records as the employee's contract, attendance, and leave, no manual re-typing, no version mismatch. Submission deadlines are tracked per entity, with alerts before a cutoff is at risk, and gratuity is calculated automatically per country and contract type the moment an offboarding is initiated. For multi-entity groups, compliance status rolls up into a single view without losing the entity-level detail regulators or auditors will eventually ask for.
See how AmalOps payroll generates WPS files and tracks the 1st-of-month deadline for every entity.
5 controls that keep you WPS compliant every month
| Control | What it prevents |
|---|---|
| Document expiry alerts at 90, 60 and 30 days | Employees dropped from the salary file because their Emirates ID or labour card expired |
| Pre-submission validation | Rejected files from missing fields, bad IBANs or unusual pay amounts |
| Maker-checker approval | Errors nobody else reviewed before money moved |
| Timeliness tracking | Missing the 1st-of-month deadline |
| Bank return-file reconciliation | Rejected transfers that are never reissued |
Understanding the rules is the easy half. The organisations that never receive a wage protection issue are not the ones with the most knowledgeable HR team; they are the ones with controls that operate whether or not anyone is paying attention.
Document expiry pipeline. The single most common cause of a failed or incomplete submission is an employee whose identity document lapsed. A renewal pipeline flagging expiries ninety, sixty, and thirty days ahead, with assigned ownership to the PRO team and escalation when a date passes, removes the entire failure mode.
An anomaly scan can flag expired Emirates IDs before they block a WPS payment.
Pre-submission validation. The file should be checked before it leaves, not after it bounces: record completeness, account detail validity, employees excluded because of documentation, negative or implausible net amounts, and variance against the previous month beyond a set threshold.
Maker-checker approval. A different person approves the run than prepared it. This is standard control practice and it should survive automation rather than being replaced by it.
Timeliness tracking. Submission dates recorded and monitored against the statutory window, so lateness is a reported metric rather than an incident.
Return-file reconciliation. Bank return files imported and matched, so rejected transfers are identified and reissued in the same cycle rather than discovered when an employee reports a missing salary.
What are the penalties for late salary payment in the UAE?
The asymmetry worth understanding is that consequences attach to the establishment, not to the value of the error. A small number of employees excluded from a file because their documents lapsed can result in restrictions on new work permits, which in a hiring cycle affects the whole business rather than the payroll team.
| Days after the due date | What happens |
|---|---|
| Day 2 | Electronic monitoring flags the delay; warning notices are sent to the employer |
| Day 5 | New work permits are suspended; the employer is formally notified to pay |
| Day 11 | Administrative fines; repeat violations within six months can mean downgrading to the third category |
| Day 16 | Labour disputes can be opened for affected workers; wider permit suspensions, especially for employers with 25 or more workers or in construction, transport, storage, security, cleaning and recruitment |
| Day 21 | Legal escalation: enforcement orders, asset seizures and travel bans on responsible officials; repeat cases at companies with 50 or more workers can go to the public prosecutor |
Source: Ministerial Resolution No. 340 of 2026, effective 1 June 2026.
This is why framing wage protection as an administrative task understates it. The realistic exposure is an operational constraint arriving at an inconvenient moment, which is a different order of risk from a correction, as we set out in the real cost of payroll errors.
Where automation genuinely helps
Three specific places. Generating the submission file directly from the payroll register, so no re-keying occurs between calculation and submission. Blocking employees with lapsed documentation from the file automatically, with a resolution queue rather than a silent exclusion. And scanning each run against history for anomalies that pass every rule-based check, which is the class of error that otherwise reaches employees, discussed in AI anomaly detection in payroll.
Verifying the current requirements
Wage protection rules, submission windows, approved agent arrangements, and penalty structures are periodically updated by the relevant authorities, and free zone arrangements can differ from mainland. The guidance here describes how the system works and where employers commonly fail. Confirm the current requirements applicable to your establishment and licensing authority, and take professional advice on your specific circumstances, before relying on any figure or deadline stated here.
WPS compliance in 2026 is less about understanding the rules, most HR and finance leaders in the UAE know them well by now, and more about removing the manual steps where those rules quietly get broken. A SIF file that fails validation, a new hire missed off a run, a gratuity figure calculated on an outdated formula: these are not intent-to-violate problems, they are process problems. Fixing the process is the only durable way to stay compliant as headcount and entity count grow.
Sources
The 2026 rules above are summarised from the following reports of Ministerial Resolution No. 340 of 2026. Check them against MOHRE's own announcement, and confirm with your free zone authority how they apply to free zone companies.