Running Kenyan payroll on stock ERPNext means fighting the Salary Structure engine every pay run. ERPNext core gives you a generic component/formula framework, but it does not ship the KRA PAYE tax bands, the tiered NSSF Act 2013 contribution logic, SHIF (the successor to NHIF) deductions, or the 1.5% Affordable Housing Levy — nor the P10 monthly return and per-employee P9 forms that KRA expects. Teams end up hand-coding fragile formula strings into Salary Component rows, re-editing them every time a rate or band changes, and reconciling statutory totals in spreadsheets outside the system. That is exactly where ERPNext native runs out of road.

We build a proper Frappe app (its own module, installed via bench get-app / bench install-app) that layers Kenya statutory logic onto ERPNext's existing Salary Structure, Salary Slip and Payroll Entry DocTypes rather than replacing them. Statutory rates live in versioned configuration DocTypes — PAYE band tables, NSSF Tier I/II limits, SHIF rate, personal and insurance relief — so when the Finance Act or a KRA notice changes a number, you edit a record instead of a formula string. The calculation runs through server-side logic (Python server scripts and hooks.py doc events on Salary Slip validate/on_submit) so PAYE, reliefs, NSSF, SHIF and Housing Levy are computed deterministically on the server, not in the browser, and applied consistently across single slips and bulk Payroll Entry runs.

Technically, the PAYE engine walks the graduated band table and applies personal relief and, where configured, insurance/pension relief; NSSF is computed as a tiered contribution against the pensionable-pay limits with the employer match; SHIF and the Housing Levy are applied as their respective percentages with the correct earnings base. Statutory returns are generated as ERPNext reports/print formats — a KRA iTax-ready P10 summary for the month and per-employee P9 forms — exportable for upload. Everything is exposed through the standard Frappe REST API and whitelisted methods so downstream tools (or your accountant's integrations) can pull results, and access is governed by role profiles and permissions so payroll data stays scoped to authorized roles. client scripts add the in-form validations and helper fields your team needs, and scheduler events can be wired for period-end reminders or draft-run generation. Built and tested against Frappe/ERPNext v15, with a v16 upgrade path.

Because this is build-to-order, nothing is a blind download. We start with a short scoping call to confirm your ERPNext version, pay elements, existing Salary Structures and which statutory outputs you file. ECOSIRE then builds your version of the app, validates it on a staging copy of your data with UAT and a rollback plan, installs it on your instance, and runs a training session before go-live. Typical delivery is one working week from confirmed scope, and you receive the full git repository plus a post-go-live support window.