Purchase Order Matching

An office orders 100 chairs at $200 each, but a supplier invoice requests payment for 110 chairs. A purchase order match flags the extra 10 before payment, and the buyer can investigate a changed order, delivery evidence or invoice error.

The purchase order records an authorised commitment of supplier, items, quantities, prices and terms, the invoice is the supplier's request for payment, and a receipt or service acceptance documents what arrived or was completed. Two-way matching compares the purchase order with the invoice, three-way matching also uses receipt information, and four-way matching adds an acceptance or inspection check for purchases where arrival alone is not enough.

Oracle's payables guidance explains these distinctions and notes that price and quantity tolerances can put mismatched invoices on hold. These are configurable controls, not a rule that every company must use four documents.

Agree on the level of comparison, since matching only the grand total can hide one overpriced line offset by another underpriced line, whereas line-level checks make discrepancies easier to explain. Set tolerances carefully: a small freight variation may be legitimate, while a large price increase should need approval, so document which amounts can pass automatically, who can approve exceptions and what happens when they recur.

Partial deliveries require attention too, because if only 60 of 100 chairs arrived, the invoice for 100 may be premature even though the order itself was authorised, and a later receipt should be linked to the same order without paying the same invoice twice. Services need a practical receipt equivalent, such as a signed milestone approval, timesheet acceptance or project manager confirmation, and a system should not invent a warehouse receipt for consulting work.

Taxes, shipping and currency may not appear on the purchase order in the same way as product lines, so define the basis for comparison and route unexpected additions for review instead of hiding them in a broad tolerance. Match the right supplier identity and account, because a valid invoice sent by a familiar supplier can still carry changed bank details or an unrelated order number, and matching does not replace supplier verification and payment controls.

Hold exceptions for resolution, not automatic rejection, since the invoice might reflect an approved contract amendment that never reached the purchasing system, so confirm authority, update the record and keep an audit trail. An illustrative discrepancy is invoice quantity minus eligible received quantity: if 110 units were invoiced and 100 were received, 10 units are unmatched, which is an exception, not proof of fraud.

Track what caused exceptions, as frequent mismatches from one product catalogue may signal stale prices and a supplier sending invoices before delivery may need a clearer billing schedule. Use duplicate detection alongside matching, because two invoices may each match the same order and receipt if the system does not track already-billed quantities, so compare invoice identifiers, supplier and paid-to-date values.

Automated matching saves clerical work when identifiers are reliable, but OCR can misread order numbers or totals, so a confident-looking automated match still needs sensible thresholds and review of anomalies, and segregation of duties should be kept where the company can, with small teams using compensating owner review rather than a large approval chain. Measure exception rate and time to clear holds, since an excessively rigid process can delay valid suppliers while a permissive one can pay for items never received, and remember that purchase order matching answers whether a bill aligns with an authorised, delivered purchase, not whether the original purchase was wise, the vendor is secure or the payment account is safe.