Invoice Hold on a Blanket Agreement Receipt
A services company buys MRO supplies through a punchout catalog and direct purchase orders. A blanket agreement with supplier X has a total value of $250,000 and a quantity tolerance of plus or minus 2%. A recent PO for 1,000 safety gloves at $48 each was received as 980 units; the receipt was recorded as 980. The supplier invoice is for 1,000 units at $48, plus $960 tax, total $48,960. The three-way match tolerance is 2% for quantity and 1% for price. The invoice is on hold. The buyer also notices that the PO was created from a requisition that had a $50,000 approval threshold, but the PO total is $48,000, and the requisition was approved by a manager with a $25,000 limit. The supplier is on the approved supplier list but its insurance certificate expired last month.
1. Identify the most likely reasons the invoice is on hold and determine whether the quantity variance alone should block payment.
Read the worked answer
The quantity variance is 20 units on 1,000 ordered, which is exactly 2%. Because the tolerance is 2%, the match may pass or fail depending on whether the system treats the boundary as inclusive. That ambiguity alone is a weak reason to hold the whole invoice, but it is not the only issue.
The stronger causes are:
- Tax: the PO appears to be $48,000 with no tax line, while the invoice adds $960. If tax is not configured as a recoverable or matching-relevant charge, the invoice will fail the match even though the price is correct.
- Approval authority: the requisition total of $48,000 exceeds the approving manager's $25,000 limit. If the workflow did not escalate, the PO is non-compliant regardless of the invoice match.
- Supplier compliance: the insurance certificate expired last month, which should trigger a supplier hold or block depending on configuration.
The buyer should not release payment simply because the quantity is within tolerance. Paying 1,000 units when only 980 were received would create a 20-unit overpayment unless the agreement explicitly allows full invoicing against a 2% under-receipt. The correct first step is to read the hold reason code and separate match failure from supplier or approval holds.
2. What resolution steps should the buyer take before releasing the invoice?
Read the worked answer
Resolve each control failure on its own terms.
- Quantity: confirm whether the 2% tolerance is inclusive. If it is, the quantity match can pass; if not, the invoice should be adjusted to 980 units or the supplier should be asked for a credit note for 20 units. Do not override the receipt without evidence of the missing gloves.
- Tax: determine whether the $960 is recoverable tax that should have been on the PO. If it is valid, correct the PO or tax setup and re-run the match; if it is invalid, request a corrected invoice.
- Approval: route the requisition or PO for approval at the correct authority level. A $48,000 commitment approved by a $25,000-limit manager needs retroactive escalation and a documented reason.
- Supplier insurance: obtain a renewed certificate and update the supplier record before releasing payment, or obtain a documented exception from procurement compliance.
Only after these steps should the buyer consider a manual hold release. The judgment is to avoid converting a configuration gap into a payment error. If the supplier is strategic and the gloves are operationally needed, the buyer can expedite the certificate and approval in parallel, but payment should still wait for the corrected match.
3. What procurement controls would prevent this recurrence?
Read the worked answer
The incident combines three preventable control gaps.
- Approval limits: the requisition workflow should derive approval authority from the total commitment, including tax and anticipated changes, not from the PO amount after the fact. Test the $50,000 threshold with a $48,000 requisition and a $25,000 approver to confirm escalation works.
- Supplier qualification: insurance expiry should be a monitored supplier qualification attribute with an automatic block or warning before a PO is created. A monthly exception report listing expired certificates is more reliable than relying on the buyer to notice.
- Match configuration: decide explicitly whether the 2% quantity tolerance is inclusive or exclusive, and align the blanket agreement, receipt, and invoice tolerances. Tax should be configured so that valid recoverable tax does not create a false match failure.
The deeper control is a hold-reason dashboard reviewed daily. A single invoice hold is a transaction problem; a pattern of holds on the same supplier or buyer is a process problem. The buyer should also check whether the punchout catalog carries the correct unit price and tax code so that future POs do not repeat the mismatch.