Skip to main content
Skip table of contents

Troubleshooting Single Touch Payroll

What data is included in STP submissions?

Each STP submission includes:

  • Contact information for the payer (employer)

  • Contact and personal details for each employee included in the originating pay run

  • Year-to-date pay information for each employee included in the originating pay run, including allowances, deductions, superannuation and FBT

All information included in a batch can be viewed on the Manage Submission screen (MPPP5019)—see Managing STP submissions.

Do I still have to send payment summaries?

As the Single Touch Payroll data provides all year-to-date values, the STP process replaces the old Payment Summary process. Employees can view their payment information online using their myGov account.

If any employees do not have a myGov account (this may be the case for working holidaymakers or seasonal workers), they can contact the ATO for a printed copy of their payment information.

Once you have successfully submitted STP data, you do not need to generate Payment Summaries for employees or submit the usual PSAR to the ATO. If you started STP submissions before 1 July 2018, you do not need to generate Payment Summaries or the PSAR for the 2017/18 financial year. 

What do I do if a submission fails?

When an STP submission returns an error, you will need to examine the error response and make the appropriate corrections. The method for addressing the error depends on the error status returned:

  • If a batch has the “Not created” status, this could mean that the internal process that creates the STP batch has failed, or that the originating pay run was completed before STP was enabled, but is future-dated to a date after STP was enabled. Open the pay run from the Manage Pays screen (MPPP4110) and click the Create STP Batch button to create a batch manually.

  • If a batch has the “Submission failed” status, this means that the batch could not be sent to MYOB’s online services, which forward the data to the ATO. You will need to re-send the batch manually by clicking the Re-send to ATO button on the Payer Details tab of the Manage Submission screen (MPPP5019).

  • If a batch has the “Submission not successful” status, this means that the batch was successfully submitted to the ATO, but the ATO rejected some or all of the batch. You will need to open the batch on the Manage Submission screen (MPPP5019) and review the Errors tab to see exactly which records in the batch were rejected. You can then click on the ID of each record to open it in a new window and correct the problems that resulted in the error. Generally, it is not necessary to re-submit the batch—the issues will simply be corrected in the STP batch for the next pay run.

Records are rejected on an individual basis, i.e. only those employee records that have the “Submission not successful” status have been rejected by the ATO; all others have already been accepted.

How does STP affect pay run reversals?

If a pay run is reversed, the reversal will not be included in STP reports; however, the STP batch for the replacement or subsequent pay run will report the correct YTD totals.

What do I do if a my.MYOB login fails?

If you are unable to log in with the my.MYOB/Secure Authentication login associated with an MYOB Advanced user, try removing the association on the User Profile screen (SM203010), then re-associating the user with their my.MYOB login after STP reporting has been activated.

How do I correct incorrect reporting categories?

Allowance amounts in STP must be assigned the correct STP category—this category comes from the allowance’s pay item.
If a pay item has been assigned the wrong category, update it on the Pay Item Liabilities screen (MPPP1025) and click Update Pay History. The next time STP data is sent, the amounts in each category will be corrected.
However, if the wrong pay item was processed in an employee’s pay, you’ll need to use the Adjust Pays button on the Pay Run Details screen (MPPP3120) to correct it. See Adjusting Employees' Pays for more information.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.