Voiding and deleting
Voiding cancels a real document and keeps it; deleting removes one that should never have existed, and only works on a draft or a voided document with nothing attached to it.
Voiding and deleting are different actions. Using the wrong one can leave a gap in your document numbers that is difficult to explain to an auditor.
Void — for a real document that went wrong
The invoice was raised, and it should not stand. Voiding cancels it, reverses the stock it moved, re-opens anything it settled, and keeps the document exactly where it was, at nil value, with the reason on it.
A voided document keeps its number, which is why it is not a gap in the sequence. Nothing was quietly removed, and the audit report can prove it.
Delete — for a document that was never a document
For example, a booking converted twice, or a duplicate created by accident. Voiding these would leave them in every list permanently. Deleting removes the document, but MOTION first records the whole document in the audit trail: every line, the totals, the customer, the vehicle, who deleted it and the reason given.
When delete is refused, and why
Only a draft or a voided document can be deleted at all. Beyond that, MOTION refuses anything the books depend on, and says which thing by name:
- a payment against it
- stock moved for it
- an inspection
- a courtesy car
- a line on a purchase order
- a line on a supplier invoice
- an online booking request
Deleting a document with any of these would leave a financial record without its source, so void it instead. Messages and reminders do not prevent a deletion: they are kept, because what was sent to a customer is a record in its own right.
Deleting needs the same permission as voiding, because it is the stronger version of the same act.