Muqeem ↔ Odoo Integration

Residency and visa status lived in Muqeem while everything else about an employee lived in Odoo. HR teams switched between portals to answer basic questions — is this employee's iqama valid? — and expired documents were discovered late, sometimes after penalties. Legal status was the one piece of employee data the company couldn't see in its own system.

The integration pulls Muqeem residency data into Odoo's employee records on a disciplined schedule, attaching iqama validity, expiry dates, and status flags directly to the canonical employee profile. Expiry-driven alerting turns the data into action: thresholds trigger notifications to HR and the employee long before documents lapse. The sync engine shares its idempotent, auditable core with the Qiwa integration.

Muqeem data is authoritative but not real-time, so the design embraces eventual consistency with clear freshness indicators rather than pretending to be live. Expiry alerting required careful threshold tuning — too early and people ignore the noise, too late and it stops being a warning. The same scheduled-batch philosophy as the Qiwa integration keeps operational cost low.

4,000+ employees' residency status is now visible inside Odoo, where HR actually works. Expired-document surprises dropped to near zero thanks to proactive expiry alerts, and the company always knows its compliance posture at a glance.