Where they started
Saudi HR keeps its own records: iqama numbers and expiry dates, GOSI, Hijri dates, air tickets, exit and return, end-of-service pay. On the old Odoo 13 system these sat in modules from several vendors.
Staff requests and payments also went through approval chains that the standard apps don't model.
What we built
The employee file
Iqama, GOSI and Hijri dates on the employee record, plus contracts, recruitment, memos, embassy letters and clearance.
Payroll and end of service
Overtime, loans and advances, and an end-of-service calculation that uses leave balances. Payroll posts to accounting.
Travel and leave
Air tickets, business trips, return from vacation and a printable Arabic leave form, each with its approval chain.
Self-service on the phone
A mobile portal where staff check in and out with their location and request leave, loans or advances.
Spend control and reports
Payment requests, admin expenses, analytic invoices, a cost ledger and VAT invoices with the ZATCA QR code.
Website orders
An API turns each course sold on the website into a customer, an invoice and a payment in Odoo.
What they have now
Three versions, one partner
From Odoo 13 to 17 in 2024 and to 19 in September 2026.
28 custom modules
The full Saudi HR cycle, from hiring to clearance, in one system.
Staff use their phones
Check-in and requests happen on the phone, not at a desk in HR.
Have a similar problem?
Tell us how your company works today. A free 20-minute call is enough to see whether we can help.

