NSD’s trade repository messages specifications

Current specification

EquitySimpleTransaction

A type for defining simple equity spot or term transaction.

FieldTypeDescriptionPrint form titleFFSM titlePropertiesConditions
primaryAssetCl​assAssetClassA classification of the most important risk class of the trade.Primary asset class.0-1, ncfAt the first stage this element is not used in the repository messages.
secondaryAsset​ClassAssetClassA classification of additional risk classes of the trade, if any.Secondary asset class.0-∞, ncfAt the first stage this element is not used in the repository messages.
productTypeProductTypeA classification of the type of product.Product type.Derivative instrument type.0-∞, mre, mfrThis element is mandatory for NSD messages, except for messages, related to master agreement registration.
productIdProductIdA product reference identifier. The product ID is an identifier that describes the key economic characteristics of the trade type, with the exception of concepts such as size (notional, quantity, number of units) and price (fixed rate, strike, etc.) that are negotiated for each transaction. It can be used to hold identifiers such as the "UPI" (universal product identifier) required by certain regulatory reporting rules. It can also be used to hold identifiers of benchmark products or product temnplates used by certain trading systems or facilities. Derivatives classification code.Classification code of the derivative financial instrument.0-∞, mre, mfrMandatory field for NSD messages, except for messages, related to the registration of master agreements, repo transactions and quarterly representation of trades exercised within 4 working days period. This is used to hold classification codes for derivatives transactions required by FFMS.
embeddedOption​TypeEmbeddedOption​TypeDescribes the type of any embedded optionality in the transaction that might not otherwise be apparent. Can be used to represent embedded optionality such as early termination provisions, extendible provisions, or cancelable provisions, etc., where applicable. If omitted, no embedded optionality is applicable. Embedded option type.0-2, ncfOptional field for NSD repository messages. It is not used in messages, related to the registration of master agreements and quarterly representation of trades exercised within 4 working days period. This is used only if trade terms include embedded option of a type specified in the coding scheme. At the first stage this element is not used in the repository messages.
@idxsd:ID1-1
buyerPartyRefe​rencePartyReferenceA reference to the party that buys this instrument, ie. pays for this instrument and receives the rights defined by it. See 2000 ISDA definitions Article 11.1 (b). In the case of FRAs this the fixed rate payer. Buyer party.Party code.0-1, mre, mfr
buyerAccountRe​ferenceAccountReferen​ceA reference to the account that buys this instrument.Buyer's account.Party's client.0-1, ncfAt the first stage this element is not used in the repository messages.
sellerPartyRef​erencePartyReferenceA reference to the party that sells ("writes") this instrument, i.e. that grants the rights defined by this instrument and in return receives a payment for it. See 2000 ISDA definitions Article 11.1 (a). In the case of FRAs this is the floating rate payer. Seller party.Party code.0-1, mre, mfr
sellerAccountR​eferenceAccountReferen​ceA reference to the account that sells this instrument.Seller's account.Party's client.0-1, ncfAt the first stage this element is not used in the repository messages.
numberOfUnitsxsd:decimalThe number of units (index or securities).Number of units.1-1, mre, mfr
unitPriceMoneyThe price of each unit. Some Transactions may have zero upfront cost.Unit price.1-1, mre
equityEquityAssetIdentification of a Equity.Equity.1-1, mre
termPeriodDefines a trade term by specifying period multiplier and period type.Trade term.0-1
deliveryMethodDeliveryMethod​EnumSpecifies the delivery method. There is a business rule associated with this field: if deliveryMethod is DVP then there must be specified an equal value of the elements settlementDate and deliveryDate. It is incorrect to specify DVP and indicate different dates for cash and security transfers. Delivery method.0-1, afr
settlementDateAdjustableOrRe​lativeDateA date of settlements on a security transaction.Settlement date.1-1, mre
deliveryDateAdjustableOrRe​lativeDateA date of delivery on a security transaction. It is not required to be included if this is equal to the date of settlement on the given transaction. Delivery date.0-1
EquitySimpleTransaction