Page tree
Skip to end of metadata
Go to start of metadata

Automatic Payment Run

For each company code using the payment program, certain basic specifications must be in place.

Since the payment program can be used for more than one company code, you must also specify the company code that is making the payment.

Detail Steps are as follows.

  •  House Bank Configuration - FI12.
  • Payment Program Configuration - FBZP
  • Define Check numbers - FCHI and Void Reasons - FCHV
  • Payment Run - F110

To control the payment program, you must specify the following in advance:

  • How payment requests are selected and, if necessary, grouped together for one payment
  • The payee
  • How the payment method is selected
  • How the bank is selected
  • Which forms and other data carriers are used
    You make these specifications when:
  • Configuring the payment program
  • Entering data in the master records of your business partner
  • Entering data in the payment requests
  • Entering data for the payment run in hand
     When configuring the payment program, you specify the company codes that are involved in automatic payments and also which company code makes the payments (paying company code).

The payment program identifies the open payment requests and selects the items to be paid. It basically pays items as late as possible. You specify the exact time of payment when configuring the payment program

The selection of open payment requests is determined by the following factors:

  • The due date of the items is basically determined by the due date and the level of urgency indicator in the payment request
  • For each payment run, you specify the date of the next payment run. The program uses this date to determine whether an item is to be included in the current or the next payment run.

You block the items that, regardless of their due date, you do not want to pay. To do this, you enter a blocking key in the item that represents the reason for blocking. If you want to block the account of a customer or vendor from payment, you enter the blocking key in their master record.

The standard system contains several blocking keys, which you can add to or change.

The payment program creates a payment proposal during the payment run. The payment is made on the basis of this payment proposal list. The blocked items are displayed separately in the list. You can process the payment proposal, and, for example, set or cancel the payment block on an item.

It is also possible to specify that a blocking key cannot be changed from the payment proposal transaction.
On the whole, the payment date is used as the clearing date. There exist, however, the following exceptions.

Items whose posting date comes after the posting date of the payment run will be paid, provided they are already due.

The clearing date for such payments is not the payment date, but rather the latest posting date possible. Thus any danger of the clearing date coming before the posting date is prevented in the context of paid items. Errors are avoided in this way.

Grouping of Payment Requests 
Wherever possible, the payment program will always group payment requests together for payment. However, you can also specify that an individual payment (separate payment) is made for a particular item. For certain payment methods, only individual payments are possible.

The payment program can only group together open payment requests into one payment if the open items in an account have the same:

  • Payment currency
  • Payment method in the item
  • Bank in the item
  • Contents of the grouping fields

You can also settle payment requests from different company codes together as well as customer and vendor items.

Items in an account are not grouped together if you:

  • Make payments seperately per business area. This procedure entails separate payments being created per business area.
  • Wish to make individual payments.

For further information, follow the link

Payment Processing is a component of SAP's R/3 Financial Accounting module (FI). FI is a powerful module integrating many activities, including General Ledger, accounts payable, accounts receivable and assets accounting. You will learn to process simple and complex payment transactions. In addition, you will maintain data and systems settings for accurate and effective payment processing in this course

Link in HELP: