MM / P2Padvanced

MM Invoice Verification Part 6: GR/IR Reconciliation, Invoice Reduction and Subsequent Debits/Credits

Key takeaway

Resolve differences properly: invoice reduction when suppliers overcharge, subsequent debits/credits for price changes without quantity, credit memos for returns, GR/IR analysis and clearing (MR11), and period-end regrouping of GR/IR.

Explanation

📌 KEY POINTS
✅ Invoice reduction posts the correct amount and creates a supplier credit note request for the difference.
✅ Subsequent debit/credit adjusts value without changing quantity (e.g. later price increase).
✅ Credit memos reduce quantity and value (e.g. returns).
✅ GR/IR maintenance (MR11) clears remaining differences after analysis; finance regroups GR/IR at period-end.
⚠️ Using credit memos for pure price corrections distorts invoiced quantities.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 5 covered blocks. Now differences.

━━━━━━━━━━━━━━━━━━━━
▶ 1. INVOICE REDUCTION

MIRO reduction layout; complaint document to supplier.

━━━━━━━━━━━━━━━━━━━━
▶ 2. SUBSEQUENT DEBIT/CREDIT

Value-only adjustments; valuation effect depends on stock coverage.

━━━━━━━━━━━━━━━━━━━━
▶ 3. CREDIT MEMOS

Quantity and value reversal (returns, overbilling).

━━━━━━━━━━━━━━━━━━━━
▶ 4. GR/IR ANALYSIS

Open items per PO; causes and owners.

━━━━━━━━━━━━━━━━━━━━
▶ 5. CLEARING AND REGROUPING

MR11 after approval; period-end regrouping of GR/IR balances.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Post an invoice with reduction.
Post a subsequent debit.
Clear an old GR/IR difference.

✅ CHECKPOINT: every GR/IR balance has an owner, cause and resolution.

Code example

ABAP Code

===== STEP 1: invoice reduction =====MIRO: supplier invoiced 1,200, correct 1,000 → reduce 200 → complaint output ===== STEP 2: subsequent debit/credit =====MIRO transaction: subsequent debit → value only, quantity unchanged ===== STEP 3: GR/IR =====Analysis per PO | MR11 clearing (approval) | period-end regrouping (finance process)

Real project scenario

During year-end close, a manufacturer found GR/IR balances where AP had used credit memos for price corrections, leaving invoiced quantities below received. Correcting with subsequent credits and clearing remaining differences restored consistent PO histories.

Common mistakes

Credit memos for price only.
Paying overcharges instead of reducing.
Clearing GR/IR blindly.
No owner for differences.
Ignoring regrouping.

Best practices

Use the right document type.
Use invoice reduction.
Analyse before MR11.
Assign owners.
Reconcile monthly.

Interview angle

Questions: "Invoice reduction vs credit memo?", "What is a subsequent debit?", "How do you clean GR/IR?"
Strong answer: reduction, subsequent debit/credit, credit memo use, GR/IR analysis and MR11, regrouping.

Practice this lesson

Quick check

1. What is the risk of manually releasing price-blocked invoices without buyer review?

2. At year-end, GR/IR shows differences because AP used credit memos for price corrections. What is the consequence?

3. What is the main distinction between a subsequent debit/credit and a standard credit memo in Invoice Verification?

Interview questions

1. An invoice includes both planned freight charges already estimated on the PO and an unplanned customs duty charge added at invoice entry. Post-invoice, the tax amount posted doesn't match what finance expected, and GR/IR shows a residual balance. How would you troubleshoot this?

Answer it in your own words first, then compare.

2. During month-end GR/IR reconciliation, you find an invoice was blocked as a duplicate, but the vendor insists it's a legitimate separate delivery tied to an SD-driven return-and-replace scenario. How do you investigate and resolve this?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.