As a company grows, it often ends up operating through several legal entities — separate registered companies under a common group, perhaps for different business lines, different locations, or structural reasons. The moment that happens, payroll gets considerably more complicated, because each legal entity is a separate employer in the eyes of the law, with its own registrations, its own filings, and its own compliance. Running payroll across multiple entities well is a real operational challenge. This guide explains what is involved and how to handle it.
Why multiple entities complicate payroll
A single company running payroll deals with one set of statutory registrations and one stream of filings. A group with multiple legal entities multiplies this — because, legally, each entity is its own employer.
Each entity typically has its own PF registration, its own ESI registration, its own professional tax registrations (which are themselves state-specific), its own TAN for TDS, and its own compliance obligations. An employee belongs to a specific entity, and their statutory contributions and deductions are made under that entity's registrations. So instead of one PF filing, the group makes one per entity; instead of one TDS return, one per entity; and so on. The compliance workload scales with the number of entities, and keeping each entity's filings correct and on time is a multiplied burden.
Separate registrations and filings
The first reality of multi-entity payroll is that the statutory machinery is replicated per entity. Each entity files its own PF and ESI returns under its own registrations, deposits its own TDS under its own TAN and files its own TDS returns, handles its own professional tax in each relevant state, and issues its own Form 16 to its own employees. None of this can be casually merged, because the registrations are entity-specific and the authorities expect filings per registered entity.
This means a payroll process for a multi-entity group has to keep each entity's employees, contributions, deductions, and filings cleanly separated and correctly attributed. An employee in Entity A must have their PF go to Entity A's PF account, their TDS deposited under Entity A's TAN, and so on. Mixing these up creates compliance errors that are awkward to unwind.
Inter-entity transfers
A particular complication arises when employees move between entities in the group — a transfer from Entity A to Entity B. This is more involved than it sounds, because the employee is effectively leaving one employer and joining another, even though they remain within the group.
Handling a transfer correctly involves questions about continuity of service (which matters for gratuity and other service-linked entitlements), the treatment of accumulated balances, the transfer or settlement of statutory accounts, and ensuring the employee's records move cleanly from one entity's payroll to the other's. Done badly, transfers create gaps or duplications in the employee's record and statutory history. Done well, they preserve continuity where appropriate while respecting that the legal employer has changed. Groups that move people between entities frequently need a clean process for this.
Consolidated reporting
While each entity files separately for statutory purposes, the group's management and finance functions usually need a consolidated view — total headcount, total payroll cost, total statutory liabilities across all entities. This is essential for budgeting, for understanding the group's overall people cost, and for financial reporting at the group level.
The tension is that the data is necessarily separated by entity for compliance, but needs to be aggregated for management. Producing reliable consolidated reporting means being able to roll up the per-entity payroll data into a group view accurately. When each entity's payroll lives in a separate system or spreadsheet, this consolidation is a manual exercise of pulling figures from each and adding them up — error-prone and slow, especially every month.
The accounting dimension
Multi-entity payroll also has to feed each entity's accounting separately, because each entity keeps its own books. The payroll cost for Entity A's employees posts to Entity A's general ledger; Entity B's to Entity B's. And the group may need consolidated financials on top. This adds another layer where per-entity payroll data has to flow correctly into per-entity accounting, and then roll up to the group. Keeping payroll and accounting aligned per entity, and consolidating accurately, is a significant part of the multi-entity challenge.
Common multi-entity payroll mistakes
The recurring errors include:
Mixing up which entity an employee belongs to, so their statutory contributions go to the wrong entity's registrations.
Missing or mis-filing one entity's returns among the many, since the workload is multiplied.
Mishandling inter-entity transfers, breaking continuity of service or duplicating records.
Producing inaccurate consolidated reporting because per-entity figures are pulled and added manually.
Misaligning each entity's payroll with its accounting, creating reconciliation problems per entity.
Running each entity's payroll in a separate system, which makes the whole group's payroll fragmented and hard to manage coherently.
Why multi-entity payroll belongs on one system
The core difficulty of multi-entity payroll is holding two things at once: clean separation by entity for compliance, and accurate aggregation across entities for management and the group. When each entity's payroll runs in a separate system or spreadsheet, achieving both is a constant manual effort — separate processing per entity, then manual consolidation, then per-entity accounting, then group roll-up, with transfers handled by hand in between.
When payroll for all entities sits on a single database, the system holds each entity's employees, registrations, contributions, and filings separately — so compliance stays correctly attributed per entity — while making the consolidated group view available instantly from the same data, because it is all in one place. Inter-entity transfers are handled within one system rather than across systems, preserving the employee's record. And each entity's payroll feeds its own accounting, with the group roll-up available from the same source. Nothing has to be manually consolidated. This is exactly how Helion handles multi-entity payroll — one platform that keeps entities cleanly separated for compliance while giving the group a single, accurate consolidated view, with transfers and accounting handled coherently. For a growing group operating through several legal entities, that single-database design turns multi-entity payroll from a multiplied manual burden into one manageable system.
This guide gives general information on running payroll across multiple legal entities in India as of 2026. The specific registration, filing, and inter-entity requirements depend on the entities' structures and the prevailing law, and should be handled with qualified payroll and tax professionals for a specific group.