Two-way matching checks a supplier invoice against its purchase order alone, comparing price and quantity ordered, with no separate proof of delivery.
Two-way matching is an accounts payable control that compares exactly two documents before a supplier invoice is approved: the purchase order and the invoice itself. It verifies that the unit price, the quantity billed and the commercial terms correspond to what was agreed when the order was raised. It deliberately leaves out the third document used in three-way matching, the goods receipt, so nothing in the check confirms that anything was actually delivered.
The control exists because a receipt is not always meaningful. Subscriptions, consulting days, rent, insurance, freight and utilities produce no delivery note to record, so demanding one simply parks the invoice in a queue waiting for a document that will never exist. Two-way matching lets that category clear on the day it arrives, which keeps early payment discounts reachable and avoids late payment interest. The trade off is explicit: the check catches billing that deviates from the order, but it cannot catch an order that was billed and never fulfilled.
Business Central treats matching as a posting mechanic rather than as a separate engine. Every purchase order line tracks quantity received and quantity invoiced, and a purchase invoice can be built from the order or from posted receipt lines. In practice, two-way matching is what happens when a team posts Receive and Invoice in a single step, or invoices service and G/L account lines for which no independent receipt is ever recorded. What the standard product does not include is a tolerance framework: there are no configurable price or quantity variance thresholds that release small differences automatically, and no built in variance report across open orders. Approval workflows with amount limits are the usual compensating control, and the dedicated matching guide covers how the modes are set up.
Example: a purchase order is raised for 40 consulting hours at CHF 180, so CHF 7,200 net, on 30 day terms. The invoice arrives for 42 hours at CHF 180, so CHF 7,560. Two-way matching surfaces a CHF 360 difference, five percent above the order. Nothing in the check can say whether the two extra hours were worked, so the answer has to come from the budget holder, which is why the approval step is not optional for this category of spend.
The usual failure is drift: two-way matching becomes the default for everything because nobody records receipts, including for physical goods, and short or damaged deliveries stop being caught. Duplicate invoices are a separate risk that matching does not address, which is why recording the supplier invoice number on every document and making it mandatory matters. Teams that measure this split their invoice volume by match type and track the share of invoices posted with no receipt in categories where a receipt should exist.
When there is nothing physical to confirm: services, subscriptions, rent, freight, utilities and most professional fees. For goods that arrive at a dock or a warehouse, the receipt carries information the order cannot, and three-way matching is the appropriate control.
No. It compares an invoice to its order, not to invoices already posted. Duplicate control comes from capturing the supplier invoice number on every purchase document and enforcing it, so the system warns when the same number appears twice for the same vendor.
Zentriq's AI tools automate many of the manual processes around two-way matching in Business Central. Learn about the Zentriq Agent or try Zentriq PunchOut to see how AI simplifies procurement in BC.