Choosing an HRMS for 1,000+ Employees in India
Published: 24 Sept 2026 · Updated: 03 Nov 2026 · Author: NeevHR team
At 1,000 employees and above, an HRMS decision involves the CHRO, CFO and CIO together. The questions shift from features to governance: several legal entities in one system, bulk changes that keep history, separation of duties, an audit trail, a security review, and a rollout de-risked by a pilot and a reconciled parallel payroll.
Multiple legal entities in one system
Large Indian employers are rarely one company: an operating company, a services subsidiary, a manufacturing unit, sometimes an acquired business. Each legal entity has its own PAN and TAN (so its own TDS deposits, Form 138 returns and Form 130 certificates, formerly Form 24Q and Form 16), its own PF establishment code and ESI employer code, PT registrations in each state, salary bank accounts and general ledger.
The HRMS must keep these apart for statutory purposes while giving HR one view of the workforce. Ask to see two entities with different registrations running payroll in the same period, each producing its own ECR, ESIC file, TDS return and journal voucher.
An inter-entity transfer is usually a change of employer for income tax: each entity reports the salary it paid, and the new entity takes the earlier income and TDS into its projection. The UAN stays the same while the PF establishment changes. Decide and document service continuity for gratuity and leave before the first transfer, and record the move as a dated event on one employee record.
Bulk operations without breaking history
At this size change arrives in batches: a reorganisation moves 200 people to new managers, an annual revision changes everyone's pay, a site closure separates a team. Look for bulk import with a dry run that reports errors before saving, mass actions for transfers, manager changes and separations that create proper dated events, compensation cycles with review and approval, and an audit entry for every bulk change.
Separation of duties
Payroll fraud and payroll errors share a root cause: one person who can change data, run payroll and release payment. Auditors expect the duties split, and the system should enforce it, not only document it.
| Activity | Maker | Checker |
|---|---|---|
| Salary revision or new structure | HR operations | HR head or compensation team |
| Bank account change | Employee or HR | Payroll or HR reviewer |
| Payroll compute | Payroll executive | Payroll lead (verify) |
| Payroll approval | Not the person who computed | Finance or payroll head |
| Publish, bank file and payslips | Payroll | Finance releases payment |
| Role and permission changes | IT or HRIS admin | Separate approver |
Audit trail
For any change the log should show what changed, from what to what, who made it and when. At this size it should cover employee master, salary and bank changes, payroll runs and approvals, statutory settings, roles and permissions, and data exports. Ask to see the log for a salary change made last week, and how long logs are kept.
The security review
Get answers in writing, and ask for what is available today rather than what is planned.
| Question | Why it matters |
|---|---|
| How is our data isolated from other customers? | Isolation should hold at the database layer, not only in application code |
| Which fields are encrypted at rest? | PAN, Aadhaar, UAN and bank details are high-risk if exposed |
| Can MFA be enforced for all users? | Password-only access to salary data is hard to defend |
| Is single sign-on available? | Your identity team may require it |
| Where is data hosted? | Many Indian employers prefer or require hosting in India |
| Which certifications are held today? | Some procurement policies require SOC 2 or ISO 27001 |
| How are DPDP requests handled? | The DPDP Act, 2023 applies to employee data; its main duties apply from 13 May 2027 under the DPDP Rules, 2025 |
| What retention and legal hold controls exist? | Records must be kept for statutory periods and some preserved during disputes |
Integrations
Expect to connect biometric devices across many sites (ideally over a standard push protocol), bank payment files in your banks' formats, your accounting system through a journal export or an API, and your own data platform through APIs and webhooks. Ask for the integrations live today and test the ones you depend on during the pilot.
Phased rollout with a pilot and parallel payroll
Choose a pilot that is representative but not the most complex: it should include shifts, more than one state and a mix of ESI and non-ESI employees.
| Phase | Scope | Exit criterion |
|---|---|---|
| 1. Foundation | All entities: employee master, organisation, roles and data scopes | Master data reconciled to current payroll headcount |
| 2. Pilot entity | One entity or location: attendance, leave, payroll | One parallel payroll fully reconciled |
| 3. Pilot go-live | Pay the pilot entity from the new system | Statutory files accepted and bank payment successful |
| 4. Remaining entities | Waves, each with its own parallel run | Each wave reconciled before go-live |
| 5. Talent modules | Performance, recruitment, compensation cycles | Introduced at a cycle boundary |
Worked example: reconciling a parallel run
A group has three entities: A with 650 employees, B with 400 and C with 250, 1,300 in all. The team pilots Entity C for one month in parallel. The rule: every employee's net pay must match the legacy payroll to the rupee, or the difference must be explained and accepted. Of 250 employees, 243 match and 7 differ.
Three differences were configuration errors in the new system, now fixed; four were errors or timing issues in the legacy payroll. That is typical: a parallel run tests both systems. After the fix the team reran the month, got 250 of 250 matched or explained, and went live the following month.
| Cause | Employees | Resolution |
|---|---|---|
| LOP divisor: legacy used 30 days, the new setup calendar days | 3 | Policy confirmed as 30 days; configuration corrected |
| PT state: mid-month transfers, legacy applied the old state | 2 | New system correct; legacy error noted |
| Arrears: a backdated promotion missed in legacy | 1 | New system correct |
| TDS: a declaration updated after the legacy cut-off | 1 | Timing difference; accepted |
Common mistakes
- Treating all entities as one for statutory purposes, so returns and challans mix registrations.
- Making bulk changes outside the system, which breaks the change history.
- Granting one person compute and approve rights because the team is busy at go-live.
- Accepting a security questionnaire on trust without checking what is live.
- Going live across every entity at once with no pilot and no parallel payroll.
Where NeevHR fits
NeevHR is an India-first HRMS and payroll software platform for growing and mid-market businesses. It supports multiple entities, bulk actions, separation of duties, an audit log, each company's data kept separate in the database, field-level encryption of sensitive identifiers and enforceable MFA. Worth knowing: single sign-on covers Google with Microsoft being switched on but not SAML, and NeevHR does not currently hold SOC 2 or ISO 27001 certification.