search icon

Sage MicrOpay STP
Support

Support Services

Experiencing Sage MicrOpay Error Messages?

Here are some common messages you may receive when running your STP reporting and how to resolve them.

Pay Event > Invalid characters

Error: Value '351' is not valid with respect to pattern '[0-9]{4}' for type 'PostcodeTAddressDetails'. The value '351' of element 'tns:PostcodeT' is not valid.

Resolution: Fix the postcode on employee record.

 

Pay Event > Object activation

Error: Error during Object activation - Access Violation at address…

Resolution: Please review the eKnowledge Answer 371 regarding Access Violation/Object Activation Errors

 

Pay Event > Employee declaration date

Error: Employee Declaration Date cannot be in the future for employee EMPLOYEE NAME with employee payroll number W01.

Resolution: Restore to prior to generating EFT and remove employee transaction, change the Declaration date, enter transaction, generate EFT and create Pay Event.

 

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

 

Pay Event > Run date/timestamp

Error: The payroll run date/timestamp cannot be in the future.

Resolution: Use Google to check date and time and match to PC - sometimes the computer time is ahead of ‘real time’ and this is why the file gets rejected.

 

Pay Event > ATO Reporting could not be submitted

Error: Unable to submit the selected Pay Event to the ATO Reported Error ATO Reporting Couldn’t submit Pay Event to the ATO – Reported error: Couldn’t create ATO PAYEVNTEMP record Reported Error: String or binary data would be truncated

Resolution: Please review the eKnowledge Answer 886 regarding Sage MicrOpay Data Audit IQ Report

 

Pay Event > Invalid character value

Error: Invalid characters Value (02)-99555444 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 error, including a space. i.e. ( ) - # or a space has been used in the phone number in the table. Please re-key the phone number in company details.

 

Pay Event > Pending status error message

Error: Pending Status error message – Unknown error

Resolution: To allow MicrOpay to use the ATO gateway API, please enable outgoing connections on port 443 from “C:\Program Files (x86)\Sage MicrOpay\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, I am 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.

Known Issues

Payment Summary > Employee not loaded into STP grids

Issue: Employees who have had a payment summary produced are then not being loaded into the STP Reporting/STP Update grid. For STP Reporting this may occur when the payment summary is produced for the current financial year. For STP Update, this may occur when a payment summary has been produced for the Financial Year selected in the STP Update filter options. For example, a payment summary was produced for an employee for 2016, and 2016 is the selected Financial Year in the STP Update filer options.

Resolution: Please download and run the following fix to resolve the error.
 

Status Message Definitions

At the time of submitting your STP pay event or update event these are the status messages you may receive and what they mean.

Status Description
Not Reported The message has been generated in Sage MicrOpay, but has not yet been reported to the ATO.
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 Gateway
  • Check: Customers should check that the connection to the Sage Gateway is working correctly by going into STP Setup and pressing ‘Test Connection’
  • Check: Payroll Company/companies in Common Screen and Payroll Company/companies screen that ‘Australia’ is listed in the Country Code field – if missing please enter. Then click on this link, download the script and run. Return to STP Reporting tab and the file should populate to ‘Received at Gateway’.
  • The Pay Event will continue to be ‘re-tried’ each time the user goes into STP Reporting screen
  • Please check the following:
  1. Network or SQL server connection issues – Product Delivery has resolved these by using another PC for reporting
  2. Outdated operating system without .Net 4.5.1 or higher installed – resolved by installing .NET or using another PC
  3. Citrix environment with manual proxy settings required to access the network – resolved by adding a firewall rule or proxy bypass
To allow MicrOpay to use the ATO gateway API, please enable outgoing connections on port 443 from “C:\Program Files (x86)\Sage MicrOpay\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 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).
In Progress Sage MicrOpay is in the process of sending the message to the Sage STP Gateway.
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.
Connection Error Sage MicrOpay could not connect to the Sage STP Gateway due to a network issue. Sage 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 Sage 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 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.
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 Sage 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 be 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 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 Sage MicrOpay, with the Sage STP Gateway or with the ATO.

Still have questions?

Contact Support via our courtesy call back feature.

To ensure that you retain your place in the queue we have implemented Courtesy Call back. This replaces the voicemail system. To receive a call back please ensure when prompted to register for a courtesy call back please provide all details requested and do not hang up. Ensure you complete all steps to register your call until advised your call is registered. If all details such as Customer Number, Phone number and your name are not all recorded the system is unable to register you for a call back.

 

Contact our Help Desk on: 1300 729 329