A retailer with a head office and several stores across Riyadh needs GOSI, end-of-service and WPS handled correctly in Odoo HR, not assumed to work because the module exists.

Odoo's HR applications cover recruitment, employee records, contracts, time off, attendance, appraisals and payroll. For a business already running Odoo Accounting, adding HR keeps employee cost flowing into the ledger and project costing without a separate interface. The critical question is payroll localization, and it deserves a direct answer before the module is chosen.

The Saudi payroll localization question

Odoo's standard payroll does not include Saudi statutory rules out of the box in the way an enterprise platform does. Saudi payroll runs on a localization module, and these vary considerably in quality and maintenance. Before committing we check five things. Does the module handle GOSI rates for Saudi and non-Saudi employees? Does it accrue end-of-service under the Labor Law formula? Does it cover statutory leave types? Does it generate WPS files for your specific bank? And is it actively maintained against regulatory change?

Core HR and self-service

Employee records, contract history, document expiry tracking for iqamas and certifications, and organizational structure are all handled well in standard Odoo. Self-service lets employees submit leave requests and view balances in Arabic or English, and manager approval flows follow the reporting structure. For a business moving from spreadsheets and paper forms, this is often the most visible improvement.

Attendance and time off

Attendance can be captured through kiosk, mobile or biometric device integration, feeding overtime and absence calculations. Leave types are configured for Saudi statutory entitlements alongside company policy, with accrual rules and carry-forward handled by the system. This needs deliberate configuration, because default settings may be built for other markets.

A hypothetical example

Imagine a Riyadh trading company that tracks leave in a shared spreadsheet and calculates end-of-service by hand when someone resigns. With a maintained Saudi payroll module, iqama expiry alerts and employee self-service, leave balances would be visible to everyone and the company could produce an accrued end-of-service liability figure for its auditors.

Knowing the limits

Odoo HR suits small and mid-sized employers with reasonably standard arrangements. Businesses with complex shift patterns, multi-entity payroll under separate registrations, or advanced talent and succession needs will find it thinner than a dedicated platform such as Oracle HCM. We say so where that is the case, and we do not stretch the tool beyond what serves you.

Document expiry as an operational control

For Saudi employers, iqama, passport, medical insurance and professional certification expiries carry operational consequences, since an expired iqama can stop an employee from working. Odoo tracks these with automated alerts to HR and the line manager at defined intervals, which turns a recurring administrative scramble into a managed process. This connects to workforce planning, because renewal timing and Saudization ratios interact.

Starting with records before payroll

We usually recommend implementing employee records, leave and attendance first and moving payroll to a second phase. This gives the team time to adapt at low risk and makes sure employee data is clean before payroll depends on it. Payroll built on incomplete records produces errors that look like system errors but are data errors.