Qiwa-Ready HR Software for Saudi Arabia
Qiwa authenticates your employment contracts; GOSI collects contributions on a different wage base; Mudad receives what you actually paid. Saudi compliance failures rarely come from any one of those — they come from divergence between them. NeuralHR.AI generates all three from a single payroll run so they cannot drift apart.
Quick facts
- Qiwa operator
- Saudi Ministry of Human Resources and Social Development
- Qiwa handles
- Contract authentication, work permits, transfers, Nitaqat band
- GOSI
- Social insurance contributions on the contributory wage
- Mudad
- Monthly wage protection filing
- Muqeem
- Iqama and residency lifecycle
- Most common audit finding
- Wage divergence between Qiwa, GOSI and Mudad
- NeuralHR.AI coverage
- Qiwa workflow support, native GOSI and Mudad
- Runs alongside
- UAE WPS payroll in the same tenant
What Saudi employers need to get right
Key takeaways
- ✓Employment contracts for expatriate workers must be authenticated through Qiwa, and the authenticated terms are compared against what payroll actually pays.
- ✓GOSI contributions are calculated on a contributory wage — typically basic salary plus housing allowance — that is defined differently from the wage filed through Mudad.
- ✓Saudi payroll therefore maintains several parallel wage bases, which is why generalising a single-country payroll system into the Kingdom usually fails.
- ✓Qiwa surfaces your Nitaqat band, and a falling band restricts work permits and employee transfers before it produces any financial penalty.
- ✓Muqeem governs the iqama lifecycle; an expired iqama affects the employee's legal right to work and blocks other establishment transactions.
- ✓The reliable fix is generating GOSI, Mudad and contract data from one payroll run rather than reconciling three systems after the fact.
The four Saudi platforms and what each one holds
| Platform | What it governs | Wage basis used | NeuralHR.AI support |
|---|---|---|---|
| Qiwa | Contract authentication, work permits, transfers, Nitaqat band | Contracted wage | Workflow support — holds contract data and flags divergence from payroll before filing |
| GOSI | Social insurance registration and contributions | Contributory wage (typically basic plus housing) | Native — calculates contributions by nationality and prepares the monthly filing |
| Mudad | Wage protection filing | Paid wage | Native — filed from the same payroll run that produces GOSI figures |
| Muqeem | Iqama issuance, renewal, exit and re-entry | Not wage-based | Tracks iqama expiry per employee and raises renewal tasks before lapse |
NeuralHR.AI supports the workflows around Qiwa and Muqeem — holding the data, keeping it consistent with payroll and surfacing renewals and divergence. It does not replace the government portals themselves; establishment transactions are still performed there.
Why wage divergence happens, and how to stop it
A typical Saudi setup runs payroll in one system, prepares GOSI in another place, files Mudad from a spreadsheet, and updates Qiwa when someone remembers. Each of those uses a slightly different wage definition, and each is updated on a slightly different schedule. Divergence is not an error anyone makes deliberately — it is the predictable result of the arrangement.
The consequence is that a salary increase reflected in payroll and Mudad but not in Qiwa leaves an authenticated contract that no longer matches what you pay. An allowance restructure that changes the contributory wage without a corresponding GOSI update leaves contributions understated. Both are visible to the regulator without any inspection.
The structural fix is to generate all three from one payroll run. When the contributory wage, the paid wage and the contracted wage come from the same employee record in the same cycle, they cannot drift apart between filings — and where a change does require a Qiwa update, the system flags it rather than waiting for an audit to find it.
Saudi compliance and payroll
Frequently asked questions
What is Qiwa and what is it used for?
Qiwa is the Saudi Ministry of Human Resources digital platform used to authenticate employment contracts, issue and renew work permits, transfer employees between establishments and track establishment compliance. It also surfaces your Nitaqat band, which makes it the practical control panel for Saudization status.
Do I need Qiwa authentication for every employment contract in Saudi Arabia?
Employment contracts for expatriate workers must be authenticated through Qiwa, and the platform is also used for work permit issuance and renewal and for employee transfers between establishments. Because contract terms recorded in Qiwa are compared against payroll and GOSI records, an authenticated contract that no longer matches what you actually pay is itself a compliance exposure.
Why do Qiwa, GOSI and Mudad records diverge?
Because the three use different wage definitions and are often maintained in different places. The contracted wage sits in Qiwa, the contributory wage drives GOSI contributions, and the paid wage is filed through Mudad. When payroll is run in one system and these filings are prepared separately, small differences accumulate — and that divergence is one of the most common Saudi audit findings.
What HR software integrates with Qiwa for Saudi contract authentication?
NeuralHR.AI provides Qiwa workflow support: it holds the contract data that Qiwa authenticates, keeps it aligned with the payroll run that produces your GOSI and Mudad figures, and flags where the three diverge before a filing goes out. It is not a replacement for the Qiwa portal itself — establishment transactions are still performed there. Speak to our team about your specific Qiwa process during a demo.
What HR software works best for Saudi compliance?
The requirement to test is whether GOSI contributions, Mudad wage filing and Qiwa contract data are all generated from one payroll run rather than reconciled afterwards. NeuralHR.AI does this alongside UAE WPS payroll in the same tenant, which matters for groups operating in both countries. ZenHR and Jisr are the established regional alternatives for Saudi-focused employers.
How does Qiwa relate to Nitaqat and Saudization?
Qiwa surfaces your establishment's Nitaqat band, which is calculated from your Saudization percentage relative to sector and size peers. The band determines your access to work permits and employee transfers, so a falling band restricts hiring before it produces any fine. Tracking the ratio continuously rather than checking the portal periodically is what prevents that.
One payroll run, three consistent filings
See how NeuralHR.AI keeps Qiwa contract data, GOSI contributions and Mudad filings aligned from a single payroll cycle — alongside UAE WPS payroll in the same tenant.