What Is a Delivery Note: Essential 2026 Guide
Discover what is a delivery note, its format, legal uses, and how to automate processing for 2026. Reduce errors and save time effectively.
A truck unloads at 8:10 a.m. By 9:00, the warehouse has checked the goods, procurement is asking whether the order is complete, and finance is waiting to match the receipt against the purchase order and the invoice. The only shared record is a delivery note attached as a PDF from the supplier, scanned at an angle, with item names in a layout your system has never seen before. That is where many digital supply chains still break.
A delivery note sits at the point where the physical movement of goods must match the digital record. On paper, that sounds simple. In practice, it is often the first document that exposes whether inventory, receiving, purchasing, and accounts payable are working from the same facts. A missing quantity, an unread line item, or a misread product code can lead to stock errors, delayed approvals, short-pay disputes, and extra follow-up between teams.
The problem is not the document itself. The problem is the format. Delivery notes now arrive through email inboxes, supplier portals, mobile scans, and multi-page PDF attachments, often with no standard structure across vendors. Traditional OCR can read characters, but it often struggles to understand context, line items, handwritten marks, tables, and supplier-specific layouts without custom setup. It works like reading letters on a page but missing what the page means.
That gap matters operationally. A delivery note is often treated as a simple shipping document, yet it acts more like a control point for the order-to-cash and procure-to-pay cycle. When teams still key in data by hand or review exceptions one file at a time, scale becomes expensive and error-prone. This is why teams dealing with this daily now treat delivery note data extraction workflows as part of their core automation stack.
Understanding what a delivery note is starts with understanding why it creates friction in modern systems. Once the document becomes unstructured, manual processing slows the business down, and basic OCR stops short of true automation. Advanced AI extraction changes the equation by identifying the right fields, interpreting document context, and turning inconsistent supplier documents into usable operational data.
What Is a Delivery Note
A delivery note is a commercial document that accompanies goods in transit and confirms the contents, quantities, and physical details of the shipment when it reaches the customer.
It's easy to confuse it with an invoice. It isn't one. A delivery note focuses on what physically arrived, not on price, tax, or payment. Its job is practical first. The recipient uses it to check the shipment. The sender uses it to prove dispatch and, once signed, prove receipt.
Why companies use it
A delivery note creates a shared reference point between the warehouse, the carrier, the customer, and the finance team.
It usually answers simple but important questions:
What was sent
The note lists the goods, often by SKU or item description.How many units arrived
Quantities matter because inventory and billing depend on them.Who received the shipment
This becomes especially important if there's a later dispute.Whether anything was missing or damaged
Notes and signatures can record exceptions at the moment of receipt.
A delivery note becomes operationally important the moment the physical shipment and the digital record need to match.
Where people get confused
Many teams think of delivery notes as “just a packing slip.” That's too narrow.
In practice, the document can play three roles at once:
| Role | What it does |
|---|---|
| Logistics record | Helps the receiver verify the shipment |
| Operational checklist | Confirms quantities and item details at handoff |
| Proof of delivery | Creates evidence once signed and archived |
That last role is the one people often underestimate. A delivery note isn't just paperwork. In many workflows, it's the document that proves goods were received.
The Anatomy of a Delivery Note
A compliant delivery note needs a clear structure. According to SumUp's delivery note guidance, the six essential elements are seller's name and contact details, customer's name and contact details, date of issue, date of delivery, detailed description of ordered goods, and the exact quantity of each product in the shipment. The same source notes that standardized templates reduce document processing errors by 45%.
The six required elements
Here's what those fields mean in day-to-day operations.
Seller name and contact details
This identifies who dispatched the goods. If there's a discrepancy, the receiver knows exactly which supplier or warehouse sent the shipment.Customer name and contact details
This ties the shipment to the right destination and the right buyer. It sounds basic, but this field matters when companies manage multiple sites or departments.Date of issue
This shows when the document was created. It helps establish sequence if the goods were prepared on one day and delivered on another.Date of delivery
This is the operational handoff date. Warehouses, inventory teams, and finance teams often rely on this field to anchor follow-up actions.Detailed description of goods
The note should describe the items clearly enough that the recipient can verify what's in front of them. Generic labels create avoidable confusion.Exact quantity of each product
This is the field most likely to trigger downstream issues if it's wrong. Inventory accuracy depends on it.
Useful fields that make the note stronger
A delivery note can also include extra fields that improve traceability:
- Delivery note number for tracking and filing
- Order number to connect the shipment to the original order
- Special instructions for handling or exceptions
- Receiver signature to confirm receipt
- Condition of goods if the customer needs to record visible issues
Practical rule: If the recipient can't use the document as a physical checking list at the loading dock or receiving desk, the note is too vague.
Why signatures matter
The signature isn't decorative. It turns the document into a stronger operational and legal record.
When the receiver signs, the company has evidence that the shipment was handed over and checked at that moment. If goods are later disputed, the signed note is usually one of the first documents everyone asks for.
Delivery Note vs Invoice and Other Documents
A lot of process problems start with document confusion. Teams treat a delivery note like an invoice, or they assume a purchase order proves receipt. It doesn't.
According to IONOS on delivery notes, a delivery note is a non-valuation-based instrument. It lists quantities and physical descriptions while omitting monetary values, which legally separates it from an invoice. The same guidance states that it requires two copies, one for the customer and one for the seller to archive as proof of delivery once signed.
Delivery note and invoice
The clearest distinction is this:
| Document | Main purpose | Includes prices |
|---|---|---|
| Delivery note | Confirms what was physically delivered | No |
| Invoice | Requests payment for goods or services | Yes |
That difference shapes who uses each document.
A warehouse team needs the delivery note to check the load. Finance needs the invoice to process payment. If a company uses the invoice as the only proof that goods arrived, it's trusting a financial request instead of a delivery confirmation.
Delivery note and purchase order
A purchase order comes earlier in the process. It shows what the buyer asked for.
The delivery note appears at handoff. It shows what the seller says was delivered and what the receiver can verify in front of them.
That distinction matters because “ordered” and “received” aren't the same thing.
Delivery note and bill of lading
A bill of lading usually belongs to transport and carriage. It focuses on the movement of goods and the carrier relationship.
A delivery note is closer to the operational receipt of goods by the customer. In many businesses, both may exist in the same shipment flow, but they don't solve the same problem.
If you need to answer “what did the customer actually receive,” the delivery note is the first document to check.
Why Manual Delivery Note Processing Fails
A receiving team can handle ten delivery notes by hand and still feel in control. At one hundred a day, control starts to slip. PDFs arrive by email, drivers hand over phone photos, suppliers send different layouts, and scanned copies lose table structure. What looked like a simple admin step turns into an operational bottleneck.
Delivery notes create trouble because they are rarely standardized in practice. One supplier puts item codes in a narrow table. Another splits quantities across two pages. A third adds handwritten remarks such as "short shipped" or "back order to follow." In a digital supply chain, that variation matters because warehouse, procurement, finance, and inventory systems all depend on the same fields being captured correctly.
The manual workflow usually follows a familiar pattern. Someone opens the file, reads the lines, keys the data into the ERP, and saves the document for reference. That sounds manageable until volume rises or document quality drops. Then the process starts failing in small ways that create larger downstream problems.
Common failure points include:
Line items losing context
A person can read the text but still attach the wrong quantity to the wrong SKU, especially when tables wrap across pages.Code entry mistakes
Similar product codes such as 8B01 and 8801 are easy to mistype when scans are faint or layouts are crowded.No real-time checks
Data gets entered even when quantities conflict with the purchase order or the item count is incomplete.Exception queues growing quietly
Unclear documents sit in a shared inbox, which slows goods receipt, matching, and follow-up with suppliers.
Scaling teams usually see these problems first in their manual data entry automation challenges, where document volume grows faster than headcount.
Traditional OCR adds speed, but not enough understanding. It reads characters. It does not reliably understand which fields belong together, which table continues on page two, or whether a handwritten note changes the meaning of a line item. OCR is like copying every word from a packing slip onto a whiteboard without preserving the rows and relationships. The text is there. The structure that operations teams need is often gone.
That is why unstructured delivery notes create a broader automation crisis. The issue is not getting text out of a document. The issue is turning a messy document into trusted operational data that can trigger receiving, matching, stock updates, and supplier communication without manual review. Basic OCR often stops at text capture, which leaves staff to do the hardest part themselves.
The business cost shows up in places companies often notice too late. Inventory records drift from physical reality. Three-way matching slows down. Disputes take longer to resolve because the proof of receipt is buried in email attachments and scanned copies. Payment approvals get delayed, or worse, incorrect receipts move forward as if they were clean.
This also affects product data discipline across the business. Teams trying to improve catalog quality, supplier consistency, and order accuracy often run into the same underlying issue discussed in how PIM drives growth. Bad document inputs create bad system records.
Manual delivery note processing fails because digital supply chains need structured, validated data, and delivery notes rarely arrive in a structure machines can trust on their own. That gap is exactly why OCR alone falls short, and why advanced AI extraction has become the practical path to real automation.
Automating Delivery Notes with AI The Modern Solution
A warehouse receives 40 delivery notes before lunch. Some arrive as clean PDFs from large suppliers. Others are phone photos, scans, or multi-page attachments with stamps, handwritten marks, and inconsistent table layouts. The goods may be easy to unload. The document data is not. That is where many automation projects break, because digital supply chains still depend on documents that were never designed for machines to read reliably.
Modern document automation solves that problem by treating a delivery note as a business record, not just an image with text on it. The workflow combines text recognition, document classification, field extraction, and validation so the system can identify the document, understand its structure, and return data that downstream systems can use.
What AI extraction does
A useful way to understand the process is to follow the document from file to workflow:
- OCR reads the visible text
- Classification identifies the document type
- Extraction captures the required fields and line items
- Validation checks whether the output is complete, correctly formatted, and plausible
- Automation sends trusted data into the next system or exception queue
That sequence matters because traditional OCR only handles the first step. It can pull words off the page, but delivery notes depend on relationships between fields. Which quantity belongs to which SKU. Which address is the supplier and which is the receiver. Whether a stamp, signature, or handwritten correction changes the meaning of the document. In practice, that is why teams that need to OCR documents, extract data from PDF, or implement document automation often find that OCR alone still leaves a human doing the hardest part.
According to the verified business description for Matil.ai, the platform combines OCR, classification, validation, and workflow orchestration through an API, works with pre-trained models, supports rapid customization, and is built for enterprise security with GDPR, ISO 27001, SOC alignment, and zero data retention.
From messy PDF to structured data
The output is not text. It is structured data.
That distinction is the difference between a clerk reading a document on a screen and an ERP or WMS processing it automatically. A good extraction system returns fields in a predictable format, including supplier details, dates, document IDs, and line items, so receiving and finance workflows can continue without rekeying.
{
"delivery_note_id": "DN-2026-98765",
"issue_date": "2026-10-22",
"delivery_date": "2026-10-23",
"supplier_details": {
"name": "Global Industrial Supplies",
"address": "123 Supply Chain Rd, Factory Town, 12345"
},
"customer_details": {
"name": "Matil.ai Fulfillment Center",
"address": "456 Automation Ave, Tech City, 67890"
},
"line_items": [
{
"sku": "SKU-HD-500",
"description": "Heavy Duty Widget",
"quantity": 150,
"unit": "pieces"
},
{
"sku": "SKU-LT-250",
"description": "Lightweight Gadget",
"quantity": 300,
"unit": "pieces"
}
],
"received_by": {
"name": "John Doe",
"signature": "pending",
"timestamp": null
}
}
Once a delivery note is converted into a structure like this, the business can trigger stock updates, route exceptions, support matching controls, and store reliable proof of receipt without asking staff to interpret every attachment by hand.
The concept is similar to how PIM drives growth. In both cases, the value comes from turning inconsistent inputs into structured records that other systems can trust.
One example of a complete workflow
Tools such as Matil.ai fit this model because they handle more than OCR. They provide an API for extraction, classification, validation, and automation across PDFs, images, and multi-page documents. For a practical explanation of that category, this overview of intelligent document processing is a useful reference.
A short product walkthrough makes the difference visible in practice:
Clean JSON is what automation needs. That is the handoff point where a delivery note stops being a file and starts being usable operational data.
The Strategic Role of Delivery Notes in Business Operations
A delivery note matters most when goods, records, and payments need to stay aligned.
According to Mecalux on delivery notes and three-way matching, the delivery note is the critical third component in three-way matching, the accounting control that reconciles the purchase order, delivery note, and final invoice before payment is authorized. The same source explains that the process depends on the note's SKU list, shipped quantities, and recipient details to provide definitive proof of delivery.
Why finance teams care
Without the delivery note, finance can compare what was ordered with what was billed. It still can't fully confirm what was received.
That gap matters because payment approval should depend on physical delivery, not only on paperwork generated upstream.
A basic three-way match works like this:
| Step | Document | Question answered |
|---|---|---|
| 1 | Purchase order | What did we agree to buy? |
| 2 | Delivery note | What actually arrived? |
| 3 | Invoice | What is the supplier charging us? |
| 4 | Match result | Do these records align closely enough to pay? |
Why operations and legal teams care
The delivery note also creates an audit trail. If the customer says part of the shipment was missing, or if the supplier says everything was delivered, the note is one of the clearest records available.
That's especially true when it includes:
- A complete item list that the receiver could physically verify
- Accurate quantities tied to each SKU
- Recipient identification showing who accepted delivery
- A signature or confirmation that marks the handoff event
When teams store delivery notes as structured, validated records instead of disconnected PDFs, disputes are easier to investigate and controls are easier to enforce.
Good practice for senders and receivers
For senders, the goal is clarity. Use a standard format, keep descriptions specific, and make sure the note matches the shipment exactly.
For receivers, the goal is verification. Check quantities against the physical goods, record any shortage or damage immediately, and archive the final version in a way that finance and operations can retrieve later.
That's the bigger point behind the question “what is a delivery note.” It's not just a shipping attachment. It's a control document that connects the warehouse, the customer, and the payment process.
If you're evaluating how to automate delivery note processing, invoice matching, or other high-volume document workflows, you can explore Matil as one option for turning unstructured files into validated, structured data through an API.
