Saudi enterprises running expatriate workforces carry a compliance burden that ERPNext core was never designed to hold. Iqama expiries, Qiwa labour contracts, Nitaqat colour bands and Muqeem visa records live in government portals, while your HR team re-keys the same dates into ERPNext Employee records by hand — or worse, into a side spreadsheet. Stock ERPNext gives you an Employee DocType with a handful of ID fields and no scheduled awareness of an expiring Iqama, no concept of a Saudization ratio, and no bridge to Qiwa or Muqeem. The result is missed renewals, GOSI/MOL exposure, and a workforce master that nobody fully trusts.

ECOSIRE builds Saudi Qiwa & Muqeem HR Sync as a proper Frappe application — a versioned app installed on your own bench, not a settings tweak. We add custom DocTypes such as Qiwa Contract, Iqama Record, Saudization Snapshot and Portal Sync Log, plus custom fields on the standard Employee DocType so the government identifiers become first-class, permissioned data. A whitelisted integration layer authenticates against the Qiwa and Muqeem endpoints (or an authorised intermediary, per your access agreement), maps their payloads to your records, and writes back through the Frappe ORM so every change respects your role profiles and audit trail. hooks.py scheduler events poll for status changes on a cadence you choose; document events on Employee keep the single authoritative master in step, cascading updated identity data to payroll, HR and any downstream integrations.

Operationally, the app turns raw portal data into action. A Nitaqat tracker computes your Saudization ratio in real time and renders the platinum/green/yellow/red band with threshold alerts before you slip. Muqeem monitoring watches Iqama, passport and visa expiry windows and fires staged reminders — 90/60/30/7 days — via ERPNext Notifications, email and (optionally) a ToDo assignment to the responsible GR officer. Every sync writes a Portal Sync Log entry so you can prove exactly when a status was last verified. Client scripts surface band colours and expiry countdowns directly on the Employee form; server scripts and controller validations stop stale or conflicting government data from being saved silently.

Because this is build-to-order, you are not downloading a generic marketplace app and hoping it fits. We start with a short scoping call to confirm your portal-access model, the exact fields and cadences you need, your role/permission structure, and whether you are on Frappe/ERPNext v15 or v16. We then build against a staging copy of your instance, run UAT with your HR team, and hand over installable source and a git repository you own. Typical delivery is one working week from confirmed scope, with a post-go-live support window included.