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.
| Document | Quantity | Example value |
|---|---|---|
| Purchase order | 100 units | ₹5,000 |
| Goods receipt | 60 units | ₹3,000 |
| Supplier invoice | 100 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
- Confirm the purchase order item, supplier and material match the invoice.
- Compare the order unit, receipt unit and invoice unit, including conversions.
- List valid receipts and their reversals rather than adding only positive entries.
- Check earlier invoices, credit memos and cancellations for that item.
- 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.
Worked example: an earlier invoice changes the open quantity
Keep the original purchase order for 100 units and the valid receipt for 60 units. Now assume an earlier, valid invoice already covered 20 units. The receipt quantity still available for comparison with a further invoice is 60 − 20 = 40 units. If the next invoice requests 50 units, the excess over that open quantity is 50 − 40 = 10 units, equivalent to ₹500 at the unchanged ₹50 price.
Cumulative invoices would become 20 + 50 = 70 units against 60 units received. The same 10-unit difference appears in both calculations. This cross-check catches a common learner mistake: comparing each new invoice with the full receipt quantity and forgetting what was invoiced earlier. Use only valid, relevant documents and their actual quantity effects; an amount-only adjustment is not automatically a quantity correction.
Distinguish missing delivery from a unit-of-measure mistake
Suppose the supplier’s invoice states six boxes and the purchase order uses individual pieces. If the verified conversion is ten pieces per box, six boxes represent 60 pieces. Comparing the numbers six and 60 without conversion creates a false discrepancy. Write the unit alongside every quantity in the reconciliation and confirm the conversion from the appropriate purchasing and material records.
A price stated per hundred pieces also needs care. ₹5,000 per hundred pieces is equivalent to ₹50 per piece in this example; it is not ₹5,000 for each piece. Separate the order unit from the price unit before multiplying. If the document uses variable weight or another different pricing quantity, investigate that specific relationship instead of imposing a fixed box conversion.
Check the receipt reference when GR-based verification applies
SAP documentation explains that goods-receipt-based invoice verification links invoices to individual receipt references. In a practice system using SAP GUI, inspect the purchase order item’s Invoice tab and purchase order history in ME23N. The available history views and authorizations depend on the system. Record the receipt document, year and item, because the purchase order number alone may not identify the delivery being invoiced.
Consider two receipts of 30 units each. If the first receipt has already been invoiced, a second invoice must be checked against the correct remaining receipt reference. A purchase order total of 60 received units does not prove that a selected receipt still has 60 units available. This distinction becomes particularly useful after cancellations and replacement receipts.
Practical diagnosis checklist before a correction
- Delivery evidence: compare the delivery note and receiving record with the posted receipt. Physically delivered goods and posted goods can differ temporarily.
- Invoice evidence: check supplier invoice number, item description, quantity and unit, then identify whether the document is an additional bill or a replacement.
- Posting evidence: retain material and invoice document references, dates, reversals and the exact message. Do not assume a document was posted because it was entered on screen.
- Resolution evidence: state who will verify the delivery, correct the relevant document or review the block. Recalculate the quantities after that action.
Frequently asked questions about partial receipts
Does a zero invoice balance prove the quantities match?
No. A balanced entry does not establish that its quantity agrees with the relevant receipt history. Check invoice entry balance, quantity comparison and payment-block status as separate facts.
Can one invoice have both quantity and price differences?
Yes. Check quantity against the appropriate open quantity and price against the applicable purchasing basis separately. Fixing a missing receipt may leave a price issue unresolved.
Why does another system show a different message?
System messages, tolerances, document references and verification settings can differ. SAP documents configurable behaviour for quantity discrepancies. Record the actual settings and message in the training system rather than expecting one screenshot to describe every installation.
Official SAP references
Consult the documentation for your installed edition and release; screen availability and configured behaviour can differ.
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.