Settings and activity
9 results found
-
14 votes
An error occurred while saving the comment 
Charles Hewitt
supported this idea
·
-
9 votesCharles Hewitt
supported this idea
·
-
97 votesCharles Hewitt
supported this idea
·
-
174 votes
Hi team, I know it's been sometime since this idea was initially raised and we wanted to update you all here.
We appreciate and understand why some businesses would prefer the acceptance of a Quote be sent to the organisation's reply to email address, rather than the user that initially created the Quote.
While our product team have reviewed and are attentive to your interest in this, we want to be upfront that this is not something we currently have direct plans for changing the behaviour of.
Our team will continue to review this idea and when we're in a position to assess notification and communications for Quotes, we'll share if there are any updates around this, here.
Charles Hewitt
supported this idea
·
-
1,177 votes
Hi community, we understand your needs in this feature and want to assure you were taking on board all your feedback.
As many of you accustom to this idea will know, multiple addresses requires a complex solution. It's been something we’ve been moving towards for some time and we’ve done a lot of back end work that will allow us to bring it to you in the future.
We have 12 different products within Xero that rely on contact data, as well as many of our app partners. This means that contacts need to seamlessly flow across technology, products and all connections on Xero. And that’s exactly what we’ve been working on.
One of the reasons we announced the retirement of classic invoicing is because many of the features being asked for, just can’t be brought into classic invoicing. The old technology has too many technology limitations to enable this.…
An error occurred while saving the comment Charles Hewitt
commented
Some really good points here from @SamBond...
I would strongly recommend using the xero api to address these needs.
It is relatively straight forward now to create web pages that interact with the Xero api (which is well documented) and design pages to do just the type of thing you are describing.
It is not ideal and you would expect a competent accounts package to offer the features you are describing.I run a complete subscription and renewal package via an api web interface, the subscription and subscriber data is stored in a separate database and it links to invoices and quotes raised in xero, I am slowly expanding it to include account interactions like sending reminders and accepting quotes and purchase orders.
This leaves xero to handle the transactions and manage the financial accounts - rather than let it get too close to my business.
In the attached screenshot of my online subscription business I can see overdue invoices, expiring subscriptions and subscriber status in one shot with all the payment, quotes and invoicing data linked to xero and new quotes are automatically generated in xero when required.
An error occurred while saving the comment Charles Hewitt
commented
Really helpful to have a customer field for how to present an invoice.
Many of our customers use various supplier portals (each with their own url and login details etc) others require invoices to be sent to a specific email address. It would be very helpful to have a free text field in the Customer attribute to allow us to record how invoices should be presented to the specific customer. The field should be large enough to support a URL, username and password and some free text if necessary.Charles Hewitt
supported this idea
·
-
662 votes
Hi everyone, as another step toward improving history of new invoicing you'll find you'll now see an entry when an invoice is sent, and the email address it has been sent to.
We appreciate this is something we've heard a fair amount of feedback on and we hope helps in your journey to using new invoicing.
We still have more enhancements on the way for history and I'll be back again when more updates land.
An error occurred while saving the comment Charles Hewitt
commented
Same comment repeated again and again in this thread since Jan 2024...
Notes History no longer includes emails and addressees.
This is a _serious_ retrograde step from old Invoice.
Having the email and the addressees included in the Notes History is essential for establishing the evidence for late payment claims.If you insist on trying to add an improvement then include the template name used for the email in the note.
Charles Hewitt
supported this idea
·
-
782 votes
Hi team, now in 2025 and many here will have received our recent communication leading up to the retirement of classic invoicing on 27 Feb this year.
We’re continuing to work hard on delivering more features within new invoicing that’ll help most in your workflow.
Thanks for staying engaged with us on changes that’ll help you through the idea here.
To give an update on recent deliveries that positively impact some of you that have shared on the idea here. Late last year we released improvements to the issue and due date fields so you can now use all the date entry shortcuts that were available in classic, and we made it simpler to access the date picker. We also updated the Files attachment modal so you can now drag & drop files anywhere on the page, and when you use tracked inventory you can see the number of items…
An error occurred while saving the comment Charles Hewitt
commented
Notes History no longer includes emails and addressees.
This is a _serious_ retrograde step from old Invoice.
Having the email and the addressees included in the Notes History is essential for establishing the evidence for late payment claims. -
218 votes
Hi community, thanks for getting involved here and letting us know the importance around being able to see the details whenever an invoice is sent from Xero. We understand the importance of this to our customers and our product team are beginning to review this idea to solve needs in this space. We'll move to Under review and I'll let you know as there's more progress here. Thanks
An error occurred while saving the comment Charles Hewitt
commented
In case anyone is in any doubt this is a critical invoicing feature.
If new Invoice wanted to make and improvement then add the template name used to generate the email as well as including the email addresses it was sent to.
Charles Hewitt
supported this idea
·
An error occurred while saving the comment Charles Hewitt
commented
This is a _serious_ retrograde step from old Invoice.
Having the email addresses included in the Notes is essential for establishing the evidence for late payment claims.It is likely any claims we make for late payment under the new invoicing view will be much harder to make stand and this will cost us money and time to resolve - we may well have to remove all our invoice communications out of Xero and just use the API from our own web app.
-
153 votes
Hi community, thanks for your interest in this idea. Just wanted to pop in here to share, for those who aren't already aware, that you can export the Receivable Invoice Summary report. The report has a 'Last Payment Date' column that you can add to it which is useful for finding customers who habitually pay late so that you can take appropriate action.
To be transparent, building a feature to show the average days to pay by customer isn't on our roadmap at this time, but we'll be sure to update this idea if that changes in future.
An error occurred while saving the comment Charles Hewitt
commented
We like to understand how effective the different stage of our account receivable process is, to do this we need to know the proportion of invoices that are paid at each stage:
Average proportion paying within a range of days for a given reporting period ie 35% < 5 days, 30% 6-30 days, 15% 31-60 days, 10% > 60 days etcCharles Hewitt
supported this idea
·
This is about the only 'event' generated in the app that requires action - yet there is no notification in the app - it relies on an email.
Why does this event (quote accepted) not show in the 'notifications' - I am not sure what notifications is for if not for this type of event.