SAP MM Partial Receipts: Check Invoice Quantity Variances

A purchase order can be correct while an invoice still raises a quantity concern. The supplier may invoice the full order before all material arrives, a receipt may have been reversed, or an earlier invoice may already account for some quantity. The first useful question is therefore not “How do I remove the block?” It is “Which quantities are being compared, in which units, and at what point in the document history?”

This worked example supports learners exploring SAP MM training in Vizag. The numbers are fictional and exclude tax, freight, currency differences and price changes so the quantity relationship stays visible.

Start with a document-level comparison

Assume a purchase order item requests 100 units at ₹50 per unit. Its ordered value is 100 × ₹50 = ₹5,000. A goods receipt records 60 units, worth ₹3,000 at that example price. The supplier then sends an invoice for 100 units and ₹5,000.

Fictional purchase order, receipt and invoice comparison
DocumentQuantityExample value
Purchase order100 units₹5,000
Goods receipt60 units₹3,000
Supplier invoice100 units₹5,000

The invoice exceeds the recorded received quantity by 100 − 60 = 40 units. At ₹50 each, that difference represents ₹2,000. This establishes a receipt-to-invoice gap; it does not establish that the supplier invoice is fraudulent or that SAP must reject it.

Identify the invoice verification context

Check whether goods-receipt-based invoice verification applies to the purchase order item. This setting affects the relationship between receipts and invoices. Inspect the actual item and the receipt references instead of assuming that every purchase order uses the same verification process.

Also check the applicable tolerance settings and the recorded invoice status. Depending on configuration and circumstances, a discrepancy may produce a message, a payment block, or prevent a particular posting step. A posted invoice that is blocked for payment is a different outcome from an invoice that was not posted. Record which outcome occurred before discussing a remedy.

Reconcile the complete history

  1. Confirm the purchase order item, supplier and material match the invoice.
  2. Compare the order unit, receipt unit and invoice unit, including conversions.
  3. List valid receipts and their reversals rather than adding only positive entries.
  4. Check earlier invoices, credit memos and cancellations for that item.
  5. Read the exact system message and the invoice’s current status.

Prior invoice quantity matters. If an earlier invoice already accounted for 20 units, a new invoice for 100 units is not simply the same comparison as a first invoice for 100. Establish whether the new invoice is incremental, a replacement, or a duplicate, and compare the appropriate cumulative quantities within the configured verification process.

Test two follow-up events

If a later valid receipt records the remaining 40 units, total receipts become 60 + 40 = 100. The original 40-unit receipt gap then closes. The business still needs to review the invoice’s status and any required release process; a new receipt should not be described as an automatic guarantee that every block disappears.

If 10 units of receipt quantity are subsequently reversed, net receipts become 100 − 10 = 90. Against the same 100-unit invoice, the gap is now 10 units, equivalent to ₹500 at the unchanged example price. Keep the reversal document and its reason in the reconciliation.

Resolve the cause with evidence

Possible actions include waiting for a verified delivery, correcting a misposted receipt, requesting a corrected invoice, or following an authorised blocked-invoice review. Choose the action that matches the underlying event. Changing tolerance settings just to make this example pass can hide a genuine control issue and should not be the default troubleshooting step.

Practice question

Build a small ledger containing order quantity, net receipt quantity and net invoice quantity after each event. Explain the 40-unit gap, its closure, and the later 10-unit gap to someone who has not seen the documents. A useful answer names the relevant documents, distinguishes quantity from price differences, and states what evidence is still needed.

Common question: does a partial delivery mean the invoice is wrong?

No. Commercial terms and the supplier’s billing arrangement may explain it. The reconciliation shows what has been ordered, received and invoiced; the purchase agreement and configured process determine the appropriate next step.

Continue learning

SAP MM invoice verification and tolerance checks; SAP FICO–MM purchase-to-pay integration. Explore the linked course page for the current training information.

Leave a Comment

Your email address will not be published. Required fields are marked *