Process Flow of End-of-Day Processing 

Purpose

End-of-day processing can be carried out daily or at longer intervals, depending on how current the data needs to be.

Prerequisites

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 as follows:

·        Report RBCA_PO_RESEND_EXTERN  (Repeated transfer of payment orders to PTS)

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 there are communication errors, the order is flagged with an error indicator. 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 persists, the error indicator remains and the payment order is selected again during the next run.

·        Report RBCA_PAYMITEM_PROCESS_ENQ (post payment item from BCA_PAYMITEM_ENQ in BCA_PAYMITEM)

This report ensures the correct posting of the payment items that were placed in a special table during daily business.

When a payment item reaches Account Management by way of the payment transaction system, and when it is checked, the system checks whether the account is technically available or locked by conflicting activities. If this is the case, the item is placed in a queue. This report enables the queue to be processed later.

The general ledger update during end-of-day processing can only take place when there are no more items in the queue with a posting date before or the same as the current posting date.

Process flow

End-of-day processing includes the following tasks that are carried out periodically:

·        Set posting date for payment transactions (RBCA_DATE_POST_SET)

See Setting the Posting Date.

This is where you increase the current date for payment transactions. We describe this operation as Posting Cut-Off.  All payment transaction postings are then made with the new date specified by you (taking account of the posting calendar). Execute the posting cut-off before any other settlement tasks (cash concentration, account settlement and so on) to ensure that no additional postings occur in the period being settled during the account settlement run (value dates in the past are still possible). The posting date for end-of-day processing remains unaffected and thus generally falls (if executed daily) on the last posting date for payment transactions. The posting date for end-of-day processing is not increased until the end of end-of-day processing.

·        Execute cash concentration (RBCA_CCON_RUN_PP)

See Running Cash Concentration.

The cash concentration run clears accounts for each bank posting area for all accounts with the same master contract product. On the basis of specified carryforward rules, the cash concentration run generates payment orders that generate credits or debits on the accounts involved to keep the account balances within a certain range, or clear accounts completely, for example.

·        Run account settlement (RBCA_SETTLE_RUN_PP)

See Account Settlement.

This involves interest and charge calculation for the accounts due for settlement and posting accordingly to the respective accounts.

·        Increase posting date for end-of-day processing (RBCA_DATE_CLOSE_SET)

See Setting the Posting Date.

After all the settlement tasks are completed, the system increases the posting date for end-of-day processing. You need to increase the posting date every working day, even if no account settlement has taken place.

If you have the same settlement and bank statement dates for all your accounts within the selected bank posting area, (for example, end of the quarter), you do not need to execute the account settlement and bank statement runs daily, but only on this date. If you do not balance the accounts daily but, for example, monthly, note the following:

As long as period settlement has not been executed for all accounts, the posting date for end-of-day processing is not to be increased to a date after the last working day of the bank in the period. To run account settlement on a day in the following period, proceed as follows: On the last day of the old period, set the posting date for end-of-day processing and do not change it until the settlement has been executed.

·        Close posting day (RBCA_GL_CLOSE_DAY)

See Closing Posting Day for General Ledger Transfer.

The posting day is closed so that the daily turnovers can be prepared for the general ledger (balance sheet preparation). As of this point in time, no more postings can be made on or before this posting day.

·        Calculate interest and charge accrual / deferral (RBCA_ACCRUE_RUN_PP)

See Accruing/Deferring Account Results.

The accrual/deferral of the interest already incurred but not yet posted can take place independently of the other periodic tasks, particularly account settlement.

·        Execute balance sheet preparation (RBCA_BSPREP_RUN_PP)

See Executing Balance Sheet Preparation.

During the balance sheet preparation, the turnovers of the posting day are grouped together for the general ledger and are written to aggregated documents. It is recommended that you run balance sheet preparation daily.

·        General ledger transfer (RFBKGL01)

See 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. The transfer to the general ledger ideally takes place daily.

·        Due product changes (RBCA_OR_COP_TEV_START_BCA_BOCP)

See Executing Due Product Changes (Account)

·        Execute bank statement run (RBCA_BAST_RUN_PP)

This involves a mass run in which all the bank statement data is generated for all agreements for accounts due for the issuing of a bank statement, and correspondence requests are created.

·        Post standing orders (RBCA_SORD_RUN_PP)

See Executing a Standing Order.

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.

If you adhere to the order specified here within end-of-day processing, the standing orders due for the following day are generated, as the posting cut-off has already been made. This ensures that the orders are placed in external payment transactions in good time.