Three-Way Matching vs Invoice Review: Which AP Control Do You Need First?
Published September 2026 by Solarc Labs
Three-way matching depends on three reliable records
Three-way matching compares a purchase order, supplier invoice and receipt or delivery evidence. Xero’s UK purchase-order guidance describes this as a core AP capability for checking those records together. That means the control is only as useful as the upstream records. If purchase orders are missing, receipt information is informal or identifiers do not line up, the matching layer will inherit those weaknesses.
Invoice review answers a simpler question
A source-document invoice review asks whether the facts extracted from the invoice are visible, internally consistent and ready for an accountable person to decide what happens next. It does not require the organisation to have mature procurement records. For smaller teams, this can be the fastest way to reduce manual handling while preserving control.
Use three-way matching when purchasing discipline already exists
If the business already creates purchase orders consistently, records receipt of goods or services and has stable identifiers across systems, automated matching can reduce repetitive checks and focus attention on mismatches. In that environment the automation is grounded in real source records rather than inferred process maturity.
Use review-first automation when the data foundation is weaker
If invoices are the only consistently available record, start by making invoice intake and review reproducible. Preserve the PDF, extract the fields, surface defined exceptions and require a named decision. This is not a lesser control. It is a control matched to the evidence the organisation actually has today.
A staged AP roadmap is often lower risk
A practical sequence is invoice intake and review first, then reliable PO capture, then receipt evidence, then matching, and only later broader straight-through automation where the economics and controls justify it. The point is to automate verified process maturity rather than automating around missing records.
Primary sources
Sources used for this article
Continue the job