Running Indian payroll on ERPNext looks fine until statutory month-end. Native HR & Payroll gives you Salary Structures, Salary Components and Payroll Entry, but it has no built-in understanding of the EPF wage ceiling, the ESI gross-wage eligibility cut-off, per-state Professional Tax slabs, or Section 192 TDS projection across the financial year. Teams end up maintaining parallel spreadsheets, hand-keying ECR text files into the EPFO and ESIC portals, and reconciling Form 24Q returns by hand — which is exactly where errors, late-filing interest and audit exposure creep in.

This build-to-order product is a proper Frappe application (india_statutory_payroll) with its own module, installed alongside ERPNext HR & Payroll on your bench rather than bolted on as loose customizations. We add configuration DocTypes — PF Settings, ESI Settings, Professional Tax Slab (keyed by state and effective-from date), and TDS Declaration for employee investment proofs — plus computed statutory Salary Components wired into your Salary Structure. Contribution math runs as server-side logic in hooks.py document events on Salary Slip (validate and on_submit) and in dedicated @frappe.whitelist() methods, so employer/employee EPF splits, EPS diversion, the ESI 0.75%/3.25% shares, PT slab lookup and monthly TDS deduction are calculated deterministically from the employee's structure — never re-typed.

On top of the calculation layer we build the outputs that actually get filed. A Query/Script Report generates the EPFO ECR text file in the correct fixed-width layout from submitted Salary Slips; a matching report produces the ESIC monthly contribution statement. TDS runs off a projected annual-income model per employee — total tax estimated across the financial year, spread evenly across remaining pay periods, and recalculated when a TDS Declaration or mid-year revision is submitted. Form 16 (Part B) and Form 24Q quarterly annexures are produced as print-format / report exports, and a scheduled scheduler_events job maintains gratuity liability accruals so the balance-sheet provision stays current without a manual month-end run. Role Profiles and DocType permissions scope PF/ESI/TDS configuration to Payroll Managers while employees only see their own declarations, and every whitelisted method is permission-checked so nothing leaks across the org.

Because this is build-to-order, nothing ships until we have agreed your scope. We start with a short scoping call to confirm your states for PT, your PF/ESI registration specifics, financial-year conventions, and target Frappe/ERPNext version (v15 or v16). We then build against a staging bench, run UAT with your real salary structures, and hand over installable source, a git repository, documentation and a training session. Typical delivery is 2–4 weeks from confirmed scope, and every deployment includes a rollback plan plus a post-go-live support window.