WPS and Mudad in Saudi Arabia: how salary compliance actually works

In Saudi payroll, paying the right amount is only half the job. The other half is proving that wages were paid through the required channel, for the right employee, in the right period, from the right entity. WPS and Mudad sit at that intersection of payroll, banking and compliance.

This guide explains the practical workflow, the data that causes failures and the controls finance teams should build into the monthly cycle. It is a regulatory overview, not legal or tax advice.

WPS and Mudad are related, not identical

WPS — the Wage Protection System — is the requirement to pay wages through approved channels and maintain evidence of the payment. Mudad is the platform used to manage and evidence salary compliance. They sit in the same control chain, but they answer different questions.

The monthly WPS workflow

1. Finalise and approve the payroll register.
2. Generate the salary file from the approved payroll, not a separate spreadsheet.
3. Validate employee identifiers, bank details, entity, currency and net salary.
4. Fund the correct entity or bank account and obtain payment approval.
5. Release the payment through the bank or approved channel.
6. Submit the salary file through the required process.
7. Capture payment evidence and resolve rejected or returned payments.
8. Reconcile payroll, bank, WPS/Mudad and the general ledger.

What the salary file needs to be right

The salary file is a control document, not a formatting exercise. Each line should be traceable to an employee, an approved payroll run, a legal entity and a bank payment.

• Employee identifier and name as held in the official records.
• Correct legal entity and establishment.
• Bank account and IBAN in the employee’s name.
• Pay period, currency and net salary.
• Payment status and reason for any exception.
• Reference to the payroll run and approval.

The most common problem is not the file layout. It is a mismatch between the payroll register and the data used for payment. A late bank-detail change, a salary adjustment after approval, or an employee moved between entities can all produce a clean-looking file with the wrong content.

Where WPS failures usually start

• Employee master: wrong identifier, nationality, entity or bank account.
• Payroll cut-off: late joiners, leavers, overtime or commissions not included.
• Approval: payment released before the final payroll review.
• Funding: paid from the wrong entity or account.
• Bank: rejected payment, closed account or name mismatch.
• Exception handling: correction made outside the system without evidence.
• Reconciliation: payroll, bank and GL never formally agree.

Exceptions are part of the process

Not every payroll line can be paid normally. Employees may be on leave without pay, have a new bank account, be in a final settlement, or have a correction from a prior period. The control is not to eliminate exceptions; it is to capture them, approve them and evidence them.

• Define who can approve an exception and at what value.
• Record the reason, supporting document and payroll impact.
• Keep the exception visible in the reconciliation.
• Do not let an exception become a permanent off-system workaround.

Multi-entity and multi-bank payroll

Saudi groups often run several legal entities, each with its own bank account and payroll obligations. A single group payment file can create a clean treasury view but a poor statutory trail. Keep entity-level controls and group-level reporting separate.

• Map each employee to the correct legal entity and bank account.
• Reconcile each entity’s payroll and bank independently.
• Control secondments, shared employees and intercompany recharges.
• Consolidate reporting without merging statutory records.

How open banking fits

Open banking can connect the approved payroll file to the bank payment process, capture payment status and improve reconciliation. It can reduce manual uploads and give finance a clearer view of failed or pending payments. It does not remove the need for payroll approval, WPS requirements, bank controls or statutory evidence.

The strongest design is usually: payroll system → approved salary file → bank/open-banking payment → payment status → reconciliation. Each step should retain the same reference.

What to review every month

• Does the approved payroll register match the salary file?
• Does the bank payment match the salary file by employee and amount?
• Are all exceptions documented and approved?
• Does the payroll liability reconcile to the GL?
• Are rejected or returned payments cleared before the next cycle?
• Is the evidence retained and easy to retrieve?

Frequently asked questions

Where this fits

WPS and Mudad are one part of the wider KSA payroll compliance lifecycle. For the contribution side, read the GOSI guide. For the operating model, see our managed payroll service and open-banking payroll integration.