Qiwa and Nitaqat: Contract Documentation for Compliance

• You registered every Saudi employee on GOSI. Your payroll runs through WPS. Then Nitaqat recalculated overnight and your Green band dropped — because half your Saudi workforce had contracts that existed on paper but not on Qiwa.

• That is Qiwa Nitaqat compliance in 2026. The Ministry of Human Resources and Social Development no longer treats social insurance enrollment as proof of employment. The contract itself must live on the platform, authenticated and notarized, or the person vanishes from your Saudization numerator.

• If you hire in Saudi Arabia, this shift affects every headcount decision you make from offer letter to work permit renewal.

What changed on 15 April 2026

• [Zawya reported the core rule clearly](https://www.zawya.com/en/economy/gcc/saudi-arabia-updates-nitaqat-saudization-calculation-through-qiwa-contracts-ghwi8n8q): effective 15 April 2026, **only Saudi employees whose employment contracts are electronically documented through Qiwa** count in Nitaqat Saudization calculations.

• Before that date, GOSI registration was the gate. Hire a Saudi national, register them for social insurance, and they entered your ratio. [Fragomen confirmed the post-April requirement](https://www.fragomen.com/insights/saudi-arabia-nitaqat-calculation-now-requires-online-contract-submission.html): employers must now ensure contracts are submitted on Qiwa **and** GOSI status is registered for inclusion.

• The practical impact is immediate. An establishment with 40 Saudi employees on GOSI but only 30 documented on Qiwa calculates Saudization as if it had 30 Saudis — not 40. Ten people still show up on payroll. They simply stop counting toward the band that unlocks your next expatriate visa.

The notarization targets you are measured against

• Contract documentation is not binary for the whole company forever. [MHRSD announced phased compliance rates](https://www.hrsd.gov.sa/en/media-center/news/%D8%B6%D9%88%D8%A7%D8%A8%D8%B7-%D8%A7%D9%84%D8%A7%D9%84%D8%AA%D8%B2%D8%A7%D9%85-%D8%A8%D8%AA%D9%88%D8%AB%D9%8A%D9%82-%D8%B9%D9%82%D9%88%D8%AF-%D8%A7%D9%84%D8%B9%D9%85%D9%84-%D8%B9%D8%A8%D8%B1-%D9%85%D9%86%D8%B5%D8%A9-%D9%82%D9%88%D9%89):

• MHRSD calculates the rate by comparing notarized contracts to **all** employee contracts in the establishment — Saudi and expatriate. That means legacy expat contracts sitting in filing cabinets hurt the denominator even when they do not affect Saudization math directly.

• Fall below the threshold and services tied to compliance indicators stall. Work permits, transfers, and band-linked privileges are the ones employers feel first.

Qiwa, GOSI, and Nitaqat: three systems, one truth

• Think of compliance as a chain, not a checklist item:

• Break any link and downstream systems disagree about reality.

• **Qiwa** is the Ministry's unified labor portal — contract creation, notarization, work permits, employee transfers, and Nitaqat monitoring. [Mercans documents over 12 million contracts processed electronically on the platform](https://mercans.com/glossary/qiwa-platform/), reflecting how central it has become to labor market data.

• **GOSI** confirms social insurance enrollment. It still matters. It just no longer substitutes for a Qiwa contract.

• **Nitaqat** reads the intersection: documented Saudi contracts on Qiwa, weighted by economic activity, salary bands, and — separately — profession-specific quotas.

• Your HR team may track headcount in an HRIS. Government systems track **documented** headcount. When those numbers diverge, Nitaqat trusts Qiwa.

Where employers lose compliance silently

• These failure modes show up in every audit cycle:

1. **Offer-to-Qiwa lag** — You hired a Saudi graduate three months ago. GOSI is active. Qiwa contract is still "pending employee acceptance." They do not count.
2. **Renewal drift** — Fixed-term contracts expired and renewed on paper without re-notarization on Qiwa.
3. **Acquisition baggage** — Merged entities inherit undocumented contracts from the predecessor establishment.
4. **Title-salary mismatches** — Contract terms on Qiwa do not match actual WPS payments, triggering review holds.
5. **Recruiting handoff gaps** — TA closes the hire; HR ops never receives nationality and contract-start data structured for Qiwa entry.

• Each gap looks administrative until your band drops and visa renewals queue behind a red indicator.

Contract documentation is now a hiring workflow problem

• Recruiting teams often treat compliance as post-hire operations work. In 2026, that handoff is too late.

• You need nationality, salary, contract type, profession code, and start date **at application** — not extracted from a PDF offer three weeks after acceptance. You need a closed-loop status: draft, employee signed, notarized, GOSI linked. You need a dashboard that shows "countable Saudis" versus "Saudis on payroll."

• Generic ATS platforms store resumes. They do not store Qiwa contract state. HRIS modules add headcount but rarely surface Nitaqat impact per hire. The gap sits between "candidate selected" and "contract notarized" — exactly where most employers lose ratio points.

• [Hiring on proof of fit](/spaces/hiring-on-proof-of-fit) does not mean ignoring compliance. It means capturing structured evidence about each candidate — skills, credentials, nationality, salary expectations — so the compliance team can document the contract on Qiwa without reconstructing the hire from email threads.

Reconciling your numbers this week

• Run this audit before your next requisition goes live:

1. **Pull Qiwa establishment report** — notarized versus total contracts.
2. **Cross-match GOSI active Saudi registrations** against Qiwa-documented Saudis.
3. **List every Saudi on payroll missing Qiwa authentication** — these are phantom ratio points.
4. **Calculate Saudization with documented headcount only** — compare to your internal HRIS figure.
5. **Project the next three hires** — if they are expatriates, does band hold? If they are Saudi, is Qiwa documentation in the onboarding SLA?

• Use the [Saudization calculator](/saudization-calculator) for establishment-level band modeling once your countable headcount is honest. Garbage in still means garbage out — but documented garbage is at least visible.

Building a compliance-first hiring rhythm

• Treat Qiwa documentation as part of time-to-fill, not a parallel universe:

• **Requisition template** — USOC profession code, salary band, nationality requirement (if driven by quota), contract type.
• **Offer checklist** — Arabic contract draft ready before verbal offer for Saudi nationals.
• **48-hour Qiwa SLA** — employee authentication triggered on start date minus onboarding window.
• **Weekly ratio review** — TA and HR ops share documented-Saudi count, not just accepted offers.

• Employers who [build shortlists in hours](/spaces/build-shortlist-in-hours) without this infrastructure move fast on the wrong numbers. Speed without documentation is how Green bands turn Red between reporting cycles.

The bottom line

• Qiwa Nitaqat compliance in 2026 rewards employers who unify recruiting data and contract documentation — not teams that treat the platform as an afterthought for HR ops. Document every contract. Register every Saudi on GOSI. Reconcile weekly. Hire with your countable ratio in view.

• [Start with an honest band calculation](/saudization-calculator), then [see how XUnframed helps employers hire on proof](/companies) while compliance stays attached to every seat you fill. More context in [Spaces](/spaces).