header
Monitoring STP Report Job
- michaella_Datacom
Analytics
On finalisation of a Pay Run, a job will be created to send the XML STP reports to the ATO (provided you have not opted to stop this when finalising). It is crucial that the status of these jobs are tracked to ensure the reports have been sent successfully. Where the report failed to generate or failed, the user must remedy them.
Note: The DataPay Support Team will not be monitoring this screen on your behalf. Ensuring that your STP jobs are successfully sent and accepted by the ATO is the responsibility of your payroll team. All users with the Payroll Administrator screen have access to use the below screen.
The below STP screen can be found in the Tools tab > STP.
The above screen in split into 4 tabs - All, Action Required, In Progress and Completed. The STP job created from the Pay Run you just finalised should first appear in the In Progress tab with a Status of Pending. Files are automatically validated and sent to the ATO typically every 5 - 10 minutes, so if your job has been in this status for longer than 30 minutes please notify the DataPay Support Team so we can investigate.
A typical STP job will progress from Pending > FilesSentToATO reasonably quickly, however it will remain in the In Progress tab for anywhere between 15 minutes up to 72 hours while it is being processed by the ATO. If the ATO accepts the file it will move to the Completed tab with a File Status of FileAccepted. If there were errors found in the file it will be moved to the Action Required tab. Below is a list of all the possible values you will see in the File Status tab.
File Status
File Status | Tab | Message / Response from | Definition | Action |
|---|---|---|---|---|
| Pending |
| Datacom | The job is sitting in queue to be sent to ATO | If one of your STP jobs has been sitting in Pending for longer than 30 minutes, contact the DataPay Support Team for assistance |
| FilesSentToAto |
| Datacom | The XML files have been generated and sent to ATO | Await response from ATO |
| FailedToGenerate |
| Datacom | The XML files failed to be generated at Datacom end. The main reason would be because the validations we have in place have not met. For example:
| There should be an error message attached to this STP job. Please read the message and action any changes. |
| FailedToProcessReceipts |
| Datacom | ATO have sent back a receipt that DataPay Live_Australia was not able to interpret | Contact the DataPay Support Team |
| FileProcessedWithWarnings |
| ATO | Both the employer and employee XML files were accepted and processed in full by ATO. However there are few warnings | Take note of the warnings and fix them, so they are not captured again the next time we send data to ATO. The file for this Pay Run does not need to be resent. |
| FileAccepted |
| ATO | Both the employer and employee XML files were accepted and processed in full by the ATO with no errors or warnings | None |
| ExcludeFromStp |
| Datacom | On finalisation of a pay run, the user had selected to not send data to ATO for STP purposes. In this case, a line is still generated in STP screen for the pay group, but nothing will be sent to ATO.
| None |
| FilePartiallyProcessed |
| ATO | Employer XML file was accepted and processed in full and at least one employee record was accepted and processed. However as its partially processed there are issues with one or more employees in the file and their records were not accepted. | Have a look at the error message and take note of the employees who failed. If the employees error is related to basic information such as TFN then:
If the employees error is related to payroll information, then:
If the error message is not clear enough, please contact the DataPay Support Team for assistance. |
| FileFailedWithError |
| ATO | When severity code is ERROR, which means either:
This means the files were rejected in full. | Have a look at the error message and take note of the reason for failure. If the employer information was cause of failure:
If employee information was the cause of failure:
If the error message is not clear enough, please contact the DataPay Support Team for assistance. |
| FileFailed |
| ATO | An example of this is when the credentials to send data is incorrect. This usually means a Datacom problem and you will likely not be the only client impacted. | Contact the DataPay Support Team |
| PendingApproval |
| Datacom | An update job is created, and the job is waiting approval by authorised personnel before being sent to ATO. | Check the STP reports and if you are happy go ahead and select the Submit to ATO option. |
| Cancelled |
| Datacom | The only time a job would show up as Cancelled is where the file failed to generate on our end (Failed To Generate) or file was sent to the ATO but was rejected (File Failed or File Failed With Error) and we have decided to re-open the Ray Run, make changes and re-finalise. As re-finalising a Pay Run generates a new job, it is preferred that the old job is cancelled. | None |
| FailedReportDistribution |
| Datacom | Indicates that report distribution has failed for an Update and Recreate job. | Contact the DataPay Support Team |
General Guidelines
- If an STP Job is sitting in any status for a long time, please follow up.
- If an STP Job was never accepted by the ATO (Cancelled, File Failed, File Failed With Error etc) it is OK to resend the files
- If the STP Job was accepted however, please do not re-open the Pay Run and make changes
For more information, please see our DataHelp article on Re-opening Pay Runs
Related content
footer