Single Touch Payroll is the quiet infrastructure of Australian employment: every time you run pay, your software files a report with the ATO — gross wages, tax withheld, super liability, allowances, leave — itemised per employee, in near real time. Most employers enabled it years ago and haven't thought about it since, which is exactly how it's designed to work. But "automatic" isn't "correct": STP reports whatever your payroll file says, errors included, to an agency that increasingly cross-checks everything. Here's what it actually does, and the habits that keep it uneventful.
What gets reported, and who uses it
Each pay event sends the ATO year-to-date figures per employee: gross pay broken into components (under STP Phase 2, that means salary, overtime, allowances by type, bonuses and paid leave reported separately — not one lumped number), tax withheld, and superannuation liability. Employment details like start dates, cessation dates and reasons, and the basis of employment travel with it.
That data flows further than most owners realise. Employees see it as live income statements in myGov (no more annual payment summaries). Services Australia uses it for family payments and child support. And the ATO uses it as a matching engine: STP wages against your BAS W1/W2 labels, STP super liability against what funds actually receive — a match with real teeth now that payday super requires contributions within days of each pay event. Mismatches don't trigger drama immediately; they accumulate as flags.
Where it goes wrong
The errors are rarely exotic:
Mis-mapped pay items. STP Phase 2's disaggregation means every pay item in your software carries a classification — and an allowance mapped to the wrong category, or a loading folded into ordinary earnings, reports wrongly every pay run thereafter. Set wrong once, wrong forever. This mapping also drives what's flagged as ordinary time earnings for super, so a mapping error can quietly become a super shortfall too.
The BAS mismatch. W1 and W2 on your activity statement should reconcile to your STP-reported totals for the period. When payroll runs in one system and the BAS is prepared from another (or from habit), gaps open — and this is among the most common, most automated cross-checks the ATO runs.
Out-of-cycle payments handled casually. Bonuses, terminations, back-pays and corrections done "outside" payroll (a quick bank transfer, fixed up later) break the year-to-date chain. Everything paid to employees should go through the payroll system, full stop.
Finalisation done blind. The 14 July finalisation declaration tells the ATO (and your employees' tax agents) the year's figures are final. Finalising without reconciling payroll to the general ledger first converts small in-year errors into amended income statements, employee phone calls and re-lodged returns.
The accuracy habits that keep STP boring
Four routines, none onerous: reconcile quarterly — payroll reports vs general ledger vs the W1/W2 you're about to lodge, every BAS; audit pay item mappings once — an hour with your bookkeeper reviewing every pay item's STP category and super flag, repeated only when you add new items; keep employee data current — names, TFNs, dates and employment basis, since matching errors create flags even when the dollars are right; and fix errors through the system — payroll software has proper correction mechanisms that update the year-to-date data; side-channel fixes just create the next mismatch.
The reframe worth making
STP means the ATO's picture of your payroll is continuous, not annual — which sounds like surveillance but cuts both ways. An employer whose STP, BAS and super payments all reconcile is visibly compliant, every fortnight, without lifting a finger. In an environment where wage underpayment carries escalating consequences, a clean automated record is an asset. The businesses that find STP stressful are the ones whose underlying payroll is shaky; the reporting just makes existing quality visible. Fix the payroll and the reporting takes care of itself.
FAQ
Do I have to do anything each pay run?
No — lodgement is automatic when you finalise the pay run. Your obligations are accuracy, on-time pay events, and the annual finalisation by 14 July.
What if I discover a mistake from months ago?
Fix it in the payroll system, which will report corrected year-to-date figures in the next pay event. For significant errors (especially anything touching super), loop in your bookkeeper or agent — back-corrections can have super and tax consequences beyond the STP report itself.
Does STP apply to closely held payees — like paying myself?
Yes, with some concessions: closely held payees (family members, directors) can be reported quarterly rather than per-pay in defined circumstances. If you're paying yourself wages, those payments belong in STP like anyone else's.
Payroll is where compliance, cash and people meet — and where small setup errors compound quietly. Our free Business Health Check includes a payroll once-over; it takes five minutes.
About the author
Nick Lucock
Chief Executive Officer, Valont
Nick leads Valont's day-to-day operations across Finance, People, Operations and Growth. He writes about how the work actually gets done — the processes, systems, and tools that keep Australian SMEs compliant and growing.
LinkedIn →