Three-way match for manufacturers: automating invoice matching

What three-way match is

Three documents should tell the same story before money leaves your account:

• The purchase order. What you agreed to buy, how many, and at what price.
• The receiving record. What actually came in the door. Your ERP may call it a receipt, item receipt or product receipt.
• The invoice. What the supplier says you owe.

If all three agree, you pay. If they don't, someone finds out why. Microsoft's Dynamics 365 invoice matching guide puts it simply: two-way matching compares the invoice price to the PO price, and three-way matching also compares the invoice quantity to the quantity on the product receipts. Older Oracle Payables documentation adds a fourth level: the quantity billed can't be more than the quantity accepted after inspection.

Why it matters now

A match does two jobs. It catches honest mistakes: the price that crept up, the short shipment, the invoice you already paid. And it makes fraud harder.

Business email compromise is the big one. The FBI's 2024 Internet Crime Report counted 21,442 business email compromise complaints with $2,770,151,146 in reported losses, about $2.77 billion. The FBI describes it as a scam aimed at businesses or people who work with suppliers or regularly pay by wire, using tricks or hacked email accounts to get money sent where it shouldn't go. That's down a little from 2023's $2.95 billion, but it's still billions of dollars a year.

Texas is near the top of that report. Texans reported $1,351,598,183 in losses across all types of internet crime in 2024, second only to California. That figure covers every scam type, not just email compromise. The FBI also notes these are complaints people chose to file, so the real numbers are likely different.

Fraud also comes from the inside. The ACFE's Occupational Fraud 2026: A Report to the Nations studied 2,402 cases. When the fraudster was unusually close with a vendor or customer, the median loss was $300,000. In the full report, billing schemes, such as fake or inflated invoices, showed up in 21% of cases with a $90,000 median loss, and lasted a median of 14 months before anyone caught them.

What a fraud case cost, by the warning sign

ACFE 2026, median loss per case. Behavioral red flags with the highest losses, plus billing schemes.

1. Pressure from within the organization$532,000
2. Past legal problems$400,000
3. Unusually close with a vendor or customer$300,000
4. Billing schemesFake or inflated invoices, 21% of cases$90,000

Source: ACFE, Occupational Fraud 2026: A Report to the Nations, 2,402 cases investigated Jan. 2024 to Sept. 2025. Cases reported by fraud examiners, not a random sample.

The ACFE also found that a lack of internal controls was the top weakness, behind about one-third of cases. A match on every invoice is one of the simplest controls a mid-size company can have.

Why it gets skipped

Most AP people know the rule. The problem is time. Matching by hand means pulling up the PO, finding the receiving record, and comparing each line of the invoice. Units don't line up (the PO says cases, the invoice says each). A partial shipment means two receipts for one PO line. A price changed by phone and nobody updated the PO.

So on a busy week the match turns into a glance at the total. That's where the double payment, the freight charge nobody agreed to, and the bank-change email slip through.

The money adds up. In APQC benchmark data, as reported by CFO.com, even top performers had about 0.8% of annual payments go out as duplicate or wrong payments, and bottom performers about 2%. For example, on $20 million a year in supplier spend, 1% is $200,000 you'd have to chase back.

Speed matters too. Ardent Partners' State of ePayables 2024, published on its sponsor's site, reports best-in-class AP teams spend $2.78 to process an invoice against $12.88 for others, and take 3.1 days instead of 17.4. The page doesn't give the sample size, so treat it as a rough guide.

The match itself is simple. Doing it by hand on every invoice is what nobody has time for.

What your ERP already does

Before buying anything, check what you own. Most mid-market ERPs can match invoices, though with limits.

• NetSuite. Oracle's 3 Way Match Vendor Bill Approval Workflow checks a vendor bill against its purchase order and item receipt, and routes bills with differences to a supervisor. Oracle notes it doesn't support partially received item receipts.
• Business Central. Microsoft's Payables Agent reads vendor invoice PDFs from a mailbox, suggests matching PO lines, and flags quantity, receipt, unit and price problems. Microsoft is clear that the agent doesn't post the invoice. A person does.
• Dynamics 365 Finance. Microsoft's matching policies let you set two-way or three-way match by item, by vendor, or by item and vendor, with price tolerances.
• Sage Intacct. Its 2026 Release 2 notes describe AI-driven, line-level matching across POs, receivers and vendor invoices, with tolerance thresholds.

On Sage 100, Epicor, JobBOSS or QuickBooks, ask your partner what's built in. Our guide to Sage 100 AP automation covers that system.

What automated matching looks like

Done well, the flow is short:

1. Read the invoice. Software pulls the vendor, PO number, lines, quantities, prices and freight from the PDF or email.
2. Find the PO and receipts. It looks them up in your ERP, including partial receipts.
3. Compare line by line. Item, quantity received vs. billed, price vs. PO price, within the tolerances you set.
4. Sort. Clean invoices go to a list for quick approval. Ones that don't agree go to your AP person with the reason spelled out: "billed 500, received 400" or "price $4.10, PO says $3.85."
5. A person approves. Nothing posts or pays without a human sign-off.

Two checks belong next to the match. First, duplicates: same vendor, same invoice number or same amount and date. Second, bank details: any change to a vendor's remit-to account gets a phone call to a number you already had, never one from the email. Microsoft builds the same idea into the Payables Agent: vendors it creates start blocked, because Microsoft says vendors and their bank accounts get approved by talking with the vendor and making callbacks.

Your AP person stops being a typist and becomes the one who handles the exceptions. That's a better use of the person who knows your suppliers.

Where the other side has a point

Three-way match on everything isn't always right.

• Small purchases. Plenty of organizations use a dollar line. The University of Georgia, for example, uses two-way match for goods orders under $2,500 and three-way above that.
• Services. There's often no receiving record for a repair or a consultant. Rockefeller University uses two-way match when there's no receiving report, for services and repairs. A sign-off from the person who got the service can stand in.
• Tight tolerances create noise. If every 2-cent rounding difference becomes an exception, people learn to click past them. Microsoft's example uses a 5% unit price tolerance. Set yours on purpose.
• Bad receiving data breaks it. If the dock doesn't record receipts, or records them days late, the match flags everything. Fix receiving first, or the automation just moves the mess.

Microsoft's own example applies three-way match only to certain vendors with a history of delivery problems. That's a reasonable start: match where the risk is, then widen it.

How to start

1. Pull last month's invoices. Count them, and note how many had a PO and a receipt.
2. Time ten of them. Minutes to match each one by hand. Our guide on measuring office automation ROI shows how.
3. Set your rules. Which purchases get three-way, which get two-way, and what tolerances.
4. Check your ERP. Turn on what's built in, and see where it stops: partial receipts, unit conversions, invoices that arrive as PDFs in an inbox.
5. Automate the reading and the matching, not the approval. See human-in-the-loop automation for why.

How Peekgentic does it

We build the part around your ERP that reads supplier invoices from the inbox, finds the PO and receipts, matches line by line with your tolerances, and hands your AP person a short list of what doesn't agree, with the reason. Clean invoices go to a person for approval in bulk. Your team keeps working in the ERP it already uses. See our purchasing build for how it works.