Direct answer

In SAP FI, the Automatic Payment Program identifies eligible open customer or supplier items according to run parameters and payment configuration, creates a payment proposal for review, and then executes the approved payment run. Depending on the setup, payment media can be created after the run for transmission through the organization’s banking process.

Why the proposal matters

The proposal is a control point, not merely a preview. It shows which items the system intends to pay and exposes exceptions before money moves. SAP’s Manage Automatic Payments app supports scheduling proposals or payments directly, and the automatic scheduling documentation identifies parameters such as company code, payment method, run date, next posting date and document-selection dates.

What makes an item eligible

Eligibility is shaped by more than due date. Payment terms, payment methods, company-code settings, business-partner master data, payment blocks, available bank information and run parameters can all influence whether an open item is selected or excluded. The payment run should therefore be understood as the outcome of configured rules plus current transaction data.

PAYMENT OPERATIONS REVIEWAP analystProposal exceptionsBlocked item · missing methodbank detail · timing issueResolve before run
A disciplined payment team reviews exclusions and unusual selections before converting a proposal into an executed payment run.

From proposal to payment

Once the proposal is reviewed and issues are resolved, the payment run posts the payment documents. SAP documentation also supports automatic creation of payment media after scheduling a payment run, while some landscapes use additional approval or bank-communication controls before the final outbound file is released.

Consultant checks

Test the intended payment methods, company codes, due-date logic, payment blocks, supplier bank data, discount timing and exception logs. Also test a proposal containing both valid and invalid items so users understand why one item is selected while another is not. The strongest design separates configuration, proposal review, payment execution and bank release responsibilities where the organization’s control model requires it.

AUTOMATIC PAYMENT RUN LIFECYCLE1. Parametersscope & dates2. Proposalcandidate items3. Reviewexceptions4. Runpost + media
The proposal stage is where payment selection becomes reviewable before execution changes accounting and creates downstream payment output.

Continue with Payment Blocks and Release Controls, Payment Terms and Baseline Dates, Cash Discount Processing and the SAP FI / FICO hub.

Official SAP References