Company: Link Technologies
Case No: L11902
Logged By: Sanjay (Link Technologies) on 14 Feb 2020 09:22AM
Priority: Low
Product: Payroll & HR
Group: Support
Time Taken: 5.00 (Weight: 5.00)
Assigned To: Development
Circulation: Alvis, Development, Sanjay
Resolve By: Saturday, 15 February 2020 12:00 AM [1529 days since logged date]
Status: Closed
Subject: ATO STP PayEvent.Update event not triggered from Link Payroll
Summary:    See email from ATO  DSP below. I have replied saying that we have implemented the PayEvent.Update event, however we need to push an Update for them to verify.
---------- Forwarded message ---------
From: DPO <DPO@ato.gov.au>
Date: Thu, 13 Feb 2020 at 3:27 pm
Subject: RE: STP payevnt.update [SEC=UNCLASSIFIED]
To: sanjay@linktechnologies.com.au <sanjay@linktechnologies.com.au>
Cc: DPO <DPO@ato.gov.au>

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

Get ready for AUSkey decommissioning in March 2020

Be ready now. Make the move to myGovID – RAM – M2M

Stay informed. Subscribe to our Digital service providers newsletter

 

Access support and track requests in Online services for DSPs

From: DPO 
Sent: Wednesday, 15 January 2020 3:05 PM
To: sanjay@linktechnologies.com.au
Subject: STP payevnt.update [SEC=UNCLASSIFIED]

 

 

 

 

 

STP payevnt.update

Digital 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.

*********************************************************************

Audit Notes:
14 Feb 202009:23AM Comment 1 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 19-02-2020 11:22 AM Time Taken: 2.00
On Fri, 14 Feb 2020 at 9:05 am, Sanjay Singh <sanjay@linktechnologies.com.au> wrote:
Hi Nadeem,

We have implemented the PayEvent.Update event, however our clients have not had to do an update. 

If you need confirmation, I can plan a PayUpdate Event from our system jus so you can see this in the STP production system.

PS: You should be able to see the PayEvent.Update event on the testing platform.

Regards
Sanjay

14 Feb 202009:25AM Comment 2 by Sanjay (Link Technologies) Assigned To: Alvis (Link Technologies) Followup Date: 19-02-2020 11:23 AM Time Taken: 1.00
Hi Alvis, can you push a PayEvent.Update event from our internal systems so ATO can tick this off?. Please place details on this case so we have an audit log of this event for future reference.

14 Feb 202010:09AM Comment 3 by Sanjay (Link Technologies) Assigned To: Alvis (Link Technologies) Followup Date: 01-07-2020 10:00 AM Time Taken: 1.00

The pay update event is when a backdated pay is processed after a financial year rollover.

We will do this in July after the End of the Year.


25 Feb 202004:31PM Comment 4 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 27-02-2020 06:30 PM Time Taken: 1.00
ATO confirmed they have taken note and no further action is required.

If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L11902 in the subject line of all emails regarding this issue.

Document size: 17.8 KB
For call complaints, please contact the Managing Director of the company using this form