The difference between 2-way and 3-way matching in accounts payable comes down to one document: two-way matching compares a purchase order against the vendor’s invoice, while three-way matching adds a receiving report that confirms the goods actually showed up before payment goes out. Two-way is faster and fits services or subscriptions where nothing physical arrives. Three-way is the standard for inventory and any purchase where you need proof of delivery before cutting a check.
The Documents Behind Each Match
Every matching decision revolves around three documents, and knowing what each one does makes the rest of the comparison straightforward.
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. The receiving report is a record created by whoever physically accepts the delivery, confirming what showed up, how much of it arrived, and whether it was in acceptable condition.
The receiving report exists independently of both purchasing and accounts payable, and that separation is what gives it value as a control. Different people handle ordering, receiving, and payment approval, so no single person can create a fictitious purchase and pay themselves for it.
The data points verified across these documents include vendor identification, item descriptions or codes, quantities, unit prices, and payment terms. When numbers don’t line up, the invoice is held until someone figures out why.
How Two-Way Matching Works
Two-way matching compares only the purchase order against the vendor invoice, checking that the supplier is billing for what your company actually 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 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 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 straightforward. Without a receiving report, you’re trusting 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 Three-Way Matching Works
Three-way matching adds the receiving report as a mandatory third checkpoint. Now the system verifies not just that the financial terms match, but that someone in your organization physically confirmed the goods arrived. 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 still sitting on a truck somewhere, or for items that arrived damaged and got sent back.
The flow works 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 using the PO number. The system runs its comparison, and if quantity and price align across all three documents within tolerance thresholds, the invoice moves to the payment queue.
Three-way matching is the standard approach for inventory purchases and capital expenditures. Microsoft’s Dynamics 365 documentation illustrates the split 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
Tolerance Thresholds
Perfect matches sound clean in theory. In practice, minor rounding differences, shipping variances, and unit-of-measure conversions create tiny discrepancies on nearly every transaction. Tolerance thresholds prevent trivial mismatches from clogging up payments.
Tolerances can be set as a percentage, a flat dollar amount, or both. Microsoft’s Dynamics 365 documentation shows how this plays out: 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 the day chasing penny differences. Too loose, and you’re approving invoices with meaningful overcharges. Review your exception data periodically and tighten or loosen thresholds based on what’s actually causing holds.
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 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 Each points to a different root cause, and the resolution path depends on the type.
A few typical scenarios:
- Invoice exceeds PO price. The AP clerk contacts the vendor for a corrected invoice, or works with purchasing to determine whether a PO amendment was approved but never entered into the system.
- Quantity billed exceeds quantity received. This usually means a short shipment. The AP team 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. The AP team contacts the vendor for an updated invoice reflecting the full delivery.
These resolution cycles can add days or weeks to the payment timeline, and the delay has a real cost. Many vendor agreements include early payment discounts. A typical term like “2/10 net 30” offers a 2% discount if you pay within 10 days, with the full amount due within 30 days. Missing that 10-day window on a $100,000 invoice costs you $2,000. Annualized, that 2% discount over 20 days works out to roughly a 36% return, which is why AP teams push hard on processing speed.
Choosing Between Two-Way and Three-Way
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 the right fit for services, subscriptions, utilities, and other purchases where no physical goods change hands. It also works 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.
Most ERP systems let you set matching policies at multiple levels. You can define a default policy for the entire company, then override it for specific vendors, item categories, or individual purchase orders. A company might default to two-way matching across the board but escalate to three-way for any PO over $5,000.2Microsoft Learn. Three-way Matching Policies
Beyond Three-Way: Four-Way Matching and ERS
Two other approaches sit at the edges of this decision. Four-way matching adds a quality inspection report as a fourth document, confirming goods arrived in acceptable condition rather than just confirming they arrived. Oracle’s AP system supports it as an option that can be enabled at the supplier, supplier site, or purchase order level.1Oracle. Two-, Three-, and Four-way Matching Manufacturing, pharmaceuticals, and food production are typical use cases; most companies reserve it for high-value materials where a quality failure would be expensive or dangerous.
Evaluated Receipt Settlement (ERS), also called “pay on receipt,” goes the other direction and skips the invoice entirely. The buyer’s system generates a payment document based on the PO prices and the quantity recorded in the goods receipt.6Oracle. Know More about Pay on Receipt Auto Invoice It works best in high-volume, stable supplier relationships where prices are fixed by contract and deliveries are frequent, and it requires the vendor to agree to the arrangement upfront.
Both sit outside the core two-way versus three-way decision, but they’re worth knowing about if your standard three-way process either isn’t catching enough (four-way) or is creating unnecessary paperwork with your largest suppliers (ERS).