The Allowance Side of Payday Super

Plenty changed on 1 July. New rates, super moving every payday, a clearing house that closed for good. Most of that was visible enough to plan around. The earnings base wasn't. A tool allowance and a fuel reimbursement can reach the same payslip off the same timesheet, and super attaches to one and not the other. Nothing in the pay run flags which is which.

What award interpretation now decides

Under quarterly remittance, a misclassified allowance produced one wrong figure and up to thirteen weeks before anyone had to look at it. That cushion is gone. The classification now sets the super owed and the charge that applies when the amount falls short, and both go out through Single Touch Payroll every cycle. Get the allowance type wrong, and the same error reaches the contribution, the STP submission and the client invoice inside one run. Award interpretation stopped being a wages question in July, and Working Blind Is About to Get Expensive covered the version of this that surfaces under review, where the entry survives, but the reasoning behind it doesn't.

The payments that changed sides

Ordinary time earnings didn't change. What sits around them did, and the ATO's guidance on qualifying earnings lists each category.

The list settles what counts. It doesn't settle where the call gets made. Allowance types are set at the pay item, usually once, usually by whoever configured the system, and every run after that inherits it. So, a wrong type isn't an error made in the cycle where it surfaces. It was made months earlier and has been going out correctly wrong ever since.

Same code, two answers, is the one that catches labour hire specifically. An allowance that's all-purpose under one agreement can be a reimbursement under another. A worker moving between two sites inside one fortnight carries the same code with two correct treatments. Systems that hold allowance types against the employee resolve it one way for the whole fortnight. Systems that hold them against the placement resolve each entry on its own.

The other trap is amount-driven. A reimbursement covers what a worker actually spent. Pay a flat daily figure of $45 regardless of the receipts, and it stops being a reimbursement, whatever the payslip calls it, and starts attracting super.

Correcting a pay item type used to be housekeeping. Adjust it, and the quarterly contribution absorbed the difference before anything went out. Now every cycle since the wrong type went in stands as its own late contribution, with its own date and its own charge.

Hence, it is worth testing against your own allowance table before the next cycle runs. The D-Bit FAQ section covers how classification, super and invoicing resolve from a single entry, including what happens when an allowance type gets corrected mid-run.

Where the difference is small and where it isn't

There's a reasonable assumption doing the rounds that qualifying earnings amounts to a relabelling exercise. For a salaried worker on fixed ordinary hours, no commission and no allowances, that's close to accurate. But that worker isn't the one labour hire, transport and mining operations are built around.

Commissions are where the two bases separate most cleanly. All of them count now, including those paid for work done entirely outside ordinary hours, which the ATO treated as exempt until July. Anyone running a desk on placement commissions has a super figure that moved in July without a single rate changing.

Variable hours carry the same exposure from a different direction. Someone has to establish which hours count as ordinary before the calculation can start. A timesheet upload and interpretation process that resolves it correctly for wages resolves it correctly for super, because the calculation runs off the same entry. One that works it out by hand does it twice (and the second pass is the one nobody blocks out time for).

Common questions

Which allowances count towards super? 

All-purpose allowances set by an award or agreement form part of the base. Money paid back to a worker for expenses they've already covered doesn't count, though a flat amount paid without reference to what was spent generally does.

Does overtime attract super now? 

No. Payments for hours worked outside ordinary hours fall outside qualifying earnings, and time off in lieu is treated the same way.

What happens when a pay item was coded wrong for several cycles? 

Each affected cycle stands as its own shortfall with its own date, and the charge follows the same timeline. Correcting the pay item stops it from recurring but doesn't clear the cycles already submitted.

Where to start looking

The allowance table is the fastest place to check, and it's a short job — the types are finite, and the wrong ones tend to be the oldest. The harder question is how many cycles have already gone out on one. Talk to D-Bit about what your current system can tell you there, and what it would take to answer it from the entry instead of the audit.