2-way vs 3-way matching: how invoice matching works in accounts payable

2-way matching checks a supplier invoice against its purchase order, and 3-way matching also checks it against the receiving record, so you pay only for goods that actually arrived. Both are forms of invoice matching, the accounts payable control that holds an invoice until its documents agree within the tolerances you set.

This guide covers what each match compares, how a 3-way match runs, the exceptions it raises, how to set tolerances and how matching is automated.

What are 2-way, 3-way and 4-way matching?#

Each level adds one document and one rule to the level before it. The rules below are how Oracle Payables defines each level, and every rule applies within the tolerances you set.

• 2-way match: invoice and PO

  The price billed must be at or below the PO price, and the quantity billed at or below the quantity ordered. It catches prices and quantities above the order but can't tell whether anything arrived. Typical use: services, subscriptions and repeat orders from trusted vendors.

• 3-way match: adds the receipt

  The quantity billed must also be at or below the quantity received, as logged on the goods receipt (also called a receiving report or GRN). It stops payment for goods that haven't arrived. Typical use: physical goods.

• 4-way match: adds inspection

  The quantity billed must also be at or below the quantity accepted after inspection. It stops payment for units that failed inspection. Typical use: manufacturing inputs and other goods inspected on arrival.

A purchase order is the buyer's approved order to the supplier: items, quantities and prices, agreed before anything ships. The invoice is the supplier's request for payment, and the receipt records what actually came in. For how POs are raised and approved, see the purchase order process.

How a 3-way match works#

In purchase invoice processing, matching sits between capture and approval (see automated invoice processing for the whole flow). A three-way match runs line by line: each invoice line is paired with its PO line and its receipt, then compared.

Below, the toner line matches on all three documents, but the invoice bills 12 cases of copy paper when 10 were received, so the whole invoice goes to an approver instead of straight to payment.

An invoice that matches the PO and the receipt on every line, within tolerance, can be approved without a person; this one bills two cases that weren't received, so it goes to an approver.

Common matching exceptions and who resolves them#

When the documents don't agree within tolerance, the invoice is held (Oracle calls it a matching hold) until someone resolves the difference. Exceptions are routine. Ardent Partners' State of ePayables 2025, a sponsored analyst report, puts the average invoice exception rate for AP departments at 18.4%.

A repeat invoice is better caught before it reaches matching: see duplicate invoice detection.

How to set matching tolerances#

A tolerance is the variance you accept before an invoice is held. ERPs let you set it as a percentage, an amount or both, and vary it by vendor or item. In Microsoft Dynamics 365, for example, a line with both a percentage and an amount tolerance fails if it exceeds either one. Tolerances are a policy choice, not a standard figure, so set yours from your own exception data.

• Set tolerances by vendor, item or categoryOne global number is too loose for some purchases and too tight for others.
• Cap a percentage with an amount1% of a $500,000 order is $5,000. A not-to-exceed amount keeps a small percentage from becoming a large overpayment.
• Start tight, then loosen with evidenceIf approvers pass the same variance unchanged every time, widen that tolerance; if errors get through, tighten it.
• Match lines, not only totalsOffsetting errors can leave the total right and two lines wrong.
• Give charges their own toleranceFreight and fees that weren't on the PO shouldn't ride inside the price tolerance.
• Review quarterlyLook at exception rates and approved variances by vendor, and adjust.

Automating 2-way and 3-way matching#

Matching is only as good as the data it compares: the invoice's line items, the PO lines and the quantities received. By hand, that means keying lines and laying three documents side by side. With automation, extraction reads the lines, the match runs on every invoice, and people see only the exceptions.

Docsumo, our product, is an intelligent document processing (IDP) platform. For accounts payable automation, it reads invoices, purchase orders and receipts, line items included. On the Enterprise plan, its cross-document checks match each invoice line to the PO and the receipt on quantity, unit price and amount. It also flags duplicate invoices, sends fields it's unsure about to a person and, on the Business plan, routes invoices for approval. Data goes to your ERP through API and webhooks. It doesn't create POs or pay vendors.

The demo below shows 3-way matching in Docsumo, which is on the Enterprise plan.

Play video: How to automate 3-way matching for AP documents in Docsumo (Enterprise plan)

• 99%99%field-level accuracy across 250+ document types
• 95%+95%+of documents processed straight through, without manual review
• 99%+99%+touchless invoices at Valtatech

The bottom line#

Use a 2-way match where there's nothing to receive, a 3-way match for goods and a 4-way match where goods are inspected; invoices with no PO need approval instead. Set tolerances by vendor or category and review them against your exception data. Automation keeps the same rules and removes the keying, so AP spends its time on the invoices that don't match.

Book a demo to see matching on your own invoices, POs and receipts, or start a free trial to test extraction.

Frequently asked questions#