Three-Way Match: Glossary

Three-way match compares invoice, purchase order and receipt. Learn what it catches, what it misses, and how it relates to margin drift. Read the full guide.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Three-Way Match: Glossary

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. Three-way match is a different control: it compares the invoice against the purchase order and the receiving record, checking that the quantity and price billed match what was ordered and what arrived. It answers "did we get what we paid for," not "did we pay the right price under the contract." Understanding that boundary matters, because a passed three-way match is often treated as proof an invoice is clean.

That proof is narrower than it looks. A three-way match can pass while a rate card is stale, a rebate is unapplied, or a surcharge has outlived its trigger condition.

1. What is three-way match?

Three-way match is an AP control that compares three documents before an invoice is approved for payment: the purchase order, the goods receipt or service confirmation, and the vendor invoice. It confirms that the quantity ordered, the quantity received, and the quantity billed agree, and that the unit price on the invoice matches the price recorded on the purchase order. If the three documents agree within tolerance, the invoice moves to payment.

The control exists to stop payment for goods never ordered or never received, and to catch simple price entry errors against the PO. It runs inside the ERP or AP automation platform at the point the invoice is entered, before payment.

It is a pre-payment gate, not a contract audit.

2. What does three-way match actually check?

Three-way match checks three fields: quantity ordered versus quantity received versus quantity billed, and unit price on the invoice versus unit price on the purchase order, usually within a set tolerance band. It operates against the purchase order as the reference point. If the purchase order itself carries an outdated or incorrect price, the match will pass, because the control tests agreement between documents, not agreement with the underlying contract terms.

This is why a passed match is not the same as a compliant invoice. The purchase order is the reference document, and a purchase order is only as accurate as the price it was cut against.

  • Quantity check: Confirms units ordered, received and billed line up before payment releases.
  • Price check: Confirms the invoice unit price matches the PO unit price within tolerance.
  • Reference document: Tests against the purchase order, not the contract, so a stale PO price passes cleanly.

3. What does three-way match miss?

Three-way match does not test whether the price on the purchase order reflects the current rate card, whether a volume tier has been crossed, whether a rebate clause applies, or whether a surcharge is still contractually valid. Those terms usually live in a contract document outside the ERP, not in the PO record the match reads against. A PO cut at last year's rate will match an invoice billed at that same stale rate every time.

This is the gap contract compliance work addresses. It checks the invoice against the contract directly, not against a PO that may already be wrong.

Examples of terms three-way match cannot see include a rate card update, a volume tier crossing, a rebate clause, an index escalation, and a minimum commitment shortfall.

4. How does three-way match relate to margin drift?

Three-way match and a margin drift review test different reference points. Three-way match tests the invoice against the purchase order and the receipt. A margin drift review tests the invoice against the contract itself, including rate cards, volume tiers, rebate clauses and surcharge schedules.

An invoice can pass three-way match cleanly and still carry margin drift, because the purchase order it was checked against never reflected the contract term that changed.

This is why contract compliance work is a separate layer rather than a stricter setting on the existing match. It reads a different source document.

For the wider pattern this sits inside, start with the margin drift guide.

5. Frequently Asked Questions (People Also Ask)

Is three-way match the same as a contract compliance audit?

No. Three-way match compares the invoice, purchase order and receipt. A contract compliance audit compares the invoice against the underlying contract terms, such as a rate card or rebate clause, which the purchase order may not reflect accurately.

Can an invoice pass three-way match and still be overbilled?

Yes. Three-way match tests agreement between the invoice, the PO and the receipt. If the PO price itself is stale or the contract term changed after the PO was cut, the invoice can match the PO exactly and still diverge from the contract.

Does three-way match catch duplicate payments?

Three-way match is not designed to catch duplicate payments; that is typically a separate control looking for repeated invoice numbers, amounts or vendor references across the payment history.

Does three-way match check volume tier pricing?

No. Three-way match checks the invoice against the purchase order price, not against a volume tier schedule. A volume tier crossing that should trigger a lower rate is invisible to this control unless the PO itself was updated.

What tolerance does three-way match use?

Tolerance bands are set by the AP system configuration, commonly a small dollar or percentage variance allowed between the PO price and the invoiced price before the match fails and routes for manual review.

Who is responsible for running three-way match?

The AP team configures and operates three-way match inside the ERP or AP automation platform. It runs automatically as invoices are entered, before payment approval.

1. What is three-way match?

Three-way match is an AP control that compares three documents before an invoice is approved for payment: the purchase order, the goods receipt or service confirmation, and the vendor invoice. It confirms that the quantity ordered, the quantity received, and the quantity billed agree, and that the unit price on the invoice matches the price recorded on the purchase order. If the three documents agree within tolerance, the invoice moves to payment. The control exists to stop payment for goods never ordered or never received, and to catch simple price entry errors against the PO. It runs inside the ERP or AP automation platform at the point the invoice is entered, before payment. It is a pre-payment gate, not a contract audit.

2. What does three-way match actually check?

Three-way match checks three fields: quantity ordered versus quantity received versus quantity billed, and unit price on the invoice versus unit price on the purchase order, usually within a set tolerance band. It operates against the purchase order as the reference point. If the purchase order itself carries an outdated or incorrect price, the match will pass, because the control tests agreement between documents, not agreement with the underlying contract terms. This is why a passed match is not the same as a compliant invoice. The purchase order is the reference document, and a purchase order is only as accurate as the price it was cut against. - Quantity check: Confirms units ordered, received and billed line up before payment releases. - Price check: Confirms the invoice unit price matches the PO unit price within tolerance. - Reference document: Tests against the purchase order, not the contract, so a stale PO price passes cleanly.

3. What does three-way match miss?

Three-way match does not test whether the price on the purchase order reflects the current rate card, whether a volume tier has been crossed, whether a rebate clause applies, or whether a surcharge is still contractually valid. Those terms usually live in a contract document outside the ERP, not in the PO record the match reads against. A PO cut at last year's rate will match an invoice billed at that same stale rate every time. This is the gap contract compliance work addresses. It checks the invoice against the contract directly, not against a PO that may already be wrong. Examples of terms three-way match cannot see include a rate card update, [a volume tier](/glossary/volume-tier) crossing, [a rebate clause](/glossary/rebate-clause), [an index escalation](/glossary/index-escalation-misapplied), and [a minimum commitment shortfall](/glossary/minimum-commitment-shortfall).

4. How does three-way match relate to margin drift?

Three-way match and a margin drift review test different reference points. Three-way match tests the invoice against the purchase order and the receipt. A margin drift review tests the invoice against the contract itself, including rate cards, volume tiers, rebate clauses and surcharge schedules. An invoice can pass three-way match cleanly and still carry margin drift, because the purchase order it was checked against never reflected the contract term that changed. This is why contract compliance work is a separate layer rather than a stricter setting on the existing match. It reads a different source document. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide.

Questions & Answers

Is three-way match the same as a contract compliance audit?

No. Three-way match compares the invoice, purchase order and receipt. A contract compliance audit compares the invoice against the underlying contract terms, such as a rate card or rebate clause, which the purchase order may not reflect accurately.

Can an invoice pass three-way match and still be overbilled?

Yes. Three-way match tests agreement between the invoice, the PO and the receipt. If the PO price itself is stale or the contract term changed after the PO was cut, the invoice can match the PO exactly and still diverge from the contract.

Does three-way match catch duplicate payments?

Three-way match is not designed to catch duplicate payments; that is typically a separate control looking for repeated invoice numbers, amounts or vendor references across the payment history.

Does three-way match check volume tier pricing?

No. Three-way match checks the invoice against the purchase order price, not against a volume tier schedule. A volume tier crossing that should trigger a lower rate is invisible to this control unless the PO itself was updated.

What tolerance does three-way match use?

Tolerance bands are set by the AP system configuration, commonly a small dollar or percentage variance allowed between the PO price and the invoiced price before the match fails and routes for manual review.

Margin Drift Resources