In accounts payable, 2-way and 3-way matching are the two most common ways to verify a vendor invoice before paying it. Two-way matching compares the purchase order against the invoice to confirm the vendor is billing for what you agreed to buy. Three-way matching adds a receiving report so you also confirm the goods physically arrived before the check goes out. Which one you use depends on what you’re buying: services and subscriptions usually get two-way, inventory and equipment usually get three-way.
The Documents Behind Each Match
Every version of AP matching combines some mix of three documents, and the names are worth getting straight before comparing methods.
The purchase order is your company’s formal request to buy something. It locks in the item, quantity, unit price, and payment terms before the vendor ships anything. The vendor invoice is the supplier’s bill, listing what they claim to have delivered and what they expect to be paid. It’s the document that actually triggers payment. The receiving report is created by whoever physically accepts the delivery, confirming what arrived, how much of it arrived, and whether it was in acceptable condition. That report exists independently of both purchasing and accounts payable, which is what gives it value as a control.
The fields checked across these documents are vendor identification, item descriptions or codes, quantities, unit prices, and payment terms like due dates or discount windows. When the numbers don’t line up, you have a discrepancy, and the invoice gets held until someone figures out why.
How 2-Way Matching Works
Two-way matching is the simpler version. It compares only the purchase order against the vendor invoice, checking that the supplier is billing for what your company agreed to buy. Oracle’s AP module describes this as verifying that the quantity billed is less than or equal to the quantity ordered, and that the invoice price is less than or equal to the purchase order price.1Oracle. Two-, Three-, and Four-way Matching
The process starts when AP receives an invoice and links it to the corresponding PO number. The system checks whether the item descriptions, unit costs, and quantities align. If everything falls within the company’s tolerance limits, the invoice is approved for payment automatically. If the invoice amount exceeds the PO amount or the item codes don’t match, the system flags it.
Two-way matching fits purchases where a physical receiving report doesn’t make sense. Services are the classic example. A consulting engagement relies on a signed statement of work that functions as the PO, and the invoice is matched against the labor hours and rates specified in that agreement. Nobody is counting boxes at a loading dock. The same logic applies to software subscriptions, utility bills, and similar non-inventory spending.
The tradeoff is obvious. Without a receiving report, you’re trusting that the vendor actually delivered what they billed for. For a $200 monthly subscription, that’s a reasonable bet. For a $50,000 equipment purchase, it’s not.
How 3-Way Matching Works
Three-way matching adds the receiving report as a mandatory third checkpoint. The system now verifies not just that the financial terms match, but that someone in your organization physically confirmed the goods arrived. This closes the gap between “we agreed to buy it” and “we actually got it.”
Oracle’s documentation spells out the additional criterion: the quantity billed must be less than or equal to the quantity received.1Oracle. Two-, Three-, and Four-way Matching Without that check, your company could pay for shipments that are still on a truck somewhere, or for items that arrived damaged and were sent back.
The flow runs like this. Purchasing creates a PO and sends it to the vendor. When the shipment arrives, receiving personnel inspect it against the PO and generate a receiving report documenting what was accepted. AP then receives the vendor’s invoice and links all three documents by the PO number. If quantity and price align across all three within tolerance, the invoice moves to the payment queue.
The receiving report is typically generated by warehouse or receiving staff who sit outside both the purchasing and AP departments. That separation matters. When different people handle ordering, receiving, and payment approval, no single person can create a fictitious purchase and pay themselves for it.
Three-way matching is the standard approach for inventory purchases and capital expenditures. Microsoft’s Dynamics 365 documentation reflects this directly: invoices for items used as fixed assets should be matched with both purchase order lines and product receipt lines using three-way matching, while routine vendor invoices based on purchase orders can use two-way matching.2Microsoft Learn. Three-way Matching Policies
What About 4-Way Matching?
Some organizations go a step further with four-way matching, which adds a quality inspection report as a fourth document. Where three-way matching confirms that goods arrived, four-way matching confirms they arrived in acceptable condition. The inspection report is prepared by a quality control team after examining the delivery against the specifications in the purchase order or contract.
This is the method that distinguishes “we received 500 units” from “we received 500 units that actually meet our specs.” Industries with strict quality requirements, like manufacturing, pharmaceuticals, or food production, are the ones most likely to need this extra layer. Oracle’s AP system supports four-way matching as an option you can enable at the supplier, supplier site, or purchase order level, layering it on top of the standard two-way and three-way checks.1Oracle. Two-, Three-, and Four-way Matching Most companies reserve it for high-value materials where a quality failure would be expensive or dangerous.
Tolerance Thresholds
Perfect matches sound great in theory. In practice, minor rounding differences, shipping variances, and unit-of-measure conversions create tiny discrepancies on nearly every transaction. Tolerance thresholds prevent these trivial mismatches from clogging up the payment process.
Tolerances can be set as a percentage, a flat dollar amount, or both. Microsoft’s Dynamics 365 documentation shows how this works in practice: a company might set a net unit price tolerance of 10%, meaning the invoice price can deviate up to 10% from the PO price before the system flags a discrepancy. Price totals matching might use a 15% tolerance or a $500 cap, whichever triggers first.3Microsoft Learn. Accounts Payable Invoice Matching Overview Most ERP systems let you configure different tolerances for different item categories, vendors, or dollar thresholds.
Setting tolerances is a balancing act. Too tight, and your AP team spends all day chasing penny differences. Too loose, and you’re approving invoices with meaningful overcharges.
What Happens When a Match Fails
When an invoice falls outside tolerance on price, quantity, or both, the system places a hold on it. That invoice cannot be paid until someone investigates and resolves the discrepancy. Oracle’s AP module applies holds automatically when matching criteria aren’t met, and some of those holds can only be released by fixing the underlying problem rather than manually overriding them.4Oracle. How Invoice Holds Work Common hold types include quantity received holds, price discrepancy holds, maximum order amount holds, and missing receipt holds for goods.5University of California, Riverside Accounting Office. Invoice Holds and Resolution
A few typical scenarios:
- Invoice exceeds PO price. The AP clerk contacts the vendor to request a corrected invoice, or works with purchasing to determine whether a PO amendment was approved but never entered.
- Quantity billed exceeds quantity received. This usually means a short shipment. AP requests a credit memo from the vendor for the undelivered items, or holds the invoice until the remaining goods arrive and a new receiving report is generated.
- Quantity received exceeds quantity billed. Less common, but it happens. AP contacts the vendor for an updated invoice reflecting the full delivery.
These resolution cycles can add days or weeks to the payment timeline. That delay has a real cost, because many vendor agreements include early payment discounts. A term like “2/10 net 30” offers a 2% discount if you pay within 10 days, with the full amount due within 30. Missing that 10-day window on a $100,000 invoice costs you $2,000.
When to Use Each Method
The choice isn’t one-size-fits-all. Most companies use a mix, applying different levels of verification based on the risk profile of each transaction.
Two-way matching is best for services, subscriptions, utilities, and other purchases where no physical goods change hands. It’s also appropriate for low-value, high-volume purchases like office supplies, where the cost of rigorous verification exceeds the risk of overpayment.
Three-way matching is the standard for inventory, raw materials, and any physical goods recorded as assets. It’s also the default for purchases above a company-defined dollar threshold, regardless of category.
Four-way matching stays reserved for items where quality directly affects production, safety, or regulatory compliance. Pharmaceutical ingredients, precision components, perishable goods.
Most ERP systems let you set matching policies at multiple levels. You can define a default for the entire company, then override it for specific vendors, item categories, or individual purchase orders. A company might default to two-way across the board but escalate to three-way for any PO over $5,000 and four-way for a specific high-risk supplier.2Microsoft Learn. Three-way Matching Policies
Why the Choice Matters Beyond Efficiency
AP matching isn’t just an efficiency play. For publicly traded companies, it’s a compliance requirement. Section 404(a) of the Sarbanes-Oxley Act requires management to assess and report on the effectiveness of internal controls over financial reporting, and Section 404(b) requires an independent auditor to attest to that assessment.6U.S. Securities and Exchange Commission. Study of the Sarbanes-Oxley Act of 2002 Section 404 Internal Control Over Financial Reporting Requirements AP matching is one of the most visible and testable internal controls an auditor will examine.
An auditor reviewing your AP process wants to see that invoices are matched against POs and receiving reports before payment, that discrepancies are flagged and resolved through a documented process, and that the people who approve payments are different from the people who order goods or accept deliveries. Three-way matching satisfies all three in a way that’s easy to demonstrate.
Even for private companies that aren’t subject to SOX, maintaining a clear matching trail protects against vendor fraud, duplicate payments, and financial statement errors. If your AP process can’t demonstrate that every payment corresponds to a verified order and, where applicable, a confirmed delivery, your financial statements are only as reliable as the honesty of every person in your supply chain.