One employee record for contracts, documents, leave and payroll inputs, built for Saudi labor rules and the data Qiwa requires.

Saudi HR teams juggle Qiwa, GOSI and Muqeem portals, an Excel of iqama expiry dates and an HR SaaS whose per employee fee rises with every hire, while the finance team keeps a separate list of the same people. Odoo Employees holds the master record every HR process reads from, and Naqlah, Odoo partner in Saudi Arabia, configures contract types, document alerts and access rules to fit Saudi practice.
Contract fields in Odoo mirror what Qiwa documents: contract type, start date, probation up to 180 days when written in the contract, the one year default term for non Saudi staff and the 60 and 30 day notice periods, so the Odoo record and the Qiwa contract stay consistent. Saudi and non Saudi headcount can be read per company and branch, which is the figure Nitaqat and the Qiwa Saudization count depend on, and employee data access follows the PDPL with sensitive fields restricted by role. Payroll runs in Odoo Payroll or syncs with Jisr and ZenHR through the connections on the integrations page.
Document expiry before it costs you
Iqama, passport, license and health card dates sit on the employee record with alerts ahead of each deadline. HR renews on time instead of discovering an expired iqama at a government service counter.
Saudization view per CR
Headcount by nationality is reported per company and branch, so management sees the Nitaqat position of each commercial registration before hiring decisions, not after a band change.
Payroll inside or outside
Run Odoo Payroll on the same record, or keep Jisr or ZenHR and sync employees and journal entries into Odoo. Either way there is one employee ID across attendance, expenses and the ledger.
1. Record created
The applicant is converted from Recruitment or a record is created by HR with Arabic and English names, nationality, department and branch.
2. Contract and documents attached
The contract template for Saudi or non Saudi staff is applied with salary, probation and notice terms, and iqama, passport and health card copies are uploaded with expiry dates for the Qiwa and GOSI registrations.
3. Leave and attendance assigned
The leave allocation for the contract and the attendance source for the branch, biometric device, kiosk or app, are linked to the record.
4. Payroll inputs flow
Contract salary, allowances and attendance reach Odoo Payroll, or are exported to Jisr or ZenHR, so the first payslip is right without re-entry.
Timelines depend on headcount, number of entities and the state of current files, and Naqlah gives you a clear roadmap in the first consultation.
| Area | Before | With Odoo via Naqlah |
|---|---|---|
| Employee files | Paper folders and an Excel master list | One record with documents, contract and history |
| Document expiry | Calendar reminders set by one person | Automated alerts per document and deadline |
| Contracts | Word templates edited by hand | Templates with Saudi probation, notice and term rules |
| Attendance | Device export emailed to payroll | Synced to the employee record daily |
| Saudization | Manual count before a Qiwa check | Headcount by nationality per CR and branch |
| Payroll inputs | Re-keyed into the payroll system | Flow automatically to Odoo Payroll or Jisr |
Everything else, we cover in a free 30-minute consultation.
Free consultation. Meet the team and get a clear roadmap in one call.