Browse Business Software Categories

A
B
C
D
E
F
H
I
M
N
P
R
S
W
Close  

Accounting

Distribution

eProcurement

ERP

Financial Management

Three-Way Match in Accounts Payable: How It Works and How Software Automates It

Sherman Hsieh
Share This Post!
Published
Three-Way Match in Accounts Payable: How It Works and How Software Automates It

Last updated: October 7, 2026 · Independent guide · We do not sell rankings or coverage.

A three-way match in accounts payable checks a supplier invoice against the purchase order and the receiving record before the invoice is approved for payment. The PO confirms the agreed price, the receipt confirms what arrived, and the invoice states what the supplier wants paid. When all three agree within your tolerances, the invoice can pay without anyone touching it. When they do not, it is held as an exception until the right person resolves the price or quantity difference. The match itself takes seconds in most ERPs, but each stage around it has a different owner, and most failures start there.

The three-way match process in seven stages

  1. Raise and approve the purchase order. Purchasing records item, quantity, unit price and unit of measure.
  2. Receive the goods and post the receipt. The warehouse records what physically arrived against the PO.
  3. Capture the invoice. AP enters or imports the supplier invoice and links it to the PO.
  4. Run the match and apply tolerances. The system compares invoice price to the PO and invoice quantity to the receipt.
  5. Resolve exceptions. Purchasing fixes price differences, receiving fixes quantity differences, and AP coordinates.
  6. Approve and schedule payment. Matched invoices are released for the next payment run.
  7. Clear accruals and post variances. Accounting reviews the received-not-invoiced balance and posts price and quantity variances at period end.

Oracle’s Payables documentation sets out the levels. Two-way matching checks invoiced quantity against quantity ordered, three-way adds quantity received, and four-way adds quantity accepted when the PO requires inspection (Oracle Payables Help, no date shown). Use two-way for services, three-way for stocked goods and four-way for materials that go through incoming quality control.

Who does what: stage ownership table

This RACI-style summary shows who does the work (R), who answers for the result (A), and who is consulted or informed (C/I). Adjust the titles to your organization, but keep price changes out of AP’s hands.

Stage Responsible (R) Accountable (A) Consulted / Informed (C/I)
1. Purchase order Buyer Purchasing manager Requester (C), supplier (I)
2. Receipt Receiving clerk Warehouse manager Quality control (C), buyer (I)
3. Invoice capture AP specialist AP manager Supplier (C)
4. Match and tolerances System, monitored by AP Controller (owns tolerance policy) Purchasing (C)
5. Exceptions Buyer (price), receiving (quantity) AP manager Supplier (C), requester (I)
6. Payment approval AP manager Controller or treasurer Supplier (I)
7. Accruals and variances General ledger accountant Controller Cost accounting (C), purchasing (I)

Stage 1: Raise and approve the purchase order

The buyer creates the PO from an approved requisition or reorder signal, and a manager approves it within their spending limit. The output is a PO sent to the supplier, which becomes the price reference for the match.

The control is that the PO carries the price the supplier will actually bill. POs issued at an old price, or without freight and surcharges, become price exceptions at stage 5.

Stage 2: Receive the goods and post the receipt

The receiving clerk counts what arrived and records a receipt against the PO line. NetSuite calls it an item receipt, Dynamics 365 a product receipt and SAP a goods receipt. For inventory items, the receipt also posts a debit to inventory and a credit to an accrued purchases or received-not-invoiced liability.

The control is that receipts are posted on the day goods arrive and record only what passed the dock check. Late receipts are a common reason a three-way match fails. Stampli, an AP automation vendor, points out that NetSuite’s native match works only once item receipts are recorded (Stampli, June 2, 2026). Receiving against supplier advance ship notices makes receipts faster and more accurate; see our guide to the EDI 856 advance ship notice.

Partial receipts are routine in distribution, so the receipt must record the quantity actually received, not the quantity ordered.

Stage 3: Capture the invoice

The AP specialist enters the invoice or imports it through document capture and links it to the PO number.

The controls are a duplicate invoice number check per supplier and a rule that invoices without a valid PO number go back to the supplier or requester. Capture line detail, not only header totals, or the system cannot tell which line caused a difference.

Stage 4: Run the match and apply tolerances

The system compares invoice price to PO price and invoice quantity to received-but-not-invoiced quantity. A tolerance is the variance you allow before the system flags an exception. Too tight, and rounding differences stop invoices; too loose, and price increases pay without review. The controller should own the tolerance policy, because each tolerance accepts small overpayments in exchange for less manual work.

ERPs set tolerances differently:

  • Dynamics 365 Finance sets net unit price tolerance percentages by item, vendor, their groups or legal entity, plus separate charges tolerances (Microsoft Learn, May 15, 2025). The matching level can be set down to the PO line, and a user can approve posting with discrepancies (Microsoft Learn, June 4, 2026).
  • NetSuite has percentage and absolute quantity limits for bill against PO and bill against item receipt, set on the item, vendor or subsidiary. They drive the 3 Way Match Vendor Bill Approval Workflow, which needs the Approvals Workflow SuiteApp (Oracle NetSuite Help, no date shown).
  • SAP S/4HANA uses tolerance keys such as DQ for quantity and PP for price. An invoice above the upper limit is blocked for payment as a whole, even if only one line varies (SAP Learning, no date shown).
  • Sage Intacct sets quantity and price tolerance percentages per purchasing transaction definition (Sage Intacct Help, October 1, 2026). The page describes percentages only.

A percentage on its own lets large lines through with large dollar variances, so pair it with an absolute cap where the software allows. Use tighter limits on high-value items than on consumables. When one invoice covers several receipts, the engine should match against all open receipt lines; Dynamics 365 Finance, for example, lets you select receipt lines from multiple purchase orders (Microsoft Learn, May 15, 2025).

Stage 5: Resolve exceptions

Purchasing owns price exceptions, receiving owns quantity exceptions, and AP tracks the queue. AP should not change PO prices itself, because the same person would then control both the commitment and the payment, which weakens segregation of duties.

  • Invoice before receipt. Goods arrived but nobody posted the receipt. Post the receipt rather than override.
  • Price variance. The supplier billed a new price that never reached the PO. The buyer amends the PO or requests a credit.
  • Quantity variance. Over-billing, short shipments, or rejected goods still invoiced.
  • Unit of measure mismatch. PO in eaches and invoice in cases, which shows as a quantity and a price variance at once.
  • Unplanned charges. Freight, fuel surcharges and tariffs that were not on the PO. Handle them with a charges tolerance or a two-way rule.

Illustration: a distributor with a 2% price tolerance and zero quantity tolerance. All figures are illustrative. The PO is for 1,000 units at $12.50, or $12,500. The supplier ships 600 units, which the warehouse receives. The invoice bills 1,000 units at $12.80 plus $150 freight, or $12,950. The match fails three ways: 1,000 units invoiced against 600 received, a price 2.4% above the PO, and a freight line the PO never had.

The buyer confirms an announced price increase that was never keyed, amends the PO to $12.80 and approves the freight. AP pays 600 units at $12.80 ($7,680) plus $150, a total of $7,830, and the other 400 units stay open until received. At a $12.50 standard cost, $180 posts to purchase price variance. At $12.70, a 1.6% variance, the price would have passed with no review.

Stage 6: Approve and schedule payment

Matched and cleared invoices are released for the next payment run, which the AP manager reviews and the controller or treasurer approves.

The control is that only matched or formally approved invoices enter the run, and any invoice posted with a discrepancy carries the approver’s name and reason. What goes wrong here is timing: exceptions that sit for weeks cost you early-payment discounts.

Stage 7: Clear accruals and post variances

At period end, the general ledger accountant reviews the received-not-invoiced balance and posts any variances. NetSuite’s help shows a receipt crediting Accrued Purchases and the vendor bill debiting it. Any difference stays in Accrued Purchases until Post Vendor Bill Variances moves it to quantity, price or exchange rate variance accounts (Oracle NetSuite Help, no date shown).

Under standard costing, the price difference becomes purchase price variance, as explained in our guide to standard cost vs actual cost. Unmatched receipts and unreviewed variances pile up in the accrual account and slow month-end close, so age the balance every month.

Metrics to track

  • Exception rate, split by cause (price, quantity, missing receipt, unit of measure, charges) so each owner sees their part.
  • Touchless rate: the share of invoices that pay with no manual step.
  • Cost per invoice: total AP processing cost divided by invoices processed.
  • Invoices received before their receipt, the most direct measure of receiving discipline.
  • Exception age by owner.
  • Variance passed within tolerance: dollars paid above PO price without review, reported quarterly.
  • Received-not-invoiced aging at 30, 60 and 90 days.
  • Early-payment discounts missed because of open exceptions.

For benchmarks, Ardent Partners’ 2025 research, summarized by apexanalytix (which sells AP recovery software), reports an average exception rate of 14%, $9.40 per invoice against $2.78 for best-in-class teams, and touchless processing of 32.6% against 49.2% for the best (apexanalytix, March 12, 2025). Our AP and AR KPI guide covers how to build these into a dashboard.

How software supports each stage

Dynamics 365 Finance, SAP S/4HANA, NetSuite and Sage Intacct document native tolerance-based matching, so on those systems your effort belongs in receiving discipline and tolerance design.

Acumatica creates bills from purchase receipts and posts cost differences to purchase price variance, according to MYOB’s help for its Acumatica-based edition, which describes no tolerance check (MYOB Acumatica Help, no date shown). In April 2026 Acumatica announced a closed beta of a “Matching Hold” status, preliminarily targeted for 27R1 (Acumatica Community, April 15, 2026). Business Central lets you pull received-not-invoiced lines with Get Receipt Lines but describes no tolerance-based match (Microsoft Learn, no date shown); add-ons such as Continia Document Capture add order and receipt matching (Continia Docs, no date shown). QuickBooks Online links POs to bills with partial quantities (Intuit QuickBooks Help, no date shown), but Intuit describes no separate receiving document, so stage 2 has no record of its own.

AP automation platforms mainly cover stages 3 to 6. Tipalti offers two-way and three-way matching at header and line level, with tolerances by amount or percentage (Tipalti, July 22, 2026). BILL supports three-way matching for QuickBooks Desktop, NetSuite and Sage Intacct (BILL, no date shown). Ramp matches against receipts created in Ramp or imported from NetSuite, so QuickBooks users record receipts in Ramp (Ramp Support, no date shown). Stampli prompts receivers to confirm receipt early (Stampli, June 2, 2026). For the wider case for automation, see how AP automation cuts costs and strengthens controls.

How we researched this

We reviewed the top-ranking pages for this term, mostly vendor blogs with little on tolerances, partial receipts or who owns each step, then read vendor documentation for every product named. Each claim links to its source with the date shown on the page. No vendor paid for inclusion.

Related guides

Frequently asked questions

What are the three documents in a three-way match?

The purchase order, the receiving record and the supplier invoice. The invoice is approved only when its price agrees with the PO and its quantity agrees with the receipt, within your tolerances.

What is the difference between two-way and three-way matching?

Two-way matching compares the invoice only to the PO. Three-way also compares invoiced quantity to quantity received, so it can stop payment for goods that never arrived.

What is a normal tolerance for three-way matching?

No regulator or accounting body sets one, so each company chooses its own. Combine a percentage with an absolute dollar cap where your software allows, and set tighter limits on high-value items.

How do you handle a partial receipt in a three-way match?

Pay for the units received and not yet invoiced, and leave the rest of the PO open. If the supplier billed the full quantity, hold or short-pay the unreceived portion and request a corrected invoice.

Can QuickBooks do three-way matching?

QuickBooks Online links POs to bills, but Intuit describes no separate receiving document. For a true three-way match, add a tool that records receipts, such as Ramp.

Who should resolve three-way match exceptions?

Purchasing owns price exceptions and receiving owns quantity exceptions. AP coordinates and approves payment but should not change PO prices itself, which would weaken segregation of duties.

Sources

Sherman Hsieh

CEO & Editor-in-Chief, Business-Software.com
Independent analysis of enterprise software — ERP, CRM and more
Sherman Hsieh is the founder, CEO, and editor-in-chief of Business-Software.com. He leads the site's independent, buyer-focused coverage of ERP, CRM, and other business systems, including vendor-neutral comparisons, pricing analysis, and implementation guidance. Before founding Business-Software.com, Sherman was an executive at Siebel ...

Users Who Read This Article Also Read