Settings and activity
39 results found
-
148 votes
Hi everyone, we appreciate all the attention and interest this idea has received. This has not gone unnoticed and our product team understand the importance of these estimates for practices.
There is a bit of complexity involved in being able to achieve this, but we'd like you to know this is something our teams are looking into.
As soon as we have any updates we'll be sure to share with you all through this idea. Thanks 🕵️
Xero Ideas at GT
supported this idea
·
-
5 votes
An error occurred while saving the comment Xero Ideas at GT
supported this idea
·
-
30 votesXero Ideas at GT
supported this idea
·
-
19 votesXero Ideas at GT
supported this idea
·
-
574 votes
Hey everyone, thanks so much for sharing all your ideas and detailed suggestions for a comprehensive Audit Trail Report.
Through some of the comments in this discussion we wanted to highlight the Journal Report that may help with visibility of detail some are after. We've taken on board your thoughts on how this could be enhanced, like including an 'edited date' column and improving the export to Excel, however this is not in the roadmap right now.
Being open, providing a complete audit trail of every single event and change within an organisation is not in our plans.
That said, it’d help to gather interest in specific items you'd like to see added within the history and notes and I've shared links to a few ideas that have already been started on the platform. We welcome you to add your vote, or start a new idea for those that'd be…
Xero Ideas at GT
supported this idea
·
-
154 votes
Thank you for your engagement and feedback on this idea. We’ve seen some great suggestions in this thread on how a password-protected lock date could work. The current lock date feature prevents new transactions from being entered and can only be removed by Advisor level users, but we recognise that some users would benefit from introducing password protection.
As part of our new Xero Product Idea process, we have recently reviewed the idea and shifted this to “Accepted”. This reflects that this is an idea we’d like to develop, but that this isn’t currently on the roadmap. We'll be back with another update as soon as we have more to share.
An error occurred while saving the comment Xero Ideas at GT
commented
Would prefer to have the ability to specifically give / remove this access to certain users only, not a password as it could get difficult for accountants and advisors to manage and keep track of different passwords across all clients.
Xero Ideas at GT
supported this idea
·
-
159 votesXero Ideas at GT
supported this idea
·
-
34 votesXero Ideas at GT
supported this idea
·
-
46 votes
Thanks for sharing your interest in single sign on across Xero's products. This is available currently across many areas or Xero. For example if you are logged in and working in Xero, then move across to Xero Central(our support hub) you may need to click the login button in the top right of the screen but if you're session hasn't ended you should find the page should refresh and automatically log you in.
We appreciate wanting a smoother login experience that's recognised across all Xero products and will share if there are any improvements planned around this with you all, here.
An error occurred while saving the comment Xero Ideas at GT
commented
Enterprise grade single sign-on (SSO) capability is required. Not having this capability represents a significant risk of inappropriate access to client data. It also increases the administration cost of administering new staff and leaving staff.
Xero Ideas at GT
supported this idea
·
-
48 votesXero Ideas at GT
supported this idea
·
-
137 votes
Hi Community! Thanks for your active and on-going participation in this idea. The volume of comments and votes highlights how important more granular user permissions are for managing your payroll processes effectively.
Improving user permissions and providing greater control over sensitive data is a key area of focus for us. While we have no specific feature to announce today, your feedback is critical in shaping the future of this part of Xero.
Because of the clear need you've all highlighted and our desire to investigate this further, we're moving this idea's status to In Discovery.
During the discovery phase, our product team will be digging deeper into the core problems you’ve raised.
We appreciate your patience as we explore this. We'll be sure to update this thread when we have more to share. Thank you again for helping us understand what matters most to you.
An error occurred while saving the comment Xero Ideas at GT
commented
Currently, to be able to access Payroll reports, we need to give staff full access to the client's Payroll system, due to the lack of security options available in this area. This is a significant risk issue. We should not be giving our staff access to client’s payroll due to privacy and risk issues. The payroll system contains personal information about the client’s employees, including TFNs and DOB, which we do not need to perform our services. Further, access to Payroll allows staff to perform pay runs, change employee bank account details etc.
Xero needs more detailed security in this area to allow staff access to certain payroll reports, without access to the full payroll system.Xero Ideas at GT
supported this idea
·
-
19 votes
An error occurred while saving the comment Xero Ideas at GT
commented
Role based security is fundamental to any user based system and is required to properly manage user access efficiently and effectively, particularly when there are hundreds of users.
This is a risk issue and also creates additional work.Xero Ideas at GT
supported this idea
·
-
1 voteXero Ideas at GT
shared this idea
·
-
10 votesXero Ideas at GT
supported this idea
·
-
22 votesXero Ideas at GT
supported this idea
·
-
202 votes
Hi everyone, thanks for your feedback here. It’s great to see so much engagement on this idea, and we appreciate you taking the time to share your thoughts with us.
We understand you’re looking for the ability to create your own report code structures within Xero that'd allow for more detailed and flexible reporting, helping to automate processes and provide clearer insights for your clients.
As noted by others in the idea, you can currently leverage the existing report code mapping functionality. While it doesn't allow for entirely new report codes, you can map multiple chart of account codes to the same report codes to group them for reporting.
To do this in bulk, you can also export your chart of accounts, apply the mapping in a CSV, and then re-import it.
We see the value in providing more customisation in reporting. Right now we have some more codes…
Xero Ideas at GT
supported this idea
·
-
25 votesXero Ideas at GT
supported this idea
·
-
1 voteXero Ideas at GT
shared this idea
·
-
43 votes
An error occurred while saving the comment Xero Ideas at GT
commented
We have a number of clients who have multiple branch numbers yet we are not able to lodge their activity statements in Xero. A tax system should be able to handle this common scenario. The work arounds are not acceptable as they cause inefficiency and quality/ risk issues.
Xero Ideas at GT
supported this idea
·
This function is required across all financial reports eg compilation report so we don't have trustee(s), directors(s) etc which looks so unprofessional.
Basic function but is critical if presentation and correct grammar is important to you.