If you have ever worked on an internal tool for a business that ships physical goods, invoicing, inventory, order management, you have probably brushed up against delivery notes without giving them much thought. They look like a boring paperwork detail. They are not. Let me explain why.
The document, not the invoice
A delivery note is the document that travels with a shipment. It lists what was sent and in what quantity, and it gives the recipient a way to check the delivery against the original order. Once they confirm everything matches, they sign it. That signature is what turns a working document into proof of delivery.
People mix this up with an invoice constantly, so here is the actual distinction.
| Document | Purpose | Includes Prices | Requires Signature | Triggers Payment |
|---|---|---|---|---|
| Delivery Note | Confirms what was physically delivered | No | Yes | No |
| Invoice | Requests payment | Yes | No | Yes |
| Packing Slip | Internal picking reference | Sometimes | No | No |
Prices are deliberately left off a delivery note. The idea is that warehouse staff should be verifying quantities, not values, and in a lot of B2B scenarios the receiving party should not even see the seller's cost. Using a delivery note in place of a proper tax invoice is a real compliance mistake in most jurisdictions, not just a stylistic preference.
Why two quantity fields matter more than they look
The most important pair of fields on any delivery note is quantity ordered and quantity delivered. A lot of templates and a lot of internal tools collapse these into a single number, which works fine until a shipment arrives partially fulfilled. Anyone dealing with back orders, phased stock releases, or split shipments needs to see both numbers, plus a calculated outstanding balance, without maintaining a separate spreadsheet on the side.
If you're modeling this in a database or a form, it is worth treating outstanding as a derived value rather than something manually entered. Order 100 units, deliver 60, and the outstanding field should just show 40 on its own.
The condition notes field nobody thinks about until they need it
There is usually a small section on a delivery note for the recipient to flag damage or discrepancies right at the point of handover. It is easy to treat as an afterthought. In practice it is often the single most important field on the whole document, because a dispute over missing or damaged goods is far harder to resolve without something written down at the moment of delivery, rather than a complaint that surfaces two weeks later.
Signatures carry real legal weight
A dual signature block, one for the person delivering, one for the person receiving, is what actually gives the document evidentiary weight. In the UK for example, a signed delivery note is treated as prima facie evidence that goods were delivered, which shifts the burden of proof onto whoever is disputing it. An unsigned delivery note is a much weaker document in any commercial disagreement.
It also plugs into tax compliance
This is the part that surprised me most. In a lot of countries, the delivery date on this document is what anchors the legal date of supply. In South Africa, that date starts the clock on the window a vendor has to issue a proper tax invoice. In Kenya, under the eTIMS electronic invoicing system, the delivery note is the physical evidence that a supply actually happened, corroborating the digital tax record. Retention requirements also vary by country, generally somewhere between five and six years, so if you are building anything that touches this data, it needs to stay queryable well past the transaction date, not get archived and forgotten.
Fields worth including if you are building or documenting this yourself
- Delivery note number, sequential, for tracking and matching
- Issue date, delivery date, and dispatch date as separate fields, they answer different questions
- PO reference and invoice reference, for three way matching
- Separate billing and shipping addresses, these are frequently not the same location in B2B
- Quantity ordered, quantity delivered, and outstanding
- Delivery method, carrier, and tracking number
- Condition notes
- Dual signature block
If you want a reference to work from rather than building the layout from scratch, there is a free delivery note template available in Excel, Word, PDF, and Google Sheets, with a live outstanding quantity formula in the spreadsheet version.
Curious whether anyone else here has had to model this kind of document flow, purchase order to delivery to invoice, and what tripped you up the first time around.
Top comments (0)