Void an unsigned Delivery Note

Withdraw an open note through the permission-protected status action. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

What you’ll accomplish

Withdraw an open note through the permission-protected status action. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.

Follow these steps

1. Go to and verify the note is unsigned.
2. Obtain approval to withdraw it.
3. Invoke the supported void controller action from an authorised interface or controlled request.
4. Verify the success message and return to the register.
5. Check status Void and the `void` event.
6. Create a replacement from the invoice only when required.

Fields and options to review

• Note ID
• Delete capability
• Existing status must not be signed

Rules the system enforces

• The controller uses Delete permission for voiding.
• The model returns false for a signed note.
• Void updates status and updated_at; it does not delete the row.
• The supplied admin detail template does not render a visible Void button.

How to confirm it worked

• The note remains auditable but no longer acts as the invoice’s active public delivery note.

Safety checks and troubleshooting

• Do not add an undocumented hard-delete action or tell users to look for a button the supplied view does not contain.

Continue with related guidance