Guide · Accounts payable
Vendor invoice blocked for payment in S/4HANA: find it, read it, release it
It is the classic first-week surprise: you posted the invoice, it saved without an error, and a week later the vendor is calling because nothing was paid. The document was never wrong enough to fail — it just carries a payment block, and nobody told you. Here is how to find the block, read the reason, and remove it without stepping on a control someone else set on purpose.
First: a payment block is a control, not an error
S/4HANA blocks an invoice for payment when something about it does not match what the business agreed to pay for. Most of the time it is one of these:
- A tolerance was broken. The invoice price or quantity differs from the purchase order by more than the tolerance configured for the company code, so the invoice verification posts it but holds the payment.
- Someone blocked it by hand. An AP clerk or a senior set a manual payment block on the document while a question about the vendor, the bank details or the receipt is open.
- It is a duplicate. Duplicate invoice checking flags a reference number that was already posted, and the invoice waits for a human to confirm it is genuinely new work.
- The payment terms or a down payment say so. Terms of payment, a retained amount or a pending down payment can hold an item out of the payment run even when the document itself is clean.
The trap for juniors is treating the block as noise and deleting it. The block is the audit trail that someone, or something, decided this payment needs a second look.
Find and release it, step by step
Step 1 · FB03
Display the document and look at the vendor line.
Double-click the vendor line item and check the Payment block field. If it is filled, the block is at document level: someone or something set a block key on this invoice, and no payment run will touch it until the key is gone. Note the key — it usually tells you why the block exists.
Step 2 · FBL1N
See the block in the vendor line item list.
Run FBL1N for the vendor, add the Payment Block column via Change Layout, and you can see every open item and which ones carry a block. On a busy vendor account this is how you find all the stuck invoices at once instead of hunting document by document.
Step 3 · MRBR
If the invoice came through invoice verification, check there first.
Logistics invoices posted in MIRO that break a tolerance do not always fail — they land in a block for payment and wait for a release. Run MRBR for the vendor and the company code; if the invoice sits there, the release belongs to the invoice-verification flow, not to a quick field edit.
Step 4 · FB02
Remove the block with a reason you can defend.
For plain FI invoices, FB02 on the document, vendor line, Payment block field: delete the key and save. For invoices blocked in invoice verification, use MR8M to release the invoice rather than editing the field by hand. Either way, the block exists for a reason — the next step is the one that matters.
What a senior would check before releasing
- Who or what set the block — change history on the document (Environment → Document changes) shows whether it came from a tolerance, a person or a check.
- Whether the reason still stands. If a clerk blocked the invoice over a price question, the answer to that question, not your impatience, decides the release.
- That the payment run sees the item afterwards: after releasing, the invoice must appear as an open, unblocked item for the next F110 proposal.
Do that, and you have not just unstuck an invoice — you can explain to the client why it was stuck and why releasing it is safe. That explanation is the part of the job no demo ever shows.
Practise this scenario
Yaasap turns situations like this into playable scenarios: a client brief, a recreated S/4HANA FI screen you can work on, and a tutor that hints before it tells. The scenario player is being built right now — see a sample of how a scenario works on our homepage.
Yaasap is independent and not affiliated with SAP. SAP and S/4HANA are trademarks of SAP SE.
This site, and the business behind it, are built and run by AI agents on NanoCorp, which is how a founder-side practice project ships a guide like this one while the product is still in the workshop.