Приказ №62 нко зао нрд issued by nsd от 18. 03. 2016
Скачать 2.14 Mb.
|
| |
| 1.32.3.17.7.If there is no cross Reporting Form on Status of Obligations under contracts from Reporting Agent 2, the Repository shall perform consecutive reconciliation of the Contract Obligation Status Reporting Form. |
|
| 1.32.3.17.7.1.The Repository shall send a Reconciliation Request (document code RM005, Appendix 1) to the Principal Reporting Agent of the Client’s counterparty (Principal Reporting Agent 2). Concurrently the Repository shall send a Notification on a Reporting Form Status (document code RM003, Appendix 1) to Principal Reporting Agent 1. 1.32.3.17.7.2.The Contract Obligation Status Reporting Form shall be confirmed by Principal Reporting Agent 2 by sending to the Repository confirmation of parameters of the Reporting Form (document code CM001, Appendix 1). 1.32.3.17.7.3. When confirmation of the parameters of the Reporting Form is obtained from Principal Reporting Agent 2, the Repository shall make a reconciliation of the Contract Obligation Status Reporting Form of Reporting Agent 1 with the received confirmation of parameters of the Reporting Form obtained from Reporting Agent 2 across all matching fields. In case of positive results of reconciliation, the Repository shall enter information about the Contract Obligation Status Reporting Form in the Contracts Register and send a Registration Advice (document code RM001, Appendix 1) to Reporting Agents. In case of negative results of reconciliation the Repository shall send a Notification on discrepancies in terms of reporting forms (document code RM006 Appendix 1) to Principal Reporting Agent 2 while the Contract Obligation Status Reporting Form submitted by Principal Reporting Agent 1 shall be kept by the Repository in a pending status. |
|
| 1.32.3.17.8.Following the submission of the Contract Obligation Status Reporting Form (document code CM093 of Appendix 1 to these terms and Conditions) when the counterparty is a Client not obliged to submit information to the Repository and refusing to submit information to the Repository, the Repository shall send the Reporting Party initiating the submission of the Contract Obligations Status Reporting Form, a Notification on delivery prepared pursuant to the EDI Agreement. 1.32.3.17.9. While processing the Contract Obligations Status Reporting Form the Repository shall verify the Reporting Form for accuracy and completeness of mandatory fields, check its record systems for rejection to submit information to the Repository, check for the fill-in of the field “Party not providing information to the Repository” of the Master Agreement Reporting Form on the basis of which the Contract Obligations Status Reporting Form is submitted. In case of any incompleteness of the Contract Obligations Status Reporting Form’s fields or any discrepancies between information contained in the Contract Obligations Status Reporting Form and information recorded by the Repository or in the Contracts Register, the Repository shall prepare and send to the Reporting Agent that submitted the Reporting Form on Obligations Status, a Notification on Registration / Execution Rejection (document code RM002 of Appendix 1 to these Terms and Conditions) indicating reasons for such rejection. 1.32.3.17.10.In case of accuracy and completeness of the fields of the Contract Obligations Status Reporting Form and compliance of the Contract Obligations Status Reporting Form with information contained in the record systems of the Repository and the Contracts Register, the Repository shall make an entry to the Contracts Register and shall send the Reporting Agent that submitted the Reporting Form on Obligation Status Notification on registration (document code RM001 of Appendix 1 to these Terms and Conditions). 1.32.3.17.11.Following the receipt by the Repository of the Contract Obligation Status Reporting Form (document code CM093 of Appendix 1 to these Terms and Conditions) as an electronic document when one of the parties to the contact is an n entity not obliged to submit information to the Repository and that is not a Client of the Repository, the Repository shall send the Reporting Agent submitting the Contract Obligations Status Reporting Form to the Repository a Notification on delivery prepared pursuant to the EDI Agreement. 1.32.3.17.12.While processing the Contract Obligations Status Reporting Form the Repository shall verify it for accuracy and completeness of mandatory fields, verify that the code specified in the Contract Obligations Status Reporting Form and identifying the party not obliged to submit reports and that is not the Client of the Repository , corresponds to the code of the counterparty that is a foreign entity contained in the Master Agreement Reporting Form registered in the Contracts Register. The Repository shall also verify that the Master Agreement Reporting Form on the basis of which the Contract Obligations Status Reporting Form is submitted the field “Party not providing information to the Repository” is filled in. In case of any discrepancies or incompleteness of the Contract Obligations Status Reporting Form’s fields or any discrepancies between information contained in the Contract Obligations Status Reporting Form and information recorded by the Repository or in the Contracts Register, the Repository shall prepare and send the Reporting Agent that submitted the Reporting Form on Obligations Status, a Notification on Registration / Execution Rejection (document code RM002 of Appendix 1 to these Terms and Conditions) indicating reasons for such rejection. In case of accuracy and completeness of the fields of the Contract Obligations Status Reporting Form and correspondence of the Contract Obligations Status Reporting Form to information recorded by the Repository in its record systems and in the Contracts Register, the Repository shall make an entry to the Contracts Register and shall send the Reporting Agent that submitted the Reporting Form on Obligations Status, a Notification on registration (document code RM001 of Appendix 1 to these Terms and Conditions). |
|
| 1.32.3.18.The procedure of Credit support annex reporting form registration. 1.32.3.18.1.Information on credit support shall be entered into the Contracts Register on the basis of Credit support annex reporting form (document code CM015 attached at Appendix 1 to this Terms and Conditions) 1.32.3.18.2.The registration of the Credit support annex reporting form is evidenced by corresponding entries made in the Contracts Register and in the Registration Log, and the issuance by the Repository of a Registration Advice (document code RM001 attached at Appendix 1) or, respectively, a Registration / Execution Rejection Advice (document code RM002 attached at Appendix 1) specifying the reasons for the rejection. 1.32.3.18.3.The registration of information on Credit support annex can be initiated by the Principal Reporting Agent. 1.32.3.18.4.The registration of a Credit support annex reporting form shall be done by the Repository 1.32.3.18.5.. Upon receipt by the Repository of an electronic Credit support annex reporting form, the Repository shall send to that Principal Reporting Agent (Principal Reporting Agent 1), a delivery acknowledgement report prepared in accordance with the EDI Agreement. 1.32.3.18.6.Upon receipt of the Credit support annex reporting form, the Repository shall examine it to ensure its compliance with the necessary requirements and if there are any defects in its preparation, send to Principal Reporting Agent 1 a Registration / Execution Rejection Advice (document code RM002 attached at Appendix 1) specifying the reason for the rejection. 1.32.3.18.7.If the Credit support annex reporting form is prepared correctly with all necessary data, the Repository shall send to the Principal Reporting Agent of the Client’s counterparty (Principal Reporting Agent 2) a request for approval (document code RM005 attached at Appendix 1). At the same time, the Repository shall send to Principal Reporting Agent 1 a notification on a reporting form status (document code RM003 attached at Appendix 1). 1.32.3.18.8.The Credit support annex reporting form shall be confirmed by Principal Reporting Agent 2 sending the Repository a report affirming the data contained in the Master Agreement Reporting Form (document code СM001 attached at Appendix 1). 1.32.3.18.9.Upon receipt of a report affirming the data in the Credit support annex reporting form by Principal Reporting Agent 2, the Repository shall compare the Credit support annex reporting form received from Principal Reporting Agent 1 with the report affirming the data contained in the Credit support annex reporting form received from Principal Reporting Agent 2. The Repository shall compare all data pursuant to rules provided by Appendix 6 to these Terms and Conditions, and if the two sets of data match, the Repository shall record the information on the Credit support annex in the Contracts Register and shall send to Principal Reporting Agent 1 and Principal Reporting Agent 2 a Registration Advice (document code RM001 attached at Appendix 1). When matching results are negative the Repository shall form and provide the Notification of dismatch to the Principal Reporting Agent 2 (document code RM006 attached at Appendix 1) |
Похожие:
 | Особенности организации эдо при обеспечении депозитарной/клиринговой/ репозитарной деятельности | | |
| Небанковской кредитной организации закрытого акционерного общества «национальный расчетный депозитарий» | | ... |
| ... | | Порядок взаимодействия клиентов и нко зао нрд при оказании услуг по управлению обеспечением 1 |
 | Нрд – канал информационного взаимодействия, обеспечивающий взаимодействие программного обеспечения Клиента и/или Информирующего лица... | | Комитетом пользователей услуг нко зао нрд (Комитетом пользователей услуг центрального депозитария) |
| Комитетом пользователей услуг нко зао нрд (Комитетом пользователей услуг центрального депозитария) | |