Egyptian businesses running ERPNext hit a wall the moment they try to run a compliant local payroll. ERPNext core ships a flexible Salary Structure and Salary Slip engine, but it knows nothing about Egypt's progressive personal income-tax brackets, the annual exemption, or the split of social-insurance contributions between employer and employee against a capped insurable wage. Teams end up maintaining fragile spreadsheets alongside ERPNext, hand-keying tax and insurance deductions, and reconciling figures that never quite match what the tax authority and the National Organization for Social Insurance expect. Arabic payslips and the reporting layouts local authorities ask for are simply not there out of the box.

ECOSIRE builds a proper Frappe app — installed on your own ERPNext instance — that encodes Egyptian payroll rules as first-class, configurable data rather than hard-coded logic. We ship configuration DocTypes for the income-tax brackets (with effective-dated versions so a bracket change is a data edit, not a redeploy), the annual personal exemption, and the social-insurance parameters (contribution rates, minimum and maximum insurable wage, employer vs. employee shares). Payroll calculation is driven by hooks.py document events and server-side methods hung off the standard Salary Slip: when a slip is validated, our code resolves the correct effective-dated brackets, computes the progressive tax on annualized taxable pay, derives the social-insurance base against the capped wage, and writes clean, auditable earning and deduction components back onto the slip. Because it plugs into the native Salary Structure Assignment and Payroll Entry flow, your existing ERPNext HR processes, leave, and attendance keep working unchanged.

On top of the calculation core we build the compliance and end-user layer. End-of-service settlement is computed from configurable service-length rules and final wage, exposed as its own DocType and report. Arabic payslip templates are delivered as Print Formats with correct RTL layout and Arabic component labels, so employees receive a bilingual slip. Tax-authority and social-insurance reporting formats are produced as Query/Script Reports and exportable files matching the layouts your accountants file. Everything is permission-scoped: a dedicated Payroll Officer role profile and DocType permissions keep salary data out of general users' hands, and sensitive figures are gated behind Frappe's role and field-level permissions. Where you need to feed data to another system, the relevant methods are exposed as whitelisted endpoints over the Frappe REST API, and scheduled recalculations or period-close checks run as scheduler events.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call to confirm your company structure, which salary components you run, whether you need multi-company or multi-branch handling, and the exact tax and social-insurance parameters in force for your filing. We then build against Frappe/ERPNext v15 or v16 to match your instance, deliver on a staging environment for UAT, and only promote to production once you sign off. Typical delivery is one working week from confirmed scope. You receive the full source in a Git repository, install and configuration documentation, and a post-go-live support window so the first live payroll run is covered.