MM / P2Pintermediate

MM Invoice Verification Part 5: Blocked Invoices and Release

Key takeaway

Handle blocked invoices: blocking reasons (price, quantity, date, quality, amount, manual), automatic release when reasons disappear, manual release with MRBR, workflow to buyers, payment block handling in FI, and cash discount risk.

Explanation

📌 KEY POINTS
✅ Blocked invoices carry item blocking reasons and payment block R.
✅ MRBR releases invoices automatically (when reasons are resolved, e.g. GR posted) or manually.
✅ Workflows can route blocked invoices to buyers for decisions.
✅ Aging of blocked invoices threatens cash discounts and supplier relations.
⚠️ Releasing invoices manually without resolving the variance pays overcharges.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 4 covered architecture. Now blocks.

━━━━━━━━━━━━━━━━━━━━
▶ 1. BLOCKING REASONS

Price, quantity, date, quality, amount, manual.

━━━━━━━━━━━━━━━━━━━━
▶ 2. AUTOMATIC RELEASE

MRBR with automatic release option (e.g. after GR arrives).

━━━━━━━━━━━━━━━━━━━━
▶ 3. MANUAL RELEASE

After buyer confirmation or PO correction.

━━━━━━━━━━━━━━━━━━━━
▶ 4. WORKFLOW

Notify buyer; decisions: correct PO, request credit memo, accept.

━━━━━━━━━━━━━━━━━━━━
▶ 5. MONITORING

Aging, value, cash discount due dates.

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

Post invoice blocked for quantity (GR missing).
Post GR; run MRBR automatic release.
Release a price-blocked invoice after PO correction.

✅ CHECKPOINT: blocked invoices are resolved before discount deadlines.

Code example

ABAP Code

===== STEP 1: MRBR =====Selection: company code, supplier, blocking reason | processing: automatic release / manual release ===== STEP 2: decisions =====Price block → buyer updates PO price (if valid) → release | or supplier credit memoQuantity block → post missing GR → automatic release ===== STEP 3: monitoring =====Blocked invoices by age/value | discount due date

Real project scenario

A company lost significant cash discounts because blocked invoices waited weeks in AP. Daily automatic release runs, buyer workflows for price blocks and a dashboard by discount date cut average resolution to three days.

Common mistakes

Manual release without analysis.
No automatic release runs.
Buyers not involved.
Ignoring discount dates.
No aging reports.

Best practices

Schedule automatic release.
Route price issues to buyers.
Track discounts.
Document release decisions.
Monitor aging.

Interview angle

Questions: "How do you release blocked invoices?", "What causes quantity blocks?", "How do you protect cash discounts?"
Strong answer: blocking reasons, MRBR automatic/manual, workflows, monitoring and discounts.

Practice this lesson

Quick check

1. Which transaction is typically used to review and release invoices that have been blocked for payment due to price or quantity variances?

2. In Logistics Invoice Verification, what is the primary function of the tolerance key 'PP' (Price Variance) configured in customizing?

3. An invoice posted via MIRO exceeds the configured price tolerance limit. What is the standard system behavior?

Interview questions

1. An EWM-managed warehouse posts goods receipts with quantities that differ slightly from what the PO specifies due to batch splitting at putaway confirmation. This is causing a spike in quantity-blocked invoices in LIV. How would you architect a resolution?

Answer it in your own words first, then compare.

2. Post go-live of an Ariba integration, invoices routed through Ariba are landing in MRBR with a price variance block even though the PO price matches Ariba's catalog price exactly. How do you troubleshoot this cross-system discrepancy?

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.