Qiwa ↔ Odoo Integration

Qiwa is the system of record the Saudi government trusts; Odoo is the system the business runs on. Between them sat spreadsheets, copy-paste, and a growing drift between what the government believed and what the company knew. Contract changes, transfers, and terminations had to be recorded twice — and sometimes they weren't, which is a compliance problem, not just an inconvenience.

An integration layer maps Qiwa's HR constructs to Odoo's employee and contract models, with a deterministic sync engine that detects creates, updates, and deletions on both sides. A reconciliation job continuously diffs the two systems and flags divergence before it becomes a compliance issue. Every sync event is logged with before/after state so any record can be traced to its source decision.

Qiwa's API model doesn't map 1:1 onto Odoo's, so the mapping layer makes explicit, documented decisions about what wins when definitions differ — and government definitions always win. Full real-time sync was rejected in favor of scheduled, idempotent batches: HR data changes slowly enough that batch correctness beats live fragility, and idempotency makes retries safe.

4,000+ employees stay synchronized between Qiwa and Odoo without manual reconciliation. Contract and employee-record drift became a monitored, self-healing condition instead of a quarterly fire drill, and compliance reporting pulls from one consistent dataset.