Start with the obligations, not the feature list
Every vendor will show you an org chart, a leave calendar and a dashboard. Those are table stakes and they rarely differ enough to decide anything. What separates HR software in the UAE is whether it handles five statutory obligations correctly: wage protection, social insurance, end-of-service gratuity, nationalisation reporting, and document expiry. Everything else can be worked around. These cannot.
The practical way to evaluate is to take your own last payroll run and ask each vendor to reproduce it. Not a demo dataset — yours, with its allowances, its mid-month joiners, its expired documents. Most evaluation mistakes come from watching a clean demo and assuming your data will behave the same way.
1. Wage Protection System: file generation is not the hard part
The Wages Protection System, administered by MOHRE with the Central Bank, requires salaries to be paid through an approved agent using a structured Salary Information File. Almost every vendor can produce a SIF. The question is what happens before it is produced.
An employee with an expired Emirates ID silently drops out of the file. The submission succeeds, the run looks clean, and one person is not paid. You find out from a complaint, not an error message. Ask specifically: does the system validate record completeness, IBAN format, negative net pay and document expiry before submission, and does it block the run or merely warn?
Ask also how late or failed submissions are tracked. WPS non-compliance carries establishment-level consequences, so the audit trail matters as much as the file.
2. End-of-service gratuity: accrual, not a leaving calculation
Under Federal Decree-Law No. 33 of 2021, gratuity accrues at 21 days of basic wage for each of the first five years of service and 30 days per year thereafter, subject to a cap of two years' wage, with treatment differing between resignation and termination.
The common failure is software that calculates gratuity only when someone leaves. That produces a correct final payment and an incorrect balance sheet all year. Ask whether gratuity is carried as a live monthly provision, whether it reconciles to your finance figure, and whether basic wage is defined consistently across employees in the same role — inconsistent basic salary definitions are very hard to defend in an audit.
3. Social insurance and ILOE
The General Pension and Social Security Authority scheme applies to Emirati nationals, with employer and employee contributions tracked separately. Involuntary Loss of Employment insurance registration applies more broadly and needs maintaining as a compliance register.
Ask how the system identifies who is in scope. If nationality has to be flagged manually on each record, it will drift. Detection from the employee record is the difference between a register that stays accurate and one that is accurate on the day it was set up.
4. Emiratisation: the number you need is the forecast
Knowing your current position against target is useful the day before a review and not much use before that. What changes decisions is forward projection — your position in three months given approved requisitions and known notice periods.
Ask whether targets are calculated per establishment from live workforce data, and whether the system projects forward. A quarterly report you assemble by hand is not tracking; it is reporting after the fact.
5. Document expiry and the cost of finding out late
Emirates ID, passport, visa and labour card expiries all have downstream consequences, and most of them surface at payroll. Renewals need flagging with enough runway to act — 90, 60 and 30 days is a reasonable cadence — and they need assigning to whoever actually handles them, usually a PRO.
Ask what happens when a document expires despite the alerts. Does the employee drop out of the next WPS file silently, or does the run stop and tell you?
The questions most evaluations skip
Ramadan hours. The standard working day reduces while salary stays the same, so the derived hourly rate rises and hours that were not overtime last month now are. Systems holding eight hours as a constant under-record overtime for a full month. Ask how reduced hours are applied — as a calendar event that adjusts overtime thresholds, or not at all.
Air-ticket allowance. The entitlement builds monthly whether or not anyone claims it. Software that recognises the cost only when a ticket is booked understates what you owe. Ask whether it accrues as a liability.
Mainland and free zone together. If you hold entities under different licensing authorities, ask whether they can sit in one group and report together, with the correct wage protection arrangement and social insurance treatment applied per entity.
Arabic, properly. Ask to see the interface in Arabic rather than a screenshot of it. Full right-to-left support means layout, forms and reports render correctly — translated labels on a left-to-right layout is a different thing. If you issue employee letters, ask whether they can be produced bilingually in the format authorities accept.
What happens at migration. Historical gratuity accrual has to come across, not just current headcount. A vendor promising a two-week implementation is usually not migrating it. Six to eight weeks is realistic for a single entity of a few hundred people; multi-entity groups take longer.
Regional versus global platforms
Global HR platforms support the UAE. The question is how. In most, regional requirements are a localisation layer added to a system designed elsewhere — WPS becomes a report template, gratuity becomes a custom formula somebody configured. That works until the rules change or an edge case appears, at which point you are waiting on a vendor whose roadmap is set by a much larger market.
Regionally built software treats those requirements as core functions. The trade is usually breadth: a global platform may offer more in areas unrelated to compliance. The honest framing is that this is a genuine trade-off, and which side it falls depends on whether your risk sits in compliance or elsewhere.
The test that cuts through it: ask whether compliance behaviour is a configurable default or something that had to be constructed for you. Constructed things need maintaining, and you will be the one maintaining them.
A checklist to take into vendor calls
Bring your own last payroll run. Then ask each vendor to show you, on that data: the SIF validation before submission; the gratuity provision reconciled to a finance figure; the Emiratisation position with a three-month projection; a document expiry alert assigned to a person; an overtime calculation during Ramadan; and an air-ticket liability on the balance sheet.
Six things. If a vendor can demonstrate all six on your data, the rest of the evaluation is about price, service and fit. If they cannot, the feature list is not the thing to be discussing.