10 Questions to Ask Before Buying an HRMS

Why HRMS shortlists get decided on the wrong evidence

Most HRMS shortlists are built from three artefacts: a demonstration, a feature matrix and a price. All three are produced by the vendor. The demonstration runs on clean data in a single-entity tenant. The feature matrix rewards whoever ticks the most boxes rather than whoever can generate a compliant wage file for your fourth licensed entity. The price covers the scope the vendor assumed, which is rarely the scope you have.

The outcome shows up in the research. Sapient Insights Group’s 27th Annual HR Systems Survey, drawing on 3,318 organisations across 59 countries and more than 25 million employees, found that over 25% of organisations fell short of their implementation expectations, and that 23% did not meet their adoption expectations. ISG’s HR Tech Survey Report, published in November 2025 from more than 200 global HR, IT and business leaders, found that 52% now report measurable HR technology return, up from 46%, and that fully integrated HR ecosystems deliver roughly twice the return of siloed ones. Both datasets are global. No comparable GCC-specific study is published, so treat them as direction rather than local benchmark.

What they point at is the same thing. The variables that decide whether an HRMS works are settled before signature, in questions a standard demonstration is not built to answer. The ten below are written to close that gap. Each is phrased as a demonstration request, because a vendor can agree to almost any requirement in a meeting and can only show a working system once.

The 10 questions to ask before buying an HRMS

1. Which statutory calculations does the system perform, and on which salary base?

The base matters more than the calculation. Under Article 51 of Federal Decree-Law No. 33 of 2021, UAE end-of-service gratuity for an eligible foreign full-time worker is calculated on the basic wage: 21 days’ basic wage for each of the first five years of service and 30 days for each subsequent year, subject to the statutory conditions and the overall cap of two years’ wages. Where an employee’s basic wage is lower than their gross remuneration, configuring the calculation against gross pay rather than basic wage can materially overstate the gratuity liability. It does so quietly, every month, inside the number the CFO reports.

Saudi Arabia is a different calculation, not a regional variant of the same one. According to the Ministry of Human Resources and Social Development, the Saudi end-of-service award is generally calculated at half a month’s wage for each of the first five years and one month’s wage for each subsequent year, using the last wage as the basis rather than basic pay alone. Where employment ends by resignation the entitlement is reduced on a service-based scale, nothing below two years, one third from two to five years, two thirds from five to ten and the full amount from ten, subject to the statutory rules and exceptions under the Saudi Labour Law. A system that treats end of service as one configurable rule will get one of the two countries wrong.

The salary base is not consistent across the region either, which is why “which base” has to be asked per country rather than once. The UAE runs on basic wage. Saudi Arabia and Qatar both run on the last wage, though Qatar narrows it to the last basic wage under Article 54 of Law No. 14 of 2004, while the Saudi base is broader than basic pay. Oman runs on the last basic wage. Bahrain still has a wage base, but it is applied differently: the employer contribution is a percentage of monthly wages as the Social Insurance Organisation defines them, paid monthly, rather than a figure calculated at termination. Five countries, five answers to what looks like one configuration field.

The employee population also matters, because Article 51 gratuity applies to the foreign full-time worker rather than to everyone on the payroll. Eligible UAE nationals must be registered under the applicable UAE pension and social-security regime, within the registration period GPSSA sets and with financial consequences for late registration. GCC nationals working in the UAE are generally covered through the Insurance Protection Extension System, with contributions determined under the pension rules of their home country and administered in coordination with GPSSA. The system therefore has to distinguish nationality, applicable pension authority and contribution rules rather than applying expatriate gratuity logic to every employee, which is where end-of-service and final settlement accuracy stops being a payroll detail and becomes a reported liability.

Ask for: a live calculation for one of your own mid-service leavers, in every country you operate in, with the salary base visible on screen.

Worry if: gratuity is described as fully supported and the demonstration uses the vendor’s sample employee.

2. Can the system hold every jurisdiction we operate in, at the same time?

Most GCC groups are not in one regime. A single UAE group can run mainland entities under the federal labour law, free-zone entities administered by their zone authority, and a DIFC or ADGM entity under its own employment law. DIFC replaced end-of-service gratuity with a defined-contribution workplace savings regime in February 2020. Separately, since DIFC Law No. 1 of 2024 took effect on 1 March 2024, DIFC employers have also had to top up a Qualifying Scheme for eligible UAE and GCC nationals registered with GPSSA where their pension contributions fall short of the equivalent amount. No top-up is required where that shortfall is less than AED 1,000. ADGM sits under its own employment regulations again.

Nationality then splits the population inside each entity, and the alternative savings scheme splits it once more. Employers who have moved staff onto the voluntary alternative end-of-service benefits scheme, introduced under Cabinet Resolution No. 96 of 2023 and in effect from 1 November 2023, carry two things for the same employee: a frozen historical entitlement and a live subscription. MOHRE is explicit that enrolled workers “will keep the gratuity they earned so far (prior to subscription to the new Scheme)”. A system that cannot hold a closed balance alongside an active contribution will either lose the balance or misstate the liability.

Ask for: one payroll run containing one employee from each regime and each population you actually have, processed together, in one cycle.

Worry if: separate tenants, databases or company codes per jurisdiction end up fragmenting approvals, audit trails, reporting or statutory outputs so that your team has to consolidate them by hand. Company codes are a legitimate architecture; manual consolidation on top of them is not. What managing payroll across multiple entities actually requires is one set of controls, not several copies of the same one.

3. How does the system produce a compliant wage file for each entity?

Wage protection is not a reporting feature. It is the mechanism by which an employer is found compliant or not. MOHRE requires private-sector establishments to pay wages monthly through approved banks, financial institutions and exchange houses, and the UAE Government puts the accountability plainly: “Paying wages on the due date is the responsibility of every employer.”

The due date itself changed recently, which is why this question needs asking now rather than at renewal. For establishments subject to MOHRE’s Wage Protection System, Ministerial Resolution No. 340 of 2026, effective 1 June 2026, requires wages for the preceding Gregorian month to be due on the first day of the following Gregorian month, and repealed Ministerial Resolution No. 598 of 2022. For WPS compliance purposes an establishment is treated as compliant where at least 85% of the total wages due are transferred by the due date, raised from the previous 80% threshold, subject to the resolution’s own rules on lawful deductions, exclusions and enforcement. The resolution applies directly to establishments licensed with MOHRE; free-zone employers should confirm the applicable payment and submission requirements with their relevant free-zone authority. Saudi Arabia operates a separate wage protection regime under the Ministry of Human Resources and Social Development, with its own platform and submission mechanics.

The deadline is also different in every country, which is the part that catches multi-country groups. Oman requires wages to be transferred within three days of the end of the wage period under Ministerial Decision No. 729/2024, effective 16 December 2024. Qatar files through the Ministry of Labour with a reported seven-day window. Bahrain files through the Labour Market Regulatory Authority’s Expatriate Management System, and its enhanced wage protection system became mandatory in January 2026 with administrative penalties from February 2026. Kuwait covers all private-sector workers with no minimum company size. One payroll calendar cannot serve all of them, so the question is whether the system holds a separate submission clock per country or expects your team to remember which is which.

Two consequences for the evaluation, and both are covered in more depth in UAE WPS compliance and salary deadlines. The file has to be produced per licensed entity, not per group. And an 85% threshold measured on the first of the month compresses the approval, exception-handling and file-generation sequence into a working window that is shorter than most groups’ current process. Test the sequence, not the output format.

Ask for: a wage file generated for your second and third entities, from data you supplied, including the approval step that precedes generation, and one file for each country in your footprint rather than one for the group.

Worry if: wage file generation is described as an export that the payroll team reformats afterwards, or one submission calendar is offered for the whole region.

4. Who can see, change and approve payroll data, and what does the audit trail record?

Payroll is the point at which HR data becomes financially and legally consequential, which makes access control a governance question rather than an IT preference. Three things are worth establishing before the contract: who can change a salary, who has to approve it before it reaches a wage file, and whether those are ever the same person in any entity.

Then test the record itself. An audit trail that logs that a field changed is not the same as one that records the previous value, the new value, the user, the timestamp and the approval that authorised it. The second is defensible in a labour dispute or an audit. The first is a log file. The same discipline underpins employee record integrity in the GCC, where the audit trail is often the only evidence that a change was authorised at all.

Ask for: the audit record of a retrospective salary change and of a reversed payment, presented as a report a non-technical auditor can read, not a database query.

Worry if: the audit trail is available on request from support.

5. Where does our employee data live, and how does that meet the PDPL?

The UAE Personal Data Protection Law, Federal Decree-Law No. 45 of 2021, came into force on 2 January 2022. According to the UAE Government, it allows an individual to “request for corrections of inaccurate personal data and to restrict or stop the processing of his personal data”, and it sets out requirements for the cross-border transfer and sharing of personal data. If you hold a DIFC entity, the DIFC Data Protection Law, DIFC Law No. 5 of 2020, applies there instead. ADGM entities fall under the ADGM Data Protection Regulations 2021. One group can therefore owe duties under more than one regime at once, out of one employee database.

For a CIO this converts into three specific requests rather than a security questionnaire, because a questionnaire tests whether the vendor has a policy and a demonstration tests whether the product can execute it.

Ask for: the hosting location and the list of roles holding administrative access to production data; a demonstration of how a correction request is executed and evidenced; and the written position on cross-border transfer where support, hosting or backup sits outside the jurisdiction.

Worry if: data protection is answered with a certificate instead of a process.

6. What does the integration actually involve, and who owns the mapping?

ISG found that fully integrated HR ecosystems deliver approximately twice the measurable return of siloed implementations, which is the strongest available argument for making integration a first-round question rather than a phase-two problem. In practice three interfaces decide the answer: general ledger posting and cost-centre mapping into finance, single sign-on and identity provisioning, and the time and attendance feed from whatever devices are actually installed on your sites.

What separates vendors is not whether an integration exists. It is who owns the mapping when your chart of accounts changes, and whether the interface is a supported product with a published specification or a script written once during implementation by someone who has since left the project.

Ask for: the interface specification, a named example of the same integration running in production, and a written statement of who maintains the mapping after go-live.

Worry if: the answer is that the system integrates with everything, and no specification follows.

7. How does the system absorb a statutory change after go-live?

This is the question buyers ask least and regret most. Count the changes across the region in roughly two years. In the UAE, the wage protection threshold moved from 80% to 85% and the payment due date was unified from 1 June 2026. Saudi Arabia’s Social Insurance Law requires cohort-specific configuration: for workers covered by the new system who had no prior qualifying subscription period before 3 July 2024, the pension contribution rate for both employer and employee rises progressively from 9% to 11% in half-point annual increments beginning in the second year, reaching 11% in 2028. Employers have to determine which social-insurance regime applies to each employee rather than applying a single GOSI rate across the whole Saudi workforce. Bahrain’s employer social insurance share rises one percentage point every year towards 17% under Law No. 14 of 2022, and its enhanced wage protection system carried penalties from February 2026. Oman introduced a three-day wage transfer rule in December 2024, phased new Social Protection Fund contribution branches in through 2024 and 2025, and has a savings system already legislated for July 2027. Qatar amended its Labour Law by Law No. 9 of 2026, in force 25 July 2026.

Every one of those is a configuration change that somebody has to make, on a date, correctly, and several of them recur annually without any decision on the employer’s part. The evaluation question is who: the vendor, as part of the subscription, or you, as a chargeable change request. Get the answer in writing, because it is the difference between a subscription and a retainer. Oman is the useful test case, because the July 2027 commencement is already known, which means a vendor can be asked today how it will be handled.

Ask for: the last three statutory changes the vendor shipped in your countries, with release dates, and confirmation of whether customers were charged for them.

Worry if: the vendor simply says the system is fully compliant, without explaining which statutory rules it maintains, how changes are deployed, and which compliance responsibilities remain with you as the employer.

8. What does the implementation require from us?

The research here is unusually consistent. Sapient Insights Group’s 27th Annual HR Systems Survey found that only 7% of organisations allocate the recommended 20% of project budget to comprehensive change management, and that organisations practising adaptive change management were roughly twice as likely to exceed expectations on implementation budget (23% against 8%), adoption (20% against 12%), timeline (18% against 10%) and resourcing (16% against 8%).

None of that is about software. It is about whether the buyer understood what they were agreeing to supply. So the useful version of “how long does implementation take” is a different question: what do we have to give you, and which decisions must we settle before you can configure anything? That is also the point at which what HRMS implementation readiness actually requires stops being the vendor’s problem and becomes yours.

Ask for: the employee master data field list you must populate, the policy decisions that must be settled before configuration begins, the named client-side roles required and the hours expected from each.

Worry if: an implementation timeline is quoted before anyone has seen your entity structure.

9. What is inside the total cost, and what creates a new charge?

Licence cost is the part that is easy to compare, which is exactly why vendors compete on it. The cost that decides the five-year number is usually somewhere else: an additional legal entity, an additional country, a second payroll run inside one month, an off-cycle final settlement, a new report, a new interface, a non-production environment, statutory account administration in each jurisdiction, and support outside contracted hours.

Procurement is better served by a trigger list than by a discount. A named trigger can be forecast against your entity roadmap. A discount cannot.

Ask for: a five-year cost model with every charge trigger named, built against your actual entity and country roadmap rather than today’s headcount.

Worry if: the quote arrives as a single line.

10. What happens to our data if we leave?

Ask it before signature, because it becomes unaskable afterwards. Establish the export format for employee master data, historical payroll results and the audit trail; whether that export is self-service or a chargeable service; the notice period; and what assistance the vendor is contractually obliged to give a successor system. Then confirm your own statutory record-retention obligation in each jurisdiction you operate in, and check that the exit terms let you meet it.

Ask for: a sample export file and the exit clause, both before contract signature.

Worry if: exit is described as something no customer has ever needed.

The 10 questions, the evidence to demand and the answer that should worry you

Table 1. The ten questions mapped to the buying-committee member who should own each one, the evidence that settles it, and the answer that indicates the question has not been tested. Source: gulfHR.

The six GCC countries, side by side

The reason question two matters more than its position on most evaluation scorecards is that a single GCC group commonly spans several statutory regimes at once. The six GCC states do not operate one common end-of-service model. The UAE alone can involve federal labour-law entities alongside DIFC and ADGM entities, which is why it is broken out below. Bahrain moved covered non-Bahraini workers to an SIO-funded end-of-service model in March 2024, and Oman has legislated a savings system for non-Omani workers with commencement currently scheduled for July 2027.

Bahrain takes the most structurally different approach. Since 1 March 2024, end-of-service benefits for covered non-Bahraini private-sector workers are funded through monthly employer contributions to the Social Insurance Organisation rather than relying solely on an employer-funded gratuity payment at termination. The employer contribution is 4.2% of monthly wages for the first three years of service and 8.4% thereafter, and the SIO pays the benefit. Salary definitions still matter, so the system has to hold Bahrain’s contribution and benefit rules separately from the UAE, Saudi Arabia, Qatar and Oman. Service completed before that date remains under the Private Sector Labour Law, Law No. 36 of 2012, and is claimed from the employer, so one Bahraini employee can carry a legacy entitlement and a live monthly contribution at the same time.

Oman is on a timer. Article 61 of the Labour Law issued under Royal Decree 53/2023 keeps end-of-service at not less than one basic wage per year of service, explicitly until the savings system under the Social Protection Law comes into force, and Royal Decree 60/2025 deferred that commencement to July 2027. Any system bought this year will meet that change inside its first contract term. That is a question you can put to a vendor today, about a change that is already on the statute book.

Table 2. The six GCC countries, each stated from its own jurisdiction’s source, with the UAE’s four jurisdictions nested beneath it. A group with entities in two of those four UAE jurisdictions is running two statutory models from one employee database. Sources: Federal Decree-Law No. 33 of 2021 and MOHRE (UAE); Morgan Lewis on Ministerial Resolution No. 340 of 2026; DLA Piper and Clyde and Co on DIFC Law No. 1 of 2024; Saudi Ministry of Human Resources and Social Development; Fragomen and Lockton on GOSI; Qatar Law No. 14 of 2004 via ILO NATLEX and Hukoomi; Kuwait Law No. 6 of 2010 via ILO NATLEX; Bahrain Social Insurance Organisation and Labour Market Regulatory Authority; Oman Social Protection Fund and Royal Decrees 53/2023 and 60/2025.

Verify your own position before relying on this

What each member of the buying committee should be testing

Four people are usually accountable for an HRMS decision and they are not evaluating the same product. Giving each of them explicit ownership of specific questions is what stops the group defaulting to the demonstration everyone watched together.

Table 3. Question ownership by buying-committee member. Source: gulfHR.

What gulfHR sees in practice

Four patterns come up repeatedly in HR and payroll selection and implementation work across the GCC. None of them is a software defect. All four are decided during evaluation, which is why they belong in a buying guide rather than an implementation one.

Table 4. gulfHR expert view. Observed patterns from HR and payroll selection and implementation work in the GCC, presented as practitioner observation rather than measured research.

Where gulfHR fits

gulfHR is an enterprise HR and payroll platform and HRMS software built for the UAE and the wider region rather than adapted from a global template, and it is designed for the kind of complexity the ten questions above are trying to expose: multiple legal entities, multiple jurisdictions, mixed national and expatriate populations, and approval chains that have to hold across all of them.

Where configured, the platform can support payroll processing per licensed entity, statutory calculation logic held separately per jurisdiction, role-based access with approval gates ahead of wage file generation, an audit trail across employee and payroll changes, leave and absence management, time and attendance, employee self-service and reporting for HR and Finance. gulfHR is hosted on Microsoft Azure with enterprise-grade security and is ISO 27001 certified. Which statutory calculations run natively in your configuration, and which are configured during implementation, should be confirmed during scoping rather than assumed from a feature list, including gulfHR’s.

gulfHR’s core operating base is the GCC, with clients located across 16 or more countries. What matters in an evaluation is not the size of that list but the distinction behind it, and it is a distinction worth demanding of any vendor: which countries are supported in the product, which have actually been implemented, and which would need to be configured for your specific statutory requirements. Ask for that split in writing, from every vendor on your shortlist, gulfHR included.

If you are still assembling criteria rather than questions, the buyer’s checklist for HR, Finance and IT covers the UAE-specific requirements in more depth, and multi-country GCC payroll covers what changes when a second country is added.

Frequently asked questions

What is the most important question to ask before buying an HRMS?

Which statutory calculations the system performs, and on which salary base. In the UAE, end-of-service gratuity is calculated on basic wage under Article 51 of Federal Decree-Law No. 33 of 2021, so where an employee’s basic wage is lower than their gross remuneration, a system configured against gross pay can materially overstate the liability. It is the only question on the list whose wrong answer produces a wrong number in the accounts every month rather than an inconvenience.

Who should be on the HRMS buying committee?

At minimum the CHRO or HR Director, the CFO or Finance Director, the CIO or IT Director, and a procurement or evaluation lead, with the payroll manager involved in any test that touches a calculation. Each should own specific questions rather than attending the same demonstration, because they are accountable for different failures. Table 3 above sets out a workable split.

How many vendors should be on an HRMS shortlist?

Fewer than most processes run, and each tested harder. Three vendors each asked to demonstrate your real scenarios will separate more cleanly than six vendors each giving a standard demonstration, because the discriminating evidence is entity structure, statutory base and approval design, and producing that evidence takes vendor effort you cannot ask of a long list.

Is a demonstration enough, or should we ask for a proof of concept?

A demonstration is sufficient if you supply the data and the scenarios. Ask for a mid-service leaver, a transfer between two of your entities, an employee in a different jurisdiction and an unusual allowance, all processed in one cycle. If a vendor cannot run your cases in a demonstration, that is itself the finding, and a proof of concept is worth the cost only when the integration or the entity model is genuinely unusual.

Can one HRMS handle UAE mainland, free zone and DIFC entities together?

It can, but this has to be demonstrated rather than assumed, because the three jurisdictions do not share an end-of-service regime. Mainland and free-zone entities operate gratuity under the federal labour law, while DIFC has run a defined-contribution workplace savings regime since February 2020 and, since DIFC Law No. 1 of 2024, also carries an employer top-up obligation for eligible UAE and GCC nationals whose pension contributions fall short. Ask for all three in one payroll run.

How different are end-of-service rules across the GCC?

Different enough that “does the system handle end of service” is not a usable question. The UAE calculates 21 then 30 days per year on basic wage. Saudi Arabia uses half a month then one month per year on the last wage and reduces the award on resignation. Qatar provides not less than three weeks’ remuneration per year on the last basic wage under Article 54. Oman provides not less than one basic wage per year until its savings system commences, currently scheduled for July 2027. Bahrain funds the benefit through monthly employer contributions to the Social Insurance Organisation for covered non-Bahraini workers rather than an employer payment at termination. And in Kuwait the formula should be confirmed with the Public Authority of Manpower rather than taken from any secondary summary. Table 2 sets all six countries out side by side.

Bring your hardest cases to the demonstration

Sources

1. Federal Decree-Law No. 33 of 2021 on the Regulation of Employment Relations, Articles 51 to 53, UAE Legislation portal (accessed 7 September 2026).
2. Wages Protection System, UAE Ministry of Human Resources and Emiratisation (accessed 7 September 2026).
3. Payment of wages, UAE Government portal, u.ae (accessed 7 September 2026).
4. UAE Introduces New Wage Protection System Resolution Effective 1 June 2026, Morgan Lewis, May 2026 (accessed 7 September 2026).
5. Voluntary Alternative End-of-Service Benefits Scheme goes into effect by Cabinet Resolution, UAE Ministry of Human Resources and Emiratisation, 1 November 2023 (accessed 7 September 2026).
6. DIFC Employment Law Amendments: Changes to DEWS and End of Service Gratuity, DLA Piper, March 2024 (accessed 7 September 2026).
7. Data protection laws, Federal Decree-Law No. 45 of 2021 and DIFC Law No. 5 of 2020, UAE Government portal, u.ae (accessed 7 September 2026).
8. Emiratisation Targets, UAE Ministry of Human Resources and Emiratisation (accessed 7 September 2026).
9. End of service award, Saudi Ministry of Human Resources and Social Development, Knowledge Centre (accessed 7 September 2026).
10. Labour Law No. 14 of 2004, Article 54, State of Qatar, official English text via ILO NATLEX (accessed 7 September 2026).
11. Inquire about a company’s WPS subscription, Hukoomi, Qatar Government portal (accessed 7 September 2026).
12. Labour Law No. 6 of 2010, State of Kuwait, via ILO NATLEX (accessed 7 September 2026).
13. Wage Protection Systems in the GCC, International Labour Organization, November 2025 (accessed 7 September 2026).
14. End of service gratuity for non-Bahrainis, Bahrain Social Insurance Organisation (accessed 7 September 2026).
15. Wage Protection System Guideline, Bahrain Labour Market Regulatory Authority, October 2025 (accessed 7 September 2026).
16. Contribution rates payable by the worker and employer, Sultanate of Oman Social Protection Fund (accessed 7 September 2026).
17. Labour Law, Royal Decree 53/2023, Article 61, and Royal Decree 60/2025 amending the Social Protection Law, Sultanate of Oman, via Decree (accessed 7 September 2026).
18. Saudi Arabia: Amended Social Security Contributions for Saudi Nationals, Fragomen, 27 August 2025 (accessed 7 September 2026).
19. Impact of DIFC Amendment Law No. 1 of 2024, Clyde and Co, May 2024 (accessed 7 September 2026).
20. Employers registration, and End of Service of GCC Nationals under the Insurance Protection Extension System, General Pension and Social Security Authority (accessed 9 September 2026).
21. Recruiting in free zones, UAE Government portal, u.ae (accessed 9 September 2026).
22. 27th Annual HR Systems Survey Report, Adaptive Change and Implementations segment, Sapient Insights Group, November 2024 (accessed 7 September 2026).
23. 2025 HR Tech Survey Report, ISG, November 2025 (accessed 7 September 2026).