Process Flow of End of Day Processing
Purpose
End of day processing can either be carried out daily or at longer intervals, depending on how current the data needs to be.
Before you start end of day processing, it is advisable to execute a few programs (reports) several times during the day (approximately every two hours) by means of a job. The reports must run at least once, directly before the posting cut-off for payment transactions and the other end of day processing steps.
The reports in question are the following:
Report RFBKPOEX (payment order)
For the processing of payment orders with at least one external recipient, the order is transferred to the previous/feeder system to determine the routing. If errors in communication occur, the order is flagged with an error indicator. When executed, the report selects all these payment orders and sends the information once again to the previous/feeder system. If this corrects the error, the error indicator is removed and the payment order is completely edited. If the error still exists, the error indicator remains and the payment order is selected again during the
next run.Report RFBKENQ1 (payment item)
With this report, those payment items that had been placed in a special table (Totals records in queue) for the following reasons during daily business are duly and properly updated:
Report RFBKPRE1
In productive operation, payment items can have the status "parked", because there was not sufficient coverage in the account at the time of the limit check. When executed, the report selects all those items for which the status "parked" was due exclusively to the insufficient coverage. The system checks if there is now sufficient coverage in the account. If this is the case, the item is posted.
The following tasks, to be executed periodically, belong to end of day processing itself:
Here you set the posting cut-off. All postings in payment transactions are subsequently made with the following date. In most cases, the system automatically sets the posting cut-off (if you have pre-set this in Customizing for the bank area). Execute the posting cut-off before any other balancing tasks to ensure that no additional postings occur in the period to be settled during the account balancing run (value dates in the past are still possible). The posting date for the balancing postings remains unaffected and lies within the period to be balanced (if executed daily).
In the cash concentration run, the system creates carry forwards for those accounts that are organized in account hierarchies. All root accounts for which cash concentration is due on the current posting date are selected. (You control this by your entries on periodic account balancing in the account master data).
You can execute cash concentration before or after account balancing. If you execute the cash concentration run before account balancing, the balancing calculations already take the carry forwards into account.
For this, interest and charges for the accounts due for balancing are calculated and posted accordingly to the respective accounts. Interest compensation is triggered automatically.
For this, all the bank statement data for all accounts due for the issuing of a bank statement is printed or transferred to a corresponding interface in a mass run.
After execution of all balancing tasks, the system increases the posting date for balancing postings. Increase the posting date daily, even if no account balancing has taken place.
If you have the same balancing and bank statement dates for all your accounts within the selected company codes, (for example, end of the quarter), you do not need to execute the account balancing and bank statement runs daily, but only on this date. If you do not execute balancing daily but rather, for example, monthly, note the following:
The posting date for the balancing postings must always be within the period to be balanced. If you wish to perform account balancing on a day in the following period, this is what to do: On the last day of the old period, set the posting date for the balancing postings and do not change it before the balancing has been executed.
The system selects the standing orders due for the current posting date. Postings are created (with the current posting date for payment transactions) and forwarded to the payment transaction system.
(Note: If you adhere to the order specified here for end of day processing, the standing orders due for the following day are created, as the posting cut-off has already been executed. This guarantees that the orders are placed in external payment transactions in good time).
The accrual/deferral of the interest already incurred but not yet posted can take place independently of the other periodic tasks, particularly account balancing.
During balance sheet preparation, division into receivables and payables takes place. It is advisable to perform balance sheet preparation daily. There is a report "Balance sheet preparation" (RFBKGLBSPREP) available to you for this that you can also find using the menu options. Choose Periodic tasks ® General ledger ® Balance sheet preparation.
The time periods in which the data is transferred to the general ledger depend on how up to date you require the information on the general ledger. (From a technical point of view, this can be at any time during the balancing tasks; the time period is a maximum of once a day). General ledger transfer ideally takes place daily.
The time periods in which you execute the account closure run depend on how up to date you require the information and the number of closed accounts.
You can execute end of day processing in two different ways: