MRBR — Release Blocked Invoices
MRBR is used to review and release invoices blocked for payment because of price, quantity or tolerance checks. It is most useful when MIRO documents posted but payment is blocked until procurement/receiving differences are resolved. Work from the exact document, organizational level and business date, then verify downstream status or accounting evidence before changing master data or configuration.
This page explains MRBR — Release Blocked Invoices — as a practitioner reference: what it does, when it belongs in the process, the fields that matter, how to prove the result in SAP data, and the mistakes that create the most rework.
Published 19 Sept 2026· 574 words
Purpose
review and release invoices blocked for payment because of price, quantity or tolerance checks. The key is to treat MRBR as one step in an end-to-end process. What users see here is often determined earlier by master data, document status, organizational assignments or configuration, so always capture those inputs before changing the transaction result.
When it is used
MRBR is typically used when MIRO documents posted but payment is blocked until procurement/receiving differences are resolved. It is also valuable in integration and regression testing because the resulting document/status provides objective evidence of whether upstream data and configuration are aligned. Narrow the working population first so any change can be reconciled safely.
How to use it in practice
- Select a focused company/vendor/date population.
- Open the block reason and PO history before releasing.
- Correct missing GR, PO price or invoice data where appropriate.
- Release only when business approval/tolerance conditions are satisfied.
- Confirm the payment block is removed and AP sees the expected item.
Key data objects
These fields and business objects usually explain the result in MRBR. Put them into support tickets and test evidence so another consultant can reproduce the same state instead of working from a generic symptom.
- invoice document — verify the exact value, status, organizational context and date relevance.
- blocking reason — verify the exact value, status, organizational context and date relevance.
- PO item — verify the exact value, status, organizational context and date relevance.
- price/quantity variance — verify the exact value, status, organizational context and date relevance.
- release status — verify the exact value, status, organizational context and date relevance.
How to prove it in the data
Prove the issue through document flow and chronology. Start with the source requirement or document, identify the exact master/configuration keys used, then inspect the generated logistics or accounting document and its status. For quantity issues, reconcile ordered, received, delivered, invoiced and current/historical stock; for value issues, reconcile pricing, account determination and the FI document.
ECC vs S/4HANA
MRBR remains relevant on S/4HANA, although Fiori exception-handling apps may provide alternate workflows. In an S/4HANA program, keep valid GUI transactions as support tools but use the strategic Fiori, workflow, embedded analytics and clean-core integration patterns where they provide the preferred business surface.
Common pitfalls and how to diagnose them
- Releasing every blocked invoice to clear an AP backlog. Check the complete document flow before applying a workaround.
- Ignoring a recurring price variance caused by wrong PO master/contract data. Check the complete document flow before applying a workaround.
- Assuming release changes the invoice accounting values. Check the complete document flow before applying a workaround.
Whose problem this is
Primary ownership sits with MM/P2P depending on the transaction, with Finance joining where accounting is created and EWM/integration teams joining where execution happens outside core ERP. Escalate with document numbers, organizational keys, date, expected result and proven status.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/mrbrERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.