📌 Quick answer: STP Phase 2 compliance isn’t a one-off setup — it depends on three things holding true at the same time: (1) your payroll software is genuinely configured for Phase 2, not just activated, (2) employee master data is complete and current, and (3) year-end finalisation and error corrections are handled on time. Use the checklist below to spot gaps in your own setup.
If you are asking, “Am I STP Phase 2 compliance?”, the best answer is not a simple yes or no. In 2026, compliance is less about whether the reform exists and more about whether your payroll data, pay categories, software settings and year-end finalisation process are all working as intended.
STP Phase 2 began on 1 January 2022, and most Australian employers should already be reporting under it. Even so, payroll teams still uncover gaps years later, especially after software upgrades, entity restructures, payroll staff changes, Award updates or a rushed implementation during an earlier digital service provider transition. A business can be lodging STP and still have Phase 2 errors sitting in employee records or pay item mapping.
Compliance is now a data-quality issue as much as a software issue.
What STP Phase 2 compliance means in 2026
Under STP, employers report employee tax and super information to the Australian Taxation Office each time employees are paid through STP-enabled payroll software. Phase 2 expanded that reporting. Instead of only sending broad pay and tax totals, employers may also need to report more detailed payroll attributes, including tax treatment codes, income types, employment basis, country codes and cessation details.
The practical effect is clear. Payroll systems now need to tell a more accurate story about each employee and each payment. That matters not only for ATO reporting, but also for how information flows across government agencies.
A business is more likely to be compliant when three things are true at the same time:
- the payroll platform is genuinely configured for STP Phase 2
- employee master data is complete and current
- year-end finalisation and corrections are handled on time
STP Phase 2 compliance checklist for Australian employers
A short checklist can quickly show where to focus your review. If several items below are uncertain, it is a strong sign that your STP Phase 2 setup needs attention.
| Compliance area | What to confirm | Why it matters |
|---|---|---|
| STP-enabled software | Your payroll software is activated for Phase 2 and your digital service provider setup is current | A business cannot meet Phase 2 requirements if the product is still mapped to older reporting fields |
| Transition status | Any past deferral, delayed transition or concessional reporting arrangement has ended and your reporting is now fully updated | Historic transition settings can leave partial configurations behind |
| Employee tax setup | Each employee has the correct 6-character tax treatment code | This affects withholding treatment and replaces the need to separately send a TFN declaration copy in many cases |
| Employee classification data | Employment basis, income type and any relevant country code fields are accurate | These fields are part of the expanded reporting dataset |
| Pay item mapping | Gross earnings are correctly split into the required reporting categories | Phase 2 expects more detailed reporting rather than one broad gross amount |
| Termination reporting | Cessation date and cessation reason are captured properly for employees who leave | Incorrect exit data can create reporting issues and confusion for employees |
| Software migration history | Previous payroll IDs or Business Management Software IDs are recorded where relevant | This can reduce duplicate income statements after payroll system changes |
| Child support reporting | Garnishees and deductions are reported where your process and software support this | Phase 2 can reduce separate reporting to the Child Support Registrar |
| Correction process | Errors are fixed within 14 days or by the next regular pay event, where that timing applies | Prompt correction supports accurate employee income statements |
| Year-end finalisation | Finalisation declarations are completed by 14 July | Employees rely on finalised data for tax readiness |
Payroll software and DSP readiness for STP Phase 2
The first question is not whether your software vendor says it supports Phase 2. The real question is whether your payroll file, settings and pay items were fully converted and checked when Phase 2 was switched on.
That distinction catches many businesses out. A product may be compliant in theory, while the employer configuration remains incomplete. This often happens when old payroll categories were carried over, custom earning codes were left unmapped, or employee defaults were copied from legacy records without review.
If your organisation changed payroll systems, changed entities, or adjusted payroll IDs during the past few years, review that history closely. STP Phase 2 can include previous identifiers to help prevent duplicate income statements appearing in ATO online services. That is especially useful after a migration.
Common warning signs include:
- old pay items still bundled into one gross bucket
- tax treatment codes left on defaults
- employee records with blank country fields where those fields are relevant
- duplicate or confusing income statement outcomes after a software change
Employee data fields required for STP Phase 2
A strong Phase 2 setup starts with employee master data. The ATO’s expanded reporting model expects more detail, and payroll teams need that detail captured at onboarding, reviewed during employment, and updated when circumstances change.
This is where compliance often becomes operational rather than technical. A payroll officer cannot report a valid field that has never been collected, and a system cannot interpret a tax position correctly if the underlying employee data is incomplete.
Key data points to review include:
- Tax treatment code: the 6-character code that reflects withholding factors for the employee
- Employment basis: the employment classification your software requires for Phase 2 reporting
- Income type: the reporting category that applies to the worker’s arrangement
- Country code: relevant where an employee’s reporting position requires this field
- Cessation details: the correct date and reason when employment ends
- Previous payroll identifiers: useful when moving records from one payroll environment to another
The tax treatment code deserves special attention. If it is wrong, withholding outcomes and reporting accuracy can both be affected. Phase 2 made this field central to the reporting model, and it is one of the most useful checkpoints when reviewing whether a payroll file is genuinely compliant.
Employment basis and income type also deserve more respect than they often receive. They can look like simple dropdown choices, yet they influence how the employee is represented in STP reporting. For businesses with mixed workforces, multiple legal entities, labour-intensive operations, or unusual engagement models, these fields should be validated rather than assumed.
Disaggregation of gross and pay category mapping in STP Phase 2
One of the biggest changes in Phase 2 is the disaggregation of gross. In plain terms, this means employers may need to report payment components with more detail instead of sending one broad gross figure for everything.
This matters because different payment types can be treated differently for government reporting purposes. If every earning code flows into a single gross category, the STP file may technically lodge while still producing a poor reporting outcome.
Payroll teams should look closely at how allowances, leave payments, bonuses, commissions, overtime and similar items are mapped in the system. The right setup depends on the payroll platform and the nature of the payment, so a blanket approach is rarely safe.
A quick review usually starts with three questions:
- Are any custom pay codes sitting in generic gross when they should be separately identified?
- Do Award or EBA-based pay items still match current payroll categories?
- Has any new earning or deduction code been added without checking its STP reporting treatment?
For employers covered by modern Awards or enterprise agreements, this area deserves extra care. Complex penalty structures, leave loading, varied allowances and roster-driven earnings can create mapping errors if payroll categories were built for convenience rather than reporting accuracy.
Year-end finalisation deadlines and error correction under STP
Even with accurate pay-event reporting during the year, STP work is not finished until finalisation is done properly. Employers need to make a finalisation declaration by 14 July each year so that employee income information becomes tax ready.
This date still matters in 2026. Businesses sometimes assume STP has replaced all year-end obligations. It has changed them, not removed them.
There is also a timing expectation around fixing mistakes. Where an STP reporting error is found, it should generally be corrected within 14 days or by the next regular pay event. That gives payroll teams a practical window, but it also means errors should not sit unresolved for months.
Useful year-end checkpoints are:
- Before finalisation: reconcile year-to-date wages, PAYG withholding and reportable payroll categories
- By 14 July: lodge the finalisation declaration for relevant employees
- After an error is found: update the payroll records and submit the correcting STP report within the required timeframe
Ceased employees can often be finalised earlier, during the financial year, rather than waiting until July. That can reduce admin later and give former employees earlier access to tax-ready information.
Internal payroll controls that support STP Phase 2 compliance
A compliant payroll file is easier to maintain when the process around it is disciplined. Good controls do not need to be complicated, but they do need to be consistent.
Start with ownership. Someone should be responsible for employee onboarding data, someone for pay item mapping, and someone for the year-end STP reconciliation. In smaller businesses, one person may handle all three, though the review should still be independent where possible.
A strong internal routine often includes:
- quarterly checks of employee master data fields
- review of new or changed earning and deduction codes before first use
- reconciliation of payroll categories ahead of 30 June
- documented sign-off for corrections and finalisation declarations
If your payroll is affected by Awards, EBAs, employee mobility, child support deductions or frequent software changes, a periodic payroll health check can be a smart safeguard. It is much easier to fix mapping, classification and identifier issues before year-end than after employees start asking why their income statement looks wrong.
For many businesses, the most practical test is this: if the payroll manager changed tomorrow, would another experienced person be able to review the STP setup and clearly see how the compliance decisions were made?
If the answer is no, the process may still be too dependent on memory and workarounds.
