Company: Link Technologies
Case No: L11700. Project: 11.40: LinkSOFT Version 11.4
Logged By: Sanjay (Link Technologies) on 27 Aug 2019 03:59PM
Priority: High
Product: Payroll & HR
Group: Software Defect
Time Taken: 27.50 (Weight: 29.50)
Version: 11.3.0902
Assigned To: Sanjay (Link Technologies)
Circulation: Development, Rashna, Sanjay
Resolve By: Tuesday, 27 August 2019 12:00 AM [1913 days since logged date]
Status: Closed
Subject: STP - Implementation of Year Finalization and Update Event Handling
Summary:    
STP payevnt.update
Digital Service Providers

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 a mandatory requirement for your users to fix errors throughout the year and to amend end of financial year data.

What you need to do

If you have already implemented and made available the service action of ‘payevnt.update’ in your software product, no further action is 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.

What happens next

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 DPO has provided correspondence to all SSPs on this matter.

For further information please request assistance via Online Services for DSPs or email DPO@ato.gov.au.

--- Update Event Definition in the ATO STP BIG ---

Update event
The update event allows the employer to report changes to employee YTD amounts previously reported. The update event may only be used in circumstances other than when the employee is paid.

The update event cannot be used to supply:
  1. Employer ‘Total gross payments’ and ‘Total PAYGW Amounts’.
  2. The onboarding section (which contains the employee withholding details and declaration).
It may be used to align the latest employer BMS data with the last employee data reported to the ATO, or to assist with EOFY  processes, including finalisation and amendments to STP prior finalised years.

After 30 June, any changes made to reported employee data for the prior financial year must only be submitted through the update event.

The update event must include the latest YTD value for all payments (including each ETP by payment date and code) made in the financial year. It cannot only include the values that have changed. As there is no associated payment to the employee when changes are reported via the update event, the employer pay period totals for gross payments and PAYG withholding cannot be included in an update
Audit Notes:
27 Aug 201903:59PM Comment 1 by Sanjay (Link Technologies) Case 11700 added to project 11.00
27 Aug 201904:09PM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 27-08-2019 04:09 PM Time Taken: 25.50

Development work for this case has been completed.

The change will be available in version:11.0.20190827

1. The following changes were made(Include Database object names, Program classes and any other relevant information):

  1. Added "Final Pay" to STP Processing. The user can set this before submitting STP.
  2. Added Employee View to STP Detail section to allow the Payroll officer to set individual employees as "Final Pay" before submitting to Tax Office
  3. Added a new tab to allow for "Manual Submissions". A manual submission will allow the Payroll Staff to RESUBMIT a pay that has already been submitted and select the submission to be marked as "Final". This tab is mainly used for when the Payroll Staff has done a submission and later realizes that the submission should have been a "final pay".

2. Affected Areas:

  1. "Payroll Processing ~> ATO - Single Touch"

3. The issue was caused by:

  1. Did not account for this scenario in the initial build.

4. Notes

  1. "Final Pay" is where the pay is the last pay of the year or if the employee is terminated and this is the "final pay" of the employee before leaving
  2. Pay update is used only to update closed Financial Year Employee data.

5. Next Step: UAT


17 Sep 201903:16PM Comment 3 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 17-09-2019 03:16 PM Time Taken: 2.00
QA Results
Tests carried out according to requirements specified on the case header

Test Results Summary

Table 1 - Summarised list of issues
NoTest DescriptionPass/Fail
1

Enable ATO integration

  1. Enable Single Touch process in Linkweb. Set the frequency. Update default company.
  • Set the pay date as 30/06/2019. Create pay for the employees.
  • Update pay with bank date as 30/06/2019.This should create single touch submission with employee status as "Not Finalised".
  • The submission should be completed. 


Pass
2
  1. Create a manual submission with date as 30/06/2019.
  2. Create and update special pay for employee E0001.
  3. The submission should be completed. 
Pass
3
  1. Submit the final pay and mark June 2019 as closed
Pass
4
  1. Create a pay for 30/06/2019.
  2. This should go into ATO submission as an "Update".
  3. This should create single touch submission  with employee status as "Finalised"
Pass
5
  1. Create a pay for current year 14/07/2019.
  2. Update pay with bank date as 14/07/2019.This should create single touch submission  with employee status as "Not Finalised".
Pass

Environment Details

  1. OS version: Windows Server 2012
  2. Application version: 11.003.916
  3. Setup: Demo
  4. Server : 10.0.0.14
  5. Database: LINKSOFT-DEMO-11-RASHNA

Next Step

Closure

Thanks
Alvis and Rashna

    09 Oct 201908:22AM Comment 4 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - Cleared queue due to large number of calls
    If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L11700 in the subject line of all emails regarding this issue.

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