UPDATED AUGUST 2026
The invoice landed Tuesday. 24 brake rotors at $94.25 each. The purchase order said $89.50. The receiving log said 22.
Accounts payable teams have one mission: make sure suppliers get paid accurately and on time, without overpaying, duplicating payments, or introducing unnecessary risk. The hard part is that the proof lives in three different places.
Between manual processes, miscommunications across departments, and a constant flow of invoices, it’s easy for errors to slip through. That’s where 2-way, 3-way, and 4-way matching come in. These checks are among the most effective internal controls finance teams can use to ensure accuracy and prevent financial leakage.
Pair matching with automation and you get a streamlined, audit-ready AP process, plus a record of every purchase your team can actually report on.
Let’s walk through how each type of matching works, when to use each one, and what gets easier when the documents land in one place.
How 2-Way Matching Works
Here’s a common scenario. Your team places an order for 500 ergonomic office chairs at $120 each. A few days later, an invoice lands in your inbox, but it lists 550 chairs at $135 each. That's $74,250 billed against a $60,000 order.
Without checks in place, that overpayment could easily fly under the radar. But with 2-way matching, the invoice is automatically compared to the original purchase order. Any pricing or quantity discrepancies trigger a flag.
What the check does:
2-way matching is the right fit when there is nothing to receive. Managed IT contracts, software subscriptions, utilities, rent, professional fees. No pallet arrives, so no receiving record exists to check against. The PO and the invoice are the only two documents in play, and comparing them is enough.
Requiring more than that on a services invoice creates exceptions nobody can clear, because the missing document is never coming.
What 2-Way Matching Misses
Notice what the chair example does not tell you: whether 500 chairs, 550 chairs, or 300 chairs actually showed up. The math can reconcile perfectly while the delivery falls short. For anything physical, that gap is the whole risk.
How 3-Way Matching Works
Let’s say you ordered 1,000 feet of steel tubing at $6.40 a foot. The PO and invoice match at $6,400, but your receiving team logs only 800 feet. Whether it was short-shipped or delayed, the mismatch means you are about to pay $1,280 for tubing that never arrived.
3-way matching fills that gap by introducing the receiving report. It verifies not just what was ordered and billed, but what was physically received.
What the check does:
When To Use 3-Way Matching
Use it for anything physical. Parts, inventory, raw materials, equipment, consumables. If something has to arrive somewhere before you owe for it, the receiving record is not optional.
This is the level most finance teams should be running on goods spend, and the one most often skipped.
Why 3-Way Matches Fail
Not because the rule is complicated. Because receiving happens somewhere else.
The PO sits in your ERP or DMS. The invoice arrives by email. The receiving record sits with the parts counter, the warehouse, or the shift that signed for the delivery. Executing the match means going and getting all three, which is fine on a $40,000 invoice and quietly doesn't happen on a $600 one.
That is where the control erodes. Not in a decision to skip it, but in a hundred small triage calls nobody logs. Most of these breakdowns start upstream, in how requisitions and POs get created. Our procure-to-pay process guide walks the full cycle.
The added closing line replaces what the stat was doing. It generalizes the $40,000 versus $600 point into a claim about how controls actually fail, which is the argument, and it needs no citation because it's reasoning rather than data.
No imagine the shipment arrives in full. Then inspection finds 20% of the material out of spec. On an $18,000 order, that's $3,600 you shouldn't pay for.
If you’re only relying on the PO and receiving slip, AP might approve the full payment without knowing that part of the shipment was rejected. The receiving record says it showed up. It doesn't say anyone accepted it.
That gap is what 4-way matching closes. It add a final step: verification that what was received was also accepted by your quality or compliance team.
What the check does:
When to Use 4-Way Matching
Use it where receiving and accepting are genuinely separate events. Manufacturing, healthcare, construction, food and beverage, aerospace. Anywhere material has to clear a spec, safety, or compliance check before it can be used.
Note where that acceptance record lives. Not in finance. It sits with QA, the shop floor, the service department, or a third-party inspector. 4-way matching is the level that most obviously depends on operations data reaching the people approving payment.
When 4-Way Matching Is Overkill
Adding an inspection gate to spend that has no inspection step creates a fourth document that is never coming. The invoice sits in exception, someone eventually overrides it, and the override becomes routine. That is worse than a 3-way match, because now you have a control your audit trail says exists and your team has learned to bypass.
Match the level to the purchase, not to the highest standard available.
2-Way vs. 3-Way vs. 4-Way Matching: A Side-by-Side Comparison
|
|
2-Way Match |
3-Way Match |
4-Way Match |
Invoice Approval Only |
|
Documents Compared |
PO + invoice |
PO + invoice + receiving report |
PO + invoice + receiving report + inspection record |
Invoice only |
|
What It Confirms |
You were billed what you approved |
The goods actually arrived |
The goods arrived and passed inspection |
Someone with authority approved it |
|
Where Those Documents Live |
Your ERP or DMS, plus the invoice |
Add the dock or the parts counter |
Add QA, the shop floor, or a third-party inspector |
An inbox |
|
Best Fit For |
Services, subscriptions, utilities, rent, professional fees |
Parts, inventory, raw materials, equipment |
Regulated or spec-sensitive goods |
Low-dollar spend under a defined threshold |
|
Where It's Standard |
Services-heavy spend in any industry, including financial services |
Dealerships, retail, distribution, heavy trucking |
Manufacturing, healthcare, construction, aerospace |
Small vendors and low-dollar spend everywhere |
|
Effort to Run by Hand |
Pull the PO, compare two documents |
Pull the PO, then track down whoever signed for the delivery |
All of the above, plus chase a sign-off that lives outside finance |
None |
|
Trade-Off |
Fastest to clear, blindest to what arrived |
Catches the most common leakage, depends on receiving discipline |
Highest assurance, easiest to turn into a rubber stamp |
No friction, no control |
|
Trade-Off |
Fastest to clear, blindest to what arrived |
Catches the most common leakage, depends on receiving discipline |
Highest assurance, easiest to turn into a rubber stamp |
No friction, no control |
Even when these controls exist, manual matching is a bottleneck. Teams chase paper trails, approvals stall in inboxes, and disconnected systems make it hard to verify anything in real time.
The delay is the cost. And it lands in three places that have nothing to do with AP.
Early Payment Discounts
Terms like 2/10 net 30 pay you 2% to settle 20 days early. That window is a calendar, not a queue. An invoice that sits in exception for nine days has burned half of it before anyone opens the file.
On $2M in annual parts and supplies spend, capturing that 2% in full is $40,000. Most teams capture a fraction of what's available and never see the gap, because a discount you didn't take doesn't show up on any report. Capturing them consistently comes down to how you pay, not just how fast you approve.
Month-End Close
You cannot accrue what you cannot confirm. Every invoice still in dispute at close is a liability someone has to estimate, defend, and true up the following month. That gets easier when the documentation behind every accrual is searchable rather than filed.
A few dozen open exceptions across four rooftops turns close into a negotiation rather than a process. The controller isn't closing the books. They’re adjudicating which numbers are solid enough to sign.
Cash Forecasting
Payables is one of the few near-term outflows finance can actually predict. That holds only if you know what's committed, what's received, and what's approved.
When those three answers live in three systems, your AP number is an estimate presented as a fact. Treasury plans against it anyway, because it's the only number available.
Your suppliers feel all of this too. Every invoice stuck in exception eventually generates a call, and answering it means someone reconstructing the same three documents the match would have assembled in the first place. The work doesn't disappear when the control gets skipped. It relocates to your inbox and your phone.
Capture Comes First
Automated matching starts before the match. Smart Capture combines AI-powered document capture with Human-in-the-Loop validation. Invoices, POs, and receiving slips read at intake, line item by line item, and land in one place instead of five. Then your rules run against them.
You no longer need to dig through files or cross-check spreadsheets. Instead, the system captures and matches line-item data in real time, flagging exceptions and routing them to the right person with full context.
Matching is one piece of AP automation. Because PO and receiving data sync from your ERP or DMS, the match runs against your actual records. onPhase connects to NetSuite, Dynamics 365, Sage, Acumatica, Business Central, and SAP, and to dealership platforms including CDK, Procede, and Excede.
What that matching looks like in action:
Teams that implement Smart Capture with 3-way matching and exception routing often see significant time savings, reducing invoice intake time by as much as 70%.
That’s where Smart Capture comes in. It combines AI-powered document capture with Human-in-the-Loop validation. Invoices, POs, and receiving slips are automatically matched based on your rules.
You no longer need to dig through files or cross-check spreadsheets. Instead, the system captures and matches line-item data in real time, flagging exceptions and routing them to the right person with full context.
Here’s what automated matching looks like in action:
Teams that implement Smart Capture with 3-way matching and exception routing often see significant time savings, reducing invoice intake time by as much as 70%.
Matching is a control, not just an efficiency measure. Automated, it's one of the few controls that runs on every transaction instead of on the invoices someone had time to check.
Here’s how matching strengthens your fraud defenses:
Every comparison, exception, approval, and override is logged against the documents that triggered it. When SOC 1 or audit season comes around, the control isn't something you describe. It's something you export.
When matching runs inside the workflow instead of alongside it:
Matching tells you an invoice is correct. It doesn't tell you how to pay it, or when paying it serves you best. A clean match on a paper check still means print, sign, stuff, mail, and wait, on the payment method most exposed to fraud.
onPhase brings invoices, purchase orders, receiving records, contracts, and the approvals that move them into a single platform, connected to the ERP or DMS your team already runs on. Matching is where most finance teams start. What they get is a system where AP, payments, and document management share the same data, so the record that proves an invoice is correct is the same record that tells you where your working capital is going. See how it works.
Invoice Matching FAQs
What is the difference between 2-way, 3-way, and 4-way matching?
2-way matching compares the invoice to the purchase order. 3-way matching adds the receiving report to confirm delivery. 4-way matching adds an inspection or acceptance record to confirm quality. Each level adds one more document and one more point of verification before payment.
Which level of matching should we use?
Match the level to what you're buying, not to the highest standard available. Services and subscriptions need 2-way. Anything physical needs 3-way. Goods that have to pass a spec, safety, or compliance check before use need 4-way. Applying one rule to all spend creates exceptions that can't resolve.
When should you use 2-way matching instead of 3-way?
Use 2-way matching when there's nothing physical to receive. Services, software subscriptions, utilities, and professional fees have no receiving report to compare against. Requiring a 3-way match on those invoices creates exceptions that will never resolve.
Do you have to match every invoice?
Most teams don't, and that's usually deliberate. Below a defined dollar threshold, many run approval-only, with no PO comparison at all. That's a reasonable policy as long as the threshold is set consciously and reviewed, rather than becoming the default because matching is too slow to sustain.
What is a matching tolerance?
A tolerance is the variance you'll accept before an invoice is flagged. Most teams set both a percentage and a dollar cap, for example 5% or $50, whichever is lower. Tolerances keep small freight or rounding differences from consuming your team's day.
What causes a matching exception?
The most common causes are partial shipments, receiving reports entered late or not at all, unit-of-measure mismatches between the PO and invoice, unapproved substitutions, and freight or tax lines that don't appear on the PO. Exceptions are usually a document availability problem rather than a vendor problem.
Can invoice matching be automated?
Yes. Automated matching captures line-item data from the invoice, compares it to the PO and receiving report, and clears anything inside tolerance without human review. Exceptions route to the right person with all supporting documents attached, which removes the back-and-forth that makes manual matching slow.
Does my ERP already handle invoice matching?
Most ERPs, including NetSuite, Dynamics 365, Sage, Acumatica, Business Central, and SAP, support matching for invoices already keyed into the system. The gap is upstream: getting invoice and receiving data in accurately, and resolving exceptions once they're flagged. That's the work most teams are still doing by hand.
Is invoice matching required by SOX or GAAP?
Neither standard names matching specifically. SOX Section 404 requires effective internal controls over financial reporting, and matching is one of the most common controls auditors expect to see in a purchase-to-pay cycle. What matters to an auditor is that the control exists, is applied consistently, and is evidenced.
Does matching prevent invoice fraud?
Matching blocks several common schemes, including inflated invoices, duplicate submissions, and invoices from vendors with no corresponding purchase order. It isn't a complete defense on its own, and works best alongside vendor validation and segregation of duties.