Somewhere in your AP inbox right now, there's an invoice for 500 units. Your purchase order says 450. Your receiving dock counted 480, and twenty of those arrived dented. Welcome to the daily reality of manufacturing accounts payable, where paying an invoice is rarely as simple as paying an invoice.

Three-way matching exists precisely for this mess. It's one of the oldest controls in finance, and in manufacturing, it's also one of the most abused; either skipped entirely when things get busy, or enforced so rigidly that vendors wait weeks while someone hunts down a packing slip. This post covers what it is, why manufacturers feel it more than anyone, and how to run it without turning your AP team into full-time detectives.

What is three-way matching?

Three-way matching is an accounts payable control that compares three documents before an invoice gets paid: the purchase order, the receiving report, and the vendor invoice. If the quantities, prices, and terms agree across all three, the invoice is approved for payment. If they don't, it's flagged as an exception and held for review.

The logic is simple. The purchase order proves you ordered it. The receiving report proves it actually showed up. The invoice proves the vendor's math matches yours. Payment only happens when all three stories align, which is how you avoid paying for goods that never arrived, quantities you never ordered, or prices that quietly crept up between quote and invoice.

How the three-way match process works

For teams targeting a clean, repeatable workflow, the process breaks down into five steps:

1. A purchase order is issued: Procurement creates a PO specifying items, quantities, agreed prices, and terms. This becomes the reference document for everything downstream.

2. Goods are received and recorded: The receiving team checks the delivery against the PO and logs what actually arrived, including shortages, overages, and damage. This becomes the receiving report.

3. Vendor invoice arrives: The supplier bills for what they believe they shipped, at the price they believe was agreed.

4. The three documents are compared: AP checks that quantities and prices line up across PO, receiving report, and invoice, usually within a set tolerance.

5. Match or exception: Clean matches get approved and scheduled for payment. Mismatches get routed to someone who can investigate, which is where most of the time actually goes.

That fifth step is the whole ballgame. Ardent Partners' AP Metrics That Matter in 2025 found the average invoice exception rate sits at 22%, while best-in-class teams hold it to 9%. Roughly one in five invoices at a typical company needs a human to stop and figure out what went wrong. In manufacturing, that ratio often runs worse, for reasons worth spelling out.

Why does manufacturing makes matching harder

Most industries buy things occasionally. Manufacturers buy things constantly, in volume, from long supplier lists, under conditions practically designed to create mismatches.

Partial shipments are normal, not exceptional

A single PO for 10,000 components might arrive across four deliveries over six weeks. Each delivery generates its own receiving record, and the vendor might invoice per shipment, per month, or per whim. One PO, four receipts, three invoices; the "three-way" match quickly becomes an eight-document reconciliation.

Prices move between order and delivery

Raw material surcharges, freight adjustments, and volume-tier pricing all mean the invoice price can legitimately differ from the PO price. Your match process has to distinguish a valid steel surcharge from a vendor error, and that judgment call lands on AP.

Receiving data lives on the shop floor

The people who know what actually arrived are at the dock, not in finance. If receiving records are on paper, in a spreadsheet, or entered days later, AP is matching against stale or missing data, and every gap becomes an exception.

Unit-of-measure mismatches are everywhere

The PO says 2 pallets, the receiving report says 96 cases, and the invoice says 2,304 units. All three might be identical quantities. Good luck explaining that to a rigid matching rule.

The cost of getting it wrong in either direction

Skip matching, and you're exposed to duplicate payments, phantom deliveries, and price creep; the exact leaks the control exists to plug. Over-enforce it manually, and you create a different problem: invoices stuck in review while payment terms tick away, vendors calling to ask where their money is, and early payment discounts expiring in someone's follow-up folder.

The processing gap between disciplined automation and manual heroics is stark. The same Ardent Partners research found best-in-class AP teams process an invoice in 3.1 days, against 17.4 days for everyone else. In manufacturing, those extra two weeks aren't abstract; they're the difference between a supplier who prioritizes your orders and one who quietly moves you down the queue when materials get scarce, a dynamic we dug into in how manufacturers improve working capital without delaying supplier payments.

Making the match work at manufacturing volume

The fix isn't more diligence; it's removing the manual steps that create errors in the first place.

Set tolerance thresholds so trivial variances don't become exceptions. A $3 freight difference on a $40,000 invoice shouldn't stop anything. Define acceptable variance by percentage or dollar amount, and let clean-enough matches flow through automatically. Reserve human attention for mismatches that actually mean something.

Capture invoice data at the source instead of rekeying it. This is where AI changes the equation. Forwardly's AI-powered AP inbox reads incoming vendor invoices, extracts the line items, and matches them to the right PO automatically, so the comparison step happens in seconds instead of sitting in a queue. Exceptions are flagged by Forwardly AI Agent and then routed to a human, but through approval workflows that send them to the right person by amount, vendor, or department, rather than whoever opens the inbox first.

And once an invoice clears the match, pay it on your terms. With payment speeds from standard ACH up to instant transfers, and automatic sync back to QuickBooks Online, Intuit Enterprise Suite, Sage Intacct, Oracle NetSuite, Xero, FreshBooks, Zoho Books, and Microsoft Dynamics, the invoice that matched cleanly this morning can be paid and reconciled by this afternoon.

Three-way matching was never the problem. Doing it by hand, at manufacturing volume, with documents scattered across three departments, that was the problem. See how Forwardly handles the busywork so your team can spend its judgment on the exceptions that deserve it.