Process Flow of End-of-Day Processing 
Purpose
End-of-day processing can be run daily or at longer intervals, depending on how current the data needs to be.
Before you start end-of-day processing, we recommend that you run certain programs (reports) several times during the day (approximately every two hours) by using 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.
These reports are as follows:
Report RFBKPOEX (Payment Order)(applies only to banks)
To process payment orders with at least one external recipient, the order is transferred to the upstream system to determine the routing. If there are communication errors, the order is flagged with an error indicator. This report selects all these payment orders and sends the information once again to the upstream system. If this corrects the error, the error indicator is removed and the payment order is processed. If the error still exists, the error indicator remains and the payment order is selected again during the next run.
Report RFBKENQ1 (Payment Item)
This report enables the correct processing of payment items that were placed in a special table (totals records in queue) during daily processing due to the following:
In the productive system, during a currency changeover, the affected accounts are locked for the EURO during a currency conversion.
If the payment transaction system transfers a payment item to the current account system, the item undergoes the limit check on the relevant account. Items that arrive simultaneously encounter a limit lock.
Report RFBKPRE1 (Process Parked Payment Items)
In productive operation, payment items can have the Parked status because the account did not have any coverage at the time of the limit check. The report selects all the items for which the Parked status was caused exclusively by a lack of coverage. The system checks if there is sufficient coverage on the account now. If this is the case, the item is posted.
You must also execute the Collect Deposit Amount for Fixed-Term Deposit report (RFBKTDEPOSITCOLLECTION) and the Fix Fixed-Term Deposit Accounts report (RFBKTTERMCONTROL) before beginning the end-of-day processing.
The reports RFBKTMP1 and RFBKTMP1_PO for posting planned items or forward orders whose planned posting date has been reached need to be scheduled for the start of the day, and must not be included in end-of-day processing.
End-of-day processing includes the following periodic tasks:
Posting cut-off for payment transactions
You set the posting cut-off, whereby all subsequent payment transaction postings are entered with the subsequent date. The system can set the posting cut-off (if you have defined this accordingly in the Customizing settings for the bank area) or schedule it in end-of-day processing. Complete the posting cut-off before any other balancing tasks to ensure that no additional postings occur in the period to be balanced during the account balancing run (value dates in the past are still possible). The posting date for the balancing postings remains unaffected and is normally (if run daily) on the last posting date for payment transactions.
Running cash concentration
In the cash concentration run, the system creates carryforwards for the accounts in account hierarchies. All root accounts are selected for which cash concentration is due on the current posting date. (You determine this by your entries for the periodic account balancing in the account master data).
You can run cash concentration before or after account balancing. If you run the cash concentration before account balancing, then the balancing calculations include the carryforward amounts.
Balancing accounts
Interest and charges for the accounts due for balancing are calculated and posted on each account accordingly. Interest compensation is triggered automatically.
Collecting Deposit Amount on Term Agreements(banks only)
The contract amount is collected for term agreements when the collection date is reached (depending on the Customizing settings).
Fixing Term Agreements(banks only)
Term agreements whose term start date has been reached are fixed.
Prenotifying Maturity of Term Agreements(banks only)
On the predefined date, the system initiates correspondence for the prenotification of maturity of term agreements.
Calling Term Agreements(banks only)
If the maturity date has been reached (depending on the Customizing settings, either one working or one calendar day before the term end), the agreements are called (see also: Fixed-Term Deposit Processing ).
Closing accounts
The time periods in which you close accounts depend on how current the information is to be and the number of accounts to be closed.
Generating the bank statement
The bank statement data for all the accounts to go on the bank statement is printed or transferred to a suitable interface in a mass run.
Updating the posting dateto the next day for the balancing postings
Once the balancing tasks are complete, the system updates the posting date for balancing postings to the next day. The posting date must be updated daily, even if no accounts were balanced.
If you have the same balancing and bank statement dates for all your accounts in the selected company codes (for example, end of the quarter), you do not need to balance the accounts or generate the bank statements every day, but on this date only. If you do not balance the accounts daily but, for example, monthly, note the following:
If the period end closing has not yet been completed for all accounts, the posting date must not be changed to a date after the last bank working day of this period. To balance accounts on a day in the following period proceed as follows: On the last day of the old period, set the posting date for the balancing postings and do not change it before the balancing is complete.
Posting standing orders (banks only)
The system selects the standing orders due for the current posting date. Postings are created (with the current posting date for payment transactions) and transferred to the payment transaction system.
( Note: If you use the processing sequence specified here for end-of-day processing, the standing orders due for the following day are generated, as the posting cut-off has already been completed. This guarantees that the orders are placed in the external payment transaction system in good time).
Calculating interest accrual/deferral
The accrual/deferral of the interest already incurred but not yet posted can be calculated separately from the other periodic tasks, particularly account balancing.
Preparingthebalance sheet
During balance sheet preparation, data is divided into receivables and payables. It is advisable to run balance sheet preparation daily. You can use the Balance Sheet Preparation report (RFBKGLBSPREP) by choosing Periodic Tasks → General Ledger → Balance Sheet Preparation from the SAP Easy Access menu.
General ledger transfer
The time intervals at which the data is transferred to the general ledger depend on how current the information on the general ledger is to be. Normally you need to transfer the data to the general ledger each day.
You can run end-of-day processing with one of the following options:
As event control. For more information, see: End-of-Day Processing as Event Control
As job chain control in Bank Customer Accounts (BCA)whereby it is recommended that you automate these typical process flows by using jobs. For more information, see: Setting Up a Job Chain