What is 2-way and 3-way invoice matching in accounts payable, and how do I run it across POs, receiving documents, and vendor invoices?

What do two-way and three-way matching compare?

The Indian Affairs Manual's accounts payable chapter defines a 2-way match as one between the obligation and the invoice only, with no receiving report. It defines a 3-way match as verifying that the purchase order, receiving report and invoice match before payment is processed. In a business, the obligation is the approved purchase order.

Two-way asks whether the vendor is billing what you agreed to buy, at the agreed price. Three-way adds whether you received what you are billed for. A two-way match passes an invoice for 100 units against an order for 100 even if only 80 arrived; only the receipt catches that.

What has to exist before a match means anything?

A match is worth no more than the records it reads. A three-way match needs three documents; a two-way match needs only the first and the third:

• An approved order. It is approved before the vendor proceeds and lists each item's unit of measure, quantity and unit price.
• A receipt made from the delivery. Whoever takes the delivery counts it and records what arrived.
• An invoice that quotes the order. The order number lets you pull the right order and its receipts.

New York's State Comptroller, in its receiving guidance for state agencies, says the receiver should record the receipt date, quantity received and quantity accepted at the time of receipt. That guidance requires blind receiving whenever practical: the receiver gets the order without quantities and must independently identify and record the quantity received. It describes the failure for an invoice that arrives with no purchase order: staff route the invoice to the receiver and ask whether everything on it arrived, and with the quantities in front of them the receiver has no need to count.

Record the receipt from your own count of the goods as delivered. The same receiving guidance has receivers attach documents supporting the receipt, so attach the packing slip and note any difference between your count and it. Never copy quantities from the slip or the invoice; they are the vendor's own figures.

Which fields are compared, and at what level?

Compare line by line. Each invoice line is matched to its order line and, in a three-way match, to the receipts recorded against that line:

The quantity and amount rules are those in New York's State Comptroller's matching guidance. Where a line needs no receipt, the invoice quantity may not exceed the unmatched quantity on the order line; where it needs one, it may not exceed the unmatched quantity received; either way, the dollar amount may not exceed the line's remaining balance. The Comptroller's receiving guidance requires the unit received to match the unit on the order, so a case is not a gallon.

Microsoft's documentation for Dynamics 365 Finance matches charges as their own field, comparing the invoice's charges with the purchase order's. Where your orders state payment terms, check the invoice's terms against them and send any difference to whoever approved the order.

Agreeing totals are not a match, as the worked example shows.

How do you run a match, step by step?

Whoever processes invoices runs the match in this order:

1. Pull the documents. Log the invoice and pull the order it quotes and every receipt against that order.
2. Check the header. Confirm the vendor, order number and any payment terms, that the invoice is not a duplicate, and that its lines add up.
3. Compare each line with the order. Check item, unit, quantity, unit price, line amount, and each charge and its amount.
4. Compare each three-way line with its receipts. Compare the invoiced quantity with the quantity received and not yet invoiced.
5. Classify each line. It is matched, within tolerance, an exception, or incomplete because a required document is missing.
6. Hold and route. One failing line holds the whole invoice, and each exception goes to its owner.
7. Match again after each fix. Re-run the comparison against the corrected document.
8. Release the matched invoice. Send it, with its match record, to an approver who neither placed the order nor recorded the receipt, where the business has one; otherwise, see the small-team rule below.

A matched invoice is cleared for approval, not approved or paid. New York's State Comptroller, in its matching guidance, requires agencies that process vouchers online to address match exceptions before a voucher is submitted into workflow.

What is a tolerance, and how is a variance within it handled?

A tolerance is a preset allowance that lets a small difference pass. New York's State Comptroller, in its payment-tolerance guidance, describes tolerances as allowing slight price variations between orders and vouchers during matching, applied to a minimal difference in either the unit price per line or the total cost of the line. A voucher within the tolerance passes matching; one outside it fails, and the exception must be resolved.

In Microsoft Dynamics 365 Finance, for example, a unit-price tolerance can be set per item or vendor, and a line-total tolerance can be a percentage, an amount, or both.

Set tolerances narrowly, following these rules:

• Only where prices genuinely vary. New York's tolerance guidance names items with contractually volatile prices, such as fuel and milk products.
• None where a contract fixes the price. The same guidance applies no tolerance under an agency's own contracts, because the contract sets the price.
• No paying above the order without a documented reason. The tolerance guidance says not to pay prices above the order unless a contractual or legal obligation requires it or the order carried a lower price in error, and otherwise to return the invoice to the vendor for correction.
• Out of the hands of the people they govern. The tolerance guidance sends change requests, with a detailed reason and supporting documentation, to a director outside the requesting unit, and does not publish tolerance values. In a business, only the owner or someone else who neither enters nor matches invoices sets or changes a tolerance, on a written reason, and vendors are not told the values.

Nobody investigates a line that passes on tolerance, so a wide tolerance or routine overrides let the match approve what it was installed to catch. New York's internal control standards warn that a manager can override a control activity because of time constraints. Each month, the owner reviews by vendor how many lines passed on tolerance and how many exceptions were overridden or cleared by amending the order.

What exceptions does a match produce, and who resolves each one?

A line that is neither matched nor within tolerance is an exception, where a document disagrees, or incomplete, where one is missing. The owner is whoever answers for the document in question, not the clerk who found the difference:

The over-delivery and unit-of-measure resolutions follow New York's receiving guidance, which sends any amendment to management for approval and, for over-delivery, has the vendor told of the discrepancy. An amended order makes an exception disappear without resolving it, so the monthly review counts amendments.

What does a line-level match look like on a real purchase?

A café sends purchase order 2051 to its food-service distributor. The supply agreement bills milk at its price on the delivery date, so the owner allows a 3% tolerance on the milk line's unit price and line total, and none elsewhere. The kitchen lead counts the delivery from an order list showing no quantities: 30 cases of milk, 20 bags of flour, 8 cases of cups. The invoice arrives:

The milk variance, 25.20, is inside a tolerance that exists for a contractual reason, so it passes. The cups line holds the invoice. A two-way match would have passed it, 10 billed against 10 ordered; only the receipt shows 2 cases never arrived. The receiver confirms 8, and accounts payable asks the distributor to ship the other 2, which are then received and matched, or to issue a credit memo for 128.00. With the credit memo, the invoice (2,495.20) and the credit (128.00) are matched together and cleared for approval at a net 2,367.20. Record the credit as its own document; do not edit the invoice.

Now suppose everything was received in full and the invoice billed milk at 42.00 (1,260.00), flour at 30.00 (600.00) and cups at 61.00 (610.00). The total, 2,470.00, agrees with the order and with the receipts at order prices. Only the line comparison shows flour about 5.3% over its order price with no tolerance: a price exception. Cups at 61.00, below the order price, pass the price test. Because that saving is what makes the totals agree, confirm from the receipt that the cups delivered are the ones ordered.

Which purchases need three-way matching, and which can take two-way?

Decide by category. The deciding question is whether there is a delivery or performance that someone other than the buyer can confirm:

These rows follow New York's State Comptroller. Its matching guidance requires receipts on all order lines for commodities. Its receiving guidance exempts utilities from receipt entry. The same receiving guidance says blind receiving is not necessary for prepaid services or fixed-cost lease payments, which still take a receipt. It has receipts for ongoing services recorded when the services are received or contractually due, by a receiver who does not know the quantity ordered, and says amount-only receiving may suit repairs of unknown extent and professional services.

A service invoice approved only by whoever ordered the service is a two-way match, whatever the system calls it.

What changes when one order arrives in several deliveries and invoices?

Matching becomes cumulative. New York's State Comptroller, in its receiving guidance, requires a receipt for each delivery, and its system matches each invoice line to the receipts recorded against that order line. Compare each invoice with the quantity received and not yet invoiced, not with the full order quantity.

For each order line, keep three running figures: ordered, received to date and invoiced to date. An invoice line passes only if invoiced to date, including it, stays at or below received to date. For example, an order for 100 receives 60, then 30. An invoice for 60 passes; a second invoice for 40 fails, because only 30 are received and unbilled. A duplicate fails this test only if it pushes invoiced to date above received to date, so the step-2 check of vendor invoice number, date and amount against invoices already logged remains the duplicate control. Close the line when the three figures agree or the vendor confirms the unshipped balance is cancelled.

How do you run the match without purchase orders or a purchasing module?

Without orders there is nothing to match, and an order typed up after the invoice only copies it. New York's State Comptroller, in its receiving guidance, notes that buying without a purchase order hinders blind receiving and raises the risk of paying for goods and services not ordered or not received. The minimum order discipline has four parts:

• Every purchase above a limit you set gets a numbered order before the vendor proceeds.
• Someone other than the buyer approves it, and it states vendor, item, unit, quantity and price.
• The vendor quotes the order number on the invoice.
• A recurring charge gets one standing order for the contract or period, which each invoice quotes and draws down.

Designing the wider payables workflow, and handling invoices with no order, are separate questions.

Without a purchasing module, a spreadsheet or paper file can carry the match. The Comptroller's receiving guidance expects receiving to establish what was received, the quantity or amount, the date and who received it. The file needs three records:

• Order log. It holds the order number, date, approver and vendor, and each line's item, unit, quantity and price, with running received and invoiced totals.
• Receiving log. It holds the order number, date, item, unit, quantity counted and accepted, and the receiver's name, with the packing slip attached.
• Match record. It holds each invoice's line results, tolerances applied, exceptions with owner and resolution, and who released it.

The Comptroller's receiving guidance says receiving should be recorded outside the payment process. Only receivers write the receiving log, on signed paper or in a sheet the invoice processor can read but not edit. Whoever matches takes received to date from that log, never types it, and writes only the match record.

Run the same eight steps against these records. Check your accounting system's documentation for whether, and under which settings, it matches orders, receipts and invoices. If it does, let it make the comparisons in steps 3 and 4; you still classify, route and release. In Microsoft Dynamics 365 Finance (documentation last updated 2025-05-15), for example, matching calculations typically run automatically when vendor invoices are edited, or on demand, depending on a setting.

Who should order, receive and approve?

The match has force only because different people produce the documents. New York's State Comptroller, in its separation-of-duties guidance, says the procure-to-pay activities, from initiation, purchase approval and ordering to receipt and payment approval, should ideally be done by different employees. In its example, one employee orders, a second receives and counts, and a third compares the invoice with the order and receiving information and approves it; that separation helps ensure the organization orders what it needs, gets what was ordered and pays only for the volume received.

So the invoice approver should be neither the person who placed the order nor the one who recorded the receipt. Someone who orders, receives and matches is checking their own paperwork.

Small teams drift there, for instance when the bookkeeper starts signing for deliveries. For staff too few to separate tasks, the separation-of-duties guidance says management should perform a risk assessment, establish compensating controls where it will not accept the risk, and document any residual risk it accepts, adding that compensating controls often include a post-transaction review. Where nobody can approve without having ordered or received, the owner decides in writing who approves (usually the owner, for orders the owner placed, provided someone else recorded the receipt), records the risk accepted, and relies on that review as the compensating control. For matching, that review goes back to the goods. Someone who neither ordered nor received them, the owner or, if the owner places orders, an outside accountant, attends some deliveries unannounced and counts them, or counts goods on hand against recent receipts. Never check receipts against packing slips or invoices, because a receipt copied from them agrees with them. The same person approves any exception cleared by override or amendment.

What does a match catch, and what does it miss?

New York's State Comptroller, in its matching guidance, says its receipt and matching requirements help to ensure that agencies pay only for commodities received, pay no more than the price agreed in the order, and do not exceed order-line amounts and quantities. The match proves the documents agree, not that they are true, so it misses five things:

• A bad order. An order at an inflated price, or for goods nobody needed, produces an invoice that matches it; order approval is the control for that.
• Collusion. New York's internal control standards note that two or more employees can act together in collusion to circumvent control. A buyer and a receiver who both document goods that never arrived pass any match.
• Quality. A count says nothing about condition; New York's receiving guidance has receivers confirm that quality received matches quality ordered.
• A receipt copied from the vendor. A receipt taken from the invoice or packing slip agrees with them by construction.
• Who gets paid. The match compares quantities, prices and charges, not payment details; an invoice carrying changed bank or remittance details matches as well as a genuine one. Checking payee details belongs to payment approval, a separate question.

Keep the exception record by vendor: it shows who short-ships, overbills or adds unordered charges, which is evidence when you raise the pattern with them.