Matching Purchase Orders to What Actually Shows Up on the Dock

The standard control in distribution is three-way matching: the purchase order says what was ordered and at what price, the receiving record says what actually arrived, and the supplier invoice says what they're billing for. When all three agree, payment clears without a second look. When they don't, a partial shipment, a price that crept up since the PO was cut, a quantity that doesn't match what the warehouse counted, someone has to investigate before paying, and that's the process a distribution business actually needs a procurement platform to support well.

A three-way match works in this sequence:

1. The purchase order records what was ordered and at what price, with quantity and price locked in before the order is placed.
2. The receiving record captures what actually arrived at the dock, counted against the purchase order.
3. The supplier invoice states what is being billed, and it is compared with both earlier records.
4. If all three agree, payment clears; if they differ, hold the invoice until purchasing and receiving confirm what happened.

Procurify was built around a purchase-order-first workflow, which matches how distribution buying already works: a buyer creates a PO with quantity and price locked in, it gets approved, and receiving checks incoming shipments against it. That structure makes the mismatch, a receiving count that doesn't match the PO, visible immediately rather than surfacing only when the invoice arrives weeks later and someone has to reconstruct what was actually ordered.

Not every distribution cost fits a PO cleanly. Freight surcharges that vary shipment to shipment, fuel costs, and small incidental purchases at the warehouse level don't always have a clean pre-set quantity and price the way a standard inventory PO does. Airbase's card-first model handles that variability better, letting a warehouse or logistics lead make a fast purchase and tag it to the relevant shipment or route afterward, rather than forcing a variable freight cost through a rigid PO structure it doesn't fit.

Say a regular supplier raises prices on a commodity item by a few percent, and the change doesn't get caught until an invoice arrives, because the PO was generated from a stale price list that nobody updated. Without three-way matching enforced at the platform level, that invoice might get paid at the new, higher price with no one flagging the discrepancy against the original PO. With matching enforced, the mismatch stops the payment automatically until someone confirms whether the new price is accurate and whether the standing price list needs updating, which is a small check that prevents a supplier's incremental price creep from going unnoticed across hundreds of line items a year.

Distributors often use blanket or standing purchase orders for regular suppliers, one approval covering many shipments over a period, which is efficient but risky if nobody revisits the blanket PO's terms periodically. A blanket PO set a year ago at a given price and volume can drift out of date as supplier pricing or the distributor's own purchasing volume changes, and a stale blanket PO that nobody reviews becomes a rubber stamp rather than a real control. Reviewing blanket POs on a fixed schedule, quarterly for major suppliers, catches this before the gap between the standing terms and current reality gets large.

A supplier who ships a substitute item, or fulfills part of an order now and backorders the rest, breaks a strict three-way match unless the process has a defined way to handle it. Receiving needs a way to record a partial or substituted shipment against the original PO without simply flagging every such shipment as a hard mismatch requiring a full investigation, since substitutions and backorders are routine in distribution, not exceptions. A workable process splits the PO automatically when a partial shipment arrives, matching what was received against that portion and leaving the backordered quantity open against the same PO, so the eventual second shipment reconciles cleanly instead of creating a confusing partial-payment situation.

Distributors that don't build this flexibility in tend to either hold payment on every partial shipment until the full order arrives, which frustrates suppliers who fulfilled their portion correctly, or they pay the full invoice regardless of what actually showed up, which reopens the exact risk three-way matching exists to close. Building this into the platform's matching rules once, rather than handling every partial shipment as a one-off exception, is what makes three-way matching sustainable at real distribution volume.