Why Three-way match matters to internal audit and controllers
The match compares quantities, prices and terms across the three documents. An invoice that bills for more than was ordered or received should be held.
A two-way match checks only the order and the invoice, which suits services. A four-way match adds an inspection record.
Most ERPs enforce the match. The risk sits in the gaps: tolerances set too wide, users overriding a block, and invoices posted without a purchase order.
A failed match caught at entry costs far less than a recovery.
An example
A purchase order is raised for steel bars at an agreed price. The goods receipt records fewer bars than ordered. The supplier invoice bills the full quantity at a higher price. A three-way match holds the invoice until the difference is explained.
How IRAME handles it
In IRAME's AP control, IRA, IRAME's agentic AI, runs the match on every invoice before payout, using SAP, Oracle or NetSuite data. GenAI reads PDF and scanned invoices. Each mismatch goes to an owner in Action Hub.