AmendmentRejectionNotificationV03

tsmt.008.001.03

Scope The AmendmentRejectionNotification message is sent by the matching application to the requester of an amendment. This message is used to notify the rejection of an amendment request. Usage The AmendmentRejectionNotification message can be sent by the matching application to pass on information about the rejection of an amendment request that it has obtained through the receipt of an AmendmentRejection message. In order to pass on information about the acceptance of an amendment request the matching application sends an AmendmentAcceptanceNotification message.

Message Construction

Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification

classDiagram
     direction LR
%% AmendmentRejectionNotificationV03 recursion level 0 with max 0
AmendmentRejectionNotificationV03 *-- "1..1" MessageIdentification1 : NotificationIdentification
AmendmentRejectionNotificationV03 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification
AmendmentRejectionNotificationV03 *-- "1..1" DocumentIdentification3 : EstablishedBaselineIdentification
AmendmentRejectionNotificationV03 *-- "1..1" TransactionStatus4 : TransactionStatus
AmendmentRejectionNotificationV03 *-- "0..2" DocumentIdentification5 : UserTransactionReference
AmendmentRejectionNotificationV03 *-- "1..1" MessageIdentification1 : DeltaReportReference
AmendmentRejectionNotificationV03 *-- "1..1" Count1 : RejectedAmendmentNumber
AmendmentRejectionNotificationV03 *-- "1..1" BICIdentification1 : Initiator
AmendmentRejectionNotificationV03 *-- "1..1" IRejectionReason1Choice : RejectionReason
AmendmentRejectionNotificationV03 *-- "0..1" PendingActivity2 : RequestForAction
  

Now, we will zero-in one-by-one on each of these building blocks.

NotificationIdentification building block

Identifies the notification message. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MessageIdentification1 recursion level 0 with max 1
class MessageIdentification1{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
  

MessageIdentification1 members

Member name Description Data Type / Multiplicity
Identification Identification of the message. IsoMax35Text - Required 1..1
CreationDateTime Date of creation of the message. IsoISODateTime - Required 1..1

TransactionIdentification building block

Unique Identification assigned by the matching application to the transaction. This identification is to be used in any communication between the parties. . Information related to an identification, eg, party identification or account identification. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SimpleIdentificationInformation recursion level 0 with max 1
class SimpleIdentificationInformation{
    Identification IsoMax35Text
}
  

SimpleIdentificationInformation members

Member name Description Data Type / Multiplicity
Identification Name or number assigned by an entity to enable recognition of that entity, eg, account identifier. IsoMax35Text - Required 1..1

EstablishedBaselineIdentification building block

Unique identification assigned by the matching application to the baseline when it is established. Identifies a document by a unique identification and a version. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% DocumentIdentification3 recursion level 0 with max 1
class DocumentIdentification3{
    Identification IsoMax35Text
    Version IsoNumber
}
  

DocumentIdentification3 members

Member name Description Data Type / Multiplicity
Identification Identification of a set of data. IsoMax35Text - Required 1..1
Version Unambiguous identification of the version of a set of data. Example: Version 1. IsoNumber - Required 1..1

TransactionStatus building block

Identifies the status of the transaction by means of a code. Identifies the status of the transaction by means of a code. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TransactionStatus4 recursion level 0 with max 1
class TransactionStatus4{
    Status BaselineStatus3Code
}
  

TransactionStatus4 members

Member name Description Data Type / Multiplicity
Status Identifies the status of the transaction by means of a code. BaselineStatus3Code - Required 1..1

UserTransactionReference building block

Reference to the transaction for each financial institution which is a party to the transaction. Identifies a document by a unique identification and its issuer. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% DocumentIdentification5 recursion level 0 with max 1
class DocumentIdentification5{
    Identification IsoMax35Text
}
DocumentIdentification5 *-- "1..1" BICIdentification1 : IdentificationIssuer
%% BICIdentification1 recursion level 1 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}
  

DocumentIdentification5 members

Member name Description Data Type / Multiplicity
Identification Identification of a set of data. IsoMax35Text - Required 1..1
IdentificationIssuer Uniquely identifies the financial institution which has issued the identification of the set of data by using a BIC. BICIdentification1 - Required 1..1

DeltaReportReference building block

Reference to the identification of the delta report that contained the amendment. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MessageIdentification1 recursion level 0 with max 1
class MessageIdentification1{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
  

MessageIdentification1 members

Member name Description Data Type / Multiplicity
Identification Identification of the message. IsoMax35Text - Required 1..1
CreationDateTime Date of creation of the message. IsoISODateTime - Required 1..1

RejectedAmendmentNumber building block

Sequence number of the rejected baseline amendment. Specifies a sequence number or a total. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Count1 recursion level 0 with max 1
class Count1{
    Number IsoNumber
}
  

Count1 members

Member name Description Data Type / Multiplicity
Number Sequence or total number. IsoNumber - Required 1..1

Initiator building block

Party that has rejected the amendment. Unique and unambiguous identifier of a financial institution, as assigned under an internationally recognised or proprietary identification scheme. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% BICIdentification1 recursion level 0 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}
  

BICIdentification1 members

Member name Description Data Type / Multiplicity
BIC Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 “Banking - Banking telecommunication messages - Business identifier code (BIC)”. IsoBICIdentifier - Required 1..1

RejectionReason building block

Specifies the reaons for rejecting the amendment. Allows the sender of the rejection message to indicate only one rejection reason that applies to the entire rejected message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IRejectionReason1Choice recursion level 0 with max 1
  

RejectionReason1Choice members

Member name Description Data Type / Multiplicity

RequestForAction building block

Information on the next processing step required. Specifies the event that require an action from one of the parties to the trade transaction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PendingActivity2 recursion level 0 with max 1
class PendingActivity2{
    Type Action2Code
    Description IsoMax140Text
}
  

PendingActivity2 members

Member name Description Data Type / Multiplicity
Type Code which specifies the next course of action that the receiver of the message must take. Action2Code - Required 1..1
Description Further information on the course of action that the receiver of the message must take. IsoMax140Text - Optional 0..1

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the AmendmentRejectionNotificationV03 implementation follows a specific implementaiton pattern. First of all, AmendmentRejectionNotificationV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AmendmentRejectionNotificationV03Document implements IOuterDocument. Because AmendmentRejectionNotificationV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AmendmentRejectionNotificationV03.

classDiagram
    class IOuterRecord
    AmendmentRejectionNotificationV03 --|> IOuterRecord : Implements
    AmendmentRejectionNotificationV03Document --|> IOuterDocument~AmendmentRejectionNotificationV03~ : Implements
    class IOuterDocument~AmendmentRejectionNotificationV03~ {
        AmendmentRejectionNotificationV03 Message
     }
  

Document wrapper for serialization

The only real purpose AmendmentRejectionNotificationV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:tsmt.008.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AmendmentRejectionNotificationV03.ToDocument() method. The returned AmendmentRejectionNotificationV03Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    AmendmentRejectionNotificationV03Document *-- AmendmentRejectionNotificationV03 : Document
  

Sample of message format

This is an abbreviated version of what the message should look like.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:tsmt.008.001.03">
    <AmdmntRjctnNtfctn>
        <NtfctnId>
            <!-- NotificationIdentification inner content -->
        </NtfctnId>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <EstblishdBaselnId>
            <!-- EstablishedBaselineIdentification inner content -->
        </EstblishdBaselnId>
        <TxSts>
            <!-- TransactionStatus inner content -->
        </TxSts>
        <UsrTxRef>
            <!-- UserTransactionReference inner content -->
        </UsrTxRef>
        <DltaRptRef>
            <!-- DeltaReportReference inner content -->
        </DltaRptRef>
        <RjctdAmdmntNb>
            <!-- RejectedAmendmentNumber inner content -->
        </RjctdAmdmntNb>
        <Initr>
            <!-- Initiator inner content -->
        </Initr>
        <RjctnRsn>
            <!-- RejectionReason inner content -->
        </RjctnRsn>
        <ReqForActn>
            <!-- RequestForAction inner content -->
        </ReqForActn>
    </AmdmntRjctnNtfctn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_kPGaiNE8Ed-BzquC8wXy7w_-267112267"
  name="AmendmentRejectionNotificationV03"
  definition="Scope&#xD;&#xA;The AmendmentRejectionNotification message is sent by the matching application to the requester of an amendment.&#xD;&#xA;This message is used to notify the rejection of an amendment request.&#xD;&#xA;Usage&#xD;&#xA;The AmendmentRejectionNotification message can be sent by the matching application to pass on information about the rejection of an amendment request that it has obtained through the receipt of an AmendmentRejection message.&#xD;&#xA;In order to pass on information about the acceptance of an amendment request the matching application sends an AmendmentAcceptanceNotification message."
  registrationStatus="Registered"
  messageSet="_wRx2yk2rEeG_I4xRYCA_7g _1a374FXOEeOkkLyrDUP66g"
  xmlTag="AmdmntRjctnNtfctn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_kPGaidE8Ed-BzquC8wXy7w_-266192003"
    name="NotificationIdentification"
    definition="Identifies the notification message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="NtfctnId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_kPGaitE8Ed-BzquC8wXy7w_-267112171"
    name="TransactionIdentification"
    definition="Unique Identification assigned by the matching application to the transaction.&#xA;This identification is to be used in any communication between the parties.&#xA;."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TxId"
    complexType="_P-ile9p-Ed-ak6NoX_4Aeg_745508310" />
  <messageBuildingBlock
    xmi:id="_kPQLgNE8Ed-BzquC8wXy7w_-266191475"
    name="EstablishedBaselineIdentification"
    definition="Unique identification assigned by the matching application to the baseline when it is established."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="EstblishdBaselnId"
    complexType="_RJNBwdp-Ed-ak6NoX_4Aeg_-1127047102" />
  <messageBuildingBlock
    xmi:id="_kPQLgdE8Ed-BzquC8wXy7w_-266191149"
    name="TransactionStatus"
    definition="Identifies the status of the transaction by means of a code."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TxSts"
    complexType="_RbFb-Np-Ed-ak6NoX_4Aeg_1598523783" />
  <messageBuildingBlock
    xmi:id="_kPQLgtE8Ed-BzquC8wXy7w_-266191055"
    name="UserTransactionReference"
    definition="Reference to the transaction for each financial institution which is a party to the transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="2"
    minOccurs="0"
    xmlTag="UsrTxRef"
    complexType="_RJWLsdp-Ed-ak6NoX_4Aeg_-86119846" />
  <messageBuildingBlock
    xmi:id="_kPQLg9E8Ed-BzquC8wXy7w_-266192097"
    name="DeltaReportReference"
    definition="Reference to the identification of the delta report that contained the amendment."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="DltaRptRef"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_kPQLhNE8Ed-BzquC8wXy7w_-266190976"
    name="RejectedAmendmentNumber"
    definition="Sequence number of the rejected baseline amendment."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RjctdAmdmntNb"
    complexType="_RJDQxNp-Ed-ak6NoX_4Aeg_1838853440" />
  <messageBuildingBlock
    xmi:id="_kPQLhdE8Ed-BzquC8wXy7w_871587777"
    name="Initiator"
    definition="Party that has rejected the amendment."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Initr"
    complexType="_QEp0kNp-Ed-ak6NoX_4Aeg_792527554" />
  <messageBuildingBlock
    xmi:id="_kPQLhtE8Ed-BzquC8wXy7w_-267112249"
    name="RejectionReason"
    definition="Specifies the reaons for rejecting the amendment."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RjctnRsn"
    complexType="_RJ8ooNp-Ed-ak6NoX_4Aeg_891683676" />
  <messageBuildingBlock
    xmi:id="_kPQLh9E8Ed-BzquC8wXy7w_-266191570"
    name="RequestForAction"
    definition="Information on the next processing step required."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="ReqForActn"
    complexType="_RaowBtp-Ed-ak6NoX_4Aeg_-888447978" />
  <messageDefinitionIdentifier
    businessArea="tsmt"
    messageFunctionality="008"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.