Use the table below to review Single Touch Payroll (STP) Sending Status Messages and why you receive them:
Message or Event Status | Description |
Not Reported | The message has been generated in MicrOpay but has not yet been reported to the ATO. |
Pending | The event has been reported, i.e., the user has clicked Report to ATO/Update ATO, but it has not been received by the ATO or the STP Gateway. Please contact your IT Team to review and update as detailed below. |
In progress | MicrOpay is in the process of sending the message to the STP Gateway. |
Failed Validation: Gateway | The message has been sent to the STP Gateway but a problem with the content has prevented it from being passed to the ATO. More detail about the cause is shown after the message, e.g., Failed Validation Gateway: Invalid ABN. |
Connection Error | MicrOpay could not connect to the STP Gateway due to a network issue. MicrOpay will attempt to resend the message the next time that the STP Reporting window is opened. |
Received at Gateway: awaiting response | The message has been sent on from the STP Gateway but confirmation not yet received that the file has been successfully sent to the ATO. |
ATO Retry Pending | The message was received by the STP Gateway but has not been successfully sent to the ATO. The STP Gateway will automatically continue to resend the message, however if a major outage is detected at the ATO it may be cancelled. |
Cancelled | The message was received at the STP Gateway but will not be processed further due to an error either at the STP Gateway or the ATO. The message may need to be resent from MicrOpay, or included in the next Pay Event/Update Event. |
Partial Success | The message was accepted by the ATO but contains some individual records that could not be processed due to validation errors, e.g., an employee has an invalid TFN. More detail about the error is shown in the Pay Event Details grid, per employee. |
Not sent - Internet Connection Issue | The message could not be sent due to an issue with the internet connection. The error will contain more detail about the issue can potentially be resolved, e.g., check network settings. |
Success: Message Accepted | The message has been received and accepted by the ATO. It can take up 72 hours for the ATO to confirm receipt of an Event. |
Unknown error | This status indicates an unexpected response from either the STP Gateway or the ATO. It may not be caused by an issue with the message itself, more so it is an issue in MicrOpay, with the STP Gateway or with the ATO. Some of the reasons why this may occur:
|
Pending status
You will receive a pending status when the STP Event has not reached the Gateway. You should check that the connection to the Gateway is working correctly by going into STP Setup and clicking Test Connection. The Pay Event will continue to be re-tried each time the user goes into STP Reporting screen.
Check the following:
Network or SQL server connection issues. Try using another PC for reporting.
Outdated operating system without .Net 4.5.1 or higher installed. Install .NET or use another PC.
Citrix environment with manual proxy settings required to access the network. Add a firewall rule or proxy bypass.
To allow MicrOpay to use the ATO gateway API, enable outgoing connections on port 443 from C:\Program Files (x86)\Access MicrOpay\MCS\MicropayClientServicesService.exe, the default installation location to the following URL: https://sagestp.superchoice.com.au.
Firewall. The specifics for how to enable the ATO gateway API on your firewall / proxy depend on the vendor, and unfortunately, we are unable to provide a range of IP addresses. You should be able to set up a DNS rule to allow outgoing connections to *.superchoice.com.au or “sagestp.superchoice.com.au” - the only services required are HTTPS/SSL (port 443).
