Three-way matching is the check that compares three documents before an invoice is paid: the purchase order, the goods receipt, and the supplier invoice. If the quantities, prices and line items agree across all three, the invoice is cleared for payment. If they do not, it becomes an exception and a person has to resolve it.
That is the definition. The more useful question is what happens to the ones that do not agree, because that is where the time goes.
What are the three documents in a three-way match?
Each one answers a different question, and the match only means something because they come from three different places.
- The purchase order. What we agreed to buy, at what price, in what quantity. Raised by whoever requested it, approved before anything was ordered.
- The goods receipt (or GRN). What actually arrived, and how much of it. Recorded by whoever took delivery, which is usually not the person who raised the PO and almost never the person who will pay the invoice.
- The supplier invoice. What we are being asked to pay for. Written by the supplier, in the supplier's format, arriving by whatever channel the supplier prefers.
A two-way match drops the goods receipt and compares the invoice to the PO alone. That is common for services, where there is nothing to receive. A four-way match adds an inspection or quality record, which matters where what arrived has to be checked as well as counted.
How do matching tolerances work?
Almost nothing matches to the cent. Tolerances are the rules that decide how much disagreement is acceptable before a human is involved, and they are usually set on four axes:
- Price variance, as a percentage or an absolute amount per line. A unit price two cents higher than the PO is not worth anyone's afternoon.
- Quantity variance, often asymmetric: over-delivery is treated differently from short delivery, because one is a credit note and the other is a missing shipment.
- Total variance, a ceiling on the whole invoice regardless of how the lines behave, so a hundred small in-tolerance differences cannot add up to a large one.
- Category and supplier overrides, because freight, utilities and spot-priced commodities do not behave like a contracted parts list.
The tolerance matrix is the part most teams never write down. It lives in a controller's head, gets applied slightly differently by whoever is covering, and cannot be audited afterwards because there is no record of what the rule was on the day the invoice cleared.
Why do so many invoices fail the match?
More than most people expect. On APQC's benchmark, across 4,438 organisations, the median organisation matches 75% of invoice line items first time. The other quarter comes back to a person.
The reasons are mundane and repetitive:
- The goods receipt was never entered, or was entered late, so the invoice arrives before the evidence it needs
- Partial deliveries against a single PO, invoiced separately, in a different order
- Freight, duties, surcharges or rebates on the invoice that were never on the PO
- Unit-of-measure mismatches: the PO is in cases, the invoice is in units
- The supplier changed a part number, or invoiced against the wrong PO entirely
- The invoice arrived as a scan, a photo, or a PDF whose line items do not survive extraction cleanly
Separately, APQC finds that at the median organisation half of all invoice line items are still keyed into the finance system by hand, across a sample of 2,044 organisations. That is not an error rate, and it should not be read as one. It is a measure of how much of this is still typing.
One more number, and it is worth keeping separate from the two above because it comes from a different sample and a different definition: APQC puts the median time to clear a single invoice exception at five working days, measured across 461 organisations from the moment the exception is detected to the moment it is resolved. That is elapsed time, not effort. Most of it is waiting.
What is actually slow about an exception?
Not the comparison. Comparing three numbers is instant, and has been for as long as there have been ERPs.
What is slow is everything around it. An exception opens, and now someone in AP has to work out which of the three documents is wrong, find the person who knows, and ask them. The receiving supervisor who never entered the GRN. The buyer who agreed a price change over the phone. The supplier's accounts team, who will answer when they answer. Then AP waits, chases, waits again, and clears the exception days later with an answer that took ninety seconds to give.
The decision was never the slow part. Getting to it was.
This is why exception rates and cost-per-invoice are so stubborn. Automating the extraction makes the invoice arrive as data faster. It does nothing about the missing goods receipt, because that answer does not exist in any document. Somebody has to be asked for it.
Is three-way matching a workflow or a decision?
It is usually built as routing, which is why it disappoints. A case arrives, it fails a check, it gets routed to a queue, and it sits there. Routing moves a case towards a person. It never gets the answer that was missing.
Treated as a decision, the same process looks different. There is an outcome to reach: pay, hold, query, or partially pay. There is evidence that has to be true before that outcome can be reached: a receipt exists, quantities reconcile within tolerance, the price matches the contracted rate, the supplier is the one on the PO. Each of those is a gate. A gate that is open is not a queue entry, it is a specific unanswered question with a specific person who can answer it.
Once the process is shaped that way, three things become possible that routing never allowed. The tolerance matrix becomes explicit and versioned, so the rule that cleared an invoice in March can be reproduced in September. The chase becomes automatic, because an open gate knows who it is waiting on. And the case is either decision ready or it is not, which is a far more useful state than "in the approvals queue".
Where does three-way matching sit in the wider AP process?
- Capture. The invoice arrives, by email, portal, EDI or post, and becomes structured data.
- Enrichment. The supplier is identified, the PO is located, the goods receipt is pulled.
- Matching. The three documents are compared line by line against the tolerance matrix.
- Exception handling. Whatever did not clear is chased with whoever can resolve it.
- Approval. Whatever needs a human decision gets one, on a case that is already complete.
- Posting and payment. The outcome is written back to the ERP.
Steps one to three are where most AP automation projects concentrate, and they are the steps that were already fastest. Step four is where the five days live.
How Floowed handles it
Three-way matching is one of the decisions in the library, and it runs the way every decision on Floowed runs. The invoice is read whatever it arrives on, including the scans and photographs that break line-item extraction elsewhere. The PO and the goods receipt are pulled from the systems that already hold them. The tolerance matrix is written as rules in the Decision Engine, owned by the finance team rather than by engineering, versioned, and applied identically to every invoice. What clears, clears. What does not becomes a named open gate against a named person, and gets chased until it closes or the case is handed to someone with everything already assembled.
Your ERP stays the system of record. We integrate in both directions, with 400+ integrations across the industries we serve, so the outcome posts back where it belongs and nothing migrates. Activation runs in days, not quarters, with no professional-services engagement attached.
Floowed returns the decision and the reasons behind it. It never moves money.
Common questions
What is the difference between two-way and three-way matching?
A two-way match compares the invoice to the purchase order only. A three-way match adds the goods receipt, so you are confirming that what you are being billed for actually arrived. Two-way is normal for services and subscriptions, where there is no delivery to record.
What is a four-way match?
A four-way match adds an inspection or quality-acceptance record to the three above. It is used where receiving something is not the same as accepting it, such as in manufacturing, construction and regulated supply chains.
What tolerance should we set?
There is no correct universal number, and any vendor who gives you one is guessing about your spend profile. Set it by looking at your own exception history: the tolerance that would have auto-cleared the differences nobody ever disputed, and held the ones that turned out to matter. Then write it down, version it, and apply it the same way every time. The value is in the consistency more than the threshold.
Does three-way matching prevent invoice fraud?
It catches a specific and important class of it: being invoiced for goods that never arrived, or arrived in smaller quantities than billed. It does not catch a fraudulent supplier record, a duplicated legitimate invoice, or an altered document that still reconciles internally. Those need supplier verification and document-tampering checks alongside the match, not instead of it.
Can three-way matching be fully automated?
The comparison, yes. The exceptions are the honest answer: a quarter of line items do not match first time, and clearing them means getting an answer that is not written down anywhere yet. What can be automated is the asking, the chasing, and the recording of what came back. What should stay with a person is the judgment call at the end, on a case that arrives complete instead of half-assembled.
See it on one of your own decisions
Book a demo and name the decision you want automated. We will come back with how it runs: what gets gathered, which gates stay open, who gets chased, and what the Decision Engine returns. To try it yourself first, start free.
Related reading: best invoice approval software, the cost of manual invoice approval, and how document approval breaks down.
Last updated 2026-08-26 by Kira.