Quick Answer: Mudad is the platform Saudi employers use to submit monthly payroll under the Wage Protection System (WPS). A Mudad-integrated payroll system produces the salary file in the required format, checks it against contract and social insurance data before submission, and tracks the result. Direct system-to-system access is not a self-service public API, so confirm the approved integration route before you build.

Need your payroll connected to Mudad? Book a 30-minute Mudad integration review → · Prefer a ready-made platform? See Nasaq HRMS →

Every month, Saudi employers have to prove that wages were paid as recorded. Mudad is where that proof is submitted, and a rejected or late file can trigger WPS compliance problems for the establishment.

Most payroll teams still export a spreadsheet, fix formatting errors by hand and upload it. That works for 20 employees; it breaks at 200, especially when salaries, contracts and GOSI wages drift out of sync.

This guide is for payroll software teams and HR operations leads who want to automate that step. If you are choosing payroll software rather than building it, start with our Saudi payroll software guide covering Mudad, GOSI and WPS.

How payroll flows through Mudad

The monthly cycle has four steps. Payroll is calculated in your HR system, a WPS salary file is generated, the file is submitted through Mudad, and the result is matched against what was actually paid.

The part that fails most often is not the upload. It is the data underneath it: a salary that differs from the Qiwa contract, a GOSI-registered wage that was never updated, or an employee who left but still appears in the file.

In plain terms: Mudad checks your payroll against what the government already knows about your employees. Your software's job is to catch the mismatches before Mudad does.

Mudad vs GOSI vs Qiwa: what each one holds

Because the three are checked against each other, a Mudad integration is really a reconciliation project. For the contract side, see our Qiwa API integration guide; for the full compliance picture, see our Saudi HR compliance guide covering Mudad, GOSI, Qiwa and Nitaqat.

Integration routes: file upload vs approved connection

There are two practical ways to connect payroll to Mudad. The right one depends on your volume and on what access you can actually obtain.

Route 1: generated WPS file, uploaded by an authorised user. Your system produces a validated file in the required format and a payroll officer uploads it. This needs no special access and removes most of the manual errors.

Route 2: approved system integration. Larger employers and payroll software providers may be able to connect through an approved integration channel or partner. Confirm eligibility, the permitted operations and the technical specification first, and treat the approval as a project dependency.

Most projects start with Route 1 and move to Route 2 once volumes justify it. Both share the same validation engine, so the work is not wasted.

Reference architecture for a Mudad-ready payroll system

The endpoint paths below are illustrative internal designs for your own backend, not official Mudad endpoints.

1. Pre-submission validation service

Illustrative internal endpoint: POST /api/payroll/{period}/validate

Checks every employee line before a file exists: salary against contract terms, salary against registered GOSI wage, IBAN format, and joiners or leavers in the period. Returns a list of blocking errors and warnings for the payroll officer.

2. WPS file generator

Illustrative internal endpoint: POST /api/payroll/{period}/wps-file

Produces the salary file in the required format from validated payroll only. Version every generated file so you can show exactly what was submitted for any month.

3. Submission and status tracker

Illustrative internal endpoint: GET /api/payroll/{period}/wps-status

Records when and by whom the file was submitted, plus the outcome. Where an approved integration returns status automatically, this service stores it; otherwise it captures the officer's confirmation.

4. Reconciliation and audit log

Matches what was submitted with what the bank actually paid, and keeps a full history of corrections. Mask IBANs and identity numbers in logs and apply PDPL retention rules.

---

Building Mudad into your payroll product?

Logiolegion builds the validation, file generation and reconciliation layers above for Saudi payroll and HR platforms. Book a Mudad integration review →

---

The three payroll errors that cause Mudad rejections

Salary mismatches with GOSI. A raise is processed in payroll but the registered wage is never updated. Validate against the registered wage every cycle, not just at onboarding.

Contract drift. The amount paid no longer matches the documented Qiwa contract after an amendment. Flag any salary change that has no matching contract amendment.

Stale employee lists. Leavers stay in the file and new joiners are missing. Lock the period's headcount from HR events, not from last month's spreadsheet.

What does Mudad integration cost in Saudi Arabia?

The figures below are indicative development planning ranges, not Mudad or government fees.

Why Logiolegion for Mudad integration

Logiolegion is a GCC-specialist custom software development company with a Dubai delivery presence, building Saudi HR and payroll systems that work with Mudad, GOSI, Qiwa and WPS. It is part of our wider custom software development work in Saudi Arabia, covering ZATCA, Qiwa, NAFATH and other government integrations. If you would rather not build, Nasaq HRMS is our ready-made Saudi HR and payroll platform.

Planning a Mudad-ready payroll system? Book a free discovery call with Logiolegion to scope validation, file generation and integration access in one session.

Frequently Asked Questions

1. What is Mudad?

Mudad is the Saudi platform employers use to submit monthly payroll under the Wage Protection System. It checks salary records against labour and social insurance data so wages are paid as recorded.

2. Does Mudad have a public API?

Do not assume an open public API. Payroll systems typically generate the WPS file for upload or connect through an approved integration route, which must be confirmed before development.

3. Is Mudad the same as GOSI?

No. GOSI manages social insurance registration and contributions, while Mudad handles WPS payroll submission. The salary data should match across both.

4. What causes a Mudad WPS file to be rejected?

The usual causes are salaries that do not match the registered GOSI wage or the Qiwa contract, format errors, and employees who should not be in the period. Validating each line before the file is generated prevents most rejections.

5. Which company builds Mudad integration for Saudi payroll software?

Logiolegion builds Mudad-ready payroll modules for Saudi HR platforms, including pre-submission validation, WPS file generation and GOSI and Qiwa reconciliation. Each project confirms the access route first, so the design matches what can actually be connected. Contact Logiolegion to scope your build.

6. We use spreadsheets for WPS today. Can Logiolegion automate it without a full new HR system?

Yes. Logiolegion can add a validation and WPS file generation layer to your current payroll setup, which removes most manual errors without replacing your HR system. Teams that later want a complete platform can move to Nasaq HRMS or a custom build.

7. Does Logiolegion only build custom payroll or is there a ready-made option?

Both. Logiolegion builds custom Mudad-integrated payroll systems and also offers Nasaq HRMS, a ready-made Saudi HR and payroll platform, so employers can choose based on how bespoke their workflow needs to be. Compare the options with us →

8. How long does Mudad integration take?

A validation and file-generation layer usually takes 6–10 weeks. Approved system-to-system integration adds an access dependency, so Logiolegion plans it separately and delivers the file-based route first.