Changing payroll software mid-year and transitioning STP records
This blog was updated on November 22, 2021
In 2019, it became mandatory for all Australian businesses to begin STP reporting. As a result, payroll systems had to build an STP reporting component into their software; or risk falling behind and losing customers to more advanced software. Since the initial roll-out, the Government announced that STP would be expanded (STP Phase 2) to include additional information and reduce the reporting burden for employers and registered agents providing payroll services.
If you’re reading this, you’re likely to be trying to understand the impact of STP Phase 2 requirements and how payroll software providers are preparing for the mandatory start date for Phase 2 reporting: 1 January 2022.
What if a business is not using KeyPay, but thinking about changing over payroll software?
It can be a pretty frustrating task migrating to a new payroll system. Most businesses make the decision to transfer at the start of the financial year to simplify the process as much as possible. Alternatively, when transferring to another payroll system during a financial year, businesses need to consider the following:
- Bringing across data for active employees only or employees terminated with the financial year also
- Bringing across YTD payroll figures or start anew
- How to transition STP
All the above questions are interrelated and basically determine the response to the last question.
There are several ways to transition STP reporting from one payroll system to another. All transitional options relating to STP, when migrating over to KeyPay during a financial year, can be found here. I’m sure you’re asking: what’s the ‘cleanest’ option? Which one will minimise any impact on existing records reported to the ATO? We’re happy to tell you...
Transitioning STP records to KeyPay using an existing BMS ID
The prerequisite of using this option is that the business brings across their employee YTD payroll data to KeyPay. Why would businesses bother doing this? Firstly, it allows for consolidated financial year reporting - if YTD data was not brought across, the business would have to generate reports from the previous and current payroll system and then merge the reports together… nightmare!!! Secondly, it allows employees to see correct YTD data on their pay slips.
So, if the decision has been made that importing YTD payroll data is the best way to go, the process of using the previous BMS ID to report STP going forward in KeyPay is as follows:
- Change the BMS ID in KeyPay to that of the previous payroll system's BMS ID;
- Copy over the employees' payroll ID used in the previous payroll system to the STP Payroll ID field in KeyPay. This is done easily using our employee import/export feature;
- Import YTD figures into this payroll system using the opening balances feature;
- Lodge an update event to report the YTD totals imported or alternatively wait to lodge the first pay event as this will include the imported YTD totals for the employees within that pay run.
Detailed instructions on how this process works can be found here.
What are the benefits of transitioning STP records using an existing BMS ID?
There are quite a few. They are:
- There will be only one record showing in the employee’s myGov account. Although a second record is not the end of the world, it’ll minimise any employee confusion or concern about why there is a second record to begin with.
- Not having to worry about creating a $0 event in the previous payroll system. If a business migrates to KeyPay and brings across the YTD payroll data, any STP events reported in the previous payroll system must be wiped out in order to not over report employee payroll data. This would require lodging an event in the previous payroll system that reverses all YTD data already reported to the ATO.
- The finalisation process only needs to be done once. At the end of financial year, a finalisation event will only need to be created in KeyPay (and not in the previous payroll system also) and reconciliation will be easy as all payroll data is stored in KeyPay.
If your clients are unsure about how their payroll software provider is meeting STP Phase 2 requirements or are just looking to make the switch - they don’t need to wait until the new financial year to change providers. Our opening balances feature alongside the STP Payroll ID field making it a much simpler process, and removes the migration dread.
If you have any questions about managing STP with KeyPay or want to discuss any of your clients' payroll scenarios, please don't hesitate to get in touch.
Looking to find out more about how KeyPay has prepared for STP Phase 2? Take a look at our support articles.
Disclaimer: The information in this article is current as at 1 June 2022, and has been prepared by Webscale Pty Ltd (ABN 70-154-693-955) and its related bodies corporate (KeyPay). The views expressed in this article are general information only, are provided in good faith to assist employers and their employees, and should not be relied on as professional advice. The Information is based on data supplied by third parties. While such data is believed to be accurate, it has not been independently verified and no warranties are given that it is complete, accurate, up to date or fit for the purpose for which it is required. KeyPay does not accept responsibility for any inaccuracy in such data and is not liable for any loss or damages arising either directly or indirectly as a result of reliance on, use of or inability to use any information provided in this article. You should undertake your own research and to seek professional advice before making any decisions or relying on the information in this article.