In a situation, where for some reason the counterparty is not a client of the repository, he/she is unable to fully perform their obligations and register a master agreement or a transaction in the repository. However, if the counterparty sends a registration order that will be recorded in the log of the repository’s incoming messages, this fact will be sufficient to ensure the regulator has no claims against the counterparty.

Page contents:

Registration of master agreements

When creating an order for registering a master agreement it is necessary to choose its parties (Fig. 1).

Figure 1 – parties of the MA

Clicking on the link opens a form, where the user must choose the first and second parties to the agreement. If the party is in the list, select it by clicking on the name. If the party is not in the list (not a client of the repository), in the filter field (Fig. 2) enter a string that uniquely identifies the counterparty. 

Figure 2 – selection of the counterparty

An identifier of a non-repository client is generated as follows: [NONREF] Organization name. Click on the Set own party button to add [NONREF]. After that enter the organization name.

If you know INN of organization (e.g., 0123456789), the identifier should be filled as follows: INN_0123456789.

Registration of contracts

When registering the contract it is necessary to specify the master agreement, under which the contract was concluded. If the master agreement had been registered in the repository earlier, it can be selected from the list by clicking the NONREF link (Fig. 3, field  1).

Figure 3 – filling out the Number of master agreement field

Clicking on the link opens a form, where the user can can select a master agreement (Fig. 4).

Figure Selection of master agreement form

In a situation where the counterparty is not a client of the repository and the master agreement hasn’t been registered in the described manner, the client will not be able to find it in the list. In this case, instead INTERNAL_NUMBER (Fig. 5), you need to specify the contract number of the the party’s internal contract accounting system, or any unique number.

An internal number is used as the MA number when creating orders for registration of master agreements/contracts/transactions with non-repository clients.

Figure – example of field completion

Next, it is necessary to specify the parties to the transaction. To do this, click on links 3 and 4 (Fig. 3), and in the form that opens enter the IDs and names of the counterparties, the same way as described above in case of registering a master agreement.

Figure – information about counterparty

If one of the parties to the transaction is a repository client, it is necessary to specify their repository code and short name registered in the repository.

Sent contracts are listed among the incoming messages of the repository, and in the Rejections form of the Web-client.