Setting up payroll badly is one of the fastest ways to create avoidable ATO problems.
If you are hiring staff for the first time, changing software, or trying to fix a messy payroll file, Single Touch Payroll setup Australia is not an admin task. It is a compliance job. The good news is that once the setup is done properly, day-to-day reporting becomes much easier.
Key Takeaways:
- STP requires employers to report payroll information to the ATO through STP-enabled software each pay run.
- For small businesses, getting setup right comes down to software choice, clean employee data, correct pay item mapping, and a proper ATO connection.
- STP Phase 2 adds more detailed reporting categories, so old payroll item setups often need review.
- The most common failures are not technical. They come from incorrect business details, incomplete employee records, and wrong payroll mappings.
Understanding Your Single Touch Payroll Obligations
Single Touch Payroll is the ATO’s payroll reporting system. Instead of waiting until year end to report wages and tax information, employers send payroll data through STP-enabled software when they process a pay run.
For the original rollout, STP became mandatory for large Australian businesses with 20 or more employees on 1 July 2018, and for small businesses with 1 to 19 employees on 1 July 2019 according to this STP compliance guide for small business owners. That same guide notes small businesses had a transition period until 30 September 2019.
What STP reports
At a practical level, STP reports payroll information such as:
- Employee details
- Gross wages
- PAYG withholding
- Superannuation contributions
Employees can access year-to-date information through ATO online services, which is one reason the old payment summary process changed.
Who needs to use it
If you employ staff, you should assume STP applies unless a specific concession or exemption clearly covers you. The common small business trap is assuming a very small headcount means the rules do not apply. That is usually wrong.
Some limited arrangements have existed for micro-employers and closely held payees, but these are not broad opt-outs. They are reporting concessions with conditions and dates attached.
Practical rule: If you run payroll, set up STP from the start rather than trying to work around it.
A second trap is treating STP as separate from super setup. It is not the same obligation, but the records need to line up. If you need a refresher on super compliance while setting up payroll, review these super guarantee obligations for employers.
Why this matters early
This is not paperwork you can “sort out later”. Errors at setup flow into every pay run after that. Once bad categories, wrong employee details, or incomplete payroll items are embedded, cleanup takes longer than doing it properly the first time.
Decoding STP Phase 2 and Reporting Deadlines
Many business owners understand basic STP, then get stuck when they hit STP Phase 2. The reason is simple. Phase 2 asks for more detail, not just a total payroll figure.
What changed under Phase 2
Phase 2 expanded reporting to include more detailed payroll classifications. According to the verified STP guide, the rollout from 2022 added requirements such as:
- Disaggregated gross payments
- Detailed allowances
- Overtime
- Income type codes such as SAW for salary and wages and CHP for closely held payees
That extra detail matters because your software needs the right reporting category attached to each pay item. If an allowance, overtime item, or deduction sits under the wrong label, the submission may still go through, but the reporting can still be wrong.
What this means in real life
For a small business, Phase 2 affects three setup areas:
- Pay item mapping Old legacy wage categories often need review.
- Employee classification Standard employees, working holiday makers, and closely held payees do not always report the same way.
- Allowance treatment Flat “miscellaneous” items are where many files become messy.
Good setup works because the payroll chart is clean. Most STP problems I see start with untidy pay items that were acceptable for internal bookkeeping but not detailed enough for ATO reporting
STP reporting requirements at a glance
| Reporting frequency | Each pay run |
| What to report | Wages, PAYG withholding, and super information |
| Deadline | On or before payday |
| End of year step | Finalise payroll information through your software |
Check current ATO guidance before acting, especially if your payroll includes unusual employee types or you are correcting historical data.
Deadlines that small businesses should remember
The broad pattern is straightforward. You process payroll, then report through STP as part of that pay cycle. You do not leave it until the end of the quarter just because PAYG withholding or super payments may have separate payment schedules.
Small businesses commonly confuse payment deadlines with reporting deadlines. STP reporting follows the pay run rhythm. Your software should be set up to support that routine every time.
The Complete STP Setup Process for Small Businesses
Most payroll setups fail before the first lodgement. Not because the software is poor, but because the file is only half-prepared.
Start with the file, not the lodgement button
Before you click opt-in or register, check the business record inside the software. In MYOB, the setup process starts in the Payroll command centre under Payroll Reporting. The critical point is that your ABN, TFN, business name, and address need to match ATO records exactly, as explained in this MYOB STP setup guide.
If the business identity does not match, the connection stage becomes harder than it should be.
Then review every employee card. Full legal name, residential address, state, postcode, and TFN all matter. The same guide notes that TFN mismatches account for 15 to 20% of initial setup errors.
Choose software that fits how you pay people
For most small businesses, the practical shortlist is Xero, MYOB, or QuickBooks. All are used for STP-compliant reporting.
What matters more than brand preference is this:
- Can the software handle your pay cycle cleanly?
- Can you map earnings and allowances properly for Phase 2?
- Can your bookkeeper or accountant support it easily?
If your business has simple weekly or fortnightly wages, any of the major platforms can work. If you have awards, varied allowances, multiple leave types, or family members on payroll, I would lean toward the system your adviser knows well enough to troubleshoot quickly.
Connect to the ATO properly
For Xero, the usual path is Payroll, then Single Touch Payroll, then opt-in and register. The setup process connects through myGovID or AUSkey and enables pay run submissions once registration is complete, based on the Xero setup walkthrough in the verified data.
For MYOB, the initial declarer needs to connect first. Additional users then authorise themselves separately.
This is one of those small details that causes unnecessary delay. A business owner assumes anyone with admin access can lodge. The software may not accept that until the declarer arrangement is set correctly.
Do not delegate the first connection casually. Choose the person who will remain responsible for payroll reporting, or make sure authority is set up cleanly from day one.
Map pay items before the first live pay run
Compliance-first setup is essential here.
Xero’s STP Phase 2 wizard flags legacy pay items. According to verified data, those legacy items caused many transition failures in 2022 in Xero-related transitions. In MYOB, the same setup discipline applies. You need clean ATO reporting categories for income types and payroll items.
Typical mapping work includes:
- Salary and wages under the correct income type
- Allowances under the right allowance category
- Overtime separated correctly
- Deductions and PAYG linked properly
- Super obligations reflected correctly in payroll settings
If you import an old chart of payroll categories without reviewing it, Phase 2 setup tends to become patchwork.
Run a test before processing real payroll
A test pay run is one of the highest-value steps in the whole setup.
The MYOB guidance recommends it, and I agree. A test submission helps you identify unallocated income codes, incorrect employee data, and odd pay item behaviour before staff are paid.
This is also the point where you should reconcile year-to-date balances if you are migrating mid-year. Historical migration may include prior YTD payments, PAYG amounts, leave balances, and super obligations. If those opening figures are wrong, your STP reporting will be wrong even if every future pay run is processed perfectly.
Worked example for a small café
Take a small café with 3 employees, weekly wages of $3,000, and $450 withheld for PAYG.
The practical STP flow looks like this:
- The owner runs payroll in Xero or MYOB
- Gross wages are calculated for the week
- PAYG withholding is applied
- Super settings are included in the payroll records
- The pay run is lodged through STP on or before payday
- Year-to-date figures update in the employee and ATO records
That is the value of proper setup. Once the file is configured, each pay run becomes a repeatable process rather than a fresh compliance exercise.
For a broader pre-payroll admin check before hiring or first wages, this payroll registration checklist for Australia is a useful companion.
Copy and use this STP checklist
- Software selected Confirm you are using STP-enabled payroll software such as Xero, MYOB, or QuickBooks.
- Business details verified Make sure the ABN, TFN, legal name, and address match ATO records.
- Employee records completed Check names, TFNs, addresses, and core payroll data.
- Pay items reviewed Map wages, allowances, overtime, deductions, and income types correctly.
- ATO connection established Complete the registration and declarer setup.
- Opening balances checked If migrating mid-year, verify YTD figures and leave balances.
- Test submission processed Review and fix errors before the first live lodgement.
Comparing Popular STP Software Options
The right software does not make payroll compliance automatic, but the wrong software can make it harder than necessary.
For small businesses, the best choice usually comes down to complexity, payroll frequency, and who will maintain the file after setup.
STP software options at a glance
| Software | Best For | Key Feature |
|---|---|---|
| Xero | Small businesses | Cloud payroll workflow and STP integration |
| MYOB | Growing businesses | Strong payroll depth and detailed setup controls |
| QuickBooks | Simplicity | Straightforward interface for smaller operators |
How to choose sensibly
Xero suits owners who want a clean cloud workflow and easy visibility across bookkeeping and payroll. It is often the easiest fit for service businesses, small retail, and cafes with relatively standard payroll patterns.
MYOB suits businesses that expect more payroll variation or want deeper control over payroll settings. It can be a good fit where complexity is growing and internal admin staff need more payroll-specific tools.
QuickBooks suits businesses that want a simpler general accounting environment and relatively straightforward payroll needs.
If you are still deciding, this guide to the best accounting software in Australia can help narrow the choice.
The best STP software is the one your business can maintain accurately every pay cycle. Feature lists matter less than clean setup, reliable use, and support when something goes wrong.
Avoiding Common STP Errors and ATO Penalties
You run payroll on Thursday afternoon, hit lodge, and the file rejects because an employee record does not match ATO data. Payday is Friday. That is the point where a small setup mistake becomes a compliance problem.
In practice, STP mistakes come from three areas. Employee data, pay item mapping, and payroll process. The software matters, but I see more errors caused by rushed setup and unchecked assumptions than by the platform itself.
Data errors
These errors appear first because the ATO will reject details that do not line up with its records.
Common examples include:
- Wrong TFN
- Missing address fields
- Business identifiers entered differently from ATO records
The fix is simple. Check employee names, dates of birth, TFNs, addresses, and business details before the first live lodgement. If the business has changed entity, ABN, address, or payroll contact, update that first.
In Xero, review each employee card and the ATO settings before you file. In MYOB, confirm the payroll reporting details and connected business information match the current entity. In QuickBooks, check employee profiles line by line, especially if records were imported from another system.
Mapping errors
These are the expensive ones because the pay run can look correct to the owner while the STP reporting is wrong underneath.
Typical examples are:
- Allowances left in generic wage categories
- Overtime grouped into standard wages
- Income types not assigned correctly
- Legacy pay items left unchanged after Phase 2 updates This is a common pitfall for small businesses. A cafe owner sees the gross pay total is right and assumes the file is right. The ATO does not assess it that way. It looks at how each amount has been classified.
Review every active earning category, deduction, allowance, and leave item. Remove duplicate or unclear pay items. If a category could mean two different things, fix it before the next pay run. Do not leave old payroll categories sitting there because they were used in a prior system.
Submission errors
Late or failed lodgements come back to process gaps.
That often means:
- payroll is run manually with no checklist
- only one person knows how to lodge
- the ATO connection was not fully completed
- no test pay run or file review was done after setup
A good setup includes a repeatable routine. Check exceptions before payday. Finalise the pay run. Confirm the STP status. Save a record of what was lodged. If someone else needs to step in, they should be able to follow the same process without guessing.
STP is no longer a fringe system. It is the standard reporting environment. Late reporting, repeated corrections, and unresolved setup issues are easier for the ATO to spot because payroll data is sent as part of the normal pay cycle.
What works: accurate employee records, clear pay item mapping, and a payroll checklist someone else in the business can follow. What creates trouble: fixing the same coding issue every pay run, ignoring warnings in the software, and assuming a successful lodgement means the payroll setup is correct.
STP Setup FAQs and Getting Expert Help
What is Single Touch Payroll in simple terms
It is a system that sends payroll information to the ATO through your payroll software each time you run payroll.
What is STP Phase 2 in plain English
It is the newer version of STP reporting that asks for more detailed payroll categories, including clearer treatment of gross pay components, allowances, overtime, and income types.
When do I report payroll to the ATO
Your STP report is generally lodged as part of each pay run, on or before payday. Check current ATO guidance if you have unusual payroll arrangements.
Do I need special software to use STP
Yes. You need payroll software that supports STP reporting. Xero, MYOB, and QuickBooks are common examples used by small businesses.
Can I fix mistakes after setup
Usually yes, but fixing STP errors is easier when you catch them early. That is why test pay runs, data checks, and proper mapping matter so much.
A correct setup removes most of the stress from ongoing payroll. The hard part is not pressing submit. The hard part is making sure the file behind that button is right.
If you want help getting payroll right the first time, Nanak Accountants and Associates can assist with STP setup, payroll compliance, bookkeeping integration, and ATO-ready payroll processes for small businesses across Australia. If your file is already live but messy, they can also review the setup, correct reporting issues, and help you move to a cleaner system with less risk.
