Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

A payment proposal is a proposed selection of items for payment. It is a review stage, not proof that money has been sent to the supplier.

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 proposal created: Why that does not mean the supplier was 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.

Classic automatic-payment program and S/4HANA Manage Automatic Payments concepts. Bank integration, payment formats and settlement evidence depend on the deployed process.

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

Verify whether a component supplier was paid

A proposal is not a bank payment

Invoice selected: Yes. Payment proposal: Created. Payment execution: Not yet established. Bank outcome: Separate evidence
What to notice: Do not report a supplier as paid solely because an item appears in a proposal.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Invoice selected
Yes
Payment proposal
Created
Payment execution
Not yet established
Bank outcome
Separate evidence
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.

Eligible invoices → Payment proposal → Execution evidence. Conceptual diagram for SAP payment proposal created: Why that does not mean the supplier was paid.
Apply the idea: A buyer tells a critical supplier that its invoice appeared in a payment proposal, while the supplier still asks for payment confirmation.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. Verify whether a component supplier was paid

    A buyer tells a critical supplier that its invoice appeared in a payment proposal, while the supplier still asks for payment confirmation.

  2. A proposal is a candidate selection, not proof of money movement

    A payment proposal identifies items and proposed payments for review under the run’s parameters and controls.

  3. Read the run identity and stage together

    Record run date, identification, paying/company-code scope, creator and displayed proposal/payment status.

  4. Worked case: three invoices, two proposed payments

    Fictional run PAY14 for company 1000 considers supplier S100 invoice I1 for 1,000 EUR, S200 invoice I2 for 600 EUR and S300 invoice I3 for 400 EUR.

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.