Many Entities, One Company: What Multi-Entity HR Really Requires

Key Takeaways

In mid-sized companies, multiple legal entities are rarely a designed structure — they emerged from doing business. Operations run as one company, while the unit of HR administration (employment contracts, payroll, insurance, organization) is always the entity
Headcount reporting, org charts, inter-entity transfers, dual roles, payroll close, company-wide HR programs — what all of these have in common is that information fragmented by entity has to be managed at the company level, and that this gets harder with every entity added
Three things resolve it — treating the entity as an attribute of the individual rather than a partition of the organization, an org-chart structure that holds multiple entity affiliations in a single chart, and HR data linkage that carries a person's record across inter-entity transfers
JaDE supports entity-level administration and company-wide consolidated lookup within a single system, and on inter-entity transfer the prior employee number's history and HR data are linked automatically

Three entities with slightly different names. From the outside they are one company. The businesses are the same or connected, the CEO is the same, employees commute to the same head office, and without a business card even they do not think much about which entity they belong to. HR is two people at head office. Their days include moments like these. "Starting next month, take on the engineering side." To the person giving the instruction it is a departmental move; on paper it is a resignation and a new hire. "How many people do we have in total right now? Can we see it by division?" — a question that only gets an answer after opening three entity rosters, aligning job-grade criteria, and filtering out duplicate dual-role holders. Each one is something you can handle and move past. The problem is that in a multi-entity organization this is daily life, and that with every additional entity the administration gets steadily heavier.

This guide is written for the following readers.

HR staff at mid-sized and small companies with two or more entities where one team handles all HR and payroll
Organizations with frequent inter-entity transfers and dual roles, where every request for a company-wide figure means consolidating entity-level files
Organizations that have coped with per-entity systems or spreadsheets but are about to add one more entity

Why this hits mid-sized companies hardest

Multi-entity HR tends to bring to mind affiliate management at large corporate groups, but the companies more exposed to this problem are mid-sized ones. The reason is paradoxical. Large corporations know that movement between entities and consolidated administration is a big deal. They have transfer consent forms, group-wide job-grade systems and HR policies in place, and dedicated teams. In mid-sized companies, by contrast, entities came about from doing business. They were added one at a time for a client or a bidding requirement, for licensing or tax reasons, to separate business risk — and it is common for the same line of business to be run split across entities. Since no one ever designed the organization to operate at the entity level, no policy or tooling for inter-entity movement or consolidated reporting was ever prepared either. There are no entity boundaries in management's mind, yet the unit of HR administration — employment contracts, payroll, insurance, organization — is always the entity. Bridging that mismatch falls entirely on a small HR team.

What happens to HR as entities multiply

Laying out what actually arises from that mismatch gives the following. The degree varies by organization, but the moment you pass two entities, most of these appear in order.

Area	What happens in multi-entity operations	Limits of entity-level administration
Headcount and reporting	Management asks for total headcount, hiring and attrition trends, and labor costs on a "whole company" basis	Entity rosters are pulled and consolidated by hand. Duplicate dual-role holders and recently transferred employees have to be filtered out manually every time
Org chart	There is one org chart for the company, yet the same team contains members belonging to different entities	A system that manages headcount by entity cannot hold this org chart. The chart ends up in slides while the roster is kept separately per entity
Inter-entity transfer	Changing entity changes the party to the employment contract, so it is processed on paper as a resignation and rehire, with consent forms and social insurance filings following	The more frequent the transfers, the more an individual's history and tenure fragment by entity, and a ten-year veteran exists in the system as "hired this year"
Dual roles and secondment	One person performs work for two entities and must process approval documents for both	Even within the same department, members belong to different entities, so a single approval line cannot be set. Routing splits by which entity a document belongs to, and dual-role holders' approval authority has to be maintained per entity
Payroll close	One or two staff repeat the payroll close as many times as there are entities. Pay items and payment rules differ by entity	When each entity has its own system or ledger, close work grows in proportion to the number of entities, and cross-verification is effectively skipped
Company-wide HR programs	Evaluation, training, and recruiting are meant to run on a "whole company" basis, but the participant roster exists per entity	Evaluation and training run on one company-wide standard, yet participants cannot be pulled from the system in one go, so consolidating entity rosters is itself the first task

These six look like different jobs, but peel back a layer and they are the same problem. Processing a transfer, counting dual-role holders, consolidating an evaluation roster — all of it is re-gathering information about people and organization that is fragmented by entity back to the company level. What management wants is always the "whole company" picture, the data always exists at the entity level, and the gap between them is filled by someone's spreadsheet. The trouble is that the spreadsheet starts going stale the moment it is created. A "company-wide status" that does not reflect last week's transfers and this week's new hires goes into the management meeting.

Three things that resolve it

What it takes to get out of this state comes down to three things. They are not separate tasks but interlocking ones, so doing only one gets you half the effect.

1. Treat the entity as an attribute of the individual, not a partition of the organization

Most HR systems and management ledgers put the entity at the top and place organizations and people beneath it. With three entities, the structure splits into three worlds. Yet the reality of the company described here is the opposite. The company, the organization, and the people come first, and the entity is closer to a tag determining which employment contract a person holds and which entity handles their payroll and insurance. The job-grade system, the HR policies, and the working organization are all one at the company level from the start. The administrative structure has to follow that reality. That means keeping one HR master for the company and managing each member's entity affiliation as an attribute. Once this is in place, company-wide headcount stops being a matter of "consolidating" entity rosters and becomes simply a lookup, while processes that must be at the entity level — payroll, insurance, contracts, filings — are performed accurately according to each person's entity attribute.

2. Org chart: can it hold the one chart you actually have?

The org chart problem grows from the same root. This company's org chart is singular from the start. Work runs through a division, office, and team structure, and every member sits on that chart. It is just that within the same team, someone from one entity sits next to someone from another. The problem is that a system managing headcount by entity cannot express this obvious picture. Either a single team gets drawn split as many times as there are entities, or the chart is drawn in slides while the roster is kept per entity — a double bookkeeping begins. What is needed is the separation of organizational placement from entity affiliation. When where a member sits on the org chart and which entity they belong to are managed independently, the reality of three entity affiliations mixed in one team goes into the system as-is, and someone holding roles across two entities is expressed naturally on that structure too. Reorganizations are handled on the chart; entity changes are handled in the attribute. Because the two are separated, each one becomes simple.

3. HR data linkage: does the person's record carry across the transfer?

Whatever HR system you use, an inter-entity transfer ultimately consists of a resignation at the old entity and a hire at the new one. When the entity differs, the party to the employment contract changes, so this is not a limitation of the system but a procedure the law requires. Ancillary work such as collecting consent forms and filing social insurance is likewise something to execute the same way at each transfer, according to the policies and procedures the company has set. The real issue is not the procedure but the record — whether the person's history breaks or carries through the resignation and rehire. In a structure where history breaks at the entity boundary, the transferred employee exists at the new entity as "hired this year," evaluation and training history and payroll base data fragment, and the more frequent the transfers the more such people accumulate. This is why, at every promotion review or final severance settlement, someone repeats the work of tracking down and reattaching records from the previous entity. Even if the procedure follows resignation and rehire, whether the person's record carries across the entity as one continuous thread is the point to check when choosing a multi-entity system.

JaDE's approach: administer by entity, view company-wide

JaDE's multi-entity management supports the three points above within a single system. Things that must be at the entity level — pay policies, employment contracts, insurance processing — are separated and administered accurately by entity, but rather than a separate system per entity, one system lets the administrator switch entities while working. People and organization, meanwhile, default to the company level. The org chart is managed as one for the company and members' entity affiliation is held as an attribute, so the reality of several entity affiliations mixed within one team is expressed as-is, and total headcount and organizational composition are looked up on a consolidated basis regardless of entity boundaries. It is a structure where "how many people do we have?" is answered by a system lookup rather than a spreadsheet consolidation.

For inter-entity transfers, procedure and record operate separately. The procedure follows resignation and rehire, but on rehire the prior employee number's history is linked to the new one and basic HR data carries over automatically. The transferred employee's assignment, evaluation, and training history and payroll base data remain viewable after the entity change, and there is no re-entering information from scratch as if registering a new hire. Even an employee who has moved entities several times remains one continuous record inside the system.

And there is one thing the system cannot do for you: deciding how to represent your own company's structure. How entity affiliations are arranged on a single org chart, what principles govern inter-entity transfers and dual roles, and where to draw the line between what varies by entity and what is common to the company are the organization's to determine. That is why, during implementation, a JIC (JaDE Implementation Consultant) works through this alignment with you based on hands-on HR experience. Before the next reorganization, the next company-wide report, or the next inter-entity transfer, take a moment to check whether your HR data is in a state that can be viewed on a "whole company" basis. How to build that structure is something you can discuss directly with the JaDE team.