Pakistani SMEs running ERPNext hit a wall the moment they process a real monthly payroll. ERPNext core ships a generic Salary Structure and Income Tax Slab engine, but it has no concept of the FBR annual tax slabs for salaried individuals, no EOBI employer/employee contribution logic tied to the minimum-wage ceiling, and no handling for the provincial social-security schemes (PESSI in Punjab, SESSI in Sindh, and their KP/Balochistan equivalents). Teams end up maintaining tax and contribution math in parallel spreadsheets, then keying numbers back into Salary Slip records by hand — which is slow, error-prone, and falls apart at year-end when FBR revises the slabs.

ECOSIRE builds a proper Frappe app (a versioned app with its own module, DocTypes, and hooks.py) installed onto your ERPNext bench rather than a pile of ad-hoc customizations. We add configuration DocTypes for the current FBR Income Tax Slab set, EOBI parameters, and per-province PESSI/SESSI rates, so the compliance rules live in data you can update — not in code you have to redeploy. Salary components for income tax, EOBI (employee and employer share), and provincial social security are wired into your Salary Structure, and their amounts are computed from these config DocTypes at slip generation.

Technically, the deduction math runs through server-side logic bound to Frappe doc events — a Salary Slip validate/on_submit hook recomputes the FBR slab tax on annualized taxable income, applies the EOBI contribution against the correct wage ceiling, and adds the applicable provincial contribution based on the employee's work location. Whitelisted methods exposed over the Frappe REST API let your bank-file export and reports run programmatically or from a scheduled job; a scheduler event can prepare the monthly statutory summary. Client scripts add the in-form helpers HR needs (live recalculation, validation prompts), and role profiles plus DocType permissions keep tax configuration and disbursement files restricted to the right HR and Finance roles.

Because this is a scheme with statutory numbers and edge cases specific to your headcount and provinces, it is build-to-order: nothing to instantly download. After a short scoping call we confirm exactly which provinces, slabs, and salary components apply to you, then build against a copy of your ERPNext configuration. Typical delivery is one working week from confirmed scope. You get the installable app source for your version, deployment onto staging for UAT, a rollback plan, and a defined post-go-live support window — all validated on Frappe/ERPNext v15/v16 before it touches production.