What Is Purchase Order Matching? A Retail Overview

Purchase Order Matching is the process of comparing purchase orders, receipts, and invoices to verify that billed goods and amounts agree with the transaction. In retail operations this control sits at the heart of procure-to-pay: it stops overpayment, prevents duplicate payments, provides evidence for dispute resolution with suppliers, and feeds accurate inventory and COGS data into the ERP.

At its core the activity links three documents and events: the purchase order issued by the buyer, the goods receipt (or receiving note) recorded when items arrive, and the supplier invoice requesting payment. Matching can also be reduced to two-way (PO vs invoice) when no goods receipt is available — for example, with some service contracts or direct-ship arrangements — but most retail merchandise programs use three-way matching because retail depends on physical receipt confirmation to manage shrinkage, returns, and inventory accuracy.

How The Matching Process Works

Matching proceeds in stages: the system or accounts-payable clerk first finds the customer PO referenced on an incoming invoice, then compares quantities, unit prices, and extended amounts against the PO. Next the invoice is compared with the receiving record to confirm the quantity actually accepted. If quantities, SKU numbers, or pricing match within allowed tolerances, the invoice is approved for payment; if not, it routes to an exception workflow.

• PO Identification: Find the PO number and supplier on the invoice and confirm it matches the buyer’s purchase order record.
• Quantity Check: Compare invoiced quantities with receiving records; consider partial receipts and backorders.
• Price Check: Verify unit price and extensions against the PO terms, applying discounts and freight rules if applicable.
• Tolerance Rules: Apply pre-set percentage or absolute tolerances for minor discrepancies to reduce false exceptions.

Why It Matters In Retail

Retail margins are slim and inventory is both capital and risk. Accurate matching protects margin by preventing overpayment and allows inventory quantities on hand to reflect actual physical stock. For retailers with omnichannel fulfillment, matching also verifies that inventory was received at the correct location (DC, store, or cross-dock) and supports chargeback analyses between trading partners.

Where Manual Matching Breaks Down

Manual matching is time-consuming and error-prone when invoice volumes surge around promotions or seasonal peaks. Typical failure modes include missing or incorrect PO numbers on invoices, receiving notes not entered promptly by warehouse staff, unit-of-measure mismatches (cases vs each), and price exceptions from negotiated contracts. Each error creates an exception that ties up AP staff and delays payment — or worse, results in unintended overpayments.

Automation And System Requirements

Automated matching in an ERP or dedicated AP automation tool reduces manual labor and shortens cycle times. Key capabilities are accurate PO capture, receiving integration with the WMS or barcode scanners, automated three-way comparison logic with tolerance bands, and exception routing with audit trails. Effective implementations also use EDI for PO/invoice exchange or OCR with invoice data extraction for non-EDI suppliers.

• WMS Integration: Receiving data must flow from the warehouse system into the accounting system in near‑real time.
• EDI/OCR: Use EDI 810 invoices where possible; for paper or emailed invoices, OCR with validation reduces keyed-entry errors.
• Tolerance Settings: Set rules by supplier, category, and SKU class to balance exception volume and control.

Common Exception Types And How To Handle Them

Exceptions create the bulk of matching work. Common reasons include partial shipments, backorders, price variances linked to promotions, and receiving records that show discrepancies (damaged goods, shortages). Retail exception handling should combine automated routing with clear SLA targets: for example, route price exceptions to procurement, quantity discrepancies to receiving/warehouse, and tax or payment terms to AP teams.

Metrics To Track

• Match Rate: Percentage of invoices auto-matched without human intervention; a primary measure of automation effectiveness.
• Exception Rate: Percentage of invoices that require manual review; track by exception type and supplier.
• Days Payable Outstanding (DPO): Monitor how matching delays affect payments and supplier relationships.

Practical Example: Seasonal Apparel Receive

A retailer orders 10,000 units of a holiday sweater. The supplier sends two shipments, and the first delivery is recorded at 6,000 units in the WMS. The supplier invoice references the PO for 10,000 units. An automated three-way match flags a quantity exception because the receiver shows only 6,000 accepted. The system either holds payment for the 4,000 short-shipped units or routes the invoice so procurement can confirm backorder timing. Because receiving data is timestamped, AP can also match partial invoicing scenarios where the supplier invoices per shipment.

Tips For Retail Implementation

• Label: Standardize SKU and UOM usage across PO, WMS, and supplier catalogs to avoid mapping exceptions.
• Label: Use EDI 850/810 and ASN (856) messages to reduce manual invoice handling and provide earlier visibility into shipments.
• Label: Set supplier-specific tolerance rules for high-volume vendors to reduce false positive exceptions.
• Label: Train receiving staff to scan items at the point of acceptance and record disposition (accepted, damaged, rejected).

In short, the Purchase Order Matching process is a control that ties purchasing, receiving, and payables together to ensure retailers pay the right amounts for the inventory they actually received. When implemented with clear rules, real-time receiving, and automation, it cuts cost, reduces dispute cycles, and improves inventory accuracy.