Creating & Lodging a Pay 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.

** If you need assistance with configuring and setting up your payroll account for reporting to the ATO for STP this video will assist: STP - Setup and Configuration

Creating a Pay Event 

A Pay Event can only be created upon finalising a pay run. You will now be provided the following new option when finalising a pay run:


(a) When choosing to lodge a pay event manually at a later date

If you choose this option and then click "Finalise", the pay run will finalise as per the standard process. To lodge the event at another time, you simply need to access that pay run and click on "Lodge Pay Run with ATO":


You will then be redirected to the Create Pay Event lodgement screen.

(b) When choosing to lodge a pay event now 

If you choose this option and then click "Finalise", the pay run will finalise as per the standard process and then you will be redirected to the Create Pay Event lodgement screen. 

Create Pay Event Lodgement Screen

A list of all employees with payment details attached to that pay run will appear on the screen along with their year to date details:


A few things to point out when a pay event is generated:

  1. You can filter your view by searching for a specific employee or by employing entity (if you have more than one employing entity set up in the business). Please note however that when the event is lodged it will lodge for ALL employees in that pay event; that is, the filtering does not filter the data lodged with the ATO.
  2. Employees who have been employed by more than one employing entity during the financial year will have a row of data per employing entity.
  3. Employees who have changed between a working holiday maker (where Type = H) and a non-working holiday maker (where Type = S) during the financial year will have a row of data per tax change.
  4. Terminated employees who have received an ETP will still appear in the event with the "Is Final" checkbox automatically ticked - refer to Grace Lim above as an example. 
  5. You can choose to view the payroll figures pertaining to the actual pay run in addition to the YTD figures by clicking on "Show figures from this pay run". The screen view will update to include the pay run figures, highlighted in blue:  Screen_Shot_2018-07-03_at_18.35.49.png

Can I edit any information contained in a Pay Event?

There are only 2 items that can be edited in a pay event:

  1. Reportable Fringe Benefits Amount (RFBA): You can choose to report employee RFBA on an ongoing basis or at the end of the financial year. To edit an employee RFBA, click on the pencil icon under the RFBA column for the specific employee, enter the grossed up RFBA value and then click on the green tick icon. If you choose to enter RFBA on an ongoing basis, you must enter the amount as a YTD value.
  2. Is Final: If an employee has terminated employment and a termination pay has been processed, the "Is Final" checkbox will be ticked automatically. If the employee has not been terminated within a pay run but there will be no further payments for that employee in the financial year, you can tick the "Is Final" checkbox. This will indicate to the ATO that no further payments for this employee will be made. If an employee is reinstated and the same employee payroll ID is used, you will need to untick the "Is Final" checkbox. 

Pay Event Actions

You will notice there is "Actions" button on the right hand side of the even table, where you can undertake the following actions:


  • Excel: Click on this button to generate an excel report of the data contained in this pay  event. This report can be generated at any time - upon creation of the event through to post lodgement of the event.
  • Mark all as final: If no further employee payments are to be made during the financial year, the pay event can be marked as final. When an employer reports the finalisation declaration during the financial year, this replaces the employer’s obligation to provide the employee with a part year payment summary. Making this declaration will update the employee’s myGov display to show the STP information from the employer is final for the financial year. Pre-fill information will not be available until after 30 June. When clicking on "Mark all as final", the below popup will appear. Upon clicking "Accept", the "Is Final" checkbox will be automatically ticked for all employees in the pay event. If this was selected in error you can cancel the finalisation by clicking on Actions > Mark all as not final. N.B. Employees who were previously marked as "Is Final" (because of a termination pay) will remain marked as "Is Final". Screen_Shot_2018-07-18_at_16.31.07.png
  • Mark all as not final: This action will only appear if there are employees in the event marked as "Is Final". Selecting this option will remove the checkbox from those employees, thereby denoting that the employees will still be receiving payments in that financial year.
  • Add Employee: This action allows you to add employees missing from the pay event. You can only add employees that have been excluded because of validation issues, however the system will only allow you to add them if the validation issue has been rectified.
  • Request Client Authority: This action will only appear to businesses that are using Tax/BAS Agents to submit STP information to the ATO, as determined via their ATO Settings. A Client Authority may be required if (a) there is no Standing Authority or (b) this event does not cover a standard pay run and so the employer must provide a declaration to the agent approving the lodgement. When clicking on "Request Client Authority", the following popup will appear and should be completed as follows: Screen_Shot_2018-07-03_at_13.42.30.png
    • User: When you click your mouse in the User field, a dropdown list of full access users and users with STP Pay Event Approver permission will appear. You can select one or more of these users to request client authority from. Take note that only one person is required to approve the event lodgement. Instructions on how to set up a user with STP Pay Event Approver permission can be found here.
    • Notes: You can enter any notes here that you want the Client Authority to read when they are sent the request notification email. For example, advising the authoriser that the pay event relates to bonuses or commissions made for the month, etc.

    When you click on "Submit Request", a notification email will be sent to the assigned Client Authority and the lodgement status will change from "Created" to "Waiting on client authority". The process thereafter is detailed further below.

  • Refresh Data: This action can be used to refresh the payroll data contained in the pay event. For example, if you have unlocked a pay run (for an event that has already been created), changed employee payroll figures, finalised the pay run and then chosen to lodge with the ATO at a later date, you would then go back to the pay event and refresh the data to ensure it up to date with actual payroll figures. 

Client Authority required to action a Pay Event

An assigned client authority will be notified that they are required to action a pay event via email. The email will include a link to the pay event: Screen_Shot_2018-07-03_at_18.40.17.png

The client authority, when clicking on the link, will be directed to the same information as the user who made the request but can only perform the following actions:

    • Approve lodgement; or
    • Reject lodgement; and
    • Export an excel report of the pay event. 



If the authoriser rejects the lodgement, they will need to add a reason for the rejection. Screen_Shot_2018-07-03_at_18.52.13.png         

An email notification will then be sent advising them the pay event has been rejected and the reason why. If you sent a request to more than one client authority, there is still the opportunity that another client authority approves the lodgement. However, if you have not, you will need to send another client authority request. N.B. You cannot send the request again to the same client authority who rejected the lodgement.  


When the authoriser approves the lodgement, they will be required to complete a declaration, that will appear in the form of a popup: Screen_Shot_2018-07-03_at_19.01.43.png

The client authority will need to select the checkbox and then click on "Approve Pay Event". Once this is done, an email notification will be sent advising the lodgement has been approved. The lodgement status will change from "Waiting on client authority" to "Client Authorised" and you can now start the lodgement process.

N.B. To clarify, the requirement for a Client Authority approval is only required for businesses using a BAS/Tax Agent to submit STP lodgements to the ATO on their behalf. 

Lodging a Pay Event

To lodge a pay event, click on "Lodge with ATO".

Side note: At this stage, if Two-Factor Authentication has been set up, you will be required to enter the verification code sent to you before you can proceed any further. You know this will be required when the following popup appears:


A lodgement declaration will appear in a popup that needs to be completed before the lodgement is complete. The instructions here are different depending on your ATO Settings:

I will be lodging reports to the ATO as the Employer 

The following popup will appear:


Tick the declaration checkbox and then click on "Lodge Pay Event". The lodgement is then queued for ATO submission.


I will be lodging reports to the ATO as a registered Tax/BAS Agent

The following popup will appear:


When completing the "Using authority" requirement, the dropdown list will show you any Standing Authority, along with any Client Authority who has either rejected the lodgement and/or approved the lodgement. You cannot select the authority who has rejected the lodgement. You should only be selecting a Standing Authority or Client Authority who has approved the lodgement. If there is no Standing Authority or Client Authority who has approved the lodgement, you cannot proceed with the lodgement and will need to obtain that authotity beforehand.

Once the relevant authority has been selected in the dropdown list, the only requirement thereafter is to tick the declaration checkbox and then click on "Lodge Pay Event".   

This ATO setting does not prevent a business owner from lodging pay events with the ATO (so long as they are a full access user). The only difference here is the business owner will need to select "Business Owner" from the "Lodge as" dropdown list. This will then remove the "Using  authority" requirement. The business owner then needs to tick the declaration checkbox and then click on "Lodge Pay Event":



I will be lodging reports to the ATO as an intermediary for multiple Employing Entities 

The following popup will appear:


Tick the declaration checkbox and then click on "Lodge Pay Event". The lodgement is then queued for ATO submission. 

Deleting a Pay Event

Pay events cannot be deleted.


This video will show you these steps as well: STP - Create and Lodge a Pay Event


Our complete STP Guide can be found here.

If you have any questions or feedback, please let us know via


Powered by Zendesk