Purchase order, receipt and invoice: three-way matching in Accounts Payable
The invoice agrees with the purchase order, but part of the receipt is missing in the system. Can it be paid? Only a line-level comparison and the right evidence can distinguish a late posting, a partial delivery and a genuine mismatch.
In Accounts Payable, matching the PO number and total is not enough. The control should connect what was ordered, what was actually received and what the supplier invoiced. This model covers data control and exception handling in the client’s system; it does not replace the client’s purchasing policy or payment approval rights.
1. Define the required match level
Oracle documentation distinguishes two-way, three-way and four-way matching. Two-way matching compares the purchase order with the invoice. Three-way matching adds the receipt, while four-way matching also considers the accepted quantity after inspection. The required level should follow the client’s configuration and policy.
Do not assume that every PO invoice follows the same route. Services, materials and purchases subject to quality acceptance may use different criteria. First identify the order type, required evidence and applicable tolerances.
2. Match lines, not only document totals
Two invoices can have the same total even when one line has an incorrect price or quantity. The control keys should include the PO number, line, item or service description, unit of measure, quantity, price, currency and tax treatment within the client’s scope.
Oracle explains that an invoice can be matched to a purchase order, receipt or other relevant document. In operational terms, the relationship between specific lines must be retained. Agreement at header level does not prove that every line is correct.
3. A tolerance does not remove the cause
A tolerance helps the system decide whether a variance requires a hold, but it should not hide recurring errors. Record the variance type: price, quantity, additional charge, unit, currency, tax or missing receipt.
Editorial example: 100 units were ordered, 80 received and 100 invoiced. The 20-unit difference may reflect a partial delivery, a late receipt record or premature billing. Raising a tolerance explains none of those causes.
4. Handle partial receipts and different dates
Compare data at the same cut-off and separate the latest receipt quantity from cumulative receipts. One invoice may cover several deliveries, while one delivery may support several invoices. Each evidence item needs an identifier so that it is not counted twice.
SAP describes three-way matching as checking the invoice against the purchase order and receipt using rules and tolerances. If the receipt is not yet recorded, the line should remain an exception for clarification rather than being marked as matched without evidence.
5. Close the cause, not merely the hold
For each mismatch record the owner, due date, cause, required document and decision. Common routes include an authorised receipt posting, a supplier credit or corrected invoice, a controlled PO amendment, or an approved exception.
Do not release a hold solely because someone wrote “please pay”. Confirm that source data was corrected and that the approver has the right authority. Retain the previous status, decision evidence and the result of revalidation.
6. Measure the exception queue
The report should show the number, age and value of mismatches, their cause, owner and investigation stage. Separately track the proportion of invoices matched without exception and recurring issues by supplier, business unit or purchase type.
BackOffice Outsourcing can support data controls in Accounts Payable under the client’s systems, procedures and permissions. Describe your purchase order, receipt and invoice workflow to define the control scope. See also our guide to resolving the cause of invoice holds.
Sources and scope
Oracle and SAP documentation was checked on 26 October 2026. Feature descriptions apply to the named products and their configuration. The numerical example, exception register and metrics are editorial proposals to be agreed with the process owner. This guide is not a posting instruction or payment authorisation.
FAQ
Is a purchase order number on the invoice enough for approval?
No. Check the required match level and the relevant lines, quantities, prices and receipt evidence.
Does a missing receipt always mean that delivery did not happen?
No. It may be a late posting or missing evidence, but it must be clarified before the invoice is released.
Can a variance within tolerance be accepted?
Only under the client’s configuration and policy. Tolerance does not replace analysis of recurring causes.
What should an AP exception register contain?
Invoice and line identifiers, variance type and value, owner, due date, decision evidence and the revalidation result.
