A Tax Base That Crosses Your Workspaces
Most tax obligations line up with a legal entity: this company earned this, owes this, files this. Victorian payroll tax does not. Part 5 of the Payroll Tax Act 2007 constitutes <em>groups</em> of employers on several independent bases, and once you are in a group the wages of every member matter to every other member — including for liability, which is joint and several. That is a base drawn across company boundaries, in a product whose strongest guarantee is that one workspace cannot see another.
Four ways into a group, and they stack
The Part constitutes groups on more than one basis: corporations related to each other, businesses under common control, businesses that use each other's employees, and interests traced through corporations — the Act carries its own worked example, following a forty per cent direct interest from one corporation into another. Section 68 then removes the obvious escape route. The fact that a person is not a member of a group constituted under one provision of the Part does not prevent that person being a member of a group constituted under another. The tests are cumulative, not alternative, and there is a further provision under which smaller groups are subsumed by larger ones.
Two provisions soften and sharpen it in turn. Under section 79 the Commissioner may, by order in writing, determine that somebody who would be a member of a group is not one — but only having regard to the nature and degree of ownership and control, the nature of the businesses, and anything else the Commissioner considers relevant. And a determination can be expressed to take effect on a date <em>earlier than the date of the determination</em>, and can later be revoked.
A figure that was right can become the wrong figure
That back-dating power is the fact worth carrying away. A group boundary is not simply hard to establish — it can be redrawn retrospectively, by an order made after the periods it affects have closed. Which means the numbers you computed for a single entity, correctly, on the information you had, can turn out to have been the wrong numbers all along. The only defence against that is being able to recompute, which is a statement about your records rather than about your accounting: you need the wages, by period, by entity, in a form that can be re-aggregated on a boundary somebody else moved.
And the consequence of being in a group is not merely arithmetic. Under section 81, if a member of a group fails to pay an amount it is required to pay in respect of any period, every member of the group is liable jointly and severally, and the Commissioner may recover the whole amount from them, or from any of them. Section 80 lets the members designate one qualified member as the designated group employer — but only with the Commissioner's approval, and qualification is tested against a threshold amount in the Act's own Schedule.
What this post is not telling you
No threshold and no rate appear anywhere above, deliberately. Both live in Schedule 1 to the Act, which we did not read, and both move between financial years and between Australian states. Nor is there any filing cadence here: in Victoria the return and payment machinery sits in the Taxation Administration Act 1997 rather than in this Act, and we did not read that either. What is set out above is the shape of the grouping rules, which is the part that bears on how a system has to hold the data.
Tenant isolation is the best thing about this product's architecture, and it is exactly what makes a grouped tax base unreportable from inside it. Both of those statements are true and neither is a defect.
Two dimensions the payroll run does not have
A payroll run in this product is identified by three things: the workspace it belongs to, the period as a seven-character year and month, and the country the work was done in. That triple is the unique key. It moves through draft, calculated, approved and paid, and it carries timestamps for when it was run, approved and posted.
Set that against what this Act needs and two gaps appear, and they are of very different kinds. The first is a column. Payroll tax is a <em>state</em> tax, and the wages base is state by state; our dimension is the country of work, and an employee record carries a department, a position and a manager but no work location at all. So Australian wages cannot be split into Victorian wages and everything else, which is the first number the whole calculation needs.
The second is not a column, and calling it a gap would be misleading. Since the tenancy work of August 2026, a request with no resolvable workspace and no explicit filter returns zero rows rather than everything, and cross-workspace work has to be declared deliberately through a context object. That is the behaviour we want and the thing we would least like to loosen. It also means that if your group is five companies in five workspaces, no report inside any of them can produce the group's total wages — because producing it would be precisely the thing the isolation exists to prevent.
What a grouped calculation needs, against the payroll schema
| The input | Held today | Per entity | Across entities |
|---|---|---|---|
| Wages for a month, per workspace | Yes | Yes | No |
| The country the work was done in | Yes | Yes | No |
| The state or province the work was done in | No | No | No |
| Earnings separated from employer contributions | Yes | Yes | No |
| The group a workspace belongs to | No | No | No |
| A designated member who files for the group | No | No | No |
| Re-aggregation on a boundary that moved | No | No | No |
Built and maintained Configurable by you, not maintained by us Not built
The fourth row is worth crediting: a payslip line is typed as an earning, a statutory deduction, an employer contribution or a voluntary deduction, so what counts as wages is separable from what does not — which is the distinction most payroll-tax definitions turn on. The third row is a column. The last three rows are one design question, and it is a real one rather than an oversight.
What we would actually do about it
The honest answer has two halves, and only one of them is ours. The state dimension is a column and we should have it — payroll tax is not the only obligation that wants to know where somebody works, and an employee with no work location is a gap that shows up in several places once you look for it. The group figure is a different matter. The right shape is not a report that reaches across workspaces; it is a deliberate, declared export from each workspace and an aggregation somewhere that is entitled to see all of them, with the boundary recorded and the inputs kept so a redrawn boundary can be recomputed rather than re-guessed.
A column, an export, and a place to add up
The order is deliberate: without the first, the third has nothing worth aggregating.
A work location on an employee
With a state or province, not only a country, so a wages figure can be split the way a state tax needs. Useful well beyond this obligation, and the smallest item here.
A declared wages export per period
Per workspace, per period, per jurisdiction, with the payslip line types separated, stamped with when it was produced and from what — so an aggregation is built from artefacts rather than from live queries across a boundary.
A group as a recorded structure
Which workspaces belong to which group, from when, and which member is designated to file. Held as data with dates, because the boundary can be moved retrospectively.
A recomputation from kept inputs
So a determination that takes effect on an earlier date produces a new figure from the same evidence, alongside the figure that was filed, rather than replacing it.
The first is a column and we would do it regardless. The second is the piece that respects the isolation rather than working around it, and it is where we would want a conversation about who holds the aggregate and under whose authority. The third is a small table with dates on it. The fourth is what turns a back-dated order from a crisis into an afternoon.
Tell us what your operation needsWhat AWRA OpsHub does today
- A payroll run keyed to a workspace, a month and a country of work, moving through draft, calculated, approved and paid with timestamps at each step.
- Payslip lines typed by kind — earnings, statutory deductions, employer contributions and voluntary deductions — so what counts as wages is separable from what does not.
- Employees, attendance, leave and payroll as report datasets, so a wages figure for a period is a saved definition rather than a request.
- Workspace isolation that fails closed, so a request with no resolvable workspace returns nothing rather than everything, and cross-workspace work has to be declared deliberately.
- Per-currency figures with the composition disclosed rather than summed into one converted number.
- A full audit trail on the records involved, carrying the actor, the moment and the values that changed.
- Custom fields on employees, so a work location can be recorded, reported and exported today while the column is being discussed.
More we can add to your workspace
- A work location with a state or province on an employee, which is the first split a state payroll tax needs.
- A wages figure per jurisdiction, derived from that location rather than from the country on the payroll run.
- A group recorded as a structure, naming which workspaces belong together, from when, and which member is designated to file.
- A declared wages export per workspace and period, stamped with its inputs, as the artefact an aggregation is built from.
- An aggregation across workspaces, held somewhere entitled to see all of them rather than reached across an isolation boundary.
- A recomputation against a boundary that moved, producing a new figure alongside the one that was filed rather than in place of it.
- A joint liability visible from inside one workspace, so a member can see that an unpaid amount elsewhere is also its problem.
Where we point you to a specialist
- We will not tell you whether your companies are a group. Part 5 constitutes groups on several independent bases which operate cumulatively, it traces interests through corporations, and the Commissioner has both a power to exclude a person and a power to make that exclusion effective from an earlier date. That is a state revenue question with a corporate-structure question underneath it, and it is the single most consequential fact in the whole calculation.
- We will not print a threshold or a rate. Both are in Schedule 1 to the Act, which we did not read, and both move between financial years and differ between Australian states. Nor will we state a filing cadence for Victoria, because the return and payment machinery is in the Taxation Administration Act 1997 and we did not read that either. Getting those from the State Revenue Office costs you five minutes and getting them from us would cost you more than that.
- We hold a position on the isolation boundary and we are not going to move it. A report that could total wages across workspaces would be a report that could total anything across workspaces, and the failure mode of that is far worse than the inconvenience of assembling a group figure deliberately. If you need the aggregate, the right answer is an export from each workspace and an addition somewhere authorised to hold all of them — slower, visible, and auditable — rather than a query that quietly crosses a line the rest of the product treats as absolute.
The first item is a column and we would do it whatever your jurisdiction, because an employee with no work location limits more than tax. The second follows from it directly. The fourth is the piece we would scope first if a group figure is what you actually need, because it produces the artefact everything else is built on and it does so without touching the isolation. The third is a small table with dates. The sixth is the one that repays itself the first time a determination is back-dated, and it is a reason to keep the inputs rather than only the answer. The seventh is a notification question and worth discussing separately.
Our take
If you run several Australian companies under common control, the number this Act cares about is one your workspaces are built not to produce. That is the correct trade-off and we would make it again. What we should fix is the smaller half: an employee should carry a work location with a state on it, because a state tax needs a state and today the finest split we hold is a country. Beyond that, the useful discipline is an artefact rather than a feature — a wages export per entity per period, kept with its inputs, so that when a grouping determination arrives with an earlier effective date on it, you are recomputing from evidence instead of reconstructing from memory. Get the threshold, the rate and the return dates from the State Revenue Office, and get the group boundary from somebody who has read your share register.
Tell us where your legal entities and your operations disagree
Group structures break reporting in a specific way: the obligation is drawn on one boundary and the systems are drawn on another. We have looked at the accounting side of that in <a href="/blog/intercompany-recharges-that-never-agree">Intercompany Recharges That Never Agree</a> and at the holding-company shape in <a href="/blog/holding-company-here-operations-elsewhere">Holding Company Here, Operations Elsewhere</a>. This is the tax side of the same seam.
Talk to us about your workspace