Two-Way vs Three-Way Matching
Two-way matching compares an authorized purchase order with the supplier invoice. Three-way matching adds a receipt or service-acceptance record, so payment depends on agreement among what was ordered, what was received or accepted, and what was invoiced. The suitable method depends on purchase type, evidence, risk, policy, and approved exceptions.
The two-way comparison plus goods receipt, service entry or acceptance, actual quantity, condition, date, returns, rejection, and receiver authority.
Goods, services, recurring invoices, blanket orders, non-PO purchases, materiality, fraud risk, operating cost, exception ownership, and monitoring.
Make the definition traceable to authoritative purchase records.
A trustworthy procurement, matching, purchase-order, invoice, supplier, or vendor concept names its object, perspective, lifecycle boundary, source, owner, evidence, authority, and consequence.
Define the object and boundary
Name the entity, buyer or seller, supplier, client and project, contract or policy, request, order, receipt, invoice, payment, currency, period, rule, and what is included or excluded.
Align authoritative inputs
Use consistent identities, references, versions, dates, quantities, rates, amounts, currencies, tax, statuses, delivery or acceptance evidence, approvals, adjustments, and source systems.
Record the decision or transition
Preserve the rule, tolerance, authority, actor, time, source objects, variance, evidence, communication, and downstream supplier, payable, payment, project, client, access, or accounting action.
Keep uncertainty and exceptions visible
Show missing sources, mismatches, disputed terms, duplicates, partial delivery, credits, refunds, changed details, corrections, and the recovery owner.
Questions that prevent a misleading procurement conclusion.
Use these prompts when designing source-to-pay processes, matching invoices, managing suppliers, releasing payments, communicating with stakeholders, or choosing software.
two-way vs three-way matching, answered.
Why does this definition matter?
Without stable boundaries, teams can confuse sourcing with purchasing, treat an invoice as purchase authority, pay without delivery evidence, or split one supplier across duplicate records.
Can software determine the legal or accounting treatment?
Software can apply selected rules, but accountable owners and qualified professionals must choose policy, evidence, authority, tolerance, tax, legal, and reporting treatment.
How should a team apply this page?
Map one real purchase or supplier relationship, identify authoritative records and owners, then test the normal path, a correction or reversal, and a meaningful exception.
Make the definition operational.
Connect it to authoritative records, ownership, evidence, limitations, and recovery.