An invoice for $4,820 for six new laptops lands in accounts payable. The purchase order on file lists $4,500 for six laptops, but the receiving report shows only five arrived, which is why one employee is still asking when theirs will show up.
Someone has to figure out, before that invoice gets paid, whether the price difference is a shipping charge, an unapproved increase, or a mistake, and whether the company is about to pay for a laptop it never received.
That question is exactly what 3-way matching in accounts payable is built to answer. It compares three critical documents, the purchase order, the receiving report, and the vendor invoice, and holds payment until they agree. When they don't agree, the mismatch shows up before the money leaves the company, rather than after.
This guide, based on years of growth consulting, covers how 3-way matching works, where each document comes from, how it compares to 2-way and 4-way matching, what it costs to run by hand, and what changes when procurement and accounts payable move invoice verification from a manual process to automated systems.
What is 3-way matching in accounts payable?
3-way matching in accounts payable is the process of comparing three documents, the purchase order, the receiving report, and the vendor invoice, before an invoice is approved for payment. If the quantities, prices, and terms on all three line up, the invoice moves forward. If they don't, accounts payable will hold the invoice until someone resolves the discrepancy.
The verification process pulls in more than one team. Purchasing issues the order and agrees to the price. The receiving team confirms what actually showed up. Accounts payable checks the invoice against both records before releasing payment. The vendor is part of the loop too, since it fulfills the order and submits the invoice that starts the whole matching process.
None of the three documents checks itself. A purchase order shows intent. A receiving report shows what arrived. An invoice shows what a supplier says it's owed. It's the comparison across all three, not any one of them alone, that gives accounts payable a reliable answer for whether to pay.
The process applies to purchases that generate all three documents, which in practice means most physical goods and many services with a defined delivery or milestone. A purchase with no clear delivery event, a monthly software subscription, a retainer, or a utility bill usually doesn't have a receiving report to match against, so it typically runs through a simpler check instead. The next section covers where that line usually gets drawn.
The three documents in the 3-way matching process
Matching depends on three key documents being accurate and available exactly when accounts payable needs them, and it only works if the documents align: names, numbers, and terms have to correspond across all three. Here's what each one covers.
Purchase order (PO)
The purchase order is the buyer's side of the agreement. Once a purchase request is approved, purchasing issues a PO to the supplier that lists the items or services, quantities, agreed price, and delivery terms. The PO is what the other two documents get checked against, so an inaccurate PO undermines the whole process before the first shipment even arrives.
Receiving report
The receiving report, sometimes called a goods receipt note, order receipt, or packing slip, is created when the order arrives. Whoever receives the delivery, either someone from the warehouse team, a site manager, or an office administrator, confirms the quantity and condition of what arrived and records it against the original PO. This is the document a manual, template-based purchasing process tends to skip, which is part of why partial shipments and short deliveries go unnoticed until the invoice arrives.
Vendor invoice
The vendor invoice is the supplier's bill for what it delivered. Accounts payable compares it against both the PO and the receiving report: does the price match what was agreed, do the quantities match what was received, and do the payment terms match the contract? Only when all three agree, when matching documents confirm the same price, quantity, and terms, does the invoice move to payment.
How 2-way matching, 3-way matching, and 4-way matching compare
3-way matching isn't the only way to check an invoice before paying it. Two other approaches show up often enough to be worth knowing, especially when deciding how much matching a given purchase actually needs.
2-way matching, sometimes written as two-way matching, compares the purchase order against the invoice only. It confirms that the billed price and quantity match what was agreed, but it never checks whether the goods or services were actually delivered. That gap is fine for a low-risk purchase where delivery is easy to verify some other way, such as a recurring software subscription or a routine office supplies order. It's a real exposure for physical goods, where a supplier could bill for a shipment that never left the warehouse.
4-way matching adds a fourth document, an inspection or quality report, usually for a large purchase or one where specifications matter as much as quantity, such as manufacturing components or regulated medical supplies. It's more matching than most organizations need for routine purchasing, but it's worth knowing the term exists if your industry deals in high-value or safety-critical goods.
3-way matching sits in the middle, which is why it's the default for most accounts payable teams. It adds the one document, the receiving report, that 2-way matching is missing, without adding the inspection step 4-way matching requires. For most purchase orders, that's the right amount of verification: enough to confirm delivery actually happened, without turning every invoice into an audit or QA process.
Why 3-way matching matters for accounts payable and procurement teams
The value shows up long before anyone talks about ROI. A well-run accounts payable process catches problems while they're still cheap to fix, and 3-way matching is the check that makes that possible. Here's what it actually protects.
It's a safeguard against fraud and duplicate payments
Cross-checking three independent sources of information makes it much harder for fraudulent invoices or duplicate payments to slip through. A supplier can't get paid for goods that were never ordered, because there's no matching PO. It can't be paid twice for the same delivery because the receiving report exists only once. An invoice for more than what was agreed gets flagged before it enters the payment process, rather than becoming an argument after the fact.
It improves accuracy across purchasing and accounting
Every mismatch the process catches, such as an incorrect unit price, an inconsistent quantity, or a delivery that never arrived, prevents the payment errors that accounts payable would otherwise incur. Catching it before payment is far cheaper than unwinding it afterward, and it protects payment accuracy by keeping accurate financial records rather than requiring a correction weeks later during month-end close.
It protects supplier relationships
The process runs both directions. It protects the buyer from overpaying and the supplier from being underpaid or accused of billing errors that are actually someone else's mistake. Repeated billing disputes strain vendor relationships in ways a clean, predictable match never does, and a supplier who knows every invoice gets checked fairly and paid on time once it clears is more willing to extend better pricing or hold inventory for a good customer, which keeps vendor relationships healthy over the long run.
The pattern holds across industries, even when the purchases look nothing alike. A construction firm can catch a supplier billing for lumber that was never delivered to the site. A healthcare system can confirm a medical supply order arrived in full before releasing a six-figure payment. A school district's business office can hand an auditor the documents supporting every check it issued last year without having to reconstruct anything. Different purchases, same three documents doing the same job.
Common challenges in the 3-way matching process
No process runs perfectly the first hundred times. These are the situations that trip up even a well-designed 3-way matching workflow, from invoices that don't quite line up to the occasional duplicate invoices a busy AP inbox lets through.
Partial shipments and backorders
Orders rarely arrive as one clean shipment. Eight laptops become six now and two next week. A bulk material order ships in three batches over the course of a month. Accounts payable needs a rule for this before the first invoice shows up, not while reviewing it: pay proportionally as each shipment is confirmed, or hold the full invoice until the order is complete. Whichever rule an organization picks, writing it down and applying it consistently beats a different judgment call every time, made by whoever happens to be reviewing that invoice.
Resolving discrepancies and setting tolerance thresholds
Not every mismatch is a problem. Minor discrepancies, like a shipping charge that wasn't itemized on the PO, or a price that's a few cents off due to rounding, don't need the same scrutiny as a quantity that's short by half. Most accounts payable teams set a tolerance threshold, a small, defined dollar or percentage variance that's allowed to pass without manual review, and reserve exception handling for anything outside it. Without a threshold, every minor variance becomes a full investigation, which is usually how a matching process earns a reputation for delayed payments and slowed-down purchasing rather than protection.
For a closer look at why prices drift between what was ordered and what's billed, see our guide to purchase price variance. And, more broadly, for the handoff between the order and the bill, our guide to the purchase order-to-invoice process walks through each step.
What manual 3-way matching costs your accounts payable team
The cost of manual invoice processing rarely appears as a separate line item, which is part of why it's easy to underestimate and why human error creeps in unnoticed. It's spread across the minutes each person spends on manual data entry and chasing down a document, minutes nobody adds up until data-entry errors start showing up in the exception queue.
Industry benchmarking across the accounts payable cycle puts the exception rate for organizations still relying on manual matching and spreadsheets at 10% to 25% of transactions, well above the under-10% rate typical of top-performing, more automated processes.
A useful way to see what that means in dollars: multiply your annual invoice volume by your exception rate, then by what it costs, in staff time, to resolve one exception. An organization processing 15,000 invoices a year at a 15% exception rate and $75 per resolved exception is looking at roughly $168,750 a year in exception handling alone, before counting late payment penalties, lost early payment discounts, or the processing costs of audit prep that gets harder every quarter the backlog grows.
That number isn't a reason to panic. It's a reason to measure your own version. Ask whoever processes your invoices to tally, for two weeks, how many couldn't be approved without asking someone else a question. That count, against total invoice volume, is a more honest picture of what a matching process is actually costing than any industry average.
How to automate 3-way matching
Manual AP processes for 3-way matching mean someone pulling the PO from one file, the receiving report from another, and the invoice from a third, then comparing them line by line. It works, but it's time-consuming and doesn't scale past a certain point, because every added supplier, department, or location adds another place the process can lose a document.
Automating the process doesn't remove the judgment involved. It removes the searching. Automated accounts payable systems capture invoice data directly, often through optical character recognition (OCR), which reads a submitted invoice and converts it into a structured record rather than an image someone has to retype. That structured invoice can then be checked against the purchase order and receiving record automatically, with the system flagging only the invoices where something doesn't line up, such as a price difference, a short quantity, or a delivery that was never confirmed, for a person to review.
PwC's 2024 Global Digital Procurement Survey, which surveyed 1,000 procurement professionals across roughly 60 countries, found that 70% of organizations cited efficiency gains as a primary benefit of the digital procurement tools they'd implemented. That tracks with what shows up in day-to-day accounts payable work: the time saved isn't in the matching itself, since a system that compares three numbers is nearly instantaneous. It's in not having to go looking for the documents in the first place.
None of this replaces the accounts payable team. It changes what they spend their time on: fewer invoices reviewed simply because the process requires it, more attention on the ones that actually need a decision. The point isn’t just to save time on individual invoices. Multiplied across a year of exception handling, it’s a real way to save money too.
That shift matters more than it sounds. A team that spends most of its week hunting down purchase orders and confirming deliveries by phone has little time left for the parts of the job that actually need a person: judging whether a supplier's explanation for a shortage holds up, deciding when a tolerance threshold needs adjusting, or catching a pattern across several exceptions that no single invoice would reveal on its own.
Best practices for accurate 3-way matching
These are habits, not software features, and that's exactly why they matter even after the matching itself is automated. They're what keep matched invoices the norm rather than the exception, and keep the payable process moving instead of stalling in someone's queue.
Standardize the documents everyone works from
Matching only works when all documents use the same language: the PO, the receiving report, and the supplier invoice must use consistent terminology, units, and reference numbers. If purchasing calls it a PO number and receiving calls the same field an order number, someone has to translate every time. Agree on the fields and their names once, then make sure suppliers, receiving staff, and accounts payable all use them, since consistent terminology keeps accurate invoices moving instead of stalling in review.
Promote cross-functional communication
Purchasing, receiving, and the AP team each handle a different part of the purchase process. A short, regular check-in between them, even a monthly 20-minute review of recent exceptions, surfaces recurring problems, like a supplier who consistently ships short, faster than any single team would catch on its own.
Run routine audits, not just exception reviews
Reviewing the invoices that got flagged shows where AP processes are catching problems. Randomly auditing a sample of invoices that matched cleanly shows whether the process is missing anything. Both matter. A matching process that never flags exceptions isn't necessarily accurate. It might just have tolerance thresholds set too wide to catch anything.
Set tolerance thresholds before you need them
Decide in advance, with input from both finance teams and procurement teams, how much variance is acceptable before an invoice requires manual review, and put it in writing. Waiting until a $12 rounding difference sits in someone's queue for a week is how a matching process earns a reputation for slowing purchasing down.
Invest in ongoing training
The people running this process change. New hires in purchasing, receiving, and accounts payable all need to understand not just how to complete their part of the process, but also why the other two documents matter. A receiving clerk who understands that a sloppy receiving report becomes an accounts payable problem three weeks later is more likely to get it right the first time.
How Tradogram supports the 3-way matching process
Everything above describes what a good 3-way matching process needs: consistent documents, a receiving record that is actually created, and a way to route exceptions that require a human decision. Tradogram is built around that same sequence, from managing the purchase order through to the payment, as part of a connected procure-to-pay workflow.
Purchase requests and purchase orders live in one system, so the PO that receiving and accounts payable check against is the same one purchasing approved, not a version that was retyped somewhere along the way.
Receiving is recorded directly against the original purchase order, line by line, keeping goods receipt records visible as an open order rather than letting a partial shipment disappear until someone remembers to follow up. That's the receiving report the rest of the match depends on, created by the person who actually saw the delivery.
TradoScan, Tradogram's OCR tool, extracts invoice details and receipt data directly from incoming documents and converts them into a structured record, eliminating the need to retype them.
Intelligent matching then compares that invoice against the purchase order and receiving record, and anomaly detection surfaces duplicates and inconsistencies for accounts payable to review, rather than requiring someone to go looking for them. It's the same invoice-matching logic described earlier in this guide, built into the workflow instead of being run by hand.
Budget controls sit upstream of all of it. Requests and approved orders are checked against the relevant budget before a purchase order goes out, so a mismatch discovered during matching is a documentation gap to resolve, not the first time anyone learns the purchase happened.
Approval workflows sit upstream too. Requests route to the right approver based on rules an organization sets: amount, department, project, or supplier, so the purchase order that starts the whole matching process was reviewed by someone with the authority to approve it. That's one more document accounts payable can trust without having to chase down who signed off and why.
None of this removes the judgment calls; it only removes the hours spent tracking down the documents those judgment calls depend on.
How to switch from a manual matching process
3-way matching in accounts payable isn't complicated in concept. Three documents, compared before payment. What makes it hard is keeping all three accurate, available, and easy to compare as the number of suppliers, purchase orders, and invoices grows.
When you’re considering what automating it would change, the place to start is the same: know which of the three documents you can trust today and build from there.
