Each document answers a different question. The purchase order says what was agreed: items, quantities, prices and terms. The goods receipt, or service entry, says what actually arrived and was accepted. The invoice says what the supplier is asking to be paid. Three-way match compares all three line by line. If the invoice bills for 400 units at the agreed price and the receipt confirms 400 accepted units, it can be paid. If not, it becomes an exception.
Exact matches are rare, so organisations set tolerances: how far a price, quantity or total may differ before a human must look. Tolerances often vary by category and supplier, for example a small allowance on freight-heavy goods and none on fixed-price services. Mismatches outside tolerance go to an exception queue, and the fastest teams route each exception by type: price differences to procurement, quantity differences to the receiving team, invoice errors back to accounts payable or the supplier.
Two-way match, invoice against purchase order only, is common for services or low-risk spend where no physical receipt is recorded. Four-way match adds an inspection or quality record, typical in regulated and manufacturing environments. Whatever the variant, the benefit is the same: paying only for what was ordered and received, at the agreed price, and catching duplicate invoices and billing errors before the money leaves. Its weakness is manual effort when the documents live in different systems.
How iProcure handles three-way match
Three-way matching sits in iProcure's Invoices module, which is shown on sample data today. The demo shows invoices checked against the order and the receipt, every captured value traced to its source, and only real mismatches sent to a person. Invoice approval from email is live; each country's statutory checks and ERP sync are on the roadmap.