Invoice Verification, GR/IR, Integration and Production Support

MM / P2Padvanced

MM LIV Integration and Support Part 2: GR/IR Open Items, Timing and Root-Cause Analysis

Key takeaway

Understand why GR/IR balances exist: timing (GR before invoice or vice versa), quantity differences, price differences, missing final invoice or delivery completed flags, wrong account assignment, and cancelled documents — and how to classify balances by cause and owner.

Explanation

📌 KEY POINTS
✅ Credit GR/IR balance = received not invoiced; debit = invoiced not received.
✅ Normal timing differences clear themselves; aged items indicate real issues.
✅ Common causes: missing invoice/GR, quantity or price differences, no final invoice, cancelled documents.
✅ Classify balances by cause and assign owners (buyer, receiving, AP).
⚠️ Mass clearing without root-cause analysis hides recurring process failures.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 covered integration. Now GR/IR analysis.

━━━━━━━━━━━━━━━━━━━━
▶ 1. BALANCE MEANING

Received not invoiced vs invoiced not received.

━━━━━━━━━━━━━━━━━━━━
▶ 2. TIMING

Month-end cut-off; accrual meaning.

━━━━━━━━━━━━━━━━━━━━
▶ 3. CAUSES

Quantity/price differences; missing documents; flags.

━━━━━━━━━━━━━━━━━━━━
▶ 4. AGING AND CLASSIFICATION

Buckets (0–30, 31–90, >90 days) per cause.

━━━━━━━━━━━━━━━━━━━━
▶ 5. OWNERSHIP

Buyer, warehouse, AP responsibilities.

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

List GR/IR items per PO.
Classify by cause and age.
Assign owners and actions.

✅ CHECKPOINT: aged balances have cause, owner and target date.

Code example

ABAP Code

===== STEP 1: analysis =====GR/IR analysis by PO item (e.g. Fiori GR/IR monitoring apps / reports per release) | FBL3N GR/IR account ===== STEP 2: classification =====Timing | quantity difference | price difference | missing final invoice | cancelled/reversed documents ===== STEP 3: actions =====Request invoice/credit | post GR | set final invoice/delivery completed | MR11 after approval

Real project scenario

A large aged GR/IR balance was traced to a supplier who invoiced consolidated monthly amounts against the wrong PO lines. Clarifying invoicing instructions and reallocating invoices cleared most of the balance.

Common mistakes

Mass clearing.
No aging.
No owners.
Ignoring flags.
Treating timing as errors.

Best practices

Age and classify.
Assign owners.
Fix processes.
Clear with approval.
Report monthly.

Interview angle

Questions: "Why do GR/IR balances occur?", "How do you analyse them?", "Who owns resolution?"
Strong answer: balance meaning, timing vs errors, causes, aging, ownership.

Practice this lesson

Quick check

1. A supplier invoices consolidated amounts against the wrong PO lines. What is the effect?

2. Which document posts the credit to the GR/IR account in a standard PO process?

3. Which flag prevents a PO item from expecting further invoices?

Interview questions

1. A production issue is reported in Invoice Verification, GR/IR, Integration and Production Support around GR/IR Reconciliation: Open Items, Timing and Root-Cause Analysis. How would you troubleshoot it systematically and avoid the common failure patterns?

Answer it in your own words first, then compare.

2. You inherit an existing Invoice Verification, GR/IR, Integration and Production Support implementation covering Logistics Invoice Verification: PO, GR, Invoice and Tolerance Controls. What would you review before changing it, and what would make you confident the change is production-ready?