Multi-site payroll software South Africa | Managing multiple entities

Running payroll across multiple companies shouldn't feel like running multiple jobs

For Finance Directors and HR Managers overseeing more than one entity, payroll quickly becomes one of the most time-consuming and risk-prone parts of the month. This page is for anyone who’s ever closed a laptop on a Friday wondering if every entity was done correctly.

Manual consolidation at group level

The real picture

What multi-entity payroll actually looks like in practice

In theory, running payroll for three companies instead of one should be three times the work. In practice, it’s rarely that clean — and the complexity compounds in ways that catch even experienced finance teams off guard.

Each entity in a South African group structure has its own PAYE reference number, its own EMP201 submission, its own SDL and UIF obligations, and potentially its own bargaining council requirements. A consolidated view of payroll cost across the group doesn’t exist by default — someone has to build it, usually in a spreadsheet, usually at month-end, usually under pressure.

01

Separate systems, separate risks

When each entity runs on a different system — or worse, a different version of the same system — error rates multiply. A change in tax tables needs to be applied everywhere, manually, at the same time.

02

Month-end becomes a coordination exercise

Chasing sign-offs across entities, reconciling figures from different sources, and trying to close the books at the same time across multiple payrolls is a structural problem, not a people problem.

03

Shared employees are a compliance headache

Employees who work across entities — charged to different cost centres, or on different contracts with different companies in the group — create split payroll situations that most systems handle poorly.

04

SARS doesn’t care about your org chart

Each entity is individually liable for its PAYE, UIF, and SDL submissions. A missed or incorrect EMP201 in one subsidiary creates a SARS exposure for that entity, regardless of how the rest of the group is performing.

Where things go wrong

The failure patterns that cost multi-entity businesses the most

Most multi-site payroll problems are predictable. They tend to come from the same structural gaps, repeated across organisations of different sizes and industries.

Inconsistent data across entities

Employee records, pay structures, and cost centre codes that live in separate systems drift out of sync. Reporting becomes unreliable and reconciliation takes longer every month.

Manual consolidation at group level

The group CFO or Finance Director needs a payroll cost view across all entities. Without a system that provides this natively, someone exports, copies, and pastes every single month. That process is both slow and error-prone.

Different entities on different compliance cycles

When individual entities run payroll independently, SARS submission dates get managed separately. A submission missed in one entity doesn’t show up as a problem until SARS makes contact — often months later.

Access and approval fragmentation

Payroll approval workflows that work for one company break down across three or four. Who approves what, for which entity, is often unclear — and audit trails don’t exist at group level.
Get in touch
Book a demo

What good looks like

What to look for in a multi-site payroll system

Not every payroll system is built for multi-entity management. Here’s what genuinely matters when you’re evaluating options for a group structure in South Africa.

Multiple entities, one platform

— The ability to manage all entities from a single system, with clear separation of data between companies and a consolidated view at group level when you need it.

Entity-level SARS compliance

— Each entity’s EMP201, UIF, SDL, and ETI configured and submitted independently, without manual intervention between them.

Role-based access across entities

— A group payroll manager should be able to see across all entities. An entity-level administrator should see only their own. Both should have appropriate approval workflows.

Shared employee handling

— Clear capability for employees who appear on multiple entity payrolls, with proper tax treatment across split remuneration.

Group-level reporting

— Payroll cost by entity, headcount by entity, leave liability by entity — without exporting and combining spreadsheets.

Consistent tax table updates

— When SARS changes rates, the update happens once, across all entities, at the same time. Not entity by entity.

South Africa-first compliance

— Bargaining council rules, ETI eligibility, and COIDA that apply per entity, not applied globally and then overridden.

Starting the conversation

Questions worth asking any payroll provider

If you’re evaluating systems for a multi-entity structure, these questions cut through the sales pitch quickly.

How many entities can be managed from a single login, and is there an additional cost per entity?

Can you show us consolidated payroll cost reporting across multiple entities — not just entity by entity?

How do you handle an employee who is paid by two entities in the same month?

When SARS updates tax tables, how does that flow through to all our entities simultaneously?

What does the approval workflow look like at group level versus entity level?

Can each entity have its own bargaining council configuration, or is that set globally?

Managing more than one entity?

Let’s have an honest conversation about what your group structure actually needs — no generic demo, no pressure.
Book a demo

© 2026 SmartHR. All Rights Reserved. Privacy Policy | Cookie Policy