Void an unsigned Delivery Note

Withdraw an open note through the permission-protected status action.

What this guide covers

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.

Exact step-by-step process

1. Open 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. Confirm the success message and return to the register.
5. Verify status Void and the `void` event.
6. Create a replacement from the invoice only when required.

Fields, choices and supported possibilities

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

Code-backed validations and workflow rules

• 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.

Expected result and verification

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

Checks, security and troubleshooting

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

Related Delivery Note guides