Step 1:
Select Period Ending Date for STP Submission. On click of dropdown below, you will see the listing of current financial year processed period ending dates along with current STP process status.
The below screenshot shows Period Ending Date selection along with STP Status
Screen Parameters Details:-
Period Ending Date: Regular or Financial year Pay Run Date.
Period Start Date: Default as per Weekly or Fortnightly pay run duration set in system
Submission ID: System generated unique identifier for STP Submission. Please use this Identifier for any STP related communication to ATO
Resubmit Pay event: This is needed when you would like to resubmit the already submitted STP for a period due to any reason. For Example: If an Employer has done a mistake in the pay process & submitted the same to ATO. Then after, if Entire Software is reversing the pay run as per Employer requests then it is a mandatory requirement to resubmit the Pay Event. In this scenario, Employer has to tick this flag so that ATO system will override old STP files with new one.
Staff Submitting data on behalf of Payer: Logged in user who is declaring employee’s pay to ATO. By Default, it is a logged in user name.
Payer Declaration Date: It is a date of signing the above declaration & submitting the pay run.
Payment Date by Entity: This is a date of payment to employees. By Default, system shows the date of finalizing the pay run but it can be changed from the screen as per Employer payment rules.
Is this week’s Payroll is the final Payroll of this financial year: This is an automatic prefilled flag set according to the Payroll Financial year settings. If true tells to ATO to close the books of financial year & report all members year to date details to ATO who have worked during the year.
Declarations: It is must to read & agree all declaration shown above for the STP Submission.
Step 2
Once screen data has been entered, Press Next button to move to the next step of Data processing & File Creation.
1. Check STP Date Settings: Optional Step to print a report to view STP settings before Submission. Report sample shown below.
Check TFN, Member Name & Member Address: This is a mandatory step to ensure successful STP transmission.
1. Process Pay Event Data (Mandatory Step): At this step, system calls the back end program to extract all Pay Run employees Year to Data figures.
There are 2 outcomes after its execution:-
a. Data Successfully Created:- After successful processing of Pay Event Data, next mandatory step of “Generate ATO Files” will get activated & the status of STP Submission process will change to “Date generated Successfully”.
b. Date Processing failed: This outcome is rare. In this scenario, please contact Entire Software Development Team.
Generate ATO Files (Mandatory Step):
At this step, system will create ATO required XML Header & Employees files at the set system directory location. On success, next step of “Validating ATO generated Files syntax” will get enabled & STP submission status will change to “Files Generated Successfully”
To view all generated files, click the link “Files generatedsuccessfully” as shown above. On click, system will take you to the physical file location as shown below:-
Final step before the submission – Validate ATO generated Files Syntax (Mandatory Step):
Till now, ATO Files has been generated by EntireHR. Next step is to validate the created files according to ATO standards to ensure correct files format submission. To do this step, the system calls the backend programs to go through all created files in system directory.
The outcome of this validation are:-
a. Passed: Move to final step of validated files submission to ATO
b. Failed: Please contact Entire Software with details of error.
Step 3
Submit validated files to SSP for ATO submission (Mandatory Step)
On the below screenshot, Submission Response time is blank. Once the Submit button below is selected, the system will show an ATO response message. Please refer to the Details of Message Submission Responses on page 33 for an explanation of each response.
Submission Responses
1. Queued
If the Message response is set to Queued then it means ATO files has been put in Queue to SSP for pushing to ATO Database.
2. Pushed
If the Message response is set to Pushed then it means ATO files has been successfully pushed to ATO from SSP& waiting for their verification.
3. Responded
On every poll to get response, system shows the API status as responded.
4. Transmission Unsuccessful
This is anerror response received from ATO along with details of errors. Please refer to error details & push the files back to ATO. Please note: you may need to generate the files & push it back again until it gets successful.
5. Transmission Successful
This is a positive response received from ATO. This means all files have been passed & successfully transmitted for further data checks.
6. Data Success
This is a final status which denotes for data has been successful updated in ATO System.
Message response Screenshots as sample for reference.
Screenshot: Queued
Screenshot: Pushed
Screenshot: Transmission Unsuccessful
On the transmission unsuccessful, the following will happen for further action You will get notified automatically from SSP or you can poll through EntireHR as shown below with the error response details. Please see the screenshot below.
Screenshot showing Error Response Details from ATO
Final Step
Poll ATO Response for Submission finalisation (Madatory Step)
Please view image below to see how you can poll though EntireHR to get response details
Screenshot showing Error Response details stored in system directory after polling through EntireHR – On click “Open Response File”.
After receiving the error details, please perform the below steps:-
Step 1: If errors are related to employees missing information then please fix all errors or contact Entire Software with details of error.
Step 2: After fixes, return to Step 2 for ATO Files generation and validation. Then continue with the process of files submission until you get “Files Transmission Successful”.
Screenshot: Transmission Successful
