Most HRMS feature lists are written by the vendors selling the software, which is why every one of them happens to describe that vendor's product.
Here is the version written for the buyer.
Modern human resource management system software should carry fifteen capabilities. Nine are non-negotiable for any Indian company past thirty people. Six matter more as you scale.
Use this as a shortlist filter. Full detail on each follows below, including the specific test to run during the demo.
- One employee master record
- Role-based access and a full audit trail
- Configurable approval workflows
- A payroll engine built for Indian statute
- Automated filings, challans and returns
- Multi-state and multi-entity handling
- Leave rules that feed payroll directly
- Attendance capture across every work mode
- Shift, roster and overtime handling
- A self-service portal employees actually use
- A mobile app with genuine parity
- Expense and travel claims in the same system
- Recruitment and digital onboarding
- Performance reviews tied to the employee record
- Exit and full and final settlement
The gap between a strong platform and a weak one is rarely whether a feature exists. It is whether the feature works without someone opening Excel afterwards. Every section below gives you a way to check that in under five minutes.
Why the checklist changed in 2026
Two regulatory shifts moved several of these features from useful to mandatory.
The four Labour Codes came into force on 21 November 2025, replacing 29 central labour laws, and the Central Rules under all four were notified on 8 to 9 May 2026. State rules remain uneven, so an employer with offices in three states can still face three different rule positions under one central law. The Code on Wages also requires basic plus dearness allowance to make up at least half of total remuneration, which changes the base for provident fund, gratuity, bonus and leave encashment. Salary structures built with a small basic and large allowances no longer hold.
The second shift is data. The DPDP Rules were notified in November 2025, with substantive obligations applying in full from May 2027 and penalties reaching ₹250 crore for failing to maintain reasonable security safeguards. Employee data sits squarely inside that scope: salary records, biometric attendance, health and insurance details, performance files. An HRMS is now a data protection surface, not just an HR tool.
Both changes point the same direction. The system has to hold the rules, not the person operating it.
Part 1: The system of record
1. One employee master record
Everything else on this list depends on this one. There should be a single record per employee that payroll, attendance, appraisals and exit all read from. No parallel spreadsheet for bank details. No second list of confirmation dates in someone's inbox.
Fragmented records are what produce the classic failures: an increment applied in one place and not another, a resigned employee still drawing salary, a PAN mismatch that stops a TDS return.
A serious human resource management system software platform makes the master record the only writable source, then pushes changes outward.
2. Role-based access and a full audit trail
Under the DPDP framework, being able to show who accessed employee data, when and why, stops being good hygiene and becomes evidence. The platform needs granular permissions by role rather than a blunt admin or non-admin split, plus a log that records every view and edit with a timestamp.
3. Configurable approval workflows
Approval chains differ by company and by transaction. Leave might need one approver, an expense claim above a threshold might need three, a salary revision might need finance and the founder. If workflows are hard-coded, you end up bending your process to fit the software.
This matters statutorily too. The Industrial Relations Code requires establishments with 20 or more workers to constitute a Grievance Redressal Committee, with proceedings to be completed within thirty days of the application. Running that through email leaves no defensible record of timelines. A proper employee grievance management system gives each complaint a clock, an owner and a trail.
Part 2: Pay and statutory compliance
4. A payroll engine built for Indian statute
This is where generic international platforms fail Indian buyers. The engine must handle provident fund, employees' state insurance, professional tax, labour welfare fund and TDS as native logic, not as configurable deduction rows you maintain yourself.
The details matter. ESI runs at 3.25% employer and 0.75% employee on gross wages, applicable up to ₹21,000 a month and ₹25,000 for employees with disabilities. It also runs in two contribution periods, April to September and October to March, and an employee who crosses the ceiling mid-period stays covered until that period ends. Stopping the deduction the month the increment lands is one of the most common compliance misses in Indian payroll, and a system that knows the rule prevents it silently.
Good payroll management system software also handles the awkward cases without manual intervention: mid-month joiners, unpaid leave, mid-year revisions with arrears, and the ₹15,000 EPF wage ceiling that has held since 2014 and remained in place through 2026, despite a Supreme Court direction in January 2026 asking the Centre and EPFO to decide on revising it.
5. Automated filings, challans and returns
Calculating correctly is half the job. The system should generate the ECR file for PF, the ESI return, professional tax challans by state and Form 24Q for TDS, and it should track deadlines rather than expect you to.
The cost of missing them is specific. PF and ESI contributions are due by the 15th of the following month, and late PF payment attracts interest under Section 7Q plus damages under Section 14B that scale from 5% to 25% depending on how long the default runs. Our guide to PF, ESI and TDS compliance sets out the full filing calendar.
6. Multi-state and multi-entity handling
Professional tax is levied by some states and not others. Labour welfare fund cycles differ. Minimum wage notifications are revised state by state, and each branch typically requires its own PF and ESI registration. A company with three locations is running three compliance calendars whether it acknowledges that or not.
The platform needs to hold state as an attribute of the employee, apply the right rules automatically, and still produce one consolidated payroll view for finance.
7. Leave rules that feed payroll directly
Leave balances that live in a system payroll cannot read directly are leave balances someone reconciles by hand every month. Loss of pay, encashment, carry-forward caps and prorated accrual for joiners all need to flow into the salary calculation without an export step.
An employee leave management system worth buying also handles policy variation: different quotas by grade, sandwich rules, holiday calendars by location, and accrual that starts on confirmation rather than joining if that is your policy.
Part 3: Time and workforce
8. Attendance capture across every work mode
Your workforce is probably not uniform. Some people badge into an office, some work from home, some are in the field. Attendance management software that only supports one capture method forces the rest onto a spreadsheet.
Look for biometric device integration, geo-tagged mobile punching, web check-in and a regularisation flow for the days something goes wrong. The regularisation flow matters more than people expect, because it is what stops managers approving corrections over WhatsApp.
9. Shift, roster and overtime handling
If you run shifts, this feature decides whether the platform is usable at all. Roster planning, shift allowances, night differentials, weekly off rotation and overtime calculation against the statutory wage definition all need to be native.
Overtime is worth particular attention right now. Because the Code on Wages sets basic plus dearness allowance at a minimum of half of total remuneration, the base your overtime calculates on may have moved. A system still computing on a legacy basic figure will understate the liability quietly.
Part 4: What employees actually touch
10. A self-service portal employees actually use
Adoption is the whole point. If employees cannot pull a payslip, download a Form 16, check a leave balance, update bank details or raise a claim without emailing HR, the platform has moved the work rather than removed it.
A well-built employee self service ESS portal cuts routine HR ticket volume sharply, and the effect compounds in distributed teams where the alternative is a manager relaying requests.
11. A mobile app with genuine parity
Most of the people in your company will never open the desktop platform. For field staff, factory teams and anyone without a company laptop, the app is the product.
Parity is the thing to check. Many vendors ship an app that shows payslips and nothing else, while approvals, regularisation and claims stay locked to desktop. A real HR management mobile app lets a manager approve leave, review an expense claim and check a team roster from a phone.
12. Expense and travel claims in the same system
Reimbursements are the most common source of quiet employee frustration, and they are usually handled outside the HRMS in a mix of email and finance spreadsheets. Bringing them in means claim submission with receipt capture, policy limits enforced at entry, multi-level approval and settlement through payroll rather than a separate transfer.
Employee expense management software that sits inside the HR platform also gives you something standalone tools cannot: the claim, the approval and the payout all reference the same employee record.
Part 5: Hiring, growth and exits
13. Recruitment and digital onboarding
The gap between a signed offer and a productive first day is where most HR teams lose time. Requisition approval, candidate pipeline, offer generation and document collection should run in the same system that will hold the employee record afterwards, so nothing is re-keyed.
Onboarding is where this pays off. NavoraHR's recruitment and onboarding module carries candidate data straight into the employee master, which means PAN, Aadhaar, bank details and UAN are captured once. HR letter generation software then produces the offer, appointment and confirmation letters from templates rather than from an old Word file someone edits.
This has become more pointed under the Labour Codes, which require appointment letters for workers. A system that generates them from the master record makes that a background process.
14. Performance reviews tied to the employee record
An appraisal management system that runs as a standalone form collection exercise produces documents, not decisions. The version worth buying links goals to the employee record, holds continuous feedback rather than one annual scramble, supports multiple review formats, and connects the outcome to the increment that follows.
Development belongs here too. An employee training management system that reads skill gaps from appraisal outcomes turns a review into a plan instead of a filing.
15. Exit and full and final settlement
Exits are where fragmented systems fail most visibly, because everything unresolved surfaces at once: notice period recovery, leave encashment, gratuity, asset return, pending claims, final TDS.
The Labour Codes also changed the arithmetic. Fixed-term employees now become eligible for gratuity after one year of continuous service rather than five, so exit calculations that assumed the old threshold will understate liability.
An employee separation management system should run resignation through clearance, calculate the settlement against live payroll data and generate the relieving and experience letters at the end, all from the same record.
How many of these do you actually need
Not every company needs all fifteen on day one. Buying modules you will not configure is how implementations stall.
| Headcount | Non-negotiable | Add when you get there |
|---|---|---|
| Under 50 | Features 1 to 7 | Attendance modes and mobile once you go distributed |
| 50 to 200 | Features 1 to 12 | Appraisal and training as review cycles formalise |
| 200 plus | All 15 | Multi-entity handling and deeper audit controls |
The more useful question is whether the platform can grow into the rest without a migration. That is the practical argument for buying all 12 modules in one platform rather than assembling a stack: the employee record stays single, and adding a capability is a configuration change rather than an integration project.
If you do go modular, check two things before signing. First, whether pricing is per employee, per module or per entity. Second, whether adding a module later costs the same as buying it now.
The three questions that decide it
Feature lists get you to a shortlist. These get you to a decision.
Before you shortlist
Take the fifteen features above into your next three demos and run the specific test attached to each one. Vendors demo the happy path by default. Your job is to bring the mid-month joiner, the multi-state professional tax case and the resignation with pending claims, and watch what the platform does with them.