NSD’s trade repository messages specifications

Current specification

TradeAmendmentContent

A structure describing a negotiated amendment.

FieldTypeDescriptionPrint form titleFFSM titlePropertiesConditions
eventIdentifierBusinessEventI​dentifierIndividual parties should only use a single event identifier to identify a retraction. Platforms providing services on behalf of both parties in a transaction may provide event identifiers for both parties; in this case it is up to the recipient (the trade repository) to validate that the event IDs refer to the same event. Business event identifier.0-∞, ncfThis is not used in messages to the repository.
tradeTradeA full description of the amended trade (i.e. the trade after the amendment).Trade details.1-1, mre
agreementDatexsd:dateThe date on which the change was agreed.Change agreed date0-1, mre, mfr
executionDateT​imeExecutionDateT​imeThe date and time at which the negotiated change to the terms of the original contract was agreed, such as via telephone or electronic trading system (i.e., agreement date/time). Time when change negotiation was confirmed0-1, ncfThis is not used in messages to the repository.
effectiveDatexsd:dateThe date on which the change become effective.Amendment effective date0-1, mfr
paymentPaymentDescribes a payment made in settlement of the change. Normally there will be a single fee, but there could be additional payments such as principal exchanges resulting from the termination. Payment0-∞, afr
TradeAmendmentContent