Overview
The STP module in Astute has been built to meet the ATO’s requirements for sending data. It is important that you prepare your portal to ensure that the data you send is accurate and meets the ATO’s requirements.
myGovID M2M Credential
Before STP data can be sent to the ATO, you will need to ensure that a valid and current myGovID M2M Credential has been configured for the paying entity.
If you’ve already configured a credential for the entity, you won’t need to do this again. It is still important to check, as without a valid and current credential you will not be able to meet your STP obligations.
You will need to configure a separate myGovID M2M Credential for each entity you will report STP data from.
Entity Details
You’ll need to ensure that the relevant entity details have been configured in Company Management so that your entity is connected to the ATO.
The Payment Summary Annual Report (EMPDUPE) contact details will also need to be completed in Config > Company Management > select entity > Payroll.
The system will validate these details when the Payroll > Process Payroll > STP Submissions report is accessed, to ensure that mandatory setup is complete.
You can refer to the warning banner for more information if configuration is not complete.
Pay Items, Deductions, and Superannuation Items
With the release of STP 2.0 into portals in late May 2022, the STP Report Settings that have been configured for your pay, deduction, and superannuation items are submitted through STP to identify how each pay amount will be reported. The STP Report Settings fields will lock once an item is used in a pay, so it’s essential that your items are configured correctly before they’re used.
If you pay an employee using an incorrectly configured item, you will need to:
- Create a new item with the correct settings.
- Update your Rules Engine to use the new item, if relevant.
- Process lump sum pays to reverse and repay the incorrectly paid amount.
You can check the STP Report Settings settings for different items as outlined below
Pay Items excluding allowances |
Check settings using the Detailed CSV export in Config > Payroll > Pay Items or by clicking into an individual item. |
Pay Items set as allowances |
Check settings using the Detailed CSV export in Config > Payroll > Pay Items. The export will show the allowance category in the STP Report Settings column. Pay items defined with a Payment Section of Total Allowances also need an Allowance Type set. |
Superannuation items |
Check settings using the Pay Item Balance report or clicking into the item in Config > Payroll > Superannuation |
Deductions |
Check settings using the Pay Item Balance report or clicking into the item in Config > Payroll > Deductions Deductions will need to be issued a Deduction Type, with the Payment Section set to match. |
Contributions |
Check settings using the Pay Item Balance report or clicking into the item in Config > Payroll > Deductions |
The Payment Summary Settings section in an item's config relates to the information that was previously submitted to the ATO using STP v1. These configurations will still show in your portal, but are no longer used.
Employee Details
The ATO has specific requirements for the employee data received through STP, so you’ll need to check this regularly to ensure that it is correct.
You can use the ATO Validation Report to check your employee data.
The Payroll > Process Payroll > STP Submission report will show a Failed status for any pay run with incorrect employee data, and you’ll need to correct this before you send any data to the ATO.
Pay Runs
You’ll need to keep in mind that when the data linked to a pay run is sent via STP, the pay run can not be unlocked to make changes. You'll need to use a Lump Sum Pay instead.
Comments
0 comments
Please sign in to leave a comment.