Payment Run Control

The payment run control data is specified in the master data and in the line item to be payed. The payment run control data on line item level override the data on contract account level.

The paying company code is used for the definition of house banks and payment methods. The payment methods are country-specific. For this reason, it’s only possible to select company codes within a country that has the same currency in each payment run.

The payment run control data are divided into outgoing and incoming payment methods in the contract account master data, which flexibly refer either to one or more bank account with IBAN and SEPA mandate or to one or more payment card ID of the contract account’s business partner.

The payment can be locked and default values for the lock duration can be configured. Furthermore, when debit memos fail, automatic debits can be prevented until a processing lock date is reached.

The alternative payer pays all his contract accounts items together. Payment methods, banks, and locks are determined using this offsetting contract account.

The payment run’s posting date is applied as the baseline date for determining the due date, except in the following cases:

• If a deferral date has been entered in an item, it is always used to determine the due date.
• If the cash discount date is prior to the posting date, the cash discount due date is used to determine the due date and the item is paid minus the cash discount.
• If the cash discount period has expired, the due date for net payment is used.

The due date for an item that is determined in this manner must fall within the due date interval entered in the payment run parameters.

The grouping ensures, that items with the same term, for example items of the same invoice, are paid together.

red hat openstack training courses malaysia