Follow

STP Status Message Definitions

This article is for users who are experiencing STP error status while reporting STP. 

Validation Errors In STP

  1. Double-click the line that tells you that there is a validation error.
  2. Look at the lower half of the screen and scroll through all your employees.
  3. Look for a message/details regarding the validation error in the status column.
  4. Once you have determined what the issue is, go to the Employee Details screen and correct the data, i.e. incorrect TFN, invalid character in the address, etc.

Payer Validation Error 

  1. Go to File > Company Details > Address.
  2. Check that all items are correct on this screen, i.e. no commas or brackets are allowed.

Common Error Messages When You Report STP Using Wagemaster 

  1. Entering Credentials > Outdated Operating System  
    Error: Unknown Error. 
    Resolution: Outdated operating system without .Net 4.5.1 or higher installed – resolved by installing .NET or using another PC.
  2. Pay Event > Invalid Characters  
    Error: Invalid Characters Value (02)-98845400 is not valid with respect to pattern ‘[(0-9 A/Zs])”for type ‘TelephoneMinimalNElectronicContact’. The value “029884400” of element ….invalid.
    Resolution: Any character other than numeric will cause an error including space i.e. ( ) - # in the phone number in the table. Please re-key the phone number in the company details. 

  3. STP Connection Error
    Error:
    "STP Connection Error: Unknown Error" (Relating to SSL\TLS).
    Resolution: The minimum Windows version you should be on is Windows 10 and Windows Server 2012. Any prior versions are not supported by Microsoft® and will prompt an Unknown Error when STP Reporting in Wagemaster, due to security updates.

Types of STP Status Messages

At the time of submitting an STP pay event or an update event, you may receive the below status messages. 

  1. Not Reported
    • The message has been generated in Wagemaster but has not yet been reported to the ATO.
  2. Pending
    • The message 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 Sage STP Gateway. 
    • The pay event has not reached the STP Gateway. 
    • Customers should check that the connection to the Sage Gateway is working correctly by going into STP Setup and pressing Test Connection.
    • The pay event will continue to be re-tried each time the user goes into the STP Reporting screen. 
    • Please check the following:
      • Network or SQL server connection issues – Product Delivery has resolved these by using another PC for reporting.
      • Outdated operating system without .Net 4.5.1 or higher installed – resolved by installing .NET or using another PC.
      • Citrix environment with manual proxy settings required to access the network – resolved by adding a firewall rule or proxy bypass. 
    • To allow Wagemaster to use the ATO Gateway API, please enable outgoing connections on port 443 from
      C:\Program Files (x86)\
      Wage Easy Payroll\MCS\MicropayClientServicesService.exe (default installation location) to the following URL: https://sagestp.superchoice.com.au 

    • The specifics for how to enable this 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 setup 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). 

  3. In Progress 
    • Wagemaster is in the process of sending the message to the Sage STP Gateway. 
  4. Failed Validation: Gateway
    • The message has been sent to the Sage 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. 
  5. Connection Error
    • Wagemaster could not connect to the Sage STP Gateway due to a network issue. Wagemaster will attempt to resend the message the next time that the STP Reporting window is opened. 
  6. Received at Gateway: Awaiting Response
    • The message has been sent on from the Sage STP Gateway, but confirmation not yet received that the file has been successfully sent to the ATO. 
  7. ATO Retry Pending
    • The message was received by the Sage STP Gateway but has not been successfully sent to the ATO. The Sage STP Gateway will automatically continue to resend the message, however, if a major outage is detected at the ATO it may be cancelled. 
  8. Cancelled 
    • The message was received at the Sage STP Gateway but will not be processed further due to an error either at the Sage STP Gateway or the ATO. The message may need to be resent to Wagemaster or included in the next pay event/update event. 
  9. 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. 
  10. 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 that can be potentially be resolved, e.g. check network settings. 
  11. Success - Message Accepted
    • The message has been received and accepted by the ATO. It can take up to 72 hours for the ATO to confirm receipt of an event.
  12.  Unknown Error 
    • This status indicates an unexpected response from either the Sage STP Gateway or the ATO. It may not be caused by an issue with the message itself, more so it is an issue in Wagemaster, with the Sage STP Gateway or with the ATO. Some of the reasons why this may occur:
      • You have entered the incorrect Password in the STP Credential.
        Navigate to File> Company Details> Taxation > Single Touch Payroll.
      • 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 setup 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).

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments