The wage file fails, and nobody notices for weeks. Then Qiwa blocks a service, and suddenly everyone cares. This is how most WPS stories go. The Wage Protection System in Saudi Arabia compares one number against another: the salary written in the Qiwa contract versus the salary actually paid through the bank. When the two agree, your compliance rate climbs and services flow. When they disagree, the rate drops, and the penalties arrive quietly, then all at once. This post explains how the system works, the violations that cause most of the trouble, and the monthly checks that keep your rate green. Read it once for the theory. Bookmark it for the checklist.
Last reviewed: October 2026
Key points
- WPS compares the wage in the Qiwa contract with the wage paid by bank and reported in the Mudad file. Both must match.
- The payroll file must be uploaded within 30 days since 1 March 2025. Upload in the first week of each month.
- Most violations start in contract data: wages below contract, missing employees, wrong IBANs, stale wages after a raise.
- Low compliance leads to fines, suspended services and possible inspection. Fix records first, never the file dishonestly.
1How the Wage Protection System (WPS) works in Saudi Arabia
The system is a chain of four links, and a break anywhere reads as non-compliance:
- Contract in Qiwa. Every employee’s contract records a wage. This is the number the system expects to see paid.
- Payroll file in Mudad. Each month, the salary file upload to the Mudad platform lists every employee and the wage paid.
- Bank payment. Salaries move through the banking system, via the Mudad channel, not cash. A bank transfer into the employee’s own account is the only payment the system recognises.
- Matching. Mudad compares the file against the payments and against the Qiwa contracts. Matched employees count toward your compliance rate.
The compliance rate itself is calculated from the employees covered by the system, with the eligible count and any exclusions or justifications determined by HRSD and Mudad under their official rules, so treat the exact composition of the calculation as defined by the official WPS guidance rather than a universal formula. The WPS compliance rate is the number MHRSD reads first, and the one your clients never see but feel. What it controls is the point. High compliance keeps government services running: work permits, transfers of services, new visa requests. Low compliance freezes them, in steps.
One deadline changed recently and still catches teams out. Since 1 March 2025, the payroll file for the previous month must be uploaded within 30 days, not the old 60. A team working from a 2024 guide uploads half a month late, every month, and cannot understand the falling rate.
Related course: Labour Law and Employment Compliance in Practice covers employment compliance topics that sit around payroll.
2The violations that cause most problems
Salary paid below the contract wage
The classic. The contract says SAR 8,000. The employee agreed, informally, to take 6,500. The file, if it is honest, shows 6,500 against 8,000, and the mismatch registers every month. The fix is not a cleverer file. Either the contract changes by agreement, through Qiwa, or the payment rises to the contract. Everything else is a violation with paperwork on top.
Late upload
The 30-day window is a hard edge. Upload on day 31 and the whole month registers late, however perfect the file. The control is a calendar entry, not diligence: the file goes up in the first week of each month, every month, before anyone is on holiday.
Employees missing from the file
Include employees covered for that pay period under the applicable Mudad and HRSD rules. Check new joiners, Saudis and non-Saudis, drivers and part-time staff against the official eligibility rules. A missing employee reads as an unpaid employee, and unpaid employees drag the compliance rate down faster than underpaid ones. The usual cause is a gap between HR hiring and payroll onboarding. The fix is a same-day rule: no Qiwa contract without a payroll line in the next cycle.
Paid in cash
Cash payments do not exist for WPS purposes. The money must move through the bank, into an account in the employee’s name. Cash-plus-file schemes, where the file shows a compliant figure and the difference is handed over physically, are the version that turns a compliance problem into a fraud problem. Inspectors and auditors both look for the gap between contract, file and bank.
Mismatched IDs or IBANs
A typo in an iqama number, a closed bank account, an IBAN that belongs to a different employee. The payment bounces or misroutes, the employee shows as unpaid, and nobody finds out until the rate drops. The control is boring and effective: validate IDs and IBANs at onboarding, and revalidate when the bank or the ID changes.
Contract wage not updated after a raise
The raise was approved in April. The email exists. The payroll has paid the new figure since May. The Qiwa contract still says the old number, and every month since has registered a mismatch in the other direction: paid above contract. Overpayment reads as non-compliance too, though it is the friendlier version. Update the contract first, then the payroll.
3What happens when compliance drops
The consequences arrive in stages, and the stages are the point. Service suspension is the penalty that makes WPS real to management, because it bites operations rather than budget:
- Fines first. Missing the required compliance rate or a late or missing payroll file can draw fines under the current violations schedule. Check the official schedule for the amounts that apply to your establishment.
- Service suspension next. Establishments below the required rate lose access to government services through Qiwa and related platforms: new work permits, transfer of services, and visa requests sit in a queue that does not move. A company planning to hire ten workers discovers the plan died in a payroll file.
- Inspection risk last. Persistent non-compliance, or a file delayed beyond 20 days, can invite an MHRSD inspection, which examines far more than the payroll file. Inspectors arrive with the WPS history in hand and expand scope from there.
No official percentage publishes the exact red line, and the Ministry adjusts what it requires. Treat any specific threshold you hear as hearsay. The safe position is unglamorous: keep the rate as close to one hundred as your payroll allows, and treat any dip as an incident, not a statistic.
4A monthly WPS check
Six steps before each upload. One person, one hour, once a month:
- Reconcile the employee list in Mudad against Qiwa: every hire, every leaver, every transfer.
- Compare each contract wage against the payroll line. A salary mismatch in either direction, over or under, registers as non-compliance. Investigate every difference.
- Validate IBANs and IDs for anyone new or changed.
- Confirm nobody on unpaid leave or absence is filed incorrectly.
- Upload in the first week of the month, not the last.
- Check the compliance rate after upload, and resolve any flagged wage the same week.
The sixth step is the one teams skip. Mudad lets the employer file a justification for a flagged wage, and the employee accepts or rejects it in their own account. The employer has 10 days to file a justification for a flagged wage, and the employee has 3 days to accept or reject it. Practitioners report that a justification filed and accepted closes the flag quickly, while a flag left open tends to age into a violation. Treat that as observation, not a published rule.
5Fixing a low compliance rate
When the rate has already fallen, work the list in order:
- Correct the records first. Most of the rate is recovered by fixing data: missing employees, stale wages, dead IBANs. This is days of work, not months.
- Document legitimate gaps. Unpaid leave, absences, and new joiners mid-month all have proper treatments. File them correctly rather than hoping the system averages them away.
- Raise objections where available. After an administrative decision, the objection route runs through MHRSD’s e-services, with the evidence attached. Before that stage, the justification route inside Mudad handles most flags.
- Never fix the rate by fixing the file dishonestly. A file that shows payment nobody received is fraud, and fraud converts a recoverable situation into a legal one.
The rate recovers as fast as the data corrects. Teams that fix records in week one usually see the rate normalise within a cycle or two, though the exact timing depends on the correction cycle and how quickly justifications are accepted. That is practitioner experience, not a published timeline.
One warning belongs at the end. Companies with expat-heavy workforces feel WPS problems twice: once in the compliance rate, once in the visa queue. A blocked transfer of services does not just delay a hire. It hands a competitor the candidate, and the candidate tells the market which employer pays on time. The system was designed to make wage discipline public. Treat it that way, and the rate becomes a recruiting asset instead of a liability.
6FAQ
What is the Wage Protection System in Saudi Arabia?
It is the system that compares the wage recorded in the Qiwa contract with the wage actually paid through the bank and reported in the Mudad payroll file. Matching wages keep your compliance rate high and government services open.
What is the WPS deadline each month?
The payroll file for the previous month must be uploaded within 30 days, per the rule in force since 1 March 2025. The old 60-day window is gone. Upload in the first week and the deadline never becomes a decision.
Does WPS apply to small businesses?
Yes. The phased rollout finished years ago. Check the current Mudad and HRSD rules for how your establishment size is treated, as the Minister may exempt certain categories from paying through banks in defined cases.
How are employees on unpaid leave handled?
Unpaid leave is a documented status, not a gap. The employee’s record shows the leave, the file reflects it, and the justification route covers the period. What hurts the rate is an unexplained zero, not a documented absence.
Can I pay part of the salary in cash?
No. The wage that matches the contract must move through the protected channel, per the WPS process and its exceptions, which the Minister may apply to defined categories. Cash top-ups on top of a compliant file still break the chain, because the paid wage no longer matches the recorded one, and the arrangement reads as deliberate concealment if examined. Where a genuine exception applies, it comes with its own notice and conditions, published through the official channels.
7Next step
Run the six-step check once this month, before the upload, not after. Then look at your rate in Mudad and read every open flag. Each one is a small fire with a date on it. The Labour Law and Employment Compliance in Practice course covers employment compliance in practice. For the contract side that feeds the system, read the 2025 amendments post, and for the clause that starts every wage dispute, see the probation period post.
Related reading: Saudi labour law 2025 amendments and how to calculate end of service benefits.
This article is general information, not legal or tax advice. Rules change; confirm with the official source or a licensed adviser.