Do I need a 2-way or 3-way match for this purchase?

A 2-way match (PO against invoice) is enough for low-risk, non-physical purchases like software subscriptions or professional services, where there's no separate delivery step to verify. A 3-way match (PO, receipt, and invoice) is the standard for physical goods, where confirming something actually arrived — and in what quantity — is the whole point of the extra step.

By Zuny Fester, Head of Operations and Marketing

Reviewed by Zuny Fester

Published September 14, 2026Last reviewed September 14, 2026Editorial policy

Part of the accounts payable and invoice processing guide.

2-way match compares	Purchase order against the vendor invoice
3-way match compares	Purchase order, goods receipt, and vendor invoice
2-way match fits	Services, subscriptions, and purchases with no separate physical delivery to confirm
3-way match fits	Physical goods, where quantity and condition on arrival need independent confirmation
What 3-way match adds	Protection against paying for goods that were ordered but never actually received

What each match actually checks

Bill.com's own explainer defines three-way matching as comparing the purchase order, the receiving report, and the vendor invoice before payment — three independent records that all have to agree on quantity and price. A two-way match drops the middle document: it only compares the PO against the invoice, which means there's no independent confirmation that whatever was ordered actually showed up.

Why a receipt matters for some purchases and not others

Microsoft's own documentation on invoice matching in Dynamics 365 frames matching as a control against paying for something that doesn't match what was agreed or delivered. For a service or a software license, there's no physical receiving event to check against — the invoice itself is close to the only evidence the purchase happened, so a two-way match against the PO is usually the practical ceiling. For physical inventory, equipment, or supplies, a receiving report is a real, independently generated document (often created by someone other than whoever approved the purchase), which is exactly the kind of independent check a three-way match is built to use.

Choosing by risk, not by category alone

Category is a reasonable default (goods get 3-way, services get 2-way), but the real driver is risk and verifiability. A very high-dollar service contract might still warrant a manual review step even without a physical receipt to match against. A low-dollar, low-risk physical purchase from a trusted, repeat vendor might reasonably run on a lighter 2-way match if the volume of 3-way exceptions isn't worth the review overhead. The match type is a control decision, not a fixed rule tied to the purchase category alone.

Next step

Map the finance workflow with the most exposure and prove the automation path.

Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.

Book a workflow review

Checklist

Quick decision guide: 2-way or 3-way?

Is there a physical delivery event to independently confirm? If yes, lean 3-way.
Is this a recurring software subscription or professional service invoice? If yes, 2-way is usually sufficient.
Is the dollar amount high enough that an extra check is worth the friction, even without a physical receipt? Consider a manual review step alongside a 2-way match.
Is this a low-risk, low-dollar, repeat-vendor physical purchase? A lighter 2-way match may be a reasonable tradeoff against exception-review overhead.

Frequently Asked Questions

Yes, in some ERPs and industries — a fourth document (an inspection report, common in regulated or quality-sensitive industries) can be added on top of PO, receipt, and invoice for purchases where confirming condition, not just quantity, matters.

Yes, and most do — the match type is typically configured per purchase category or vendor, not fixed company-wide. Services and subscriptions running 2-way alongside physical goods running 3-way within the same AP process is standard.

The invoice can't clear automatically — it sits in exception until someone either creates the missing receiving confirmation or manually overrides the match, which is exactly the friction point that turns into an AP bottleneck at volume.

Sources

Topic

AP & Invoice Processing

Accounts payable and invoice processing is the set of steps a vendor bill goes through between arriving at a company and turning into a payment: capturing what the vendor sent, checking it against wha…

Diagnostic

What causes a three-way match failure between the PO, receipt, and invoice?

A three-way match compares the PO, the receipt (what was actually delivered), and the invoice on quantity, price, and charges. A failure means one of those three disagrees beyond tolerance — usually because the invoice bills a quantity that isn't fully receipted yet, the unit price differs from the PO, or the invoice adds a charge, like freight, the PO never included.

Diagnostic

Why did we pay the same vendor invoice twice?

Almost always one of two things: the vendor exists as two separate records in your vendor master, so a duplicate-invoice-number check that only compares within one vendor ID never sees the second copy — or the invoice was entered twice by different people, because it arrived through two channels and each assumed they had the only copy.

Definition

What is the procure-to-pay process?

Procure-to-pay (P2P) is the full cycle from identifying a need to actually paying for it: a requisition (internal request), a purchase order (formal authorization sent to a supplier) once approved, delivery of the goods or services, an invoice, matching, and finally payment. Each step exists to keep the business from paying for something it never actually ordered or received.