Update Events

Overview

Update Events help you report corrections to your payees data held by the ATO for given a financial year(s).

The ATO only expect an Update Event to be used in the following scenarios:

1. Your organisation started using PayGlobal part-way through a financial year AND you imported your YTD amounts from your legacy payroll system.
2. Your organisation has multiple PayGlobal databases where employee(s) and their related YTD amounts have moved between databases.
3. Your PayGlobal database services multiple payers (i.e. many internal company records with different ABN/ATO branch numbers) where employee(s) and related YTD amounts have moved between payers, i.e. you changed the employee's pay period code to one with a internal company linked to a different payer OR you edited the ABN/ATO branch number fields on an internal company record(s)
4. An employee(s) who need data corrections for the current financial year is not expected to be included in the next pay run.
5. An employee(s) who need data corrections for a previous financial year.

For scenarios involving the transfer of YTD amounts, please engage with the Professional Services team to help ensure all required database tables are correctly updated BEFORE sending an Update Event to the ATO.

Any corrections to YTD amounts must be completed in a pay BEFORE sending an Update Event to the ATO.

The Update Event does not include Payer totals. If the very last pay requires the corrections to payer totals then using PayGlobal's Rollback pay feature might be an option - see Full File Replacements. Otherwise you must contact the ATO directly. For further details see Reporting corrections

Limitation: PayGlobal can only cater for 1000 employees per Update Event submission. If you have payers with more than 1000 employees, it is recommended to setup employee queries in blocks of 1000 to be used in the STP Manager Tool Updates tab

Topic: 44516