HR and payroll platforms evaluated against Saudi GOSI, Mudad, Wage Protection and Saudization requirements.
Payroll is the one system in a business that has to be right every single month, for every single person, with no tolerance at all. Everything else can be approximately right and corrected next quarter. Payroll cannot, and the people who find the error are your own employees.
In Saudi Arabia that ordinary difficulty is compounded by something specific: payroll here is not only a calculation, it is a set of filings. The calculation has to land correctly, and then it has to be represented correctly to social insurance, to wage protection, to the labour platform, and - if the establishment's Saudization position matters to its ability to operate - to the classification behind that. A global HR platform will do the calculation beautifully and know nothing about the filings.
That is the whole reason this page exists. International vendors publish deep material about talent, engagement and workforce analytics, and almost nothing about GOSI, Mudad, Wage Protection or Nitaqat, because those are not their market's problems. They are yours, and they are where Saudi payroll implementations actually fail.
Our interest, stated before the argument: Trustangle is an independent advisory firm. We deliver selection and implementation work, which is a genuine commercial interest in your decision. Where we hold a partnership or accreditation with a vendor named here, it is published on our partners page rather than implied in the copy. We do not earn a margin on your licence - which is what makes it possible for us to say that the HR module in the ERP you already own may be enough, and to point you at ERP, accounting and HR systems when it is.
The category is five layers that are sold together and fail separately.
Core HR - the employee record. Personal and contract data, position and reporting structure, documents and their expiry, and the organisational structure everything else hangs from. Unglamorous and load-bearing: every downstream error in this category traces back to a wrong record here.
Payroll. Earnings, deductions, allowances, end-of-service provisioning, the payroll run and its approval, the bank file, and the journal to the general ledger. Plus, in this market, the outbound compliance files - which is the part that distinguishes a payroll system that works here from one that merely calculates.
Time, attendance and leave. Rosters and shifts, clocking, overtime rules, leave entitlement and accrual, and absence. In operations with shift work this is where payroll accuracy is actually determined, long before the payroll run.
Talent - recruitment, performance, learning. Applicant tracking, onboarding, objectives and review cycles, training records. Valuable, but the layer most often bought first and used least, because it does not fail loudly when it is missing.
Employee and manager self-service. Requests, approvals, payslips, documents and letters. The layer that decides whether HR spends its month on administration or on anything else.
Two things make the overlap worse than it looks. Vendors in each layer have extended into the neighbouring ones, so a time-and-attendance product will show you payroll and a payroll product will show you recruitment, each competently enough to demonstrate. And ERP suites include an HR and payroll module, which is frequently sufficient and occasionally nowhere near. Which of those is true for you is a question about your workforce shape and your compliance exposure rather than about the software.
When you do not need this yet. A small, stable headcount on a single establishment with straightforward pay may be served perfectly well by an accountant and a bank file. And if the underlying problem is that employment data is wrong - contract terms that do not match what is paid, allowances with no policy behind them, job titles that exist in three variants - then a platform will industrialise that inconsistency. That is not a reason to do nothing; it is a reason to clean the employee master first, after which the software decision is both cheaper and much easier.
Every evaluation starts from your workforce and your obligations rather than from a feature grid, for a practical reason: at this scale the serious platforms all do the headline things, and the differences that decide the outcome are local ones that never appear on a comparison sheet.
How many employees, across how many establishments and how many nationalities. Shift work or not - the answer changes the shortlist. Which pay elements you actually run and which have written policy behind them. How compliance filings are produced today and by whom. What your ERP already includes and what its contract says. Whether your Saudization position is a constraint you are managing actively. Who will own payroll configuration after go-live - and whether that person exists yet.
KayanHR is the platform we implement in this category today. One named platform is the honest picture of what we deliver here rather than a shortlist dressed up as a market survey - and it is the reason this page spends its length on the obligations rather than on a product grid. What that platform does is described on its own page, in its vendor's own terms; nothing is claimed for it here.
Where the fit is not right - and for an organisation standardising on one suite it frequently is not - we say so and point at ERP, accounting and HR systems, where the HR module of a suite you may already own is evaluated alongside the rest of it. That is genuinely the better answer for some organisations, and we would rather say it here than after an invoice.
Compared here are the layers of the category, not products against each other - a product comparison would be a vendor capability claim, and those are not made on this page.
| Layer | Fails as | Decisive local question |
|---|---|---|
| Core HR | Wrong records everywhere downstream | Does one joiner reach every system once |
| Payroll | A visible error, every time | Can it produce the compliance files natively |
| Time & attendance | Silent payroll inaccuracy | Do your shift and overtime rules configure |
| Talent | Quietly unused | Is anyone actually going to run review cycles |
| Self-service | HR's month spent on letters | Arabic, on a phone, for every employee |
We publish the drivers, not a price. What decides the bill: per-employee licensing and how your headcount plan multiplies it; the number of establishments and whether they are configured separately; compliance file configuration and testing, which is the line most often missing from a first quote and the one that decides whether the system works here at all; employee data cleansing and migration, including historical balances and end-of-service provisions; time-clock hardware and integration if attendance is in scope; parallel payroll runs, which are non-negotiable and are labour on both sides; training for HR, for managers and for employees; and the run cost, meaning who owns payroll configuration afterwards.
The three-year total is what matters. Parallel running and compliance configuration are the two lines buyers underestimate most.
Structural only: institutions and platforms by their function, with no rate, no threshold and no deadline - those change, and a stale number in a content column is worse than none. Confirm current requirements with each authority.
Social insurance - GOSI. The General Organization for Social Insurance administers social insurance in the Kingdom: establishment and employee registration, contribution calculation and reporting, and occupational hazard coverage. A payroll system that cannot reflect GOSI registration status per employee and produce contributions consistent with it will be reconciled by hand every month.
Wage protection - WPS. The Wage Protection System exists so that wages actually paid can be matched against what is contractually due. The practical selection question is not "does the vendor mention WPS" but whether the system generates the required file natively, from the same run that produced the payslips, with employee identifiers that match the establishment's registered records. Mismatched identifiers are the single most common cause of a rejected submission, and they originate in core HR, not in payroll.
Mudad. Mudad is the platform used by establishments in the Kingdom for payroll and wage disbursement processes connected to wage protection compliance. Whether a platform integrates with it, exports to it, or leaves you re-keying into it is a concrete, checkable difference between candidates - and one that international HR vendors generally cannot speak to at all.
Qiwa and the labour file. Qiwa is the Ministry of Human Resources and Social Development's platform for establishments' labour services: contracts, establishment files and workforce services. Employment data therefore lives in two places by design, and keeping the HR system and the labour file consistent is an operating process, not a one-time migration.
Saudization - Nitaqat. The Saudization programme classifies establishments by their workforce composition, and that classification affects an establishment's access to labour services. The system requirement that follows is specific and frequently missed: you need to be able to see and forecast the position, not just report it. A platform that cannot model the effect of a planned hire or exit turns a managed constraint into a monthly surprise.
Workforce documentation and residency. Iqama status, document expiry and related establishment services are administered through Ministry of Interior platforms, and expiring documents are an HR operational risk before they are a compliance one. Document expiry tracking with real escalation is a core-HR requirement here in a way it is not in most markets.
Workforce development. The Human Resources Development Fund administers national programmes supporting employment and training of Saudi nationals; where an establishment participates, the supporting evidence comes out of its own HR records.
Labour law mechanics. End-of-service benefit entitlement, working hours, overtime, leave and termination are governed by the labour framework administered by the Ministry of Human Resources and Social Development. No figure, formula or rate is reproduced here - the point for system selection is that these have to be configurable and auditable, because the rules are the authority's and not the vendor's.
Calendar. The Hijri calendar governs public holidays and features in employment terms; Ramadan carries its own working-hours treatment. A payroll calendar that cannot express both calendars will be adjusted by hand every year, and adjusted-by-hand is where payroll errors live.
Arabic. Employment contracts, payslips and employee-facing documents in Arabic, with right-to-left support, on the devices employees actually use. An operating requirement in this market, not a preference.
Personal data. Employee records are among the most sensitive personal data an employer holds. The Personal Data Protection Law and its implementing regulations, with the Saudi Data and AI Authority as competent authority, govern processing, access and transfer - including transfer to a vendor's own support teams.
Discovery starts with your workforce shape and your filing obligations, because those determine the shortlist more than any feature does. A written shortlist with the reasoning visible, including the case for the HR module in the ERP you already own. Demonstrations scripted against your pay elements and your compliance files, run on real structures rather than vendor demo data - this is where candidates separate, and it is the step most often skipped. A commercial review of the three-year picture. Then implementation: employee master cleansing first, payroll configuration second, parallel runs until two consecutive months reconcile to the ledger and to every outbound file, and only then cutover. Training covers HR, managers and employees, because self-service that nobody uses is a cost with no benefit.
We do not publish a number. What sets it: headcount and number of establishments, how clean the employee master is, how many pay elements have written policy behind them, whether time and attendance is in scope, and how many parallel runs are needed before everyone is comfortable. Parallel running is the stage that sets the go-live date, and cutting it short is the most expensive saving available in this category. We give a dated plan after discovery.
Licence plus compliance file configuration and testing plus data cleansing and migration plus attendance hardware and integration plus parallel runs plus training for three audiences plus the internal owner of payroll configuration afterwards. Section 5 lists the drivers. A quote that prices only the licence is not a three-year number.
Not as a property of the product - as a property of how it is configured and what it is connected to. The obligations that bite are social insurance through GOSI, wage protection and the labour framework through the Ministry of Human Resources and Social Development, the payroll and wage disbursement path through Mudad, the establishment's labour file through Qiwa, workforce documentation through Ministry of Interior platforms, and employee personal data under the Personal Data Protection Law with the Saudi Data and AI Authority as competent authority. Where the platform is hosted, who can access employee data from where, and whether that is acceptable, is a question to put to the vendor in writing and to check against current requirements - not one to take from a sales deck or from this page.
We publish the shortlist and the reasoning with every recommendation, including what we rejected and why. In this category the rejection reason is very often "could not produce the compliance files natively", and that is worth seeing written down.
Usually. The common shape is a specialist HR and payroll platform posting a journal to the ERP that stays the financial record - and that works well. The question to settle first is which system owns the employee master. Two systems that both think they do produces exactly the joiner-and-leaver drift that breaks compliance filings, and it is a design decision rather than a product feature.
The heading asks for numbers. This section has none, and we would rather say so plainly than publish a figure we cannot evidence. What we would tell you to demand of any adviser here, including us: how many Saudi payrolls they have actually taken live, at what headcount, how many parallel cycles they ran, whether they have personally configured a wage protection submission that was accepted, and the name of one client who will take your call. Ask in a meeting, where it can be checked.
We do not name clients without their written agreement, and payroll clients are among the least likely to consent to a logo wall. References relevant to your headcount and your sector are offered during evaluation, by name.
Case material is shared under the same rule as section 10: relevant, named, and only with the client's agreement. We do not publish anonymous percentage improvements, because an unattributable number is not evidence.
Testimonials appear here only when a real client has written and approved one. There are none invented in the meantime.
Published and maintained on the partners page, which is the single source of truth. We do not restate them in body copy, where they go stale silently and where a claim is hardest to check.
ERP, accounting and HR systems - the suite view, and the right starting point if you are standardising on one platform. ERP consulting - where the suite-versus-specialist question is actually decided. All solutions and platforms and independent software comparisons.
Bring your headcount by establishment, your list of pay elements, and one month's compliance submissions however they are currently produced. Book a decision session - or start with an impartial assessment - and we will tell you, plainly, whether this is a platform decision, a configuration problem in the system you already own, or an employee-master cleanup that has to happen either way. It is frequently the last one.
