HR system for Saudi companies: modules and integration with GOSI and Mudad

An HR system for Saudi companies should hold one clean record per employee and keep it in step with three government platforms: GOSI for social insurance registration and wages, Qiwa for documented contracts and occupations, and Mudad for the monthly wage protection file. Pick modules by headcount, and test every integration live before you sign.

This guide explains what each module does, what it has to exchange with GOSI, Qiwa and Mudad, how employee data falls under the Personal Data Protection Law (PDPL), and how to compare HR software with a 12-point checklist. The platform rules were checked on the official sites on 14 October 2026. It is general information, not legal advice: for a specific case, check the official source or ask a licensed advisor.

What an HR system does for a Saudi company

An HR system (sometimes sold as an HR suite or HR solutions) is the software that holds employee records and runs the processes around them: contracts, payroll, attendance, leave, requests and reports. In Saudi Arabia it has a second job. Most HR events also have to be reported to, or mirrored from, a government platform, and the deadlines are short.

Three platforms matter most:

• GOSI registers employees for social insurance, holds the contributory wage and invoices the establishment every month.
• Qiwa, the Saudi labour-market platform, documents employment contracts, manages occupations and hosts the work regulations.
• Mudad receives the bank's wage file for the Wage Protection System and measures each establishment's compliance.

A spreadsheet can track ten employees. Once the company has several branches, a mix of Saudi and non-Saudi staff, or shift work with overtime, the number of events per month makes a system worth its cost.

The core modules and when you need each

The "typically needed from" column is our editorial judgement, not a rule. A ten-person company with night shifts may need attendance before a fifty-person office does.

Integration with GOSI: the events your HR system must catch

GOSI's business services cover registering a contributor, updating wages, excluding a contributor who leaves, reporting a work injury and viewing the establishment's invoice [4]. Each of these starts as an event in your HR system, and GOSI's regulations under the 1445H Social Insurance Law set the deadlines [5].

Two practical points follow. The payroll module must know which GOSI system each Saudi employee is on, because the pension rate for people first registered on or after 3 July 2024 rises every July until 2028 [5]. And the HR system should raise a task for each event above, with its deadline, rather than relying on someone to remember.

Integration with Qiwa: contracts and occupations

Qiwa's contract service lets business owners and HR teams create, update and end employment contracts, free of charge. Contracts are documented in Qiwa first and then updated automatically in GOSI, not the other way round. Every employee's contract should be documented from the start date, including during probation, and a contract offer that the employee neither accepts nor rejects is cancelled automatically after 10 days [6].

For an HR system, that means Qiwa is the master record of contract status. The HR system can draft the offer and store the signed copy, but it should mirror what Qiwa shows rather than keep a separate truth.

Occupations work the same way. Qiwa's occupation service shows a compliance indicator: the number of employees whose occupations match the Saudi Unified Classification of Occupations, and how many correction requests the establishment still needs to issue [3]. Saudization decisions that target specific occupations are checked automatically against the occupational titles held in GOSI's database [7], so the HR system's job titles should map to the official occupation code, not just to an internal title.

Qiwa also hosts the work regulations every establishment needs. Establishments with 49 employees or fewer can use the model regulations, which the Ministry approves automatically; those with 50 or more need customised regulations prepared by a law firm approved by the Ministry [8]. Your leave, overtime and discipline settings in the HR system should copy the approved regulations.

Integration with Mudad and the Wage Protection System

The Wage Protection System proves that salaries were paid on time and in full. Wage files are uploaded only through Mudad, within 30 days of the due date, which is the first day of each Gregorian month. The file is issued by the bank after the transfer, so salaries paid in cash cannot be uploaded, and continued non-compliance can lead the Ministry to suspend services such as visas and the Saudization certificate [9].

There are two common set-ups:

1. Your HR system produces the bank salary file. The bank pays the salaries and issues the wage protection file, which someone uploads to Mudad.
2. Payroll runs through Mudad's own payroll system. It reads company and employee data through Mudad's link with GOSI and uploads the wage protection file automatically after each transfer. Mudad states that customers of HR systems can use its payroll services to transfer salaries and get the automatic upload [10].

Either way, the HR system should store the WPS file reference for each month next to the payroll run, so the compliance rate in Mudad can be traced back to a specific payment.

Employee data and the PDPL

An HR system holds more personal data than almost any other system in the company. Under the Personal Data Protection Law, health data, credit data and biometric data that identifies a person are all sensitive data. Collected data must be limited to the minimum needed for the purpose, and the controller must publish a privacy policy that people can read before their data is collected [11].

Three settings deserve attention before go-live:

• Biometric attendance. Fingerprint and face scans are biometric identity data; collect them only where a simpler method will not do, and restrict who can see them.
• Medical certificates and sick leave. Keep them in a restricted section, not in the general employee file.
• Hosting location. If the vendor stores data outside the Kingdom, transfers must meet the PDPL's conditions; our guide on data residency in Saudi Arabia walks through them.

HR system checklist: 12 questions for every vendor

Ask each vendor to show the answer live, on your data or realistic test data, rather than on slides.

1. Language and calendar. Full Arabic and English interfaces, with Hijri and Gregorian dates.
2. Employee record. Fields for ID or iqama, nationality, GOSI system, Qiwa contract reference and occupation code.
3. Payroll rules. Different GOSI rates per employee, the SAR 45,000 cap on the contributory wage, and a clear audit trail.
4. Attendance and overtime. Daily or weekly standard, Ramadan hours, rest-day hours as overtime, compensatory leave.
5. Leave types. Annual leave at 21 and 30 days, plus the leave types added in 2025.
6. GOSI events. A task with a deadline for every hire, exit and wage change.
7. Qiwa. Contract status and occupations mirrored from Qiwa, with no second version kept in the HR system.
8. Mudad. A bank salary file in your bank's format, or a working route through Mudad's payroll system.
9. Saudization view. Saudi share by entity and by occupation code, ready for Nitaqat planning.
10. Self-service. Leave requests, approvals and letters on mobile, in both languages.
11. Data protection. Hosting location, role-based access, an audit log, handling of biometric and health data, and a full export of your data.
12. Price and exit. Price per employee per month, implementation fee, Arabic support hours and what happens to your data if you leave.

Not every vendor connects directly to every platform. Ask which steps are automatic, which are a file you upload, and which stay manual, and price the manual steps in staff hours.

Ready-made HR solutions, connected systems or a custom build?

Most small and medium companies are best served by a ready-made HR system plus Mudad and the government portals. A company with unusual shift patterns, several legal entities or an existing ERP may need its HR system connected to other software, and a few need a tailored build. Our guide to custom software development in Saudi Arabia sets out when to buy, connect or build.

Whatever you choose, roll it out in six steps:

1. Clean the master list. Match every employee against GOSI's contributor list and Qiwa's employee list before importing anything.
2. Fix occupations in Qiwa first. Correct codes there, then copy them into the HR system.
3. Configure from your approved work regulations. Leave, overtime, allowances and discipline settings follow the regulations, not a vendor's default template.
4. Run one parallel month. Calculate payroll in the old way and in the new system, and reconcile both with the GOSI invoice.
5. Train HR and line managers, then switch on self-service for employees.
6. Review after 90 days. Check missed GOSI deadlines, Mudad compliance and the requests still handled outside the system.

Your next step

This week, list every HR event from the last three months (hires, exits, wage changes, injuries, leave and overtime) and note which platform each one touched and how long it took. That list becomes the brief for your HR system for Saudi companies: the modules you need, the integrations to test live, and the manual steps worth removing. If an AI assistant could help with the letters and requests that remain, our guide on AI agents, RPA and workflow tools shows which kind of automation fits which step. You can read more about O AI, a software and AI company in Al Khobar, on our home page.