Blog — 2026-08-07
By Emad Yahya — web developer & IT systems engineer, Dubai
A WPS-compliant HR and payroll system in the UAE needs four things working together: employee and wage records that match what is registered with your labour authority; a salary file in the format your bank or exchange house expects — commonly called the SIF, the Salary Information File; submission through an approved agent inside the window the authorities set; and, underneath all of it, attendance and leave data accurate enough that the numbers in that file are actually true. The file is the easy part. The data underneath it is where UAE payroll usually breaks.
I'm Emad Yahya, a web developer and IT systems engineer in Dubai. I built the PSQ HR Platform that runs HR operations for Platinum Square Real Estate — onboarding, leave, documents and reporting in one place, integrated with the company's Microsoft 365 environment. That is the HR layer payroll depends on. It is not a WPS submission engine, and I am not going to pretend otherwise. This guide explains what a compliant flow involves, which part of it a custom HR system genuinely solves, and which part stays with your bank, your accountant or your payroll provider.
One caveat that applies to every sentence below: WPS rules, file specifications and deadlines are set by UAE authorities and implemented by the agents processing your payments, and they are revised over time. Treat this as a working explanation, not a compliance document. Confirm current requirements with MoHRE, your free zone authority and your bank before you rely on them.
WPS is an electronic salary transfer system that requires employers to pay employee wages through approved financial institutions, so that the authorities can verify wages were paid, in full and on time. Its stated purpose is verification — proof that wages were paid, rather than the employer's word for it.
In broad terms, mainland companies registered with the Ministry of Human Resources and Emiratisation fall in scope, and payments run through banks, exchange houses and other approved agents. Free zones typically operate their own arrangements. Which regime applies depends on where your company is licensed — the first question to settle before anyone designs a payroll process for you.
The consequence side matters too. Non-compliance is generally handled through the labour system rather than the banking one — late or missing salary files can affect a company's ability to process new work permits and other transactions, and penalties can apply. Thresholds, grace periods and penalty structures are published by the authorities and revised periodically. Ask your PRO or your bank, not a blog post.
A SIF — commonly expanded as Salary Information File — is the structured file submitted so a WPS payment run can be validated. It carries two kinds of record: one for the employer and the batch, one per employee. Typically it includes:
The field layout, encoding and validation rules are set by the authorities and implemented by the agent, so the bank or exchange house processing your file is the practical authority on the current specification — and specifications change. That is one half. The other half is the data underneath: an IBAN with a transposed digit, a day count that disagrees with the leave register, a leaver still sitting in the batch. Formatting is your bank's specification to hand you; the records are yours to get right.
Almost never at the file. In the small and mid-sized Dubai companies I see, payroll goes wrong in the week before the run, when someone reconciles attendance sheets, leave approved over email and a spreadsheet of salary changes into a single number. The recurring failures look like this:
Through one employee record that every process reads from and writes to. That is the design principle behind the HR platform I built. Onboarding is a structured workflow rather than a paper checklist, because a workflow leaves a trail. Leave carries balances and approval chains, because a balance in the system cannot drift from the balance in someone's head. Contracts, IDs and HR records sit in one central repository, because a document you cannot find is a document you effectively do not have.
Before that platform, HR at Platinum Square ran on paper, email threads and spreadsheets: slow onboarding, untracked leave balances, documents scattered across inboxes. Today it is one auditable source of truth for every employee record, with org-level reporting for management and paper-based HR processes eliminated company-wide. That is the layer that makes a payroll number defensible — days worked, days of unpaid leave and approved variable pay all coming from records nobody had to rebuild by hand.
On top of that layer, payroll tracking means salary records tied to attendance and leave, with exports for your accountant or payroll provider. To keep scope honest: the platform running today does not generate SIF files and does not transmit anything to an agent. It produces the numbers; the submission step stays with whoever handles your WPS channel.
In most cases, no — and here I will argue against extra scope. Many UAE SMEs already submit through their bank's WPS portal or through an exchange house, and that step works fine. Paying to rebuild a payment channel that is not broken is rarely the best use of a build budget.
The case for building it in is volume and repetition. If someone re-types hundreds of employee rows into a portal every month, generating the file from the system that already holds the data removes a whole class of error. If you go that way, get the current specification from the agent who will process the file, build validation against it, and run parallel submissions for a cycle or two before switching off the manual route.
Everything else — the layer that makes the numbers right in the first place — is ordinary build territory. A full HR platform covering attendance, leave, payroll tracking, documents and approvals is typically a 4–8 week build. A focused tool, such as a leave and attendance tracker alone, runs 2–4 weeks. Those are real delivery times from systems now in production in Dubai.
Whatever you end up buying or building, these are the questions I would put to any vendor — including me — before signing anything.
If you want a straight read on your own setup, describe your headcount, how attendance is captured today and who currently submits your salary file. I will tell you which parts are worth systemising and which are fine as they are, and if a build makes sense you get a fixed written quote within 24 hours.
WPS is the Wage Protection System — an electronic salary transfer system that requires employers to pay wages through approved financial institutions so the authorities can verify staff were paid in full and on time. Mainland companies registered with MoHRE generally fall in scope; free zones typically run their own equivalent arrangements. Confirm which regime applies to your licence with your authority or PRO, as the rules are revised over time.
A SIF, or Salary Information File, is the structured file submitted so a WPS payment run can be validated. It normally carries employer and batch details plus one record per employee — identifier, IBAN, pay period, days covered, and fixed and variable pay kept separate. The exact field layout and validation rules are set by the authorities and implemented by your bank or exchange house, so treat the agent's current specification as the source of truth.
No — and I would rather say that plainly than blur it. The PSQ HR Platform I built handles onboarding, leave, documents and reporting. Payroll tracking — salary records tied to attendance and leave, with exports for your accountant or payroll provider. Submission stays with whoever runs your WPS channel today. If you want SIF generation built into a new system, it is a scoped feature, and the format has to be confirmed against your bank's current specification before any code is written.
It depends on the free zone. Several operate their own wage protection arrangements through their authority rather than the mainland MoHRE process, and the requirements and file handling can differ. Check with your free zone authority and your bank rather than assuming the mainland rules apply to you.
That is the main thing it is good for. Payroll errors usually start upstream of the payroll sheet — unpaid leave approved over WhatsApp, mid-month joiners pro-rated by hand, overtime collected in three formats. A system where leave carries balances and approval chains, attendance is captured once, and every process reads from one employee record removes the manual reconciliation step where those errors are introduced.
It depends entirely on scope — a leave and attendance tracker is a different project from a full HR platform with payroll tracking, documents and approvals, and adding file generation for a specific bank changes it again. Send me your headcount and how payroll is handled today, and you get a fixed written quote within 24 hours.
HR System Development in Dubai — full service page · Custom Software Development in Dubai · Custom Software vs Off-the-Shelf for UAE SMEs