Invoice Blocked for Quantity Variance

Accounts payable reports that a vendor invoice is sitting unpaid and the vendor is chasing payment or threatening to put the account on hold. The AP clerk says the invoice 'is stuck in blocked status' or 'won't release no matter what I do' and cannot explain why, since the amount matches the PO. Sometimes the complaint comes from the buyer instead, who is told by the vendor that an invoice from weeks ago has not been paid, and only finds out from AP that it is quantity-blocked, not price-blocked. Occasionally the report is the reverse: someone tries to release the invoice manually and the block reappears the next posting run, which is the point at which the case usually reaches whoever owns MM configuration rather than staying with AP.

Pull the blocked invoice list filtered on the quantity variance blocking reason and cross-reference each line against the purchase order history table entries for that PO item, showing ordered, received, and invoiced quantities side by side. A genuine shortfall shows received quantity below invoiced quantity with no reversal document in between. A false positive from unit of measure shows matching physical quantities but mismatched units and conversion factors on the same line.

If the tolerance key is genuinely too tight for legitimate business variance, widening it in OMR6 is a configuration change requiring a transport and sign-off from whoever owns invoice verification policy, since it changes exposure for every vendor under that company code. If the cause is a missing or partial goods receipt, the fix is a data action: get the warehouse or receiving team to post the outstanding GR, then release the invoice through MRBR, no config change involved. If the cause is a unit of measure conversion error, correcting the conversion factor in the material master is a data fix but must be checked against any open POs that already used the wrong factor, since those may need manual correction. If the cause is duplicate invoicing, the erroneous invoice document must be reversed with MR8M, not released, and the vendor's credit or resubmission handled separately. If the GR-based flag is wrong for how the vendor actually bills, correcting the PO item setting is a data fix for new POs but existing open items may need the flag changed with care, since it affects future matching for that item only.

The reflex fix is to release the invoice manually through MRBR without checking why it was blocked, on the theory that the amount looks fine and the vendor needs paying. This clears the immediate symptom but pays for goods that may not have arrived, or pays twice against the same receipt, and does nothing to stop the same PO item from blocking again on the next invoice. It also erases the diagnostic trail, since once released the block reason is no longer visible in the standard worklist, making it harder for anyone downstream to notice a pattern of repeated quantity mismatches against the same vendor or material.

Accounts payable owns monitoring the blocked invoice worklist and cannot release blocks caused by missing receipts on their own. Procurement or the MM configuration team owns tolerance key settings and the GR-based invoice verification flag. Warehouse or receiving owns posting the missing goods receipt. The handover note should state the PO and item, the tolerance key that fired, the quantity variance amount, and which of the two teams needs to act before AP retries the release.