Saudi payroll teams running ERPNext hit the same wall every month: ERPNext core Payroll handles gross-to-net salary structures, but it has no concept of GOSI's dual contribution regime, no Mudad-formatted WPS output, and no end-of-service benefit engine tied to Saudi labour law. Teams end up exporting Salary Slips to spreadsheets, hand-calculating employer and employee GOSI split by nationality, then re-keying a WPS file into a bank portal — a process that breaks the moment GOSI changes a rate or an auditor asks how a number was derived. When the July contribution rate adjustments land, the spreadsheet logic silently goes stale.

ECOSIRE builds a proper Frappe app that closes that gap inside ERPNext rather than beside it. The GOSI dual-rate engine is a set of DocTypes plus hooks.py doc events on Salary Slip: on validate, a server script resolves the employee's nationality (Saudi vs non-Saudi), applies the correct employee and employer contribution percentages against the capped contributory wage, and adds the occupational-hazard component — writing the results back as dedicated salary components so they flow into Payroll Entry and the GL without manual entry. Rate tables are stored as versioned DocTypes with effective-from dates, so the mandated July rate update is a data change with a scheduled event flag, not a code redeploy — and every calculation is reproducible and auditable.

Mudad WPS submission is handled by a whitelisted method that assembles the bank file from the posted Payroll Entry, runs pre-submission compliance checks (IBAN presence and format, GOSI-registered wage vs paid wage variance, missing establishment/employee identifiers), and blocks generation with a clear error list before you ever touch the portal. End-of-service benefit is a separate calculator DocType that applies the Saudi labour-law tiers (first five years vs beyond, resignation vs termination proration) against the qualifying wage, and a GOSI monthly reconciliation report reconciles what ERPNext posted against what was declared, flagging deltas per employee. Role profiles and permissions keep the WPS-generation and rate-maintenance surfaces restricted to payroll administrators.

Because this is build-to-order, you are not downloading a fixed marketplace app and hoping it fits. We start with a short scoping call to confirm your establishment structure, salary-component mapping, bank/Mudad setup, and Frappe/ERPNext version (v15 or v16). We then build your version against that scope, validate it on a staging copy of your data through UAT, and install it on your instance with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. You receive the installable source, a git repository handover, documentation, a training session, and a post-go-live support window.