What Is Three-Way Matching in Accounts Payable?
Three-way matching is an accounts payable control that compares three key records before an invoice is approved for payment:
Purchase Order (PO) — what the organization agreed to purchase
Receiving Report or Goods Receipt — what was actually received
Supplier Invoice — what the supplier is requesting to be paid
The objective is simple: confirm that what was ordered, received, and billed aligns before payment moves forward.
When the information matches within the organization's configured rules and tolerances, the invoice can continue through the AP process. When it doesn't, the invoice becomes an exception that requires review.
Why Three-Way Matching Matters
Three-way matching gives AP an important control before payment.
It can help organizations:
Identify incorrect quantities or prices
Avoid paying for goods that haven't been received
Detect duplicate or questionable invoice activity
Enforce purchasing controls
Reduce unnecessary overpayments
Create a clearer audit trail
Improve consistency across invoice processing
Three-way matching doesn't eliminate every payment risk, but it provides a structured way to verify that a supplier's invoice is supported by the organization's purchasing and receiving records.
The Three Documents in Three-Way Matching
1. Purchase Order
The purchase order documents what the organization authorized the supplier to provide.
Depending on the purchase, it can include:
Supplier
Item or service
Quantity
Unit price
Delivery information
Payment terms
PO number
The PO establishes the commercial terms against which the invoice can later be evaluated.
2. Receiving Report or Goods Receipt
The receiving record documents what the organization actually received.
For physical goods, that commonly includes quantities received and the date of receipt. Depending on the organization's process, it may also include information about shortages, damaged goods, or other delivery issues.
This is what distinguishes three-way matching from two-way matching.
A two-way match compares the PO and invoice. A three-way match adds evidence that the goods were actually received.
3. Supplier Invoice
The supplier invoice is the supplier's request for payment.
It typically includes information such as:
Supplier
Invoice number
PO number
Items or services billed
Quantities
Unit prices
Invoice amount
Payment terms
The invoice is compared with the PO and receiving information to determine whether the transaction meets the organization's requirements for payment.
How Three-Way Matching Works
The process typically follows four steps.
Step 1: Create and Approve the Purchase Order
Procurement or another authorized buyer creates a purchase order defining what is being purchased and under what terms.
The approved PO establishes the basis for the transaction.
Step 2: Record What Was Received
When goods arrive, the appropriate employee or receiving function records what was actually received.
This creates the receiving information that will later be compared with the supplier invoice.
Step 3: Match the Invoice
When the invoice arrives, AP compares invoice information with the corresponding purchase order and receiving information.
Common matching points include:
Supplier
PO number
Item
Quantity
Unit price
Amount
Organizations can establish their own matching rules and tolerances based on their purchasing policies and control requirements.
Step 4: Process Matches and Resolve Exceptions
If the required information matches within the organization's configured tolerances, the invoice can continue through the workflow.
If it doesn't, the discrepancy is routed for review.
For example:
Quantity mismatch: The supplier invoices 100 units but only 95 have been received.
Price mismatch: The invoice price differs from the PO price.
Missing receipt: The invoice has arrived but the corresponding receipt hasn't been recorded.
Partial shipment: Only part of the PO has been received.
Additional charges: Freight, taxes, or other charges differ from what AP expects.
The appropriate person can investigate the discrepancy before the invoice proceeds.
Two-Way vs. Three-Way Matching
Not every invoice requires the same matching process.
Two-way matching generally compares:
Purchase Order ↔ Supplier Invoice
Three-way matching generally compares:
Purchase Order ↔ Receiving Record ↔ Supplier Invoice
Two-way matching may be appropriate when receipt information isn't required for the particular transaction.
Three-way matching adds another control by confirming that the organization received what is being invoiced.
The appropriate approach depends on the organization's purchasing process, transaction type, ERP configuration, and internal controls.
Automating Three-Way Matching
Three-way matching can become labor-intensive when AP employees have to manually locate and compare information across invoices, purchase orders, receiving records, emails, and ERP screens.
Automation changes the process.
Invoice information can be captured electronically and compared with purchasing and receiving data according to configured matching rules.
Invoices that meet the requirements can continue through the workflow, while exceptions can be presented to AP for resolution.
This allows AP employees to spend less time manually comparing routine transactions and more time addressing the invoices that actually require attention.
Automating Three-Way Matching with AP Express
AP Express combines invoice capture, ERP integration, matching, exception management, and workflow to automate much of the three-way matching process.
After invoice information is captured, AP Express can use ERP purchasing and receiving information as part of the matching workflow.
For qualifying invoices, the system can compare information such as:
Purchase order
Invoice line
Quantity
Price
Receipt information
Configured tolerances
Invoices that meet the organization's matching requirements can continue through the workflow. Discrepancies can be routed for review and resolution.
The objective isn't to eliminate AP oversight.
It's to automate the invoices that don't require it and focus AP attention on the exceptions that do.
Deep ERP Integration Matters
Three-way matching depends heavily on ERP data.
Purchase orders and receiving information typically originate in the ERP, and approved invoice information ultimately needs to remain synchronized with the organization's financial system.
AP Express integrates with Oracle E-Business Suite, Oracle ERP Cloud, JD Edwards, SAP S/4HANA, and supported multi-ERP environments.
That allows AP Express to automate invoice processing around the customer's ERP while allowing the ERP to remain the system of record.
For organizations with evolving ERP strategies, the AP automation layer can also provide greater continuity as the underlying ERP environment changes.
Common Three-Way Matching Exceptions
Even a highly automated matching process will encounter exceptions.
Common examples include:
Quantity Differences
The invoice quantity doesn't agree with the quantity received.
This may result from partial shipments, receiving delays, supplier errors, or incorrect receiving information.
Price Differences
The invoice price doesn't agree with the purchase order.
AP or procurement may need to determine whether the invoice is incorrect or whether the PO requires an authorized adjustment.
Missing Receipts
The supplier invoice arrives before the receipt has been entered.
This doesn't necessarily mean the invoice is incorrect. The receiving information may simply not have reached the system yet.
Partial Deliveries
A PO may be fulfilled across multiple shipments and invoices.
The matching process needs to account for what has already been received, invoiced, and potentially paid.
Additional Charges
Freight, taxes, or other charges may not align with the information expected from the purchase order.
These exceptions require appropriate rules and review.
Better Exception Management Is Part of Better Matching
The objective of automation isn't simply to generate a match or no-match result.
AP also needs an efficient way to understand why an invoice failed the match and what needs to happen next.
A structured exception process can give AP visibility into the invoice, PO, receiving information, discrepancy, workflow status, and related activity.
Over time, exception data can also identify recurring problems.
If a large percentage of exceptions come from missing receipts, for example, the real opportunity may be to improve receiving practices rather than changing AP.
That's one of the larger benefits of automated matching: exceptions become operational data that can help improve the process.
Conclusion
Three-way matching is a straightforward concept with an important purpose:
Confirm that what was ordered, what was received, and what was invoiced agree before payment proceeds.
The challenge is doing that efficiently across large invoice volumes.
Manual matching requires AP employees to locate information, compare records, investigate differences, and manage exceptions individually.
Automation can perform much of that comparison systematically while directing AP attention toward transactions that genuinely require review.
With AP Express, three-way matching becomes part of a connected invoice-processing workflow that combines invoice capture, matching, exception management, approvals, and ERP integration.
The result is not simply faster matching.
It's a more controlled and scalable way to manage invoice exceptions across the AP process.
FAQs
How does three-way matching help reduce payment risk?
Three-way matching compares the supplier invoice with independently generated purchasing and receiving information.
That helps identify discrepancies such as incorrect prices, quantities that haven't been received, unsupported charges, or other inconsistencies before payment proceeds.
It should be viewed as one component of a broader AP control environment rather than a complete fraud-prevention solution.
Can three-way matching be automated?
Yes.
Automated AP systems can capture invoice information and compare it with PO and receiving information according to configured matching rules and tolerances.
Invoices that satisfy those rules can move forward, while discrepancies are routed for review.
What's the difference between two-way and three-way matching?
Two-way matching typically compares the purchase order and supplier invoice.
Three-way matching adds the receiving record, providing confirmation that the invoiced goods were actually received.
The appropriate matching method depends on the transaction and the organization's purchasing and control requirements.
What are the most common three-way matching problems?
Common issues include quantity differences, price differences, missing receiving information, partial shipments, additional charges, and timing differences between invoice receipt and receiving activity.
The most effective matching processes don't simply identify these exceptions—they make it easier for AP and the appropriate business users to understand and resolve them.