Single Touch Payroll Phase 2 has been compulsory for most Australian employers for several years now, yet the Australian Taxation Office keeps reporting a steady stream of avoidable data errors. Employers are lodging their pay events on time, but the detail inside many of those files is still wrong. The purpose of this article is to walk through the seven STP Phase 2 reporting fields that trip employers up most often, explain why each field matters, and set out practical steps you can take today to clean up your payroll data before mismatches, penalty notices, or unhappy employees knock on your door.
A quick refresher on what changed under STP Phase 2
The first phase of Single Touch Payroll asked employers to send gross wages, PAYG withholding, and superannuation amounts after each pay run. Phase 2 took that live data feed and turned it into an information rich source for government agencies. Instead of one gross figure, employers must now break earnings into overtime, bonuses, paid leave, allowances, and other components. Each employee record also carries an income stream type, an income type, and a coded description of the worker’s tax status. The system captures cessation reasons when staff leave, country codes for foreign sourced income, and detailed salary sacrifice and super information. That level of granularity lets the ATO, Services Australia, and other agencies match data faster and enforce the rules with more precision. It also means payroll officers and bookkeepers have to configure their software carefully and keep it updated whenever employee circumstances change.
Reporting field one – income types and income streams
Income stream is the broad category that tells the ATO what kind of payer to payee relationship exists. Examples include salary and wages, working holiday maker, closely held payee, and labour hire. Within that stream the income type provides finer detail such as whether the payment is for a director fee or a labour hire arrangement. The most common mistake is leaving every worker set to the default salary and wages stream even when they should be flagged differently. A family member who draws irregular payments from a family-owned company is a closely held payee. An overseas backpacker picking fruit under a working holiday visa is a working holiday maker. A consultant who invoices through a labour hire firm belongs in the labour hire category. When those distinctions are ignored the ATO sees withholding that does not line up with the correct tax table, and the employee’s tax return may prefill with the wrong amounts. To fix the issue, run an employee detail report, check each record against the ATO definitions, and update the stream and type fields. Once the software is corrected lodge an STP update event so year-to-date values align with the new coding.
Reporting field two – employee tax treatment codes
Phase 2 introduced a single six character code that summarises each worker’s tax settings. The characters capture residency status, tax free threshold claim, study and training loan, Medicare levy surcharge variation, and any special tax table such as senior and pensioner or working holiday maker. Many employers left the default code in place when they migrated from Phase 1. Others forgot to change the code when employees lodged new TFN declarations, cleared their HELP debt, or became Australian residents. Because the ATO uses the treatment code to compare reported withholding with what should have been withheld, the wrong code exposes employers to under-withholding or over-withholding. Review each employee’s most recent TFN declaration or Withholding Declaration, confirm loan balances, and then edit the tax treatment code in your payroll system. Your software provider should publish a cheat-sheet that shows how to build the correct code. After updating, send an STP update event or include the corrected data in your next pay event so the new code is live within two weeks of discovery.
Reporting field three – disaggregation of gross overtime bonuses and paid leave
Under Phase 1 employers could roll overtime, ordinary hours, and paid leave into one gross number. Phase 2 bans that shortcut. The ATO wants visibility of each earnings component so it can prefill income tax returns accurately and support government agencies with more detailed information. Old pay categories labelled Ordinary Earnings that also include leave or overtime remain the biggest cause of disaggregation errors. A payroll conversion that missed one legacy category can result in every fortnightly pay event mixing leave loading or site allowances into ordinary earnings. The fix involves mapping every pay category in your system to the correct Phase 2 item. Overtime must go to the overtime field, bonuses and commissions to the bonus field, and each paid leave type to its own leave category that Phase 2 recognises. Once you update the categories rerun a year-to-date payroll summary to confirm each component balances to the ledger. You can then lodge an update event to push the corrected breakdown to the ATO.
Reporting field four – allowance classifications
Phase 2 wants each allowance identified by its specific type. Travel, vehicle cents per kilometre, meal, laundry, tools, and uniform allowances all carry unique labels. If a payroll officer places an allowance under the catch-all Other allowance type, the ATO sees a flag that says this item requires manual review. Reimbursed expenses sometimes get treated as allowances even though they should not be in STP at all. The table below gives a simple cross-check for the allowances most SME employers pay. Use it as a prompt when reviewing your payroll categories.
| Allowance paid in payroll | Likely Phase 2 allowance type |
|---|---|
| Cents per kilometre car allowance | Cents per kilometre |
| Daily travel allowance for country clients | Travel |
| Meal allowance paid under award | Meal |
| Tool allowance for tradesperson | Tool |
| Laundry allowance for uniforms | Laundry |
| Site allowance for remote work | Other specific employment allowance |
Confirm each allowance in your payroll system is mapped to the Phase 2 code that matches the ATO list. If you truly have an unusual allowance that does not fit any standard code, only then use the Other category. Remember that an allowance can affect super and payroll tax differently from ordinary earnings. Update employee year-to-date figures once the mappings are corrected and lodge an STP update or incorporate the fix in the next pay event.
Reporting field five – lump sum E back payments
A lump sum E payment is back pay that relates to work performed more than twelve months earlier. The ATO removed the old one thousand two hundred dollar threshold for payments made from July twenty twenty five, which means every qualifying back payment now belongs in the lump sum E field regardless of size. Errors arise when payroll officers process a back pay through ordinary earnings because it feels faster at the time. The consequence is that the employee’s current year income statement shows higher earnings while their prior year statement remains unchanged. That creates confusion when the employee lodges their tax return and may result in a tax bill. The better practice is to flag the payment as lump sum E and split it by financial year if it relates to multiple closed years. Most modern payroll software lets you specify prior year amounts within the same pay run. If you discover a misreported back pay, create an update event, move the amount out of gross, record it in lump sum E, and allocate each component to the correct previous year.
Reporting field six – closely held payees and director payments
Closely held payees are people who are directly related to the business entity such as directors, shareholders, and family members. Because their cash drawings can be ad-hoc many employers choose the quarterly or annual reporting concession. The trouble starts when the software sends those irregular payments through the normal salary and wages stream. The ATO then interprets them as arm’s length wages and they no longer reconcile with the company tax return or director loan accounts. Another common problem is missing the special finalisation deadline. Arm’s length employees must be finalised by fourteen July, but closely held payees have until the thirtieth of September. Flag each relevant employee as closely held in your payroll system, choose the concession that suits your payment pattern, and diarise the later finalisation date. If you mistakenly lodged closely held wages as normal salary, reclassify the payee, relodge the affected pay events as update events, and ensure you issue the correct finalisation declaration.
Reporting field seven – end of year finalisation and update events
The STP feed tells the ATO every amount you pay during the year, but the data is not considered tax ready until you lodge an end of year finalisation declaration. Many employers think the last ordinary pay event before thirty June is enough. It is not. Without the finalisation tick your employees see a Not tax ready label in myGov and cannot lodge their returns. Another error is ignoring pay events that were flagged by the ATO portal as having validation warnings or partial failures. Those events still sit in Pending status and block finalisation. Best practice is to run a payroll reconciliation after the final pay run, compare general ledger wages to STP year-to-date totals, correct any discrepancies, then lodge the finalisation declaration. If you spot errors after finalising you can still send an update event. The update tells the ATO to overwrite the existing year-to-date figures, and the new data flows through to the employee’s income statement within forty eight hours.
How the ATO is using Phase 2 data
The ATO cross matches STP against PAYG withholding activity statements, business activity statements, and super guarantee clearing house records. Services Australia uses the same feed to confirm eligibility for family assistance and other payments. If an employee reports that their myGov income does not look right, the ATO opens an inquiry which often leads back to incorrect coding in the employer’s payroll. The draft Penalty Statement PS LA 2026 D2 outlines how the Commissioner will apply administrative penalties for late, incomplete, or misleading STP lodgements. First errors might receive a warning, but repeated mistakes or large discrepancies trigger monetary penalties calculated per employee record. Given that every pay run is effectively a real time data disclosure, employers now carry ongoing reporting risk rather than an annual reporting task. Maintaining clean data throughout the year is therefore essential risk management.
A practical narrative checklist to audit your data
Start with your pay categories. Export the list, review each category name, and ensure it maps to a specific Phase 2 item such as overtime, bonus, annual leave, or tool allowance. Then review every employee record. Confirm the income stream type, income type, tax treatment code, and closely held status where relevant. Next run a year-to-date payroll summary that shows each disaggregated component. Compare that report with the STP year-to-date values visible in your payroll software or the ATO Business Portal. Any mismatch means at least one pay event failed to transmit or was rejected. Investigate failed events, correct the data at source, and lodge an update event within fourteen days of discovery. Finally, check back payments that you processed during the year. Find any that relate to prior years and verify they sit in the lump sum E field with the right year allocation. Completing this narrative checklist in one sitting will give you a high level assurance that your STP data accords with ATO expectations.
When to seek professional help
If your payroll includes irregular director drawings, complex allowance structures, multiple overseas workers, or history of late super payments, a specialised payroll health check can save a great deal of time and money. An external adviser can log into your software, run diagnostic reports, and fix mapping issues without disrupting your normal pay cycle. Many small businesses choose a quarterly review so that errors never build up to an end of year nightmare. Engaging help becomes critical if the ATO has already issued an STP error letter or if employees see persistent Not tax ready messages in myGov. The cost of a professional review is usually far less than the combined penalties, interest, and staff frustration that follow prolonged data problems.
Frequently asked questions
What is Single Touch Payroll Phase 2 in Australia
STP Phase 2 is the second stage of real time payroll reporting that requires employers to send detailed earnings breakdowns, tax information, and super data to the ATO each time they pay employees.
What are the most common STP Phase 2 mistakes employers make
The most persistent errors involve incorrect income stream or income type, wrong tax treatment codes, failure to disaggregate gross earnings, misclassified allowances, lump sum E back payments reported as ordinary earnings, unflagged closely held payees, and missing finalisation declarations.
How do I know if my STP Phase 2 reporting is wrong
Warning messages in your payroll software, ATO rejection emails, mismatches between payroll year to date totals and STP reports, or employees who cannot see a tax ready status in myGov all point to data errors.
What happens if I report STP Phase 2 incorrectly
Incorrect or late reporting can lead to ATO penalty notices, interest charges, additional audits, and frustration for employees who might lodge incorrect tax returns based on faulty prefilled data.
How do I fix STP Phase 2 errors that have already been lodged
Most payroll systems let you create an update event that overrides the year to date figures for each employee. Lodge that event as soon as possible, ideally within two weeks of discovering the mistake.
What is lump sum E in STP Phase 2 and when do I use it
A lump sum E represents back pay that relates to work performed more than twelve months ago. From July twenty twenty five every qualifying amount must be reported in the lump sum E field with each prior financial year specified.
How do I report allowances correctly under STP Phase 2
Each allowance must be mapped to a specific Phase 2 allowance type such as travel, tool, or laundry. Only allowances that truly do not fit any listed type should use the Other category.
Do I still need to give payment summaries if I use STP Phase 2
If all payments are reported and finalised through STP you do not issue traditional payment summaries. You still need to give a summary for any payments made outside the STP system.
What are closely held payees and how are they reported in STP Phase 2
Closely held payees are individuals directly related to the entity such as directors and family members. They can be reported each pay, quarterly, or via an estimate with a finalisation due by thirty September.
When should I get professional help with STP Phase 2
Seek expert help if you face repeated ATO rejection messages, complex back pays across many years, multiple allowances with uncertain tax treatment, or a workforce that includes family members and overseas workers.
Final thoughts
Single Touch Payroll Phase 2 is more than a software upgrade. It is a regulatory framework that demands precise, real time data. By focusing on the seven fields covered in this guide you can eliminate the mistakes the ATO sees most often, protect your business from penalties, and give your employees confidence that their income information is correct. Schedule a short internal audit this week, fix any mapping gaps, and consider a professional health check if you are unsure. Clean data now means fewer headaches at year end and stronger compliance across your entire payroll process.
