How to Extract Goods Received Notes (GRN/GRV) to Excel

To extract goods received notes to Excel, capture the GRN or GRV header, supplier, receiving site, PO reference, line items, received quantities, condition notes, and receiver sign-off into one row per received line. Then add review columns for ordered quantity, invoiced quantity, received quantity, variance, shortage, overage, damage, substitution, and follow-up status.

That structure matters because the receiving document is not useful to AP as a scanned image alone. A goods received note, goods received voucher, receiving report, or goods receipt becomes useful when each received item can be compared with the purchase order and supplier invoice. If the spreadsheet only has one row per document, the team still has to reopen the PDF or paper form whenever one item is short, damaged, substituted, or split across multiple deliveries.

A useful extraction workflow should therefore produce a working table, not just OCR text. The output should let a bookkeeper filter for missing PO numbers, let an AP clerk compare received quantities against invoiced quantities, and let a controller see which receiving exceptions are still open before payment or month-end close.

Know which receiving document you are extracting

The same receiving evidence appears under different names. GRN is common shorthand for goods received note. GRV usually means goods received voucher, especially in South African accounting and inventory workflows. Goods receipt, receiving report, material receipt note, and MRN can point to the same buyer-side record in other systems or regions.

For extraction, the label matters less than the document's job. The spreadsheet should capture what the buyer says was received, when it was received, where it was received, who accepted it, and which PO, supplier, item, or invoice it relates to. If you need a refresher on the underlying fields, the existing goods received note field map covers the baseline document anatomy.

Do not merge supplier delivery notes and buyer-side GRNs into one undefined bucket. A delivery note travels with the goods from the supplier. A GRN or GRV records what the buyer received or accepted. The documents can support the same matching workflow, but they are not the same evidence. If your document pack includes supplier delivery notes as well as GRNs, keep a document type column and use the delivery note invoice matching workflow for the supplier-side comparison.

Mixed packs are normal. A receiving folder may contain the purchase order, delivery note, GRN or GRV, supplier invoice, warehouse stamp, and handwritten discrepancy note. Extraction should preserve enough reference fields to keep those documents connected without forcing them into a single form.

Build the spreadsheet around one row per received line

A GRN to Excel workflow should usually create one row for each received line, not one row for each document. Matching happens at line level: item code, description, unit of measure, ordered quantity, received quantity, accepted quantity, rejected quantity, and the related PO or invoice reference. A one-row document summary hides the detail that AP needs when only part of a shipment arrived or one item was damaged.

Start with document header fields: GRN or GRV number, document date, receiving date and time, source file name, page number, branch, warehouse, site, and document type. Add supplier fields such as supplier name, supplier account number, delivery address, and any supplier reference printed on the paperwork.

Then capture the purchasing references that connect the receipt to the rest of the procure-to-pay process: PO number, purchase order line number where present, supplier invoice number if already shown, delivery note number, requisition number, job number, project code, cost centre, and buyer or department. These fields are the first place teams look when a receipt will not match cleanly.

The line-item columns should carry the operational evidence: SKU, item code, barcode, description, unit of measure, ordered quantity, received quantity, accepted quantity, rejected quantity, damaged quantity, substituted item, lot number, batch number, serial number, expiry date, catch weight, and receiving notes. For food, apparel, hardware, construction, and manufacturing workflows, those details can decide whether an invoice line is payable, held, or queried.

Keep receiver evidence separate from item data. Useful columns include receiver name, signature present, stamp present, QC approval, condition notes, discrepancy notes, and handwritten comments. Where OCR or handwriting recognition may be uncertain, preserve the extracted value and add a review field beside it rather than overwriting the original text.

Add variance columns for PO and invoice checks

Extraction is only the first half of the job. The spreadsheet becomes valuable when it shows where the receipt agrees or disagrees with the purchase order and supplier invoice. For received goods, Rockefeller University's purchasing guidance states that a three-way match compares receiving, purchase order, and invoice information before the invoice is paid.

The practical version of that control is a set of review columns beside the extracted GRN or GRV data. At minimum, include ordered quantity, received quantity, invoiced quantity, accepted quantity, variance, shortage, overage, damaged quantity, substituted item, reviewer, follow-up owner, and status. If your team also reviews value, add invoice unit price, PO unit price, line value, and price exception.

Clean references make GRV to invoice reconciliation possible. One invoice may cover several GRNs, several GRNs may relate to one PO, and one GRN may include lines that are accepted, short, damaged, or still waiting for clarification. Without line-level PO numbers, invoice numbers, item codes, quantities, and status fields, AP ends up checking the same scanned document repeatedly. If you want the PO, GRN, and invoice data sitting side by side in one file, the combined PO, GRN, and invoice extraction spreadsheet shows how to key the lines together with tolerances and exception flags. For South African FMCG teams working from GRVs, the GRV three-way matching workflow for supplier invoices goes deeper into quantity, price, and VAT variance checks.

The broader three-way invoice matching process explains the control model, but a GRN extraction spreadsheet should stay closer to the receiving facts. It should show what arrived, what was accepted, what was invoiced, and which exceptions still need action.

Plan for messy receiving paperwork

Real receiving documents rarely arrive as clean, single-page PDFs. Stores send phone photos. Warehouses stamp over printed fields. Site supervisors write quantities by hand. Branches scan several receipts into one file. A supplier invoice may arrive days after the goods, while the GRV sits in a shared drive with no PO number in the file name.

Design the extraction output for those conditions. Add columns for original document type, source file, page number, handwritten note, stamp text, condition note, discrepancy note, missing PO flag, missing invoice flag, duplicate GRN number flag, and review needed. Those fields stop exception handling from disappearing into comments, email threads, or handwritten marks that no one can filter.

Partial deliveries need special care. If one PO line is received across several GRNs, the spreadsheet should keep each receipt line separate and preserve the PO reference. If one supplier invoice covers several GRNs, the spreadsheet needs enough GRN numbers, delivery note numbers, item codes, and received quantities to group the evidence later. The running-balance table for one PO across multiple GRNs and progressive invoices shows how to keep the allocation visible while receipts and invoices arrive out of order. For catch-weight or variable-measure items, capture both the count and the measured weight or volume where the document shows both.

Damaged and substituted goods should be explicit fields, not buried in a notes column. A received quantity of ten does not mean ten acceptable items if two were damaged, one was substituted, and seven were accepted. Separate accepted, rejected, damaged, and substituted quantities make the follow-up visible before the invoice is approved.

The same principle applies to site-to-head-office handoffs. If a construction site, retail branch, warehouse, or restaurant sends the receiving evidence to finance, the spreadsheet should make the local context visible: site, receiver, timestamp, photo source, and any note that explains why the receipt does not match the PO exactly.

Choose the extraction route for your GRN volume

Manual entry is still reasonable when the volume is tiny and the forms are consistent. If a bookkeeper enters a few clean GRNs a month, the overhead of configuring a new process may be larger than the data-entry work itself. The risk starts to rise when several branches, stores, sites, or warehouses send recurring GRNs and GRVs, because the same missing PO number or quantity typo can affect invoice approval, stock updates, and month-end follow-up.

Generic OCR and PDF-to-Excel tools can help with occasional clean PDFs. They are less reliable when the document has line items across pages, regional labels such as GRV or MRN, handwritten receiving notes, warehouse stamps, and review columns that do not exist on the source document. OCR may extract visible text, but AP still needs the output shaped into matching fields.

For recurring batches, Invoice Data Extraction is a practical route when the job is to extract financial documents into structured spreadsheets. Users upload PDF, JPG, or PNG documents, describe the fields they want in a natural-language prompt, and download the result as XLSX, CSV, or JSON. The same workflow can extract line items and custom review fields, so a GRN or GRV batch can be structured around the team's own matching columns rather than a fixed template.

Keep the handoff clear. Extraction software should give finance a matching-ready dataset for review, import, or downstream reconciliation. It should not be treated as final ERP posting, automatic three-way matching, or payment approval unless those steps are handled by a separate controlled workflow.

Use GRN extraction to keep receiving exceptions visible

The extracted spreadsheet should become the working queue for receiving exceptions. Useful status values include ready for invoice match, waiting for invoice, waiting for PO correction, waiting for receiving clarification, damaged goods review, supplier credit requested, duplicate receipt review, and closed.

Those statuses turn scattered paperwork into follow-up work finance can manage. AP can filter for missing invoices. Receiving can review short deliveries or damaged goods. A controller can see which unmatched PO lines are blocked by missing GRNs, unclear quantities, or supplier documents that do not agree with the receipt.

Unprocessed receiving documents also create month-end cleanup. If goods have arrived but the supplier invoice has not been matched or posted, finance may need to investigate the receipt as part of the GRNI cleanup workflow. A clean GRN extraction file does not replace that accounting review, but it gives the reviewer the document numbers, quantities, supplier details, and exception notes needed to find the issue faster.

The end point is a spreadsheet that keeps receiving evidence usable after extraction: one row per received line, clear references back to the PO and invoice, visible quantity differences, and status fields that show who still needs to act.