6.3.2 Confirming the Generation of Messages for an Event

From the filtered contracts, you have to select the contracts that need to be processed. To do this, check the Confirmed to Auto option with the respective events. This confirms that the messages for the selected events under the contract should be generated on the schedule date. However, the system does not automatically generate the messages on the schedule date. You have to manually confirm the events to generate the messages in the Outgoing Message Browser.

You can view the status code and the description of the status code received from Sanction check.

When you click the double-click the record Message Generated for the Event is be displayed.

Click Save to confirm that the messages should be generated. When you save the details, the Confirm option (in the screen above) is automatically checked.

After selecting one or more messages and selecting the Resend to SC? box, click OK. The selected messages with status code 04, 05 and 06 that are unconfirmed by Sanction check is resent to sanction check for confirmation.

The following are the various statuses that are received from Sanction check system. The status code is automatically displayed in the status column once the acknowledgement is received from Sanction Check System.

Code	Status	Description
0	TRANSMITTED TO SANCTIONS	Message has been sent from Oracle Lending to SC and awaiting a response from Sanction Screening.
-1	COMPLETE	0 hit from Global Interdict, Compliance officer approves the status.
01	PENDING-COMPLIANCE	1 or more hits from Global Interdict.
02	CONFIRMED-HIT	Compliance officer has confirmed the hit. The status is only available after maker approves the status.
03	TERMINATE	Compliance officer terminates the transaction.
04	SC APPLICATION ERROR	This is an error status if something goes wrong on sanctions check side.
05	GI APPLICATION ERROR	This is an error status if something goes wrong on GI application side.
06	OTHER ERROR	This is an error status for errors other than SC, GI.

Click on the OK to proceed. The messages associated with the event are released into the Outgoing Message Browser and the Hold status are set to N (No). This indicates that the messages have been released successfully and are no longer on hold.

Click the View button to view the message that are to be sent out.

The system sends out a message depending on when the confirmation received from you. This is explained in the example given below

Example

The following are the details of a contract booked:

• Booking Date- 1^st July 2005
• Value Date- 5^th July 2005
• Currency- USD
• Settlement Days- 2 days

If you confirm on the 1^st or 2^nd of July that the message needs to be generated, the message is sent on the 3^rd of July (BOD).

If you confirm on the 3^rd, 4^th or 5^th of July that the message needs to be generated, the message is released from the Outgoing Message Browser immediately.

If you do not confirm before the 5^th of July EOD that the message needs to be generated, the accounting entries are passed for the event, and the message is held in the Outgoing Message Browser.

Viewing separate fee liquidation entries in Forward Processing Browser

The system supports fee payment messages in modules LS, LD and SLT where the messages are released from Forward Processing browser. Firstly, the system populates the ADHOC Fee and derived fee payments into Forward Processing browser if the ‘forward processing required’ flag is checked and if fee liquidation mode at the product level is set to the following criteria’.

• Semi-Auto / Auto / Manual for ADHOC Fee
• Semi-Auto / Auto for derived Fee