The Indian HRMS market is crowded with vendors, and the field has expanded sharply in the last three years. Every one of them will tell you they handle PF, ESI, and TDS. Every one of them will show you a clean demo with a polished interface. And every one of them will present a proposal that looks competitive until the Year 2 renewal arrives.
Getting the HRMS decision wrong in India in 2026 is expensive in ways that compound quietly. A platform that does not update automatically for the four New Labour Codes active from November 2025 creates compliance risk in every payroll run. A contract that starts billing from signature rather than go-live costs you money before a single employee logs in. A platform sold to you at mid-market scale that was actually built for enterprises above 2,000 employees creates adoption problems, support gaps, and implementation overruns that take months to resolve.
This guide is a step-by-step framework for Indian HR directors, finance heads, and business owners who want to get the decision right the first time. Not a product comparison. A buying process you can follow from needs assessment to signed contract, with an RFP checklist and demo questions you can use directly.
Step 1: Scope Your Actual Needs Before Looking at Any Vendor
The most common HRMS buying mistake Indian companies make is starting with vendor demos before they have a clear picture of what they actually need. Spend one meeting answering these questions internally before you talk to a single vendor.
- Headcount and growth trajectory: How many employees do you have today? What is your realistic headcount in 24 months? A platform that works well at 200 employees sometimes hits operational limits at 400. Ask every vendor for reference customers at your projected headcount, not your current one.
- Entity structure: How many Indian legal entities does your organization operate? Holding companies, subsidiaries, and separate manufacturing and trading entities all create multi-entity payroll complexity. If you have more than one entity, confirm that multi-entity management is native, not a separate implementation per entity.
- State footprint: How many Indian states do your employees work across? Professional tax is levied in roughly 21 states and union territories, each with its own slabs; labour welfare funds apply in 16 states at different frequencies, and minimum wages are set at the state level. A platform that handles multi-state compliance in one payroll run is fundamentally different from one that requires separate configurations per state.
- Module scope: now versus 12 months: What modules do you need operational on day one? What will you activate in months 6 to 12? Buying a full suite at contract signing and activating only payroll in Year 1 locks capital in modules you are not using. Platforms that allow modular activation as you grow deliver meaningfully lower effective Year 1 cost.
- International footprint:
Do you have operations or concrete expansion plans in the UAE, Malaysia, Singapore, or other markets within 24 months? If yes, shortlist only platforms with native multi-country payroll. Adding a second local vendor in each new country creates reconciliation overhead that compounds with every market you enter.
- Compliance complexity: Are you running payroll across multiple pay structures, salaried, hourly, contractual, or third-party contractor, within the same organization? Do you have employees under both old and new income tax regimes? Do you need to track contractor compliance under the Contract Labour (Regulation and Abolition) Act? The more complex your compliance landscape, the more important native compliance depth becomes relative to any other feature.
Explore: Akrivia HR Maturity Assessment to benchmark your current HR capabilities.
Step 2: Must-Have vs Nice-to-Have in India in 2026
The Indian HRMS market changed materially in 2026. Two regulatory events shifted what belongs on the must-have list.
The four New Labour Codes — Code on Wages 2019, Code on Social Security 2020, Industrial Relations Code 2020, and Occupational Safety Health and Working Conditions Code 2020, became active in November 2025. They restructure how wages are defined (statutory ‘wages’ must be at least 50% of total remuneration, capping excluded allowances, how overtime is calculated (now at 2x the updated wage definition), how Full and Final settlement timelines work (two working days), and how leave encashment is computed. Any HRMS that has not updated for all four codes is creating compliance exposure in every payroll cycle it runs.
The new Income Tax Act became effective 1 April 2026, consolidating and restructuring India’s income tax framework. The new tax regime has been the default since the Finance Act 2023 for employees who do not actively opt for the old regime. Every HRMS must support per-employee regime selection and automatic TDS recalculation when declarations change.
Must-haves for Indian HRMS buyers in 2026:
PF with UAN-linked EPFO filing and ECR challan generation. ESI with monthly ESIC returns. Professional Tax across every applicable state’s slabs with correct deduction timing per state. LWF across all 16 applicable states at the right frequency. TDS under both old and new income tax regimes per employee with automatic December reconciliation. Gratuity provisioning calculated correctly. Four New Labour Code compliance covering revised wage definition, overtime at 2x, two-working-day Full and Final settlement, and revised leave encashment. DPDP Act compliance with consent capture and 72-hour breach notification readiness. All of this must be native, not available through a partner integration, not on a near-term roadmap, and not dependent on your HR team manually applying regulatory updates.
Nice-to-haves that vendors will lead with in demos:
AI-generated job descriptions. Gamification for performance reviews. Sentiment analysis in exit interviews. Chatbot-first employee experience. 300-plus pre-built report templates. These are legitimate features. They are not reasons to choose a platform whose compliance engine has not updated for the New Labour Codes.
The filter is simple: confirm every must-have is live and native before you spend a single demo hour on nice-to-haves.
Step 3: Total Cost of Ownership Before You Shortlist
Before creating a shortlist, run a TCO calculation for every platform you are seriously considering. Our HR and payroll software pricing guide for India covers this in detail. The short version for buying decisions:
Ask every vendor these five cost questions in writing before you move them to the shortlist:
Does billing start at contract signature or at go-live?
A 90-day implementation on a ₹5 lakh annual contract costs you ₹1.25 lakh before a single employee uses the system. This single question eliminates vendors whose commercial model transfers risk to you at the contract stage.
What is the per-entity cost for multi-entity Indian operations?
Some platforms charge separately for each legal entity. For a three-entity Indian group, this can add ₹1 to 3 lakh annually to the base subscription. Confirm in writing whether multi-entity is included in the per-employee rate or charged extra.
What are Year 2 and Year 3 subscription prices?
Platforms with commonly reported annual renewal uplifts built into contracts can increase your cost by 25 to 35% over three years without any increase in what you use. Ask for a three-year price lock or a contractual uplift cap before you sign.
What does implementation cost and what is included?
Setup fees, data migration, biometric integration, and training are almost never included in the subscription quote. Get a written implementation quote before comparing subscription prices across vendors.
Is custom reporting self-service or vendor-ticketed?
Platforms that charge for custom report builds or require vendor tickets for non-standard analytics create ongoing hidden costs that do not appear in any subscription comparison.
Check out: HR and Payroll Software Pricing in India
Step 4: Score and Shortlist Your HRMS Vendors
Once you’ve defined your requirements and estimated the total cost of ownership (TCO), evaluate every HRMS using a standardized scorecard. This helps you compare vendors objectively instead of relying on sales demos or feature lists.
Scoring Method
- 0 = Not available
- 1 = Available through configuration, customization, or a third-party integration
- 2 = Available natively within the platform
HRMS Buyer Scorecard (2026)
Compliance (18 Points)
- New Labour Code compliance (all four codes)
- New Income Tax Act support with per-employee tax regime selection
- Native EPF/ECR filing with UAN integration
- Native ESI management with ESIC return generation
- Professional Tax (PT) support across applicable states
- Labour Welfare Fund (LWF) compliance across applicable states
- Automated gratuity calculation and provisioning
- DPDP Act compliance with consent management
- Automatic updates for regulatory changes
Maximum Score: 18
Operational Fit (12 Points)
- Multi-entity support in a single instance
- Multi-state payroll processing
- Direct attendance-to-payroll integration
- Support for both old and new tax regimes
- Contractor (CLRA) compliance support
- Mobile-first employee self-service experience
Maximum Score: 12
Commercial Terms (12 Points)
- Billing starts only after go-live
- No additional charges for multiple entities
- Year 2 and Year 3 pricing confirmed
- Annual price increase cap included in the contract
- Implementation costs clearly documented
- Self-service custom reporting
Maximum Score: 12
Scalability (10 Points)
- Native multi-country payroll
- Recruitment and Applicant Tracking System (ATS)
- Learning Management System (LMS)
- Built-in people analytics
Maximum Score: 10
How to Interpret Your Score
- 45–52: Strong shortlist candidate with enterprise-ready capabilities.
- 35–44: Suitable for many businesses but review feature gaps carefully.
- Below 35: May present compliance, scalability, or operational risks for growing Indian organizations.
Complete this scorecard for every vendor before scheduling product demonstrations to ensure you’re comparing platforms on measurable criteria rather than marketing claims.
Step 5: India HRMS RFP Checklist
If your procurement process requires a formal RFP, use this checklist to ensure every section covers what Indian mid-market buyers need in 2026.
Section 1: Indian Statutory Compliance
Confirm native support for: PF/ECR/UAN-linked EPFO filing, ESI with half-yearly returns, PT across all applicable states with correct deduction timing, LWF across applicable states at correct frequency, gratuity with provisional accrual, TDS under both tax regimes per employee, new labour code compliance across all four codes, including revised wage definition, overtime at 2x, and two-working-day FFS. Confirm the auto-update process for regulatory changes with the timeline SLA.
Section 2: Payroll Engine Architecture
Confirm: multi-entity in one instance without separate logins, multi-state payroll without per-state configuration overhead, attendance-to-payroll integration without manual import, contractor compliance tracking, payroll processing audit trail, and maker-checker workflow.
Section 3: Digital Personal Data Protection Act
Confirm: employee consent capture and management; where Indian employee data is stored and processed, and whether the vendor can keep it in India if your sector regulator or internal policy requires it; 72-hour breach notification readiness; data processing agreement available. Note that DPDP permits cross-border transfer by default under a negative-list model; general localisation is not mandated, though RBI, SEBI, and sector-specific rules may apply to your business
Section 4: HR Module Coverage
Specify which modules you require at go-live versus which will be activated within 12 months. Request pricing for both scenarios. Confirm whether modules are included in the base subscription or separately licensed. Confirm LMS and L&D module status specifically.
Section 5: Commercial Terms
Require: written confirmation of billing start date (at go-live, not contract signature); three-year pricing with uplift cap; per-entity pricing disclosed upfront; implementation and data migration costs in writing; data export process at contract end; custom reporting model (self-service vs vendor ticket); and support SLA with penalty clause for breach.
Section 6: Implementation
Requirements: a project plan with milestone dates, parallel payroll run period (minimum one cycle), named implementation project manager, go-live definition in writing, and post-go-live hypercare period.
Section 7: References
Require three customer references at similar headcount and entity complexity in the Indian market, with permission to contact directly. Specifically ask for one reference that went live in the last 12 months.
Where Akrivia HCM Fits This Framework
Running Akrivia HCM through the scorecard above, here is where it scores specifically for Indian mid-market buyers:
- On the compliance layer, all four New Labour Codes are reflected in the payroll engine. Both tax regimes are supported per employee with automatic TDS recalculation when declarations change. PF, ESI, professional tax across every applicable state, LWF, gratuity, and TDS are all native to the payroll engine. Regulatory updates are auto-applied. DPDP compliance includes consent management, breach-notification readiness, and the option to keep Indian employee data resident in India for businesses whose sector rules or internal policies require it.
- On operational fit, multiple Indian legal entities are managed from one dashboard without separate logins or per-entity surcharges. Attendance via GPS, mobile, biometric, and geo-fencing feeds directly into payroll without manual import. Old and new tax regimes per employee with mid-year change handling are fully supported.
- On commercial terms, billing starts at go-live. Multi-entity is included in one instance. Custom reporting is self-service within the platform.
- On scalability, multi-country payroll covering India alongside UAE, Malaysia, Singapore, and broader GCC and Southeast Asia is native. Recruitment, performance management, L&D, and people analytics powered by Akrivia CoPilot are all included.
For Indian businesses between 200 and 2,000 employees that score platforms against this framework, Akrivia HCM consistently reaches the shortlist.
Conclusion
Buying an HRMS in India in 2026 is not a vendor selection exercise. It is a business risk management decision. The wrong platform creates compliance exposure under the New Labour Codes, payroll errors under the new Income Tax Act, and commercial surprises at renewal that your finance team will ask you to explain.
The framework in this guide removes the variables that create those surprises. Scope your needs before demos. Filter on must-haves before nice-to-haves. Run TCO before shortlisting. Score every vendor on the same criteria. Ask the five commercial questions in Step 3 in writing before you move to demos. Build your RFP around Indian-specific requirements, not a generic global checklist.
The right HRMS for your Indian business is the one that passes every stage of this framework at your headcount, your entity complexity, and your growth trajectory.
FAQs
What changed in Indian HRMS requirements after the new labour codes took effect in November 2025?
Basic pay must now be at least 50% of CTC under the revised wage definition. Overtime is recalculated at 2x under the OSH Code. Full and final settlement must be completed within two working days. Leave encashment follows revised rules. Any HRMS not updated for all four codes is creating compliance exposure in every payroll it runs.
How many vendors should be on a final Indian HRMS shortlist?
Three is the ideal number for meaningful comparison without evaluation fatigue. Shortlist based on scorecard results, not on brand recognition or sales team persistence. A vendor that scores below 35 on the scorecard in this guide should not make the shortlist regardless of how impressive the demo was.
What is the minimum parallel payroll run period recommended before going live on a new Indian HRMS?
At least one full payroll cycle, ideally two. Run both the old and new systems simultaneously, compare outputs line by line for every employee, and resolve all discrepancies before cutting over. This step prevents the post-go-live payroll correction exercises that cost Indian HR teams significant time in the first quarter after implementation.
