Two-way vs three-way invoice matching: choose the evidence each purchase needs

Two-way matching compares an invoice with its purchase order. Three-way matching adds receipt evidence. The extra record is useful when the company needs to establish that the invoiced goods or services were received before releasing payment under its policy. The right control depends on the purchase, the available evidence, and the system's actual configuration.

The labels do not specify every check. Microsoft describes two-way price matching and three-way matching that also compares invoiced quantities with product receipts. Oracle's match-approval documentation describes quantity comparisons within tolerances. Ask which prices, quantities, totals, and additional charges the proposed software checks, rather than assuming the same behavior from a shared label.

Separate goods, recurring services, project milestones, subscriptions, and purchases that legitimately have no purchase order. For each group, define what establishes the approved commitment and what proves the supplier performed. A company may use different matching policies for different purchase categories without weakening its overall review.

Goods delivered to a warehouse often have a receiving process that can provide useful evidence. A software renewal may instead depend on an approved contract, term, and user or usage count. Forcing every invoice through a physical-goods receipt screen can produce meaningless records if nobody is accountable for confirming what happened.

Document the policy owner and any permitted overrides. Employees should know before purchasing which evidence will be needed when the invoice arrives.

Suppose a fictional company orders 100 units at $20 each and receives 60 units before the supplier invoices all 100. Assume no tax, freight, discount, or permitted variance in this simplified test. The purchase order and invoice agree on $2,000, but the recorded delivery supports only 60 units at that point.

The test should show whether the software identifies the unreceived quantity and routes it to the right person. The discrepancy does not prove the supplier is wrong. The remaining goods may have arrived without a recorded receipt, the invoice may be premature, or the commercial terms may require a payment before delivery. Each explanation needs evidence and the appropriate approval.

Do not change the receiving record merely to make the match pass. The receiving owner should confirm what arrived and when. If a partial payment or supplier correction is appropriate, preserve the original invoice and the approved resolution in the record.

Ask the accountant how the invoice, receipt, and any unpaid or disputed amount should appear at close. A payment hold and the accounting treatment are related decisions, but the match status alone does not settle both.

A service receipt should describe the actual acceptance evidence. For a project, that might be an approved milestone or completed deliverable. For a time-based service, it might be approved hours at the contracted rate. For a recurring subscription, it might be the covered period and agreed scope. Use the evidence that corresponds to the commitment.

Name a business owner who can confirm performance independently of the supplier's invoice. Accounts payable should not have to invent acceptance because the requester is unavailable. If the system supports service receipts or amount-based matching, demonstrate the exact workflow and retain the evidence behind the approval.

Microsoft's documentation describes amount and percentage tolerances, including configurable combinations for price matching. The practical decision is which differences the business will accept automatically and which need review. Set that policy using the purchase population, rather than adopting a software default without examining its effect.

Test the tolerance with a small invoice and a large invoice. The same percentage can represent very different amounts. Include freight, discounts, and additional charges so the team knows whether they are checked separately or included in another comparison. An apparently matched line can leave a material unmatched charge elsewhere on the invoice.

Review overrides by reason and approver. Repeated exceptions from one supplier or purchase category may signal a contract, receiving, or setup problem. Raising the tolerance until those invoices pass would conceal that problem instead of resolving it.

Demonstrate an ordinary match, a partial receipt, a price difference, a missing receipt, and a service acceptance. The team should see which invoices are ready for the next step, which are held, why, and who must act. Confirm that a matched invoice still follows the applicable payment approval and destination controls.

Choose two-way or three-way matching by the evidence the company needs for each purchase. The stronger workflow is the one that people can operate honestly, with reliable records and visible exceptions. Adding a third document is useful when it proves receipt, not when it becomes an automatic confirmation created to clear the queue.