Multi-State Payroll Tax: How Employee Nexus Determination Works
When an employer operates across multiple Australian states, each employee's wages must be allocated to the correct state before payroll tax can be calculated. This allocation process is called nexus determination. Getting it right is the single most consequential step in multi-state payroll tax compliance.
Get nexus wrong and the entire calculation is wrong — potentially understating liability in one state while overstating it in another. State revenue offices can audit back several years. Errors discovered in audit typically attract interest and penalties on top of the primary liability.
This guide explains how nexus is determined, the five-step waterfall test that all Australian states have harmonised, and the common edge cases that cause problems in practice.
What Is Nexus?
Nexus, in payroll tax, refers to the connection between an employee and a particular state. An employee has nexus to a state when their employment relationship has a sufficient connection to that state to justify the state's claim to tax on those wages.
Importantly, nexus is determined per employee, not per employer. A single employer may have employees with nexus to three different states, which means calculating three separate state liabilities.
The Five-Step Waterfall Test
The Harmonised Payroll Tax Ruling establishes a five-step waterfall test that all Australian states except Western Australia apply to determine which state has nexus over a given employee. Western Australia uses a similar framework. The steps are applied in order — the first step that produces a clear answer determines nexus.
Step 1: Where Services Are Performed
The primary test is where the employee performs their work. If the employee performs services wholly in one state during the relevant period, that state has nexus. This is the most common case and resolves nexus for the majority of employees without going further.
An employee based at a Melbourne office who works exclusively in Victoria: nexus is VIC. An employee based at a Brisbane factory who works exclusively in Queensland: nexus is QLD.
Step 2: Employee's Home Address
If the employee performs services in more than one state — or if Step 1 is unclear — the next test is the employee's home address (principal place of residence). This step is often applied to mobile or field-based workers who regularly cross state lines.
An employee who lives in NSW but regularly visits client sites in NSW, VIC, and ACT: absent a clearer answer from Step 1, nexus is likely NSW.
Step 3: ABN State
If neither Step 1 nor Step 2 produces a clear answer, the state associated with the employer's ABN registration becomes the reference point. This step is relatively uncommon in practice but applies in unusual employment structures.
Step 4: Where Wages Are Paid
If the above steps are inconclusive, nexus defaults to the state where wages are actually paid to the employee. This typically means the location of the payroll function or the bank used to process payments.
Step 5: Principal Place of Business
The final fallback is the employer's principal place of business. This resolves any remaining cases where all prior steps have been inconclusive.
Common Edge Cases
The waterfall resolves most employees cleanly, but a subset of employment arrangements are genuinely difficult. These are the cases that most frequently cause compliance errors and audit exposure.
Remote Workers Who Relocated
The shift to remote work has created a new class of nexus problem. An employee hired in Sydney may have relocated to Queensland during their employment. Their home address changed. Their work location changed. But their payroll may still be running through an NSW payroll cycle with NSW state attributed to their wages.
Nexus follows the employee. Once the employee's home state changes, their nexus changes (assuming Step 1 is unclear and Step 2 applies). This change must be reflected in payroll tax calculations from the date of the move, not the end of the financial year.
Field-Based Multi-State Workers
Trades workers, freight drivers, field technicians, and construction workers may spend significant time in multiple states during a single month. The key question is whether the time in each state is substantial enough to invalidate Step 1.
The Harmonised Ruling provides guidance on "principally" — a worker who spends four days in VIC and one day in NSW per week is principally working in VIC. But 50/50 splits, project-based rotations, and variable patterns create genuine uncertainty.
Where Step 1 is genuinely unclear, Step 2 (home address) typically resolves the question. The employee's home state bears the nexus.
FIFO Workers
Fly-in, fly-out (FIFO) workers present a specific challenge. The physical work is performed in one state (e.g., WA for a mining site), but the employee lives in another (e.g., QLD). Under Step 1, if the employee performs all their work at the WA site, nexus is WA — regardless of home address. The site state prevails unless the employee performs substantial work in their home state between rotations.
Secondments and Long-Term Assignments
An employee seconded from a Sydney head office to a Melbourne client site for six months creates a Step 1 situation: they are performing services in VIC for the duration. Nexus shifts to VIC for that period. If the secondment ends and they return to Sydney, nexus reverts.
Tracking secondment start and end dates, and adjusting payroll tax allocations accordingly, is a compliance obligation that is easy to overlook.
Grouped Employers and Nexus
Nexus operates at the employee level and is not affected by whether the employer is part of a payroll tax group. Group membership affects threshold allocation (the Designated Group Employer claims the threshold; other members get nil). It does not affect which state has nexus over each employee.
A group member entity operating in QLD has its QLD employees' wages allocated to QLD — the same calculation applies regardless of whether the DGE is in NSW.
Why Manual Nexus Fails at Scale
For a single-state employer with a stable workforce, nexus is straightforward. For a practice managing twenty multi-state clients, or an employer with hundreds of field-based staff, manual nexus determination becomes unreliable.
The problems compound:
- Employee home addresses change and may not be promptly updated in payroll
- Field workers' state-by-state time splits are not captured in most payroll systems
- Secondments and project assignments start and end throughout the year
- FIFO rosters change
Each of these requires a decision and an update to the payroll tax allocation. Done manually, errors accumulate over the course of a financial year and may not be discovered until the annual reconciliation — if at all.
Automated Nexus Determination
Software that integrates directly with payroll systems can apply the five-step waterfall to every employee in every pay period, using the data already in the payroll system: home address, work location, leave types, and pay run history.
Where the data is clear, nexus is determined automatically. Where the data is insufficient or produces conflicting signals — a common result for field-based staff with incomplete address records — the system flags the employee as an exception and routes the case for human review.
Exception-based review is significantly more efficient than manual determination for every employee. It concentrates human attention on the genuinely uncertain cases and leaves the straightforward majority to automated rules.
Audit confidence also improves. When a state revenue office requests evidence of nexus determinations, a system with a documented five-step waterfall and per-employee determination history is a much stronger position than a spreadsheet.
This guide reflects the Harmonised Payroll Tax Ruling as applied across Australian states and territories. Verify current nexus rules with the relevant state revenue office or a payroll tax specialist before lodging.