eventIdentifier | BusinessEventIdentifier | Individual 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-∞,
ncf | This is not used in messages to the repository. |
trade | Trade | A full description of the amended trade (i.e. the trade after the amendment). | Trade details. | | 1-1,
mre | |
agreementDate | xsd:date | The date on which the change was agreed. | Change agreed date | | 0-1,
mre,
mfr | |
executionDateTime | ExecutionDateTime | The 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 confirmed | | 0-1,
ncf | This is not used in messages to the repository. |
effectiveDate | xsd:date | The date on which the change become effective. | Amendment effective date | | 0-1,
mfr | |
payment | Payment | Describes 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.
| Payment | | 0-∞,
afr | |