WPS Resolution 340's Day-2 Penalty Escalation: What Your Payroll Close Actually Needs to Look Like Now

An operations-first guide for HR and payroll teams already familiar with WPS. Last updated: September 2026.

You already know what Resolution 340 says: salaries clear the Wage Protection System by the 1st of the following month, there is no 15-day grace period, and the on-time threshold is 85%. What almost no one has written down is the operational consequence — what a payroll close calendar has to look like to hit a deadline that has zero slack in it. This guide skips the legal background (our WPS compliance guide covers that) and gets straight to the mechanics: the penalty clock, the calendar that beats it, and where automated checks stop a last-minute failure.

Informational only — not legal advice. This article is point-in-time (last updated September 2026) and assumes you know WPS basics. Verify penalty specifics and current rules with MOHRE (mohre.gov.ae) before acting.

The Day 2–21 penalty escalation

The reason the calendar matters is that the penalty clock starts almost immediately and escalates fast. Under the current framework, missing the deadline triggers a graduated sequence:

• Day 2 — notifications and warnings begin, logged against the establishment. The clock is already running the day after the deadline.
• Day 5 — new work permit applications are suspended. For any business hiring or renewing visas, this is the first stage that actually bites.
• Day 11 — administrative fines apply and the establishment can be reclassified to a lower MOHRE category, for repeat violations within a six-month window.
• Day 16 — for larger establishments (25 or more affected workers), a labour dispute can be registered automatically on employees' behalf.
• Day 21 — the most serious measures: asset attachment, a travel ban on the person in charge, and referral to Public Prosecution for persistent violation.

The key operational insight is in that first line: the clock starts on Day 2, so there is no quiet buffer after the 1st. Whatever your close process is, it has to land the money before the deadline, not test how much lateness is survivable.

Why "by the 1st" really means "before month-end"

Here is the trap that catches teams who read the rule too literally. The salary must clear WPS by the 1st. Clearing is not the same as submitting. Between your instruction and the salary actually landing in the employee's account through the WPS agent and the banking system, there is a processing lag of one to two working days.

That means a file submitted on the 1st has already missed the deadline — the money will not clear until the 2nd or 3rd. To clear by the 1st, funds and the SIF have to be with the WPS agent before month-end. Removing the 15-day grace period did not just move the deadline forward; it moved the real, operational cut-off to the last working days of the month. Plan to the clearing date, not the submission date. (For how the deadline itself is defined, see our UAE monthly salary deadline guide.)

A payroll close calendar, worked backward from the 1st

The only reliable way to hit a zero-grace deadline is to build the calendar in reverse, starting from when the money must land and adding each buffer back. A workable template (adjust the exact days to your bank and WPS agent):

• The 1st — salaries must have cleared. This is the fixed point everything else serves.
• ~29th–30th — bank/WPS processing buffer. Funds and the SIF are with the agent; the one-to-two-day processing window runs here. If the 1st falls on a weekend or public holiday, pull this earlier, because the deadline does not roll forward.
• ~28th — funding cutoff. The payroll account is funded in full. No transfer can clear that is not funded first.
• ~27th–28th — SIF submission cutoff and final sign-off. The validated file is submitted; the authorised approver has signed off after a variance review.
• ~26th–27th — payroll calculation and validation complete. Gross, allowances, overtime (rate-coded), and deductions are finalised and checked.
• ~20th–22nd — data cut-off. Attendance, overtime, leave, joiners, and leavers are locked. Anything after this moves to next cycle.

The single most important shift from the old grace-period era is that your funding and submission cutoffs are now in the last week of the month, not the first week of the next one. Teams that still fund payroll "early next month" are structurally late under Resolution 340.

What the 85% threshold means for partial payments and deductions

The compliance target is to transfer at least 85% of total wages on time. Two operational points follow:

• It is not a licence to underpay. The 85% is a company-level tolerance that accommodates legitimate cases — an employee on unpaid leave, a lawful deduction, a genuine mid-cycle exit — not a signal that paying most people is good enough. Any shortfall on an individual should be backed by a lawful, correctly coded reason (an approved deduction under the permitted categories and within the 50% cap — see our salary deductions guide), so the gap between gross due and gross paid is explainable, not a silent underpayment.
• Coding matters as much as paying. A partial payment with the correct deduction code reads as compliant; the same amount with no code reads as a shortfall. Getting the codes right is part of hitting the threshold cleanly.

Where pre-submission checks prevent last-minute failure

With no grace period, a SIF rejection discovered on the 30th is a genuine emergency — there is no time to rebuild and resubmit before the clearing window closes. The defence is to catch errors before submission, automatically, rather than discover them in the agent's rejection. The checks that earn their place:

• Header-to-detail reconciliation — the control-record total equals the sum of employee records, and the headcount matches.
• IBAN and identifier validation — bank details, labour-card/MOL numbers, and Establishment ID are present and correctly formatted, flagged if expired.
• Contract cross-check — each salary meets the registered contract and the AED 6,000 Emirati minimum where applicable.
• Completeness — every active employee is included, with NOPAY and deduction codes where needed.
• New-hire registration — anyone joined this cycle is registered and payable, not silently dropped.

Generating the SIF straight from payroll and validating it in advance is what turns the last week of the month from a gamble into a routine. If the file format itself is the weak point, our WPS SIF files explained guide walks through every record and code.

Payroll close calendar template

Adapt the days to your own bank and agent, but keep the backward-from-the-1st logic:

• ~20th–22nd: data cut-off — lock attendance, overtime, leave, joiners/leavers.
• ~26th–27th: payroll calculated, validated, variance-reviewed.
• ~27th–28th: SIF submitted, final sign-off.
• ~28th: payroll account funded in full.
• ~29th–30th: processing buffer (pull earlier for weekend/holiday month-ends).
• 1st: salaries cleared — confirm and archive the agent's acceptance.

The bottom line

Resolution 340 did not just change a date — it removed the buffer the whole payroll calendar used to rely on, and it starts penalising from Day 2. Hitting it reliably is an operations problem, not a legal one: build the calendar backward from the clearing date, move your funding and submission cutoffs into the last week of the month, back any shortfall with correctly coded deductions to hold the 85% threshold, and validate the SIF before it leaves the building. Do that, and the deadline stops being a monthly risk and becomes a routine you close early.

For the legal background this builds on, see our UAE WPS compliance guide and our UAE payroll process guide. Official rules are published by MOHRE at mohre.gov.ae and on the UAE Government Portal at u.ae.

Sources & references

This guide is based on the following official UAE sources, current at the time of writing:

• Ministerial Resolution No. 340 of 2026 — the MOHRE resolution that sets the 1st-of-the-following-month wage due date, removes the previous 15-day grace period, and raises the on-time compliance threshold to 85% of total wages. mohre.gov.ae
• MOHRE Wage Protection System guidance — the graduated enforcement sequence for late or missing wages, from warnings and work-permit suspension through fines, category downgrades, automatic labour disputes, and referral to Public Prosecution. mohre.gov.ae
• Central Bank of the UAE — WPS operating rules for banks, exchange houses, and financial institutions acting as WPS agents, including the salary information file (SIF) format and processing. centralbank.ae
• Federal Decree-Law No. 33 of 2021 and its executive regulations — the statutory basis for wage payment, permitted deductions, and the 50% cap on deductions from an employee's wage.
• UAE Government Portal — consolidated public guidance on WPS obligations for employers. u.ae

Penalty timing is described as it is commonly applied; MOHRE may apply measures differently depending on the establishment's history and circumstances. Where third-party summaries were consulted, the underlying official text was used as the authority.

---

Close payroll before month-end, every cycle

RadixHR generates and validates your WPS SIF before submission — header-to-detail reconciliation, IBAN and identifier checks, contract cross-checks, and completeness — so a rejection on the 30th never happens. See how it fits with RadixHR's payroll and compliance tools, or read how teams automate WPS end to end.

Book a demo →

---

This article is for general information only and does not constitute legal advice, and is point-in-time (last updated September 2026). WPS deadlines, thresholds, and the penalty sequence are set by MOHRE and the Central Bank of the UAE under Ministerial Resolution No. 340 of 2026 and related regulations, and are subject to change. Verify current requirements with MOHRE or a qualified adviser before acting.