tsmt.020.001.02
Scope The MisMatchAcceptance message is sent by the party requested to accept or reject data set mis-matches to the matching application. This message is used to accept mis-matches between data sets and the related baseline. Usage The MisMatchAcceptance message can be sent by the party requested to accept or reject data set mis-matches to inform that it accepts the data sets. The message can be sent in response to a DataSetMatchReport message conveying mis-matches. The information about the acceptance of the mis-matched data sets will be forwarded by the matching application to the submitter of the data sets by a MisMatchAcceptanceNotification message. The rejection of mis-matched data sets can be achieved by sending a MisMatchRejection 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
%% MisMatchAcceptanceV02 recursion level 0 with max 0
MisMatchAcceptanceV02 *-- "1..1" MessageIdentification1 : AcceptanceIdentification
MisMatchAcceptanceV02 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification
MisMatchAcceptanceV02 *-- "0..1" SimpleIdentificationInformation : SubmitterTransactionReference
MisMatchAcceptanceV02 *-- "1..1" MessageIdentification1 : DataSetMatchReportReference
Now, we will zero-in one-by-one on each of these building blocks.
AcceptanceIdentification building block
Identifies the acceptance 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 |
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
| 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 |
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
| 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 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the MisMatchAcceptanceV02 implementation follows a specific implementaiton pattern. First of all, MisMatchAcceptanceV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MisMatchAcceptanceV02Document implements IOuterDocument. Because MisMatchAcceptanceV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MisMatchAcceptanceV02.
classDiagram
class IOuterRecord
MisMatchAcceptanceV02 --|> IOuterRecord : Implements
MisMatchAcceptanceV02Document --|> IOuterDocument~MisMatchAcceptanceV02~ : Implements
class IOuterDocument~MisMatchAcceptanceV02~ {
MisMatchAcceptanceV02 Message
}
Document wrapper for serialization
The only real purpose MisMatchAcceptanceV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:tsmt.020.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MisMatchAcceptanceV02.ToDocument() method. The returned MisMatchAcceptanceV02Document value will serialize correctly according to ISO 20022 standards.
classDiagram
MisMatchAcceptanceV02Document *-- MisMatchAcceptanceV02 : 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.020.001.02">
<MisMtchAccptnc>
<AccptncId>
<!-- AcceptanceIdentification inner content -->
</AccptncId>
<TxId>
<!-- TransactionIdentification inner content -->
</TxId>
<SubmitrTxRef>
<!-- SubmitterTransactionReference inner content -->
</SubmitrTxRef>
<DataSetMtchRptRef>
<!-- DataSetMatchReportReference inner content -->
</DataSetMtchRptRef>
</MisMtchAccptnc>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_rmuIWNE8Ed-BzquC8wXy7w_-505567278"
name="MisMatchAcceptanceV02"
definition="Scope
The MisMatchAcceptance message is sent by the party requested to accept or reject data set mis-matches to the matching application.
This message is used to accept mis-matches between data sets and the related baseline.
Usage
The MisMatchAcceptance message can be sent by the party requested to accept or reject data set mis-matches to inform that it accepts the data sets.
The message can be sent in response to a DataSetMatchReport message conveying mis-matches.
The information about the acceptance of the mis-matched data sets will be forwarded by the matching application to the submitter of the data sets by a MisMatchAcceptanceNotification message.
The rejection of mis-matched data sets can be achieved by sending a MisMatchRejection message."
registrationStatus="Registered"
messageSet="_wRx2yk2rEeG_I4xRYCA_7g _1a374FXOEeOkkLyrDUP66g"
xmlTag="MisMtchAccptnc"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_rmuIWdE8Ed-BzquC8wXy7w_-505566937"
name="AcceptanceIdentification"
definition="Identifies the acceptance message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="AccptncId"
complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
<messageBuildingBlock
xmi:id="_rmuIWtE8Ed-BzquC8wXy7w_-505567246"
name="TransactionIdentification"
definition="Unique identification assigned by the matching application to the transaction.
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="_rm35UNE8Ed-BzquC8wXy7w_-505567275"
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="_rm35UdE8Ed-BzquC8wXy7w_-505567215"
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" />
<messageDefinitionIdentifier
businessArea="tsmt"
messageFunctionality="020"
flavour="001"
version="02" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.