Dear Sanjay
As per our recent correspondence below dated 15th January 2020, based on our records your Software product has been identified as ‘not reporting an STP update event in the ATO SBR production environment’
Please be reminded that this service action is mandatory - it enables employers or their intermediaries to fix errors throughout the year and to amend end of financial year data.
We understand some DSPs have already built this service and made it available to their users, however to date this service may not have been used.
Please also note that the exclusion of an Update event from your STP reporting product will compel the employer to lodge Pay events to change employees’ STP data. Pay events lodged after 30 June, referencing a pay date prior to 1 July for example, are late lodgments, and therefore, subject your client to potential late lodgement penalties.
As previously requested:
- If you have already implemented and made available the service action of ‘payevnt.update’ in your software product, reply to this email confirming this and no further action may be required
- If you have not implemented or made available the service action of ‘payevnt.update’ in your software product, you will need to provide this functionality to your users, no later than 31 March 2020
We would appreciate your prompt response in relation to this matter.
Thank you.
| | | Nadeem Shariff (on behalf of the DPO) |
DSP Relationship Manager | Technical Support Stream
Digital Partnership Office | Enterprise Solutions & Technology
Australian Taxation Office
|
| | |
| STP payevnt.updateDigital Service Providers (DSPs) According to our records your Software product (Link Technologies) has been identified as ‘not reporting an STP update event in the ATO SBR production environment’ This service action is mandatory as it enables employers or their intermediaries to fix errors throughout the year and to amend end of financial year data. We understand some DSPs have already built this service and made it available to their users, however to date this service may not have been used. What you need to do If you have already implemented and made available the service action of ‘payevnt.update’ in your software product, reply to this email confirming this and no further action may be required. If you have not implemented or made available the service action of ‘payevnt.update’ in your software product, you will need to provide this functionality to your users, no later than 31 March 2020. You should refer to the development artefacts to assist with building this service action: · Message Structure tables and STP Update validation rules, and · STP Business Implementation Guide We recommend you complete conformance testing against the ‘payevnt.update’ test scenarios. Please note: if you have already successfully met PVT requirements for the service action of ‘payevnt.submit’, you do not need to undertake further PVT against the ‘payevnt.update’. If you transact via a Sending Service Provider (SSP), you may need to contact them for support. The Digital Partnership Office has contacted all SSPs regarding this matter. For further information contact us via Online Services for DSPs or by emailing DPO@ato.gov.au. | |
| | |
| Martin Mane Assistant Commissioner, Digital Partnership Office and e-Invoicing Enterprise Solutions and Technology Australian Taxation Office | |
| ATO | Working for all Australians | |
**********************************************************************
IMPORTANT
The information transmitted is for the use of the intended
recipient only and may contain confidential and/or legally
privileged material. Any review, re-transmission, disclosure,
dissemination or other use of, or taking of any action in
reliance upon, this information by persons or entities other
than the intended recipient is prohibited and may result in
severe penalties. If you have received this e-mail in error
please notify the Privacy Hotline of the Australian Taxation
Office, telephone 1300 661 542 and delete all copies of this
transmission together with any attachments.
*********************************************************************