Running Nigerian payroll on stock ERPNext means fighting the Payroll module every month. ERPNext ships generic Salary Structures and Income Tax Slabs, but it has no built-in understanding of the Personal Income Tax Act: the Consolidated Relief Allowance (the higher of NGN 200,000 or 1% of gross income, plus 20% of gross income), the graduated PAYE bands, statutory pension splits under the Pension Reform Act, NHF at 2.5% of basic, and NSITF employer contributions. Finance teams end up maintaining fragile spreadsheets alongside ERPNext, re-keying figures into pension administrator and bank templates, and hoping the numbers reconcile at year end. That is where the native system runs out of road.

ECOSIRE builds a proper Frappe app — for example ecosire_ng_payroll — installed on your own ERPNext instance rather than bolted on as spreadsheets. The app adds custom DocTypes for statutory configuration (PAYE bands, CRA parameters, pension, NHF and NSITF rates, each effective-dated so historical runs stay correct) and wires the computation into ERPNext's existing Salary Slip and Payroll Entry flow. Statutory components are implemented as Salary Component formulas backed by server-side logic, so gross-to-net follows the legal order of operations: compute gross, derive CRA, subtract tax-exempt pension and NHF, apply the PAYE bands to taxable income, then net down. Employer-side pension and NSITF are tracked separately so they never leak into the employee's net pay.

Technically, the calculation logic lives in whitelisted Python methods invoked from hooks.py doc events (Salary Slip validate and on_submit) so the numbers recompute deterministically every run and cannot be silently edited in the UI. A State field (custom field on Employee) drives the correct state Internal Revenue Service treatment where it differs. Client scripts surface a live PAYE/pension/NHF breakdown on the Salary Slip form for reviewers. Scheduler events can queue the monthly Payroll Entry and email statutory summaries to the finance lead. Everything respects Frappe's permission model — a dedicated Payroll Officer role profile gates access to statutory config and bank schedules, and the whitelisted export methods are permission-checked, not open endpoints.

Disbursement is a first-class output, not an afterthought. The app generates a bank schedule export (CSV or the fixed-width/columnar layout your bank expects — GTBank, Zenith, Access, UBA and similar) directly from the submitted Payroll Entry, plus a PENCOM-style pension schedule and PAYE remittance summary. Reports are exposed via the Frappe REST API and whitelisted methods so a portal or downstream automation can pull them, and every figure ties back to the source Salary Slip for audit.

Because this is build-to-order, nothing is a generic download. After a short scoping call we confirm your exact requirements — states you operate in, pension administrators, allowance structure, bank formats and any collective-agreement rules — then build against ERPNext v15 or v16 to match your instance. You review the working app on a staging site during UAT, we install to production with a rollback plan, hand over the git repository and documentation, and support you through your first live payroll runs. Typical delivery is 2–4 weeks from confirmed scope.