Module setup, access and architecture

Delivery Note module overview

Understand how invoice-linked delivery notes, secure recipient signing, PDFs and compliance events connect.

Audience: Administrators and authorised operations staffPermission: Delivery Note: ViewModule v1.0.0
Exact navigationAdmin Area → Delivery Note

What this guide covers

Understand how invoice-linked delivery notes, secure recipient signing, PDFs and compliance events connect. 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 the Delivery Note register.
  2. Use invoice actions to create or open a note.
  3. Send the secure recipient link through the automated dispatch email or QR code.
  4. After signing, review the sealed note, PDF and compliance events.

Fields, choices and supported possibilities

  • Source invoice and client
  • Invoice item snapshot
  • Delivery details and recipient
  • Secure token and public link
  • Status: open, signed or void
  • PDF, QR code and event timeline

Code-backed validations and workflow rules

  • The module owns its own records and does not add columns to the core invoice table.
  • Only one non-void delivery note is returned for an invoice.
  • Signing is one-time; a signed record is locked.
  • The supplied code contains no cron, webhook or reporting subsystem.

Expected result and verification

  • Staff can trace a delivery note from its invoice through recipient confirmation and retained evidence.

Checks, security and troubleshooting

  • Use the invoice for commercial values; the delivery note records delivery evidence and item quantities, not prices.
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.