Automatic Payment Program Run F110: SAP Tutorial

โšก Smart Summary

The Automatic Payment Program, run with transaction F110 in SAP, selects due invoices and posts payments for vendors and customers. It automates invoice selection, payment document posting, and payment media output for national and international transactions.

  • ๐Ÿงพ Payment Steps: Invoices are entered, analyzed for due date, reviewed, approved, and paid.
  • โš™๏ธ Configuration: F110 configuration covers company codes, payment methods, and bank selection.
  • ๐Ÿฆ Bank Selection: Ranking order, amounts, accounts, charges, and value dates control which bank pays.
  • ๐Ÿ“… Parameters: A run is identified by run date and identification, with documents, methods, and company codes.
  • ๐Ÿ“‹ Proposal: The proposal lists payments; you review the log and edit or block items before running.
  • ๐Ÿš€ Payment Run: Starting the run posts payment documents and can generate payment media or EDI.
  • ๐Ÿค– Automation: AI adds anomaly detection and cash-flow forecasting on top of the automated run.

SAP Automatic Payment Run F110

Automatic Payment Program Run F110

Introduction
The Payment Process includes the Following Steps

  1. Invoices are Entered
  2. Pending Invoices are analyzed for due date
  3. Invoices due for payment are prepared for review
  4. Payments are approved or modified
  5. Invoices are paid

A consistently high volume of invoices have to be processed. Accounts Payable Invoices have to be paid on time to receive possible discounts. The Accounting department wishes to perform this processing of invoices automatically. The Automatic Payment Program is a tool that will help users manage payables. SAP gives users the options to automatically:

  1. Select Open(Pending) Invoices to be paid or collected
  2. Payment Documents to be posted
  3. Print Payment Media or generate EDI

The Automatic Payment Program has been developed for both national and international payment transactions with vendors and customers, and handles both outgoing and incoming payments. Configuration We can configure the Payment Program by selecting the Payment Program (Tcode – F110) Application menu Environment -> Maintain Config

Automatic Payment Program Run F110

The Settings for Automatic Payment program are divided into following Categories :

  1. All Company Codes
  2. Paying Company Codes
  3. Payment Methods / Country
  4. Payment Methods / Company Codes
  5. Bank Selection
  6. House Banks

Customizing: Maintain Payment Program

All Company Codes : In this section we perform the following settings

  1. Inter Company Payment Relationship
  2. The Company codes that process payments
  3. Cash Discounts
  4. Tolerance days for Payments
  5. The Customer and Vendor Transactions to be Processed

Change View 'Company Codes'

Change View 'Company Codes'

Paying Company codes : In this section we perform the following settings

  1. Minimum Amounts for Incoming and Outgoing Payments
  2. Bill of Exchange Parameters
  3. Forms for Payment Advice and EDI

Change View 'Paying Company codes'

Change View 'Paying Company codes'

Payment Method / Country : In this section we perform the following settings

  1. Methods of Payments – Cheques, bank transfers etc.
  2. Settings for individual Payment Methods –
    1. Master record requirements
    2. Document Types for Posting
    3. Permitted currencies
    4. Print Programs

Change View 'Payment Method / Country'

Change View 'Payment Method / Country'

Payment Method / Company Code: In this section we perform the following settings

  1. Minimum and maximum payment amounts
  2. Whether payments abroad and foreign currencies are allowed
  3. Grouping Options
  4. Bank Optimization
  5. Forms for payment media

Change View 'Payment Method / Company Code'

Change View 'Payment Method / Company Code'

Bank Selection :

  1. Ranking Order
  2. Amounts
  3. Accounts
  4. Charges
  5. Value Dates

Display View 'Bank Selection'

Bank Selection : Ranking Order

Ranking Order

Bank Selection : Bank Accounts

Bank Accounts

Bank Selection : Available Amounts

Available Amounts

Bank Selection : Value Dates

Value Dates

Bank Selection : Expenses / Charges

Expenses / Charges

Execution : After Configuration of the Payment Process we will enter parameters to execute the program. Enter the Transaction code F110 in the SAP Command Field

Execution Payment Program Run F110 in SAP

Every Payment Program run is identified by two fields

  1. Run date
  2. Identification

Execution Payment Program Run F110 in SAP

In the Parameters Tab, We have to define the following

  1. What is to be paid – Docs. Entered Up to
  2. What payment methods will be used – Payment Methods
  3. When will the payments be made – Posting Date
  4. Which company codes will be considered – Company Codes
  5. How are they going to be paid – Payment Method Sequence decides the Priority of the Payment Method

Automatic Payment Transaction:Parameters

Save the Parameters Entered

Automatic Payment Transaction:Parameters

After the Parameters are Entered we execute the Program by pressing the proposal button in Application Toolbar

Automatic Payment Transaction:Parameters

In the next dialog box, Check the “Start Immediately” and press Continue

Automatic Payment Transaction:Parameters

A payment proposal is generated based on the parameters.

Automatic Payment Transaction:Status

We can view the Proposal Log for possible errors by Pressing the Proposal Log Button

Automatic Payment Transaction:Status

We can edit the proposal to block the some payments if we want, Press the Edit Proposal Button

Automatic Payment Transaction:Status

In the next screen, the Proposal List of Vendors is generated who are to receive the Payments

Automatic Payment Transaction:Status

After edit the Proposal, and then run the payment run to release the payments. We can schedule the payment run by coming back to main screen pressing the Payment Run button

Automatic Payment Transaction:Status

In the next Dialog box, Check “Start Immediately” to start the payment run instantly and Press continue

Automatic Payment Transaction:Status

We can check the status of the Payment run on the Status Tab

Automatic Payment Transaction:Status

Best Practices for the Automatic Payment Run

A disciplined F110 process protects cash and prevents duplicate or wrong payments. Apply these best practices:

  • Always review the proposal: Check the proposal log for errors before posting payments.
  • Use test parameters: Validate configuration in a test client before a live run.
  • Block disputed items: Edit the proposal to block payments that are in dispute.
  • Control run identification: Use a clear run date and identification to trace each run.
  • Schedule carefully: Run payments after due-date analysis to capture cash discounts.

Common F110 Errors and Troubleshooting

Most payment-run problems appear in the proposal log. Typical issues and fixes include:

  • No valid payment method: Check the vendor master and payment-method configuration.
  • House bank not found: Confirm bank selection and available amounts are maintained.
  • Items not selected: Verify the posting date, document date, and company codes in parameters.
  • Blocked for payment: Remove the payment block on the relevant open items.

FAQs

The transaction code is F110. It runs the Automatic Payment Program, which selects open items, creates a payment proposal, and posts payment documents for vendors and customers.

A payment proposal is a preview of the payments the program intends to make, based on your parameters. You review, edit, or block items in the proposal before releasing the actual payment run.

After saving parameters and reviewing the proposal, press the Payment Run button, select Start Immediately or a scheduled time, and continue. SAP then posts the payments and updates the run status.

Yes. AI tools forecast cash needs, recommend the best payment timing to capture discounts, and detect unusual payments. They complement F110 by adding predictive and anomaly-detection capabilities.

artificial intelligence analyzes vendor, bank, and amount patterns to flag duplicate or suspicious payments before they post, strengthening controls around the automatic payment run.

Summarize this post with: