MM / P2Padvanced

MM Goods Receipt and Goods Issue Part 4: GR/IR, Stock Valuation and Financial Impact

Key takeaway

Understand the money side of goods movements: GR postings to stock and GR/IR, price differences with standard price, account-assigned and non-valuated receipts, GR/IR clearing with invoices, analysis of GR/IR balances and period-end maintenance.

Explanation

📌 KEY POINTS
✅ GR for PO: Dr stock (BSX) / consumption, Cr GR/IR (WRX) at PO price.
✅ With standard price, differences between PO price and standard go to price difference (PRD).
✅ The invoice clears GR/IR; remaining balances show quantity or price mismatches.
✅ Non-valuated GR (e.g. for account-assigned items with that indicator) posts value only at invoice.
⚠️ Old GR/IR balances misstate liabilities — analyse and clear (e.g. MR11) regularly.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 3 covered issues. Now valuation and GR/IR.

━━━━━━━━━━━━━━━━━━━━
▶ 1. GR POSTINGS

S price: stock at standard, difference to PRD. V price: stock at PO price.

━━━━━━━━━━━━━━━━━━━━
▶ 2. GR/IR

Credit at GR, debit at invoice; balance = received not invoiced or invoiced not received.

━━━━━━━━━━━━━━━━━━━━
▶ 3. NON-VALUATED GR

GR without value; IV posts to consumption.

━━━━━━━━━━━━━━━━━━━━
▶ 4. ANALYSIS

GR/IR per PO item; causes: missing invoice, quantity difference, price difference.

━━━━━━━━━━━━━━━━━━━━
▶ 5. MAINTENANCE

MR11 GR/IR clearing maintenance; period-end regrouping (per finance process).

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

Post GR at 11.00 for material with standard 10.00.
Post invoice at 11.00.
Check GR/IR and PRD.

✅ CHECKPOINT: GR/IR is zero for the item and differences are explained.

Code example

ABAP Code

===== STEP 1: GR (standard price 10.00, PO 11.00, 100 PC) =====Dr BSX 1,000 | Dr PRD 100 | Cr WRX 1,100 ===== STEP 2: invoice =====Dr WRX 1,100 | Dr input tax | Cr supplier ===== STEP 3: maintenance =====GR/IR analysis per PO | MR11 clear small/closed differences (with approval)

Real project scenario

Finance found a persistent GR/IR balance on a PO for months. The supplier had invoiced a lower quantity than received and never sent a final invoice. After confirming with the supplier, the team set final invoice and cleared the difference with MR11, and introduced monthly GR/IR reviews with buyers.

Common mistakes

Ignoring GR/IR balances.
Clearing without analysis.
Not setting final invoice.
Misunderstanding PRD.
Non-valuated GR used wrongly.

Best practices

Review GR/IR monthly.
Analyse by cause.
Clear with approvals.
Explain price differences.
Align buyers and AP.

Interview angle

Questions: "What happens in FI at GR?", "What is GR/IR?", "How do you clean GR/IR?"
Strong answer: BSX/WRX/PRD postings with S/V, GR/IR mechanics, non-valuated GR, analysis and MR11 maintenance.

Practice this lesson

Quick check

1. A purchase order is configured with the GR-based invoice verification indicator active. What is the direct effect of this setting on the subsequent invoice posting process?

2. A PO has a GR/IR balance for months because the supplier invoiced less than received and won't invoice more. What is the right action?

3. After several goods receipts have been posted against a purchase order but before the vendor invoice arrives, what does a credit balance on the GR/IR clearing account for that PO item represent?

Interview questions

1. Finance reports large, old GR/IR balances and unexplained price differences. How do you analyse and clean them up?

Answer it in your own words first, then compare.

2. A physical inventory count at a distribution center reveals significant unexplained stock differences concentrated in materials with open GR/IR balances. As the solution architect, how would you determine whether the discrepancy is a physical count issue or a GR/IR clearing problem masking real inventory quantities?

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.