6.1.1 Maintain the CLS Preferences for the Branch

This topic provides the systematic instructions to maintain the CLS Preferences for the Branch.

Specify the CLS preferences as part of maintaining the generic processing guidelines for FX deals entered into at your branch.

1. On the Homepage, type FXDBRMNT in the text box, and click the next arrow.

   Foreign Exchange Branch Parameters Maintenance screen is displayed.

   Figure 6-1 Foreign Exchange Branch Parameters Maintenance

   
   Description of the illustration fxdbrmnt__cvs_main.jpg
2. On the Foreign Exchange Branch Parameters Maintenance screen, specify the details as required.

   The branch code, with the name of the branch for which the preferences are maintained, is defaulted in the screen.

   For information on fields, refer to the below table.

   Table 6-1 Foreign Exchange Branch Parameters Maintenance - Field Description

   Field	Description
   Branch Code	Specify the branch code. Alternatively, you can select the branch code from the option list. The list displays all valid options.
   Branch Description	The system displays the branch description.
   Process Till	Select the date up to which FX deals are processed in the branch. The options are: System Date Next Working Day -1
   Revaluation Reversal	Revaluation entries is reversed in either of two ways, according to your specification: Account Revaluation - If you select this option, revaluation entries passed during the EOD process are reversed as part of the account revaluation process on the next working day. You must ensure that the account revaluation process is run before running the contract revaluation process. Deal Level - If you opt for deal level revaluation reversal, a BOD process reverses the contract revaluation entries posted the previous day. Revaluation entries are posted and reversed at the level of individual contracts.
   Revaluation At Product	By checking this box, you enable the passing of a consolidated revaluation entry at the product level for all forward FX contracts under that product.
   User Reference Number in Messages	Based on the specification you make here, the system assigns the Tag 20 (Sender’s reference number) of a SWIFT message to either user reference number or contract reference number. Check this box if you want the system to apply the user reference number for sender’s reference Tag 20 of the SWIFT messages sent. If you leave the box unchecked, the system applies the custom reference number according to the format (or logic) defined for the product that the contract uses. Note: This feature is applicable only for SWIFT messages sent out by Foreign Exchange module.
   CLS participant	You have to select this option to identify the branch as a CLS participant. This will enable you to process the FX deals entered into at your branch via the CLS bank. Only after you mark the branch as a CLS participant, you will be allowed to maintain the following CLS preferences.
   Settlement Member	Here, you have to select the BIC Code of the customer who will be the intermediary /settlement member through whom the FX deals of your branch will be routed to the CLS bank. The Messaging System of Oracle Banking Treasury Management will identify this customer as the receiver of the MT 304 (Confirmation Message/ Advice of a Third Party deal).
   T- Copy	This is applicable if the counterparty is a SWIFT member. If you specify that ‘T-Copy’ is required, the SWIFT media will send the CLS Confirmation Message (MT300) to the counterparty of the deal with a copy to your settlement member. If multiple addresses are maintained, MT300 is sent to the location, marked as the counter party’s primary address. If the third party does not subscribe to T-copy or if the counterparty is not a SWIFT member, Oracle Banking Treasury Management will automatically generate the MT304 message and identify the BIC of the Settlement Member (where your branch is the Third Party participant) as the receiver of the message. In such a case, MT300 is a normal confirmation, which is sent to your counterparty if it is a SWIFT subscriber. If you check T - Copy, the system will include the TPS identifier in MT300 message for CLS NDF deals. However, the system will not generate MT304 message for the message type FS_FMCONF.
   Auto-Confirm CLS Deals	You may select this option to enable the system to automatically confirm the CLS deals processed at your branch automatically. In this case, the system will ignore the MT300 received from the counterparty and mark the confirmation status as Confirmed.