Buying

3-Way Matching in Accounts Payable: Process, Example and Journal Entries

This guide covers how 3-way matching actually works, who's involved and why, a worked example with a real discrepancy, what it looks like in the journal entries, and how to automate it without losing the control it's built to enforce.
Published on:
September 22, 2026
Ajay Ramamoorthy
Senior Content Marketer
Karthikeyan Manivannan
Visual Designer
3-Way Matching in Accounts Payable: Process, Example and Journal Entries
Join the World's First Procurement Engineering Community.
Join Now

3-way matching in accounts payable compares the purchase order, the receiving report and the vendor invoice before a payment goes out, confirming what was ordered, what actually arrived, and what's being billed all agree.

Key Takeaway
  • 3-way matching compares the PO, the receiving report (GRN) and the invoice. 2-way matching skips the receiving report, checking only the PO against the invoice.
  • The process typically involves four teams: procurement (raises the PO), receiving (confirms delivery), AP (runs the match), and audit (tests it as a control).
  • A completed match doesn't post its own journal entry. It's the gate that determines whether the AP accrual entry already on the books can convert to an actual vendor payment.
  • The most common manual pitfall is a discrepancy that gets overridden under deadline pressure instead of investigated, which quietly defeats the entire point of the control.
  • 3-way matching is one of the internal controls auditors specifically test for segregation of duties, since it structurally prevents one person from ordering, receiving and paying for the same purchase.

What is 3-way matching in accounts payable?

3-way matching is an internal control that requires three separate documents to agree before an invoice gets paid: the purchase order (what was ordered), the receiving report (what actually arrived), and the vendor invoice (what's being billed). If all three line up, on item, quantity and price, the invoice clears for payment. If they don't, it gets flagged.
‍

The word "internal control" matters here, not just "process." Accounts payable teams use 3-way matching specifically because it structurally prevents a single person from ordering something, confirming its own delivery, and approving payment for it, which is exactly the kind of gap fraud and simple error both exploit.

A staff accountant or AP clerk running the match isn't just checking numbers; they're enforcing segregation of duties across three functions that usually sit with three different people.
‍

How does the 3-way matching process actually work?

The process runs in four steps: a PO gets raised, goods arrive and get logged, an invoice comes in, and AP compares all three before releasing payment.
‍

  • Purchase order is issued - Procurement raises a PO with item, quantity and agreed price, creating the baseline everything else gets checked against.
  • Goods are received and logged - Whoever receives the delivery records what actually arrived, ideally before anyone's seen the invoice, so the receiving record isn't influenced by what the invoice says.
  • Invoice arrives - The vendor submits their invoice, referencing the PO number where possible to make the match easier.
  • AP compares all three documents - Item, quantity and price get checked across the PO, the receiving report and the invoice. A clean match clears for payment. A discrepancy, an overbilled quantity, a price that doesn't match the PO, gets routed for review instead of paid automatically.
    ‍

What's the difference between 2-way and 3-way matching?

2-way matching checks the invoice against the purchase order only. 3-way matching adds the receiving report as a third check.

MethodDocuments comparedBest fit for
2-way matchingPurchase order + invoiceLow-risk, low-value purchases, especially services with no physical delivery to confirm
3-way matchingPurchase order + receiving report + invoicePhysical goods, higher-value purchases, and any category where confirming actual delivery matters

Neither method is universally correct. A company running 3-way matching on every single purchase, including a $40 office supply order, is adding audit overhead with no real fraud or error benefit. The judgment call is matching the control to the risk, not applying the strictest version everywhere by default.

The right control for the right risk. Not one rule for every purchase.

Book a demo

What documents are involved, and who handles them?

The three documents in the process above come from three different functions, which is the actual point of the control, not a coincidence of how the paperwork happens to flow.
‍

  • Purchase order (PO) -  Raised by procurement or purchasing, it's the authorized record of what was ordered, at what price, in what quantity, and it's the baseline every later check gets compared against.
  • Receiving report (also called a GRN, goods receipt note) - Logged by the receiving or warehouse team, independently of anyone who's seen the invoice, which is exactly what makes it a real check rather than a formality.
  • Vendor invoice - Submitted by the supplier, stating what they're billing for, and the only one of the three documents that comes from outside the company.
  • AP clerk or specialist - Runs the actual match, comparing all three and flagging discrepancies rather than resolving them unilaterally, since resolving a mismatch usually requires input from whoever owns the vendor relationship.
  • Internal audit - Periodically tests whether the match is actually being performed correctly, since a control that exists on paper but gets routinely overridden isn't functioning as a control at all.
    ‍

A worked example of 3-way matching

Here's what a real discrepancy looks like in practice: quantities that agree, a price that doesn't, and how it gets resolved.
‍

A company orders 500 units of packaging material at $2 per unit, a $1,000 purchase order. The warehouse receives the shipment and logs 500 units delivered, confirming quantity matches. The vendor's invoice arrives for $1,050, billing 500 units at $2.10 each.
‍

The PO and the receiving report agree on quantity. The invoice doesn't agree with the PO on price. That's a discrepancy, not a rejection, and it gets routed back to whoever manages the vendor relationship to confirm whether the higher price was a legitimate, documented increase or simply an error on the vendor's invoice. Only once that's resolved does the invoice clear for payment, at whichever price is actually correct.
‍

What does 3-way matching look like in the journal entries?

A completed 3-way match doesn't create a new journal entry by itself. It's the gate that determines whether an existing accrual can convert into an actual cash payment.

Most companies book an accrual when goods are received, debiting an expense or inventory account and crediting accrued accounts payable, based on the PO and receiving report, before the invoice even arrives.

When the invoice shows up and passes the 3-way match, AP reverses that accrual and records the actual vendor invoice: debit the expense or inventory account, credit accounts payable, at the confirmed invoice amount.

When payment goes out, AP gets debited and cash gets credited. If the match reveals a discrepancy, the entry doesn't post until it's resolved, which is exactly why an unresolved match sitting in the AP subledger is a common item auditors ask about during a close review.
‍

What are the benefits of 3-way matching?

3-way matching delivers four concrete benefits: fraud prevention, cost savings, stronger audit readiness, and better supplier relationships.
‍

  • Fraud prevention - Segregation of duties across procurement, receiving and AP makes it structurally harder for one person to order, receive and approve payment for the same fictitious purchase.
  • Fewer costly errors - Overpayments, duplicate payments, and paying for items that were never actually delivered are exactly the mistakes a completed 3-way match catches before money moves, not after.
  • Audit readiness - For SOX-compliant and publicly traded companies especially, 3-way matching is a named control auditors specifically test, and a documented, consistently applied process makes that test straightforward instead of a scramble.
  • Better supplier relationships - Vendors get paid the correct amount on time more consistently when discrepancies get caught and resolved early rather than discovered during a dispute months later.
    ‍

What are the common pitfalls of manual 3-way matching?

Manual 3-way matching breaks down four predictable ways as invoice volume grows: discrepancies get overridden, receiving checks get skipped, the process doesn't scale, and documents end up scattered across three systems. Almost all of them trace back to the same root cause: someone under time pressure taking a shortcut the control wasn't designed to allow.
‍

  • Discrepancies get overridden instead of investigated - Under deadline pressure, "close enough" quietly becomes the actual standard, which defeats the entire purpose of the control.
  • The receiving report gets skipped or backdated - If receiving logs what arrived only after seeing the invoice, the receiving check stops being an independent verification and becomes a rubber stamp.
  • It doesn't scale past a certain invoice volume - A few dozen invoices a month is manageable by eye. A few hundred is where mismatches start slipping through simply because nobody has time to check every line item.
  • Documents live in three different places. POs in procurement, receiving logs in a warehouse system, invoices in email, and AP manually pulling all three together for every single invoice.

Three documents, pulled together automatically.

Book a demo

How do you automate 3-way matching?

Automating 3-way matching means the system pulls the PO, receiving record and invoice together automatically and only routes genuine discrepancies to a person, instead of someone manually retrieving and comparing all three documents by hand.

This is one specific stage within the broader AP automation workflow, and it's usually the single highest-value stage to automate first, since it's also the most time-consuming to do manually at any real invoice volume.

Automated matching applies tolerance rules for minor, expected variances, a slightly different unit price within an agreed range, so only genuine mismatches get flagged for review instead of every invoice needing a human look.
‍

How Flo handles 3-way matching automatically

Flo Procure runs 3-way matching against data it already has: automatic matching with tolerance rules, discrepancy routing with full context attached, benchmark-checked pricing, and a complete audit log.

Matching starts with real records instead of a fresh document hunt, since the purchase order and approval from intake, and the receiving confirmation, are already sitting in the system.
‍

  • Invoices get matched automatically against the purchase order and receiving record the moment they arrive, with tolerance rules applied so minor variances don't stall every invoice
  • Genuine discrepancies route to the right person automatically, with the original PO and approval history already attached
  • Real pricing benchmarks catch a price discrepancy against market rate, not just against the PO
  • Every match, resolved or flagged, is logged, so a procurement audit or a SOX control test starts with a complete record instead of a document search

3-way matching that starts with records you already have.

Book a demo

Frequently asked questions about 3-way matching in accounts payable

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

3-way matching compares the purchase order, the receiving report and the vendor invoice before payment, confirming what was ordered, what arrived and what's being billed all agree. It's an internal control, not just a processing step.
‍

2. What's the difference between a 2-way match and a 3-way match in SAP?

The underlying logic is the same in SAP as anywhere else: 2-way matching checks the invoice against the purchase order only, while 3-way matching adds the goods receipt (SAP's term for the receiving report) as a third check before the invoice can be released for payment.
‍

3. What documents are needed for 3-way matching?

The purchase order, the receiving report or goods receipt note, and the vendor invoice. All three need to agree on item, quantity and price before payment clears.
‍

4. Who is responsible for 3-way matching?

AP typically runs the match itself, but it depends on documents from procurement (the PO) and receiving (the goods receipt), which is exactly why the control works: no single person controls all three inputs.
‍

5. Does 3-way matching create a journal entry?

Not on its own. It's the gate that determines whether an existing accrual, booked when goods were received, can convert into the actual vendor invoice entry and eventually a cash payment. An unresolved match blocks that entry from posting.
‍

6. Why is 3-way matching important for internal controls?

It enforces segregation of duties by structurally requiring three different functions, procurement, receiving and AP, to independently confirm a purchase before payment. That's specifically what auditors test for in SOX and other internal control reviews.
‍

7. When should you use 2-way matching instead of 3-way matching?

For low-risk, low-value purchases, especially services with no physical delivery to confirm, 2-way matching is usually sufficient. Reserving 3-way matching for higher-value or higher-risk categories avoids adding audit overhead where it doesn't add real protection.
‍

8. Can 3-way matching be automated?

Yes, and it's usually the highest-value stage of AP automation to tackle first, since it's the most time-consuming to do manually and the easiest to configure with tolerance rules for minor, expected discrepancies.

Better Procurement, straight to your inbox

Latest trends and best practices for finance and procurement teams.

By clicking “Submit”, I agree to Spendflo’s Terms and Privacy Policy.
You’re on the list. Look for the next issue in your inbox.
Something went wrong. Please try again!

Need a rough estimate before you go further?

Here's what the average Spendflo user saves annually:
$2 Million
Your potential savings
$600,000
Rating showing 4.6 out of 5 stars with four full stars and one partial star.Laptop screen showing a man pointing at a dollar symbol surrounded by floating digital documents.

Every request, approval and
renewal in one place.
‍
Trusted by 300+ procurement and finance teams.
Our monthly newsletter full of inspiration, trends and latest releases.
Book a Demo

Table of contents

Talk to one of our expert buyers

Find out why dozens of Finance and procurement leaders use Spendflo to optimize their SaaS spend.

You can schedule a meeting time on the next screen.
In your demo with one of our expert buyers:
Renewals done for you
No more requests stuck in approval queues
No more contracts signed without a risk check
No more invoices paid without a PO match
4.6/5 on G2
With Spendflo, we finally have unified visibility. We can look in one portal and see all our spend, upcoming renewals, and how we’re actually using the licenses we’re paying for.
Josh Rappoport
VP Finance, Acumatica
G2 Summer 2026 High Performer badge for mid-market shown with red and yellow stripes.G2 badge for Summer 2026 award, Fastest Implementation, with G2 logo on top right.Badge reading Summer 2026 High Performer with a G2 logo in the corner.
In your demo with one of our expert buyers:

To date, with Spendflo:

$3.7B
software spend processed
30%
average savings
300+
procurement and finance teams