Three-Way Match Tolerances and a Supplier Discount Demand
US Operations, a business unit in Oracle Cloud Payables, uses three-way matching with these invoice tolerances: price 5 percent, quantity 2 percent, and total $50. The match approval level is three-way. A purchase order exists for 200 units at $25.00, for a total of $5,000. The supplier ships 206 units; receiving accepts 200 and rejects 6. The supplier then submits an invoice for 206 units at $26.10, totaling $5,376.60, referencing the PO and the receipt. The invoice is matched automatically, but the payables manager sees several holds and asks why the invoice cannot be paid in the next run. The supplier insists that the extra 6 units were a substitution and should be accepted, and offers a 2 percent discount if paid within five days. The business unit also wants to prevent this pattern from recurring without blocking legitimate price increases.
1. Which holds should appear on the invoice, and which should not? Show the tolerance arithmetic that supports each conclusion.
Read the worked answer
Work through each tolerance independently, then confirm the match approval level.
- Price: ($26.10 - $25.00) / $25.00 = 4.4 percent. The configured price tolerance is 5 percent, so the price variance is inside tolerance. A Price hold should not appear. If one does, check whether the tolerance is defined at supplier site level rather than business unit level, or whether the amount is being compared to a different PO price.
- Quantity ordered: 2 percent of 200 = 4 units, so up to 204 units are allowed. The invoice is for 206, an excess of 2 beyond tolerance. A Quantity Ordered hold should appear.
- Quantity received: receiving accepted 200; 2 percent = 4 units, allowing 204. The invoice for 206 exceeds accepted receipts by 6, so a Quantity Received hold should appear. Rejected units cannot be invoiced unless receiving later accepts them.
- Total: PO total is $5,000; invoice total is $5,376.60; variance is $376.60. The configured total tolerance is $50, so a Total or Amount hold should appear.
The invoice should therefore carry quantity-ordered, quantity-received, and total/amount holds, but not a price hold. The rejected 6 units are the root cause of most of the exposure.
2. The supplier offers a 2 percent discount for payment within five days. Should the manager manually release the holds to capture it? What is the correct resolution, and what accounting or control risk would manual release create?
Read the worked answer
Manual release is the wrong first move. Releasing the quantity holds would authorize payment for 6 units that receiving rejected and for a quantity 3 percent above the order, bypassing the three-way match control. The discount is $107.53 on the submitted $5,376.60, or $104.40 on a corrected $5,220 invoice; that is small compared with the $376.60 overpayment and the control breach.
The correct path is to fix the transaction:
- If the 6 substitute units conform, receiving should accept them and a PO change order should increase the ordered quantity to 206.
- If they do not conform, the supplier should credit or reissue the invoice for 200 units.
- If the $26.10 price was legitimately agreed, update the PO price so the price and total comparisons use the approved amount.
- Re-match the invoice, let the system re-evaluate holds, and release only holds that remain after the correction, with documented approval.
A manual release can still be done by an authorized user, but it leaves the receipt and PO inconsistent with the invoice and can misstate received-not-invoiced accruals. The discount can be taken only on a valid invoice if the payment date is on or before the discount date. Paying an invalid gross amount to save about $100 is not a good trade.
3. What configuration or process changes would reduce recurrence while still allowing legitimate price increases?
Read the worked answer
Keep three-way matching for physical goods and control the exceptions at the source rather than widening tolerances broadly.
- Require receipt acceptance before invoicing, and use receipt routing and rejection reasons so rejected quantities are visible to AP.
- Require PO change orders for quantity increases and price increases above the agreed threshold. A legitimate price increase should be reflected on the PO, not absorbed by a tolerance change.
- Consider tighter quantity tolerances for high-risk suppliers and leave price tolerance at a level that reflects normal commodity variation.
- Use supplier-specific tolerance overrides only with documented approval; do not raise the business-unit quantity tolerance just to clear this invoice.
- Monitor the Invoice Hold Report and aging by hold reason. A recurring quantity-received hold usually indicates a receiving or supplier-compliance problem, not a tolerance problem.
- Give hold release authority to a role separate from invoice entry, and require a reason code when a hold is manually released.
These changes preserve the three-way match control while allowing approved price changes to flow through a PO revision.