Most HR platforms are built somewhere else and translated. HROMS was built here, for here — and it shows in the places that matter.
We kept meeting the same HR director.
They had bought a well-known HR platform. It was expensive, it was polished, and it could do almost everything — except the things that actually kept them awake.
It couldn't calculate their Nitaqat band, so they ran it in a spreadsheet. It couldn't produce the wage file their bank wanted, so someone rebuilt it by hand every month. It didn't know that end of service in Saudi Arabia isn't one calculation but several, depending on why someone left. It printed payslips in English to a workforce that mostly read Arabic. And when the Ministry changed a rate — which it does, on a schedule — they had to raise a support ticket with a vendor eleven time zones away and wait for a release.
So we started from the other end. We took an open, proven enterprise platform used by thousands of companies worldwide — and we built the Kingdom into its foundations rather than bolting it on the side.
HROMS is what you get when compliance is the starting point instead of a localisation package.
GOSI rates step up every July. The Nitaqat constants change every year. The wage-file window was cut from sixty days to thirty in March 2025. On 15 April 2026, the very definition of a countable Saudi employee changed. In HROMS, none of those require a software release. Every rate, threshold, multiplier and formula constant is a dated record with a review history. When the Kingdom changes its mind, we change a number — and you can see exactly who changed it, and when.
Every change to the payroll engine ships with automated tests that assert the exact amount, to the halala. Not “it looks right.” The number. Every statutory calculation is written so that a labour lawyer who has never seen code can read it and check it against the article it cites.
No Saudi government system — GOSI, Qiwa, Mudad or Muqeem — publishes an open, self-serve API. Any vendor telling you they have “real-time Qiwa integration” should be asked to show you the credentials. We build the path that works on day one: generate the file, import the data, reconcile the numbers, and show you every discrepancy. It's less glamorous than an API and it's the thing that actually keeps you compliant.
The Ministry now uses automated analytics to detect fictitious Saudization. We will not build a feature whose only purpose is to make the count look better than reality — not because we're squeamish, but because it gets found, and the penalty is exclusion from Nitaqat entirely. HROMS is designed to make it easy to be genuinely compliant, and impossible to accidentally look like you aren't.
Every screen, every payslip, every contract, every government file, every letter — bilingual and right-to-left, from the first line of code. Not a language pack added in year two.
HROMS is built by a team that pairs senior software engineers with Saudi compliance analysts — people whose full-time job is to read the Ministry's circulars, verify the rates before they change, and translate labour law into a specification an engineer can build against.
Most HR vendors don't have this role. It shows in their products: we have seen a market-leading platform's public Nitaqat calculator use the wrong multiplier for employees with disabilities, and another vendor's help centre document the rules in detail and then tell the customer to go and use the government's website instead.
A beautiful dashboard on top of a wrong number is worse than useless.
We'd rather lose a deal than win it on a promise we can't keep.
Your HR system should belong to you.
Everything on this site is checkable. Start with the calculator — it uses the Ministry's real formula, and you can check it against theirs.