Understand one active Delivery Note per invoice
This guide explains the model rule that prevents duplicate non-void notes. 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.
Where to goAdmin Area → Invoices → Open invoice → Create or View Delivery Note
What you’ll accomplish
Understand the model rule that prevents duplicate non-void notes. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- Go to the invoice.
- Use the Delivery Note action.
- If a note exists, review or edit that record rather than creating another.
- Void the unsigned note only when replacement is authorised.
- After voiding, use Create Delivery Note to make the replacement.
Fields and options to review
- Active lookup excludes records whose status is `void`
- Invoice resolver redirects to existing active note
- Creation hook checks for an existing non-void note
Rules the system enforces
- Open and signed notes are treated as active.
- The database does not enforce a unique invoice ID; the application model enforces the active-note rule.
- Direct database inserts can bypass this control and are unsupported.
How to confirm it worked
- Normal code flows maintain one current non-void note for each invoice.
Safety checks and troubleshooting
- Do not duplicate delivery evidence to correct a typo; edit an open note or use the approved void-and-replace process.
Stay within the supported flowDo not force database values, expose secure tokens, bypass permission checks, replace a stored signature or invent a status or interface that the supplied code does not implement.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.