Enter your idea

So horribly confusing when an accidental entry is made. Having the record there results in wasted time for others who find them and don't know what has happened. There is no need to record a 'draft' entry of an invoice that never every existed but was done in error.

Please note this is NOT to remove a real invoice that needs to be deleted/voided which should be tracked. It is to remove a DRAFT invoice that should never have been created or recorded in the first place. It has no meaning or benefit to record AND it stuffs up our integrated products that use the sequencing numbers.

I would also like to see this functionality

Agree. They should still show somewhere but they are pointless on reports. I don't hold out much hope though, everything XERO "updates" just makes things even more clunky

to avoid confusion

Please set this up, as per previous comments this is important when invoices have been imported incorrectly and need to be removed completely, not to be able to permanently delete a void invoice is an issue.

Please please please implement this feature. It is crucial when invoices have been incorrectly imported from an API integration and we need to delete and then reimport the invoice.

My client is super annoyed this feature is not available as it has been in the past & she keeps sending me the tutorials saying so. Please add this feature back or remove all past training's so I can get some other work done.

This is required to help keep the whole system as clean as possible. If it is voided in error there must be a way of removing this.

Makes sense.

I have a question. If in the event some user unintentionally accidently deleted invoices, there should be a voided/deleted bin to hold the invoice say for six months before it is permanently deleted. Is there any audit trial of who action on this deletion for internal data integrity control of permanent delete function.

Agreed. This is a must. So annoying we can't everything looks so messy!

This is a must!

This would be helpful as there are times when clients change their minds and decide not to proceed. I end up with too many Voided invoices and it doesn't look good if Audited that there are so many Voided client invoices.

Perhaps if when choosing to delete there is a warning similar to Journal entries of the potential risk when deleting invoices.

It's a feature that would need a lot of caveats. If there was any interaction with that invoice e.g. sending it to a client, it really shouldn't be deleted.

And there should be a record of that invoice being deleted so there's an audit trail, even if the invoice doesn't appear in the list.

This would be great for those invoices you make by mistake, they should have never been made in the first place and to able to completely delete them is much cleaner. Also it prevents confusion in the future if or when you have to go back and look at something.

It would be good to have the option to delete completely. I have an invoice that was imported through another party with incorrect data on it. I am currently unable to fix the problem as only voiding the invoice will not let me submit the correct data

We have had an invoice created accidentally with sensitive info, it was accidentally voided without thinking and now that info is permanently in the xero file - we need to at LEAST be able to edit voided invoices (as you can at any other stage - ie maybe a "reinstate" so we can edit to remove this sensitive data, then re-void??!!

I always adjust any invoices I void to a zero balance with an explanation in the description and add 'voided' to the reference to avoid this problem, in case I have not excluded voided invoices when I run a report.
However, I would prefer that voided invoices are not deleted entirely as there should be included on audit reports

PLEASE DON'T DO THIS! It could potentially muck up the audit trail and open risk of a rouge Xero user decimating the system with nothing to back it up. THIS COULD GO HORRIBLY WRONG PLEASE NO!

Agree - very annoying feature that you can't fully delete it because you then have to check all reports to make sure you don't include voided transactions there too, otherwise they pull through