Three-way match: what it is, where it breaks and how to automate it.

Accounts payable has one job every other finance job depends on: pay the right vendor the right amount for what actually arrived. The three-way match is the check that does it. It is also where much of the manual work in AP collects, because every invoice that fails the check waits for a person.

This article covers how the match works, where it breaks, how to count the hours your exceptions take with your own numbers, and what changes when a system does the matching. It supports the topic on invoice processing automation, which walks through capture, approvals and posting.

What a three-way match checks.

The match runs line by line. For each line on the invoice, the clerk or the system finds the same item on the purchase order and on the receiving record, then compares three things: the item, the quantity and the unit price. Freight, tax and fees sit on lines of their own, and the invoice total is checked last.

An invoice can match on four lines and fail on the fifth. Decide in advance whether one failing line holds the whole invoice or only that line. Holding the whole invoice is simpler to reconcile. Paying the lines that match keeps the vendor paid on time for everything that was right.

The three documents, and what each one proves.

Each document comes from a different part of the company, and that is the point of the check. No single person creates the purchase, confirms it arrived and approves the payment, so a mistake in one document shows up against the other two.

Two-way, three-way and four-way match.

The number names how many documents are compared. Each one adds a question the check can answer.

• Two-way match. The purchase order and the invoice. It fits purchases with nothing physical to receive: services, subscriptions, utilities, rent. It proves the price and the quantity agree with the order. It cannot prove that anything arrived.
• Three-way match. Adds the receiving record. It is the standard check for goods bought on a purchase order, because it pays only for what came through the door.
• Four-way match. Adds an inspection record, so goods are paid for only after they arrive and pass inspection. It fits purchases where quality decides whether the goods can be used: raw materials, parts that go into your product, regulated items.

You can run all three at once, one per category of spend. Write the rule down per category, so nobody has to decide invoice by invoice which check applies.

Tolerances, and where exceptions come from.

A tolerance is how far the invoice can differ from the purchase order and the receipt and still pass. It is set as a percentage, an amount per line, or both, and every company sets its own. Tight tolerances on expensive or regulated items protect cash. Looser tolerances on low-value supplies keep small differences from turning into work. Review them whenever your exception rate moves.

When an invoice fails, the reason is usually one of these:

• Price variance. The unit price on the invoice is above the PO price by more than your tolerance: a price increase nobody put on the PO, the wrong contract price, a negotiated rate the vendor did not apply.
• Quantity variance. The invoice bills more than was ordered, or more than was received.
• Partial and late receipts. The vendor ships in two deliveries and bills once, or bills before anyone records the receipt.
• No purchase order. The invoice arrives with no PO number, or the PO was raised after the goods arrived.
• Freight, tax and fees. Charges that were never on the PO, so there is nothing to match them against.
• Duplicates. The same invoice sent twice, by email and by post, or sent again with a new number. A duplicate can agree with the PO and the receipt line for line, so the match alone will not catch it. A separate duplicate check does, and its catches belong in the same log.

Where the manual version breaks.

On paper the process is simple. In a busy AP team, the same few problems turn a clean check into a queue.

• Retyped PDFs. Invoices arrive as email attachments and get keyed into the ERP by hand. A typo in a quantity or a price creates an exception that was never real, and someone has to find it.
• Receipts recorded late. The warehouse receives on Tuesday and records it on Friday. The invoice lands on Wednesday, fails for lack of a receipt, and AP starts chasing the dock.
• Exceptions that live in inboxes. A failed match becomes a forwarded email with no owner and no deadline. Nobody can say how many are open or how old the oldest one is.
• Prices changed by phone. A buyer agrees a new price with the vendor on a call and never updates the PO. Every invoice at the new price fails until someone does.
• A messy vendor master. Two records for the same vendor let a duplicate invoice through, and an old remit-to address sends a payment to the wrong place.

The cost shows up first as hours: someone has to find out what went wrong, ask the right person and wait for an answer. Late fees and lapsed early-pay terms follow. The hours are the easiest part to count, so start there.

Count the hours your exceptions take.

You can put a number on this today with three inputs from your own records: how many invoices you process in a month, the share that fail the match, and the minutes of someone’s time it takes to clear one: finding the cause, asking the right person and fixing the record. The days an exception sits waiting are a separate measure; they cost late fees and lapsed terms, and they are not labor.

If you do not know the share or the minutes, log two weeks of exceptions before you guess. The log has a row for each exception: the date, the vendor, the reason, the minutes of handling and who cleared it. Two weeks shows you which reason takes the most hours.

The tool gives you hours. To turn them into dollars, use the loaded cost of an hour in accounts payable, as the cost to process an invoice worksheet does: salary plus benefits, payroll taxes and a share of overhead. That article also adds the other costs an invoice carries: systems, errors, late fees and missed early-pay discounts.

What a system changes, step by step.

A system runs the same check a careful clerk runs. What changes is who does the reading and the comparing, and how fast an exception reaches the person who can clear it.

1. Capture.

   Invoices are read as they land in the AP inbox or a vendor portal: the vendor, the PO number, every line, freight, tax and the total. Nobody retypes them.

2. Match.

   Each line is compared with the purchase order and the receiving record within your tolerances. The invoice is also checked against invoices already paid, so a duplicate stops before it is paid twice.

3. Route.

   Each exception goes to the person who owns its reason, with the evidence attached: a price variance to the buyer who placed the order, a missing receipt to receiving, an invoice with no PO to whoever asked for the purchase.

4. Approve and post.

   Matched invoices post to the accounting system or ERP you already use, under your approval rules. Anything that moves money waits for the approver those rules name.

5. Report.

   You see the share of invoices that matched without a touch, the exceptions still open by reason and by age, and the hours they took.

In the StrikeArc PowerPlays Library, this is the work of P06 Cut the manual work from orders and invoices. Orders and invoices arrive by email and process themselves: read, extracted, checked against your data and posted. Only the exceptions wait for a person. Documents move on their own only where your rules allow, and where money moves, a named approver signs off. The play reports the share of documents processed without a touch.

1. P06Cut the manual work from orders and invoicesSave time

Check these before you automate.

A system matches what your records say. These five decide whether it clears most of your invoices on its own or sends most of them to a person:

• PO discipline. Are purchase orders raised before the order is placed, and what share of invoices arrive with a PO number on them?
• Receiving records. Is every delivery recorded in the system, on the day it arrives, by a named person?
• The vendor master. Is there one record per vendor, with current remit-to details, and no inactive vendors still set up to be paid?
• Approval rules. Are they written down: who approves what, up to what amount, and who covers when they are out?
• The accounting system or ERP. Which one, which version, and who can grant read access to purchase orders, receipts and bills?

Write the answers down before anyone builds anything. The Workflow Brief is a one-page template for exactly that: what starts the workflow, who owns it, the steps, the systems, the exceptions and today's numbers. To see the whole route on a made-up distributor, from the baseline to the first quarter, read the worked example on orders and invoices.

Questions owners ask.

Keep reading.