Groups running staff across two or more GCC countries hit the same wall in ERPNext: standard HR & Payroll handles Salary Structures, Salary Slips and Payroll Entry well, but it has no concept of a country's Wage Protection System file, a KSA GOSI contribution split, or the divergent end-of-service gratuity math that UAE, Qatar, Oman, Bahrain and Kuwait each define differently. Teams end up running one ERPNext company per country with copy-pasted Salary Components, exporting to spreadsheets to build WPS/SIF banking files by hand, and reconciling six sets of statutory rules every month. A single wrong field in a fixed-width WPS file gets the whole batch rejected by the bank, and a miscalculated gratuity accrual becomes a real liability at settlement.

The GCC Multi-Country Payroll Suite is a proper Frappe app — its own module, DocTypes, hooks.py, fixtures and role profiles — that layers a jurisdiction engine on top of ERPNext's native payroll rather than replacing it. A GCC Country Profile DocType holds each state's rule set: the WPS/SIF file format and field map, employer/employee social-insurance rates (GOSI in KSA, GPSSA/pension in the UAE, PIFSS in Kuwait, PASI in Oman, and so on), gratuity accrual bands, and rounding. Adding or amending a country becomes configuration, not a code change. Each legal entity is tagged with its country profile, so the same instance can process a KSA company and a UAE company from one Payroll Entry run without cross-contamination of rules.

Technically, the suite hooks ERPNext's payroll lifecycle with doc_events on Salary Slip and Payroll Entry: server-side controllers compute the correct social-insurance and gratuity lines against the entity's profile and write them back as Salary Components, so the native Salary Slip stays the source of truth and existing reports keep working. A WPS File Generation DocType produces the country-specific bank file (fixed-width SIF for the UAE, the KSA WPS layout, Qatar/Bahrain/Oman/Kuwait variants) with validation that catches malformed IBANs, establishment IDs and totals before you ever hand the file to a bank. Whitelisted methods exposed over the Frappe REST API let an outsourced provider trigger generation and pull status programmatically; scheduler events (scheduler_events in hooks.py) post monthly gratuity accruals and flag employees approaching a statutory threshold. Client Scripts add country-aware UI on the Salary Structure and Employee forms, and everything is gated behind dedicated roles and permission profiles so a payroll clerk for one country cannot see another's data. It targets Frappe/ERPNext v15 and v16.

Because this is build-to-order, we do not hand you a generic download. ECOSIRE starts with a scoping call to confirm exactly which of the six countries you run, your bank/WPS agent formats, your entity structure and any local variations, then builds and configures the suite against your ERPNext instance. Typical delivery is one working week from confirmed scope. You get the version we built for you as installable source in a git repository, UAT on a staging site with a documented rollback plan, and a post-go-live support window — no fabricated benchmarks, just a working payroll engine tuned to your actual jurisdictions.