Service Companion Private Limited

The Wage Protection System and Mudad: Proving You Paid

20 min readLast updated

The due date is the 1st of the month and you have 30 days from it. Where the file comes from, why it bounces, and what stops working when it is late.

The short answer

In short: wages accrue and become due on the first day of each Gregorian month, and you have 30 days from that date to get the wage protection file onto Mudad. You do not build that file — your bank does, and it signs it electronically after the transfer clears. Mudad is now the only route; the old MHRSD e-services upload is gone. If the file is late or the compliance percentage falls short, the Ministry of Human Resources and Social Development suspends a specific, published list of your establishment's services, which includes visa issuance and the Saudization certificate. MHRSD's own schedule puts a clock on it: two months' delay stops its services but leaves work permits alone; three months stops those too, and lets your workers transfer to another employer without your consent.

Two things surprise most payroll managers. The WPS file is generated by the bank, which means a cash payroll cannot be made compliant at all. And Mudad's data spine is GOSI, not Qiwa — 108 of Mudad's published English interface strings name GOSI, and neither the English nor the Arabic file names Qiwa once.


What WPS is, and who runs it

The Wage Protection System (نظام حماية الأجور) is a monitoring programme, not a payment rail. It records what employers actually transferred, to which account, against what the worker should have been paid.

Mudad's FAQ answers the authority question in one line: the legislating authority is "the Ministry of Human Resources and Social Development." MHRSD launched the programme in 2013 — a start date the Saudi Press Agency restated as recently as 23 February 2026 — and moved it onto the Mudad platform in 2020. The programme is thirteen years old; the platform is six.

Scope is now universal. Qiwa's definitions page states that establishments with 10 or more employees must pay salaries through WPS, and that as of 31 December 2020 the system applies to all private sector establishments including micro and small ones. MHRSD describes the same thing from the other end: the final phase, in 2020, covered establishments with 1 to 5 employees, after the programme began in 2013 at 3,000 employees and above. As at 31 December 2024, MHRSD and SPA put coverage at more than 900,000 establishments, a compliance rate above 88%, and roughly 300,000 wage files worth SAR 35 billion processed monthly.

Domestic workers are a separate track, run through Musaned rather than Mudad and phased from new contracts on 1 July 2024 to full coverage on 1 January 2026. This page is about your establishment.


The monthly cycle, and the deadline most pages state wrongly

This is the single question that generates the most contradictory answers online, so here is the official one, quoted.

Mudad's FAQ, question 18, Arabic: "النظام يسمح برفع ملف حماية الأجور خلال 30 يوم فقط من تاريخ الاستحقاق والذي يكون أول يوم من كل شهر ميلادي" — the system allows the file to be uploaded within 30 days only from the due date, which is the first day of each Gregorian month. The English version of the same answer agrees: "within 30 days, starting from the first day of each month."

The due date matters more than the number. The clock does not start when you run payroll or on your company's pay date. It starts on the 1st. If you pay on the 27th and file on the 3rd of the following month, you are four days into a window that opened two days before you paid.

The window used to be 60 days. MHRSD announced the reduction on 3 February 2025, effective 1 March 2025, on the stated basis that 91% of establishments were already uploading within 30 days of the due date. You will see 20-day and 10-day upload windows and colour-coded warning ladders in circulation on commercial blogs; we looked for an official basis for those and found none. The documented upload figure is 30 days. MHRSD does publish a consequence ladder, but it is counted in months, not days, and it is set out further down this page.

Weekly payroll is permitted; the employer chooses monthly or weekly wage type. The processing differs: a monthly file is processed instantly, while for a weekly file the violations and the compliance percentage appear on the 5th of the following month. A group with branches uploads through the main establishment, and Mudad allows five files in a single operation.


Where the file actually comes from

Most guides say the employer prepares the file. The employer does not.

Mudad's instruction to an establishment transferring salaries through a bank is to "apply to the bank to obtain an electronically signed wage file", then register on Mudad, select the establishment and upload it. The bank generates the file after the transfer. That is why one of the documented error causes is a missing or repeated bank signature — the signature is the bank's, not yours.

Three operational consequences follow:

  • A cash payroll cannot comply. Mudad states plainly that a file cannot be uploaded if salaries were handed over in cash.
  • Every worker needs an account. Where a worker has none, Mudad's published options are salary cards issued by the establishment, or electronic wallets issued through Mudad's own payroll system.
  • You either hold a bank payroll agreement, or you use Mudad's payroll system. Subscribing to the Payroll Management System uploads the file automatically and removes the need for a bank payroll agreement. Mudad names its participating banks as Riyad Bank, Arab National Bank, Alinma Bank, Al Rajhi Bank, National Commercial Bank, Bank Albilad and STC Bank, and states that the system currently supports establishments of 1,000 employees or fewer.

The two halves of Mudad get used interchangeably and should not be. The Compliance System is the government wage protection system and it is free; the Payroll Management System is a commercial product with a free standard package and a paid advanced one. Only the first is mandatory. The banks' side is supervised: SAMA circular 9668 of 10 May 2022, still in force, directs institutions to resolve Mudad technical faults expressly so that establishments are not pushed into non-compliance by someone else's outage.


Why a file bounces: the two processing stages

Mudad documents two distinct stages, and knowing which one caught you tells you what to fix.

Stage What it checks Where the result appears Documented examples
1. Format and data Whether the file is readable and its values match the base records Error report on the files page, plus an email Incorrect IBAN; bank signature repeated or missing; establishment unified number missing; payment in a currency other than the Saudi riyal
2. Matching Whether the file's contents reconcile against the wage protection systems Violation details page, after upload A wage entered that does not reconcile with the worker's registered basic wage

Stage one gives you an error report — Mudad's term for the file of warning messages found during processing — and the file must be corrected and uploaded again. Stage two does not reject the file; it records a violation against specific workers, which you then justify.

One caution on stage two, and it is the reason to read the Arabic. Mudad's illustrative example of a stage-two mismatch reads, in Arabic, as a wage entered at less than 50% of the worker's basic wage. The English version of the same answer describes "a 50% increase" of the basic wage. Those are opposite conditions. The Arabic is authoritative, and the Arabic says less than half. Treat it as Mudad's example of a mismatch rather than a stated threshold — the platform publishes no rule text either way.

Note what is not on Mudad's list: a mismatch against the Qiwa employment contract. That claim is everywhere in the secondary literature. It may be operationally true, but it is not what Mudad documents. What Mudad documents, repeatedly, is integration with GOSI — establishment and employee data are drawn from GOSI, multi-branch employee data appears "through the link with the social insurance system", and justifications for non-payment are verified against GOSI. The literal string "GOSI" appears 168 times in Mudad's English language file, 111 of them inside strings the interface actually displays, across 108 distinct strings; "Qiwa" appears nowhere in either the English or the Arabic file. The practical reading: keep the GOSI registered wage and the file aligned first. Qiwa is where the consequences land, not where the reconciliation happens.


The compliance percentage, and what you are actually scored on

Mudad shows a compliance percentage per establishment: the current month on the indicators page, the previous six months on the compliance information page. When it falls below what Mudad's Arabic calls "the required percentage" (النسبة المطلوبة), the platform emails the establishment.

Mudad does not publish what that required percentage is. We looked for it in Arabic and English, on Mudad, MHRSD, Qiwa and the national portal. The phrase "required percentage" returns nothing in the English interface file at all, and Resolution 112377 — the instrument that fines you for missing it — refers only to "the compliance percentage specified by the Ministry" without stating a number. The only thresholds stated numerically are for the compliance certificate:

  • A compliance rate of 70% or higher over the past 12 months; or
  • for newly established entities, 50% or higher over the months the entity has been active in the labour market.

Those are the certificate conditions, not the enforcement threshold, and the difference matters — you can be above the certificate bar and still be carrying violations. Qiwa also states that the certificate itself is valid for one month from the date of issuance, so it is not an annual document. If a tender, a bank or a client asks for a current wage protection certificate, check the issue date before you send it.

Figures of 90%, 85% and 80% circulate as the enforcement threshold. The 90% traces to a press report of 14 November 2022 quoting Fahd Al-Qahtani, Director General of the Regulatory Relations Department at MHRSD, and it was never a single ratio: he said the required rate would rise that December to 90% for establishments of 1–29 workers and 95% for those with 30 or more, from rates then standing at 40% for 1–9 workers and 50% for 10–29. That is a dated statement of intent, not a current published rule, and the other figures we could not trace to a named source at all. The number that applies to you is on your own indicators page in Mudad.

The formula, though, is published — in Mudad's interface rather than its FAQ. Behind a "View Compliance Rate Formula" control, Mudad's interface strings give it as compliant workers divided by included workers, where included workers are total workers minus excluded workers, and excluded workers are new workers (the Arabic says workers in the probation period) plus expatriates outside the Kingdom, plus anyone not active for the entire month, plus immigrant tribes. A second formula in the same interface writes the numerator out longhand: workers whose wages were transferred successfully with no violations and who are registered in GOSI, over the total number of workers registered in GOSI for the establishment.

Note what the denominator is. It is not your payroll headcount — it is your GOSI-registered headcount, less a defined exclusion set. The version circulating on commercial blogs, (workers paid − workers in violation) ÷ total workers, has the shape roughly right and the denominator wrong, and the denominator is the part that changes the answer.

Improving the percentage has exactly two levers, per Mudad: upload the file, and justify the violations.

The justification workflow is where most of the month's work sits. Depending on the type of violation, the justification is sent to the affected worker by SMS to the number registered in Absher, and the worker accepts or rejects it in Mudad. If the worker does not respond within 3 days of being notified, the system processes the justification automatically. For non-payment cases where the worker is a new joiner or a leaver, no worker response is sought — Mudad verifies against GOSI. Workers only need to register on Mudad if they have a pending justification.

One related term: settlements (التسويات) are payments to a worker other than the monthly or weekly wage. Mudad's own examples are wages more than 90 days overdue, overtime, and advance housing allowance.


What non-compliance actually stops

Mudad publishes the list. Asked what the penalties are for continued non-compliance, it answers that MHRSD suspends certain establishment services:

  • the service for requesting an establishment or expansion visa quota;
  • visa issuance;
  • conditional temporary disbursement for government contracts;
  • transfer of labour between contracts;
  • issuance of the Saudization certificate.

MHRSD puts a clock on that list. Its wage protection programme page publishes a two-rung delay schedule:

  • Two months' delay"Stopping all the services except the service of issuing and renewing the work permits or licenses".
  • Three months' delay"Stopping all the services", and "The laborers are allowed to transfer their services to another employer without needing the approval or consent of their current establishment even if the work permit or license has not expired."

That second rung is the one to take seriously, and it is worth stating plainly because it is usually asserted without a source: at three months, your workers can leave for another employer without asking you. Read the page it sits on with its age in mind, though. It still names the ministry's old e-services portal as the upload channel, which Mudad has replaced, and it still carries a flat SR 3,000 fine that Resolution 112377 has since superseded. The ladder is the most specific statement MHRSD publishes of what happens when; the page around it is not current, so confirm your own status in Qiwa and Mudad rather than relying on it alone.

MHRSD's service pages corroborate the same thing from the other direction, more precisely than the general warnings suggest. The Visa Issuance service page lists its terms of use as a valid commercial registration, an existing establishment status, valid work permits across the unified number, "Commitment to wage protection", a permitted activity, a Nitaqat band of at least Medium Green or Green Very Small, and sufficient Absher balance. The Request for transfer of expatriate workers page carries the same wage protection condition.

The Issue and Renew Work Licence page does not. Its stated conditions are that the establishment is not in the red zone and that the licence expiry is within six months. That matches the two-month rung exactly: the block bites on visas, quota and transfers before it bites on work permits — which is why an establishment can drift out of compliance for a couple of months and notice nothing until it tries to recruit. At three months the exemption goes away with everything else.

On fines, the instrument is MHRSD Ministerial Resolution No. 112377. Two rows apply:

Row Violation Class ≤20 workers 21–49 50+ Multiplied
40 Failure to upload the wage protection file monthly, or to meet the compliance percentage specified by the Ministry Serious 500 1,000 2,000
39 Failure to pay wages and entitlements in the official currency on their due dates into approved bank accounts, or withholding wages without judicial basis Serious 300 300 300 per worker

Row 40 is not multiplied per worker. Row 39 is, which is the one that scales badly. Both are classified serious (جسيمة). Both rows were read directly from page 5 of the resolution PDF for this article. The full schedule, transcribed from the resolution, is on our labour violations and penalties page.

There is a benefit on the compliant side that nobody mentions. An establishment compliant with wage protection and in the green Nitaqat band for 13 consecutive weeks qualifies for instant calculation in Nitaqat Mutawar, the developed Nitaqat programme, at the next update of its band. If you are managing toward a band threshold, that is a lever; our Nitaqat categories guide sets out the bands.


How it meshes with GOSI and with end of service

WPS is the evidentiary layer over two other records.

GOSI holds the registered contributory wage — basic wage plus housing allowance, floored at SAR 1,500 for annuities and capped at SAR 45,000. That figure is what the file is read against, and it is the one to fix first when a wage changes. It is also, per the formula above, the source of the headcount you are scored against. The rates, tracks and floors are on our GOSI contributions page.

End of service touches WPS at two points. A leaver's final month usually produces a non-payment violation, justified and then verified against the GOSI leaver record rather than by asking the worker. And the award itself is a settlement in Mudad's sense, not a wage. Separately, Resolution 112377 row 36 requires wages and entitlements to be settled within one week of the contractual relationship ending, or two weeks where the worker resigned. How the award is calculated is on our end of service benefits page.

The sequencing rule that follows is short: change the GOSI registered wage, the Qiwa contract and the payroll instruction in the same cycle, before the file goes up. A wage changed in one place and not the others reconciles against nothing.


What is not published

Stated plainly, because guessing here is how wrong numbers spread. This list is shorter than it was in draft: three items we had expected to find unpublished turned out to be published, and they are in the body above.

  • The enforcement compliance percentage. Mudad's Arabic refers to "the required percentage" without stating it, the English interface file does not contain the phrase at all, and Resolution 112377 fines you for missing "the compliance percentage specified by the Ministry" without saying what it is. Only the certificate thresholds (70% / 50%) are published.
  • An exhaustive schedule of wage-file rejection codes. Mudad names error causes by example and publishes no complete list for the compliance wage file. The numbered rejection-code tables circulating elsewhere are not traceable to Mudad or MHRSD. Mudad's separate Payroll Management System does surface a handful of its own coded errors on bulk upload, but that is the commercial product, not the wage protection file.
  • The day-level escalation ladder. MHRSD's month-based ladder is published and is set out above. The colour-coded ladders and the 10/15/20-day warning intervals published by competitors, and the 20-day and 10-day upload windows in circulation, have no official basis we could locate.

Common questions

What is the Wage Protection System in Saudi Arabia and which establishments must comply?

It is MHRSD's programme, launched in 2013, monitoring whether private sector employers pay wages on time and in the agreed amount. Qiwa states it applies to establishments with 10 or more employees and that, as of 31 December 2020, it applies to all private sector establishments including micro and small ones.

How many days does an employer have to upload the wage protection file to Mudad?

Thirty days from the due date, and the due date is the first day of each Gregorian month. The window was reduced from 60 days to 30 with effect from 1 March 2025.

What happens if the Mudad file is late — what gets suspended?

Mudad's list is the establishment or expansion visa quota request, visa issuance, conditional temporary disbursement for government contracts, transfer of labour between contracts, and issuance of the Saudization certificate. MHRSD adds the timing: at two months' delay all its services stop except work permit issuance and renewal; at three months those stop too, and workers may transfer to another employer without their current employer's consent.

How long is the wage protection certificate valid?

One month from the date of issuance, per Qiwa. Issuing it requires a compliance rate of 70% or higher over the past 12 months, or 50% or higher for a newly established entity.

Why does a WPS file get rejected?

Format errors — an incorrect IBAN, a repeated or missing bank signature, a missing establishment unified number, or payment in a currency other than the riyal — produce an error report, and the file must be corrected and re-uploaded. Matching errors instead produce violations against named workers, which are justified rather than re-uploaded.

What is the difference between Mudad and Qiwa?

Mudad is where the wage file is uploaded and the compliance percentage is calculated; its data comes from GOSI. Qiwa is the MHRSD labour platform holding employment contracts, establishment files and certificates, and where the consequences of non-compliance appear. Our Qiwa services page sets out what is transacted there.

Must salaries be paid from a Saudi corporate bank account?

In practice yes: the file is generated and electronically signed by the bank after the transfer, and Mudad states a file cannot be uploaded where salaries were paid in cash. The alternative to a bank payroll agreement is Mudad's own payroll system, which uploads the file automatically.

Can a payroll provider upload the file on my behalf?

Yes. The owner or the person delegated for wage protection may upload it, and an establishment delegates an employee through the job roles page using their ID number, email, branch and role. The delegate must be an employee of the same establishment. This is delegation to act for you; you remain the employer.


Where this leaves you

The month has a shape, and it is not the one most payroll calendars assume. The due date is the 1st. The file is the bank's, not yours. The reconciliation is against GOSI, and so is the headcount you are scored against. Violations are cleared by justification, and the worker has three days to answer before the system decides for itself. The penalty that hurts is not the fine — it is the quota and visa block, and MHRSD sequences it: two months of delay stops its services but leaves work permits running, and three months stops those too and lets your workers leave without your consent. It is a quiet escalation rather than a silent one, which is worse in practice, because nothing on your desk fails while it is happening.

SCPL runs that cycle for companies operating in Saudi Arabia, as part of GOSI, WPS and Mudad compliance and payroll outsourcing. We act on your government portals as your authorised agent; you remain the legal employer throughout. SCPL does not hold a licence for internal labour outsourcing (تعهيد القوى العاملة) under MHRSD Ministerial Resolution 60339 and does not supply labour — a separately licensed activity, and the distinction is set out here. Head office Dammam, second office Riyadh.

If you are an employee checking whether your own wage was recorded rather than an employer running payroll, Mudad and the MHRSD unified number 19911 are the right channels, not us — SCPL works with companies, not individuals. Our own vacancies are at /careers.


Official sources