AU Payroll | Lock ABN in Organisation settings once STP filed
I would like Xero to automatically lock the ABN on a client's file after the first STP event has been lodged. This will prevent clients changing the ABN when they change the entity's structure and reporting STP incorrectly across two ABNs. Undoing this mess is a nightmare.
Thanks for your feedback so far, everyone.
We're currently looking at ways we could help fix double counting for issues at the ATO that have been made due to changes made to an organisation's ABN/Branch number and it'd be great to get input and further feedback from some of you here to help us understand and solve these issues.
📝If you're interested in participating in this research and would be available to connect (this week) on 24th or 25th November 2022 - Please click through and complete this short survey. Thanks 🙂
-
Janette Wheatley commented
It would also help for reporting purposed; especially to Govt departments; if the ABN printed on Payroll Activity reports etc.
Actually it wouldn't hurt for it to print as part of all Xero reports by default.
As part of the report header information. -
Megan Velo commented
For data keeping accuracy this is critical
-
Toni Thompson commented
Lock ABN and Company Type
-
ALISON GILBERT commented
Lock ABN & Company type. New ABN, new file. It’s a headache for Bookkeepers & Accountants.
-
Edward Henry FIPA FFA commented
Each ABN is a separate legal entity so can only belong to one Xero file.
Both the ABN and legal entity type (eg sole trader, partnership, company) belong exclusively to each other and should be represented by separate Xero files and once set up not be allowed to change to prevent client disaster. -
Michele Grisdale commented
Lock abn and company type.
-
Cassandra Ferris commented
This is a critical change to ensure that clients do not use the same file for different entities.
-
Andrew Syme commented
BUT, it would help if we could CLONE the current setup of a file into a new File.
-
Tori van der Donk commented
Having had the experience of trying to fix and relodge STP finalisation for a client who went ahead and changed ABN and then continued filing payroll under new ABN, this is very important. It was a very painful and fiddly process to fix this in the small window between payruns. I hope never to do this again, no matter how much the client pays me.
-
Michele Grisdale commented
Love this! So many small businesses come to me after having done this and it is a mess!
-
Edward Henry FIPA FFA commented
I believe this is critical. There have been so many questions about needing to start a new file for a new entity. This will lock it in. With the new STP2 requirements it would be a nightmare to fix when a client does the wrong thing.
I don’t believe it would be difficult to program. -
Paolo Coniglio commented
100% and so important with STP Phase 2 coming!
-
Cassandra Scott commented
This is going to become a far bigger issue with the expansion of STP2 - anything that can be done to mitigate payroll errors is highly valuable. While payroll reporting is one of the issues compromised if an ABN changes in a file, there are other issues that can occur as well. Best practice drives a single ABN to a single Xero file. Trying to manipulate a Xero file across 2 ABNs is fraught, and false economy