Saudi WPS for Small Firms: One Missing Record Fails 80%

On 1 December 2020 Saudi Arabia's Ministry of Human Resources and Social Development began applying the seventeenth and final phase of the Wage Protection Program, covering establishments with one to four workers. Since that day no size of private-sector employer is exempt: every establishment uploads its wage file monthly through the Mudad platform.

The rule is the same for an establishment of four and one of four thousand. The arithmetic is not. In a large establishment a missing record disappears into the total. In a small one, each employee is a quarter, a third or half of the ratio. This article is about that difference: why a small establishment falls under the threshold on a single mistake, where that mistake usually comes from, and what is enough each month to prevent it.

How the program reached small establishments

The program did not start universal. According to GOSI's program page, the first phase applied from 1 June 2013 to giant establishments (3,000 workers or more), and the eleventh phase, in August 2017, reached establishments with 60 workers or more. The phases then stepped down by size until the seventeenth in December 2020.

Some pages in circulation say the obligation "became universal for every establishment with one worker in the 2026 updates". The date is six years off. The ministry announced the final phase on 1 December 2020, and in August 2023 it reminded establishments again that wage files must be uploaded through Mudad. This is not a historical detail: whoever believes the obligation is new also believes there is an adjustment period, and there is none.

The ratio is computed against GOSI, not against your file

The ministry defines the compliance indicator as the number of employees whose wages were transferred through the Wage Protection System, out of the total employees registered with GOSI (social insurance) on the establishment. The denominator is the GOSI roster. Every name registered to you there and missing from the wage file lowers the ratio, however clean your file is. We covered the published exceptions and how to justify them in why Mudad rejects your WPS file, and will not repeat them here. What matters here is what that denominator does when it is small.

The margin table: how many records you can lose

The threshold that appears in writing in an official guide is 80%. The user guide for the services of the Contractual Relationship Improvement Initiative requires an establishment that wants to receive a transferred worker to show "compliance with the Wage Protection Program at no less than 80% for the last three months". Taking that threshold, this is how many records an establishment can miss in one month without dropping below it:

The first four rows are exactly the phase-seventeen establishments. For an establishment of one to four workers, an 80% bar means zero errors. There is no single missing record that keeps you above it. An establishment of a hundred can miss twenty records in the same month and stay compliant.

And a small establishment's ratio does not drift, it jumps. An establishment of four has only five possible values: 0, 25, 50, 75 and 100%. There is no such thing as a "slight dip" for you.

Two readings of "for the last three months"

The guide does not say whether 80% is required in each of the three months separately, or across the three months pooled. We found no official text that settles it, so here is the arithmetic under both readings for an establishment of four:

• Each month separately: one missing record in any month = 75% for that month = below the bar.
• Three months pooled: 12 records in total. One missing = 91.7%, two = 83.3%, three = 75%.

Even on the kinder reading, a small establishment's margin is two records across an entire quarter. For a one-worker establishment, with three records in total, a single miss is 66.7% under either reading. Mudad's own dashboard shows compliance status per month and for the last six months, so treating each month as if it were measured alone is the safe assumption.

Where the ratio is actually read

It can look as though a three-worker establishment needs none of this, since it will not receive transferred workers this year. But the ratio is not read in only one place:

• Receiving a transferred worker requires 80% for the last three months, per the guide above. For a small establishment, hiring from inside the Kingdom is usually the fastest way to fill a role, and that is exactly what closes. The full six conditions are in Qiwa employee transfer conditions.
• The Saudization certificate requires the establishment to be compliant with wage protection, and it is a condition for bidding on government tenders. We set out its conditions and refusal reasons in why Qiwa refuses to issue the Saudization certificate.
• A worker leaving without your consent. The same guide exempts from the transfer controls the case of "non-payment of the worker's wage for three consecutive months", and the evidence of non-payment comes from wage protection data, not from a complaint. A worker you paid in cash, who did not appear in the file for three months, looks to the system like a worker who was not paid.

In a large establishment, one worker leaving that way is one loss. In an establishment of three, it is a third of the workforce.

Where a record falls out in an establishment of four

Violations in small establishments do not look like those in large ones. There is no payroll system drifting from GOSI by hundreds of rows. What usually happens is one of five things:

1. A worker left and was never removed from GOSI. They stopped working two months ago and the record was not updated. They are out of the wage file because you no longer pay them, and in the denominator because they are still registered to you. In an establishment of four, that alone is 75%.
2. Paying in cash or from the owner's personal account. The program tracks wages transferred through banks and financial institutions in the uploaded file. A salary paid outside that route does not exist as far as Mudad is concerned, even if you hold a signed receipt.
3. Assuming every new hire is exempt. The published exception is for a newly arrived expatriate worker in the first 90 days after entering the Kingdom. A worker transferred to you from another establishment inside the Kingdom has not just entered it, so do not assume the grace period covers them until you have checked in Mudad.
4. Leave outside the Kingdom without a justification. A worker on leave abroad is not counted, but every published exception requires a justification. If none is submitted, the name stays in the denominator.
5. A salary in the file that differs from the wage registered with GOSI. This rejects the record rather than just lowering attendance, and the cause is usually a raise or allowance updated in one place and forgotten in the other. The mechanism is explained in WPS violations: the problem is in your data, not in Mudad.

Notice that none of these causes has anything to do with paying the salary on time. The small establishment that is in violation usually does pay its workers, and is then measured against a sheet that does not match what it paid.

A monthly routine that is enough for a small establishment

An establishment of four workers does not need a payroll system or a software integration. It needs five steps, repeated every month in the same order:

1. Export the list of employees registered to you at GOSI and put it next to the list of people you will pay this month. Any name in the first and not in the second must be removed from GOSI, justified, or added to the file. Decide which before uploading, not after.
2. Pay every salary through the bank, from the establishment's account, in riyals.
3. Build the file from a template with the right columns. The free WPS file template gives you the columns in the order the platform expects, and is built inside your browser without uploading any data.
4. Check the file before uploading it. The WPS file validator catches the errors that get a record rejected: totals that do not add up, ID or iqama number format, IBAN validity, and duplicates. In an establishment with no margin, the record you catch here is the difference between 100% and 75%.
5. Upload within the deadline. Since 1 March 2025 the window is 30 days from the end of the month instead of 60, and each month is uploaded on its own.

The first step matters most and is the most neglected, because it does not happen in Mudad but in GOSI. Tools check the file in front of you, but no tool that reads a single file can know that GOSI holds a name the file does not.

Conclusion

Small establishments entered the Wage Protection Program six years ago, but the arithmetic that applies to them is rarely written down: at an 80% bar, an establishment of one to four workers cannot absorb a single missing record in a month. And the missing record usually comes from a name forgotten at GOSI or a salary paid outside the bank, not from a salary that was never paid.

Has your small establishment's compliance ratio dropped even though you pay your staff? Send us your GOSI roster and the last wage file you uploaded, and we will tell you which name or record brought the ratio down and where it came from. A free diagnostic with no commitment through the contact page, or see our WPS compliance audit service if it happens every month.