Invoice Verification, GR/IR, Integration and Production Support

MM / P2Padvanced

MM LIV Integration and Support Part 3: GR/IR Reconciliation and Invoice Production Support

Key takeaway

Run production support for invoices: common incidents (blocked invoices, duplicate warnings, tax errors, IDoc invoice failures, GR/IR differences), triage runbooks, monthly GR/IR reconciliation with MR11 and regrouping, and KPIs for AP and procurement.

Explanation

📌 KEY POINTS
✅ Typical incidents: blocked invoices, duplicate invoice warnings, tax code errors, failed inbound invoice IDocs, GR/IR differences.
✅ Runbooks speed up triage: symptom → check → fix → prevention.
✅ Monthly GR/IR reconciliation: analyse, correct, clear with MR11, regroup at period-end.
✅ KPIs: blocked invoice aging, first-pass match, GR/IR aged balance.
⚠️ Fixing individual invoices without process fixes creates endless tickets.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 covered analysis. Now support routines.

━━━━━━━━━━━━━━━━━━━━
▶ 1. INCIDENT TYPES

Blocks, duplicates, tax, IDoc errors, GR/IR.

━━━━━━━━━━━━━━━━━━━━
▶ 2. RUNBOOKS

Checks and fixes per incident type.

━━━━━━━━━━━━━━━━━━━━
▶ 3. IDOC INVOICES

Status monitoring, reprocessing after master data fix.

━━━━━━━━━━━━━━━━━━━━
▶ 4. MONTH-END

GR/IR reconciliation, MR11, regrouping, accruals.

━━━━━━━━━━━━━━━━━━━━
▶ 5. KPIS AND PREVENTION

Trend analysis, root causes, training.

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

Build a runbook for top five incidents.
Set up a monthly GR/IR routine.
Report KPIs.

✅ CHECKPOINT: recurring incidents decline month over month.

Code example

ABAP Code

===== STEP 1: runbook examples =====Blocked invoice → MRBR reason → GR missing? price? → ownerIDoc invoice error → WE02 status → master data/PO fix → reprocess (BD87)Tax error → tax code/jurisdiction check ===== STEP 2: month-end =====GR/IR analysis → corrections → MR11 → regrouping → accrual review ===== STEP 3: KPIs =====Blocked invoices > 30 days | touchless rate | aged GR/IR value

Real project scenario

A support team handled hundreds of blocked-invoice tickets monthly. Trend analysis showed 60% were quantity blocks due to late GR posting at one warehouse. Fixing GR discipline there cut tickets dramatically.

Common mistakes

No runbooks.
No trend analysis.
Manual IDoc fixes without root cause.
Skipping monthly reconciliation.
No KPIs.

Best practices

Document runbooks.
Analyse trends.
Fix master data at source.
Reconcile monthly.
Report KPIs.

Interview angle

Questions: "What invoice incidents do you handle in support?", "How do you run GR/IR reconciliation?", "How do you reduce tickets?"
Strong answer: incident types, runbooks, IDoc handling, month-end routine, KPIs and prevention.

Practice this lesson

Quick check

1. Which KPI best shows invoice processing health?

2. What is the right approach to aged GR/IR balances?

3. Most blocked-invoice tickets come from quantity blocks at one warehouse. What is the best fix?

Interview questions

1. An internal audit flags that several vendor invoices were posted and paid with vendor master bank detail changes made by the same AP clerk on the same day as invoice entry. How would you assess and remediate the control gap?

Answer it in your own words first, then compare.

2. 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?