This report is available to all businesses that have enabled STP and can be accessed via Reports > Single Touch Payroll (under the "ATO Reporting" list):
This screen lists all historical Pay Events and Update Events for a specific financial year. You can further filter this report by choosing a specific pay schedule. Otherwise the default view will include all pay schedule events. If you do filter by pay schedule or change the financial year, click on "Search" thereafter to refresh the results displayed.
An example of the results displayed on this screen are as follows:
The following describes each component of this report:
- ID: Each pay event/update event has it's own unique ID (similar to a pay run). When you click on the ID, you will be directed to another screen that provides more detail of that event. This includes the wages/figures being reported to the ATO, lodgement details and errors (if applicable) as well as the ability to export the data to excel.
- Event Type: There are only two options here - a Pay Event or an Update Event. Descriptions of each event type are detailed below.
- Date: This is the date the event was created.
- Status: The options here are:
- Created: The pay event has been created upon finalising the pay run or an update event has been created. The client authorisation is yet to be requested (where lodging as Tax/BAS Agent) or lodgement has not yet been processed.
- Waiting on client authority: Client authorisation has been requested and either (a) awaiting client action or (b) client has rejected lodgement and so another client request needs to be sent. If a client has rejected a lodgement, full access users will receive an email notification. A notification will also appear on your payroll dashboard.
- Client authorised: Client authorisation has been requested and client has approved lodgement. When a client authority is approved, full access users will receive an email notification. A notification will also appear on your payroll dashboard.
- Awaiting ATO processing: The event has been lodged with the ATO and is awaiting final ATO confirmation of success or failure.
- Partially Successful: The event has been lodged with the ATO and there are one or more employees with errors. Any employees containing errors will not have been lodged as part of this event. Refer further below on how to address partially successful lodgements.
- Successful: The event has been lodged with the ATO and no errors have occurred.
- Failed: The event has been lodged with the ATO and the whole submission has failed. If this occurs, you will be advised as to the reason for the error. This type of scenario usually relates to an error in the setup of business/tax agent/intermediary details or ATO connection and so we suggest here fixing the error as detailed and lodging an update event.
- Number of Employees: The number of employees included in the event.
- Pay Schedule: You will note here that update events are associated to a pay schedule, despite the fact there is no pay run attached. This is because the data being submitted to the ATO needs to be filtered by pay schedule, similar to a pay event.
- Related Pay Run: This only applies to pay events as pay events are attached to a pay run. When you click on the pay run, you will be directed to the pay run screen of that related pay run.
What is the difference between a Pay Event & an Update Event?
Whenever an employer makes a payment (that is, creates a pay run) to an employee that is subject to withholding, they are required to lodge a pay event with the ATO on or before the date the payment is made. This includes where the amount of withholding is $0 (for example where an employee's gross income is below the tax free threshold) or where the employee has no net pay (for example where the employee is repaying an advance or overpayment to the employer, voluntarily foregoing their net pay).
A pay event reports employee YTD gross payments, tax withheld, allowances, deductions and superannuation liability information for each individual employee reported. As employee amounts are YTD, once an amount has been reported it should continue to be reported even if it has not changed (for example ETPs should continue to be reported in each pay event after they are first reported if the employee is included in any subsequent pay events).
Basically, once a pay run is finalised, a pay event should be lodged with the ATO.
An update event is used to report changes to employee YTD amounts previously reported to the ATO. Update events are not associated to any pay runs and thus can only be created when an employee payment has not been made. Other examples of why an update event would be created include:
Upon transferring YTD payroll data from one payroll system to another to align the latest employer BMS data with the last employee data reported to the ATO;
To assist with EOFY processes, including finalisation and amendments to STP. After 30 June, any changes made to reported employee data for the prior financial year must only be submitted through an update event.
Instructions on how to create an update event can be found here.