Payments With Different Run Dates in a Payment Run
Description
As of Release 3.0A it is possible to flag a payment method in a particular company code to the effect that a payment is generated for every due date. The items to be paid are thus grouped by due date and instead of a single payment, the system makes as many payments as there are due dates. This means that every payment has a unique due date, which can be used as the basis for a run date, which is information you can pass on to your house bank by form or data medium exchange.
Grouping by due date
Since it is possible to use both payment methods which group items by due date and those which do not use this form of grouping in a single payment run, the following sequence of steps has been configured for the payment program:
First, all the items in an account that are due for the payment run are taken together. A suitable payment method is then selected on the basis of the sum total and the number of items involved. If this payment method requires a breakdown of items by due date, the system creates a smaller group of items for each due date. The due date for overdue items in this case is set as the date of the payment run. This ensures that no groups with dates in the past are formed.
If every group has a payable balance, no further steps are necessary.
If a balance with the wrong sign (i.e. a minus sign) exists (a surplus of credit memos or payments on account), the items making up this balance are added to those for the next available due date. If this is not possible, the items are added to those for the nearest previous due date.
Value date
With the payment per due date method, the (anticipated) value date is calculated on the basis of the day the item is due and not (as was previously the case) on the basis of the payment date. This is also true when the value date is determined using a bank calendar or when a fixed number of days (set in the system configuration) are added to the baseline date.
Change system parameters in customizing
If any of the payment methods selected has the attribute Payment
per due date , you should go to the Financial Accounting
Implementation Guide under "Accounts Receivable and Accounts Payable" in the
step 
"Set up payment program" . In the screen that appears, select
Payment methods -> In company code . You then
select the company code you require by double-clicking on it and then the
required payment method. In the detail screen for the payment method, you then
select the Payment per due day field.
For further information see the Implementation Guide.
Changes in procedure
The processing of the payment proposal has been modified so that the due date of a payment can be changed. The system checks that the due date entered neither falls before the date of the payment run (error message) nor more than 30 days after the payment run (warning).
In the case of payments by bill of exchange, the displayed due date should be considered to be the bill of exchange due date. This means that the bill of exchange due date can be changed when a payment proposal is edited.
Dependent functions
Foreign data medium exchange for Germany (RFFOD__L)
The run date in the data medium header record (R8) is still determined on the basis of the creation date (R6), i.e. based on the the payment date from the payment run, plus the lead days from the house bank DME data.
The run date in the memo record (T5) is now calculated from the above-mentioned due date plus the lead days from the house bank DME data.
Data medium exchange Great Britain via Bank Automatic Clearing Service (RFFOGB_T).
The run date of a transaction is calculated from the due date plus the lead days from the house bank DME data.
The generation date in the data carrier header record (HDR1-8) corresponds to the date of the last run.
The individual data record contains the respective run date of the transaction in field 12 (BACS run date). This is particularly relevant for multi-processing.
Domestic data medium exchange for Norway (RFFONO_D)
The payment date in the individual data record (record 30, field 6) is calculated from the due date of the payment plus the lead days from the house bank DME data.
Foreign data medium exchange for Austria (RFFOAT_L)
The order date (sales record 2, field no.32) is calculated from the execution date which can be specified on the selection screen for the print report. If no execution date is specified, the order date is calculated from the due date of the payment plus the lead days from the house bank DME data.