Jisr HR Integration with Odoo
Bidirectional sync between Jisr — Saudi Arabia's Labour Law HR platform — and Odoo ERP. Employee records, leave approvals, attendance data, and payroll inputs move between both systems automatically, so your HR team works in Jisr and your finance team works in Odoo without duplicate data entry.
Key Highlights
Core Features
- Employee Master Data Sync
- Leave Approval → Odoo Leaves
- Attendance Data for Odoo Payroll
- GOSI and End-of-Service Inputs
Your HR Team Stays in Jisr. Your Finance Team Stays in Odoo. Both See the Same Data.
Saudi SMEs running Jisr for HR and Odoo for ERP and accounting face a familiar overhead: HR staff enter employee records, leave approvals, and attendance data in Jisr, then re-enter the same data in Odoo for payroll processing and accounting. Finance exports payroll outputs from Odoo and re-uploads them to Jisr to complete HR records. The reconciliation happens manually each month — a two-system workflow that introduces discrepancies and consumes HR and finance time on data entry rather than on analysis.
The Jisr–Odoo integration creates a bidirectional data bridge between the two platforms. Jisr sends employee master data, leave approvals, attendance records, and GOSI contribution inputs to Odoo HR and Payroll automatically. Odoo sends payroll outputs, salary disbursement records, and employee contract data back to Jisr. The Odoo modules involved are HR, Payroll, Attendance, and Leaves — each receiving data from Jisr without manual input and sending its outputs back to Jisr without export. Both systems remain in sync with each other continuously.
Jisr is built specifically for Saudi Labour Law — Muqeem integration, Iqama tracking, GOSI contribution management, end-of-service benefit calculations under Article 84 of the Saudi Labour Code, and Saudisation (Nitaqat) reporting. This Saudi-native compliance depth makes Jisr the HR platform of choice for many Saudi SMEs, particularly those with mixed Saudi–expat workforces. The Jisr–Odoo integration means companies do not have to choose between Jisr's Saudi HR compliance and Odoo's ERP depth: both systems stay in sync.
A Riyadh-based contracting company with 180 employees uses Jisr for all HR administration — onboarding, Iqama tracking, leave management, GOSI, and end-of-service — and Odoo for project costing, accounting, and subcontractor management. Before the integration, HR emailed a monthly attendance and leave summary to finance, who manually entered it into Odoo Payroll. After iWesabe deployed the Jisr–Odoo connector, leave approvals in Jisr now trigger Odoo Leaves records automatically; Jisr attendance data flows into Odoo Payroll before each monthly run; and Odoo payroll outputs feed back into Jisr's salary records. The monthly HR–finance handoff was eliminated.
What the Jisr–Odoo Connector Delivers
Employee Master Data Sync
Employee records created or updated in Jisr — Arabic and English names, Iqama number, nationality, job title, cost centre, and contract type — sync to Odoo HR automatically. New hires added in Jisr are provisioned in Odoo without a separate Odoo HR entry; terminations in Jisr trigger the Odoo HR archiving workflow.
Leave Approval → Odoo Leaves
Leave requests approved in Jisr post to Odoo Leaves in real time. Annual leave, sick leave, Hajj leave, maternity leave, and emergency leave types are mapped between the two systems. Odoo Payroll reads approved leave records directly, so leave deductions and balances are accurate in every payroll run without manual entry.
Attendance Data for Odoo Payroll
Attendance records from Jisr — working days, absent days, overtime hours — sync to Odoo Payroll before each monthly pay run. Overtime is calculated against Saudi Labour Law limits in Odoo, and GOSI working-day counts are drawn from Jisr-sourced attendance data.
GOSI and End-of-Service Inputs
Jisr's Saudi Labour Law calculations for GOSI contributions and end-of-service benefit accruals under Article 84 are available as inputs to Odoo Payroll. GOSI contribution data flows from Jisr to Odoo for the payroll run; end-of-service liability accruals post to Odoo Accounting as journal entries.
Payroll Output Written Back to Jisr
After the Odoo Payroll batch runs, net salary, deductions, and allowances are written back to Jisr employee records automatically. Finance works entirely in Odoo; HR sees the completed payroll data in Jisr without waiting for a manual update or a spreadsheet export.
Multi-Company and Nitaqat Reporting
For Saudi holding groups running multiple entities, each Odoo company syncs with its corresponding Jisr account. Jisr's Saudisation (Nitaqat) category and reporting data are included in the sync, giving finance access to workforce composition data in Odoo for cost-centre analysis.
Saudi Compliance Built Into Every Sync
- Saudi Labour Law leave types — Hajj leave, maternity leave, sick leave, emergency leave, and annual leave with Saudi accrual rules — mapped between Jisr and Odoo Leaves. Every leave type Jisr recognises under Saudi law is available in Odoo with the same entitlement rules.
- GOSI contribution data sourced from Jisr's Saudi-native GOSI engine, not from manual Odoo entry. Monthly contribution amounts for Saudi nationals and expats are calculated by Jisr using current Ministry of Human Resources rates and passed to Odoo Payroll for disbursement.
- End-of-service benefit calculations under Article 84 of the Saudi Labour Code flow from Jisr into Odoo Accounting as monthly accrual journal entries — keeping the company's end-of-service liability accurate on Odoo's balance sheet throughout the employee lifecycle.
- Iqama expiry and Muqeem data tracked in Jisr — when Iqama expiry dates approach, HR alerts fire in Jisr; Odoo sees the current Iqama status through the HR record sync, so payroll runs do not process records with expired documentation unknowingly.
- Saudisation (Nitaqat) category data from Jisr syncs to Odoo HR — allowing cost-centre managers and finance to analyse workforce composition and Nitaqat compliance from within Odoo reports without switching to Jisr's dashboard.
Supported Markets
Saudi Arabia
SAR • ZATCA compliant
United Arab Emirates
AED
Bahrain
BHD
+ Kuwait, Oman, Qatar & more
Business Outcomes After Go-Live
Monthly HR–Finance Handoff Eliminated
Leave data, attendance records, and payroll inputs no longer travel via email or spreadsheet between HR and finance. Both teams see the same data in their respective systems at all times.
Payroll Accuracy Improves Immediately
Odoo Payroll reads leave and attendance data directly from Jisr records. Manual re-entry errors — the most common source of payroll discrepancies in dual-system environments — are removed from the process.
GOSI Submissions Based on Verified Data
GOSI contribution amounts derive from Jisr's Saudi-native GOSI engine, not from manually entered Odoo figures. Discrepancy risk in monthly GOSI submissions drops significantly.
End-of-Service Liability on the Balance Sheet
Article 84 end-of-service accruals from Jisr post to Odoo Accounting automatically. The liability is visible on the balance sheet throughout the year — not discovered as a surprise at termination.
HR Stays in Jisr, Finance Stays in Odoo
Neither team is asked to change their primary system. HR continues using Jisr's Saudi-native workflows; finance continues running Odoo for accounting, cost centres, and reporting. The integration is invisible once deployed.
Onboarding and Offboarding in One Step
A new hire added in Jisr provisions automatically in Odoo HR. An employee archived in Jisr triggers the Odoo offboarding workflow — including payroll cut-off and end-of-service payout calculation — without a separate Odoo HR entry.
Implementation Steps
Prerequisite check — confirm Jisr API access credentials, verify Odoo HR, Payroll, Attendance, and Leaves modules are active, and document the field mapping between Jisr's employee schema and Odoo HR fields
Install the Jisr–Odoo connector module in Odoo and configure the Jisr API endpoint, authentication token, and sync interval (real-time or scheduled daily batch)
Configure employee field mapping — Arabic name, Iqama number, nationality, cost centre, leave types, and GOSI contribution category — between Jisr and Odoo HR
Run initial data sync — import existing Jisr employee records into Odoo HR, validate record matching, and resolve any duplicate or unmatched employee IDs
Test leave and attendance sync — approve a leave request in Jisr, confirm it appears in Odoo Leaves; run a test payroll with Jisr attendance data and verify GOSI totals
Go-live — run the first full monthly payroll cycle with Jisr-sourced data; iWesabe confirms GOSI contribution amounts, end-of-service accruals, and payroll outputs before sign-off
Saudi Industries Using Jisr and Odoo Together
Why iWesabe for the Jisr–Odoo Integration
Years Experience
Since 2012
Odoo Gold Partner
Certified by Odoo SA
Implementations
Across KSA & GCC
Delivery Locations
KSA · UAE · Bahrain · India
- Odoo Gold Partner with deep experience in Saudi HR and Payroll configuration — GOSI, WPS, end-of-service, Hajj leave, and Saudi Labour Law overtime are part of every iWesabe Odoo HR deployment
- Jisr implementation experience on the Saudi client base — iWesabe understands Jisr's data model, API behaviour, and Saudi Labour Law field mappings at the connector level, not just the surface integration
- Bilingual deployment — all Odoo HR, Payroll, and Leaves configuration delivered in Arabic and English for Saudi workforces with mixed-language HR administration
- Post-go-live payroll support for the first three cycles — iWesabe reviews GOSI totals, end-of-service accruals, and Jisr–Odoo data consistency before sign-off
iWesabe has deployed the Jisr–Odoo integration for Saudi contractors, healthcare groups, and retail operators. Every deployment includes end-of-service liability configuration in Odoo Accounting, GOSI payroll verification, and a 30-day post-launch review before handover.
Jisr–Odoo Questions Answered
The integration syncs employee master records (Arabic and English names, Iqama, nationality, cost centre, contract type), leave requests and approvals (all Saudi Labour Law leave types), attendance records (working days, absences, overtime), GOSI contribution inputs, end-of-service benefit accruals, and payroll outputs. The exact field set is configured during implementation to match your Jisr and Odoo setup.
The integration supports Odoo 16, 17, and 18, both Community and Enterprise editions. Odoo HR, Payroll, Attendance, and Leaves modules must be active. Certain features — multi-company setup, advanced payroll customisation, and detailed GOSI reporting — are available on Odoo Enterprise.
Yes, the sync is bidirectional. Jisr-to-Odoo events (new employee, leave approval, attendance data) are pushed in near real-time via Jisr webhooks or pulled on a scheduled interval. Odoo-to-Jisr payroll outputs are written back after the Odoo payroll batch run. The sync direction and trigger method are configured during implementation.
Jisr's Saudi-native leave types — annual leave, sick leave, Hajj leave, maternity leave, and emergency leave — are mapped to corresponding Odoo Leaves types during configuration. Leave accrual rules, entitlement days, and carry-over policies follow Saudi Labour Law defaults as configured in Jisr, and are respected in Odoo Leaves automatically.
GOSI monthly contribution amounts are calculated by Jisr using Saudi Ministry of Human Resources rates and passed to Odoo Payroll as contribution inputs. End-of-service benefit accruals under Article 84 of the Saudi Labour Code are calculated by Jisr and posted to Odoo Accounting as monthly journal entries — keeping the end-of-service liability on the Odoo balance sheet throughout the employee lifecycle.
A configurable conflict resolution rule determines which system is the master for each field. Typically, Jisr is the master for HR and leave data; Odoo is the master for payroll outputs and accounting entries. Fields modified in the non-master system are overwritten on the next sync cycle. iWesabe documents the conflict resolution rules during implementation so both HR and finance teams understand the data ownership model.
A standard deployment for a company with one Jisr account and one Odoo company takes 3–5 working days with iWesabe. Larger deployments involving multi-company Odoo setups or complex payroll structures typically take 2–3 weeks. iWesabe runs the first full payroll cycle jointly with the client's HR and finance teams before handover.
Explore More Solutions
Discover our full suite of industry-leading ERP tools built for every business sector.
Salla Integration for Odoo
Connect your Salla store to Odoo so every online order, customer, and stock movement flows straight into your back office. Orders become Odoo sales orders with ZATCA-aligned invoices, inventory syncs both ways to stop overselling, and fulfilment status flows back to Salla — one operation across storefront and ERP, with no manual re-entry.
ExploreFoodics Integration for Odoo
Connect your Foodics POS to Odoo so every sale, inventory movement, and payment posts to your accounts automatically. Daily F&B sales become ZATCA-aligned Odoo journals, recipe-based stock consumption flows to Odoo Inventory, and menu and pricing sync back to Foodics — giving you real-time food cost and profitability without a single manual journal entry.
ExploreQuickBooks Integration for Odoo
Keep QuickBooks and Odoo in step so your accounting data moves between them without re-entry. Customers, invoices, bills, payments, tax codes, and journal entries sync both ways — and Odoo adds ZATCA Phase-2 e-invoicing, inventory, and operations around the books you already keep, with one consistent set of figures across both systems.
ExploreTally Integration for Odoo
Keep Tally and Odoo on one consistent set of figures. Ledgers, vouchers, stock items, parties, and tax data sync both ways — and Odoo adds ZATCA Phase-2 e-invoicing, Arabic invoices, and the inventory and operations layer around the books your accountants already keep in Tally.
ExploreSalesforce Integration for Odoo
Keep Salesforce as your CRM and Odoo as the system that delivers, invoices, and reports. Leads, accounts, opportunities, products, and quotes sync both ways — and a won deal in Salesforce becomes a sales order in Odoo automatically, with delivery and payment status flowing back to the deal so sales and operations work from the same record.
ExploreZendesk Integration for Odoo
Keep Zendesk as your support desk and Odoo as the system of record. Tickets, contacts, organisations, and SLA timers sync both ways — agents see the customer's orders, invoices, and balance inside Zendesk without leaving, and Odoo users see open ticket status without leaving Odoo.
ExploreReady to Sync Jisr With Your Odoo Payroll?
Talk to iWesabe about connecting Jisr to Odoo HR, Payroll, Attendance, and Leaves — with Saudi Labour Law, GOSI, and end-of-service liability configured from the start.
