| Section |
|---|
| Column |
|---|
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. |
| Column |
|---|
| | Panel |
|---|
| bgColor | #F5F5F5 |
|---|
| borderStyle | dotted |
|---|
| Page contents: |
|
|
Registration of master agreements
When creating an order for registering a master agreement it is necessary to choose its parties (Fig. 1).
...
| Tip |
|---|
Examples of generating an identifier of a non-repository client - If you know the INN, the identifier is generated as follows: INN_{INN value}.
- If you know the SWIFT code, the identifier is generated as follows: SWIFT_{swift code}.
- If you know some other code that uniquely identifies the counterparty, then {Name of code type}_{code value}.
|
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).
...