WPS compliance: the payroll mechanics and the penalties

WPS is not a single monthly click. It is a data pipeline. Each pay cycle, an employer generates a Salary Information File (SIF) from its payroll or HR system, submits it through a MOHRE-approved agent bank or exchange house, and that agent validates and forwards it into the Central Bank system MOHRE reads to confirm payment. The registration, the file format and the transmission window are where most WPS breaches actually originate, not, as most summaries imply, from an employer simply forgetting to pay.

Key Takeaways

• WPS registration requires an active MOHRE establishment file plus a corporate account with a CBUAE-recognised agent bank or exchange house, and commonly takes one to two weeks before the first file can be submitted.
• The Salary Information File (SIF) is a plain-text file with two record types: one Salary Control Record (SCR) covering the whole batch, and one Employee Detail Record (EDR) per worker.
• A mismatched IBAN, a wrong-length field, or an SCR total that doesn't reconcile to the sum of the EDR lines gets the entire file rejected, not just one employee's line.
• The payroll and employment cost guide covers the 85%-of-value compliance threshold and the day-2-to-day-21 penalty ladder that applies once a file doesn't land on time.

Registering the establishment for WPS

Before any monthly file can be submitted, WPS registration is a one-time setup that sits on top of two things a company already has by the time it is hiring: an active MOHRE establishment card and a UAE trade licence. What it adds is a corporate bank account opened specifically with a WPS-approved agent: one of the banks or exchange houses the Central Bank recognises for this purpose. Major UAE banks including Emirates NBD, ADCB, Mashreq and FAB, and exchange houses such as Al Ansari Exchange, are commonly used as WPS agents. That account has to be held in the company's exact legal name as registered with MOHRE: a mismatch here is a routine reason first-time registrations bounce back.

Registration itself runs through MOHRE's own portal (via UAE Pass or a corporate login), where the establishment authorises WPS for its account, and then through the chosen agent's own onboarding, where the bank links that establishment's MOHRE ID to its wage-transfer service. Coordinating two separate institutions is why registration commonly takes something like one to two weeks rather than a same-day activation: worth starting well before the first payroll run, not the week salaries are due. That waiting window is also a sensible point to run current staff through the UAE gratuity calculator, so end-of-service accruals are already reconciled against basic salary before WPS payroll go-live locks the same figures in place.

Building the salary information file each pay cycle

Once registered, the recurring monthly task is generating a SIF: a plain-text file the payroll or HR system produces, structured around exactly two record types.

The first line is always a Salary Control Record (SCR), effectively the file's cover sheet. It carries the employer's MOHRE-issued establishment ID, the pay period being reported, the total number of employees included, and the total salary value of the batch.

Every line after that is an Employee Detail Record (EDR): one per employee, carrying their labour card number, their bank account (or wage card or exchange house account) details, and the salary breakdown: basic pay plus each individual allowance component.

The format is exacting by design. Fields have to appear in the sequence the Central Bank specifies, IBANs have to be the correct length and format, and (critically) the total declared on the SCR line has to match the sum of every EDR line beneath it. A file that fails any of these checks is rejected outright; there is no partial acceptance where nine correct employee lines process and one bad line gets flagged separately. That is the mechanical reason a single stale IBAN, or a labour card number HR updated but payroll did not, can hold up an entire company's wage run rather than one employee's payment.

Transmitting the file: the agent bank or exchange house step

The completed SIF does not go to MOHRE directly. It is submitted to the WPS-approved agent bank or exchange house the establishment registered with, usually through that agent's own WPS portal, or a dedicated upload interface built into payroll software the agent has certified.

The agent runs its own preliminary validation before anything moves further: checking the file structure, confirming the totals reconcile, and flagging obvious formatting errors. Only a file that clears this first pass gets forwarded into the Central Bank's WPS infrastructure, which executes the transfers to each employee's bank, wage card provider, or exchange house account, and which also feeds MOHRE's compliance monitoring.

This two-step relationship (employer to agent, agent to Central Bank system) is why the practical fix for a rejected file is almost always the same: correct the data at source, in payroll or HR, not on the bank's upload screen, then resubmit. The agent has no authority to alter an employer's declared figures.

The monthly timing window

The wage due date itself: the first of the month for the preceding month's pay, per the payroll and employment cost guide: is the compliance deadline MOHRE measures against. It is not, in practice, the day to submit the file.

Settlement across a batch of employee accounts spread across different banks, wage card providers and exchange houses is not instantaneous once a file is accepted. Agent banks need processing lead time to route funds correctly, which means a SIF submitted on the due date itself carries real risk of the underlying transfers landing after the window MOHRE checks: even though the employer technically filed "on time." Employers who consistently clear the 85%-on-time-by-value threshold build in a buffer, submitting a few business days ahead of the first of the month rather than treating that date as the submission deadline, precisely because the SIF's acceptance and the wages' actual arrival are two different events on two different clocks.

What MOHRE does with a submitted file

Submission is not the end of the process. MOHRE reconciles the wage figures in an accepted SIF against the salary declared in each employee's registered employment contract on its own system. Where the two numbers diverge: a raise processed in payroll but never updated in the MOHRE contract record is the common case: MOHRE flags the file and the employer has to correct and resubmit.

This is the same reconciliation gap the payroll and employment cost guide raises from the gratuity side: a wage breakdown that drifts from the registered contract creates a problem in two systems at once, not one. Keeping the MOHRE contract record, the SIF's basic-versus-allowance split, and the gratuity base aligned is one exercise done consistently, not three separate reconciliations run by three different people at three different times.

The monthly WPS checklist

Running this pipeline by hand against that checklist every single pay cycle is exactly the kind of recurring, rule-bound task WiserMonks' payroll feature set is built to take over, generating and reconciling the SIF automatically rather than rebuilding the same checks manually each month.

Frequently asked questions

What is a Salary Information File (SIF)?

A SIF is the plain-text file UAE payroll systems generate each pay cycle for WPS. It contains one Salary Control Record summarising the batch (establishment ID, period, employee count, total value) followed by one Employee Detail Record per worker, listing bank details and the basic-pay-plus-allowances breakdown that both the agent bank and MOHRE check.

Do we submit the SIF to MOHRE or to our bank?

To the bank or exchange house registered as your WPS agent, not directly to MOHRE. The agent validates the file's structure and totals, then forwards it into the Central Bank system that executes the transfers and feeds MOHRE's compliance monitoring. MOHRE never receives a raw file directly from the employer.

Why would a WPS file get rejected even though every employee was paid correctly?

Rejection is usually structural, not financial: a mismatched IBAN length, a labour card number that doesn't match MOHRE's record, or an SCR total that doesn't exactly equal the sum of the EDR lines. These fail validation before any money moves, regardless of whether the underlying payroll calculation itself was correct.