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.
These look like the same thing and are not. Reaching for the wrong one is how a workshop ends up with a hole in its numbering that nobody can 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
A booking converted twice, a duplicate somebody made by accident. Voiding one of those leaves it in every list for ever, which is clutter rather than a record. Deleting removes the row — but MOTION writes the whole document into the audit trail first: every line, the totals, the customer, the vehicle, who deleted it and the reason they gave.
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 one of those would orphan a record that answers for money. Void it instead. Messages and reminders do not block a deletion — they are unhooked and kept, because what was said 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.