Three-way matching: how to automate it in a small finance team

Did we get what we're billed for? Three-way matching is the accounts payable check that answers it before an invoice is paid, by comparing the invoice with its purchase order and goods received note. An AI layer checks every line, and only mismatches reach a person. At 1,000 invoices a month, our illustrative example releases about 25 hours a month of matching time.

Three-way matching at a glance

Three documents per line. Here's what a 3-way match system takes over in accounts payable (AP), and what stays with a person.

What three-way matching checks, line by line

Three documents, three questions. The purchase order (PO) is what you agreed to buy. The goods received note (GRN) is what actually arrived. The invoice is what you're being asked to pay, and the match compares all three on supplier, item, quantity, unit price and VAT.

A two-way match stops at the invoice and the PO. Adding the GRN is what stops you paying for goods that never turned up, which is why it matters most for physical stock. The median organisation uses it sparingly: APQC puts the median at 28.0% of invoice line items approved through a three-way check. We'd write the policy down plainly. Three-way for stock and materials. Two-way for services and subscriptions, with a sign-off standing in for the receipt.

Match lines, not totals. A correct invoice total can hide a short delivery on one line offset by a price rise on another, and only a line-level check sees both. Even line by line, the median organisation in APQC's data gets 75.0% of invoice line items through on the first pass, so the rest need someone's attention.

Reading the invoice in the first place is automated invoice processing; matching starts once the lines are captured.

The matching rules an SME needs

Purchase order matching breaks at the edges: part deliveries, services, freight, the invoice that arrives with no PO number. Write those rules down before anything is automated. The table shows the defaults we'd start with. They're starting points to adjust, not benchmarks.

Nobody publishes a standard tolerance. Tipalti's UK guide illustrates one as within 2% of the PO amount or variances under £100, and that's a vendor's example rather than a norm. Your number depends on your margins and on how often your suppliers' prices move. Set it per supplier or category, never globally. Then look at it every quarter, next to the exception log.

Xero users have a newer option. Xero now lets you part-receive a purchase order and bill only the goods that arrived, and Xero says the feature was released to all Xero users in June 2026. There's still no separate goods received note in Xero, so the receipt has to come from a stock app, a captured delivery note or a "work done" confirmation. Sage 200 records goods received notes and part receipts as standard.

Designing the exception queue

Once clean invoices match themselves, the failures are where a person's time goes, so we design that queue before the clean path. Missing POs, over-billed quantities, prices outside tolerance, overdue GRNs and duplicates all land here, and each item shows:

• the invoice line, the PO line and the GRN line side by side;
• the difference, and the rule it broke;
• a suggested action;
• a drafted supplier email, where the supplier is at fault.

Order matters. Work the queue by due date, oldest first, then by value, and push anything close to its payment date to the top. Each exception type has a named owner (buyer, receiver, budget holder or AP), and an item nobody has touched gets a chaser after 2 working days.

How big will the queue be? Ardent Partners puts the exception rate at 11.1% for best-in-class teams and 20.9% for the rest. Best-in-class teams also tie far more of their invoices to a purchase order: 84.0% for best-in-class teams and 47.3% for the rest. As with any workflow, design the exception queue first, then the happy path.

Matching time and cost at 1,000 invoices a month

Take a business receiving 1,000 supplier invoices a month and count the matching step only; capture, approval and payment are costed on their own pages. This is an illustrative example, not a client result. Time is priced at the median UK full-time hourly pay plus employer National Insurance and pension.

Today's figure works out at about 4.7 minutes an invoice. That's below the about 8.7 minutes of AP staff time per invoice implied by APQC's median for the whole AP process, as you'd expect, since matching is one step of several.

The example is deliberately conservative. A person still spends the full 12 minutes on every exception, so the whole saving comes from clean invoices. If the system lays out the evidence for each exception, the saving grows, and we haven't counted that. Pay cuts the other way: whoever does the matching is likely paid below the median, so the value row is an upper estimate. Released time isn't a cash saving unless someone puts it to use.

Run the same hours through our UAE rate of about AED 57 an hour and they're worth about AED 1,453 a month. That rate is an assumption, as the UAE publishes no pay data by occupation: a package of AED 8,000 a month, gratuity at 21 days' basic pay for each of the first five years, and the visa and hours assumptions set out on our UAE e-invoicing page. An Emirati hire's floor is higher: the private-sector minimum wage for Emiratis is AED 6,000 a month.

Matching and AP benchmarks

Read these as large-company numbers. Ardent surveyed 204 AP and finance leaders, 54% of them at companies with revenue above $1 billion, in a report sponsored by Bottomline. APQC's figures are cross-industry and undated. A small business without PO discipline should expect to start below the average.

How Orwell automates the match

A match is only as good as the PO and the GRN behind it, so we start upstream. This work sits in our business automation service and runs in six stages.

1. Map it. Before building anything, we map the process end to end, purchase order through payment: who raises POs, how deliveries get booked in, who signs off services.
2. Fix the inputs. Purchase order automation is the upstream half of the job. That means a PO number on every order email, a one-tap "received" confirmation for the site or warehouse, and a "work done" click for services.
3. Shadow mode. The system runs in shadow mode for a few weeks, matching in parallel, while we compare its decisions with your team's.
4. Approval gate. Anything over tolerance stops at an approval gate and waits for a person.
5. Go-live. Supplier groups switch over one at a time, highest volume first. We measure cost per invoice before and after.
6. Monitoring. A weekly batch of auto-matched invoices is sampled by a person, and tolerances are reviewed against the exception log.

Matching hands over at both ends. Once an invoice matches, approval and payment carry on in accounts payable automation. An invoice that never reached you can't fail a match; it turns up in supplier statement reconciliation instead. The rest of our finance automation guides sit on the Insights hub.

What automated matching won't do

• It won't fix missing purchase orders. If a large share of your invoices arrive without one, purchasing discipline comes before any software.
• It won't invent a receipt. If nobody records what arrived, the system can only run a two-way match, and a two-way match can't catch a short delivery.
• It won't settle a disputed price or negotiate a credit. It drafts the query. A person sends it.
• It won't pay anything. A match releases an invoice for approval, and payment stays with your AP process and a person.
• It won't catch a buying mistake. If you raised a PO for too much and the supplier delivers and bills exactly that, the documents agree. That's a purchasing control, not a matching one.
• It won't save you from loose tolerances. Set them too wide and small overcharges pass every time.

UK and UAE rules for matched invoices

Common questions

Tell us how an invoice gets matched today: who raises purchase orders, how deliveries are booked in, what happens when the numbers disagree, and roughly how many supplier invoices arrive each month. Start with an informal scoping chat; a price range for automating the match follows once we've seen your rules. Purchasing rules, volumes and ledgers vary too much between businesses for a fixed price to mean anything. Pick "Business automation" on the form.