STP - Lock ABN once first 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.
Kate Underhill
shared this idea
-
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
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