NSD’s trade repository messages specifications

Current specification

Repo

A type defining Repo transaction, modeled as an FpML:Product.

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
Choice begin
Branch1
fixedRateSched​uleScheduleThe fixed repo rate. It is usually fixed for the duration of the agreement but can be changed with mid-life events (rate changes) except for Buy SellBack trades. Fixed rate schedule.Fixed repo rate; Amortization / increase code.1-1, mre
Branch2
floatingRateCa​lculationFloatingRateCa​lculationThe float index and tenor, with a spread. Use for floating rate repos. Most floatings in Europe are against EONIA. Floating rate calculation.Floating repo rate; Amortization / increase code; Cap rate; Floor rate.1-1, mre
Choice end
dayCountFracti​onDayCountFracti​onThe day count fraction.Day count fraction.1-1, mre, mfr
noticePeriodAdjustableOffs​etNotice period for open ended or long dated repos in number of days.Notice period.0-1, ncf
durationRepoDurationEn​umA duration code for the repo contract.Repo duration type.1-1, mre, mfr
marginMarginThe margin, or haircut, that will be applied.Collateral ratio0-1, ncf
spotLegRepoTransactio​nLegNsdA repo contract is modelled as two purchase/repurchase transactions which are called legs. This is the spot leg, i.e. the transaction that will be executed on the settlement date of the contract. Repo spot leg.1-1, mre
forwardLegForwardRepoTra​nsactionLegNsdThe forward leg of the repo contract, i.e. the repurchase transaction.Repo forward leg.0-1, mreConditionally filled element. This is to be included in case of reporting information about repo forward leg except for open repo transaction. In case of open repo transaction this is not supposed to be used.
midLifeEventField must be replaced by one of next elments: cashRepricing, couponEvent, collateralSubstitution, interestPayout, markToMarketEvent, rateChange, rateObservation, 0-∞, ncf
Choice begin
Branch1
Choice begin
Branch1
bondBondIdentifies the underlying asset when it is a series or a class of bonds.Bond.1-1
Branch2
convertibleBondConvertibleBondIdentifies the underlying asset when it is a convertible bond.Convertible bond.1-1, ncfAt the first stage this element is not used in the repository messages.
Choice end
Branch2
equityEquityAssetAn exchange traded equity asset.Equity.1-1
Choice end
settlementTran​sferSettlementTran​sferParticipants may choose to explicitly specify the different financial exchanges that the product represents. This is the equivalent of the cashflow-explicit representation of an interest rate swap. In this case it is possible to give a transfer-explicit representation of a repo contract for settlement purposes. Settlement transfers.0-1, ncfThis is not used in messages to the repository.
Repo
The type RepoNsd which is inheritor to this type is used in messages to the repository.