A UAE WPS SIF file is usually rejected for one of a few reasons: the SCR total doesn’t match the sum of the employee records (EDR), an invalid IBAN or bank routing code, a basic salary below the MoHRE contract value, an Establishment ID or labour-card error, or a filename that doesn’t match the date/time inside the file. Fix the flagged field, regenerate the file, and re-upload — ideally a few days before the deadline.
There are few worse feelings in payroll than uploading your SIF file the day salaries are due — and watching the bank bounce it back. Under the 2026 Wage Protection System rules, a payment that misses the 1st of the month is recorded as a delay, and enforcement escalates from day two — so a rejected file is a compliance problem, not just an admin one. The good news: almost every rejection comes down to a short list of causes, each with a clear fix.
First, what a SIF file actually contains
A SIF is a fixed-format file defined by the Central Bank of the UAE, with two record types that must agree with each other:
- SCR — Salary Control Record: one header row with your Establishment ID (MOL number), the pay period, the total number of employee records, and the total salary amount.
- EDR — Employee Detail Records: one row per employee, with their labour card number, IBAN and salary breakdown.
Most rejections happen because something in the EDRs doesn’t add up to the SCR header, or one field in one EDR is malformed. The bank’s WPS gateway validates the whole file and rejects it as one unit — so one bad row bounces the entire payroll.
The exact error message or code you see depends on your bank or exchange house and its WPS gateway — the wording varies, but the underlying reasons below are the same across all of them.
The most common SIF rejection reasons — and how to fix each
| Rejection reason | Why it happens | How to fix it |
|---|---|---|
| SCR total ≠ EDR records | The SCR header’s record count and total amount don’t exactly equal the sum of the employee rows — even a AED 0.01 difference bounces the file. | Don’t hand-build or edit SIFs in Excel. Generate from one locked payroll source so totals are computed once and can’t drift. |
| Invalid IBAN | A UAE IBAN must be 23 characters, start with "AE", and pass its check digits. Typos, or an IBAN not updated after an employee changed banks, fail silently. | Validate every IBAN at data entry; re-confirm bank details for recent joiners and anyone who switched banks. |
| Wrong bank routing code | The routing code of the receiving bank/exchange house in the EDR is incorrect or outdated. | Keep routing codes on a controlled list rather than free-typing them per employee. |
| Basic salary below the MoHRE contract | Under WPS 2.0 tightening, a basic salary even AED 1 below the registered MoHRE contract value can trigger rejection or a flag. | Reconcile each employee’s payroll basic against their MoHRE contract before you lock the run. |
| Establishment ID / labour-card error | An extra leading zero, a stray space, or a labour-card number not updated after a status change or renewal. | Source the Establishment ID (MOL number) and labour-card numbers from live HR records, not re-typed spreadsheets. |
| Employee not registered / status mismatch | An employee not correctly registered under your establishment, or whose labour-card status changed, is rejected in the EDR. | Set up new joiners with valid, current labour-card and MOL details before their first WPS run. |
| Filename ≠ data inside the file | The SIF filename encodes the establishment number and date/time, which must match the SCR record. A mismatch is an instant rejection. | Let your payroll system produce the filename in the exact required convention automatically, tied to the file’s contents. |
| Duplicate / already submitted | Re-uploading a file for a period you’ve already submitted (or a duplicate reference) is rejected. | Track submission status per period; only regenerate when you genuinely need to correct and resubmit. |
A 6-point pre-submission checklist
Before you upload, confirm:
- Totals tie out — SCR record count and amount = sum of the EDRs, to the fil.
- Every IBAN is valid — 23 chars, "AE", check digits pass; recent bank changes updated.
- Basic salary ≥ MoHRE contract for every employee.
- Establishment ID + labour cards are current and correctly formatted.
- Filename matches the date/time and establishment number inside the file.
- Submit early — at least 2–3 business days before the 1st, so a bounce doesn’t become a late payment.
How to stop SIF rejections for good
Most rejections trace back to the same root cause: the SIF is hand-assembled or re-keyed, so totals drift and fields go stale. The fix is to generate it from your payroll data, validated, in one step. That’s how HRX360 handles it:
- The SIF is generated from locked payroll — one frozen source of truth, so the SCR header and the EDR rows are computed from the same numbers and reconcile automatically.
- Bank details are validated up front — IBAN format (23-character UAE IBAN), account numbers and the MOL Personal Number are checked when you set up each employee, not at submission.
- The filename follows the required convention automatically, tied to the file’s own establishment number and date/time — so filename-vs-data mismatches don’t happen.
- A salary reconciliation review compares each run to the previous month, so anomalies are caught before you lock and generate the file.
HRX360 generates the WPS-ready file for you to upload to your bank or exchange house — it removes the manual formatting and the last-minute scramble. (Funding salaries on time and keeping employee data accurate is still on you — but the file itself stops being the thing that fails.) See how it works on the WPS payroll & SIF generator page, or read the 2026 UAE WPS rules to make sure you’re paying on the right deadline.
Stop fighting your SIF file every month
HRX360 generates bank-ready WPS/SIF files straight from locked payroll — totals that reconcile, IBANs validated, the right filename, every time. Book a demo and we’ll show you on a UAE-configured test account.
Frequently asked questions
Why does my UAE WPS SIF file keep getting rejected?
The most common reasons are an SCR total that doesn’t match the sum of the employee (EDR) records, an invalid or outdated IBAN, a basic salary below the MoHRE contract value, an Establishment ID or labour-card formatting error, or a filename that doesn’t match the date/time inside the file. Fix the flagged field, regenerate the file, and re-upload.
What is the SCR and EDR in a SIF file?
The SCR (Salary Control Record) is the file’s header — it holds the Establishment ID, pay period, total record count and total salary amount. The EDRs (Employee Detail Records) are one row per employee with their labour card number, IBAN and salary. The SCR totals must exactly equal the sum of the EDRs, or the file is rejected.
What is the correct IBAN format for UAE WPS?
A UAE IBAN is 23 characters, begins with "AE", and its check digits must validate. Typos, missing characters, or an IBAN left unchanged after an employee switched banks are common causes of rejection.
How early should I submit my SIF file?
Submit at least 2–3 business days before the due date (the 1st of the month under the 2026 rules), so there’s time to correct and re-upload if the bank rejects the file before it becomes a late payment.
Does a rejected SIF count as late payment in the UAE?
Yes — if the corrected file isn’t accepted by the due date, the payment is treated as delayed. Under Ministerial Resolution 340 of 2026, wages are due by the 1st of each month with no grace period, and enforcement escalates from day two.
Can HRX360 prevent SIF file rejections?
HRX360 generates the SIF from locked payroll so the SCR and EDR totals always reconcile, validates IBAN and MOL details at data entry, and produces the filename in the required convention automatically — which removes the most common causes of rejection. Full compliance still depends on funding salaries on time and keeping employee data accurate.
Note on sources
SIF validation rules are set by the Central Bank of the UAE and MOHRE; exact rejection codes and wording vary by bank or exchange house and their WPS gateway. Deadline and penalty rules reflect Ministerial Resolution No. 340 of 2026. This content is informational and not legal advice — confirm specifics with your bank, MOHRE, or a qualified advisor.