Settings and activity
3 results found
-
51 votes
Thank you all for supporting and sharing back about the need to undo or revert changes to invoices, particularly where autosave can make accidental edits difficult to recover.
We want you to know that this is something we have longer-term plans to solve for.
While it's not in the pipeline just yet, we'll be sure to keep you in the know of any progress surrounding developments for the ability to undo or return to a previous state of an invoice.
Jett Benson
supported this idea
·
-
483 votes
Hi community, as mentioned in my last post we want to keep you looped in on changes around autosave.
Our product team has continued to focus attention on how we can make invoicing faster and more responsive to improve our customers' experience.
We've now optimised autosave to require less processing power, leading to faster invoice loading and saving.
While we don't have any plans to remove autosave, there is the possibility that we would make updates to improve experiences related to autosave in the future - I've provided links below to ideas that have been raised and remain open for consideration;
- Invoicing - Undo/revert to previous version of an invoice
- Exclude Auto Save from History and Notes
- Invoices - Add invoice number when invoice is Approved
Thanks again for all your feedback and sharing with us in the forums here.
Updated 10 Sept 25
Jett Benson
supported this idea
·
-
29 votes
Hi everyone, thank you to everyone that participated in our teams survey from my last update. We appreciate your insights and these continue to help inform our teams of where they can best focus their efforts, as they continue to develop invoicing.
We don't have any plans at this stage to increase the Description field character limit from 4,000, however we're interested to continue tracking the interest in community and understand what the optimal amount of characters would be for our customers.
If there are any changes we will share an update with you all, here.
An error occurred while saving the comment Jett Benson
supported this idea
·
An error occurred while saving the comment Jett Benson
commented
This is essential for our business also. This is where we record works carried out, sometimes over multiple weeks or months and therefore can't afford to be limited on characters.
How a 'new' invoicing system can be developed that includes a reduction in features is beyond me.
Often we required 10,000 characters but on occasion have needed up to 30,000.
@Kelly M, in addition to the 4,000 character description limit per line, what other restrictions are you forcing on us when you remove the functional 'classic invoicing'?
Do you have a list of what functionality us users will lose or are we expected to find out for ourselves when things don't work as well as they used to?