WhatsApp Us Now
Single Touch Payroll Phase 2 (STP2) was built on Australia’s foundation payroll reporting standard with detailed coding of income types, allowances, paid leave, overtime, salary sacrifice, child-support deductions and much more (and far more stringent real-time validation logic and transaction acknowledgement through The Australian Taxation Office (ATO) messaging).
For overworked payroll and HR teams, this change presented dozens of new failure points – a wrong income type here, a missing disaggregation there, and thus, a bounced pay event. Payroll outsourcing in Australia helps close these gaps by industrialising the data, controls and exception handling around STP2, so every submission reconciles first time, every time.
Key components of getting coding right
Outsourced payroll teams build and maintain a ‘living’ rules engine that maps each pay item to the correct STP2 constructs. For example:
Income types: STP2 requires disaggregating gross into base, overtime, bonuses/commissions, paid leave categories, salary sacrifice (super/other), lump sums, etc., with detailed reason codes.
Allowances: Correctly tagging allowances to category (e.g. cents-per-km, tools, meals, travel, qualifications) and understanding the reportable/non-reportable treatment.
Child support: Applying correct deduction/garnishee logic, handling percentage vs fixed orders, and including jurisdictional references so the ATO routing and downstream remittance align.
Offsets and adjustments: Using Year-to-Date (YTD) adjustments that preserve audit trails while repairing prior miscoding without corrupting employee balances.
Behind the scenes, they are also maintaining a controlled master-data layer—occupations, locations, cost centres, super funds, tax file number (TFN) status, etc.—so the “source of truth” for STP2 fields is consistent across onboarding, timesheets, rostering and the general ledger.
How experts reduce errors before the ATO sees them
The most effective fix is prevention. Mature vendors pre-validate every pay event in their staging areas before submission, matching locally against a subset of ATO rules. Think of it as mandatory field checks, data type/formatting, allowable value ranges, logical consistency (salary sacrifice cannot inflate ordinary time earnings (OTE)), duplicate event detection, and YTD continuity. They also operate reference data watchers (super fund USIs, tax tables, child-support references) and schedule data refreshes so no STP2 file is ever rejected for stale codes. Finally, sandbox test events are used for all new Enterprise Bargaining Agreement (EBA) clauses or allowance types before being made live.
ATO messaging and exception management
Expert providers connect securely and reliably via accredited Standard Business Reporting (SBR) gateways, and manage retries, throttling and correlation IDs for each pay event. When an event is bounced back with validation errors, exceptions are automatically triaged to the correct queue (coding, identity, transport issues). Standard operating procedures set response time targets—same day for payday events, 48 hours for non-blocking YTD corrections, and escalation if it cannot be rectified—to keep your ledger, payslips and STP2 files reconciled.
STP2 cutover checklist (STP1 → STP2 or system migration)
- Confirm inventory of all pay items and map to STP2 income types and allowance categories.
- Rebuild leave and overtime rules to disaggregate earnings; validate OTE impacts.
- Verify super stapling, USIs, fund Australian Business Numbers (ABNs), and salary-sacrifice configurations.
- Load and reconcile opening YTD balances at the employee level.
- Test a complete pay cycle in a sandbox and run parallel STP2 versus legacy reports.
- Prepare communications for employees on pay slip changes and year-end statements.
- Lock change windows and implement the post-go-live hypercare period.
Common STP2 rejection reasons (what they usually mean)
- Invalid income/allowance mapping: A pay item coded to an obsolete or mismatched category.
- Missing or malformed identifiers: TFN, ABN, USI, branch numbers or employee DOB/Address formats.
- Child-support coding issues: Deduction vs. garnishee mix-ups, order references missing, negative net.
- YTD continuity breaks: Negative or out-of-sequence adjustments that do not reconcile to prior submissions.
- Transport errors: Signature/certificate problems, gateway timeouts, or duplicate event IDs.
Remediation playbook (close the loop fast)
- Isolate the error: Pinpoint the employee, pay item and STP2 field that failed using the gateway’s detail and your pre-validation logs.
- Correct at source: Fix master data or pay-item mapping so the next run does not repeat the fault.
- Raise a clean adjustment: Post YTD adjustments that restore continuity, keeping the original event immutable.
- Resubmit with controls: Re-validate locally, then transmit the corrected event; confirm acceptance and archive artefacts.
- Prevent recurrence: Add a new automated rule or checklist step; tag the incident for trend reporting.
A reporting cadence that keeps leadership confident
- Per pay cycle: Submission status dashboard, exception log, and variance analysis to the prior cycle.
- Monthly: Reconciliation of YTD earnings vs General Ledger (GL), super obligations vs payments, and exception ageing.
- Quarterly: Compliance health scorecard (error rates, time-to-fix, rule changes), plus award/EBA change impacts.
- End of Financial Year (EOFY): Finalisation readiness pack—employee statements preview, outstanding adjustments, and sign-off tracker.
For many organisations, the real ROI of payroll outsourcing in Australia is the removal of friction. Fewer failed events, faster close, cleaner audits, and better employee trust in payslips and summaries. When combined with outsourced accounting services, CFOs gain an integrated view of payroll cost, liabilities and compliance risk, with one accountable partner, one Salary Sacrifice Arrangement (SLA) and one source of truth. STP2 submissions then become routine, not a risk.
