NRD001 | The core element #s is missing in the message or has the invalid value. The message can not be processed | BFMT |
NRD002 | Sender of the message is not registered in the repository | NARR |
NRD003 | The file with a scanned document is not attached | NARR |
NRD004 | The message does not contain the name of the attached file | NARR |
NRD005 | The form with ID #s is not found | NARR |
NRD006 | The form has not been registered | NARR |
NRD007 | Message validation error: #s | BFMT |
NRD008 | The message does not contain any signer | NARR |
NRD009 | The original document is not found | NARR |
NRD010 | The contract type #s indicated in the message does not coincide with the contract type #s indicated in the Master Agreement № #s | NARR |
NRD011 | The form is already registered | AEXS |
NRD012 | The counterparty has declined the Master Agreement form | NARR |
NRD013 | No initial message with the status "Pending" is found | NARR |
NRD014 | More than #s days has passed since the date set in "Message creation time" field. | NARR |
NRD015 | The sender specified in the message does not coincide with the real sender of the message | BINF |
NRD016 | There is no Master Agreement #s in the repository's register on a given date | NARR |
NRD017 | Master agreement registration number is not valid or Master agreement parties are not correctly specified | NARR |
NRD018 | The form of contract has already been rejected | NARR |
NRD019 | The sender of a message is not a Principle Reporting Agent specified in the Master Agreement | BINF |
NRD020 | The Principle Reporting Agent of the party #s does not have an active power of attorney for the Master Agreement. The message is registered in the Log with the number N#s. | BINF |
NRD021 | The client #s with the code #s is not the repository's client. The message is registered in the Log with the number N#s. | ICAG |
NRD022 | The party #s of the Master Agreement does not have Reporting Agents and cannot report trades under the Master Agreement.
The message is registered in the Log with the number N#s. | ICAG |
NRD023 | The party #s has a Reporting agent for contract type #s. For the party #s a Reporting agent with the same contract type should be indicated. | BINF |
NRD024 | The party has more than one Reporting Agent for the specified contract type. It is impossible to reconcile the Contract with different Reporting Agents. | BINF |
NRD025 | A form with new parameters is received in the message #s | NARR |
NRD026 | The block "party" should be filled out according to the rules of message creation | BFMT |
NRD027 | The Sender defined in the header of a message (header/sentBy) doesn't match the sender in the <party/[@id="Sender"]> block | BFMT |
NRD028 | The receiver of a message is not a Repository | NARR |
NRD029 | The form of Master Agreement with specified parties for the date is already registered #s | NARR |
NRD030 | There are differences found when comparing the counterparty's messages. The form cannot be registered. | NARR |
NRD031 | The form №#s sent on behalf of the client #s is not registered because the client #s has refused to confirm with the reason: #s | RCDP |
NRD032 | The sender is not a Reporting agent under Master agreement #s for the contract type #s | NARR |
NRD033 | There is no Contract #s in the repository's register on a given date | NARR |
NRD034 | The message (in_msg_id = #s) with <correlationId> from the sender #s has already been received by the Repository from the sender #s | NARR |
NRD035 | The message contains a future send date | NARR |
NRD036 | The message that should be replaced/cancelled has the status #s. It is impossible to make replacement/cancellation | NARR |
NRD037 | The message that should be replaced/cancelled is not found. It is impossible to make replacement/cancellation | NEXS |
NRD038 | Message #s has got replace request | NARR |
NRD039 | The Master Agreement specified in the Contract registration form is not registered | NEXS |
NRD040 | The report execution term has expired | NARR |
NRD041 | Party with code #s and code type #s is not the repository's client. The message is registered in the Log with the number N#s. | ICAG |
NRD042 | Sender #s has no right to submit messages on behalf of the client #s. The message is registered in the Log with the number N#s. | BINF |
NRD043 | Messages with specified parameters are not found in the Contracts register | NARR |
NRD044 | Short name of the party #s with code #s and code type #s does not coincide with the code from the NSD's base of clients. | NARR |
NRD045 | "href" attribute cannot have the value "Sender" | NARR |
NRD046 | The sender of a message is neither a party, nor a Principle Reporting Agent/Reporting Agent for defined contracts. The message is registered in the Log with the number N#s. | NARR |
NRD047 | It is impossible to identify the Reporting Agent of the party #s | BINF |
NRD048 | The block "Party" is incomplete. It has no id=#s | BFMT |
NRD049 | The Master Agreement form is not registered | NARR |
NRD050 | The contract form has been deregistered | NARR |
NRD051 | The Master Agreement form has been deregistered | NARR |
NRD052 | Message #s has got cancel request | NARR |
NRD053 | There is an attempt to terminate the Master agreement with open Contracts | NARR |
NRD054 | The order of the parties specified in the registered contract form does not match the order specified in the amendment/deregistration message | NARR |
NRD055 | The Master Agreement #s specified in the contract form was cancelled | NARR |
NRD056 | The Repository Services Agreement for the specified Master Agreement #s was terminated | NARR |
NRD057 | The receiver of a message is neither a party, nor a Principle Reporting Agent/Reporting Agent for defined contracts. The message is registered in the Log with the number N#s. | BINF |
NRD058 | The Contract #s is not under the Master Agreement #s | NARR |
NRD059 | The block <header> does not comply with the rules of message creation | BFMT |
NRD060 | The field "Reporting party role type" should be filled out | NARR |
NRD061 | The message does not match any repository message format | NARR |
NRD062 | The request for approval of the Reporting form №#s is cancelled because the Client #s has cancelled/replaced the Reporting form | NARR |
NRD063 | The field <correlationId> does not comply with the mask | BFMT |
NRD064 | The type #s of the message #s to be replaced does not correspond to the type #s of the replaceable message #s | NARR |
NRD065 | The contract form #s has already been deregistered | NARR |
NRD066 | The contract type #s is not found in the Product Type reference guide | NARR |
NRD067 | The identifier of the party which does not report has invalid value #s | NARR |
NRD068 | The Principal Reporting Agent of the party #s should have the "NONREF" code | NARR |
NRD069 | The party with id = TradeRepository is not the Repository | NARR |
NRD070 | Several Reporting agents are indicated for the party #s with the same role type #s | NARR |
NRD071 | The specified employee is not authorized to submit and reconcile messages | NARR |
NRD072 | The Master Agreement should have two different parties or the clients of the parties should be specified. | NARR |
NRD073 | The party #s has no right to submit information on the Contract #s. The message is registered in the Log with the number N#s. | NARR |
NRD074 | The message for replacement/cancellation is not specified | NARR |
NRD075 | The date specified for the message to be cancelled does not coincide with the date of the message to cancel / replace | NARR |
NRD076 | The purpose of the message to be canceled does not coincide with the purpose of a message to cancel / replace | NARR |
NRD077 | The status #s is not found in the contracts forms status reference guide | NARR |
NRD078 | The Principle Reporting Agent of the client #s cannot be uniquely identified | NARR |
NRD079 | The field "Contract parameters reconciliation type" has invalid value | NARR |
NRD080 | Unable to identify Reporting agent with contract type #s for the party #s | NARR |
NRD081 | There is no active contract form with given parameters | NARR |
NRD082 | No other Reporting agents are allowed when Reporting agent is appointed for contract type #s and party #s | NARR |
NRD083 | The value of the field "Trade identifier" (tradeId) of the Master Agreement/contract assigned by the party #s should not be longer than 35 characters | NARR |
NRD084 | It is impossible to indicate as #s: #s #s | NARR |
NRD085 | The repository has moved to the new messages specification format. The submitted message does not correspond to the new format. Validation error of incoming message: #s | NARR |
NRD086 | The incorrect values for the href attributes or the fields Party1 and Party2 doesnt filled. | NARR |
NRD087 | The specified partyID code #s doesn't match with a mask. | NARR |
NRD088 | Only the repository can be a sender of the message | NARR |
NRD089 | Master Agreement with the number #s does not exist | NARR |
NRD090 | There are differences found when comparing xml documents | NARR |
NRD091 | Master Agreement parties cannot be the same as their clients | NARR |
NRD092 | The identifier of the Master Agreement (tradeId) assigned by the party #s can be no longer than 35 characters | NARR |
NRD093 | The identifier of the contract (tradeId) assigned by the party #s can be no longer than 35 characters | NARR |
NRD094 | "Trade parameters reconciliation type" shoul be filled out | NARR |
NRD095 | The message cannot be cancelled/replaced by the same message | NARR |
NRD096 | The code specified in correlationId #s does not match the sender's code #s | NARR |
NRD097 | The field "Reporting party role type" for the party #s should have the value #s | NARR |
NRD098 | Neither party is associated with the sender of the message | NARR |
NRD099 | The Reporting agent of the party #s cannot be identified by the code #s | NARR |
NRD100 | The repository service agreement with the participant #s has not been concluded yet. The message is registered in the Log with the number N#s. | NARR |
NRD101 | The repository service agreement with the participant #s has been terminated. The message is registered in the Log with the number N#s. | NARR |
NRD102 | Unable to find the Master agreement corresponding to the received contract data | NARR |
NRD103 | Wrong link to the corresponding Master Agreement form | NARR |
NRD104 | The contract form refers to the Master Agreement form which was rejected | NARR |
NRD105 | The counterparty of the Contract / Master agreement has deregistered the reporting form | NARR |
NRD106 | The message (in_msg_id = #s) with the sender's #s ID received from the sender #s already exists | NARR |
NRD107 | The field #s must be filled out | NARR |
NRD108 | It is impossible to identify the Reporting Agent of the party #s | NARR |
NRD109 | The code of the client #s which is not obliged to report should be specified | NARR |
NRD110 | Invalid value for the field <Unwillingreportingparty> for the client #s - #s | NARR |
NRD111 | Invalid value for the field <Unwillingreportingparty> because the client #s - #s is the Russian entity | NARR |
NRD112 | The party #s which is indicated in the field <Unwillingreportingparty> should have the same Principle Reporting Agent | NARR |
NRD113 | The Principle Reporting Agent of the party #s which is indicated in the field <Unwillingreportingparty> should be defined as NONREF | NARR |
NRD114 | Invalid value for the field <masterAgreementParty> #s if the party #s is not willing to report | NARR |
NRD115 | The code of the Reporting Agent of the party #s should be defined as #s | NARR |
NRD116 | The Reporting Agent #s - #s of the party #s which is not willing to report should coincide with the Reporting Agent of its counterparty (should have the same code and name). | NARR |
NRD117 | The version of the format is not defined in the message | NARR |
NRD118 | The message does not contain the action | NARR |
NRD119 | Invalid type of incoming message | NARR |
NRD120 | In case of ID with type #s the field <narrative> should not be filled | NARR |
NRD121 | In case of ID with type #s the field <narrative> should be filled | NARR |
NRD122 | There are several entries in the repository for the party with code #s and code type #s | NARR |
NRD123 | No client found for given parameters | NARR |
NRD124 | Code type #s is not found in the reference guide | NARR |
NRD125 | The message contains a link to the nonexistent related document | NARR |
NRD126 | The message should contain a link to the related document | NARR |
NRD127 | Invalid related document | NARR |
NRD128 | The Master Agreement/contract ID must be defined as NONREF | NARR |
NRD129 | It is impossible to cancel a message that has been executed/cancelled | NARR |
NRD130 | The message cannot be registered because in previous message № #s the Master Agreement form № #s with the same parameters and client IDs has been registered | NARR |
NRD131 | The message cannot be registered because in previous message № #s the Contract № #s with the same parameters and client IDs has been registered | NARR |
NRD132 | The field "Country code" should be filled out | NARR |
NRD133 | Invalid value of the field "Country code" #s | NARR |
NRD134 | The Reporting Agent for Unwilling reporting party should be set as Reporting Agent for reporting party, or remain unchanged, if Reporting Agent still a repositorys client, while changing Master Agreement | NARR |
NRD135 | The counterparty #s with the Reporting Agent #s couldn't be as Unwilling reporting party | NARR |
NRD136 | The Unwilling reporting party #s #s couldnt be specified as a payer. Only the reporting party could be as a payer | NARR |
NRD137 | The Principle Reporting Agent/Reporting Agent #s doesnt have EDT profile. The message #s #s | NARR |
NRD138 | #s is a repositorys client. To identify the side of the Master Agreement/Contracts required repositorys code #s | NARR |
NRD139 | The client with LEI code #s and short name #s has more than one repositorys code. To identify the side required specified the repositorys code too | NARR |
NRD140 | In the XML block cannot find a code with type #s, XML block: #s | NARR |
NRD141 | The XML block contains several codes with type #s, XML block: #s | NARR |
NRD142 | The ID #s, specified in partyId tag, doesnt match with type of ID #s for party #s #s | NARR |
NRD143 | For the party #s #s specified an invalid ID #s | NARR |
NRD144 | In the XML unit specified an invalid ID #s for Party identification. XML unit #s | NARR |
NRD145 | The incorrect partyId elements values specified in the XML unit. XML unit: #s | NARR |
NRD146 | A required type of ID #s is missing in the element partyId of the XML unit. XML unit: #s | NARR |
NRD147 | For the Client #s #s, who specified as #s, found an incorrect country code #s | NARR |
NRD148 | For the client ID #s, specified an incorrect country code #s | NARR |
NRD149 | The specified LEI code #s dont match with repositorys coe #s, for party #s. | NARR |
NRD150 | The wrong format. Root tag does not contain the prefix #s | NARR |
NRD151 | The block <TradeHeader> does not comply with the rules of message creation | NARR |
NRD152 | The document has already been confirmed | NARR |
NRD153 | Parties of the Contract don't correspond to the parties specified in the Master Agreement | NARR |
NRD154 | The counterparty with code #s does not match any party of the contract | NARR |
NRD155 | The #s field should be left blank, for the code value = NONREF | NARR |
NRD156 | The message type #s is missing in reference message types | NARR |
NRD157 | A message with the root tag #s not supported | NARR |
NRD161 | One or both of the partyId elements for Party #s is missing (Repositorys code and LEI code), but it should be mandatory specified for Party who are obligated to submit reports. | ICAG |
NRD162 | A document type #s not supported | NARR |
NRD163 | One or both of The Principle Reporting Agent identifiers for Party #s, does not match the identifiers specified in the registered master agreement | BFMT |
NRD164 | The identifier <partyId> for Party #s does not match the identifiers specified in the registered Trade/ Master agreement | BFMT |
NRD165 | An Incorrect contracts list. All specified contracts must be registered under same master agreement. | BFMT |
NRD166 | The Master Agreement number of contracts specified in the amendment form doesn't match with the Master Agreement number of the previously registered form. | BFMT |
NRD167 | The reporting party specified in the block #s doesn't match with the Partys name from whose side the message was sent. | BFMT |
NRD168 | It is unacceptable to specify the multiple contracts with the same number. | BFMT |
NRD169 | Specified an incorrect value for the field <asOfDate>/<valuationDate>. Registrations/Amendments for the form of report CM092/CM094 is only allowed in one reporting period. | BFMT |
NRD170 | A Message size reached the maximum allowed limit (15 mb). Please remove excess characters between fields (spaces, line breaks, etc.) from the XML file, or separate the message on several parts. | BFMT |
NRD171 | The clients identifier for the message/trades is missing or has an invalid value (NONREF). | BFMT |
NRD172 | There are one or several duplicates of trade identifiers. List of duplicates: #s | BFMT |
NRD173 | Sender #s has no right to submit messages with #s form. | BFMT |
NRD0174 | Messages with specified parameters are not found in the Messages register | NARR |
NRD175 | An Invalid period for the statement request. | BFMT |
NRD176 | The message cannot be registered because in previous message № #s the form of report № #s with the same valuation dates and client IDs has been registered | NARR |
NRD177 | Do not allow to specify multiple same values for the field <valuation Date> in the one form of report CM092 / CM094. | BFMT |
NRD178 | Additional Identifier #s, specified in the previously registered form does not match with the ID in the database #s, for the member with reposytorys identifier #s. | BFMT |
NRD179 | Specified an incorrect UTI code (#s).
Possible causes: exceeded the limit of 52 characters, the code does not comply with the mask, in the Repository already exists a message with the code, not found a related document by the code. | NARR |
NRD180 | The specified Reporting Agents may not be duplicated. | NARR |
NRD181 | A form of Reporting Agents assingment for the Client #s already registered in the Repository. To make changes, please submit an amendment to an existing form. | |
NRD182 | Specified an incorrect value of the field <Transfers And Execution>, during determination the functions of Reporting Agent - #s. The value true may be specified only if the reporting authority also cover document types like CM010 or CM015. | NARR |
NRD183 | The sender is not a Principle Reporting agent under Master agreement #s for the contract type #s | NARR |
NRD184 | Specified an incorrect value of the field <MarkToMarketValuation>, during determination the functions of Reporting Agent - #s. The value true may be specified only if the reporting authority exclude document types like CM010 or CM015. | NARR |
NRD185 | Registered CSA not found with specified repository's identifier. | NARR |
NRD186 | The specified clients identifier in the contract form for the report #s does not match with the identifier in the registered CSA. | NARR |
NRD187 | To enable the automatic execution report option of the contract, must specify values for the fields <startAgrementDate> and <endAgreementDate> | NARR |
NRD188 | Simultaneous specify <nonStandardTerms> field and link for Master Agreement is not allowed | NARR |
NRD189 | Specifying UTI code is required for this type of product. | NARR |
NRD190 | Specified an incorrect authority for one or several Reporting Agents: #s | NARR |
NRD191 | The member #s is not Reporting Agent for the Party #s | NARR |
NRD192 | Could not find any information about Reporting Agent, by an incoming message with the number #s and type #s | NARR |
NRD193 | Confirmation / rejection of a request for approval of authority Reporting Agent with code #s for the client with code #s has already been registered. | NARR |
NRD194 | Invalid LEI for UTI generating party | NARR |
RCDP001 | Several fields dont match | RCDP |
RCDP002 | The incorrect deal | RCDP |
RCDP003 | The clients repository code is invalid | RCDP |
RCDP004 | Other | RCDP |