MisMatchRejectionV02

tsmt.022.001.02

Scope The MisMatchRejection message is sent by the party requested to accept or reject data set mis-matches to the matching application. This message is used to reject mis-matches between data sets and the related baseline. Usage The MisMatchRejection message can be sent by the party requested to accept or reject data set mis-match to inform that it rejects the data set(s). The message can be sent in response to a DataSetMatchReport message conveying mis-matches. The information about the rejection of the mis-matched data sets will be forwarded by the matching application to the submitter of the data sets by a MisMatchRejectionNotification message. The acceptance of mis-matched data sets can be achieved by sending a MisMatchAcceptance 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
%% MisMatchRejectionV02 recursion level 0 with max 0
MisMatchRejectionV02 *-- "1..1" MessageIdentification1 : RejectionIdentification
MisMatchRejectionV02 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification
MisMatchRejectionV02 *-- "0..1" SimpleIdentificationInformation : SubmitterTransactionReference
MisMatchRejectionV02 *-- "1..1" MessageIdentification1 : DataSetMatchReportReference
MisMatchRejectionV02 *-- "1..1" IRejectionReason1Choice : RejectionReason
  

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

RejectionIdentification building block

Identifies the rejection 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

SubmitterTransactionReference building block

Reference to the transaction for the requesting financial institution. 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

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

RejectionReason building block

Reason why the user cannot accept the request. 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

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    MisMatchRejectionV02 --|> IOuterRecord : Implements
    MisMatchRejectionV02Document --|> IOuterDocument~MisMatchRejectionV02~ : Implements
    class IOuterDocument~MisMatchRejectionV02~ {
        MisMatchRejectionV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    MisMatchRejectionV02Document *-- MisMatchRejectionV02 : 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.022.001.02">
    <MisMtchRjctn>
        <RjctnId>
            <!-- RejectionIdentification inner content -->
        </RjctnId>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <SubmitrTxRef>
            <!-- SubmitterTransactionReference inner content -->
        </SubmitrTxRef>
        <DataSetMtchRptRef>
            <!-- DataSetMatchReportReference inner content -->
        </DataSetMtchRptRef>
        <RjctnRsn>
            <!-- RejectionReason inner content -->
        </RjctnRsn>
    </MisMtchRjctn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_scq46NE8Ed-BzquC8wXy7w_1101360695"
  name="MisMatchRejectionV02"
  definition="Scope&#xD;&#xA;The MisMatchRejection message is sent by the party requested to accept or reject data set mis-matches to the matching application.&#xD;&#xA;This message is used to reject mis-matches between data sets and the related baseline.&#xD;&#xA;Usage&#xD;&#xA;The MisMatchRejection message can be sent by the party requested to accept or reject data set mis-match to inform that it rejects the data set(s).&#xD;&#xA;The message can be sent in response to a DataSetMatchReport message conveying mis-matches.&#xD;&#xA;The information about the rejection of the mis-matched data sets will be forwarded by the matching application to the submitter of the data sets by a MisMatchRejectionNotification message.&#xD;&#xA;The acceptance of mis-matched data sets can be achieved by sending a MisMatchAcceptance message."
  registrationStatus="Registered"
  messageSet="_wRx2yk2rEeG_I4xRYCA_7g _1a374FXOEeOkkLyrDUP66g"
  xmlTag="MisMtchRjctn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_scq46dE8Ed-BzquC8wXy7w_1101360850"
    name="RejectionIdentification"
    definition="Identifies the rejection message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RjctnId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_scq46tE8Ed-BzquC8wXy7w_1101360765"
    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."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TxId"
    complexType="_P-ile9p-Ed-ak6NoX_4Aeg_745508310" />
  <messageBuildingBlock
    xmi:id="_scq469E8Ed-BzquC8wXy7w_1101360819"
    name="SubmitterTransactionReference"
    definition="Reference to the transaction for the requesting financial institution."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SubmitrTxRef"
    complexType="_P-ile9p-Ed-ak6NoX_4Aeg_745508310" />
  <messageBuildingBlock
    xmi:id="_sc0C0NE8Ed-BzquC8wXy7w_1101360734"
    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="_sc0C0dE8Ed-BzquC8wXy7w_1101360788"
    name="RejectionReason"
    definition="Reason why the user cannot accept the request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RjctnRsn"
    complexType="_RJ8ooNp-Ed-ak6NoX_4Aeg_891683676" />
  <messageDefinitionIdentifier
    businessArea="tsmt"
    messageFunctionality="022"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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