Every purchase order specifies what was authorized: the vendor, the items or services, the agreed price, and the quantity. PO matching checks the incoming invoice against those specifics, line by line, catching cases where the billed amount, quantity, or item doesn't match what was actually approved.

In practice this is rarely a single clean comparison: invoices consolidate multiple POs, split one PO across several invoices, or include line items in a different order or grouping than the original PO, all of which an AI agent needs to reconcile before it can confirm a real match.

Frequently Asked Questions

Is PO matching the same as three-way match?

They overlap heavily. Three-way match specifically includes the receiving record as a third check; PO matching is sometimes used more narrowly to mean just the PO-to-invoice comparison, without necessarily involving a separate receipt confirmation.

What happens when an invoice doesn't have a matching PO at all?

This is a common and higher-risk exception, since it means someone incurred a cost without going through the normal purchasing approval process. It typically routes to a manager for after-the-fact approval rather than being auto-cleared.

Why do invoices and POs often not line up cleanly?

Vendors consolidate multiple orders onto one invoice, split large orders across several invoices, or format their invoices with different line-item structures than the buyer's PO system, none of which is fraud, just format mismatch that needs reconciling.

What tolerance thresholds are typically applied to PO matching?

Most companies allow a small percentage or dollar variance (say, within 2% or $50) to auto-clear, since minor rounding or tax differences are routine and not worth manual review, while anything outside that band gets flagged.