Qiwa Contract Authentication Rules (2026): Deadlines, Steps & Nitaqat Impact

Authentication is more than uploading a contract. On Qiwa, the employer creates the employment contract with its full terms — role, wage, allowances, duration — and the employee then reviews it from their own Qiwa individual account, where they can approve it, reject it with stated reasons, or request amendments before agreeing (source: qiwa.sa official guidance, verified 2026-08-22). Only when both parties have approved does the platform authenticate the contract automatically, at which point it is recognised by the Ministry of Human Resources and Social Development as the governing record of the employment relationship. That record then anchors everything downstream: the wage Mudad expects to see paid, the contributory wage GOSI expects declared, and — for Saudi nationals — whether the employee counts toward Nitaqat at all. Contracts not documented electronically through the platform are considered legally invalid, which converts what used to be an administrative nicety into the foundation of enforceability (source: businesslink.sa; Lexology, verified 2026-08-22).

Since 15 April 2026, a Saudi employee is included in the employer's Nitaqat calculation only if their contract is electronically documented and authenticated on Qiwa (source: hrsd.gov.sa; qiwa.sa, verified 2026-08-22). The rule's genius — and its danger for employers — is that it enforces itself through arithmetic rather than inspection. No fine is issued for an unauthenticated contract; the employee simply vanishes from your Saudisation ratio, and the consequences arrive later as a band calculation that came in lower than expected, with everything a Red or Low Green band implies for visas and permits. Because authentication requires the employee's action too, an employer can be exposed by nothing more than an unread notification. The safe assumption after April 2026: an unauthenticated Saudi contract is a Nitaqat incident in progress, and authentication status belongs on the same monitoring dashboard as the ratio itself.

The flow below is drawn from Qiwa's official employer guidance (qiwa.sa, verified 2026-08-22).

Three clocks matter. The employee's 10-day response window: if the employee takes no action, the authentication request is automatically cancelled and the employer must resend it — a silent failure mode that leaves the contract unauthenticated with no error on the employer's side (source: qiwadesk; hr360s guides, verified 2026-08-22). The job start date: authentication is expected from the start of employment, so a hire processed in payroll before the contract is authenticated is already out of sequence. And the standing state: an unauthenticated contract is legally invalid as an electronic record, does not count a Saudi employee toward Nitaqat (from April 2026), and undermines the three-way wage reconciliation Mudad performs — because there is no authenticated contract wage to reconcile against. Rejection is not a dead end: an employee who rejects states reasons, which opens a negotiation or amendment cycle on the platform; the risk is not rejection but silence.

The hard case is not the new hire — it is the workforce hired before authentication became consequential. A practical clean-up sequence: export the authentication status of every current employee from Qiwa; segment the gaps into never-issued (contract was never created on the platform), pending (issued but inside or past the 10-day window) and cancelled (auto-cancelled by silence, needs reissue); then run a campaign that pairs each reissued contract with direct employee communication — most non-responses are not disputes but lost notifications, changed phone numbers or unfamiliarity with the Qiwa individual account. Prioritise Saudi nationals first because of the Nitaqat arithmetic, then non-Saudis, whose contracts must also be authenticated. Track the campaign to zero, then keep it at zero by making authentication a gating step in onboarding: the hire is not complete — and payroll does not run — until the Qiwa authentication lands.

Everything above is workflow, which means software can carry it. NeuralHR.AI — the AI-powered HRMS for UAE, Saudi Arabia and the GCC — treats the Qiwa-authenticated contract as the single source of truth for Saudi employment: onboarding checklists gate on authentication status, so a new hire cannot silently enter payroll unauthenticated; the 10-day window is tracked per contract with escalating reminders before auto-cancellation; Saudi employees whose contracts are pending or cancelled are flagged directly on the Nitaqat dashboard as non-counting; and when a contract term changes — a raise, an allowance — the system prompts the Qiwa update before the next Mudad cycle so the three-way reconciliation keeps passing. A human approves each action; the AI makes sure nothing waits in silence. For the platform-integration comparison, see our Qiwa integration page.