Convert Delivery Note PDFs to Excel Automatically

To convert delivery note PDF to Excel, extract one row per line item and repeat the key header fields on every row, including the delivery note number, supplier, delivery date, and PO reference. For AP and receiving workflows, the spreadsheet also needs quantities delivered, backordered or short quantities, and any handwritten shortage or damage notes. If those fields are missing, the file may look converted, but it will not support matching, reconciliation, or clean import into the next system.

A delivery note is not just a table of products. It is the document that shows what physically arrived, when it arrived, which purchase order it belongs to, and whether the receiving copy records any exception. That is why a finance-useful sheet has to preserve both document-level context and line-level detail. The document-level fields identify the shipment. The line-level rows show what was delivered, what was short, and what still needs checking against the invoice or goods-received record.

For most teams, the real job is not simply to make the PDF editable. It is to turn receiving paperwork into structured rows that can be filtered, reviewed, and reused. A sheet that repeats the PO number, supplier, and delivery note number on every line is much easier to sort by supplier, isolate one shipment, trace a shortage back to the original document, or load into an ERP import template. A sheet that only copies visible table cells usually forces the team back into manual cleanup.

This is where delivery note data extraction differs from generic conversion. The output has to preserve the fields that matter operationally: SKU or item description, quantity delivered, quantity backordered, unit of measure, and the notes written by the person who signed for the goods. Once those fields are preserved in a clean spreadsheet, the file becomes useful for receiving review, bookkeeping, and later matching. That is the standard the rest of the workflow should be judged against.

Why Generic PDF to Excel Tools Break on Delivery Notes

Generic PDF-to-Excel tools are designed to copy what they can see on the page. That works reasonably well when the source document is a clean statement or a simple table. Delivery notes are different. They combine header fields, line items, handwritten receiving notes, signatures, and partial-shipment cues in one file, and those elements have to stay connected after export.

The most common failure is that a generic converter lifts the visible rows but loses the document context around them. A quantity column may survive, while the PO reference sits in a header cell that never gets repeated on each exported row. A handwritten note such as "2 short" or "1 carton damaged" may remain trapped in the image. A partial-delivery marker such as "1 of 3" may be ignored entirely. The result looks like a spreadsheet, but it does not answer the questions AP or receiving teams actually need to answer.

Plain OCR is only part of the job as well. OCR can turn printed text into machine-readable text, but delivery-note extraction needs to understand which fields belong to the whole document and which belong to each line item. It also needs to preserve exceptions that sit outside the neat product table, such as signatures, dock notes, and multiple order references. That is why the useful benchmark is not "Did the PDF become editable?" It is "Did the exported rows still carry the fields needed for review and matching?"

A field-aware setup should let the operator ask for one row per line item, repeat the delivery note number and PO reference on each row, and keep the receiving-side notes attached to the right shipment. That is the gap between a generic converter and AI extraction for delivery note and invoice workflows. In Invoice Data Extraction, the user uploads the document, describes the output in a prompt, and can request a line-item spreadsheet with repeated header fields rather than a flat visual copy. That matters because the reader's problem is not format conversion alone. It is preserving the structure that finance and operations need after the file leaves the PDF.

Which Columns to Extract for Matching, Reconciliation, and Audit

At a minimum, the spreadsheet should capture the fields that identify the shipment, the order it belongs to, and the line items that were actually received. For most teams, that means delivery note number, supplier, delivery date, PO reference, SKU or item code, description, quantity delivered, quantity backordered or short, unit of measure, and a notes field for receiving exceptions. If the document includes batch or lot numbers, pallet IDs, or carton counts that matter to the business, those should come across as separate columns too. For pub cellar workflows, a guide to brewery delivery note bookkeeping for UK pubs shows how to carry brewery-specific fields like keg IDs, ABV, deposits, and duty flags into the spreadsheet as well.

The structure matters as much as the field list. For line-item work, the cleanest layout is one row per delivered item with the document-level fields repeated on every row. That makes the file usable for filters, pivot tables, ERP imports, and exception review because the operator does not have to look back up the sheet to understand which shipment a row belongs to. It also makes it easier to split the file by supplier, isolate one purchase order, or compare delivered quantities against what the buyer expected. If one delivery note references multiple POs, keep each PO reference explicit in the exported rows instead of collapsing them into one free-text note, because that is usually the point where later matching breaks down.

This is also where the distinction between the supplier's delivery note and the receiving-side record becomes important. If your process uses a separate goods received note, the spreadsheet needs enough context to support that handoff rather than blur the two documents together. A concise guide to goods received note vs delivery note helps clarify why one proves what the supplier sent and the other confirms what your team accepted into stock.

That discipline is not just administrative neatness. CRS guidance on comparing delivery notes with goods received and purchase orders says the supplier delivery note should be compared with the actual goods received and the purchase order, and that the goods-received note should then be sent to accounts to attach to the later invoice for payment. In other words, the spreadsheet has to preserve the fields that let finance follow that chain. If the export collapses multiple POs, drops shortage notes, or strips away batch references that matter later, the data-entry step still has to be done by hand.

---

Handle Bundled PDFs, Partial Deliveries, and Handwritten Exceptions

The hard part is rarely a perfect single-page delivery note. The hard part is the supplier bundle that starts with one invoice, continues with fifty delivery notes, and includes scanned pages that were signed on a loading bay or photographed on a phone. If those pages are extracted as one undifferentiated table set, the spreadsheet becomes harder to trust than the PDF it came from.

The first job is separating relevant delivery-note pages from the rest of the bundle. If the file includes an invoice cover page, email printout, remittance summary, or other non-delivery material, those pages should be filtered out before export so they do not contaminate the sheet. Multi-page delivery notes need the same care. A continuation page with more line items, a signature block, or a handwritten note about damaged goods still belongs to the same receiving event and has to stay attached to it.

Partial deliveries also need explicit treatment. A delivery note that says "1 of 3", marks a line as backordered, or shows short-delivered quantities should not be flattened into a completed receipt. Those markers tell AP and receiving teams that the later invoice may not match the full order quantity yet. The same applies to handwritten notes such as "2 short", "3 cartons damaged", or "left on back dock". Those are not side comments. They are the operational explanation for why the delivered quantity, stock record, or invoice later looks wrong.

This is one of the places where Invoice Data Extraction can do more than a basic converter. The platform supports mixed batches of up to 6,000 files, single PDFs up to 5,000 pages, filtering of non-relevant pages, and instructions that tell the AI to prioritize handwritten notes when those notes matter more than the printed text. It also includes source file and page references in the output so a reviewer can trace a questionable row back to the original page quickly. For a team processing bundled supplier paperwork, that combination matters because the messy parts of the file are usually the parts that determine whether the exported spreadsheet is genuinely usable.

Review the Export Before You Send It to Excel, CSV, or Google Sheets

Before the file goes into the wider workflow, review the output as structured data rather than as a pretty spreadsheet. A delivery note export is ready for use when each row still makes sense on its own: the document number is present, the supplier and date are clear, the PO reference is attached to the right lines, and any shortage or damage notes are readable without reopening the PDF.

Start with the row shape. If the goal is matching, reconciliation, or stock review, one row per line item is usually the safest layout because it keeps every delivered quantity separate and makes exceptions visible. Check that the header fields repeat on every row, not just on the first line of each document group. Then check the data types and formatting. Dates should be consistent, quantities should live in quantity columns rather than in description text, and notes about shortages or returns should not be merged into generic comments that lose their meaning.

The right export format depends on what happens next. Excel is usually the best destination when the team needs formulas, pivot tables, filters, or a controlled handoff into bookkeeping and AP workbooks. A delivery note to CSV export is often enough when the next step is an ERP import or an automated data pipeline. A delivery note to Google Sheets workflow can be perfectly adequate for shared review, quick exception triage, or a lightweight receiving log, provided the underlying columns stay clean.

Whatever the format, do one final traceability check before anyone starts editing the sheet. Make sure the exported rows can still be tied back to the original file and page, especially for partial deliveries, annotated receiving copies, and bundled PDFs. That is what lets the team resolve disputes quickly instead of debating whether the spreadsheet or the paperwork is the source of truth.

---

Delivery Docket, Dispatch Note, Packing Slip, and the Next AP Step

Different teams use different names for the same basic extraction job. In the UK, Ireland, and much of Europe, the document is usually called a delivery note. In Australia and New Zealand, many users search for a delivery docket. In some sectors, dispatch note appears for the supplier-side shipping document, while US readers often mean a packing slip when they ask for the same spreadsheet outcome. Teams handling Japanese-language supplier paperwork can follow a Japanese delivery note to Excel workflow for the same spreadsheet outcome when the source fields and labels are in Japanese. The wording varies, but the operational need is the same: preserve the shipment details and exceptions in a format that can be reviewed and reused.

If the terminology itself is the sticking point, it helps to revisit what a delivery note should include so the extraction target is clear before the spreadsheet design starts. The key distinction is that the supplier's document records what was sent with the shipment, while your internal receiving or AP process may create other records later. That is why the spreadsheet should preserve the supplier-side fields first, then carry them forward into the next control step.

For most finance teams, that next step is not another round of manual typing. It is AP review, bookkeeping entry, or a delivery note invoice matching workflow that compares the purchase order, the delivery note, and the later invoice. Once the extracted sheet carries the right line items, PO references, quantities, and receiving exceptions, it stops being a converted PDF and becomes a usable input to that control process. That is the point of the workflow: less cleanup, clearer exceptions, and fewer surprises when the invoice arrives.