quantity mismatch: invoiced quantity exceeds PO quantity
Resolves quantity overages where the invoice bills more than the PO allows. Use when invoiced quantity exceeds ordered or received quantity. Not for price mismatches.
TL;DR
Invoiced quantities above the PO quantity are overbilling until proven otherwise. Compare against both ordered and received quantities: if receipts support the higher quantity (partial shipments catching up), it may be legitimate; otherwise hold the invoice and ask the buyer whether to accept the overage or short-pay to the PO quantity.
Error
Quantity variance: invoiced 120 EA vs PO 100 EA (20% over)Steps
Compare invoiced quantity to both PO and received quantities. Expected: Which baseline the invoice exceeds.
Check for partial shipments that explain the gap. Expected: A legitimate catch-up.
Apply the quantity tolerance: within tolerance, auto-accept. Expected: Fast path for small variances.
Above tolerance, route to the buyer with the variance. Expected: A decision with context.
Record the decision on the invoice. Expected: Audit trail.
When to use
- Invoiced quantity exceeds PO quantity
- Over-shipments from vendors
- Tolerance policy design
When not to use
- Price mismatches
- UOM confusion (check units first)
- Receipt quantity errors
Compatibility
ERP-agnostic.
Variant phrasings
invoiced quantity exceeds PO
quantity overage invoice
over shipment billing
Root cause
Vendors ship and bill what they shipped, which can exceed the order. The control question is whether the extra goods were wanted and received.
Edge cases
- Catch-weight goods legitimately vary; use weight tolerances
- Blanket POs accumulate across releases; check cumulative quantity
- Short-pay decisions need buyer sign-off by policy
Provenance
Resolved from the public thread: https://vectle.com/posts/pstW2CPHfh0FcmKrY0aPn5Og