Procurement and End-to-End Procure-to-Pay

MM / P2Pintermediate

MM Procure to Pay Part 2: Document Flow and Control Points

Key takeaway

Where P2P is controlled: approvals of PRs and POs, confirmations, GR-based invoice verification, three-way match, tolerances and invoice blocks, payment blocks and release, GR/IR maintenance — and what each control prevents.

Explanation

📌 KEY POINTS
✅ Approvals control commitments (PR/PO release or flexible workflow).
✅ Three-way match: PO (price/quantity) vs GR (quantity) vs invoice.
✅ GR-based IV ties invoices to specific GRs; tolerances (e.g. PP price, DQ quantity) decide blocks.
✅ Blocked invoices are released in MRBR after checks; GR/IR differences cleared with MR11.
⚠️ Wide tolerances or disabled GR-based IV weaken the whole control chain.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 showed the flow. Now the control points.

━━━━━━━━━━━━━━━━━━━━
▶ 1. APPROVAL

PR/PO release; spending limits.

━━━━━━━━━━━━━━━━━━━━
▶ 2. CONFIRMATIONS AND GR

Confirmation control keys; GR as evidence of receipt.

━━━━━━━━━━━━━━━━━━━━
▶ 3. INVOICE MATCHING

GR-based IV; price and quantity tolerances; blocking reasons.

━━━━━━━━━━━━━━━━━━━━
▶ 4. RELEASE AND PAYMENT

MRBR release; payment blocks; duplicate invoice check.

━━━━━━━━━━━━━━━━━━━━
▶ 5. PERIOD-END

GR/IR analysis and clearing (MR11), accruals.

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

Post a GR of 90 for PO of 100.
Invoice 100 at a higher price; check block.
Release after correction; analyse GR/IR.

✅ CHECKPOINT: you can explain why an invoice is blocked and how to resolve it.

Code example

ABAP Code

===== STEP 1: controls =====Release strategy / flexible workflow (PO) | confirmation control key | GR-based IV flagTolerance keys (OMR6): PP price variance, DQ quantity, BR/BW order price quantity... ===== STEP 2: blocking =====MIRO → blocked for payment (quantity/price) → MRBR release ===== STEP 3: period-end =====MR11 GR/IR clearing | GR/IR analysis reports

Real project scenario

A supplier invoice was blocked for quantity variance every month because deliveries arrived in partial GRs while invoices covered full orders. Enabling GR-based IV and aligning invoicing to deliveries eliminated most blocks; remaining ones were resolved quickly with MRBR.

Common mistakes

Disabling GR-based IV.
Overly wide tolerances.
Releasing blocks without analysis.
Ignoring GR/IR aging.
No duplicate invoice check.

Best practices

Keep three-way match.
Set tolerances with finance.
Analyse block reasons.
Review GR/IR monthly.
Activate duplicate checks.

Interview angle

Questions: "What is three-way match?", "Why is an invoice blocked?", "How is GR/IR cleared?"
Strong answer: approvals, confirmations, GR-based IV, tolerances and blocks, MRBR release, MR11 clearing, duplicate checks.

Practice this lesson

Quick check

1. Which transaction clears residual GR/IR balances where quantities differ permanently?

2. Where are invoices blocked for payment due to variances released?

3. An invoice is blocked for quantity variance each month because deliveries are partial. What helps most?

Interview questions

1. In a catalog procurement setup (e.g., SAP Ariba or open catalog interface), how should output management be configured to ensure PO documents are correctly transmitted to catalog-sourced vendors?

Answer it in your own words first, then compare.

2. Invoices are frequently blocked and paid late. How do you review P2P control points?