HRMS and payroll in India: PF, ESI, TDS and professional tax done right

Payroll errors hurt more than most system errors. An employee who is short paid notices the same day, and a missed PF or ESI deposit brings interest and damages. Yet many growing companies still run payroll on a spreadsheet maintained by one person who knows all the formulas.

Rates, ceilings and forms change every year, and nothing here is tax advice. Your chartered accountant or payroll consultant should confirm current rates and rules for your situation.

Quick answer

A good Indian HRMS calculates PF, ESI, professional tax and TDS on salary correctly for each state you operate in, produces the challans and returns in the formats the portals accept, and handles mid month joiners, leavers, arrears and revisions without manual fixes. Popular packaged options include Keka, greytHR, Zoho Payroll, Darwinbox and the payroll modules in Odoo and SAP. Custom payroll is rarely worth building.

The statutory pieces your system must get right

Provident Fund. Employee and employer contributions are calculated on PF wages, with the employer share split between the pension scheme and the provident fund. The system must handle the wage ceiling, employees who opt to contribute on higher wages, voluntary contributions, and the monthly ECR file uploaded on the EPFO unified portal.

ESI. Applies to employees below the notified wage ceiling, with separate employee and employer rates. Watch for employees who cross the ceiling mid year, since coverage continues until the end of the contribution period.

Professional tax. Levied by states, not the centre, with different slabs, due dates and registration rules. Gujarat, Maharashtra, Karnataka and West Bengal levy it; several states do not. If you have staff in four states, your HRMS needs four rule sets.

TDS on salary. The system must project annual income, apply the regime the employee has chosen, account for declarations and proofs, and spread tax across the remaining months. It must produce quarterly TDS return data and Form 16 at year end. With the Income Tax Act 2025 in force from April 2026, check that your vendor has updated section references and forms.

Labour Welfare Fund and gratuity. Smaller amounts, easily forgotten. Labour Welfare Fund is state specific. Gratuity needs a provision and a correct calculation at exit.

Where payroll usually goes wrong

• Salary structures nobody can explain. Ten allowances, each with its own rule, built up over years of negotiation. The labour codes now in force changed how wages are defined for several purposes, which affects PF and gratuity calculations when allowances form a large share of pay. Review your structure with an advisor before migrating.
• Attendance arriving late. Payroll can only be as accurate as the attendance and leave data feeding it. If shift records come in on paper on the 2nd, you will make corrections every month.
• Arrears and revisions. Increments backdated three months, with PF and TDS recalculated, are where weak systems fail. Test this specifically.
• Full and final settlement. Leave encashment, notice recovery, gratuity and TDS in one calculation. Ask to see it done.
• Contract labour. If contractors supply workers, you remain responsible for checking their PF and ESI compliance. Your HRMS or a separate process should track contractor challans.

How to test an HRMS before you buy

Take ten real employees from last year and anonymise them. Include the awkward ones: someone who joined on the 17th, someone who crossed the ESI ceiling, someone in another state, someone with a backdated increment, someone who resigned and took full and final settlement.

Ask the vendor to run those ten through their system in front of you and compare the output, line by line, with what you actually paid. Differences are not always the vendor's fault. Sometimes they reveal an error in your old process. Either way, you learn more in two hours than from any demo.

Switching without a bad month

1. Choose a start month away from year end and away from your appraisal cycle. Starting mid year is fine if opening balances for TDS and PF are loaded correctly.
2. Clean the employee master first: PAN, UAN, ESI number, bank details, date of joining, state of work.
3. Run the old and new systems in parallel for at least two months and reconcile every employee.
4. Switch employee self service on only after payroll is stable. Payslips with errors in a new portal damage trust quickly.
5. Keep the old data accessible for at least the statutory retention period.

What about privacy

Payroll holds bank accounts, PAN, Aadhaar-linked details, health information from medical claims and family data for nominations. Under the DPDP Act 2023 and the DPDP Rules 2025, with obligations phasing in up to May 2027, you need to know where this data sits, who can see it and how long you keep it. Limit HRMS admin access to the few people who need it, and turn on audit logs.

When to use a payroll service instead

If you have fewer than about 50 employees in one state, an outsourced payroll provider using a standard HRMS may be cheaper and safer than running it yourself. You still need someone internal who understands the outputs well enough to spot a wrong number.