Various Stages of EOC Process

1.1 Various Stages of EOC Process

This topis describes about the various stages involved in the EOC process.

Table 1-1 Various Stages of EOC Process

Stages of EOC Process	Description
End of Transaction input (EOTI)	The End of Transaction input (EOTI) stage is the first stage in EOD operations. The system should be moved to this status after all the transactions for the day have been entered into the system. In addition, all the transactions should be authorized and the relevant messages generated. Note: All the messages don't need to be generated on the same day as transaction input, it is ideally done that way. In an exceptional situation, go ahead with the End of Day processes without generating a message. This message will remain in the un-generated status in the Outgoing Message Browser and can be generated on any other day. An un-generated message will not be archived. EOTI must not be marked under the following circumstances: When a message is in an unprocessed state. Note: When a reply to the message sent has either not been received or arrived at by the system. The above validations are applicable for RTGS messages only. When transactions that have been input are yet to be authorized. When the debit and credit totals for the day do not match for some reason. Under such circumstances, examine the transaction(s), which have resulted in the imbalance (with the help of the Transaction Journal) and take the necessary action. The action could be in posting an extra entry or moving an entry from one account to another, etc. After the system is moved to this status, the user will neither be allowed to enter further transactions into the system nor will be allowed to perform any maintenance functions. All the relevant toolbar actions will also be disabled. However, the user can perform queries on the system. The user can run only those automated functions that have been defined for this stage of End of Day processing.
End of Financial Input (EOFI)	At this stage, no further accounting entries can be passed for the day either through transactions that have been entered or by transactions that are automatically triggered by the system. After the system is moved to this status, the user can generate financial reports for the day now since all the automatic processes have been run for the day and since the balances available will be the latest. After EOFI is marked, the user can generate all advice-related messages like reports, tracers, and all other information on the day’s activities.
End of Day	The EOD process is designed to tie up all the operations for a financial day and prepare the system for the next day. The End of Day operations for a branch can begin after all the transactions for the day have been input and authorized. Ideally, all the messages for the day should also be generated before the End of Day operations begins. A message should be carried over to a subsequent day only under exceptional conditions. The End of Day status indicates that the user has completed all the activities for the day. After EOD for a branch is run, the system will not allow running any other operation in the branch, till the system date has been changed to the next working day, and authorized. If the user tries to run any application, it will be prompted to change the system date first.

Stages of EOC Process

Description

End of Transaction input (EOTI)

The End of Transaction input (EOTI) stage is the first stage in EOD operations. The system should be moved to this status after all the transactions for the day have been entered into the system. In addition, all the transactions should be authorized and the relevant messages generated.

Note: All the messages don't need to be generated on the same day as transaction input, it is ideally done that way. In an exceptional situation, go ahead with the End of Day processes without generating a message. This message will remain in the un-generated status in the Outgoing Message Browser and can be generated on any other day. An un-generated message will not be archived. EOTI must not be marked under the following circumstances:

When a message is in an unprocessed state.
Note: When a reply to the message sent has either not been received or arrived at by the system.
The above validations are applicable for RTGS messages only.
When transactions that have been input are yet to be authorized.
When the debit and credit totals for the day do not match for some reason.

Under such circumstances, examine the transaction(s), which have resulted in the imbalance (with the help of the Transaction Journal) and take the necessary action. The action could be in posting an extra entry or moving an entry from one account to another, etc.

After the system is moved to this status, the user will neither be allowed to enter further transactions into the system nor will be allowed to perform any maintenance functions. All the relevant toolbar actions will also be disabled. However, the user can perform queries on the system.

The user can run only those automated functions that have been defined for this stage of End of Day processing.

End of Financial Input (EOFI)

At this stage, no further accounting entries can be passed for the day either through transactions that have been entered or by transactions that are automatically triggered by the system.

After the system is moved to this status, the user can generate financial reports for the day now since all the automatic processes have been run for the day and since the balances available will be the latest.

After EOFI is marked, the user can generate all advice-related messages like reports, tracers, and all other information on the day’s activities.

End of Day

The EOD process is designed to tie up all the operations for a financial day and prepare the system for the next day.

The End of Day operations for a branch can begin after all the transactions for the day have been input and authorized. Ideally, all the messages for the day should also be generated before the End of Day operations begins. A message should be carried over to a subsequent day only under exceptional conditions.

The End of Day status indicates that the user has completed all the activities for the day. After EOD for a branch is run, the system will not allow running any other operation in the branch, till the system date has been changed to the next working day, and authorized. If the user tries to run any application, it will be prompted to change the system date first.

Parent topic: EOD Maintenances