Article
How Does Three-Way Invoice Matching Work, and Where Does It Fall Short?
Three-way invoice matching is a payment control that compares three documents before an invoice is approved: the purchase order, the receiving record (a packing slip or goods receipt), and the invoice itself. If the quantities, prices, and vendor details agree across all three, the invoice moves forward for payment. If they don't, it stops for review.
That's the whole mechanism. What matters more, especially for a services firm paying subcontractors on time-and-materials terms, is what this check catches and what it quietly lets through.
What is three-way invoice matching, exactly?
Three-way matching is the accounts payable (AP) step that checks an invoice against two other records instead of trusting it on its own. The three documents are:
- The purchase order (PO) - what was authorized: the vendor, the item or service, the quantity, and the agreed price.
- The receiving record - proof that the goods arrived or the service was delivered, usually a packing slip, goods-receipt note, or a signed timesheet for services work.
- The invoice - what the vendor is now asking to be paid.
If all three tell the same story, the invoice is approved. If the invoice bills for 40 hours and the PO only authorized 30, or the receiving record shows a delivery the invoice doesn't mention, the mismatch gets flagged before money moves. This is one rung up from a two-way match, which only compares the PO to the invoice and has no independent confirmation that the work or goods were actually delivered.
For a deeper look at where this sits on the full matching ladder, see what is invoice matching software, from 2-way to 4-way.
How does the match actually happen, step by step?
In a typical AP workflow, a three-way match runs like this:
- The PO is issued. Procurement or the requesting manager sets the authorized vendor, service, quantity, and unit price before work starts.
- The work is confirmed as delivered. For goods, this is a receiving report. For a services firm, it's more often a signed timesheet, a delivery confirmation email, or a project manager's sign-off that the milestone was met.
- The invoice arrives. The vendor bills for the work, referencing the PO number.
- The system or the AP clerk compares all three. Line by line: does the vendor match, does the quantity match, does the unit price match, does the total match?
- A match posts for payment. A mismatch routes to a person. Someone has to look at the discrepancy, contact the vendor, or adjust the PO before the invoice can move again.
That last step is where most of the manual hours in an AP department go. A skilled AP person isn't slow because the arithmetic is hard; they're slow because chasing down why an invoice doesn't match, and who has to approve the fix, takes real back-and-forth.
What happens when the numbers don't line up?
A mismatch doesn't mean fraud. Far more often it means a legitimate but unlogged change: a vendor added a rush fee, a project ran a few hours over, or someone forgot to update the PO after a scope conversation. The job of the match isn't to accuse anyone. It's to force a human decision at the one moment that decision is cheap: before the invoice is paid, not after.
Common causes of a failed match include a receiving record that was never entered, a PO that wasn't updated when the scope changed mid-project, a price on the invoice that doesn't match what procurement negotiated, or a vendor billing ahead of a milestone that hasn't actually been confirmed. For a closer look at these patterns and how to clear them without a nine-day email chain, see what causes invoice matching errors, and how to fix them.
How does three-way matching compare to the rest of the ladder?
| Match type | What it checks | What it misses |
|---|---|---|
| 2-way match | PO vs. invoice | No proof the work or goods were actually delivered |
| 3-way match | PO vs. receiving record vs. invoice | Whether the rate, scope, or terms in the underlying contract were honored |
| 4-way match | Adds an inspection or quality-acceptance step to the 3-way check | Same gap as 3-way: still stops at the PO, not the agreement |
| Agreement-level match | Checks the invoice against the contract, SOW, and rate card, not just the PO | Requires reading documents most AP tools never open |
This is the gap that matters most for a contract-governed services firm: a three-way match can pass an invoice that is internally consistent - the PO, the receipt, and the invoice all agree with each other - while still billing the wrong rate, exceeding the contracted scope, or drifting from terms nobody re-checked. Three-way matching alone doesn't read the master service agreement, the statement of work, or the rate card, so it has no way to catch a violation that lives in those documents rather than in the PO. For a walkthrough of catching that specific gap on a T&M invoice, see checking contractor hours against the SOW before you pay.
Does three-way matching catch fraud?
It catches some fraud signals as a side effect - a fabricated invoice with no matching PO, for instance, will never clear a three-way match. But it wasn't built as a fraud control, and it has real blind spots: a changed bank account, a payee that doesn't match the vendor on file, or an amount parked just under an approval threshold can all sail through a match that only checks quantities and prices. Fraud losses are rarely small once they're found. In the ACFE's 2024 study of occupational fraud, the typical organization lost about 5% of its annual revenue to fraud, and the median loss per case across 1,921 cases studied was $145,000. Smaller organizations were not spared: companies with fewer than 100 employees had a median loss of $141,000, the second-highest of any size category in the study - higher than mid-sized companies with 1,000 to 9,999 employees. A services firm with a lean AP team is exactly the kind of organization that study describes. For a real example of how a fabricated invoice slips past normal review, see what a $67,000 fake invoice scam should teach every AP team.
Is three-way matching worth automating at every invoice volume?
No, and it's worth saying plainly. Building or buying automation for three-way matching pays off when there's enough invoice volume to justify it. Below roughly 200 invoices a month, the math gets harder to defend: the software and setup cost can outweigh the hours it saves, and a careful person doing the match by hand may genuinely be the more efficient answer at that scale. Above that volume, the manual version of this check starts eating a full work-week a month in an AP person's time, and that's before counting the mismatches that get waved through because nobody had time to chase them properly.
The honest framing here is not "replace your AP person with software." A three-way match, however it runs, still needs a person to look at every exception and make the call - the goal of automating the mechanical part is to absorb that workload before the next hire becomes necessary, not to remove the person approving payment. Software should clear the routine matches instantly and hand a person only the ones that actually need judgment.
Frequently asked questions
What is three-way invoice matching?
Three-way invoice matching is an accounts payable control that compares the purchase order, the receiving record, and the invoice before payment is approved, so an invoice only clears when what was ordered, what was delivered, and what's being billed all agree.
What documents does a three-way match compare?
It compares the purchase order (the authorized vendor, quantity, and price), the receiving record (proof the goods or services were delivered, such as a packing slip or signed timesheet), and the invoice itself.
What happens when a three-way match fails?
The invoice stops moving toward payment and routes to a person for review. A failed match usually means a legitimate discrepancy, such as an unlogged scope change or a missing receiving record, rather than fraud, but it requires a human decision before the invoice can post.
Is three-way matching the same as PO matching?
No. PO matching, or two-way matching, only compares the purchase order to the invoice. Three-way matching adds the receiving record as independent confirmation that the goods or services were actually delivered before payment.
Does three-way matching catch invoice fraud?
It catches some fraud as a side effect, such as an invoice with no valid PO behind it, but it was not built as a fraud control. It generally can't detect a changed bank account, a payee mismatch, or an amount parked just under an approval threshold, since those signals sit outside what the match compares.
At what invoice volume does automating three-way matching pay off?
Automation's return weakens below roughly 200 invoices a month. Below that volume, a careful person doing the match by hand can be the more cost-effective choice; above it, the manual version of the check starts consuming a meaningful share of an AP person's work-week.