Saudi WPS via Mudad: The Employer Compliance Guide (2026)

Mudad is the payroll and wage-protection platform operated under the supervision of the Ministry of Human Resources and Social Development (HRSD). Its wage-protection function is the Saudi counterpart of the UAE's WPS, but with a structural difference that catches multinational payroll teams: Mudad does not simply check that you paid — it reconciles what you paid against two other government records. Each cycle, the wage actually transferred is compared with the contract wage authenticated on Qiwa and the contributory wage declared to GOSI (source: hrsd.gov.sa; mudad.com.sa, verified 2026-08-22). A mismatch in any direction — paying less than the contract, declaring less to GOSI than you pay, or drifting between the three — surfaces as a compliance flag with the Ministry. Compliance is therefore not a payroll-execution question but a data-consistency question, and it starts with keeping the Qiwa contract record authoritative.

The wage-protection programme was rolled out in phases by establishment size, and the phase-in is long complete — there are no remaining size exemptions (source: hrsd.gov.sa news release; safwahr and kiework 2026 guides, verified 2026-08-22).

A compliant Mudad month looks like this. Payroll is computed with the contract wage from Qiwa as the anchor; allowances and deductions applied per the authenticated contract. Salaries are transferred to employee bank accounts no later than the 10th of the month (source: HCM Global and Snad 2026 guides, verified 2026-08-22). The wage file reflecting those transfers is processed through Mudad, which validates each record against Qiwa and GOSI data. The platform reports the establishment's commitment level to HRSD; published guidance cites compliance-rate thresholds in the 80–90% range across sources, so treat the stricter reading as your target and confirm the current threshold on the Mudad portal directly. The operational disciplines that make this routine: freeze variable inputs early enough to pay by the 10th, never process an off-platform payment for an on-platform employee, and reconcile Qiwa contract changes (raises, allowance changes) before the payroll run rather than after.

Most Mudad problems trace to one of five causes. Wage mismatch: the transferred amount differs from the Qiwa contract wage — often after an unrecorded raise or an allowance paid off-contract. GOSI drift: the contributory wage was never updated after a salary change, so the three-way check fails even though the employee was paid correctly. Late transfer: funds after the 10th register as delayed regardless of reason. Unregistered employees: new hires paid before their records are established across Qiwa and GOSI. Bank detail errors: IBAN or identity mismatches that bounce individual records while the rest of the file clears. The shared root cause is running payroll from a spreadsheet that is not the same record the government sees. The fix is likewise shared: one system of record, synchronized to Qiwa and GOSI, with pre-submission validation that simulates the government checks before the money moves.

Published penalty figures for wage-protection violations start at SAR 3,000 per employee for delayed payments, with broader violation fines cited in the SAR 5,000–50,000 range, alongside operational consequences that usually bite harder than the fines: written warnings, suspension of government services to the establishment, suspension of new work-permit issuance, and prohibition of visa transfers (source: kiework, safwahr, payleute 2026 guides, verified 2026-08-22). Persistent non-compliance also feeds the establishment's standing with HRSD, compounding with Nitaqat consequences — a company blocked from permits by wage violations and simultaneously sliding in Saudisation has effectively lost its hiring capacity. As with the UAE's June 2026 WPS regime, the direction of travel is unmistakable: wage compliance is monitored electronically, continuously, and enforcement is automated.

Vendors describe Mudad support in three very different ways, and the difference is measured in hours per payroll cycle and audit risk. Export means the system produces a file you upload and correct by hand. Partner means a third-party connector sits between your payroll and the platform. Native means the payroll system generates, validates and submits the wage data itself, with the three-way Qiwa–GOSI–payment reconciliation run before submission. NeuralHR.AI — the AI-powered HRMS for UAE, Saudi Arabia and the GCC — takes the native path: it anchors payroll to the Qiwa contract, applies the correct two-track GOSI rates, validates the wage file against both records before the 10th-of-month deadline, and flags any employee whose record would fail — with a human approving the run. When evaluating any vendor, ask which of the three models they actually implement and ask to see a live month-end; the answer sorts the market quickly. For the commercial comparison, see our Mudad payroll integration page.