Legislation that trips up even senior payroll professionals

By Louise Missen | Head of Member Services, APA

You've mastered payroll essentials. Here's the legislation that trips up even senior payroll professionals 

There's a moment in every payroll career where the fundamentals stop being the hard part. You can run a pay cycle in your sleep, you know your award clauses and STP finalisation doesn't make you nervous anymore. That's exactly the point where the real risk in payroll shows up, not in the transactions you do every week but in the ones you do once a year, once a decade or once ever.

We hear this constantly through the Helpdesk: it's rarely the routine pay run that generates the panicked call. It's the redundancy that doesn't fit the textbook case, the contractor arrangement that's suddenly a superannuation liability or the multi-entity restructure where nobody's sure whose payroll tax bill it actually is. These are the scenarios Payroll Essentials isn't designed to cover and where a lot of otherwise excellent, experienced professionals get caught out.

Here are four of the situations we see catch senior payroll professionals most often.

1. "Genuine" redundancy isn't a judgement call, it's a legal test, and getting it wrong is expensive

Most payroll professionals know redundancy payments have a tax-free component. Fewer are confident about what actually makes a redundancy genuine under tax law, as distinct from a termination that simply gets labelled "redundancy" in an offboarding conversation. Get the classification wrong and you're not looking at a rounding error; you're looking at incorrect PAYG withholding, an incorrect ETP category and potentially a very awkward conversation with the ATO down the track.

For 2026–27, the genuine redundancy tax-free limit is $13,598 plus $6,801 for every completed year of service. That formula is simple. Working out whether a given termination actually qualifies, particularly when a role is "restructured" rather than eliminated or when the employee is offered (and declines) a genuinely comparable role elsewhere in the business, is where it gets hard. The ETP cap that apply to the balance are also indexed annually, so a calculation that was correct last financial year isn't automatically correct this one.

2. Your "contractor" might now be a superannuation obligation you don't know about

The Closing Loopholes reforms introduced the concept of the "employee like worker" contractors, largely on digital labour platforms, who don't tick the traditional employee boxes but also don't have real bargaining power or control over how they work. Food delivery, platform based care work and parts of road transport are the clearest examples but the underlying test is about the nature of the working relationship, not the industry label on it.

Payroll teams that have always treated "contractor" as a clean, no super, no PAYG category are the ones most exposed here. Senior payroll professionals who haven't revisited a contractor arrangement since it was first set up, sometimes years ago, are relying on a classification that may no longer hold. This isn't a once and forget assessment anymore.

3. One business, five states, one very confusing payroll tax bill

Payroll tax feels like it should be simple: check the threshold, apply the rate, done. It stops being simple the moment a business has people working across state lines and grouping provisions come into play. Related entities can be grouped for payroll tax purposes even when their payrolls are run completely separately and nexus rules determine which state actually gets to tax wages when an employee works across more than one jurisdiction in a period.

We regularly hear from experienced payroll managers who've correctly registered and paid in their "home" state for years, only to discover a grouping or nexus issue during a due diligence process or an audit, usually the worst possible time to discover it.

4. Long service leave isn't one law and your payroll system won't tell you that

Long service leave is the entitlement senior payroll officers are most likely to assume they've already mastered because it feels like a fixed, universal rule: work long enough, get some extra leave. It isn't universal at all. LSL is set at the state and territory level, not federally, which means the qualifying period, the amount accrued and critically whether a departing employee gets anything before they hit the full qualifying period all depend on which jurisdiction you're in.

Notice how much variation sits inside that table. Victoria and the ACT reward loyalty in before NSW, Queensland and WA require. NSW pays pro-rata after just 5 years, but only if the person left for specific reasons, resign for a new job elsewhere and that same NSW employee may get nothing, while a colleague who resigned for illness would. That's not a detail a payroll system can infer; it's a fact about why someone left and someone has to enter it correctly.

This is exactly where relying on the payroll system becomes the risk rather than the safeguard. Most platforms ship with a default LSL configuration for the state the business was set up in and that configuration keeps calculating confidently and wrongly.

The gap between "processing payroll" and owning it

None of these scenarios is common enough to master by accident. You might see a genuine redundancy dispute once every few years, restructure a contractor base once or only discover your LSL configuration was wrong for a jurisdiction you rarely hire into, right when it matters most. That's precisely why they're the scenarios that separate a payroll officer who executes what they're told from the person a business trusts to make the call when there isn't a clear playbook.

That's the gap Advanced Payroll is built for. It's not a refresher on the fundamentals; it's the next step for practitioners who've outgrown Payroll Essentials and are ready to be the escalation point instead of the one escalating. If you're building a case to your manager for L&D budget this year or you're a team lead deciding who on your team is ready to own the complex calls instead of just flagging them, this is the course that closes that gap.