Finance Index
Automated Purchase Order Matching in Accounts Payable
Reference guide explaining automated purchase order matching in accounts payable, including two-way matching, three-way matching, receipts, tolerances, exceptions, and approval impact.
Automated purchase order matching is the process of comparing invoice details against purchase orders and, when applicable, receipts before an invoice is approved or paid. It helps AP teams confirm that billed goods or services align with what was ordered, received, and authorized. The process improves payment control by identifying price, quantity, receipt, or vendor discrepancies before downstream posting or payment.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| What it is | Comparison of invoice, PO, and receipt data. | It validates invoice accuracy before payment. |
| Two-way match | Invoice compared with purchase order. | Useful when receipt data is not required. |
| Three-way match | Invoice compared with purchase order and receipt. | Useful when delivery confirmation matters. |
| Common exceptions | Price, quantity, missing receipt, vendor, tax, or line mismatches. | Exceptions drive review work. |
| Typical output | Matched invoice, exception queue, or approval path. | AP can prioritize review and payment readiness. |
This page explains automated purchase order matching in accounts payable at the finance-practice level. It is written as neutral reference content, so it focuses on accounting concepts, workflow patterns, controls, and related terminology rather than vendor-specific setup steps, UI paths, configuration details, or promotional claims.
What PO Matching Covers
PO matching checks whether an invoice is consistent with purchasing records. The process can compare vendor, PO number, item, quantity, price, tax, freight, receipt, and other line-level values.
Two-Way Matching
Two-way matching compares the invoice to the purchase order. It asks whether the supplier billed for the items, quantities, and prices that were authorized in the PO.
Three-Way Matching
Three-way matching adds receipt or delivery confirmation. It asks whether the invoice matches both what was ordered and what was received.
Line-Level Matching
Line-level matching evaluates individual invoice and PO lines rather than only checking header totals. This matters when a single invoice includes multiple items, partial shipments, or different pricing conditions.
Tolerances and Exceptions
Many matching processes use tolerance rules to determine when a variance requires review. Exceptions may involve price differences, quantity differences, missing receipts, duplicate invoices, or mismatched vendor and PO data.
Approval Impact
A successful match can support faster approval or payment readiness. An exception usually triggers review by AP, procurement, the requester, or another business owner before the invoice moves forward.
Common Misconceptions
PO matching is not the same as approval
Matching verifies invoice accuracy against purchasing records. Approval confirms that the business authorizes the invoice to move forward.
Three-way matching is not always required
Some organizations use two-way matching for certain spend categories and three-way matching when receipt confirmation is necessary.
Automation does not remove exception review
Automation can identify matches and exceptions, but business judgment is still needed when records disagree.
Where This Fits in the P2P Workflow
PO matching sits after invoice capture and coding, and before final approval or payment readiness. It connects procurement records with AP review so invoices are not paid solely based on the supplier document.
Frequently Asked Questions
Automated PO matching compares invoice data against purchase order data and, when needed, receipt data. It helps AP teams identify whether an invoice matches what was ordered and received.
Two-way matching compares the invoice to the purchase order. Three-way matching also compares the invoice to receipt or delivery confirmation.
Common PO matching exceptions include price variances, quantity variances, missing receipts, partial receipts, tax differences, freight differences, and mismatched line details.
Line-level matching matters because header totals can hide differences across individual items or distributions. Reviewing each line improves accuracy for complex or partial invoices.
PO matching usually occurs after invoice capture and before payment readiness. It gives AP and approvers evidence that the invoice aligns with purchasing records.