Extract data from goods receipt notes

A Goods Receipt Note is the warehouse-side acknowledgement that a delivery arrived. When a supplier ships against a purchase order, the receiving dock at the buyer's warehouse inspects the load, counts the items, checks them against the PO, and generates a GRN (also called a Goods Received Note or a Delivery Note acknowledgement). The GRN is the second leg of three-way matching: PO ordered 100 units, GRN received 98 units (2 damaged on arrival), Invoice billed for 100. AP cannot pay the invoice until the GRN confirms what was actually received, and inventory cannot be released to production until receiving inspection signs off. The data inside the GRN is the link between procurement and finance: supplier name, the original PO number, the GRN number itself, the delivery date, the receiver who signed, and the line-level reconciliation between ordered and received quantities. The hard parts are partial receipts and damage. A delivery rarely arrives in one clean piece. Items can be short-shipped, damaged on transit, mislabeled, or substituted with a different SKU than the PO specified. The GRN has to record exactly what arrived, what was rejected, and what is pending. Some warehouses use a paper GRN signed at the dock; some use barcode scanning that prints a GRN; some use a forwarder-generated proof-of-delivery (POD) that doubles as the receipt acknowledgement. The PO reference on the GRN may be a single PO or a list of POs if the shipment consolidated multiple orders. Quantities may be in pieces, cases, pallets, or weight, and they have to match the unit-of-measure on the PO or get converted before the three-way match can run. Talonic returns the GRN as a structured record with the supplier and recipient, the GRN number, the delivery date, the PO reference (or references), and a line-level array showing SKU, quantity ordered (when shown on the GRN), quantity received, quantity accepted (after inspection), unit of measure, and any damage or short-shipment notes. The output maps directly to the receipt object in major ERP systems so AP can resolve invoices against actual receipts rather than against orders.

What gets extracted from goods receipt notes

How extraction works for goods receipt notes

GRNs originate from warehouse management systems (Manhattan, SAP EWM, Oracle WMS) and from carrier-side proof-of-delivery scans. Talonic classifies each GRN and routes it through the receiving schema in the Field Registry, which captures the supplier, recipient, GRN number, PO reference(s), delivery date, and the line-level receipt array. SKU mismatches between PO and GRN are flagged. Short-shipments (received quantity less than ordered) are surfaced as a discrepancy field on the line. Unit-of-measure conversions (cases to pieces, pallets to cases) are preserved as the source shows them rather than auto-converted, because the conversion factor is often vendor-specific. Per-cell confidence and pixel-region provenance follow DIN SPEC 91491 conformity, so AP and inventory teams can verify any received quantity against the source GRN before resolving the three-way match.

Sample extraction

A Goods Receipt Note from Globex Warehouse 3, receiving against PO-2026-01102

{
  "delivery_note_number": "GRN-2026-04-1102",
  "delivery_date": "2026-04-22",
  "supplier_name": "Acme Software, Inc.",
  "recipient_name": "Globex Logistics LLC, Warehouse 3",
  "delivery_address": "Globex Warehouse 3, 4421 Logistics Pkwy, Memphis, TN 38116",
  "purchase_order_number": "PO-2026-01102",
  "line_items": [
    {
      "sku": "ASW-PRO-AN",
      "description": "Annual subscription, Pro plan",
      "ordered_qty": 5,
      "received_qty": 5,
      "accepted_qty": 5,
      "uom": "EACH"
    },
    {
      "sku": "ASW-ONBOARD",
      "description": "Onboarding services",
      "ordered_qty": 8,
      "received_qty": 8,
      "accepted_qty": 8,
      "uom": "HR"
    }
  ],
  "total_quantity": 13,
  "notes": "All items received in good condition, no exceptions."
}

Frequently asked