Goods Receipt: The Missing Leg of 3-Way Match

Goods receipt is the step where you confirm what physically showed up against what you ordered, the posting SAP users know as MIGO with movement type 101, and it is the leg of the three-way match that quietly breaks everything downstream when it is wrong. Everyone talks about the purchase order and the invoice. The receipt in the middle gets ignored until an invoice will not match and nobody can say whether the shipment was short, over, or never recorded.

This piece explains what goods receipt does, how it feeds accounting, and how the EDI 861 receiving advice communicates it back to your supplier.

What the Goods Receipt Process Records

A goods receipt (GR) records the quantity, condition, and date of items physically received against a specific purchase order line. It is the moment the promise on the PO becomes verified reality. Receiving staff count what arrived, compare it to the PO, note damage or shortage, and post the receipt into the system.

That posted receipt does three jobs at once. It updates inventory so stock reflects what is on the shelf. It creates the accounting entry that recognizes a liability for goods received. And it provides the middle data point that invoice matching depends on. When the supplier sent an EDI 856 ship notice ahead of the truck, receiving checks the physical count against the ASN as well as the PO.

Miss the receipt, or post it wrong, and the invoice arriving days later has nothing accurate to match against. The AP team is then stuck asking the warehouse what really came in, which is exactly the manual back-and-forth automation is supposed to end.

Why Goods Receipt Anchors the Three-Way Match

The three-way match compares the purchase order, the goods receipt, and the invoice, so the receipt is the fact that keeps the invoice honest. Without it you only have a two-way match: the invoice against the PO. That tells you the supplier billed what you ordered, but not whether they actually delivered it.

Here is how the three documents line up:

Document	Question it answers	Source
Purchase order	What did we agree to buy?	Procurement
Goods receipt	What actually arrived?	Receiving
Invoice	What are we being billed for?	Supplier

When all three agree within tolerance, the invoice clears for payment automatically. When the invoice says 100 units, the PO says 100, but the receipt says 90 arrived, the system blocks payment for the 10-unit gap. That block is the control working. The full mechanics are in our guide to three-way match, and the receipt's role there is why receiving accuracy is an accounts payable issue as much as a warehouse one.

This is also why accounts payable automation stalls when receiving is manual. Clean matching needs clean receipts.

Goods Receipt and the GR/IR Account

Posting a goods receipt creates an entry in the goods-received/invoice-received (GR/IR) clearing account, which holds the liability until the matching invoice arrives and clears it. This account is the accounting bridge between physical receipt and financial settlement.

The flow works like this. When goods are received, the system debits inventory (or expense) and credits GR/IR, recognizing that you owe for goods you now hold. When the invoice is posted and matched, it debits GR/IR and credits accounts payable, clearing the account. A clean GR/IR balance means receipts and invoices are matching up. A GR/IR account full of stale open items means receipts without invoices, or invoices without receipts, and each one is a reconciliation problem.

In SAP, goods receipt is posted through the MIGO transaction using movement type 101 for receipt into stock against a purchase order, which automatically generates the GR/IR clearing entry (SAP goods receipt and inventory management). Other ERPs use different transaction names but the same logic: the receipt posting creates the clearing entry that the invoice later offsets.

Over-Receipt and Under-Receipt Tolerances

Tolerance bands decide how much quantity variance posts cleanly: a 5% over-receipt tolerance on a 100-unit line accepts 105 units and blocks 106. They are the same mechanism the three-way match applies at invoice time, set wider for bulk commodities and tighter for serialized goods.

Communicating Receipt Back with EDI 861

The EDI 861 receiving advice tells the supplier what you actually received, including any discrepancies, so both sides reconcile from the same record instead of a back-and-forth email thread. It closes the loop that the ship notice opened.

The sequence on an EDI transaction runs like this. The supplier sends an EDI 856 ship notice announcing what they shipped. Goods arrive, you receive them, and you send back an EDI 861 receiving advice confirming what landed. When the 861 reports a shortage or damage, the supplier's system knows before they invoice, which heads off a disputed invoice down the line.

For any of these transactions, you can check the segment structure with the free EDI Inspector before it hits your ERP. Validating the 856 and 861 against each other catches the mismatches that otherwise surface as unexplained receiving variances.

The 861 is a standardized transaction set maintained by the Accredited Standards Committee (X12 transaction sets), so its structure is consistent across trading partners even when their receiving rules differ.

Not every trading partner uses the 861. Many receipts are recorded internally with no supplier notification. But for high-volume partners where discrepancies are costly, the receiving advice is what turns receiving into a two-way, auditable exchange rather than a black box on your dock.

Frequently Asked Questions

What is a goods receipt?

A goods receipt is the record of items physically received against a purchase order. It captures the quantity, condition, and date of what arrived, updates inventory, and posts an entry to the GR/IR clearing account. It is the fact that invoice matching relies on to confirm you were billed only for goods you actually received.

What is the GR/IR account?

The goods-received/invoice-received (GR/IR) account is a clearing account that holds the liability for goods received but not yet invoiced. Posting a goods receipt credits GR/IR; posting the matched invoice debits it, clearing the balance. Stale open items in GR/IR signal receipts without matching invoices, or the reverse, and each needs reconciliation.

How does goods receipt fit into three-way match?

Goods receipt is the middle leg. Three-way match compares the purchase order, the goods receipt, and the invoice. The receipt confirms what physically arrived, so the match can verify the invoice bills only for delivered goods, not just ordered ones. Without an accurate receipt, you can only run a weaker two-way match of invoice against PO.

What is an EDI 861 receiving advice?

The EDI 861 receiving advice is the transaction a buyer sends a supplier to confirm what was received, including quantity discrepancies and damage. It follows the EDI 856 ship notice and lets the supplier reconcile the shipment before invoicing. It turns receiving into an auditable, two-way exchange for high-volume trading partners.

What are goods receipt tolerances?

Tolerances define how much a received quantity can differ from the ordered quantity and still post without manual review. Since shipments rarely arrive in exact quantities, tolerances let minor over- or under-receipts clear automatically while larger variances get flagged. Setting them too tight creates needless exceptions; too loose risks paying for goods never received.