TL;DR: Managing HR across multiple entities means keeping each entity’s people, payroll, and compliance records distinct while one HR team runs them all. One HR system can do this well. The test is whether it separates entities cleanly, scopes access by entity, shares templates, and still reports across the whole group.

Last updated 9 October 2026.

Key takeaways

• A multi-entity business runs under more than one legal or trading entity, such as several ABNs, a franchise network, or state-based associations.
• According to WGEA, a corporate group must report once its entities employ 100 or more people combined, even if no single entity does.
• According to the Fair Work Ombudsman, employees of associated entities count towards the small business employer threshold of fewer than 15 employees.
• Revenue NSW groups linked businesses for payroll tax, and only one member of a group can claim the tax-free threshold.
• Payroll stays with each entity because each one pays its own people, while HR works best as one shared function.

What does multi-entity mean in HR?

Multi-entity means your business operates under more than one legal or trading entity, run by one leadership team. Growth, acquisitions, restructures, and new regions all create entities. Each one can carry its own ABN, payroll file, and compliance obligations. However, you still want one clear view of all your people.

Modern organisations are not always simple, and multi-entity structures come in several common shapes:

• Groups of companies with different ABNs or payroll IDs
• A franchisor managing several independently trading locations, each with its own staff
• Not-for-profits with separate incorporated associations across states
• One business dividing its operations between different regions or business units

Each entity often has its own HR policies, awards, and compliance requirements. Meanwhile, the people running HR, payroll, and finance usually sit at head office and work across all of them. So the HR job is to keep entities distinct where the law needs it, and unified everywhere else.

Why is HR harder across multiple entities?

HR is harder across multiple entities because some obligations belong to each entity while others count the whole group. Payroll, contracts, and records belong to the employing entity. By contrast, several Australian thresholds add related entities together. So an HR team that only sees one entity at a time can miss an obligation completely.

Thresholds that count the whole group

Three rules show the pattern clearly. According to WGEA, a corporate group with 100 or more employees across its parent and subsidiaries must report. WGEA also counts every employee in Australia across the group, not entity by entity. The Fair Work Ombudsman includes employees of associated entities when testing for a small business employer. In addition, Revenue NSW groups linked businesses, and only one group member can claim the payroll tax-free threshold.

Suppose you run four companies with 40 people each. No single entity looks like a reporting employer, yet the group has 160 employees. Headcount is the trap. As a result, you need a combined headcount you trust, rather than four spreadsheets added up by hand.

Records that stay with each entity

Other obligations sit firmly with the employing entity, which is the employer of its own staff. For example, the Fair Work Ombudsman requires employers to keep time and wages records for 7 years. Privacy adds a further boundary between entities. According to the OAIC, related bodies corporate can generally share non-sensitive personal information with each other. However, that rule does not extend to franchise or joint-venture relationships, so a franchisor needs firmer walls between locations.

Can one HR system support multiple business entities?

Yes, one HR system can support multiple business entities, as long as it was built for them. Most systems use one of two models. The first is a single shared directory, with each person linked to their employer and payroll. The second runs fully separate organisations under one login, so each entity stays sealed off.

Which one fits depends on how connected your entities are. A corporate group with shared managers, transfers, and group reporting usually wants one directory. By contrast, a franchise network or a group of unrelated businesses often wants each entity kept apart. In that case, only head office needs to move between them.

Entities in other countries add another layer, because leave, tax, and payroll rules change at the border. So check how a system handles each country before assuming it scales offshore. The trade-offs for Australian groups with overseas arms are covered in choosing HR for overseas entities.

What does managing HR across multiple entities well require?

Managing HR across multiple entities well comes down to five things. You need clear boundaries between entities, centralised visibility across them, and permissions set by entity. You also need processes you can repeat in every entity, plus compliance reporting for each entity and the group. Any approach, spreadsheet or software, can be measured against these five.

• Clear boundaries between entities: each entity keeps its own people, payroll connection, and compliance records, so reporting stays accurate and private.
• Centralised visibility: HR, payroll, and leadership teams see organisation-wide reports without logging in and out of several systems.
• Entity-level permissions and roles: local managers see their own team, while head office keeps oversight across every entity.
• Scalable processes: onboarding, policies, and performance reviews are set up once and reused, so standards stay consistent as you grow.
• Simple compliance and reporting: templates and requirements can differ by entity, while everything stays auditable in one place.

For instance, picture an acquisition of a fifth company with 60 staff and its own payroll file. With all five in place, you connect that payroll and assign the new people to their entity. Then you apply your existing onboarding and policies, and the group headcount updates that same week.

How does Worknice manage HR across multiple entities?

Worknice handles multiple entities in two ways, both built into the core of the platform. One account can connect several payroll entities and keep a single People Directory. Alternatively, you can run separate organisations, each with its own people and data. Either way, your HR team works from one login.

One People Directory, several payroll entities

This model suits groups that want visibility across entities. An Account Owner connects each payroll entity from Apps, in the App Directory. You can even connect several instances of the same payroll platform. Worknice integrates with Xero, MYOB AccountRight, MicrOpay, KeyPay, Employment Hero Payroll, and ELMO Payroll. In every case, payroll stays the source of truth for pay rules, award interpretation, and STP lodgement.

Next, you map people to the right payroll from each integration’s Remote Records list. There, you match existing records or create new ones where a person is missing. For a new hire, you choose their payroll entity in the Integration Connections section during onboarding. Otherwise, you add it later from the Integration Connections card on their Settings tab. The multiple payroll entities guide walks through each screen.

Because everyone sits in one People Directory, the org chart, leave calendar, and Insights reports cover the whole group. A person can also hold more than one position, with FTE set for each, across entities in the same account.

Separate organisations under one login

This model suits entities that must stay apart. Each organisation keeps its own people, positions, paperwork, reviews, and Insights. To add one, an Account Owner goes to Settings, then General settings, then Add organisation. Anyone with access to several organisations switches between them under Memberships in the profile menu. Their role can differ in each one, and each organisation can carry its own logo, policies, and contracts.

How do you keep processes consistent across entities in Worknice?

You keep processes consistent across entities by building each process once and reusing it. In a shared People Directory, onboarding workflows, paperwork types, and performance reviews reach everyone, whichever entity pays them. Across separate organisations, an Account Owner duplicates a paperwork type into another organisation, along with its template and settings.

Suppose head office updates its code of conduct acknowledgement. In a single account, the updated paperwork type reaches every employee in every entity. Across separate organisations, you duplicate it into each one and adjust anything local, such as a state-specific clause.

One detail is worth checking when you duplicate a paperwork type. Settings carry across to the copy, including Auto-assign missing paperwork. So the copy will start assigning itself once a compliance group in the new organisation requires it. The duplicating paperwork types guide covers the steps. As a result, there is no more double handling of one document in five places.

Can employees move between entities?

Yes, employees can move between entities, and how it works depends on your model. In a shared People Directory, a transfer changes the payroll entity a person connects to. They keep one Worknice record, so their history stays with them. Between separate organisations, data is not shared, so you add the person to the new organisation instead.

For instance, a site manager moves from your Queensland company to your New South Wales company on 1 July. In a shared account, you update their payroll connection and position. Their documents, reviews, and leave history remain on the same profile. However, the new employer’s payroll still needs their tax declaration and super details, because payroll records belong to each employer.

What are the limits of managing entities in Worknice?

Worknice keeps HR unified, but it does not replace each entity’s payroll. Award interpretation, pay runs, and STP lodgement stay in the payroll system for each entity. In addition, separate organisations do not share data or reports, so group reporting needs the single-account model. A few permissions also follow payroll connections rather than reporting lines.

Plan for these limits before you choose a setup:

• No reporting across separate organisations: Insights is organisation-specific, so several organisations cannot produce one combined headcount report.
• People are not copied between organisations: someone added in one organisation does not appear in another until an admin adds them.
• Manager leave visibility follows payroll: managers only see leave requests from people they share a payroll connection with.
• Connecting payroll is an Account Owner task: it also needs the right permissions inside each payroll system you connect.

None of these is a fault. Each is a design choice. Still, the right model for your group depends on which limit matters most to you.

Who is this approach for, and who needs something else?

This approach suits Australian organisations of roughly 50 to 2,000 people running several ABNs, payroll files, or brands. It works for groups that grow by acquisition, franchise networks, and not-for-profits with state-based associations. The common thread is wanting one HR system while each entity keeps the payroll it already uses.

Worknice is a good fit when your entities pay people through one or more of the six payroll systems above. Because Worknice is HRIS-only by design, it connects to that payroll rather than replacing it. Onboarding, compliance, leave, and performance then sit in one place for every entity. If you are comparing platforms, see what to look for in a multi-entity HRIS.

Look elsewhere in two situations. If you want one vendor to run payroll and HR together, an all-in-one HR and payroll platform fits that preference better. Similarly, if most of your entities sit outside Australia, a global HCM suite with localised payroll is the safer choice.

Frequently asked questions

Can HR systems support multiple business entities?

Yes. Many HR systems support multiple business entities through one of two models. Some use a shared directory where each person links to their employing entity and payroll. Others run separate organisations under one login. The right model depends on whether your entities need to see each other, share managers, and report as one group.

What does multi-entity mean?

Multi-entity means a business operates under more than one legal or trading entity. Common examples include a group of companies with different ABNs, a franchise network, or a not-for-profit with separate state associations. Each entity can have its own payroll, policies, and compliance obligations, while one leadership team manages people across all of them.

Can employees move between entities in Worknice?

Yes. In a single Worknice account with several payroll entities, you change which payroll the person connects to. Their profile, documents, and history stay in place throughout the move. If your entities run as separate organisations, data is not shared between them, so you add the person to the new organisation instead.

Can I restrict what each user sees across entities?

Yes. With separate organisations, you invite each user to the organisations they need, and they can hold a different role in each. Within a single account, managers see their own team and approve leave for people they share a payroll connection with. Account Owners keep full access across every entity.

How does managing entities separately help with compliance?

Keeping each entity’s people, payroll connection, and records distinct keeps audits, payroll reporting, and record-keeping accurate for the right employer. At the same time, a combined view lets you check group-wide thresholds from one system of record. WGEA reporting at 100 employees across a corporate group is one example.

About the author

Graham Martin is Co-founder of Worknice, an Australian HRIS built for mid-to-large organisations. He has spent more than a decade working with Australian People and Culture teams on HR systems, compliance, and payroll integration.

Related reading

• Worknice and KeyPay for multi-entity teams: how several KeyPay payroll entities connect to one Worknice account.
• Worknice payroll integrations: which payroll systems connect, and what syncs in each direction.
• HRIS vs payroll software: why payroll stays per entity while HR can be shared.
• Specialised HR software over all-in-one: the case for connecting best-of-breed tools rather than replacing them.

Sources

1. Workplace Gender Equality Agency. “Who needs to report?” Retrieved 9 October 2026. https://www.wgea.gov.au/reporting/reporting-guide/eligibility
2. Fair Work Ombudsman. “Who doesn’t get redundancy pay.” Content last updated 19 March 2026. Retrieved 9 October 2026. https://www.fairwork.gov.au/ending-employment/redundancy/who-doesnt-get-redundancy-pay
3. Fair Work Ombudsman. “Record-keeping.” Content last updated 28 August 2026. Retrieved 9 October 2026. https://www.fairwork.gov.au/pay-and-wages/paying-wages/record-keeping
4. Revenue NSW. “Payroll tax grouping.” Retrieved 9 October 2026. https://www.revenue.nsw.gov.au/taxes-duties-levies-royalties/payroll-tax/grouping
5. Office of the Australian Information Commissioner. “Chapter 6: APP 6 Use or disclosure of personal information.” Australian Privacy Principles guidelines. Retrieved 9 October 2026. https://www.oaic.gov.au/privacy/australian-privacy-principles/australian-privacy-principles-guidelines/chapter-6-app-6-use-or-disclosure-of-personal-information
6. Worknice Help Center. “Multiple Payroll Entities.” Retrieved 9 October 2026. https://help.worknice.com/article/multiple-payroll-entities
7. Worknice Help Center. “Multiple organisations.” Retrieved 9 October 2026. https://help.worknice.com/article/multiple-organisations
8. Worknice Help Center. “Duplicating paperwork types.” Retrieved 9 October 2026. https://help.worknice.com/article/duplicating-templates