ERP Inventory Accounting

Goods Receipt and Three-Way Match in Manufacturing ERP: Journal Entries, Variance Handling, and Automation

The match works cleanly when the quantity received equals the quantity ordered and the invoice price equals the PO price. Manufacturing procurement rarely offers either.

0 documentsPO, goods receipt and supplier invoice
0 failuresAccount for almost every mismatch
Receiving clerk confirming a delivery against the purchase order
GR/IRShould clear to zero at period end
500-2,000Monthly POs where manual matching stops scaling
Home › Insights › Goods Receipt and Three-Way Match
Get an AI summary of this page on Google ChatGPT Claude Perplexity

What Is a Three-Way Match in Accounts Payable?

A three-way match is an accounts payable control that matches three documents before a supplier invoice can be approved for payment: the purchase order (which shows the agreed price and quantity), the goods receipt (which shows what was actually delivered) and the supplier invoice (which shows what the supplier is billing).

All three must agree within given tolerances before the invoice can be approved for payment. The three-way match prevents payment for goods not received, payment at prices higher than agreed, and payment for quantities greater than received.

01
PO
Purchase Order (PO)

The buyer's binding agreement to buy: item description, quantity, unit price and delivery terms. The PO is the system of record for what was agreed.

02
GRN
Goods Receipt Note (GRN)

The receiving document, recording the item, the quantity actually received, the date received and the receiving location. The GRN records what physically arrived.

03
Invoice
Supplier Invoice

A request for payment from the supplier. Shows item description, quantity invoiced, unit price and total amount due.

Two-way match vs three-way match

A two-way match compares the PO to the invoice. It checks what was ordered, but not what was received. A three-way match adds the goods receipt as a third check. If the delivery is not confirmed, payment cannot proceed.

Goods Receipt Accounting: Journal Entries and the AP Accrual

The goods receipt note is not only an operational document but also a financial event. Perpetual inventory accounting records the goods receipt, updating on-hand inventory and creating an accounts payable accrual at the same time.

To reconcile the AP accrual account properly and diagnose purchase price variances, controllers need to understand the journal entries at each step of the three-way match.

Step 1: Goods receipt journal entry

When the GRN is posted on scan confirmation, the ERP posts the receipt at the PO price:

AccountDebitCredit
Inventory (or Raw Materials), at the PO pricePO value—
GR/IR Accrual (goods received, not yet invoiced)—PO value

The GR/IR accrual is a balance sheet liability that increases with receipts and clears against invoices.

Step 2: Supplier invoice processing (three-way match)

The ERP matches invoice quantity and price against the PO and the goods receipt. When they match within tolerance:

AccountDebitCredit
GR/IR AccrualPO value—
Accounts Payable—Invoice value

Invoicing for the same quantity and price clears the accrual to zero with no variance.

Step 3: Purchase price variance (PPV)

If the invoice price differs from the PO price, the difference posts to a variance account rather than to inventory:

AccountDebitCredit
GR/IR Accrual, at the PO price originally accruedPO value—
Accounts Payable, at the invoice amount—Invoice value
Purchase Price VarianceDebit if the invoice is higherCredit if the invoice is lower

Controllers review chronic supplier pricing variances at period close.

GR/IR reconciliation at period end

The GR/IR account should balance to zero. Remaining balances are usually goods received but not invoiced, invoices without receipts, or unresolved quantity and price variances. See inventory reconciliation across ERP and WMS for the wider reconciliation picture.

Manufacturing-Specific Three-Way Match Complications

The three-way match is effective when the quantity received equals the quantity ordered, the invoice price equals the PO price, and the invoice arrives shortly after the goods receipt. Manufacturing procurement seldom offers all three conditions at once. Four manufacturing-specific complications add variance the ERP has to handle correctly.

01

Partial receipts

PO for 500 units, 487 received, but the supplier invoices 500. The three-way match finds the quantity discrepancy and the invoice is held.

AP will either accept the 487 and request a credit memo for the 13 units, or wait for the balance to be delivered. The ERP needs reason codes, resolution workflows and automatic re-matching.

02

Purchase price variance from contract pricing

A $4.80 per unit PO is billed at $5.10 for 487 units. That $0.30 differential produces a $146.10 purchase price variance.

AP determines whether the surcharge is approved. Purchasing updates the PO and re-matches if approved; otherwise AP requests a credit memo.

03

Landed cost creating a post-receipt cost adjustment

Bought 1,000 units at $8.00 each, so $8,000. A $600 freight invoice raises the acquisition cost to $8.60 per unit and the inventory value to $8,600.

The ERP debits Inventory $600 and credits Freight Payable $600. The cost is updated without reopening the original receipt.

04

Catch weight receiving

A PO for 100 kg at $12 per kg receives 97.3 kg. The GRN is 97.3 kg, and the AP accrual and supplier invoice are both $1,167.60.

Matching to actual weight removes a systematic variance in receiving.

Let'sTalk

GR/IR Carrying a Balance Nobody Can Explain?

20 minutes. Tell us your ERP, your monthly PO volume and the shape of the aged balance. We will tell you whether it is timing, tolerance configuration, or a receiving process gap.

Schedule A Strategy Call→

How Manufacturing ERP Enforces the Three-Way Match

The three-way match is only as good as the underlying ERP configuration and the receiving process discipline. In manufacturing ERP, three-way match failures almost always come down to one of four configuration or process gaps.

Three-way match configuration requirements in ERP

  • Tolerance thresholds: define quantity tolerances, for example ±2%, and price tolerances, for example ±1%. Without tolerances, partial receipts and rounding differences create manual exceptions that are not necessary.
  • Invoice hold workflow: send quantity mismatches to purchasing or receiving. Send price mismatches to the PO buyer. Send GR/IR aging items to the AP supervisor.
  • GR-required flag on PO lines: require a goods receipt for invoice matching in advance. Without this control, invoices can be processed without the receipt of goods.
  • Three-way match for services: set up service POs for two-way matching, since services do not produce goods receipts.

The four most common three-way match failures in manufacturing

01
Failure 1
Invoice entered before goods receipt

Keep the invoice on hold until the receipt confirmation is posted.

02
Failure 2
Ordered quantity entered instead of actual quantity

A receiver enters 500 instead of the 487 actually delivered so the invoice will match. The invoice clears, but the physical inventory is now wrong.

03
Failure 3
Different units of measure

A PO in kg and an invoice in lb will fail if the ERP does not enforce UOM conversion before matching.

04
Failure 4
Price tolerance set too wide

A 10% tolerance can let a supplier overbill systematically without ever raising an exception.

AI and Agentic Automation for Three-Way Match in Manufacturing

In high PO volume manufacturing operations, manual three-way match exception management is the largest contributor to AP overhead. An AP team processing 500 to 2,000 POs a month spends much of its time routing exceptions, chasing credit memos and reconciling GR/IR. AI and agentic automation can handle each step of that exception workflow.

Invoice data extracted and pre-matched against the PO and receipt before ERP entry
The exception work is the cost. The clean matches were never the problem
01
Extraction
AI invoice data extraction and pre-matching

ML extracts invoice number, supplier, line items, quantities, unit prices and UOM from PDF or EDI invoices and matches them against the ERP PO and goods receipt.

This three-way match automation catches mismatches before they enter the ERP, and lets clean matches continue.

02
Routing
Agentic exception resolution routing

An agent classifies quantity, price, UOM and GR/IR exceptions and routes each one, with supporting records, to the correct buyer or AP supervisor.

It also flags patterns, such as 15 consecutive price variances from one supplier, for contract-level review instead of creating 15 discrete exceptions.

03
Period End
AI GR/IR reconciliation at period end

For open items, ML classifies each as a normal timing difference, a structural mismatch requiring a credit memo or PO amendment, or a duplicate-invoice risk.

The resulting aging report recommends actions, shortening a two- to three-day manual reconciliation to same-day triage.

See manufacturing AI solutions for how these layers are implemented across finance and operational processes.

Frequently Asked Questions: Three-Way Match and Goods Receipt Accounting

What is a three-way match in accounts payable?−
A three-way match is an AP control that compares the purchase order, goods receipt and supplier invoice before payment approval. All three must agree within the tolerances specified. This prevents payment for goods not received, prices higher than the agreed PO price, and invoiced quantities higher than what was physically delivered.
What is the goods receipt journal entry in ERP?+
When a goods receipt is posted, the ERP debits Inventory at the PO price and credits the GR/IR Accrual, representing goods received but not yet invoiced. When the corresponding invoice is processed, the ERP debits GR/IR and credits Accounts Payable, clearing the accrual and creating the formal supplier liability.
What is a purchase price variance (PPV) in three-way match?+
The difference between the PO price and the supplier invoice price is a purchase price variance. For example, an invoice at $5.10 each against a PO at $4.80 each produces a PPV of $0.30 per unit. The difference posts to the Purchase Price Variance account in the ERP for analysis of supplier pricing deviations at period close.
What is the difference between two-way match and three-way match?+
A two-way match compares the PO and supplier invoice but does not confirm receipt. A three-way match adds the goods receipt, which confirms physical delivery before payment. That gives stronger AP control against paying for goods not received. Two-way matching is typically used for service purchases, because services do not generate a goods receipt.
What is GRN in accounting?+
GRN stands for goods receipt note. It is a record confirming that goods have been physically received from a supplier. In manufacturing ERP, posting the GRN updates on-hand inventory and creates the GR/IR accrual liability. It is the second document in the three-way match and provides proof of delivery before AP releases payment.
What causes three-way match failures in manufacturing ERP?+
Typical failures are posting an invoice before the goods receipt, posting the ordered quantity instead of the quantity received, receiving supplier invoices in a different unit of measure with no valid conversion, and price tolerances set so wide that systematic overpayment never raises an exception.
How does AI automate three-way match for manufacturers?+
AI can extract invoice data and pre-match it to POs and goods receipts before entry into the ERP. Agentic workflows escalate quantity, price and GR/IR exceptions to the responsible team automatically. AI-supported GR/IR reconciliation classifies period-end open items as timing differences, structural mismatches or duplicate risks, so same-day triage becomes possible.
Let'sTalk

High AP Exception Volume or GR/IR That Never Reconciles?

Tell us about your ERP, your monthly PO volume and where you have the biggest three-way match exceptions: quantity mismatches, price variances or GR/IR aging. GrayCyan will show how AI invoice pre-matching and agentic exception routing would work in your current ERP.

Book A Discovery Call→

See ERP inventory management, ship confirm and COGS, or start with the AI Readiness Assessment.

Contributor:

nish (5) 1

Nishkam Batta

Editor-in-Chief – HonestAI Magazine
AI consultant – GrayCyan AI Solutions

Nish leads an applied AI company that helps manufacturing and related companies automate operations with human-in-the-loop AI that integrates into ERPs, WMS, CRMs, and other enterprise tools, with an emphasis on no black box AI (explainable AI), clear audit trails, driving efficiency, and measurable outcomes. His team builds agentic ERP systems that execute multi-step tasks inside approved guardrails so humans keep accountability, approvals, and override control.