The Australian Taxation Office's digital payroll reporting system that requires employers to report employee wages, PAYG withholding, and superannuation information to the ATO each time they run payroll, replacing the old end-of-year reporting process.
Key Takeaways
Before STP, employers processed payroll throughout the year and then produced payment summaries (group certificates) at year-end. Employees needed these summaries to lodge their tax returns. The ATO received employer data once a year, months after the income was earned. STP flipped that model. Now the ATO receives payroll data with every pay run: weekly, fortnightly, or monthly. This gives the ATO near-real-time visibility into employer withholding and superannuation obligations. For employees, it means their income and tax information is pre-filled in their tax return from day one of tax season. For employers, the annual payment summary process is gone. STP replaced it with "finalisation" at year-end, where the employer marks the year's data as complete. The biggest shift for payroll teams wasn't technical. Most modern payroll software handles STP transmission automatically. The real change was in accuracy requirements. With annual reporting, errors could be caught and corrected before submission. With per-pay-run reporting, mistakes are visible to the ATO immediately.
STP Phase 2 significantly expanded the data employers must report, moving from aggregate gross figures to itemized components.
Under Phase 1, employers reported a single "gross" amount per employee per pay run. Phase 2 requires this to be broken into components: base salary, overtime, bonuses, directors' fees, paid leave (by type), allowances (by type), and lump-sum payments. This gives the ATO granular visibility into pay composition and helps pre-fill employee tax returns more accurately.
Phase 2 introduced income type codes that employers must assign to each payment. The key types are: SAW (salary and wages, the most common), CHP (closely held payees like family members in a business), IAA (inbound assignees to Australia), WHM (working holiday makers), SWP (seasonal worker programme), VOL (voluntary agreement), and LAB (labour hire). Each type has different reporting and withholding implications.
Employers now report a six-character tax treatment code for each employee that encodes their tax status: residency (R for resident, N for non-resident, W for working holiday maker), tax-free threshold claimed (T or N), HELP debt (H, S, F, C for different loan types or X for none), tax offset claimed (T or N), Medicare Levy variation (H for half, F for full exemption, or X for none), and Medicare Levy Surcharge status. This code determines the correct withholding rate.
Getting STP right starts with software configuration and employee data accuracy.
The STP submission is integrated into the normal payroll process. It happens automatically at the end of each pay run.
1. The employer processes the pay run in their payroll software (entering hours, leave, adjustments). 2. The software calculates gross pay, PAYG withholding, superannuation, and net pay for each employee. 3. When the employer finalizes the pay run, the software generates an STP report containing year-to-date totals for each employee. 4. The report is transmitted to the ATO via a secure API connection (Standard Business Reporting framework). 5. The ATO acknowledges receipt and validates the data. 6. If there are errors, the software displays them and the employer corrects and resubmits. 7. The pay run is complete once the STP report is accepted.
STP reports must be submitted on or before the pay day. If you pay employees on Thursday, the STP report must reach the ATO by Thursday. In practice, most payroll software submits the report as soon as the pay run is finalized, which is usually a day or two before pay day. The ATO provides some flexibility for small employers (fewer than 20 employees) who may lodge up to quarterly if they use a registered tax agent.
If you discover an error in a previous STP report, you correct it in the next pay run. STP reports contain year-to-date figures, so a correction in the current pay run automatically adjusts the cumulative totals. You don't need to go back and amend individual historical reports. For errors discovered after the financial year finalisation, you submit an update event to revise the year-to-date figures.
STP eliminated traditional payment summaries (group certificates). Instead, employers complete a "finalisation" process that tells the ATO the year's data is complete.
Employers must finalise STP data by July 14 following the end of the financial year (June 30). This involves running a final STP report that marks each employee's data as "final" for the financial year. Once finalised, the employee's income statement becomes "Tax ready" in myGov, and they can lodge their tax return using the pre-filled data. Closely held payees (family members paid by a family business) have an extended deadline of September 30.
Employees access their income statement through myGov (linked to the ATO). Before finalisation, the statement shows "Not tax ready" but displays year-to-date figures. After finalisation, it changes to "Tax ready" and the data is locked. Employees no longer receive paper or email payment summaries from their employer. If an employee needs a copy, they access it through myGov or request it from the ATO.
Family businesses and micro employers have specific STP concessions that recognize their simpler payroll structures.
A closely held payee is a person who is directly related to the entity that pays them (directors who are shareholders, family members in a family company, beneficiaries of a family trust). These payees can be reported quarterly rather than each pay run. The employer has three reporting options: report actual payments each quarter, report a reasonable estimate each quarter and reconcile at year-end, or report a percentage of the prior year's total each quarter. The extended finalisation deadline (September 30) gives these businesses more time.
Employers with 1 to 4 employees can use the ATO's free STP solution if they don't have payroll software. They can also lodge through a registered tax agent on a quarterly basis. Some low-cost STP solutions are available specifically for micro employers who process simple payrolls. The ATO's position is that no employer is exempt from STP, but the reporting pathway can be adapted for very small businesses.
The ATO takes a "support first" approach to STP compliance but has escalating enforcement tools for persistent non-compliance.
The ATO can impose Failure to Lodge (FTL) penalties on employers who consistently fail to submit STP reports on time. The penalty is calculated per 28-day period and scales with entity size: AUD 313 per period for small entities, up to AUD 1,565 per period for large entities (2024-25 rates). In practice, the ATO issues warnings and support notifications before imposing penalties, focusing on education for the first few missed lodgements.
Inaccurate STP data doesn't just affect ATO reporting. It flows into employee income statements used for tax returns, Centrelink entitlement calculations, and child support assessments. Incorrect data can cause employees to receive wrong Centrelink payments or incorrect child support assessments. The ATO cross-checks STP data against these systems automatically, so discrepancies are flagged quickly.
STP has fundamentally changed the relationship between employers, the ATO, and employees around payroll data.