Contracts

After being successfully registered by the repository contracts (transactions, agreements) are saved in the registry. A list of all registered contracts is displayed in a table (Fig. 2).

Fig. 2 – Contract form

Table 1 describes the Contract form columns.

Table 1 – Description of columns of the Contracts form 

The background color of the Status column cells differs depending on the type of contract: archived (terminated) or active (Fig. 3). If the message contains an attachment, the icon  will be displayed. 

Fig. 3 – archived and active contracts

Clicking on the table row in the table opens the history of this contract modifications (Fig. 4), which indicates modification time, status and identification number (number is assigned by the Web-client automatically).

Figure 4 – contract history

Сlicking on the Active/Expired link opens the view form of the contract.

Hovering the mouse over a table row opens up a control panel – . A set of tools depends on user access rights. Tools description is provided in Table 2.

Table 2 – Description of tools

Button	Function
	Creates a draft of message, pre-filled with values from the registered contract and calls the draft Edit and view form
	Calls the View form of a contract (calls the print form for the Aggregated report on binary options). Additionally, you can view the attached file. When you click View a file, the file will be downloaded to the user's computer
	Creates a draft of message for registering changes to the conditions of a registered contract and call the draft Edit form. Button is available for RA, which can report on this contract
	Correct the entry (the changes that do not require the verification)
	Creates a draft report on the status of obligations under this contract. The status selected is T – contract termination. Button is available for RA, which can report on this contract
	Reopen the contract
	Creates a draft report on the status of obligations under this agreement. Button is available for RA, which can report on this contract
	Saves the registry record to file
	Marks contract as read

Credit support transfers report

The form contains a list of сredit support transfers report (CM092) registered in the repository. There reports are made into a separate (Fig. 5), since the data sets (columns in the main table) they can show, significantly differ from the similar set for the Contracts section.

Fig. 5 – Fulfillment of obligations form

The table contains the following information:

• Registration date – date of report registration;
• Record ID – unique identification number of a message assigned by the repository;  
• Party – name of the organization that participates in a transaction; 
• Confirming party – name of the organization that confirms the statement on fulfillment of obligations.

This form has the following report tools available:

•  – create draft report;
•  – view report;
•  – save report as an XML file.
   

Credit support transfers report

The form contains information about mark to market (CM094) registered in the repository (Fig. 6).

Fig. 6 – Fulfillment of obligations form

The table contains the following information:

• Registration date – date of report registration;
• Record ID – unique identification number of a message assigned by the repository;  
• Party 1 – name of the organization that participates in a transaction; 
• Party 2 – name of the organization that acts as a counterparty to the transaction.

This form has the following report tools available:

•  – create draft report;
•  – view report;
•  – registration of changes;
•  – save report as an XML file.
   

Filter settings

In the Registry form the following filters are available:

Fig. 7 – filters

• Contracts status – active, expiered, rejected;
• Trade number;
• Instrument types;
• Master agreements numbers;
• UTI code;
• Parties – the parties of the fill;
• Date (from/to):
  • the date of receiving statement;
  • the value date (fxSwap);
  • the trade date;
  • the derigistration date.
• auto executed contracts (automatic closing of the contact on the date of the expiry of the contract).
  

Fig. 8 – automatic closing parameters

The principle of filtering data in the table described in Filter settings.