Saudi Qiwa & Muqeem HR Sync

Key Features

Custom `Qiwa Contract` DocType storing labour-contract number, status, occupation and authentication state, linked one-to-one to the ERPNext `Employee`

Whitelisted Frappe methods (`@frappe.whitelist()`) that authenticate to Qiwa and map contract-authentication responses to `Employee` records

Real-time Nitaqat / Saudization tracker computing the Saudi-to-total ratio per entity and rendering the platinum/green/yellow/red colour band

Threshold alerts that fire when the Saudization band is about to downgrade, so hiring/renewal decisions happen before the drop

Muqeem Iqama-expiry monitoring with a scheduled job scanning expiry windows and raising staged reminders at 90/60/30/7 days

Passport and visa (exit/re-entry) renewal tracking with the same staged-reminder pipeline as Iqama

`hooks.py` `scheduler_events` (daily/hourly) driving portal polls and reminder generation without manual triggers

`Employee` document events (`validate`, `on_update`) that keep the single authoritative master consistent and cascade identity changes downstream

`Portal Sync Log` DocType recording every sync attempt, source portal, payload hash, result and timestamp for audit and dispute defence

Role profiles and DocType-level permissions so GR officers, HR managers and payroll see only the government data appropriate to them

Client scripts on the Employee form showing live expiry countdowns and Saudization band colour without leaving the record

Notification + ToDo assignment routing so each expiring document lands on the responsible officer, not a shared inbox

Idempotent sync with reconciliation rules that flag conflicts between portal data and ERPNext instead of overwriting silently

Built and tested for Frappe/ERPNext v15 and v16, delivered as a versioned bench app with clean migration hooks

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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 2-4 weeks from confirmed scope, with a post-go-live support window included.

What you get

Installable source code for your version of the Saudi Qiwa & Muqeem HR Sync app (Frappe app, not an obfuscated blob)

Installation and configuration on your bench, including scheduler, role profiles and portal-access wiring

Technical documentation: DocType reference, hooks/scheduler map, API/whitelisted-method contract and configuration guide

End-user guide plus a live training session for your HR and GR team

UAT on a staging copy of your ERPNext instance with a documented rollback plan before production cutover

Post-go-live support window for defect fixes and questions after launch

Handover of the private git repository containing the full source and commit history

Migration/upgrade notes covering Frappe/ERPNext v15-to-v16 compatibility

Who this is for

HR Compliance Manager (KSA enterprise)

Owns MOL/Qiwa and Muqeem compliance for a large expatriate workforce and needs Iqama, contract and Saudization status visible and enforced inside ERPNext instead of tracked across portals and spreadsheets.

Government Relations (GR) / Mandoob Officer

Handles Iqama, visa and passport renewals day to day and wants staged, assigned reminders and a verified last-synced record so nothing lapses and every renewal is auditable.

ERPNext / Frappe System Administrator

Maintains the bench and needs a clean, versioned app with sensible hooks, permissions and migrations for v15/v16 — plus source and a git repo they control rather than a black-box marketplace install.

HR Director / Head of People Operations

Wants a single authoritative employee master with a live Nitaqat band and early-warning alerts to protect the company's Saudization standing and avoid GOSI/MOL penalties.

How Saudi Qiwa & Muqeem HR Sync Compares

Criterion	ECOSIRE	Custom Build	Competitor
Qiwa/Muqeem integration	Purpose-built whitelisted sync mapped to your records	You design and maintain the API layer yourself	Rarely available; Saudi portals are niche
Nitaqat / Saudization tracking	Real-time ratio with colour-band threshold alerts	Build the calculation and alerting from scratch	Generic HR metrics, not Saudi Nitaqat bands
Iqama/visa expiry reminders	Staged 90/60/30/7-day scheduled reminders + ToDo routing	Depends on in-house scheduler work	Basic date reminders if any
Fit to your process	Scoped to your fields, roles and cadences	Fully bespoke but you own all the effort	Fixed feature set, take it or leave it
Source & ownership	Installable source + your own git repo handover	You own it, and all the build risk	Often closed-source / licence-locked
Delivery time	Typically 2-4 weeks from confirmed scope	Unpredictable; scoping-to-ship is on you	Instant install but poor Saudi fit
Audit & compliance trail	Portal Sync Log + permissions + UAT on staging	Only if you build and test it	Limited logging, no Saudi context
Support & upgrades	Included go-live window + optional retainer, v15/v16	Your team maintains it indefinitely	Vendor SLA, limited Saudi expertise

Frequently Asked Questions about Saudi Qiwa & Muqeem HR Sync

Is this an existing app I can download and install today?

No. This is a build-to-order Frappe app. ECOSIRE scopes it to your portal-access model, fields and permissions, then builds, installs and supports it on your bench. You receive installable source and your own git repository — not an instant marketplace download.

How long does delivery take?

Typically 2-4 weeks from confirmed scope. The timeline starts once we agree the DocType/field set, sync cadences, role permissions and your portal-access arrangement on the scoping call. Larger or multi-entity Saudization setups may extend this, and we confirm the estimate in writing before work begins.

How does it connect to Qiwa and Muqeem?

Through a whitelisted Frappe integration layer that authenticates to the Qiwa and Muqeem endpoints (or an authorised intermediary, depending on your access agreement) and maps their responses onto ERPNext records via the ORM. Government portal access must be provided or arranged by your organisation; we build the integration around whatever authorised access you hold.

Which Frappe/ERPNext versions are supported?

We build and test against Frappe/ERPNext v15 and v16. We confirm your exact version on the scoping call and deliver the app with clean migration hooks so it upgrades with your bench.

What about support and updates after go-live?

A post-go-live support window is included for defect fixes and questions. Beyond that, because you own the source and git repository, you can extend it yourself or engage ECOSIRE on a support/retainer basis for portal-schema changes, new alert rules or version upgrades.

Will it interfere with our existing HR and payroll data?

No. It treats the ERPNext `Employee` as the single authoritative master and writes through the Frappe ORM with your permissions and audit trail intact. Syncs are logged and conflicts are flagged for review rather than overwriting your records silently. We validate all of this during UAT on staging before production.

Do you handle data residency and permissions?

Yes. Government identity data is scoped with DocType-level permissions and role profiles so only authorised HR/GR staff can see it, and every sync is recorded in an audit log. The app runs on your own infrastructure, so data residency follows your ERPNext hosting.