Short Definition
An internal control procedure that verifies consistency among purchase orders, receiving reports, and supplier invoices before authorizing payment to prevent errors and fraudulent transactions in accounts payable.
Comprehensive Definition
Three-way matching works because it separates three independent pieces of evidence: what the organization agreed to buy, what it actually received, and what the supplier is asking to be paid. Each document is typically created by a different person or function, which is what gives the control its strength. When the three agree within defined limits, payment can proceed. When they do not, the discrepancy becomes an exception that must be investigated before money leaves the organization.
What Each Document Contributes
- Purchase order (PO): Establishes the authorized quantity, unit price, item description, and terms. It reflects approval by someone with purchasing authority.
- Receiving report: Created by warehouse, operations, or the requesting department to confirm that goods arrived, in what quantity, and in what condition. For services, an equivalent is a documented acceptance or sign-off.
- Supplier invoice: The supplier's demand for payment, listing quantities, prices, taxes, freight, and payment terms.
The comparison usually focuses on item identity, quantity, unit price, extended totals, and sometimes supplier identity and payment terms. A match confirms that the organization is paying for what it ordered and received, at the agreed price.
Why It Matters to Business Professionals
Accounts payable is a common target for both honest mistakes and deliberate fraud. Duplicate invoices, overbilling, billing for undelivered goods, and fictitious vendors all exploit weak verification. Three-way matching reduces these risks by requiring corroboration from outside the AP function. It also supports segregation of duties, a core principle in internal control frameworks, because no single person can order, receive, and approve payment alone.
For compliance and audit teams, the matched documents create an evidence trail. For operations and procurement leaders, exception data reveals recurring problems such as suppliers who consistently overbill or receiving practices that are poorly documented.
How It Works in Practice
- An invoice arrives and is logged against a PO number.
- The AP team or system retrieves the corresponding PO and receiving record.
- Quantities, prices, and totals are compared against defined tolerances.
- Matched invoices are approved for payment according to the payment terms.
- Mismatches are routed to the responsible party for resolution.
Consider a company that orders 500 units at a set price. The warehouse receives 480 units, and the supplier invoices for 500. The invoice matches the PO but not the receiving report, so payment is held until the supplier issues a credit, ships the balance, or the discrepancy is otherwise explained. Without the receiving check, the company would overpay for goods it never received.
Another example is a price variance: the invoice shows a higher unit price than the PO. Procurement must determine whether a legitimate price change was agreed to, in which case the PO may need a documented amendment, or whether the supplier made an error.
Tolerances and Exception Handling
Organizations rarely demand perfect matches on every cent. They commonly set tolerance thresholds, such as a small percentage or dollar variance, within which an invoice is accepted automatically. Tolerances should be set by policy, reviewed periodically, and tighter for high-value or high-risk categories. Every exception needs an owner, a documented resolution, and appropriate approval for any override.
Related Concepts and Variations
- Two-way matching: Compares only the PO and invoice. It is faster but does not confirm receipt, so it suits low-risk or low-value purchases.
- Four-way matching: Adds an inspection or quality acceptance record to confirm the goods meet specifications.
- Automated matching: Accounting or procurement systems perform comparisons electronically and flag exceptions, allowing staff to focus on discrepancies.
- Evaluated receipt settlement and non-PO invoices: Some purchases, such as utilities or recurring services, do not follow the PO cycle and require alternative approval controls.
Common Misconceptions and Pitfalls
Matching is not a guarantee against fraud. Collusion between employees, falsified receiving reports, or a PO issued to a fictitious vendor can still pass a match. The control works best alongside vendor master data review, approval limits, and periodic audits.
Automation does not replace judgment. A system will match whatever data it is given. Poor PO discipline, such as creating POs after the invoice arrives, undermines the entire control.
Overly rigid rules create bottlenecks. Tolerances set too tightly can flood staff with trivial exceptions, delay payments, and strain supplier relationships. Tolerances set too loosely allow leakage.
Receiving is often the weakest link. If staff sign receiving documents without counting or inspecting, the match becomes a formality. Training and accountability at the point of receipt are essential.
Applied consistently and with sensible thresholds, three-way matching gives organizations a practical, defensible method for paying only for what was authorized and delivered.