BaselineMatchReportV03

tsmt.010.001.03

Scope The BaselineMatchReport message is sent by the matching application to the parties involved in the establishment of a transaction. The message is used to inform about either the successful establishment of a transaction (baseline) or the mis-matches found between two baseline initiation messages. Usage The BaselineMatchReport message can be sent by the matching application to

• the parties involved in the establishment of a transaction in the push-through mode, that is the senders of InitialBaselineSubmission and BaselineReSubmission messages including the instruction push-through. In the outlined scenario the message is used to inform either about the successful establishment of a transaction in the matching application or about mis-matches found between two baseline initiation messages,or
• the party establishing a transaction in the lodge mode, that is the sender of an InitialBaselineSubmission message including the instruction lodge. In the outlined scenario the message is used to inform about the successful establishment of a transaction in the matching application.

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
%% BaselineMatchReportV03 recursion level 0 with max 0
BaselineMatchReportV03 *-- "1..1" MessageIdentification1 : ReportIdentification
BaselineMatchReportV03 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification
BaselineMatchReportV03 *-- "0..1" DocumentIdentification3 : EstablishedBaselineIdentification
BaselineMatchReportV03 *-- "1..1" TransactionStatus4 : TransactionStatus
BaselineMatchReportV03 *-- "0..2" DocumentIdentification5 : UserTransactionReference
BaselineMatchReportV03 *-- "1..1" PartyIdentification26 : Buyer
BaselineMatchReportV03 *-- "1..1" PartyIdentification26 : Seller
BaselineMatchReportV03 *-- "1..1" BICIdentification1 : BuyerBank
BaselineMatchReportV03 *-- "1..1" BICIdentification1 : SellerBank
BaselineMatchReportV03 *-- "1..1" Limit1 : BaselineEstablishmentTrials
BaselineMatchReportV03 *-- "2..2" DocumentIdentification4 : ComparedDocumentReference
BaselineMatchReportV03 *-- "1..1" MisMatchReport3 : Report
BaselineMatchReportV03 *-- "0..1" PendingActivity2 : RequestForAction
  

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

ReportIdentification building block

Identifies the report. 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

Buyer building block

Party that buys goods or services, or a financial instrument. Entity involved in an activity. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PartyIdentification26 recursion level 0 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% GenericIdentification4 recursion level 1 with max 1
class GenericIdentification4{
    Identification IsoMax35Text
    IdentificationType IsoMax35Text
}
%% PostalAddress5 recursion level 1 with max 1
class PostalAddress5{
    StreetName IsoMax70Text
    PostCodeIdentification IsoMax16Text
    TownName IsoMax35Text
    CountrySubDivision IsoMax35Text
    Country CountryCode
}
  

PartyIdentification26 members

Seller building block

Party that sells goods or services, or a financial instrument. Entity involved in an activity. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PartyIdentification26 recursion level 0 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% GenericIdentification4 recursion level 1 with max 1
class GenericIdentification4{
    Identification IsoMax35Text
    IdentificationType IsoMax35Text
}
%% PostalAddress5 recursion level 1 with max 1
class PostalAddress5{
    StreetName IsoMax70Text
    PostCodeIdentification IsoMax16Text
    TownName IsoMax35Text
    CountrySubDivision IsoMax35Text
    Country CountryCode
}
  

PartyIdentification26 members

BuyerBank building block

The financial institution of the buyer, uniquely identified by its BIC. 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

SellerBank building block

The financial institution of the seller, uniquely identified by its BIC. 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

BaselineEstablishmentTrials building block

Specifies the number of matching trials for a baseline. Specifies the number of occurrences of a particular event and the maximum number of times this event may occur. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Limit1 recursion level 0 with max 1
class Limit1{
    Current IsoMax3NumericText
    Limit IsoMax3NumericText
}
  

Limit1 members

ComparedDocumentReference building block

Identifies the two baselines compared in this report. Identifies a document by a unique identification and a version together with the submitter of the document. Also specifies an index for easy referencing. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% DocumentIdentification4 recursion level 0 with max 1
class DocumentIdentification4{
    Identification IsoMax35Text
    Version IsoNumber
    DocumentIndex IsoMax3NumericText
}
DocumentIdentification4 *-- "1..1" BICIdentification1 : Submitter
%% BICIdentification1 recursion level 1 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}
  

DocumentIdentification4 members

Report building block

Description of the differences between the two proposed baselines. Description of the mis-matched situation between two baselines or between a baseline and a data set. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MisMatchReport3 recursion level 0 with max 1
class MisMatchReport3{
    NumberOfMisMatches IsoNumber
}
MisMatchReport3 *-- "0..0" ValidationResult5 : MisMatchInformation
%% ValidationResult5 recursion level 1 with max 1
class ValidationResult5{
    SequenceNumber IsoNumber
    RuleIdentification IsoMax35Text
    RuleDescription IsoMax350Text
}
ValidationResult5 *-- "0..0" ElementIdentification1 : MisMatchedElement
  

MisMatchReport3 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 BaselineMatchReportV03 implementation follows a specific implementaiton pattern. First of all, BaselineMatchReportV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, BaselineMatchReportV03Document implements IOuterDocument. Because BaselineMatchReportV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type BaselineMatchReportV03.

classDiagram
    class IOuterRecord
    BaselineMatchReportV03 --|> IOuterRecord : Implements
    BaselineMatchReportV03Document --|> IOuterDocument~BaselineMatchReportV03~ : Implements
    class IOuterDocument~BaselineMatchReportV03~ {
        BaselineMatchReportV03 Message
     }
  

Document wrapper for serialization

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

classDiagram
    BaselineMatchReportV03Document *-- BaselineMatchReportV03 : 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.010.001.03">
    <BaselnMtchRpt>
        <RptId>
            <!-- ReportIdentification inner content -->
        </RptId>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <EstblishdBaselnId>
            <!-- EstablishedBaselineIdentification inner content -->
        </EstblishdBaselnId>
        <TxSts>
            <!-- TransactionStatus inner content -->
        </TxSts>
        <UsrTxRef>
            <!-- UserTransactionReference inner content -->
        </UsrTxRef>
        <Buyr>
            <!-- Buyer inner content -->
        </Buyr>
        <Sellr>
            <!-- Seller inner content -->
        </Sellr>
        <BuyrBk>
            <!-- BuyerBank inner content -->
        </BuyrBk>
        <SellrBk>
            <!-- SellerBank inner content -->
        </SellrBk>
        <BaselnEstblishmtTrils>
            <!-- BaselineEstablishmentTrials inner content -->
        </BaselnEstblishmtTrils>
        <CmpardDocRef>
            <!-- ComparedDocumentReference inner content -->
        </CmpardDocRef>
        <Rpt>
            <!-- Report inner content -->
        </Rpt>
        <ReqForActn>
            <!-- RequestForAction inner content -->
        </ReqForActn>
    </BaselnMtchRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_lhzYiNE8Ed-BzquC8wXy7w_-1930237011"
  name="BaselineMatchReportV03"
  definition="Scope&#xD;&#xA;The BaselineMatchReport message is sent by the matching application to the parties involved in the establishment of a transaction.&#xD;&#xA;The message is used to inform about either the successful establishment of a transaction (baseline) or the mis-matches found between two baseline initiation messages.&#xD;&#xA;Usage&#xD;&#xA;The BaselineMatchReport message can be sent by the matching application to&#xD;&#xA;- the parties involved in the establishment of a transaction in the push-through mode, that is the senders of InitialBaselineSubmission and BaselineReSubmission messages including the instruction push-through. In the outlined scenario the message is used to inform either about the successful establishment of a transaction in the matching application or about mis-matches found between two baseline initiation messages,or&#xD;&#xA;- the party establishing a transaction in the lodge mode, that is the sender of an InitialBaselineSubmission message including the instruction lodge. In the outlined scenario the message is used to inform about the successful establishment of a transaction in the matching application."
  registrationStatus="Registered"
  messageSet="_wRx2yk2rEeG_I4xRYCA_7g _1a374FXOEeOkkLyrDUP66g"
  xmlTag="BaselnMtchRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_lh9JgNE8Ed-BzquC8wXy7w_-1930236671"
    name="ReportIdentification"
    definition="Identifies the report."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RptId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_lh9JgdE8Ed-BzquC8wXy7w_-1930237000"
    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="_lh9JgtE8Ed-BzquC8wXy7w_-1930236517"
    name="EstablishedBaselineIdentification"
    definition="Unique identification assigned by the matching application to the baseline when it is established."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="EstblishdBaselnId"
    complexType="_RJNBwdp-Ed-ak6NoX_4Aeg_-1127047102" />
  <messageBuildingBlock
    xmi:id="_lh9Jg9E8Ed-BzquC8wXy7w_-1930236979"
    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="_lh9JhNE8Ed-BzquC8wXy7w_-1930236548"
    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="_lh9JhdE8Ed-BzquC8wXy7w_-1930236093"
    name="Buyer"
    definition="Party that buys goods or services, or a financial instrument."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Buyr"
    complexType="_PcH049p-Ed-ak6NoX_4Aeg_-1219999095" />
  <messageBuildingBlock
    xmi:id="_lh9JhtE8Ed-BzquC8wXy7w_-1930236208"
    name="Seller"
    definition="Party that sells goods or services, or a financial instrument."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Sellr"
    complexType="_PcH049p-Ed-ak6NoX_4Aeg_-1219999095" />
  <messageBuildingBlock
    xmi:id="_lh9Jh9E8Ed-BzquC8wXy7w_-1930236154"
    name="BuyerBank"
    definition="The financial institution of the buyer, uniquely identified by its BIC."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="BuyrBk"
    complexType="_QEp0kNp-Ed-ak6NoX_4Aeg_792527554" />
  <messageBuildingBlock
    xmi:id="_liGTcNE8Ed-BzquC8wXy7w_-1930236123"
    name="SellerBank"
    definition="The financial institution of the seller, uniquely identified by its BIC."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SellrBk"
    complexType="_QEp0kNp-Ed-ak6NoX_4Aeg_792527554" />
  <messageBuildingBlock
    xmi:id="_liGTcdE8Ed-BzquC8wXy7w_-1930236609"
    name="BaselineEstablishmentTrials"
    definition="Specifies the number of matching trials for a baseline."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="BaselnEstblishmtTrils"
    complexType="_RJpGpNp-Ed-ak6NoX_4Aeg_-234268618" />
  <messageBuildingBlock
    xmi:id="_liGTctE8Ed-BzquC8wXy7w_-1930236239"
    name="ComparedDocumentReference"
    definition="Identifies the two baselines compared in this report."
    registrationStatus="Provisionally Registered"
    maxOccurs="2"
    minOccurs="2"
    xmlTag="CmpardDocRef"
    complexType="_RJNBxNp-Ed-ak6NoX_4Aeg_2003796933" />
  <messageBuildingBlock
    xmi:id="_liGTc9E8Ed-BzquC8wXy7w_-1930236947"
    name="Report"
    definition="Description of the differences between the two proposed baselines."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Rpt"
    complexType="_RaowANp-Ed-ak6NoX_4Aeg_-1146148189" />
  <messageBuildingBlock
    xmi:id="_liGTdNE8Ed-BzquC8wXy7w_-1930236640"
    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="010"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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