Purchase Order Receipt Matching

A purchase order sets what a company agreed to buy, a receipt records what actually arrived, and an invoice states what the supplier wants to be paid. Matching the order and receipt helps stop payment for goods not yet received or over the agreed quantity.

Begin with identifiers by matching the supplier, legal entity, purchase order number, line and delivery reference, since similar products can appear on several lines with different prices. Check order authorisation, because a receipt does not turn an unauthorised purchase into an approved one, so confirm the order and applicable changes were validly approved.

Record actual receipt: a delivery note may say ten units shipped, but a warehouse count may find eight, so use the accepted receiving record, not just the supplier statement. Separate receipt from inspection, since goods can be physically present yet damaged or held for quality testing, and some processes require an acceptance check before invoice approval.

Oracle describes two-way matching of purchase order and invoice, three-way matching that adds received quantity, and four-way matching that adds accepted quantity, with exact tolerance settings depending on the system and buyer policy. Compare unit prices and quantities, because a supplier may bill for ten units at an agreed price even though only eight arrived, and the excess should go on hold or follow the agreed partial-delivery process.

Review units of measure, since an order in cases and a receipt in individual pieces need a reliable conversion and a count of ten cases is not ten units. Handle partial deliveries by tracking cumulative ordered, received, accepted and billed quantities, because one purchase order can have multiple receipts and invoices and the second invoice should not be mistaken for a duplicate.

An illustrative open quantity is ordered units minus accepted received units, so if 100 units were ordered and 80 accepted, 20 remain outstanding under this simple measure, although cancellations or returns can change that balance. Watch timing, since an invoice may arrive before the receiving team posts goods, and do not approve merely because the supplier says the shipment is in transit.

Check over-receipts, because a supplier may send more than ordered and the team needs a decision to accept, return or amend the order, not an automatic payment. Use tolerances deliberately, since small rounding or packaging differences may be allowed while large deviations require approval, and the tolerance should be documented and proportionate to risk.

Record exceptions with cause, as missing receipt, price variance, quantity variance and damaged goods are distinct issues and routing every exception to one queue slows correction, and keep return records linked so that a batch later returned does not remain payable as if all units were accepted, checking credit notes and replacement shipments. Separate service purchases, since a consulting milestone might have an acceptance record rather than a warehouse receipt, and check freight and extras, because shipping, handling and taxes may be separate invoice lines whose contractual basis still requires review.

Avoid premature closures and reconcile by line, not just total, since an order marked completed while deliveries remain open can hide later invoices and two line errors could offset and make an invoice total look correct while the wrong items are recorded in inventory. Watch duplicate receipts, such as scanning the same pallet twice, give buyers and warehouse staff a common process in which the buyer owns price and order terms and receiving staff own physical evidence, and do not confuse a match with product quality, remembering that for owners receipt matching ties cash outflow to an authorised order and real delivery.