5.9 Reconciliation of Utilization Transactions

This topic provides information on Reconciliation of Utilization Transactions.

The (hereafter referred to as Oracle Banking ELCM) system receives Utilization Transactions (or contracts) from different external product processing systems. These external systems include Loans systems, Treasury systems, Trade and Finance systems and others. The bulk of the contract details remains with these external systems and the only the details required for processing will be sent to .

During such Utilization Transactions, mismatch of details between the external product processor and may occur. To handle such mismatches, the system features an EOD Reconciliation Process to bring both system in sync by the end of the day.

EOD Reconciliation Process

As part of the EOD Reconciliation Process, an inbound transaction process happens wherein each product processor generates a batch file containing details pertaining to all the utilization requests for the day. The system will process these batch files as part of EOD batch operation and perform the reconciliation process.

The Manual/System parameter specifies whether the mismatched transaction should be handled manually by the user or the system should perform the reconciliation process.

The system reads all the batch files for reconciliation and perform a comparison of all the transaction that has been performed in the product process with the utilization transactions performed in .

The following table shows the possible types of the mismatch.

Table 5-11 Transaction Status

Transaction Status in Product	Corresponding Utilization status	Resulting Oracle
Not Saved	Saved	Reversal
Saved	Not saved	Upload

The above mentioned action is performed only if the system parameter has been set to System.

Viewing Mismatch Summary

User can view in the mismatch Summary screen all the counter transactions that has been performed by for handling the mismatches. The summary also indicates whether the counter transactions have succeeded or failed.

For failed transactions, the reason for failure will be shown. User will have to take manual action in case of failed transactions.