Accounts Payable

Goods Received Note (GRN): Format, 3-Way Match and Automating Invoice-to-GRN

The GRN decides whether an invoice gets paid. This guide covers the GRN format and its place in 3-way matching, and how to stop matching by hand.

Khushbu Adav

Product at Predflow

Purchase order, goods received note and supplier invoice matched line by line

The GRN decides whether an invoice gets paid. This guide covers the GRN format and its place in 3-way matching, and how to stop matching by hand.


Purchase order, goods received note and supplier invoice matched line by line

A goods received note (GRN) is the document your warehouse or receiving team creates to confirm which goods arrived from a supplier, in what quantity and in what condition. The GRN decides whether a supplier invoice gets paid. Without a GRN, the invoice has nothing to match against.

One personal-care brand running SAP cut accounts payable processing time by 92% after automating invoice-to-GRN matching. Between January and September 2026, the agent posted 1,091 GRNs from 1,156 invoices, so 94% went straight through without anyone keying them in. This guide covers the GRN format and the role of the GRN in 3-way matching, then shows where matching breaks and how the automation works.

What Is the Difference Between a GRN, a Delivery Note and a Packing List?

What is a goods received note? A goods received note is the record your receiving team creates when a supplier delivery arrives. The GRN confirms which goods arrived, in what quantity and condition. Accounts payable matches the GRN against the purchase order and the supplier invoice before approving payment, so a late or wrong GRN holds the invoice.

Three documents arrive or get created around the same delivery. Teams confuse them often.

Document

Who creates the document

Purpose

Used in matching?

Packing list

Supplier

Lists contents of each package for handling and customs

No

Delivery note

Supplier, signed by the receiver

Shows what the supplier says was delivered

Supporting evidence

Goods received note

Buyer's receiving team

Confirms what the buyer received and accepted

Yes, the receipt leg of the 3-way match

The delivery note is the supplier's claim, and the GRN is your record. A signature on a delivery note at a busy loading bay shows the goods arrived. The GRN shows someone counted and checked them.

What Does a GRN Format Include?

GRN Template

Field

Example

GRN number

GRN-2026-08812

GRN date

29 October 2026

Purchase order number

PO-2026-04410

Supplier name and code

Sample Packaging LLC, V-00231

Supplier delivery note number

DN-55621

Receiving location

Jebel Ali warehouse, bay 3

Item code and description

PK-110, corrugated box 40x30x30

Quantity ordered

2,000

Quantity delivered

2,000

Quantity accepted

1,950

Quantity rejected and reason

50, crushed in transit

Received by

Store keeper name and signature

Inspected by

QC name where inspection applies

Who Creates the GRN

The store keeper or warehouse supervisor creates the GRN at the point of receipt. In businesses with quality control, QC confirms the accepted quantity before the GRN posts.

When to Create the GRN

Create the GRN on the day of receipt. A GRN created a week later from a pile of delivery notes loses accuracy and pushes payments past due dates.

How Does the GRN Work in 3-Way Matching?

3-way matching compares three documents before a supplier invoice is approved for payment:

  1. Purchase order: what you agreed to buy, at what price.

  2. Goods received note: what you received and accepted.

  3. Supplier invoice: what the supplier is billing.

When all three agree within tolerance, the invoice is approved. When they disagree, the invoice goes to a person. Read our full guide to 3-way matching for the mechanics.

The GRN handles the hard cases in matching:

  • Partial deliveries: 1,200 of 2,000 units arrive. The GRN records 1,200, and only an invoice for 1,200 matches.

  • Over-receipts: 2,100 arrive against an order of 2,000. Your policy decides whether the extra 100 are accepted, returned or held.

  • Short receipts: the delivery note says 2,000, the count says 1,940. The GRN records 1,940, and the supplier invoice for 2,000 fails the match.

  • Damaged goods: received but rejected. The GRN separates accepted and rejected quantities, and the rejected part leads to a return or credit note.


3-Way Matching With the Goods Received Note

Infographic in text: 3-Way Matching With the Goods Received Note. The GRN decides whether a supplier invoice gets paid.

  1. Purchase order: What you agreed to buy, at what price.

  2. Goods received note: What arrived and was accepted.

  3. Supplier invoice: What the supplier bills.

  4. Match within tolerance: Price, quantity, total and VAT.

  • All three agree: The GRN posts and the invoice moves to payment. In one SAP case, 94% of invoices went straight through.

  • Something differs: The invoice is held, the discrepancy is stated, and AP approves or rejects in one click.

Where Does Invoice-to-GRN Matching Break?

Late GRNs

The invoice arrives before the GRN posts. AP holds the invoice while the supplier chases payment and someone walks to the warehouse to ask. Late GRNs are the most common cause of invoices stuck in AP.

Handwritten Delivery Notes

Receivers write the actual quantity on the supplier's delivery note by hand. The GRN gets created later from the handwritten note, and numbers get misread.

Multi-Site Receiving

Goods for one PO arrive at three sites. Each site creates a GRN at a different time, and the invoice covers all three.

Arabic Delivery Notes

Local suppliers often issue delivery notes in Arabic or bilingual formats, with Eastern Arabic digits. Manual GRN entry from these documents adds errors. Our guide to Arabic OCR for invoices covers the extraction problem.

Unit Mismatches

The PO is in cartons, the GRN in pieces, the invoice in kilograms. Without unit conversions in the item master, nothing matches.

How Invoice-to-GRN Automation Works

An invoice-to-GRN agent takes over the repetitive matching and posting, and sends exceptions to a person with the reason attached. The agent built by Predflow for the personal-care brand on SAP works like this:

  1. Ingest invoices. The agent pulls invoices from vendor portals and the shared AP inbox. In the SAP case: six vendor portals and one inbox, with no manual downloading.

  2. Extract line items. The agent reads item, quantity and rate from each invoice.

  3. Match. Each invoice line is compared with the PO line and the goods received, within tolerances your finance team sets. For example, price within 1% and quantity exact.

  4. Post the GRN. When everything agrees, the agent posts the GRN in the ERP.

  5. Route exceptions. When something disagrees, the agent holds the invoice and sends the discrepancy to AP for a one-click approve or reject.

Every action is logged. In the SAP case, the agent went live in production in one to two weeks, with no custom middleware and no changes to the existing SAP setup. What used to take a full Monday morning became a 15-minute review of flagged items. Read the full invoice-to-GRN case study.

Setting Tolerances

Check

Typical tolerance

Action outside tolerance

Unit price

0 to 2%

Route to buyer

Quantity

Exact, or within the GRN quantity

Hold until GRN updated or credit note received

Total value

Small fixed amount for rounding, for example AED 5

Route to AP

Tax amount

Exact at 5% on the taxable value

Route to AP

Start strict. Loosen tolerances only after you see which exceptions are noise.

Where GRN Data Lives in SAP, Focus and Zoho Books

ERP

Where the GRN lives

Notes

SAP

Goods receipt posted against the PO (movement type 101), visible in the PO history

Invoice verification in MIRO checks against the goods receipt

Focus ERP

Goods receipt document linked to the purchase order

Purchase invoice matched to the goods receipt

Zoho Books and Zoho Inventory

Purchase receive in Zoho Inventory, bill in Zoho Books

Bills link to purchase orders and receives

Predflow builds agents on any ERP. The data location changes, while the matching logic stays the same. For the purchasing steps before receipt, read our guide to the purchase order process.

Common GRN Mistakes and How to Fix Them

Mistake

What happens

Fix

GRN created from the delivery note without a count

Short deliveries pass as full, and you pay for goods never received

Count and check before posting, record accepted and rejected quantities separately

One GRN for several POs

Matching fails, invoices sit on hold

One GRN per PO, or split lines by PO

GRN posted to the wrong PO line

Invoice matches the wrong price

Scan or select PO lines, avoid free typing

Services received with no GRN

Service invoices wait for weeks

Use a service entry sheet or a receipt confirmation from the requester

Returns not recorded on the GRN

Supplier bills for goods sent back

Record the return and request a credit note on the same day

GRN never closed on partial delivery

Open PO lines stay open for months

Close or cancel remaining quantities when the supplier confirms no further delivery

Services deserve a note. Many UAE companies only create GRNs for goods. Service invoices, such as maintenance, logistics or consulting, then have nothing to match against, and approval falls back to email. A simple receipt confirmation from the person who received the service, recorded in the ERP against the PO, closes the gap.

Review GRN quality monthly. Pick 20 GRNs at random and compare each with the delivery note and the count record. Fix the process behind every error you find.

GRNs and Supplier E-Invoices From 2027

From 1 January 2027, suppliers in the first e-invoicing phase send invoices as structured data through their Accredited Service Provider. The invoice data arrives clean, with line items, quantities and prices already in fields. Typing errors on the invoice side disappear.

The GRN side does not change. A structured invoice still needs a goods received note to match against before payment. In practice, e-invoicing moves the bottleneck: when invoices arrive faster and cleaner, late or missing GRNs become the main reason invoices wait.

Prepare for the shift now. Measure the time from delivery to GRN posting at each receiving site, and set a target of the same day. Sites with the longest delays need a simpler receiving step, such as a handheld scanner or a short receipt form in the ERP, before e-invoicing volumes arrive.

How Does Predflow Help With Invoice-to-GRN Matching?

Predflow is an AI agent development company. Predflow builds and runs AI agents for businesses in the UAE, India and the US, on the ERP and tools each business already uses, to save time and cost on repetitive work. Predflow builds and runs invoice-to-GRN agents on your ERP. For a personal-care brand on SAP, the Predflow agent cut AP processing time by 92%, and the AP team's Monday backlog became a 15-minute review of flagged items. Read the SAP case study.

Conclusion

The GRN is your record of what arrived. The GRN is the leg of the 3-way match most likely to be late or wrong, and the reason most supplier invoices sit in AP. Create GRNs on the day of receipt, with accepted and rejected quantities recorded separately.

Then automate the matching. When clean invoices post themselves and your team reviews only the exceptions, AP time drops sharply. The SAP case above went from a morning of backlog to 15 minutes.

Sources

Bring 20 invoices and their GRNs to a 30-minute teardown

We will walk your actual invoices through capture and GRN matching on the call, and point out which steps an agent takes over. No prep beyond the PDFs.

Frequently Asked Questions

What is a GRN in accounts?

In accounts, a goods received note is the internal record confirming which goods arrived from a supplier and were accepted. Accounts payable uses the GRN in 3-way matching with the purchase order and the supplier invoice. An invoice without a matching GRN should not be paid.

Who prepares the GRN?

The receiving team prepares the GRN, usually the store keeper or warehouse supervisor, at the time of delivery. Where quality checks apply, QC confirms the accepted quantity before the GRN posts. Finance and AP use the GRN but should not create the GRN.

Is a delivery note the same as a GRN?

They are different documents. The supplier issues the delivery note to show what was sent. The buyer creates the GRN to record what was received and accepted. The two often differ when goods arrive short, damaged or in excess. Matching uses the GRN.

What happens if the GRN quantity differs from the invoice?

The 3-way match fails and the invoice goes on hold. If fewer goods arrived, the supplier issues a credit note or a corrected invoice. If the GRN is wrong, the receiving team corrects the GRN. Payment waits until the documents agree within tolerance.

Can GRN matching be automated?

Yes. An AI agent reads supplier invoices, matches each line to the PO and the goods received within your tolerances, posts the GRN when everything agrees and routes exceptions to a person. One SAP user saw 94% of invoices go straight through.

Do services need a GRN?

Services have no physical delivery, but invoices for services still need confirmation of receipt before payment. Many ERPs use a service entry sheet or a receipt confirmation from the requester. Recording the confirmation against the PO gives AP a document to match the service invoice against.

More on: