Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

A payment block prevents an item from being paid through the affected payment process. An invoice can therefore exist in accounting while payment still requires a separate decision.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

Financial Accounting records business events as accounting documents. An account groups relevant amounts; individual entries explain how the total arose.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for SAP payment blocks: Why an invoice can be posted but not paid
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

SAP ERP and supported S/4HANA payment-block concepts, with Logistics Invoice Verification source/release reasoning. Direct FI reasons, manual payments and cloud applications require their own configuration scope.

Reviewed relevant official SAP indexed documentation excerpts on 14 November 2026. Examples, identifiers, amounts and expected observations are illustrative; no customer SAP execution was performed. Transaction availability, labels and results depend on the installed release, deployment and local configuration.

A MANUFACTURING EXAMPLE

Investigate an unpaid component invoice

Posted is not necessarily payable

Invoice document: Posted. Payment block: Active. Amount owed: Still recorded. Payment eligibility: Requires separate review
What to notice: A payment block can restrict payment without undoing the invoice’s accounting posting.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Invoice document
Posted
Payment block
Active
Amount owed
Still recorded
Payment eligibility
Requires separate review
Words you’ll meet in this guide
Posting
Recording a financial entry.
General ledger
The main collection of financial accounts.
Open item
An accounting entry still needing matching or settlement.
Company code
An organizational unit used for separate financial accounts.
Accounting document
A record of a financial entry with a header and individual account lines.
HANA
SAP’s database platform.
FI
Financial Accounting: the SAP area for financial postings and reporting.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Posted invoice → Payment-block status → Payment eligibility. Conceptual diagram for SAP payment blocks: Why an invoice can be posted but not paid.
Apply the idea: A component invoice is posted in the manufacturer's system, but treasury cannot include it in the intended payment process.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Investigate an unpaid component invoice

    A component invoice is posted in the manufacturer's system, but treasury cannot include it in the intended payment process.

  2. Posted and eligible for payment are separate states

    A supplier invoice can be posted in accounting while a payment block prevents payment through the affected process.

  3. Identify the source and reason of the block

    SAP documents automatic and manual invoice blocks, including variance, item-amount and stochastic reasons in Logistics Invoice Verification.

  4. Worked case: invoiced quantity exceeds received quantity

    Fictional PO item 10 orders 100 pieces at 10 EUR each.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.