Settings and activity
106 results found
-
797 votes
Hi community, we appreciate your continued feedback on having different default email addresses for various transaction types in Xero contacts, and the manual steps involved to ensure you're communicating with the right person for different purposes.
Currently, one way of managing this in Xero would be to include every additional person on a contact record in emails, and then removing those that aren't required when sending each transaction. However we totally get this isn't the ideal solution.
While being able to set different email addresses for differing transaction types is something we want to address longer term, like the idea for multiple addresses work for this feature requires cross-collaboration between teams in order to achieve.
Once the multiple addresses feature is live this is something we'll be able to consider more closely and provide further updates on.
We do regularly review all ideas here, and your input is vital. We'll…
Jon Shepherd
supported this idea
·
-
268 votes
Hi everyone, we appreciate your support and feedback for having a Repeating Invoices Report.
We know that not having a dedicated report for your repeating invoices can present limitations when trying to forecast sales.
As noted by others in the idea, while not a complete solution there is the Receivable invoice detail report, that will provide results for invoices that have already generated from a repeat invoice template. There is also Short term cashflow predictions in Xero Analytics Plus that can predict recurring cash transactions based on the past 3 months reconciliations.
For more comprehensive forecasting, some users have found third-party apps that integrate with Xero to be helpful - You can view the full suite of official apps on our Xero App store.
While we understand these aren't ideal long-term solutions, I want to let you know that there's no work currently planned to develop a specific…
Jon Shepherd
supported this idea
·
-
34 votes
An error occurred while saving the comment Jon Shepherd
supported this idea
·
-
73 votesJon Shepherd
supported this idea
·
-
344 votes
Heya team, we're now actively testing how reports could be grouped and accessed, and we'd love your input in this, so we can design a better report grouping structure that supports role-based access in reporting.
Get involved! Complete a quick 15-min online activity to test how reports are grouped and accessed:
- Part 1: answer questions about the current report grouping
- Part 2: explores a new grouping and role-based report access
👉 If you're interested, please go through the link here.
Thanks again for your support and contributions to developing a solution that works best for majority of our customers!
(Just to note - If you’ve already gone through this activity, there's no need to do it again — our researchers may have contacted you earlier 😊)
Jon Shepherd
supported this idea
·
-
31 votesJon Shepherd
supported this idea
·
-
54 votes
Thanks for your patience, it’s been a little while since you raised this idea, so we wanted to check in. We've now reviewed this idea and have moved it to Gaining Support status. Our product team are keeping an eye on this idea. We update you if this gets added to the product road map in the future.
In the meantime, it may be useful to note that the classification field is an editable field and is included in the remuneration report.
Jon Shepherd
supported this idea
·
-
81 votes
Hi everyone, thanks for your feedback on adding employee numbers to employee records.
Currently Xero uses unique identifiers for employees which are included in STP files sent to the ATO, however there’s currently no ability to add employee numbers to employment records.
After reviewing with our product team, this feature isn't currently on our roadmap so we'll update the status to 'Not in Pipeline'. As an alternative, payroll admins can use the Notes section or adapt an existing field in the employees record to assist with identifying employees.
Whilst we understand this may not be the outcome you’d hoped for, we appreciate you taking the time to provide us with feedback to help shape Xero.
An error occurred while saving the comment Jon Shepherd
commented
Would love to see this added. While each employee does get a unique identifier, it's not user-friendly.
Jon Shepherd
supported this idea
·
-
9 votes
An error occurred while saving the comment Jon Shepherd
commented
The customer statement screen should show the date that the statement was last sent or exported from Xero. This will enable users to quickly see who has recently been contacted/provided with a statement, and who needs to have them issued. There is sufficient white-space on the screen to allow this, and the information is already stored under the contact history.
Jon Shepherd
supported this idea
·
-
130 votesJon Shepherd
supported this idea
·
-
6 votes
Hi team, while this isn't something we have any direct plans around atm we appreciate the feedback here and will continue to track the support this idea receives. I will be sure to let you know if there are any updates to accommodate this styling of reports in Xero.
Jon Shepherd
supported this idea
·
-
15 votesJon Shepherd
supported this idea
·
-
32 votes
Hi everyone, thanks for your continued engagement on this idea. We want to be upfront that there is currently no planned work to modify bank account notifications.
The current setup is in place as a critical layer of security. We understand this means all payroll admin are notified of bank account changes, but maintaining robust security remains a top priority.
Although it isn’t on our immediate roadmap, we will keep monitoring your feedback and use cases, and we’ll update this thread if things change.
Jon Shepherd
supported this idea
·
-
184 votes
Hi everyone, thanks for sharing your thoughts on this! With Payday Super legislation now active, superannuation contributions align directly with regular pay runs. Because of this shift to real-time processing, quarterly due date reminders are no longer necessary.
To assist with compliance under the new legislation, we have added reminder prompts directly to the super payment page to highlight which accruals are at risk of being late.
As a result, we won't be moving forward with quarterly reminder updates for this request. We really appreciate everyone’s feedback on this topic, please continue to share your ideas on how we can keep improving your Xero experience!
Jon Shepherd
supported this idea
·
-
38 votes
Thanks for sharing your idea, and letting us know the changes that matter most for you.
To help your idea gain traction, please share it with colleagues so they can vote for it too. The comment section is also open for all members to share how this feature would improve their Xero experience.
Jon Shepherd
supported this idea
·
-
145 votes
An error occurred while saving the comment Jon Shepherd
commented
I agree, this would be handy. My workaround for this is to mark DD bills as paid with payment coming out on the day of the direct debit.
Jon Shepherd
supported this idea
·
-
10 votesJon Shepherd
shared this idea
·
-
17 votesJon Shepherd
supported this idea
·
-
61 votesJon Shepherd
supported this idea
·
-
100 votes
Hi team, thanks for sharing detail of the value in this idea in the ways you invoice.
We've just released a new line item grid in invoicing which includes the ability to manually add blank rows and shift these to where you're like them placed in your invoice.
That said, I want to be transparent in how this works - When you save your invoice any blank lines will be removed. So, if you'd like blank lines to help break your invoice into sections, you'll need to enter a character in the Description field of the blank line. Even a full stop '.' or dash '-' would suffice.
Jon Shepherd
supported this idea
·
Add the option to filter reports by is not/does not equal. Currently the only option is to filter where the value does match. When there is a need to filter out a single payment type, or worse, a contact, from a report the filters show thousands of included rows in the description, and not just the one excluded.