MRBR: Release Blocked Invoices in SAP

โšก Smart Summary

Release an Invoice in SAP using transaction MRBR. A blocked invoice cannot be paid until the block is lifted, and MRBR clears manual payment blocks as well as blocks raised by variance during invoice verification.

  • ๐Ÿ”“ Core Transaction: MRBR releases blocked invoices; the block itself is set during invoice verification in MIRO.
  • ๐Ÿข Selection Entry: Company code plus invoice number narrows the worklist to the document being processed.
  • โš™๏ธ Two Release Methods: Manual release lets the user pick documents; automatic release clears only blocks whose cause has disappeared.
  • ๐Ÿšฉ Green Flag Status: A green flag in the status column confirms the invoice has been passed to Financial Accounting.
  • ๐Ÿ’ฐ Payment Effect: Once released, the finance department sees the document as ready for the next payment run.
  • โš ๏ธ Naming Trap: Automatic release in MRBR is unrelated to automatic blocking in MIRO, despite the similar wording.

Release blocked invoices in SAP using MRBR

Why Invoices Get Blocked in SAP

Invoice verification compares three documents: the purchase order, the goods receipt, and the vendor invoice. When they disagree beyond the configured tolerance, SAP still posts the invoice but sets a payment block so money cannot leave until someone reviews it.

The block is therefore a control, not an error. Understanding which check raised it tells you whether releasing is appropriate or whether the underlying document needs correcting first.

Block reason What triggered it Usual resolution
Price variance Invoice price differs from the purchase order price beyond tolerance Correct the order price, or accept and release
Quantity variance Invoiced quantity exceeds the quantity received Post the missing goods receipt, then release
Date variance Delivery arrived later than the scheduled date Review with the buyer, then release
Quality inspection block Material is still in quality inspection stock Complete the usage decision, then release
Manual payment block A user set the block deliberately in MIRO Release manually once the query is settled
Stochastic block Random sampling selected the invoice for audit Review and release; no document is wrong

Quantity variance is the most common of the six and almost always means the goods receipt has not been posted rather than that the vendor over invoiced.

How to Release Blocked Invoices

An invoice request is blocked for payment until it is manually released. You can release the invoice by using t-code MRBR.

Step 1)

  1. Execute t-code MRBR.
  2. On the initial screen enter the company code and invoice number.
  3. Check the release method (release manually if you want to process it in the second screen). This can be done choosing Automatically (please note the difference with automatic release in MIRO transaction being blocked and automatic release in t-code MRBR as those are two different things).
  4. Our document has a manual payment block, so we will select that option. Execute.

Release Blocked Invoices in SAP

Step 2)

  1. Select the invoice you want to release.
  2. Click on the flag icon – release.

Release Blocked Invoices in SAP

You can see that now the invoice has Status field filled with green flag โ€“ it means, it is released to FI.

Release Blocked Invoices in SAP

Financial department should now be able to see the invoice ready for payment.

Manual Release vs Automatic Release in MRBR

The selection screen offers two release methods and they behave very differently. Choosing the wrong one is why an expected invoice sometimes fails to appear in the worklist.

Parameter Release manually Release automatically
What it does Lists blocked invoices for the user to select and flag Scans blocked invoices and clears those whose block reason no longer applies
User decision needed Yes, per document No, the system decides
Clears a manual payment block? Yes No, a manual block always needs a person
Typical use Reviewing genuine price or quantity disputes Nightly job after goods receipts have caught up
Run as background job Not practical Yes, this is the normal setup

โš ๏ธ Warning: Automatic release in MRBR and automatic blocking in MIRO are unrelated settings despite the similar names. Automatic release only removes a block whose cause has genuinely gone; it never overrides a manual payment block set by a user.

Invoice Verification Transaction Codes

MRBR sits at the end of the invoice verification chain. The table lists the transactions that surround it.

Transaction Code Purpose
MIRO Enter an incoming invoice against a purchase order
MIR7 Park an invoice for later completion or approval
MIRA Background invoice verification for high volume processing
MIR4 Display or change an invoice document
MIR5 Display a list of invoice documents
MIR6 Invoice overview with selection by status and block
MRBR Release blocked invoices
MR8M Cancel a posted invoice document
MR11 Clear GR/IR account differences after the process closes

Where the invoice itself is wrong rather than merely blocked, cancelling with MR8M and re-entering is cleaner than releasing and correcting afterwards. Where the purchase order carried the wrong price, fix it in change purchase order and update the purchase info record so the next invoice matches automatically. The wider process is mapped in the SAP MM tutorial series.

FAQs

Open the invoice in MIR4 and check the item list. Blocked lines carry a blocking reason indicator that names the variance, or the header shows a manual payment block instead.

Yes, by setting the payment block field on the accounting document in Financial Accounting. MRBR itself only releases; it does not reinstate a block once cleared.

AI reads incoming invoices, matches them to orders and receipts before posting, and flags mismatches at entry. Fewer documents reach MIRO with a variance, so fewer blocks are raised.

Yes. Models rank blocked documents by risk using variance size, vendor history, and past release decisions, so accounts payable reviews the exceptions rather than the whole queue.

No. Release only removes the payment block. The document is then picked up by the next payment run according to its payment terms and baseline date.

Summarize this post with: