Three Way Matching in Accounts Payable: The Complete Guide

Three-way matching means an invoice is only paid when three documents agree: the purchase order showing what you ordered, the receiving record showing what arrived, and the invoice showing what you are being billed.

It exists because each document alone can be wrong, and the combination catches the errors that matter.

What each document proves

• Purchase order: this was authorised, at this quantity, at this price
• Receiving record: this actually arrived, in this quantity, in acceptable condition
• Invoice: this is what the supplier is charging

Match all three and you have established that the charge was authorised, the goods were received, and the price is what was agreed. Any one missing leaves a gap someone can walk through.

What it catches

• Being billed for quantities never delivered
• Price increases applied without agreement
• Duplicate invoices for a single delivery
• Invoices from suppliers you never ordered from
• Partial deliveries billed as complete

Tolerances

Exact matching on every line is impractical. Most processes allow a small tolerance on price and quantity, above which the invoice goes to review. Set tolerances deliberately: too tight and everything becomes an exception nobody has time to clear, too loose and the control stops catching anything.

Two-way matching

Where there is no separate receiving step, matching the invoice to the purchase order alone is common. It confirms authorisation and price, and it does not confirm receipt. Reasonable for services and for goods where the person ordering also confirms delivery.

Applying the principle without purchase orders

Most small service businesses do not raise POs, and forcing them in creates paperwork nobody reads. The principle still applies, using whatever evidence you have.

• Match the invoice to an approved quote or signed contract, which serves the PO function
• Match it to evidence the work happened: a completion sign-off, a delivery note, a timesheet, a photograph
• Confirm the rate matches what was agreed

The test is the same: was this authorised, did we receive it, is the price right. The documents differ; the question does not.

Where it breaks down

Recurring services with no per-instance evidence, such as monthly retainers or subscriptions. For these, the control moves upstream: approve the contract, then review periodically that the service is still wanted and the rate has not changed. Suppliers raising prices quietly on auto-renewing services is a common and entirely preventable leak.

The three-way match workflow from order to payment

Three-way matching works best when the evidence is created during the normal purchasing process. The requester documents what the business intends to buy. An authorized person approves that commitment. Someone confirms what was actually received. Accounts payable then compares those records with the supplier invoice before scheduling payment. The sequence matters because reconstructing approval after an invoice arrives turns a control into a paperwork exercise.

A practical workflow has clear ownership at every handoff. The requester owns the business purpose and specifications. The approver owns the budget decision. The receiver owns confirmation of quantity and condition. Accounts payable owns the comparison, duplicate check, and exception record. The payment approver owns the final release. One person may hold more than one role in a small company, but the roles should still be visible.

A worked three-way matching example

Assume a business issues an approved purchase order for 40 units at an illustrative price of $125 each. The receiving record shows that 36 acceptable units arrived. The supplier invoice requests payment for all 40 units at $130 each. The invoice fails both the quantity and price tests. The authorized quantity is 40, the received quantity is 36, and the invoiced quantity is 40. The authorized price is $125, while the invoice uses $130.

The correct response is not to edit the purchase order until it agrees with the invoice. Accounts payable should place the invoice on hold and identify what happened. Perhaps four units are still in transit. Perhaps the supplier applied an unapproved increase. Perhaps the receiving record is incomplete. Payment can be released for the supported amount only after the business decides how partial deliveries are handled and the evidence agrees with that decision.

Line-level matching and invoice-level matching

Matching only the invoice total can hide offsetting errors. One line may be overbilled while another is underbilled, leaving the grand total unchanged. A line-level match compares the item, description, quantity, unit price, tax, freight, and other charges where those details matter. It is more work, but it identifies the reason for a difference and produces a cleaner supplier conversation.

Invoice-level matching can be reasonable for a simple recurring charge governed by a current contract. It is less suitable for mixed orders, partial deliveries, variable rates, or invoices containing several jobs or locations. The control should fit the purchasing risk. A low-value fixed subscription does not need the same review as a large equipment purchase, but both need evidence that the charge is authorized and still wanted.

Setting useful tolerances

A tolerance is a rule for deciding which small differences can pass automatically and which require review. Tolerances may address price, quantity, freight, tax, or rounding. They should be based on the economics of the purchase and the reliability of the process, not copied from a software default. A percentage-only rule can be misleading because a small percentage on a large purchase may still be material to the business.

Document who can approve an exception and what evidence is required. A buyer may be allowed to accept a minor price difference supported by a supplier notice. A quantity difference may require confirmation from the receiver. Repeated differences from the same vendor should trigger a contract or master-data review. A tolerance is a routing rule, not permission for suppliers to drift away from agreed terms.

How to manage matching exceptions

Every failed match should enter a visible exception queue with an owner, reason, age, and next action. Common reason codes include price variance, quantity variance, missing receipt, duplicate invoice, missing purchase order, tax difference, and unauthorized freight. Reason codes make the queue measurable and reveal whether the same operational problem is recurring.

Accounts payable should not resolve an exception by guessing which document is correct. The requester or buyer confirms commercial terms. The receiver corrects receipt evidence. The supplier corrects its invoice when the billing is wrong. Accounts payable records the resolution and keeps the supporting trail. That separation keeps the accounting team from silently making purchasing decisions.

Matching services, retainers, and subscriptions

For services, the approved statement of work or contract usually performs the purchase-order role. Evidence of receipt might be an approved timesheet, milestone sign-off, delivery of a report, or confirmation from the service owner. The invoice should agree with the contracted rate, billing period, reimbursable-expense terms, and any cap. A vague email saying that the work looks fine is weaker than a specific confirmation tied to the invoice period.

Retainers and subscriptions need a different rhythm. The initial agreement is reviewed before activation, invoices are compared with the current contract, and the business owner periodically confirms that the service is still used. Review seat counts, plan tiers, renewal dates, and price changes. A perfectly matched invoice can still be wasteful if the underlying subscription is no longer needed.

Controls for a small team

When headcount is limited, complete separation of duties may be impossible. The strongest practical response is to separate payment release from invoice preparation, use bank permissions that require approval, and provide the approver with the invoice, support, and exception history. The approver should review a payment register rather than approve a total without seeing the vendors and amounts behind it.

Protect vendor master changes as carefully as invoices. A valid invoice matched to a valid order can still be paid to a fraudulent bank account if vendor details were changed without verification. Require an independent callback using contact information already on file, record who verified the change, and prevent the same user from changing bank details and releasing the payment.

Software setup and audit trail

Configure the accounting or procurement system so purchase-order, receipt, invoice, exception, and approval records remain connected. Standard identifiers are essential. Suppliers should use the purchase-order number on the invoice, receiving records should reference the same order, and credit notes should reference the original invoice. Free-text descriptions alone make both matching and later review harder.

Automation should show why a document matched or failed. Keep the original invoice, extracted data, approval history, changes, and payment reference. Avoid workflows that overwrite a rejected invoice or remove the evidence after a correction. A reviewer should be able to move from the payment back through the invoice, receipt, order, and approval without assembling the story from email.

Metrics that reveal process quality

• Percentage of invoices matched without manual intervention
• Number and value of invoices on hold
• Average age of unresolved exceptions
• Duplicate invoices prevented before payment
• Price or quantity variances by supplier
• Invoices received without a valid order or approval
• Credits requested but not yet received

Metrics should lead to a process change. A high rate of missing receipts may mean receivers need a simpler confirmation method. Repeated price differences may mean vendor terms or master data are outdated. A growing exception age may mean ownership is unclear. The goal is not a perfect dashboard. It is fewer invoices that require investigation and stronger evidence for the payments that leave the bank.

An implementation checklist

• Define which purchases require an order, quote, or contract
• Name who can request, approve, receive, match, and release payment
• Decide what counts as acceptable evidence of receipt
• Set tolerances and approval authority for each exception type
• Create a duplicate-invoice check using vendor, invoice number, date, and amount
• Protect supplier bank-detail changes with independent verification
• Review open exceptions before every payment run
• Reconcile the accounts payable control account each month
• Review recurring services and subscriptions on a schedule
• Retain the complete approval and payment trail

Review the process through one payment

Select one completed payment and trace it backward. Confirm the bank release agrees with the payment register, the payment agrees with an approved invoice, and the invoice agrees with authorization and receipt evidence. Check who performed each step and whether any document changed after approval. This single walkthrough often reveals broken references, informal approvals, or system permissions that a policy review misses.

Repeat the walkthrough for one exception, one partial delivery, one recurring service, and one vendor whose bank details changed. The purpose is not to prove that selected transactions were perfect. It is to test whether the process produces enough evidence to identify and resolve differences before cash leaves the bank.

Questions for the process owner

• Can every payment be traced to a named approver?
• Can the receiver confirm only the quantity actually received?
• Does the system prevent the same invoice from being entered twice?
• Are tolerances documented and visible to reviewers?
• Is an exception owner notified without relying on email forwarding?
• Can vendor bank changes be identified on the payment register?
• Are unresolved credits and price disputes reviewed before another order?

Use the answers to create a short improvement list. Fix high-risk gaps first, particularly bank-detail verification, duplicate payment exposure, and approvals that happen after payment. Then simplify handoffs that create unnecessary exceptions. A good three-way match process should make the ordinary invoice quick and the unusual invoice visible.

Decide what success looks like

A successful match process pays supported invoices on time, holds unsupported amounts before payment, preserves supplier relationships, and creates evidence a reviewer can follow. Review the design when purchasing channels, systems, approvers, locations, or payment methods change. A control built for yesterday’s workflow can appear active while new transactions bypass it.

Document improvements with an owner and completion date. Recheck a sample after the change. The test is whether ordinary invoices move cleanly and exceptions remain visible until resolved.