3-way PO matching is the process of cross-referencing three documents before approving a vendor payment - a purchase order, goods receipt, and supplier invoice.
Here’s how they work:
The purchase order (PO) — the document your company issues to the vendor specifying what you're ordering and at what price.
The goods receipt note (GRN) — confirmation that what was ordered has actually been received. Sometimes called a goods received note or delivery receipt, it's the internal record that your team signs off when goods or services land.
The supplier invoice — the bill from the vendor requesting payment.
When companies use 3-way matching in their finance processes, all three need to line up before a payment is released. If any of them conflict — e.g. wrong quantities, mismatched prices, or a missing delivery confirmation — the invoice is usually flagged for review before money is released to pay the invoice.
Why does 3-way matching exist?
Without 3-way matching, your AP team is essentially taking vendors at their word. A supplier invoices you for 100 units. Did 100 units arrive? Were they the right units? Was the price what you agreed? Without a structured matching process, answering any of those questions means someone chasing emails, digging through delivery notes, and making judgement calls.
3-way matching turns that reactive scramble into structured control. It means every payment is tied to documented evidence — something was ordered, something was received, and the bill matches both.
For companies processing significant invoice volumes, it's also a meaningful fraud deterrent. Duplicate invoices, inflated quantities, and fictitious vendor schemes are far harder to execute when every payment requires a matching PO and GRN.
A concrete example
Say your procurement team raises a PO to a supplier for 100 units at £10 each — a total of £1,000.
The delivery arrives. Your warehouse team counts 95 units and records that on the GRN.
The supplier sends an invoice for £1,050.
At this point, the match fails — twice. The GRN shows 95 units, not 100. The invoice value is £50 higher than the agreed unit price would suggest even for the full order.
Before any payment is approved, your AP team needs to understand why.
Was it a pricing error? A delivery shortfall? A miscommunication on specification? Without the 3-way match to surface the discrepancy, €1,050 might simply get approved and paid. With it, the exception is caught automatically, investigated, and resolved before money leaves the business.
Where 3-way matching can go wrong
Knowing what 3-way matching is in theory and executing it consistently in practice are very different things. Most AP problems don't come from misunderstanding the process, but from process gaps in how it actually runs.
1. POs aren't being raised
In many businesses, purchasing happens informally. A team member calls a supplier, gets what they need, and the invoice arrives weeks later — but no PO was ever created. When there's nothing to match against, the matching process either breaks down or gets skipped entirely. The result is invoices approved on trust rather than evidence.
2. GRNs are inaccurate or missing
The goods receipt note is only useful if it's completed properly and on time. In practice, GRNs are often filled in retrospectively, estimated rather than counted, or simply not raised for service-based purchases where there's no physical delivery. When the GRN data can't be relied upon, the three-way match becomes a two-way match at best.
3. Manual processes get skipped under pressure
End-of-month pressure, staff absence, high invoice volumes — any of these can push AP teams into approving payments without completing the full matching process. When matching is a manual, multi-step task, the shortcut is always available.
4. Tolerances aren't defined
Not every mismatch is a problem. A minor rounding difference or a quantity variance of 1% on a large order doesn't always warrant a full hold on payment. But if no one has defined what's acceptable, every minor discrepancy becomes a manual decision — and the team either over-flags (creating bottlenecks) or under-flags (missing real issues).
2-way vs. 3-way matching: when to use each
2-way matching is a slightly simpler process, that compares just the PO and the invoice — it verifies that what was billed matches what was ordered, but doesn't confirm delivery.
It's faster and sufficient in many situations: service contracts with no physical delivery, recurring payments on fixed-term agreements, or low-value purchases below a set threshold.
3-way matching is appropriate when physical goods are involved, when supplier relationships are newer, or when the value of the transaction justifies the additional check. As a rule of thumb: the higher the value and the more variable the delivery, the stronger the case for 3-way.
Some finance teams also run 4-way matching, adding an inspection or quality report as a fourth document. This is most common in manufacturing, pharmaceuticals, or any sector where goods need to meet a defined specification before acceptance.
How to set up 3-way matching properly
Getting 3-way matching right is less about the matching itself and more about the processes that feed into it.
Make PO creation mandatory. No PO, no payment. That rule needs to apply across the business, not just in finance. If purchasing happens without a PO, the AP process starts on the back foot.
Define GRN responsibilities clearly. Someone needs to own goods receipt confirmation — and it needs to happen promptly, with accurate counts. If your receiving process is informal, your matching data will be unreliable.
Set tolerance thresholds. Define what level of variance is acceptable for auto-approval versus manual review. This stops your AP team from being buried in minor discrepancies while keeping genuine exceptions visible.
Document your exception process. When a match fails, the investigation process needs to be clear: who reviews it, what evidence is required, what happens if the supplier disputes the finding. Without structure here, exceptions become the place where process breaks down.
Audit regularly. Matching processes drift over time. Periodic audits of your AP controls help surface where POs aren't being raised, where GRNs are being back-filled, or where tolerances are being applied inconsistently.
Why automation changes how invoices are verified
Manual 3-way matching is time-consuming at any volume — and genuinely difficult to maintain consistently when invoice numbers grow, team capacity fluctuates, or business complexity increases.
AP automation platforms handle the matching automatically, comparing PO, GRN, and invoice data the moment an invoice is received. It then flags discrepancies in real time, and routes exceptions to the right reviewer without manual triaging. What used to take hours of cross-referencing becomes a background process.
Perk's invoice automation handles matching automatically — PO, GRN, and invoice compared by our powerful AI in seconds. That means your AP team focuses on exceptions that need a decision, not the routine processing of invoices that already match. The result is faster cycle times, fewer errors, and a matching process that scales with your business rather than against it.
3-way PO matching isn't complicated in principle. What makes it hard is maintaining it consistently across real business conditions — informal purchasing, inaccurate receipts, time pressure, and volume.
Getting the process right means building the right discipline upstream, defining clear rules for exceptions, and removing the manual effort that makes shortcuts tempting.
Perk automates 3-way matching — so your AP team reviews exceptions, not every invoice.
:format(webp))
:format(webp))
:format(webp))
:format(webp))
:format(webp))