How Single Touch Payroll Phase 2 works in SAP Payroll and SuccessFactors Employee Central Payroll, the wage type mapping errors behind most STP problems, and what Payday Super changed from July 2026.
By SAVIC SAP Practice · Nov 12, 2026 · 11 min read
SAP STP Phase 2: The Short Answer
SAP STP Phase 2 is the Single Touch Payroll Phase 2 reporting that SAP payroll, on SAP ERP, S/4HANA or SAP SuccessFactors Employee Central Payroll, sends to the ATO each pay event. Since 1 January 2022, each report must break gross pay into components and include income types, employment basis, tax treatment and cessation codes. From 1 July 2026, Payday Super added qualifying earnings and super liability to every report.
SAP supplies the reporting logic. Whether your reports are right depends on how your wage types are mapped and how complete your employee data is. That is what this guide is about. It covers SAP configuration, not tax or payroll law: confirm your STP and Payday Super obligations with your payroll or tax adviser.
What STP Phase 2 Changed for SAP Payroll Teams
Single Touch Payroll began in July 2018 for larger employers. Phase 1 sent the ATO a pay event with year-to-date gross, tax withheld and super. Phase 2, from 1 January 2022, turned that into a much richer record so the ATO could share it with Services Australia and stop asking employers for separate forms.
For an SAP payroll team, the change came down to six things:
- Disaggregation of gross. Paid leave, allowances, overtime, bonuses and commissions, directors' fees and salary sacrifice are reported separately from ordinary gross.
- Income types. Each payment carries a type such as salary and wages, closely held payee, working holiday maker, inbound assignee, foreign employment income or labour hire.
- Country codes. Required for working holiday makers, inbound assignees and foreign employment income.
- Employment basis. Full-time, part-time, casual, labour hire, voluntary agreement, death beneficiary or non-employee.
- Tax treatment codes. A short code describing the tax scale and options applied, such as tax-free threshold, Medicare levy settings and study loans.
- Cessation types. A reason code when employment ends, which replaced the employment separation certificate.
Phase 2 also means employers no longer send TFN declarations to the ATO, and lump sum E letters are no longer needed. The ATO sets out the detail in its STP Phase 2 employer reporting guidelines.
How STP Phase 2 Works in SAP Payroll and Employee Central Payroll
SAP delivers STP Phase 2 inside its Australian payroll localisation. The same engine runs in on-premise SAP Payroll (on SAP ERP HCM or SAP HCM for S/4HANA) and in SAP SuccessFactors Employee Central Payroll, so the logic is identical. Here is the flow:
- Employee data — employment basis, tax treatment inputs, income type and country code — is held on the employee record. In Employee Central Payroll it is replicated from Employee Central.
- Payroll runs and produces wage types for every payment, deduction and allowance.
- Wage type allocation assigns each wage type to an STP Phase 2 field in configuration. It is the single most important piece of STP setup.
- SAP's STP Phase 2 reporting program builds the pay event from the payroll results and the allocation.
- Lodgement sends the file to the ATO through your STP channel, and the response flows back for monitoring.
Two things follow from this. First, SAP cannot know that your "site allowance" is a tools allowance or your "retention payment" is a bonus. You have to tell it. Second, legal changes such as Payday Super arrive through SAP updates, so a system that is behind on support packages is behind on compliance.
STP Phase 2 Wage Type Mapping: Where Most SAP Errors Start
In our experience, almost every STP Phase 2 problem in an SAP system traces back to mapping or master data, not to the SAP code. The usual suspects:
| Problem | What goes wrong | Fix |
|---|---|---|
| Custom wage types never allocated | Amounts fall into ordinary gross or drop out of the report | Review every wage type used in the last 12 months against the STP allocation |
| Allowances in the wrong category | Employees see wrong amounts in myGov; deductions questioned at tax time | Map each allowance to its ATO allowance type, using the award or agreement wording |
| Leave loading and paid leave mixed with ordinary pay | Paid leave under-reported, which affects Services Australia data | Split leave wage types by leave type |
| Missing employment basis or tax treatment | ATO rejects or flags the pay event | Run a master-data completeness check before each pay run |
| Terminations without a cessation type | Former employees chased for separation certificates | Make cessation reason mandatory in the termination process |
| Behind on support packages | Missing Payday Super fields or outdated validation rules | Apply SAP's Australian legal change packages on schedule |
PwC's analysis makes the same point: accurate payroll system mapping is the foundation of correct STP Phase 2 reporting. Mapping is a one-time project, but it decays every time someone adds a wage type for a new enterprise agreement.
Payday Super and STP: The July 2026 Changes in SAP
Payday Super started on 1 July 2026. For SAP payroll teams it changed STP in two ways:
- Timing. Super guarantee is now paid with each pay cycle rather than quarterly, and contributions generally need to reach the fund within seven business days of payday. New employees have a longer first-payment window.
- Data. Every STP report now carries each employee's qualifying earnings and super guarantee liability for the period, so the ATO can match what was due with what funds receive.
The ATO's Small Business Superannuation Clearing House also closed on 1 July 2026. The ATO summarised the changes when the Payday Super legislation was introduced.
In SAP, this means three checks four months in: are the Payday Super legal changes applied, is the qualifying earnings figure derived from the right wage types, and does your super payment run, whether a clearing house file or SuperStream integration, now run every pay cycle rather than every quarter?
SAP HCM vs SAP SuccessFactors Employee Central Payroll for STP
Australian companies on SAP payroll usually face a second question alongside STP: where should payroll live after 2027?
- SAP ERP HCM (on ECC). Mainstream maintenance ends in 2027. STP keeps working, but the platform has a clock on it.
- SAP HCM for S/4HANA (H4S4). The on-premise path, with a longer support horizon; check SAP's current maintenance dates for your release. Your STP configuration largely carries over.
- SAP SuccessFactors Employee Central Payroll. The cloud path. Same payroll engine and STP logic, with SAP hosting the system and delivering legal updates. Employee data comes from Employee Central.
Whichever you pick, the STP wage type mapping is the asset to protect. A migration is the best moment to clean it up and the worst moment to discover it was wrong. Our SAP SuccessFactors implementation guide covers the wider programme.
What We See in SuccessFactors Payroll Projects
SAVIC's SuccessFactors practice works mainly in India and the Middle East. Payroll localisation rules differ by country, but the delivery lessons transfer directly to STP:
- Employee Central first. Always. In Employee Central Payroll, STP fields such as employment basis start life in Employee Central. If the core HR data is wrong, STP will be wrong.
- Parallel runs prove the mapping. Run old and new payroll side by side for at least two pay cycles and compare STP-level totals, not just net pay.
- Year-to-date carries the history. When payroll moves systems mid-year, plan how opening year-to-date amounts are loaded so STP figures stay continuous.
- Someone owns the mapping. A named person in payroll should approve every new wage type's STP allocation before it is used.
That is the base we write from. Not press releases.
STP Phase 2 Health Check: 6 Steps for SAP
- List every wage type used in the last 12 months, including custom ones.
- Check each STP allocation against the ATO's Phase 2 categories and your awards or agreements.
- Run a master-data completeness report for employment basis, tax treatment, income type and country code.
- Confirm Payday Super readiness with your payroll adviser: legal changes applied, qualifying earnings mapped and super paid each cycle.
- Reconcile year-to-date STP figures to payroll results for a sample of employees, including leavers.
- Set a change rule so no new wage type goes live without an STP allocation sign-off.
Why SAVIC
SAVIC Technologies has delivered 125+ S/4HANA Cloud projects for customers in 15+ countries. In Australia, we are SAVIC PTY LTD, registered at 34 Sampson Road, Mitchell Park SA 5043 (+61 449 799 134), with delivery by SAVIC's global SAP team in India and Singapore.
We look at STP as part of your wider SAP landscape: SAP SuccessFactors and Employee Central Payroll, ECC to S/4HANA migration and ongoing SAP support. See our SAP services in Australia, read our guide to SAP Peppol e-invoicing in Australia, or compare the top SAP implementation partners in Australia.
Frequently Asked Questions
What is STP Phase 2?
STP Phase 2 is the expanded version of Single Touch Payroll that the ATO introduced from 1 January 2022. Instead of one gross figure, employers now report each pay event with gross pay broken into components, an income type, an employment basis, a tax treatment code and, when someone leaves, a cessation reason. The extra detail lets the ATO share data with Services Australia and pre-fill tax returns accurately.
Is STP Phase 2 mandatory?
Yes. STP Phase 2 reporting has been mandatory since 1 January 2022, with deferrals granted to software providers rather than individual employers. Those deferrals have long expired, so every employer using STP-enabled payroll, including SAP payroll, must now report in the Phase 2 format. Phase 1 reports are no longer accepted for current pay events.
Does SAP support Single Touch Payroll Phase 2?
Yes. SAP delivers STP Phase 2 as part of its Australian payroll localisation, used by both SAP Payroll on ERP or S/4HANA and SAP SuccessFactors Employee Central Payroll. The standard solution includes the Phase 2 report generation and the wage type allocation used to place each pay item in the right STP field. Your job is to keep support packages current and to map your own wage types correctly.
What is disaggregation of gross in STP Phase 2?
Disaggregation means splitting gross pay into separate amounts instead of reporting one total. Phase 2 reports paid leave, allowances, overtime, bonuses and commissions, directors' fees, salary sacrifice and certain lump sums separately from ordinary gross. In SAP this depends entirely on each wage type being allocated to the correct STP category, which is where most errors start.
What changed in STP for Payday Super from 1 July 2026?
From 1 July 2026, employers must pay super with each pay cycle, and contributions generally need to reach the employee's fund within seven business days of payday. STP reports must also include each employee's qualifying earnings and super guarantee liability for the pay period. The ATO Small Business Superannuation Clearing House closed on the same date, so SAP payroll teams have had to update both payment processes and STP data.
What is the difference between SAP Payroll and SAP SuccessFactors Employee Central Payroll for STP?
Both use the same SAP payroll engine and the same Australian STP logic, so the Phase 2 rules and wage type mapping work the same way. The difference is where the system runs and who maintains it. Employee Central Payroll is SAP-hosted and receives legal changes through SAP's update cycle, while on-premise SAP Payroll needs your team or partner to apply support packages and notes on time.
How do I fix STP Phase 2 errors in SAP?
Start with the ATO rejection or the year-to-date mismatch, then trace it back to the wage types feeding that STP field. Most errors come from wage types allocated to the wrong category, missing employment basis or tax treatment data on the employee record, or support packages that are behind. Correct the mapping or master data, then let the next pay event or an update event correct the year-to-date figures.
How long does an SAP STP Phase 2 review take?
For a single Australian payroll area, the length of a review of wage type mapping, employee master data and recent STP submissions depends on how many wage types and payroll areas are in scope. Multiple payroll areas, enterprise agreements with many allowances, or a recent migration from another payroll system add time. The output should be a corrected mapping, a list of master-data fixes and a reconciliation of year-to-date amounts.
Last reviewed: 12 Nov 2026 by SAVIC SAP Practice
Frequently Asked Questions
What is STP Phase 2?
STP Phase 2 is the expanded version of Single Touch Payroll that the ATO introduced from 1 January 2022. Instead of one gross figure, employers now report each pay event with gross pay broken into components, an income type, an employment basis, a tax treatment code and, when someone leaves, a cessation reason. The extra detail lets the ATO share data with Services Australia and pre-fill tax returns accurately.
Is STP Phase 2 mandatory?
Yes. STP Phase 2 reporting has been mandatory since 1 January 2022, with deferrals granted to software providers rather than individual employers. Those deferrals have long expired, so every employer using STP-enabled payroll, including SAP payroll, must now report in the Phase 2 format. Phase 1 reports are no longer accepted for current pay events.
Does SAP support Single Touch Payroll Phase 2?
Yes. SAP delivers STP Phase 2 as part of its Australian payroll localisation, used by both SAP Payroll on ERP or S/4HANA and SAP SuccessFactors Employee Central Payroll. The standard solution includes the Phase 2 report generation and the wage type allocation used to place each pay item in the right STP field. Your job is to keep support packages current and to map your own wage types correctly.
What is disaggregation of gross in STP Phase 2?
Disaggregation means splitting gross pay into separate amounts instead of reporting one total. Phase 2 reports paid leave, allowances, overtime, bonuses and commissions, directors' fees, salary sacrifice and certain lump sums separately from ordinary gross. In SAP this depends entirely on each wage type being allocated to the correct STP category, which is where most errors start.
What changed in STP for Payday Super from 1 July 2026?
From 1 July 2026, employers must pay super with each pay cycle, and contributions generally need to reach the employee's fund within seven business days of payday. STP reports must also include each employee's qualifying earnings and super guarantee liability for the pay period. The ATO Small Business Superannuation Clearing House closed on the same date, so SAP payroll teams have had to update both payment processes and STP data.
What is the difference between SAP Payroll and SAP SuccessFactors Employee Central Payroll for STP?
Both use the same SAP payroll engine and the same Australian STP logic, so the Phase 2 rules and wage type mapping work the same way. The difference is where the system runs and who maintains it. Employee Central Payroll is SAP-hosted and receives legal changes through SAP's update cycle, while on-premise SAP Payroll needs your team or partner to apply support packages and notes on time.
How do I fix STP Phase 2 errors in SAP?
Start with the ATO rejection or the year-to-date mismatch, then trace it back to the wage types feeding that STP field. Most errors come from wage types allocated to the wrong category, missing employment basis or tax treatment data on the employee record, or support packages that are behind. Correct the mapping or master data, then let the next pay event or an update event correct the year-to-date figures.
How long does an SAP STP Phase 2 review take?
For a single Australian payroll area, the length of a review of wage type mapping, employee master data and recent STP submissions depends on how many wage types and payroll areas are in scope. Multiple payroll areas, enterprise agreements with many allowances, or a recent migration from another payroll system add time. The output should be a corrected mapping, a list of master-data fixes and a reconciliation of year-to-date amounts.
