Single touch payroll is a legislative requirement in Australia which needs to be implemented by 1st July 2018.

Development Plan:

1. Research single touch payroll requirements
2. Design
3. Build and release

https://www.ato.gov.au/About-ATO/About-us/In-detail/Strategic-direction/Using-Single-Touch-Payroll/ 

The following steps are required before we can start with design:

1. Register online at http://www.sbr.gov.au/software-developers/what-can-i-expect/registration-form 
2. When you register, the ATO will provide you with an account manager who will work with you through each stage of software development and product deployment 

The following tasks have been completed:

1. Packaged Pay Event into the XML format required by ATO
2. Packaged the Pay Event Emp which the XML for each employee
3. Added delimiter for each employee record
4. Added XML wrapper as required by ATO
5. Created controls on PAY UPDATE to initiate the process of ATO submission

Added the following API Calls 

1. Call to API to get authorization Token
2. Call to API to submit XML Payload
3. Call to API to query Message

Tasks in progress

1. Call to API to retrieve XML Payload with results of the submission

Next Steps:

1. Retrieve Payload with messages
2. Handle error messages
3. Allow Resubmit file as UPDATE after corrections are made
4. Close STP submission

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

1. Single touch payload implementation in compliance with WIG and BIC requirements from ATO

Single touch pay submission process has been completed. See figure 1 below.

Design Notes:

1. STP Schedule runs every 2 minutes. This is controlled by the WEB.CONFIG configuration named: 

   EnableSingleTouchPayrollIntegration

2. When a "pay" is updated, an entry is created in the ATO Single Touch menu. The status is marked as "New"
3. A user needs to edit this entry, accept the terms and save. This changes the status to "Approved"
4. The scheduler picks up entries that are "Approved" and changes the status to "Ready To Submit".
5. All employees that are in the PayRun are picked up and payment summary values are extracted, packaged into the ATO PAYEVNT and PAYEVNTEMP XML format and submitted via SSP (OZEDI) for processing
6. Once submitted, the system checks every two minutes for a response from ATO. 
7. When a response is available, the response is loaded and analyzed. If the transmission is successful, the entry is marked as Completed. 
8. If the response is unsuccessful, the entry is marked as "New". The user then needs to read the response and make the necessary corrections. Once corrections are done, the entry needs to be edited, "accept" the terms and conditions and Save. The submission process will start again.

Figure 1 - STP Log

Next Step:

1. Complete documentation (Alvis)
2. Complete security documentation and get approval from ATO for Security and PVT (Sanjay)
3. Perform Production Verification Tests. Upgrade AYW TEST Environment, run tests on their systems then prepare AYW Production Upgrade. (Alvis) 

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

1. Changes to OZEDI interface
2. System Tests changes