Tax Manager - Remove 'Ready to Start' tax returns from existing jobs
"Ready to Start" tax returns should not show up in existing jobs. We have all these tax returns that are showing up in Job that are not related to the client, Individual Tax Return showing up under an Activity Statement Job for a company that is completely unrelated. If they tax returns placeholder is going be added it should only appear under the client tax return tab, not in an existing Job. And there should be away to turn it off.
Christopher Sykes
shared this idea
Hi team, taking on board feedback there are several changes our team are working on to solve the pain points raised by customers around 'Ready to start' returns within new Tax Manager.
To give an idea of what's coming - we're working to;
- only show ready to start returns on "active" jobs
- limit ready to start returns to 25 on a page
- change for identify related clients to only be where there is a relationship or they're in the same "taxable" client group
I'll keep you updated here as these changes are implemented.
-
Patrizia Capolingua
commented
I agree. This has created more work, caused confusion and increases the risk of mistakes being made.
I will be raising a case with Xero Support to have this feature disable for our practice.
-
Judy She
commented
Agree. This is creating unnecessary admin work. We don't prepare superfunds on Xero tax so I don't need it to appear on the automatic quarterly BAS Job!
-
Kara Pursell
commented
I agree with this as well. All the group's entities are getting mixed up on the jobs that they shouldn't be on. Very confusing.
-
Rochelle Louden
commented
Even when a job is closed and archived, unrelated entities are still showing in the archived job.
If you then click on one of these unrelated entities, it is automatically added to the job, despite having no connection to that client.
It looks like the system is now reading client types rather than client groups, which is causing entities to be pulled in incorrectly.
This needs to be fixed urgently.
At this point, there is no trust in XPH/XPM. We cannot tell what is feeding into what. There are duplicates everywhere, basic controls are missing, and functionality has gone backwards.
As an accounting practice, this is extremely concerning. We are worried about:
incorrect client information appearing where it shouldn’t
jobs including entities with no relationship to the client
the risk of information being incorrectly displayed or shared
This is not just frustrating — it is a practice risk!
-
Lachlan Bonser
commented
Agreed with this and it has cause a lot of unnecessary confusion among the team... In my view this is not an efficiency/work flow feature that needed to be implemented. How XPM dealt with / showed the returns pre UX changes was workable... this new way is not.
I would like to see only the tax documents that relate to the specific client not the group. -
Kylie Barratt
commented
this is AWFUL and very confusing - pls fix this! It is adding tax returns of other entities in the group that should NOT be on the job.
-
Craig Shields
commented
I agree with this. I look at old jobs (ie last year) to see what entities to include in current year jobs, and now it includes all ready to start tax returns in that group. i dont want see everything possible in the group at that stage, i want to see what was included in that completed job only. Just because its in the same group, doesnt mean it will be included in the same job.