All Posts

Procure Tech

How Three-Way Invoice Matching Works, and What It Misses

How Three-Way Invoice Matching Works, and What It Misses

TechShorts Newsroom

Editorial Team

Invoice matching decides whether a supplier invoice pays automatically or stops for a person to review. Oracle, SAP and Microsoft each document their own version in their ERP software. The configuration behind it sets how many invoices wait in an exception queue, and which errors get through anyway.

What matching compares

Matching checks documents that should agree. The purchase order records what the buyer agreed to pay. The receipt shows what arrived, and the invoice is the supplier's request for payment. In Oracle Payables, an invoice that falls outside its set limits goes on hold until someone resolves the difference.

Two-way, three-way and four-way

The names count the documents being compared.

Two-way matching compares the invoice with the purchase order, checking billed price and quantity against what was ordered. It confirms the supplier is charging what was agreed, not that anything arrived.

Three-way matching adds the receipt. The system checks invoiced quantity against received quantity and holds an invoice for a full order if only part of it arrived.

Four-way matching adds an inspection or acceptance step, so nobody pays for goods that failed a quality check. In Oracle E-Business Suite, the "receipt required" and "inspection required" settings on a purchase order shipment determine whether matching runs three ways or four.

Microsoft's Dynamics 365 Finance sets a default line matching policy for each legal entity, which individual purchase order lines can override. One line on an order can require three-way matching while the others keep the default.

Oracle's cloud procurement documentation also separates the matching level from a second choice: whether an invoice is matched to the purchase order or to the specific receipt.

Tolerances decide what stops

Documents do not always agree exactly. Unit prices drift between order and invoice, and deliveries run over or short. Tolerances set how much variance the system accepts before it holds an invoice.

Oracle Payables sets quantity tolerances separately for ordered, received and consumed quantities, each as a percentage or a maximum quantity. A separate price tolerance compares the invoice unit price with the unit price on the purchase order schedule line. Once defined, tolerances are assigned to a supplier site.

The same documentation notes that a percentage tolerance of zero allows no variance, while an active tolerance with no value allows infinite variance. On a setup screen, those two look much alike.

Tight tolerances send more invoices to the exception queue, where someone has to chase a buyer or a receiving clerk. Loose tolerances let more through unreviewed, including ones that are wrong in the supplier's favor.

Where matching gets awkward

Services have no loading dock. SAP's ERP handles them with a service entry sheet: a record of work performed, entered against the purchase order. Invoice verification can then run against the accepted sheet. Whoever accepts it is, in effect, the receiving dock.

Evaluated receipt settlement goes further and removes the supplier invoice. As SAP documents it, the system settles goods receipts directly and generates and posts the invoice itself, so no vendor invoice is required. The vendor must be flagged for it in the vendor master record, and the order price cannot be an estimate. SAP notes there are then no price and quantity variances in invoice verification. Accuracy rests entirely on the order price and the receipt.

Invoices without a purchase order give matching nothing to work with. They rely on approval workflows, and none of the controls above apply.

What to check when evaluating software

Useful questions for a vendor demo or a configuration review:

  • Can the matching level be set per supplier, per item and per purchase order line, or only company-wide?
  • Do tolerances support both a percentage and an absolute cap, and what happens when a field is left blank?
  • Does the system catch a second invoice against a receipt that has already been paid?
  • Where does a held invoice go, and can whoever resolves it see all three documents together?
  • Who can change a supplier's bank details, and what does a change trigger?

What matching does not catch

Matching verifies what the business is paying for, not where the money goes. An invoice that agrees perfectly with its order and receipt still passes if someone switched the supplier's bank details to a fraudster's account the week before.

Business email compromise, where an attacker poses by email as a trusted contact, is one route to that switch. In the Association for Financial Professionals' 2026 Payments Fraud and Control Survey, 74% of the US organizations surveyed said they were affected by business email compromise in 2025. AFP surveyed 465 treasury practitioners in January 2026.

A 2019 FBI Private Industry Notification on business email compromise in the construction sector described exactly this pattern: fraudsters emailed a direct deposit form with instructions to change previously submitted banking details, and later invoice payments went to the altered account. The notice told businesses to confirm transfer requests by phone using previously known numbers. It also advised verifying changes in a vendor's payment location with an extra step, such as a secondary sign-off by company personnel.

Those controls sit in the vendor master and the payment run, not in the matching engine. An evaluation that stops at the matching screens has not tested them.

Sources

  • https://docs.oracle.com/en/cloud/saas/financials/26b/fappp/invoice-tolerances.html
  • https://docs.oracle.com/en/cloud/saas/procurement/26d/oapro/match-approval-level-options.html
  • https://docs.oracle.com/cd/E18727-01/doc.121/e12796/T434602T367249.htm
  • https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/accounts-payable-invoice-matching
  • https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/three-way-matching-policies
  • https://help.sap.com/saphelp_erp60_sp/helpdata/en/f8/1cbf53d25ab64ce10000000a174cb4/content.htm
  • https://help.sap.com/saphelp_erp60_sp/helpdata/en/79/6fb6531de6b64ce10000000a174cb4/content.htm
  • https://www.financialprofessionals.org/about/learn-more/press-releases/Details/over-75-percent-of-us-firms-experienced-payments-fraud-in-2025-while-ai-adoption-for-fraud-mitigation-lags
  • https://www.aha.org/system/files/media/file/2019/11/tlp-white-pin-20191107-001-cyber-actors-leverage-subscription-based-commercial-databases-11-8-19.pdf