3-Way Matching in Accounts Payable: Process & Controls

3-way matching in accounts payable compares a supplier invoice with the purchase order and the record of goods or services received before the invoice is approved for payment. The control helps businesses identify quantity, price, or receipt discrepancies before cash leaves the company. It works best when matching rules, tolerances, exception ownership, and approval responsibilities are clearly defined rather than requiring every invoice to match manually line by line.

For purchase-based organizations, three-way matching creates a simple control question:

Did we order it?
Did we receive it?
Are we being billed correctly?

If those three records align within approved tolerances, the invoice can continue through the AP workflow.

If they do not, the transaction becomes an exception that needs review.

What Is 3-Way Matching in Accounts Payable?

3-way matching in accounts payable validates three records relating to the same purchase:

1. Purchase Order (PO) — what the business authorized
2. Goods Receipt / Service Receipt — what the business actually received
3. Supplier Invoice — what the vendor is requesting payment for

SAP’s current S/4HANA documentation similarly describes three-way matching as the comparison of the supplier invoice with the purchase order and goods receipt before invoice approval and posting.

The purpose is not to prove that every document is identical down to every field.

The purpose is to confirm that the payment request is supported by the underlying purchase and receipt records.

For example:

The transaction matches.

Now consider:

Here the invoice should normally require review because the company has only recorded receipt of 80 units.

That is the practical value of 3-way matching in accounts payable: the control identifies the exception before payment rather than relying on reconciliation after the cash has already moved.

2-Way vs. 3-Way vs. 4-Way Matching

Not every invoice requires the same level of verification.

Two-Way Matching

Two-way matching compares:

Purchase Order ↔ Supplier Invoice

It checks whether the vendor, quantities, prices, and terms being invoiced align with what was ordered.

SAP Ariba documentation notes that two-way matching can be used for PO line items that do not require a receipt.

This can fit recurring or lower-risk purchases where separate receipt confirmation adds limited control value.

Three-Way Matching

Three-way matching adds:

Goods Receipt / Service Receipt

Now AP can verify not only that the purchase was authorized, but also that the company has recorded receipt before paying.

Four-Way Matching

Four-way matching introduces an additional inspection or quality-acceptance record.

It may be useful for purchases where payment depends not simply on delivery, but also on verification that received goods meet defined quality requirements.

More controls are not automatically better.

The matching method should reflect the value, complexity, and risk of the purchase.

For most PO-based purchasing environments, 3-way matching in accounts payable provides a practical balance between payment control and processing efficiency because it verifies both purchasing authorization and actual receipt before payment.

How the 3-Way Matching Process Works

A typical workflow is:

PO created → Goods/services received → Receipt recorded → Invoice received → Match → Resolve exceptions → Approve → Pay

Purchase Order Is Created

The process begins before the supplier invoice arrives.

The purchase order establishes what has been approved, including information such as:

• Supplier
• Item or service
• Quantity
• Price
• Currency
• Payment terms
• Entity
• Cost center

Without reliable purchase-order data, later matching becomes much harder.

Receipt Is Recorded

When the goods or services are received, the organization needs evidence of receipt.

Depending on the process, this could be:

• Goods Receipt Note
• Warehouse receipt
• Service entry sheet
• Digital receiving record

This step is essential because an invoice can accurately reference a valid PO even when only part of the order has actually been delivered.

Supplier Invoice Arrives

The invoice typically contains:

• Vendor
• Invoice number
• PO reference
• Quantity
• Unit price
• Tax
• Freight
• Total amount

AP or the automation platform then associates the invoice with the relevant purchasing records.

The Three Records Are Compared

The 3-way matching in accounts payable process may evaluate fields such as:

Vendor → PO → Quantity → Price → Receipt → Invoice

Straightforward matches can proceed.

Differences are flagged.

Exceptions Are Reviewed

An exception does not automatically mean fraud or error.

It may result from:

• Partial delivery
• Agreed price adjustment
• Freight
• Tax
• Timing
• Unit-of-measure differences
• Updated contract terms

The goal is to route these exceptions to the person best able to resolve them.

Approved Invoice Moves to Payment

Once the required match and approvals are complete, the invoice can continue to payment scheduling.

For the wider invoice-to-payment workflow, see Accounts Payable Process: Steps & Best Practices.

What Should Be Matched?

A strong matching process defines the fields that matter rather than applying vague “everything must match” rules.

Supplier

The supplier on the invoice should correspond with the approved PO vendor.

Unexpected vendor changes should trigger investigation.

Quantity

The invoiced quantity should be supported by:

• ordered quantity, and
• received quantity.

Partial receipts require particular care.

Unit Price

The invoice should reflect the agreed purchase price, subject to approved tolerance rules.

Purchase Order

Invoices should reference an authorized PO where the company’s procurement policy requires one.

Receipt

The receipt confirms that the underlying goods or services were accepted before payment.

Other Charges

Tax, freight, discounts, and other charges may require separate matching logic.

This is where a rigid manual process often becomes inefficient.

Not every legitimate transaction will have identical numbers across every field.

Use Tolerances Instead of Treating Every Difference as an Error

A mature 3-way matching in accounts payable process distinguishes a material discrepancy from an insignificant variance.

For example:

PO price: $1,000
Invoice: $1,000.50

Automatically escalating a $0.50 difference through multiple approval levels may cost more than the discrepancy itself.

Organizations can therefore define matching tolerances based on:

• Absolute amount
• Percentage
• Quantity
• Supplier
• Spend category
• Invoice value

For example:

These are illustrative rules, not universal thresholds.

Tolerance levels should reflect the company’s risk appetite, transaction values, purchasing agreements, and control environment.

SAP Concur’s current three-way matching functionality similarly uses configurable matching rules to determine how variances between invoice, PO, and receipt records should be handled.

Common 3-Way Matching Exceptions

Knowing why invoices fail to match is more useful than simply measuring how many fail.

Effective 3-way matching in accounts payable should therefore classify exceptions by root cause so Finance can distinguish supplier issues from procurement, receiving, system, or AP problems.

Quantity Mismatch

Example:

PO: 100 units
Received: 80
Invoice: 100

Potential response:

Verify whether the remaining goods are still in transit or the supplier invoiced prematurely.

Price Mismatch

Example:

PO: $50/unit
Invoice: $55/unit

Check:

• contract changes,
• purchasing approval,
• freight,
• or pricing error.

Missing Receipt

The invoice and PO may match, but no receipt exists.

Possible causes include:

• Receiving team has not posted the receipt
• Service completion was not documented
• Goods have not arrived

Missing PO

An invoice arrives with no valid purchase order.

The correct response depends on the organization’s non-PO policy rather than automatically paying or rejecting it.

Duplicate Invoice

The same invoice may arrive through:

• Email
• Vendor portal
• Resubmission

Duplicate detection should operate alongside matching controls.

Understanding exception types allows finance to distinguish:

AP problem → Procurement problem → Receiving problem → Supplier problem

That is more useful than treating all failed matches as an AP issue.

When Should You Use 3-Way Matching?

Not every invoice should necessarily go through full three-way verification.

3-way matching in accounts payable is particularly useful for:

• Inventory
• Equipment
• Raw materials
• High-value purchases
• Variable-quantity purchasing
• PO-based procurement

Two-way or other controls may be appropriate for:

• Rent
• Utilities
• Fixed subscriptions
• Certain professional services
• Other transactions where a formal receipt is not part of the operating model

This is a risk-based decision.

Requiring a receiving record for a monthly SaaS subscription may create administrative work without adding meaningful protection.

A well-designed AP policy defines which transactions require which control before invoices enter the workflow.

Why 3-Way Matching Matters

Prevents Unsupported Payments

The supplier invoice alone proves that a vendor is requesting money.

It does not prove that the purchase was approved or received.

Matching creates supporting evidence before payment.

Reduces Overpayments

Quantity and price checks can identify:

• Overbilling
• Partial delivery
• Incorrect rates
• Duplicate charges

before payment.

Strengthens Purchasing Discipline

If PO-based purchases require valid matching, departments have a stronger incentive to follow approved procurement procedures.

Improves Auditability

The PO, receipt, invoice, exception resolution, and approval together create a more traceable transaction history.

Makes Exceptions Visible

Perhaps the most operationally useful benefit is visibility.

Instead of AP staff discovering issues manually during payment preparation, matching can surface them earlier and route them to the right owner.

Manual vs. Automated 3-Way Matching

Manual matching typically requires AP employees to:

• Locate PO
• Locate receipt
• Open invoice
• Compare fields
• Investigate variance
• Record approval

At low volume, this may be manageable.

At scale, the number of document touches becomes significant.

Automating 3-way matching in accounts payable can reduce those repetitive comparisons by allowing compliant invoices to move through predefined rules while sending material mismatches to human reviewers.

SAP Concur’s 2026 AP Automation Trends research found that 77% of organizations still manually enter invoices into accounting systems, while only 7% describe their AP function as fully automated. Among organizations already using AI in AP, 49% use it for invoice matching and approvals.

Automation can help by:

Invoice captured
↓
PO located
↓
Receipt retrieved
↓
Matching rules applied
↓
Matched → Continue
Exception → Human review

This changes the role of AP staff.

Instead of checking every standard invoice, they can focus on exceptions.

For a broader software evaluation, see Accounts Payable Automation Software: 2026 Guide.

Straight-Through Processing vs. Exception Management

The objective of automation should not be:

Automate every invoice.

A stronger target is:

Automatically process transactions that meet approved rules and make exceptions visible quickly.

SAP Concur documentation supports both configurable match exceptions and straight-through processing where invoices meet the relevant rules.

That creates two lanes:

Standard Invoice

Match → Approval → Payment

Exception Invoice

Mismatch → Reason identified → Appropriate owner → Resolution → Approval

This is more scalable than adding additional AP staff solely to perform repetitive document comparisons.

How to Measure 3-Way Matching Performance

Useful KPIs include:

Avoid optimizing match rate in isolation.

A 99% auto-match rate is not impressive if tolerances have been set so broadly that important discrepancies are ignored.

For a wider AP performance framework, see Accounts Payable Metrics: How to Measure AP Performance.

What a Stronger AP Control Process Looks Like in Practice

Three-way matching is one control within a wider AP environment.

An Innovature finance stabilization engagement provides a useful example of why pre-payment review and traceability matter.

A fast-growing FDI manufacturer in Vietnam was simultaneously:

• Keeping BAU finance operations running
• Resolving historical accounting gaps
• Preparing for a Microsoft Dynamics 365 transition.

The existing AP environment had incomplete records, unreconciled positions, and weak traceability. Innovature’s recovery process established the invoice population, confirmed balances, traced source documents, reviewed accounting treatment, and standardized the AP workflow through a dedicated SOP.

Importantly, stronger review checkpoints caught a duplicate payment before approval and surfaced unreconciled transactions during the recovery process.

The engagement ultimately improved posting completion from 86% to 100%, reviewed and processed approximately 800 invoices, and identified 100+ previously unrecorded invoices.

This case was broader than three-way matching itself, so these results should not be attributed specifically to that control.

It illustrates the larger principle behind 3-way matching in accounts payable:

Financial controls are most valuable when they identify missing, duplicated, or inconsistent information before those problems flow further into payment or the general ledger.

How to Improve a 3-Way Matching Process

A practical improvement program should focus on four areas.

Improving 3-way matching in accounts payable starts with the quality of the purchasing and receiving data, not simply with adding another approval step inside AP.

Improve Source Data

Matching quality depends on:

• PO accuracy
• Timely receiving records
• Supplier invoice quality
• Clean vendor data

Bad upstream data creates downstream exceptions.

Apply supplier master data controls alongside matching rules to keep vendor identities, record changes, and payment details properly verified and approved. A successful invoice match does not independently validate a newly supplied bank account.

Define Matching Policy

Specify:

• Which purchases require 3-way matching
• Which use 2-way matching
• Which variances are tolerable
• Who resolves each exception

Track Root Causes

Do not simply measure the exception count.

Categorize:

• Procurement
• Receiving
• Supplier
• AP
• System

Repeated exceptions should lead to process improvement.

Automate Standard Transactions

Use technology where invoice volume makes manual checking inefficient.

Human review should remain focused on:

• Material exceptions
• Unusual transactions
• Supplier changes
• High-risk payments
• Judgment calls

Frequently Asked Questions

1. What is 3-way matching in accounts payable?

It is the comparison of a supplier invoice, purchase order, and goods or service receipt before payment. The control verifies that the purchase was authorized, received, and billed consistently.

2. What is the difference between 2-way and 3-way matching?

Two-way matching compares the PO and invoice.

Three-way matching adds the receipt, providing evidence that the goods or services were actually received.

3. Is three-way matching required for every invoice?

No. Companies may use different matching controls based on transaction type and risk. Recurring or non-PO expenses may follow different approval procedures.

4. What happens if an invoice fails the match?

The invoice becomes an exception. The appropriate team—such as AP, Procurement, Receiving, or the supplier—should investigate and resolve the discrepancy before payment according to company policy.

5. Can three-way matching be automated?

Yes. Modern AP platforms can retrieve purchasing and receipt data, compare fields using predefined rules, auto-process compliant transactions, and route exceptions for review.

6. Does 3-way matching eliminate invoice fraud?

No.

It can reduce certain types of unsupported or incorrect payment risk, but it does not eliminate all fraud. Vendor-master controls, access controls, segregation of duties, approval authority, duplicate detection, and payment controls remain important.

3-Way Matching Works Best as an Exception Control

The value of 3-way matching in accounts payable is not that every invoice receives more manual scrutiny.

Its value is that the finance process can distinguish:

Authorized and received purchases

from

transactions that require investigation.

A good matching model defines which invoices need three-way control, maintains reliable PO and receipt data, uses sensible tolerances, assigns exception ownership, and measures whether the process is actually reducing risk without creating unnecessary payment delays.

Technology can perform more of the comparison.

People still need to decide what an exception means and whether it is acceptable.

That balance turns three-way matching from an administrative check into a practical AP control.