Three-way match: definition and how it works in accounts payable

What it means

Three-way match compares three documents before an invoice is released for payment: the purchase order, which shows what was agreed; the receiving record, which shows what actually arrived; and the invoice, which shows what the supplier is charging. Payment clears only when item, quantity and price agree within the tolerances your company has set. If any of the three disagrees, the invoice waits.

Each document answers a different question. The purchase order answers what we ordered and at what price. The receiving record answers what we accepted into the building. The invoice answers what the supplier says we owe. Remove any one of the three and the control weakens: invoice against purchase order alone lets you pay for goods that never arrived, and invoice against receipt alone lets you pay a price nobody agreed.

Tolerances carry most of the judgment. An invoice tolerance is the permitted difference, whether a few cents on price or a small quantity variance on a bulk delivery, that does not need human attention. Tolerances differ by company, by supplier and by spend category, and there is no single correct setting. What matters is that they are written down and that the exceptions they produce are actually worked.

How it works in practice

On a clean match, all three documents line up line by line: same item, same quantity, same unit price, inside tolerance. The invoice posts and is scheduled under normal payment terms. Nothing for a person to do.

On an exception, the invoice does not post. It goes to an exception queue for the buyer to resolve on price or the receiver to resolve on quantity before payment. A PO price of $18.50 and an invoice price of $18.95 differ by 2.4%. With a 2% price tolerance the line is held for review instead of being paid. The clerk's job is not to decide who is right but to route the line to someone who can, and to keep it visible until they do.

Not every purchase can be matched three ways. Services and utilities often have no receiving record, because nothing arrives at a dock, so they are usually matched two-way against the purchase order or approved directly by the budget owner. A four-way match adds a further document, typically an inspection or quality sign-off, and is used where acceptance criteria matter. Non-PO invoices, where no order exists at all, sit outside the control and need a separate approval route.

One limit is worth stating plainly. Three-way match stops payment for goods never received and for prices above the purchase order. It does not by itself stop the same invoice being paid twice under a different invoice number, because a second invoice can carry its own matching documents or arrive as a non-PO item. Duplicate payment needs its own check.

Where it goes wrong

Receiving records that are never created. Goods arrive, the truck leaves, the packing slip goes in a drawer, and no receipt exists in the system. The invoice then fails matching not because the supplier is wrong but because the receiving step was skipped. This is the most common reason a valid invoice gets held, and the fix sits at the dock rather than in accounts payable.

Receipts booked at the wrong quantity or against the wrong order. Someone receives the full order when half arrived, or books a delivery against the wrong purchase order because the paperwork was unclear. The match then succeeds against a false record, which is worse than a visible exception. A quantity tolerance stretched to cover the gap hides the problem instead of surfacing it.

Tolerances set wide enough to pass almost everything. If the price tolerance swallows everyday variances, price drift goes through untouched and the control only catches the extreme case. Tolerances should be tight enough to catch real movement and reviewed when purchasing patterns change.

Exceptions that age in the queue. An invoice held for weeks gets paid in a rush at period end, or the supplier chases and someone releases it just to stop the noise, so the underlying mismatch is never resolved. An exception queue is a control only when someone owns it and the ageing is reported. A related failure is a price amended by a change order the buyer never recorded, so the purchase order the system matches against is out of date.

What to check

Check the queue, not just the ledger total. Count open exceptions, age them, and see which buyers and receivers they sit with. A queue that is steady in size but growing in age is a backlog, not a control.

Check whether receipts exist before invoices land. Compare open purchase orders with your goods received not invoiced balance. A receipt with no invoice is normal for a while; an invoice with no receipt means the match will fail or was overridden.

Check that overrides leave a trace. Any invoice released without a clean match should record who released it and why. If overrides cannot be listed, they cannot be reviewed.

Check the price side against the vendor record. Repeated small variances on one supplier, such as the 2.4% in the example above, are the pattern to look for rather than a single line. And run the duplicate check separately, because a clean three-way match will still pass an invoice paid twice under two different numbers.

Questions