Philippine BPOs and SMEs standardizing on ERPNext hit the same wall every payroll cycle: ERPNext core Payroll gives you Salary Structures, Salary Components and Payroll Entry, but it has no concept of the mandatory Philippine statutory deductions. SSS contribution brackets, the PhilHealth premium formula, Pag-IBIG (HDMF) contributions and BIR graduated withholding tax all end up hand-maintained in spreadsheets or hard-coded into brittle formula components that break the moment a circular changes a bracket. Finance teams then reconcile by hand and rebuild the BIR alphalist and 1601C every filing period. That is slow, error-prone, and does not survive an audit.

We build a proper Frappe app — for example ecosire_ph_payroll — installed on your own bench as a versioned module, not a pile of manual Salary Components. The statutory tables live in dedicated DocTypes (SSS Contribution Table, PhilHealth Bracket, Pag-IBIG Setting, BIR Withholding Tax Table) so effective-dated brackets are data you can edit through the ERPNext desk, not code you have to redeploy. Contribution and withholding logic runs in server-side Salary Component formulas and Python on_submit/validate doc events wired through hooks.py, so amounts compute deterministically inside the standard Payroll Entry run and post to the correct GL and liability accounts. Employer-vs-employee splits, salary-ceiling caps and the monthly-vs-semi-monthly proration are all handled in the computation layer rather than left to the payroll clerk.

On top of the calculation engine we build the reporting and compliance surface your accountants actually file with: the BIR alphalist and 1601C monthly remittance return as Query/Script Reports, per-agency remittance schedules for SSS/PhilHealth/Pag-IBIG, and 13th-month pay computation prorated over actual months worked. Role Profiles and permission rules scope who can view raw salary data versus who can run and approve a payroll cycle. Where you need to feed a government portal or a downstream system, we expose whitelisted methods over the Frappe REST API so remittance and alphalist data can be pulled programmatically, and scheduler events can pre-stage each cycle. The app targets Frappe/ERPNext v15 and v16, and client scripts add the desk-side validations and field behavior your team expects.

Because this is build-to-order, nothing is downloaded and hoped-for. We start with a short scoping call to confirm your pay frequencies, entity structure, which statutory circulars are in force and any company-specific allowances or de minimis rules. We build against that scope, hand you installable source for your version, deploy to a staging bench for UAT, then cut over to production with a rollback plan and a post-go-live support window. Typical delivery is one working week from confirmed scope, depending on how many pay groups and report variants you need.