Casi d'uso

Three-way matching without an ERP

Ultimo controllo 7 September 2026 · Questa pagina è disponibile in inglese.

Three-way matching without an ERP works because the three documents already sit in your mailbox: the purchase order in Sent, the order confirmation and the invoice in Inbox. Forward them, with the supplier's price list, to Price Double Check and the match comes back by email as a table, plus one check no ERP makes: the price itself.

A three-way match in an ERP is a discipline before it is a feature. The buyer keys the purchase order into the system, books a goods receipt against it when the pallet arrives, and the invoice is matched to both inside the same database. Most companies with ten to fifty people do all three steps on paper and email and none of them in a system, so the control is unavailable to them at any price. This page sets out what the match needs, what it costs at each tier, what it never checks, and how the same comparison runs on forwarded documents.

What a three-way match is

Before a supplier invoice is paid, the buyer's system compares it with the buyer's own purchase order and the buyer's own goods receipt. Quantity, unit price, line totals and the PO number must agree within a tolerance, typically one to five percent or a fixed amount per line. A line outside tolerance blocks the invoice and puts it into a match-exception queue for a person to look at. Two-way matching drops the receipt and compares only PO and invoice; four-way matching adds an inspection or acceptance step.

The vocabulary is worth borrowing because it is precise. A match exception is a line that did not agree. An invoice price variance, in Oracle's definition, is the quantity invoiced multiplied by the difference between the invoice unit price and the purchase order unit price. A non-PO invoice is one that arrived with nothing to match against. Every one of these terms describes a comparison between two documents, and every comparison needs both in one place, structured, keyed by item code.

What the match needs before it can run

Every system that offers a three-way match presupposes the same three habits, and the licence is the smallest of the three costs.

1. The purchase order is keyed into the system, line by line, with item codes, quantities and unit prices, before it is sent. A PO written in Excel and emailed to the factory does not count until it is re-typed.
2. A goods receipt is booked against that PO when the delivery arrives, again line by line, by whoever is in the warehouse that morning.
3. The invoice is entered or captured into the same system and linked to the PO number, so that the three records can be compared at all.

Where one of the three is missing, the match does not run. IOFM's benchmark puts the share of invoices that reach accounts payable without a system PO at thirty to fifty percent, and ProcurementExpress claims that nearly half of mid-size companies run purchasing on Excel, Word and email. Both are vendor figures, not ours, but they describe the companies we talk to every week: the purchase order exists, the factory demanded it, and it lives in Sent.

What three-way matching costs at each tier

The table below is our reading of the market in September 2026 for a distributor or importer with ten to fifty people. Prices are the vendors' published figures where they are published; where a vendor sells by quote we say so.

Two figures from the table we checked on the vendors' own pages this week. Lightyear lists Essentials at 130 GBP per month and Standard at 179 GBP per month, and places three-way purchase order matching in the Standard plan. ApprovalMax lists bill-to-PO matching among its financial controls but publishes prices per accounting platform rather than on one page, so we do not quote a figure. In every row the same condition holds: the PO must be created inside that tool, or synced from an accounting system where it was created, before an invoice can be matched against it.

Why sending purchase orders is not a match

The objection we hear is that the company already sends a PO for every order, so the control must exist somewhere. It does not. The PO is a document the supplier required and the buyer produced, usually from a spreadsheet template with the item codes and last known prices. It goes out by email. The order confirmation comes back by email, sometimes with a changed price or a substituted code. The invoice comes by email as a PDF. Nobody re-types the three into one system, because the people who would do it are the same two people who receive the goods and pay the bills. The documents are complete; the comparison never happens, or happens by eye on the invoice with the highest total.

This is the position of most buyers we talk to. A Baltic distributor of a sports-nutrition manufacturer sent a PO for every order, received a confirmation for most, and paid eleven invoices over a season. When we compared the chain, 382 invoice lines, 327 matched the list exactly and 41 were real price differences. One line billed 17.75 percent over the list price ate 91 percent of the margin of that delivery. Every document needed for a three-way match was in the mailbox the whole time.

The check a three-way match never makes

Even where the ERP runs a perfect match, it verifies one thing: that the invoice agrees with the PO and the receipt. It never asks whether the PO price was right. The PO price is keyed by the buyer from a quote or a price list; a keying error, a stale price after an increase letter, or a supplier's own error that the buyer copied into the PO flows straight through and matches perfectly. Phacet, which sells matching automation, states the gap plainly: three-way matching verifies that the invoice price matches the purchase order price, and does not verify that either reflects what was negotiated.

In the enterprise this is a separate product category, contract compliance, sold by Coupa, Jaggaer and Sirion at enterprise prices. For a distributor it is the whole question. The supplier sent a price list with an effective date. The invoice should carry those prices. Whether the PO in between was typed correctly is a detail; the comparison that matters is invoice against price list, and no matching system makes it, because the price list is not one of its three documents.

Three-way matching without an ERP, on forwarded documents

Three-way matching without an ERP starts from the fact that the three documents, plus the fourth that the match ignores, are all emails. Forwarding them to one address is the whole setup.

• The purchase order, from Sent, gives the codes, quantities and prices you ordered at.
• The order confirmation or pro forma, from Inbox, gives what the supplier agreed to ship, and shows a price or quantity that changed before dispatch.
• The invoice, from Inbox, gives what you are being billed.
• The price list, from Inbox or from the supplier's last email with an attachment, gives the price that should have been on all three.

We join the four by item code within one supplier, never by description, because in the chain above 335 of 442 lines carried a description that did not match the price list wording while the code did. Before any line is compared, the line sums of each invoice must equal its printed total to the cent; a PDF that fails that gate is reported as unreadable rather than compared. Then the reply lists, per line, the code, the description, the quantity, the billed price, the expected price, the delta, and whether it is in your favour or against you. Codes that appear on the invoice but not on the PO, short or over deliveries by quantity, and lines that could not be matched are listed with their amounts. The detail of the PO side is on the page compare a purchase order with an invoice; the price-list side is described in how to check an invoice against a price list.

There is no goods receipt in this picture, and we do not pretend otherwise. We do not check what arrived on the pallet, and we do not check delivery notes. What we check is the commercial leg: what was ordered, what was confirmed, what was billed, and what the price list said, on the documents as the supplier and the buyer wrote them. The reply arrives within the hour of the forward when the price list is already on file; comparisons of one price list with the previous one, and of drift across invoices, come as a digest.

Where an ERP is the better answer

If your purchase orders, receipts and invoices already live in one system with matching turned on, keep it; it does the receipt leg that we do not. Even then the price-list leg is missing, and forwarding the invoice and the price list adds it without touching the ERP. If you run Xero or QuickBooks and want an approval workflow with a PO register, an add-on such as ApprovalMax or Lightyear is the right tool for the workflow; the price check against the supplier's list is the part they leave to you. A purchaser who wants to see what a match reveals across a season, not only per invoice, can read track supplier price changes over time.

Forward one invoice and the price list to your address, add the purchase order from Sent, and the three-way comparison comes back by email within the hour.