Odoo HR Payroll in Saudi Arabia: What the Localization Covers and What Still Needs Setup

Odoo HR Payroll in Saudi Arabia: What the Localization Covers and What Still Needs Setup
HR and finance leads who evaluate Odoo HR payroll in Saudi Arabia usually ask the same question: how much of Saudi payroll does the system handle on day one, and how much depends on our own setup? The honest answer is that Odoo's Saudi payroll localization gives you a solid base, with salary rules, GOSI contribution parameters, end-of-service provisions and a Wage Protection System (WPS) export, but the result is only as accurate as your employee data, your contracts and the decisions you make during configuration.
This guide sets out what a Saudi employer needs from a payroll and HR system, what Odoo's documentation says the localization covers, what still needs configuration or a local partner, and how to migrate, test and go live safely. It does not repeat the legal hiring steps; for those, read our guide on hiring employees in Saudi Arabia through Qiwa, GOSI and wage protection. If you are still deciding whether Odoo suits your business overall, start with our Odoo ERP guide for Saudi businesses.
Table of Contents
- What a Saudi payroll and HR setup has to handle
- What Odoo HR payroll in Saudi Arabia covers out of the box
- What still needs configuration, decisions or a local partner
- Data migration and parallel payroll runs
- Controls, audit trail and employee data protection
- Go-live checklist and common mistakes
What a Saudi payroll and HR setup has to handle
Before comparing software, list what your payroll process must produce every month. For most Saudi employers the core requirements are:
- Employee master data. Legal name, nationality, Saudi National ID or iqama number, work location, bank IBAN and, for expatriates, iqama and work permit details. Nationality matters because GOSI treatment differs between Saudi and non-Saudi employees.
- Employment contracts. Contract type and dates, basic wage, allowances such as housing and transport, working schedule and probation. Contracts documented on Qiwa should match what payroll pays.
- Salary structure. A clear split between basic salary, fixed allowances, variable inputs (overtime, commissions, deductions) and employer-paid costs such as medical insurance and iqama fees.
- GOSI contributions. Employer and employee contributions calculated on the correct base, recorded as a liability and paid on time.
- End-of-service benefits. A monthly accrual and, on exit, a final settlement that follows the Labor Law rules for length of service and reason for leaving.
- Leave. Annual leave balances, leave salary and the treatment of untaken leave at exit.
- Wage Protection System file. A salary file, uploaded through the Mudad platform, that shows what each employee was paid and when.
- Accounting. Journal entries reconciled to bank payments.
- Saudization reporting. Reliable headcount by nationality to monitor your Nitaqat position.
If any of these lives in a spreadsheet only one person understands, fix that first, whichever system you choose.
What Odoo HR payroll in Saudi Arabia covers out of the box
Odoo's Saudi Arabia payroll localization documentation for version 19.0 describes two modules: Saudi Arabia - Payroll (l10n_sa_hr_payroll), which provides the salary structure and rules, and Saudi Arabia - Payroll with Accounting (l10n_sa_hr_payroll_account), which posts payroll to the books. As documented, the localization covers the following:
- Company setup. The Ministry of Labor (MoL) number, SAR currency, an establishment bank account marked as trusted and the MoL Establishment ID in payroll settings.
- Saudi employee fields. A 10-digit Saudi National / IQAMA ID used in the WPS export, a non-editable annual leave balance, monthly housing, transportation and other allowances, and annual amounts for iqama fees, medical insurance and work permits.
- Payroll blocked without a trusted bank account. Odoo shows a warning and will not run payroll for an employee who has no trusted bank account (IBAN).
- Salary structure. A KSA Employee structure with two structure types: Saudi Arabia: Monthly Pay and SA Salary Advance And Loan Structure.
- GOSI contributions in Odoo. Rule parameters for Saudi company contributions, non-Saudi company contributions and Saudi employee contributions. The employee's nationality determines which rate applies.
- Overtime. A Saudi Arabia overtime rate parameter, with work entries drawn from working schedules, the Attendances app or the Planning app.
- End of service provision. A number-of-days field on the employee record, with the benefit accrued monthly to an end-of-service provision account.
- Accounting. Fifteen Saudi chart-of-accounts payroll accounts, including GOSI payable and end-of-service and leave provisions.
- Loans and advances. Loans repaid automatically through salary adjustments; advances paid off-cycle and recovered later.
- WPS file. A Saudi WPS export generated per payslip or per pay run, which Odoo states is structured according to the technical guidelines issued by the Ministry of Human Resources and Social Development (MHRSD).
Odoo adds updated rule parameters each calendar year and advises editing them only when an official rate changes. The dedicated Saudi payroll page appears in the 19.0 documentation; features can differ in other versions, and the page does not address edition or hosting, so confirm both with your partner before planning.
What still needs configuration, decisions or a local partner
The localization is a starting point. These areas usually need deliberate setup, testing or process work outside Odoo:
| Area | What Odoo documents | What you still own |
|---|---|---|
| GOSI | Contribution parameters by nationality; GOSI payable account | Checking rates and the contribution base against GOSI before go-live; registration and monthly payment through GOSI's own channels; reconciling Odoo's liability to GOSI's figures |
| End of service | Number-of-days field and monthly provision | Testing final settlements against the Labor Law rules, which differ by years of service and by whether the employee resigned or the employer ended the contract |
| WPS and Mudad | Saudi WPS file export | Uploading the file through Mudad, as the MHRSD wage protection upload service describes, confirming your bank's and Mudad's acceptance in a test month, and explaining any non-compliance flags |
| Leave | Annual leave balance from a chosen time off type; leave provision account | Defining leave types, accrual rules and approval flows that match your contracts and policy |
| Contracts and Qiwa | Contract dates, wage type, contract type, allowances | Keeping Odoo contracts consistent with contracts documented on Qiwa; Odoo's page does not describe a Qiwa integration |
| Saudization | Nationality on each employee | Building a headcount report by nationality; the documentation does not describe a Nitaqat report |
| Company-specific pay | Standard rules and inputs | Bonuses, commissions, shift and site allowances, deductions policy and multi-company structures |
End of service deserves particular care. The MHRSD end-of-service award summary describes half a month's wage for each of the first five years and a full month for each later year, based on the last wage, with reduced entitlements when an employee resigns after shorter service. A single days-per-year field supports the monthly accrual, but your final settlement process must reflect these tiers and the reason for exit. Test a set of real leaver scenarios before relying on any calculation.
A local partner adds most value where payroll meets other systems: the chart of accounts, bank formats, attendance data and, if you invoice from Odoo, the separate Odoo e-invoicing module, which sits in the same database but follows its own setup.
Data migration and parallel payroll runs
Most go-live payroll problems come from migrated data, not the software. Treat migration as its own workstream:
- Freeze a cut-over date. Choose the first month Odoo will pay, ideally not a month with annual increments, bonuses or a large intake.
- Clean employee records. Reconcile names, ID and iqama numbers, nationality and IBANs against official records and your current payroll. One wrong ID can affect the WPS file.
- Load opening balances. Bring in leave balances, accrued end-of-service provisions, outstanding loans and advances, and year-to-date figures you need for reporting. Document the source and date of each balance.
- Map pay elements. Match each line of your current payslip to an Odoo salary rule or input. Anything without a match needs a decision before testing.
- Run at least one parallel month. Run payroll in the old process and in Odoo for the same month and compare net pay, GOSI, provisions and journal entries employee by employee.
- Agree tolerance and sign-off. Decide in advance which differences are acceptable (for example rounding) and who signs off that Odoo is ready.
Keep the parallel run results: they are your evidence for auditors and management that the new figures can be trusted.
Controls, audit trail and employee data protection
Payroll combines money and personal data, so controls matter as much as calculations:
- Segregation of duties. The person who edits salaries or contracts should not be the person who validates the pay run or releases the bank payment.
- Approval steps. Odoo's documented flow already separates validating work entries, computing and validating payslips, posting journal entries and generating payments. Assign each step to a named role.
- Change log. Review salary, bank account and rule parameter changes before each pay run, and restrict who can mark a bank account as trusted.
- Reconciliation. Reconcile net pay to bank transfers, the GOSI payable to GOSI's figures and the WPS file to the payslips every month.
- Restricted access. Limit payroll data to those who need it, including in test databases.
Employee records contain identity numbers, bank details, salaries and often medical insurance data, all of which fall under Saudi Arabia's Personal Data Protection Law (PDPL). In general terms, that means collecting only what you need, telling employees how their data is used, keeping it secure, setting retention periods and controlling transfers to systems or hosting outside the Kingdom. Our PDPL compliance checklist explains the core obligations; apply the same principles to HR data.
Go-live checklist and common mistakes
Go-live checklist
- Company VAT number, MoL number, MoL Establishment ID and trusted establishment bank account (with Bank Establishment ID and SARIE code) are set.
- Every employee has nationality, a Saudi National / IQAMA ID, a trusted IBAN, a valid contract and the KSA Employee pay category.
- Allowances and employer-paid costs match contracts.
- GOSI rule parameters have been compared with GOSI's published rates for the year.
- Leave types, balances and the annual leave time off type are configured.
- Opening end-of-service, leave and loan balances are loaded and reconciled.
- At least one parallel month matches within the agreed tolerance.
- A test WPS file has been generated and checked against Mudad and bank requirements.
- Journal entry posting (per payslip or batched) is decided before the first run.
- Roles, approvals and access rights are documented.
Common mistakes
- Editing rule parameters casually. Change them only when an official rate changes, and record why.
- Missing or untrusted bank accounts. Payroll and WPS files fail for those employees.
- Assuming the end-of-service accrual equals the final settlement. Test resignation and termination cases separately.
- Contracts that differ from Qiwa. Payroll then pays one figure while the documented contract shows another.
- Skipping the parallel run. Errors surface in employees' bank accounts instead of in testing.
- Treating payroll as an IT project. HR and finance must own the rules and sign-off.
Our Odoo ERP implementation team can help configure and test the Saudi payroll localization, and Odoo ERP consulting can support process design and a review of an existing setup. Where payroll entries feed your books, our accounting management services can support monthly reconciliation. Labor, social insurance and wage protection rules are updated from time to time, so confirm the current requirements with MHRSD, GOSI or a qualified adviser before go-live.
Frequently Asked Questions
Does Odoo have a Saudi payroll localization?
Yes. Odoo's 19.0 documentation describes a Saudi Arabia payroll localization with two modules: one for salary structures and rules, including GOSI parameters, end-of-service provisions and a WPS export, and one that links payroll to accounting. Features and screens can differ by version, so confirm what your database supports before planning the rollout.
Does Odoo calculate GOSI contributions?
Odoo's Saudi localization includes rule parameters for employer contributions for Saudi and non-Saudi employees and for Saudi employee contributions, with the rate driven by the employee's nationality. The amounts post to a GOSI payable account. You should still compare the parameters with GOSI's official rates and reconcile the liability to GOSI's figures each month.
Can Odoo produce the Wage Protection System file for Mudad?
Odoo can generate a Saudi WPS file per payslip or per pay run, which it states follows MHRSD's technical guidelines. The file is then uploaded through the Mudad platform. It requires the MoL Establishment ID, a trusted establishment bank account with its bank codes, and a National ID or iqama number for every employee. Test it with a real month before go-live.
How long does it take to move Saudi payroll to Odoo?
It depends on headcount, the number of pay elements, data quality and whether Odoo already runs your accounting. The longest steps are usually cleaning employee data, loading opening balances and running one or two parallel months, so plan the timeline around these rather than around installing the software.
Planning to run your Saudi payroll, GOSI and HR records in Odoo? Contact Sokrab Saudi Arabia today.
Category
Latest articles
-
Audit Requirements in Saudi Arabia: SOCPA Standards and What Companies Must Prepare for a Statutory Audit
Audit requirements in Saudi Arabia explained: who needs a statutory audit, the small-company exemption, SOCPA standards and an audit preparation checklist.
-
Social Media Advertising in Saudi Arabia: Choosing Between Snapchat, TikTok, Instagram, X and LinkedIn
Social media advertising in Saudi Arabia: compare Snapchat, TikTok, Meta, X and LinkedIn by objective, plus Arabic creative, tracking and a 30-day test plan.
-
LLC Articles of Association in Saudi Arabia and Shareholder Agreements: What Each Document Does
LLC articles of association in Saudi Arabia explained: what the Companies Law requires, what a shareholder agreement adds, plus a checklist to get both right.