MisMatchAcceptanceNotificationV03

tsmt.021.001.03

Scope The MisMatchAcceptanceNotification message is sent by the matching application to the parties involved in the transaction. This message is used to notify the acceptance of mis-matched data sets. Usage The MisMatchAcceptanceNotification message can be sent by the matching application to pass on information about the acceptance of mis-matched data sets that it has obtained through the receipt of an MisMatchAcceptance message. In order to pass on information about the rejection of mis-matched data sets the matching application sends a MisMatchRejectionNotification 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
%% MisMatchAcceptanceNotificationV03 recursion level 0 with max 0
MisMatchAcceptanceNotificationV03 *-- "1..1" MessageIdentification1 : NotificationIdentification
MisMatchAcceptanceNotificationV03 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification
MisMatchAcceptanceNotificationV03 *-- "1..1" DocumentIdentification3 : EstablishedBaselineIdentification
MisMatchAcceptanceNotificationV03 *-- "1..1" TransactionStatus4 : TransactionStatus
MisMatchAcceptanceNotificationV03 *-- "0..2" DocumentIdentification5 : UserTransactionReference
MisMatchAcceptanceNotificationV03 *-- "1..1" MessageIdentification1 : DataSetMatchReportReference
MisMatchAcceptanceNotificationV03 *-- "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

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

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

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

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

DataSetMatchReportReference building block

Reference to the identification of the report that contained the difference. 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

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

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    MisMatchAcceptanceNotificationV03 --|> IOuterRecord : Implements
    MisMatchAcceptanceNotificationV03Document --|> IOuterDocument~MisMatchAcceptanceNotificationV03~ : Implements
    class IOuterDocument~MisMatchAcceptanceNotificationV03~ {
        MisMatchAcceptanceNotificationV03 Message
     }
  

Document wrapper for serialization

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

classDiagram
    MisMatchAcceptanceNotificationV03Document *-- MisMatchAcceptanceNotificationV03 : 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.021.001.03">
    <MisMtchAccptncNtfctn>
        <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>
        <DataSetMtchRptRef>
            <!-- DataSetMatchReportReference inner content -->
        </DataSetMtchRptRef>
        <ReqForActn>
            <!-- RequestForAction inner content -->
        </ReqForActn>
    </MisMtchAccptncNtfctn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_rLAcuNE8Ed-BzquC8wXy7w_2021244556"
  name="MisMatchAcceptanceNotificationV03"
  definition="Scope&#xD;&#xA;The MisMatchAcceptanceNotification message is sent by the matching application to the parties involved in the transaction.&#xD;&#xA;This message is used to notify the acceptance of mis-matched data sets.&#xD;&#xA;Usage&#xD;&#xA;The MisMatchAcceptanceNotification message can be sent by the matching application to pass on information about the acceptance of mis-matched data sets that it has obtained through the receipt of an MisMatchAcceptance message.&#xD;&#xA;In order to pass on information about the rejection of mis-matched data sets the matching application sends a MisMatchRejectionNotification message."
  registrationStatus="Registered"
  messageSet="_wRx2yk2rEeG_I4xRYCA_7g _1a374FXOEeOkkLyrDUP66g"
  xmlTag="MisMtchAccptncNtfctn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_rLKNsNE8Ed-BzquC8wXy7w_2021244988"
    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="_rLKNsdE8Ed-BzquC8wXy7w_2021244957"
    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="_rLKNstE8Ed-BzquC8wXy7w_2021244896"
    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="_rLKNs9E8Ed-BzquC8wXy7w_2021244927"
    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="_rLKNtNE8Ed-BzquC8wXy7w_2021244587"
    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="_rLKNtdE8Ed-BzquC8wXy7w_2021244566"
    name="DataSetMatchReportReference"
    definition="Reference to the identification of the report that contained the difference."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="DataSetMtchRptRef"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_rLKNttE8Ed-BzquC8wXy7w_2021244865"
    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="021"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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