Three Way Matching Process for Accounts Payable

Three way matching is an accounts payable control that compares three records before a supplier invoice is approved: the purchase order, the receiving document, and the supplier invoice. The goal is simple. Finance should pay for what was authorized, delivered, and billed accurately.

For small teams, matching may feel like extra administration. For companies managing many vendors, contractors, locations, projects, or purchase categories, it becomes a practical payment safeguard. It reduces overpayments, duplicate payments, quantity disputes, unauthorized purchases, and avoidable vendor confusion.

What’s in this article?

• What three way matching means in accounts payable
• How the process works from PO to payment approval
• When to use two-way, three-way, or exception-based matching
• Common failure points that slow finance teams down
• How Workhint fits into payment and approval workflows

Why three way matching matters

The three way matching process matters because payment risk usually appears before the invoice reaches AP. A team may order one quantity, receive another, and get billed for a third. A vendor may bill at the wrong price. A shipment may be partial. A project milestone may not be accepted yet. Without a matching process, AP has to decide whether to pay based on incomplete evidence.

The Washington State Auditor’s Accounts Payable Guide describes a three-way match as comparing quantity and price across the purchase order, receiving document, and invoice, calling it a standard industry best practice. UC Davis Finance and Business also emphasizes AP controls such as separating the people who approve purchases, receive materials, and reconcile records in its accounts payable internal control practices.

Those controls are not just audit theater. They help finance prove that the business had an obligation to pay, that the vendor delivered what was expected, and that the invoice amount is supportable before cash leaves the company.

The three way matching process

A useful matching process follows a clear operating path. The purchase order confirms what the company agreed to buy. The receiving document confirms what arrived or what service was accepted. The invoice asks for payment. AP compares the three before approving payment.

1. Create the purchase order: The business documents the vendor, item or service, quantity, unit price, total amount, currency, delivery terms, budget owner, and approval record.
2. Record receipt or acceptance: The receiving team, project owner, or service owner confirms what was delivered, when it was delivered, and whether it met the agreed requirement.
3. Receive the invoice: AP captures the supplier invoice number, date, due date, tax, total, remit-to details, and line items.
4. Compare the records: AP checks vendor name, PO number, item or service description, quantity, unit price, tax, freight, currency, and payment terms.
5. Route exceptions: Differences outside tolerance go to the right owner before payment approval.
6. Approve payment: Once matched or resolved, the invoice moves into the payment run with a clean audit trail.

NetSuite defines three-way matching as verifying a supplier invoice against the purchase order and order receipt before payment, while Tipalti describes it as comparing the PO, invoice, and goods receipt to make sure they match before invoice approval. The wording varies, but the control logic is consistent: approval should depend on matched evidence, not just an invoice in the inbox.

A practical three way matching workflow

The best workflow is risk-based. Requiring full manual matching for every invoice can delay payments and frustrate vendors. Skipping matching for high-risk spend can create losses. Finance teams should define when matching is required, what tolerances are acceptable, and who resolves each exception.

A simple tolerance policy helps. For example, finance may auto-clear small freight differences, route quantity differences to receiving, send price differences to procurement, and require controller review for vendor bank changes. The point is to standardize judgment so AP does not negotiate every mismatch from scratch.

What to compare before payment

At minimum, compare the vendor legal name, PO number, invoice number, item or service description, quantity, unit price, total amount, taxes, currency, delivery date, payment terms, and receiving confirmation. For service businesses, replace the goods receipt with service acceptance, milestone approval, timesheet approval, or deliverable acceptance.

Finance should also decide whether matching happens at the header level or line level. Header-level matching compares totals. Line-level matching compares each item, unit price, quantity, and tax treatment. Line-level controls take more setup, but they are often necessary for manufacturers, logistics teams, healthcare suppliers, construction projects, marketplaces, and companies with high invoice volume.

Common mistakes

• Matching after approval: If the invoice is already approved, exception handling becomes cleanup instead of control.
• No receiving owner: AP cannot confirm delivery alone. Someone close to the work must own receipt or service acceptance.
• No tolerance rules: Tiny variances clog the process when finance has not defined acceptable differences.
• Weak vendor records: Matching fails when vendor names, remit-to accounts, tax details, or payment terms are inconsistent.
• Chat-based exceptions: Decisions made in messages are hard to audit unless they are attached to the invoice record.

Where Workhint fits

Workhint helps finance and operations teams turn three way matching from a manual AP checklist into a live workflow. A company can route purchase requests, vendor onboarding, receipt confirmation, contractor acceptance, invoice review, exception handling, and payment readiness through one operational system.

That is especially useful when invoices depend on work happening outside finance: contractors completing milestones, field teams confirming delivery, managers approving services, procurement checking price variances, or finance validating vendor records. Workhint is not the accounting ledger. It helps coordinate the roles, approvals, documents, reminders, and audit trail around the payment workflow before the final payment is released.

FAQ

What is three way matching in accounts payable?

Three way matching is the process of comparing a supplier invoice against the purchase order and receiving record before approving payment.

What are the three documents in a three way match?

The three documents are the purchase order, the goods receipt or service acceptance record, and the supplier invoice.

When is two-way matching enough?

Two-way matching may be enough for low-risk services, software renewals, or approved purchases where there is no separate receiving document. Finance should still document who accepted the service or renewal.

Who should resolve matching exceptions?

AP should route exceptions based on the issue. Quantity differences usually go to receiving, price differences to procurement, service acceptance to the project owner, and bank or vendor record issues to finance control owners.

Conclusion

Three way matching works when it is designed as an operating workflow, not just an AP task. Define the documents, owners, tolerances, exception routes, and payment-readiness rules before invoices arrive. Then finance can protect cash, pay vendors with confidence, and spend less time reconstructing what happened after the fact.