Complete Guide on Managing Your Human Resource
Managing human resources in India is mostly a compliance problem wearing the costume of a people problem. The appraisal cycle and the engagement survey get the attention; what actually breaks is a provident fund calculation against a ceiling that moved, or an ESI deduction applied to the wrong wage base. This guide is about the part that has rules.
Key takeaways
- Statutory deductions are the hard constraint: EPF at 12% from each side and ESI at 3.25% employer, 0.75% employee, each against its own wage definition and its own ceiling.
- The EPF wage ceiling reportedly moved in September 2026. A payroll system that hardcodes a ceiling is the problem, not the ceiling.
- Published sources on the new ceiling disagree and cite three different notification numbers, so verify against EPFO or the Gazette before you configure anything.
- Most of what HR software sells is reporting. Most of what it has to get right is arithmetic against statute.
What does HR management actually involve in India?
Four things with legal consequences and one without. The four are provident fund, state insurance, professional tax and tax deducted at source. The fifth — performance, engagement, learning — matters commercially but no inspector audits it.
The contribution rates are settled and worth knowing before any vendor explains them to you. Employee and employer each contribute 12% to EPF. The employer's 12% is not one number: 8.33% goes to the pension scheme and 3.67% to the provident fund proper, with roughly 0.5% administration charges and another 0.5% for EDLI on top (employer guide, Teamed). ESI is 3.25% from the employer and 0.75% from the employee on gross wages, and applies only below the notified ceiling (Empxtrack).
What an employer actually pays above salary
Roughly, on a covered employee, before any benefit you choose to offer:
| Component | Employer | Employee |
|---|---|---|
| EPF (provident fund share) | 3.67% | 12% combined |
| EPS (pension share) | 8.33% | — |
| EPF administration charges | ~0.5% | — |
| EDLI (linked insurance) | ~0.5% | — |
| ESI | 3.25% | 0.75% |
Each line has its own wage definition and its own ceiling. That is the whole difficulty: they are not one calculation applied five times.
Why did the provident fund ceiling just become everyone's problem?
Because it moved, and because the sources do not agree on the detail. Most published summaries say the EPF wage ceiling rose to ₹25,000 with effect from 17 September 2026 (LexComply), while other pages still describe the older ₹15,000 basis and the ₹1,800 maximum mandatory contribution that follows from it (Mercans). The sources also cite three different notification numbers between them.
So the practical instruction is: confirm the current ceiling against EPFO or the Gazette notification itself, not against a blog, and then check whether your payroll system lets you change it without a developer. If it does not, that is the finding — not the rate.
Which parts should be software, and which should not?
Software should own anything that is the same calculation every month: contributions, deductions, payslips, the statutory returns, leave balances, the employee master. These are high-volume, repetitive and checkable, which is the test for automating anything.
Software should not own judgement. A performance conversation routed through a workflow is still a conversation; a tool that scores it mostly produces a number people learn to game. Buy software for the arithmetic and the audit trail, and leave the judgement where it belongs.
Should you build an HRMS or buy one?
Buy, in most cases, and we will say so before quoting you a build. A product already tracks statute, and somebody else updates it when a ceiling moves — which, as above, it just did. That maintenance is the main thing you are paying for.
A build earns its cost under specific conditions: leave, shift or approval rules no product will model; a group consolidating several entities onto one payroll; or an existing system that has to stay and be integrated with. If none of those is true, a product is the cheaper answer. Our HR management system page covers what one platform spans, and payroll management covers why payroll is usually cheaper inside the same system than beside it.
What we have seen at DECK IT
We build business systems from Ahmedabad for companies in India and the United States, and the HR projects that go wrong tend to fail the same way twice.
The statutory configuration is treated as setup rather than as a feature. It is the feature. A system that cannot be reconfigured when a ceiling changes will need a developer every time the law moves, which is a running cost nobody quoted.
Payroll gets bought separately from HR, then reconciled by hand every month. Payroll depends on attendance, leave and the employee master. Keeping those in two systems creates a monthly matching exercise that no feature list warns you about.
Frequently asked questions
What are the EPF contribution rates in India?
Employee and employer each contribute 12%. The employer's share splits into 8.33% to the pension scheme and 3.67% to the provident fund, with around 0.5% administration charges and 0.5% EDLI on top. The wage ceiling that these apply to is the part that changes, so verify it against EPFO before configuring payroll.
What are the ESI contribution rates?
Employer 3.25% and employee 0.75% of gross wages, for employees at or below the notified wage ceiling. The rates are consistent across sources; the ceiling is the figure worth confirming.
Did the EPF wage ceiling change in 2026?
Most published summaries say it rose to ₹25,000 with effect from 17 September 2026, but they cite three different notification numbers and some pages still describe the older ₹15,000 basis. Check EPFO or the Gazette directly rather than a secondary source.
Should payroll be part of the HR system or separate?
One system is usually cheaper if you are buying both, because payroll depends on attendance, leave and the employee master. Separate payroll makes sense only when the HR system is one you intend to keep.
How long does an HRMS implementation take?
Six to eight weeks for a straightforward implementation, three to five months where it integrates with payroll, attendance and accounting. Payroll additionally needs a parallel run alongside your current process before you switch, so allow a cycle or two beyond the build.
Conclusion
Judge HR software on the boring part. Ask how the statutory ceilings are configured, who changes them when the law moves, and whether payroll reads the same employee master as everything else. Those three answers predict more about the next three years than any feature list will.
If you would like a second opinion on whether to configure a product or build, tell us what you run today.