What it means
A business orders goods or services, records what it receives and later gets an invoice. Three-way matching compares these records before payment, and an exception appears when the information fails a defined check.
The purchase order shows authorised terms, the receipt shows what arrived or was accepted, and the invoice shows what the supplier requests. A mismatch may be genuine or simply a timing or data-entry issue, so review the records rather than assuming wrongdoing.
For example, an invoice may charge for 100 units while the receiving team recorded 90, and the missing ten may still be in transit, may have been rejected or may reflect an incomplete receipt entry. Price discrepancies also occur when the invoice unit price differs from the order because of a changed agreement, a currency issue or a supplier mistake, so check the approved terms and any amendment.
Companies can set tolerances for small differences, and Microsoft's Dynamics 365 documentation describes configurable price and quantity matching policies for its product. A software tolerance is a control choice, not a universal legal allowance or a reason to ignore suspicious differences.
An exception may affect one line while other lines match, so keep line-level detail; whether to pay an undisputed portion depends on the system, contract and business policy. The receiving record must be reliable, because an invoice can be correct but show an exception when goods arrived without the receipt being posted.
A purchase order can also be wrong: if an approved price changed but procurement did not update the order, invoices will repeatedly fail, so investigate who owns the master data and the approval trail. Different purchases may use two-way or three-way matching, and a service may need evidence of acceptance rather than a physical goods-received note.
The exception rate can help monitor the process. Divide invoices with at least one defined match exception by invoices subjected to the same matching rule, so that 120 of 2,000 gives a rate of 6%.
State whether the numerator counts invoices or exception events, because one invoice with three line errors is one affected invoice but three events. A high rate can delay supplier payments and consume staff time, and it may point to weak orders, delayed receiving, price changes or unsuitable tolerances.
A low rate is not proof every invoice is correct, since loose tolerances, missed invoices or weak receipt controls can suppress recorded exceptions. Create a clear queue with ownership and age, document approvals for legitimate differences, and never pay a disputed invoice merely to empty the queue.
In practice
Real-world examples.
Example
A supplier invoices 100 units, while the purchase order is for 100 and the receipt records 90. The team checks whether the missing ten units are in transit, rejected or simply unrecorded. The invoice is held for the short quantity while the rest of the order stays approved.
Example
An invoice price exceeds the approved order price by $2 a unit on a 500-unit order. Procurement verifies whether a documented price change exists. If it does, the order is amended and the $1,000 difference is cleared with an approval record; if not, the supplier is asked for a corrected invoice.
Example
A receipt has not been posted even though goods arrived. The receiving team corrects its record after checking delivery evidence. The invoice then matches and is released, and the team reviews why the receipt was delayed.
Formula
Calculation
Illustrative affected-invoice exception rate = invoices with a defined three-way match exception / invoices subject to three-way matching x 100. For 120 / 2,000, the rate is 6%.
The same data can be viewed by event. Suppose the 120 affected invoices carry 180 separate line exceptions, so the average is 180 / 120 = 1.5 events per affected invoice. Reporting both the 6% invoice rate and the 180 events lets accounts payable see how many invoices are blocked and how much line-level work sits behind them.Case study
Seen in the real world.
This entirely fictional case follows Pine Distribution, an invented buyer with many held invoices. Staff found that updated supplier prices were not reflected in approved orders. Procurement corrected the approval process and monitored exception reasons. No real supplier-payment improvement is claimed.
The accounts payable lead sorted the held invoices by cause rather than by supplier. Price differences, unposted receipts and quantity shortfalls each had a different owner, and each owner received a weekly list showing the age of every case. Over the following quarters the team tracked both the invoice rate and the event count. The illustrative lesson is that the percentage showed the size of the problem, while the cause breakdown showed where to fix it.
Watch out
Common mistakes.
- Treating every exception as proof the supplier billed incorrectly.
- Clearing discrepancies without checking the order, receipt and approval trail.
- Comparing invoice-based and line-event rates as though they were the same.
Questions
People also ask.
Does an exception always stop payment?
No. The treatment depends on the matching policy, contract and approval process.
Can a valid invoice show an exception?
Yes. A late or inaccurate receiving record can trigger one.
How should a team reduce exceptions?
Analyse causes and fix ordering, receiving or supplier-data problems.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%