Single Touch Payroll Phase 2 and Payroll System Implementation: A Go-Live Checklist

payroll system implementation

By Natasha Silveira | 25 October 2026 | 12 min read

TL;DR

  • Single Touch Payroll Phase 2 splits gross pay into itemised income types, so every pay code needs a mapping.
  • Run a parallel pay run before go-live, not after your first real one.
  • Payday Super means super must reach each fund within 7 business days of payday.
  • Compare STP reports with your payroll register after every early pay run, then finalise by 14 July.
  • Give one person ownership of go-live day and sign off each step.

Your new payroll system is booked to go live on the first pay run next month. The pay codes are half mapped, nobody has tested the super file, and the old provider’s contract ends on Friday. This is where Single Touch Payroll Phase 2 errors begin. A payroll system implementation that skips the checks sends wrong figures to the ATO on every pay run until someone notices. This go-live checklist shows what to set up, test and confirm first. For help with the switch, see VeiraMal’s outsourced payroll services and payroll system support.

Single Touch Payroll Phase 2 go-live checklist, VeiraMal payroll discovery call CTA
Planning a payroll system switch? Book a free discovery call before your go-live date.

What Single Touch Payroll Phase 2 means for a payroll system implementation

Single Touch Payroll Phase 2 is the ATO’s expanded payroll reporting standard. Instead of one gross figure, your software sends gross pay split into set categories, along with employment basis, tax treatment and cessation details. Your system builds those fields from your pay codes, so the setup decides whether the reports are right.

The ATO’s guidance on disaggregation of gross lists the categories you report separately: gross, paid leave, allowances, overtime, bonuses and commissions, directors’ fees, lump sum W and salary sacrifice. Paid leave has its own types, from parental leave to unused leave paid on termination. Unpaid leave isn’t reported.

Phase 2 isn’t new, but a new system resets the work. Every code in the old payroll was set up once, often years ago, by someone who has since left. When you move to new software, those decisions get made again. Make them on purpose, and write them down.

Employment basis matters too. Each employee needs to be recorded as full-time, part-time or casual, and the new system has to carry that through to the report. When an employee leaves, you also report why. If the data export from your old system is patchy, you’ll find out here.

Why payroll system implementation goes wrong at go-live

Most go-live problems aren’t dramatic. They are small setup errors that repeat every fortnight. A pay code sits in the wrong category. An opening balance is a week out. A fund number has a typo. None of it looks serious until the figures reach the ATO, or an employee’s payslip.

Confidence is part of the problem. The Workforce Pulse 2026 survey of 510 Australian business owners, run by Citation Group, found that 87% were confident their payroll reflected the right award rates and entitlements. Yet 42% had found a payroll error at some point, and 58% ran payroll, HR and safety on platforms that don’t talk to each other. Confidence without checks isn’t a control.

Four causes show up again and again when a new system goes live:

  • Copied pay codes: codes carried across from the old system with no review.
  • Late balances: year-to-date and leave balances loaded after the first pay run.
  • Untested super: fund details and payment files never checked end to end.
  • No owner: nobody is clearly responsible on go-live day.

Each one is a setup problem, not a pay run problem. Our guide to the 7 STP Phase 2 errors that trigger an ATO review shows how these mistakes appear in your reports. Fix the setup first and most of those errors never happen.

Single Touch Payroll Phase 2 go-live checklist: before you switch on

Work through these steps in order. Each one is short on purpose, so you can assign it to a named person and tick it off.

  1. Name one person who owns go-live and signs off each step.
  2. Export a full employee list with tax, super and employment basis details.
  3. Confirm each employee’s employment basis: full-time, part-time or casual.
  4. Map every pay code to an STP income type.
  5. Check salary sacrifice, allowance and leave codes line by line.
  6. Load year-to-date and leave balances from the old system.
  7. Validate super fund details and the payer bank account.
  8. Confirm your software provider is nominated and connected to the ATO.
  9. Run a parallel pay run and compare it with the old result.
  10. Set a cut-off date and tell staff when payslips will change.

Step one gets skipped most often, and it matters most. When five people each assume someone else checked the mappings, nobody checked them. Pick one person, give them authority to delay go-live, and make sure the owner has read access to both systems.

Step eight is a quiet trap. For cloud software, the ATO’s STP reporting issues and errors page explains that you must nominate your software provider in Access Manager, and that the software service ID must match your ABN. If that’s missing, your first report is rejected before it reaches the ATO. Sort it a week early, not on pay day.

Before go-live vs the first pay runs: what to set up and what to check

Set up before go-live

✓

Pay code mapping – every pay code linked to the right STP income type before the first pay run.

✓

Opening balances – year-to-date amounts and leave balances loaded and checked against the old system.

✓

ATO connection – your software provider nominated and authorised for your ABN.

Check in the first pay runs

✓

STP against the register – reported gross matches the payroll register for every employee.

✓

Super on time – payments reach each fund within 7 business days of payday.

✓

Payslips – staff see the right pay, leave and super lines, and queries get answered fast.

Mapping pay codes to Single Touch Payroll Phase 2 income types

Mapping is the heart of payroll system implementation. Every code in your system, from base pay to the tool allowance, must land in one ATO category. Here are the spots where mapping goes wrong most often.

Gross, overtime and allowances

Overtime and shift penalties look alike on a payslip but sit in different places in the report. The ATO says shift penalties are reported under gross, not overtime. A system that sends them as overtime reports the wrong category on every shift. Allowances must be reported separately too, so don’t fold them into gross to keep the code list short.

Salary sacrifice

For employees with an effective salary sacrifice arrangement, you report the pre-sacrifice amount and report the sacrifice amount separately. A system that sends only the lower, post-sacrifice figure understates gross pay. Test this with one real sacrificing employee before go-live, and check the super calculation at the same time.

Paid leave and lump sum W

Paid leave is split into types: other, parental, workers’ compensation, ancillary and defence, cash out in service, and unused leave on termination. Check that your leave codes map to the right type. Lump sum W is its own category, and return-to-work payments that used to be reported as gross now belong there.

Terminations

When someone leaves, the system needs a cessation reason and the right payment categories for the final pay. Run a test termination in the new system before the real one lands in the middle of your go-live fortnight.

VeiraMal payroll system implementation and payroll audit services overview
VeiraMal covers payroll processing, audits and compliance, and payroll systems.

Go-live numbers worth writing on the whiteboard

7

business days for super to reach the employee’s fund after each payday

3

business days a super fund has to allocate or reject a payment

14 July

yearly deadline for your STP finalisation declaration

24 hrs

minimum wait between full file replacements

Source: ATO, Payday Super and Single Touch Payroll guidance

Payroll system implementation and Payday Super: the dates that matter

Payday Super applies to earnings paid from 1 July 2026. The ATO’s guidance on paying super says contributions must reach the employee’s fund, with enough information to allocate them, within 7 business days of each payday. A fund then has 3 business days to allocate or reject the payment. If a payment is rejected, the 7-day deadline doesn’t move.

That changes what your new system must do. It needs to calculate super on qualifying earnings, which include ordinary time earnings, commissions and salary sacrifice amounts that would otherwise be superable. It then reports year-to-date qualifying earnings and super liability through STP. The ATO’s Payday Super checklist for employers also notes that the Small Business Superannuation Clearing House can’t be used for payments on or after 1 July 2026.

Four checks belong on your go-live list for super:

  • Software readiness: ask your provider in writing when Payday Super features are live.
  • Payment method: confirm how contributions reach each fund and how fast.
  • Fund details: validate every member number and fund identifier before the first pay run.
  • Rejections: decide who monitors failed payments and fixes them the same week.

If super is late, unpaid or sent to the wrong fund, the super guarantee charge can apply. The ATO says it can include the unpaid amount, notional interest and an administrative amount. That’s a cost you can avoid with an afternoon of testing.

Timing the switch matters as much as the setup. Cutting over mid-month can leave one pay event in each system. Our article on how to switch payroll providers without breaking a pay run walks through a six-step migration, including how to choose a clean cut-off.

“

Outsourcing my HR to the highly professional Natasha Silveira at VeiraMal saved us about $30k annually and gave me back hours every week I was spending on compliance I didn’t understand.

S

Steve

properT Network

Run a parallel pay run before go-live

A parallel run is the cheapest insurance you can buy. You process the same pay period in the old and the new system, but only one of them reports to the ATO and pays staff. Then you compare the results person by person.

Compare gross pay, tax withheld, super, leave accrual and net pay for every employee, not a sample. Where numbers differ, find the cause before you decide which system is right. The old one may be the one that’s wrong. Many businesses discover a long-standing award error at exactly this point.

That discovery carries real weight. The Fair Work Ombudsman reported that it recovered $358 million for more than 249,000 underpaid workers in 2024-25. If your parallel run exposes an underpayment, fix it and speak to an adviser about back pay. An independent payroll audit and award compliance check is a sensible step when the differences are large or you don’t know why they exist.

If you want a quick read on your situation, call VeiraMal directly or send a message through the contact form. We will tell you plainly whether your go-live plan holds up.

Switching payroll systems this quarter?

A short conversation with VeiraMal will show where your go-live risk sits, before the first real pay run goes out.

Book Your Free Discovery Call

Free Download: Payroll System Go-Live Checklist

A one-page list of the STP Phase 2, Payday Super and parallel run checks to complete before you switch payroll systems.

Download Free Checklist

Quick scorecard: How ready is your payroll go-live?

Tick every item that applies to your business.

Choosing between software, a provider and full outsourcing

Not every business needs a new system. Some need a better process on the system they already own, and some are better off handing payroll to a provider altogether. The right answer depends on headcount, award complexity and who in your team actually has time to run the pay.

Software alone suits a small team with simple pay and someone who knows the awards. A provider suits a business that wants the work done to a standard without hiring in-house. Our comparison of payroll software, business payroll services or full outsourcing sets out the trade-offs in plain terms.

First pay runs after go-live: what to check

Go-live isn’t the finish line. The first two or three pay runs are where setup mistakes show up, so treat them as part of the project. The ATO requires your STP report to be submitted on or before payday, so plan your check for the day before, not the day after.

  • Compare STP with the register: reported gross for each employee should match your payroll register.
  • Watch super payments: confirm each one reaches the fund and fix any rejection quickly.
  • Read real payslips: ask two or three staff whether pay, leave and super lines make sense.
  • Keep the old system: staff will ask about past payslips, and you will need the history.

If a report needs correcting, be careful. The ATO notes that a full file replacement can only be submitted once within a 24-hour period, so get the correction right the first time. For error codes you can’t clear, contact your software provider.

How VeiraMal Works

1

Discovery Call

A free conversation about your payroll system, your go-live date and where the risk sits.

2

Threshold Review

Pay codes, mappings and super setup checked against your actual workforce.

3

Ongoing Support

Advice on call when the first pay runs raise questions.

Book a VeiraMal discovery call for your Single Touch Payroll Phase 2 go-live
Book a free discovery call to test your payroll go-live plan.

Year-end finalisation after a mid-year system switch

A system switch during the financial year leaves two sets of figures to reconcile. The ATO’s STP finalisation guidance requires a finalisation declaration by 14 July each year, or 30 September for closely held payees. Before you lodge, check that every employee’s year-to-date amounts are correct.

Lodge a declaration for every employee you paid and reported through STP that year, including terminated employees and casuals. If you changed software or payroll IDs part-way through, the ATO says to zero out amounts in the old software or notify it of your previous business management software ID. Skip that step and the same pay may appear twice.

Put the reconciliation on the calendar when you plan the go-live. In the last week of June, compare the year-to-date figures in both systems against your records. It takes an hour in June and saves a long phone call in July.

Frequently asked questions

What is Single Touch Payroll Phase 2?

Single Touch Payroll Phase 2 is the ATO’s expanded payroll reporting standard. Instead of one gross figure, your software reports gross pay split into categories such as overtime, allowances, paid leave, bonuses and salary sacrifice. It also reports employment basis, tax treatment and the reason an employee leaves. Your payroll system builds these fields from your pay codes, so correct setup matters on day one.

What should a payroll system implementation go-live checklist include?

A good go-live checklist covers a named owner, a clean employee data export, employment basis for each person, pay code mapping to STP income types, opening balances, super fund validation and your software’s ATO connection. It should also include a parallel pay run, a cut-off date and a plan for checking the first reports. Keep every step short, assign it to a person and tick it off in writing.

Should I run my old and new payroll systems side by side?

Yes, for at least one pay cycle. Run the same pay period in both systems and compare gross pay, tax, super and leave for every employee. Chase each difference until you know the cause. Do not report from both systems for the same pay event. Treat the old system as your answer key, and keep it available for queries after go-live.

How does Payday Super affect a payroll system implementation?

From 1 July 2026, super must reach each employee’s fund within 7 business days of payday, so your new system needs to calculate super on qualifying earnings and report your year-to-date qualifying earnings and super liability through STP. Check the payment method too, because the Small Business Superannuation Clearing House can’t be used for payments made on or after that date. Confirm readiness with your software provider.

Do I need to finalise STP again if I change software mid-year?

You still make one finalisation declaration for each employee, by 14 July for most employers. Before you do, check that year-to-date amounts are correct. The ATO says that if you changed software or payroll IDs during the year, you should zero out amounts in the old software or tell the ATO your previous business management software ID. This avoids the same pay being counted twice.

A tested go-live protects every pay run that follows. If you would like help with Single Touch Payroll Phase 2 setup, super testing or a parallel run, explore VeiraMal’s payroll services for Australian businesses and we will match the support to your workforce and your timeline.

Going Live Soon? Get The Payroll Checks Done First

VeiraMal reviews your headcount, contracts, policies and termination process against the obligations that actually apply to your size. Businesses in Melbourne, Sydney and Hobart.

Book Your Free Discovery Call

Melbourne: Level 2, 480 Collins Street, VIC 3000
Sydney: Level 26, 44 Market Street, NSW 2000
Hobart: Level 6, Reserve Bank Building, 111 Macquarie Street, TAS 7000
info@veiramal.com

Thoughts from an HR expert

Stay informed with Tash Talks

Explore our monthly blogs for expert insights into industry trends and legislative updates, including HR advice Australia.

Book a free consultation

Interested to see how our HR solutions can propel your business to new heights?