KSA payroll compliance: GOSI, WPS, Mudad, Qiwa and end of service

A Saudi payroll run can look correct on the payslip and still be wrong. The salary may have been paid, but the GOSI wage is different, the WPS file does not reconcile, the employee change was late, or the end-of-service accrual was never reviewed. In Saudi Arabia, payroll is a chain of statutory and financial controls — not a calculator.

This guide is written for finance, HR and ERP teams running payroll in the Kingdom. It covers the monthly lifecycle, the local interfaces that matter and the questions to ask before configuration begins. It is a regulatory overview, not legal or tax advice.

Why KSA payroll is different

Most payroll products can calculate basic salary, allowances, deductions and net pay. The difficult part in Saudi Arabia is the surrounding compliance and evidence:

• GOSI — registration, contributory wage and monthly contribution reconciliation.
• WPS and Mudad — salary payment through approved channels, salary files and evidence of compliance.
• Qiwa — employment contracts, work permits and establishment data.
• Nitaqat and Saudization — headcount and nationality mix can affect the establishment’s classification.
• Absher and Muqeem — iqama, visa and dependant data for expatriate employees.
• Saudi Labour Law — leave, overtime, Ramadan and Eid, notice, probation and end-of-service.
• Multi-entity reality — groups often run several legal entities, banks, GOSI numbers and approval chains.

The monthly payroll lifecycle

A controlled payroll cycle starts before the payroll run and ends after the payment. The exact sequence varies by company, but the control points are consistent.

Onboarding: the payroll record starts before payroll

Most payroll defects are created before the first payroll run. The employee master, contract, GOSI registration, bank account and cost centre need to agree from day one.

• Contract type, start date, probation, notice period and leave entitlement.
• Basic salary, allowances, variable pay and benefit eligibility.
• GOSI registration and the wage elements that form the contributory wage.
• Bank account and WPS eligibility, including the correct legal entity.
• Iqama, visa, work permit and Muqeem/Absher data for expatriate employees.
• Department, cost centre, project and approver for management reporting.

The onboarding checklist should be owned jointly by HR and finance. If HR changes a contract and payroll is not updated, the error usually surfaces at GOSI, WPS or the final settlement.

Payroll inputs: what changes the number

Saudi payroll is not only basic salary. The payroll design has to define how each element behaves in the payroll register, GOSI, WPS, end-of-service and the general ledger.

• Basic salary — the anchor for many calculations and contract terms.
• Allowances — housing, transport, phone and other contractual or discretionary payments.
• Variable pay — commissions, bonuses, incentives and sales-based pay.
• Overtime — eligibility, rate, approval and payroll period.
• Leave — annual, sick, unpaid and other absences, including carry-forward rules.
• Deductions — advances, penalties, benefit contributions and recoveries.
• One-off adjustments — arrears, corrections, final settlements and retroactive changes.

Each element needs an explicit rule: is it pensionable, included in the GOSI wage, included in the WPS salary, included in end-of-service, and which GL account and cost centre does it hit? “It depends on the payroll team” is not a control.

GOSI: registration, wage base and reconciliation

GOSI is a monthly statutory process, not an annual registration. The employer needs to register employees, maintain the contributory wage, submit contributions and reconcile the result to payroll.

Contribution rates, wage ceilings and treatment can change. Confirm the current rules with GOSI before configuring rates or signing off a payroll. The system should store the rule and the effective date, not a hard-coded number hidden in a formula.

WPS and Mudad: payment is not the same as evidence

The Wage Protection System is designed to evidence that wages were paid through approved channels. A bank transfer on its own is not the whole control. The salary file, bank disbursement, salary register and Mudad record need to tell the same story.

1. Finalise the payroll register and approve the payment file.
2. Validate employee identifiers, bank details, entity, currency and net salary.
3. Fund the correct entity or bank account and release the payment.
4. Upload or submit the required salary file through the approved process.
5. Capture payment evidence and resolve rejected or returned payments.
6. Reconcile the bank, payroll register and statutory record.

Common failures include a salary that differs from the WPS file, an employee paid from the wrong entity, a closed bank account, a late joiner not included, a leaver paid twice, or an exception cleared without supporting evidence. These are payroll control failures, not bank failures.

Qiwa, Nitaqat and Saudization

Qiwa holds employment contracts and establishment data. Nitaqat classification is linked to Saudization, and payroll headcount is part of the evidence base. When an employee joins, leaves or changes nationality status, the payroll, Qiwa and GOSI records should not drift.

• Keep contract dates and payroll effective dates aligned.
• Reconcile active headcount between HR, payroll, Qiwa and GOSI.
• Review Saudi and expatriate headcount before workforce decisions.
• Document part-time, flexible and contract arrangements correctly.
• Track establishment-level data if the group has multiple entities.

Labour law, leave and end-of-service

Payroll has to apply the employment contract and the Saudi Labour Law consistently. Annual leave, sick leave, public holidays, Ramadan hours, overtime, notice and probation all affect pay, accruals or final settlement.

End-of-service is one of the most visible payroll calculations. It depends on the final wage, length of service, reason for leaving and contract terms. The calculation should be documented, reviewed and reconciled to the accrued liability in the general ledger. Do not treat it as a last-day spreadsheet exercise.

The Saudi payroll calendar

A payroll calendar should include internal cut-offs and external deadlines. Exact dates and submission windows can change, so confirm the current requirements with the relevant authority and bank.

Ramadan and Eid affect working hours, holiday pay and bank cut-offs. Build the calendar around the actual month, not a generic template from another country.

Multi-entity and multi-branch payroll

Saudi groups often run multiple legal entities, each with its own GOSI registration, Qiwa establishment, bank accounts and approval chain. A single group payroll file can hide statutory problems.

• Separate payroll and statutory data by legal entity.
• Keep group reporting and consolidation separate from statutory submissions.
• Control intercompany recharges, secondments and shared employees.
• Reconcile each entity’s bank, GOSI and payroll independently.
• Give group finance a consolidated view without weakening entity controls.

What “good” looks like in the ERP

A payroll system is only useful if it creates a controlled record. The ERP should hold the employee master, contract, pay components, leave, payroll runs, approvals, bank disbursement, GL postings, cost centres and audit trail in one flow.

• Effective-dated employee and salary changes.
• Configurable pay components with payroll, GOSI, WPS and EOS treatment.
• Maker-checker approval before payment and before master-data changes.
• Bank file generation, reconciliation and exception handling.
• Payroll-to-GL reconciliation by entity, cost centre and account.
• Retained evidence for payroll, GOSI, WPS/Mudad and employee queries.

Common KSA payroll mistakes

• The payroll register, GOSI contributory wage and WPS salary file tell three different stories.
• New joiners, leavers and salary changes are updated after the payroll cut-off.
• Allowances and variable pay are treated inconsistently across contracts and payroll runs.
• Employee bank details are changed without maker-checker approval.
• Leave, unpaid absence and final settlements are calculated outside the system.
• Payroll is funded from the wrong entity or bank account.
• Mudad or WPS exceptions are cleared without a documented correction.
• Month-end payroll journals do not reconcile to the bank or the general ledger.

Local business context

Saudi payroll is shaped by how local businesses actually operate: family-owned groups, sponsorship-linked employee records, mixed Saudi and expatriate workforces, field and site-based teams, sales commissions, government contracts, Arabic payslips and multiple bank relationships.

That context is why a generic payroll template often fails. The design has to reflect the approval chain, the exception paths and the evidence the business needs when a bank, auditor, employee or authority asks a question.

Payroll readiness checklist

• Employee master, contracts and payroll effective dates agree.
• GOSI registrations and contributory wages are reconciled.
• WPS/Mudad salary files reconcile to payroll and bank.
• Qiwa headcount and contract data agree with HR and payroll.
• Leave, overtime and end-of-service rules are documented.
• Pay components have payroll, GOSI, WPS, EOS and GL treatment.
• Funding, approval and bank exception controls are defined.
• Payroll, bank and GL reconcile every month.
• Evidence is retained for audit and employee queries.

Frequently asked questions

How Finalytics helps

Finalytics runs managed payroll and implements HR and payroll systems for Saudi businesses. We work across GOSI, WPS, Mudad, Qiwa, Nitaqat, end-of-service and bank disbursement, using Finalytics ERP and open-banking integrations.

If you are assessing your payroll process, start with the managed payroll service, the HR and payroll system, or the detailed guides on GOSI and WPS and Mudad.