DataSetSubmissionV05

tsmt.014.001.05

Scope The DataSetSubmission message is sent by a party involved in the transaction to the matching application. This message is used to trigger either a match or a pre-match of the information submitted with the message. Usage The DataSetSubmission message can be sent by either party with the instruction pre-match. In the outlined scenario, the matching application will compare the data set(s) conveyed by the DataSetSubmission message with the established baseline and report the matching result to the requester of the data set pre-match by sending a DataSetMatchReport message. or The DataSetSubmission message can be sent by the party specified in the baseline as data set submitter with the instruction match. In the outlined scenario, the matching application will compare the data set(s) conveyed by the DataSetSubmission message with the established baseline and report the matching result to

• the parties involved in a transaction established in the push-through mode, or
• the initiator of a transaction established in the lodge mode. The DataSetSubmission message can be used to submit multiple data sets for multiple transactions (baselines) at the same time. However, all transactions (baselines) covered by the message must be for the same parties, that is transaction initiator and counterparty, as well as for the same buyer and seller. The DataSetSubmission message consists of data reflecting trade information related to the purchasing agreement covered by the transaction(s), for example shipment date, invoice amount.

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
%% DataSetSubmissionV05 recursion level 0 with max 0
DataSetSubmissionV05 *-- "1..1" MessageIdentification1 : SubmissionIdentification
DataSetSubmissionV05 *-- "1..1" DataSetSubmissionReferences3 : RelatedTransactionReferences
DataSetSubmissionV05 *-- "1..1" SimpleIdentificationInformation : CommonSubmissionReference
DataSetSubmissionV05 *-- "1..1" InstructionType3 : Instruction
DataSetSubmissionV05 *-- "1..1" BICIdentification1 : BuyerBank
DataSetSubmissionV05 *-- "1..1" BICIdentification1 : SellerBank
DataSetSubmissionV05 *-- "0..1" CommercialDataSet5 : CommercialDataSet
DataSetSubmissionV05 *-- "0..1" TransportDataSet5 : TransportDataSet
DataSetSubmissionV05 *-- "0..1" InsuranceDataSet1 : InsuranceDataSet
DataSetSubmissionV05 *-- "0..1" CertificateDataSet2 : CertificateDataSet
DataSetSubmissionV05 *-- "0..1" OtherCertificateDataSet2 : OtherCertificateDataSet
  

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

SubmissionIdentification building block

Identifies the submitted information. 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

RelatedTransactionReferences building block

Identifies the transactions that this submission relates to and provides associated information. Provides references to the submitted data set both for the matching application and for the user. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% DataSetSubmissionReferences3 recursion level 0 with max 1
class DataSetSubmissionReferences3{
    TransactionIdentification IsoMax35Text
    SubmitterTransactionReference IsoMax35Text
    ForcedMatch IsoYesNoIndicator
}
DataSetSubmissionReferences3 *-- "1..1" DocumentIdentification7 : PurchaseOrderReference
%% DocumentIdentification7 recursion level 1 with max 1
class DocumentIdentification7{
    Identification IsoMax35Text
    DateOfIssue IsoISODate
}
  

DataSetSubmissionReferences3 members

CommonSubmissionReference building block

This reference must be used for all data sets belonging to the same submission group. 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

Instruction building block

Specifies the instruction given by the submitter. Specifies the type of instruction requested by the submitter by means of a code. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% InstructionType3 recursion level 0 with max 1
class InstructionType3{
    Type InstructionType3Code
}
  

InstructionType3 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

CommercialDataSet building block

Commercial information that is submitted to the matching application for processing. Goods or services that are part of a commercial trade agreement. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CommercialDataSet5 recursion level 0 with max 1
CommercialDataSet5 *-- "1..1" DocumentIdentification1 : DataSetIdentification
CommercialDataSet5 *-- "1..1" InvoiceIdentification1 : CommercialDocumentReference
CommercialDataSet5 *-- "1..1" PartyIdentification26 : Buyer
CommercialDataSet5 *-- "1..1" PartyIdentification26 : Seller
CommercialDataSet5 *-- "0..1" PartyIdentification26 : BillTo
CommercialDataSet5 *-- "1..0" LineItem15 : Goods
CommercialDataSet5 *-- "1..0" PaymentTerms4 : PaymentTerms
CommercialDataSet5 *-- "1..1" SettlementTerms3 : SettlementTerms
%% DocumentIdentification1 recursion level 1 with max 1
class DocumentIdentification1{
    Identification IsoMax35Text
    Version IsoNumber
}
DocumentIdentification1 *-- "1..1" BICIdentification1 : Submitter
%% InvoiceIdentification1 recursion level 1 with max 1
class InvoiceIdentification1{
    InvoiceNumber IsoMax35Text
    IssueDate IsoISODate
}
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% LineItem15 recursion level 1 with max 1
class LineItem15{
    FinalSubmission IsoYesNoIndicator
    LineItemsTotalAmount IsoCurrencyAndAmount
    TotalNetAmount IsoCurrencyAndAmount
}
LineItem15 *-- "1..1" DocumentIdentification7 : PurchaseOrderReference
LineItem15 *-- "1..0" LineItemDetails14 : CommercialLineItems
LineItem15 *-- "0..0" Adjustment6 : Adjustment
LineItem15 *-- "0..1" Charge25 : FreightCharges
LineItem15 *-- "0..0" Tax22 : Tax
LineItem15 *-- "0..0" UserDefinedInformation1 : BuyerDefinedInformation
LineItem15 *-- "0..0" UserDefinedInformation1 : SellerDefinedInformation
LineItem15 *-- "0..1" Incoterms4 : Incoterms
%% PaymentTerms4 recursion level 1 with max 1
PaymentTerms4 *-- "1..1" IPaymentCodeOrOther1Choice : PaymentTerms
PaymentTerms4 *-- "1..1" IAmountOrPercentage2Choice : AmountOrPercentage
%% SettlementTerms3 recursion level 1 with max 1
SettlementTerms3 *-- "0..1" IFinancialInstitutionIdentification4Choice : CreditorAgent
SettlementTerms3 *-- "1..1" CashAccount24 : CreditorAccount
  

CommercialDataSet5 members

TransportDataSet building block

Transport information that is submitted to the matching application for processing. Provides details on the transportation of goods that are part of a commercial trade agreement. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TransportDataSet5 recursion level 0 with max 1
TransportDataSet5 *-- "1..1" DocumentIdentification1 : DataSetIdentification
TransportDataSet5 *-- "0..1" PartyIdentification26 : Buyer
TransportDataSet5 *-- "0..1" PartyIdentification26 : Seller
TransportDataSet5 *-- "1..1" PartyIdentification26 : Consignor
TransportDataSet5 *-- "0..1" PartyIdentification26 : Consignee
TransportDataSet5 *-- "0..1" PartyIdentification26 : ShipTo
TransportDataSet5 *-- "1..1" TransportDetails4 : TransportInformation
%% DocumentIdentification1 recursion level 1 with max 1
class DocumentIdentification1{
    Identification IsoMax35Text
    Version IsoNumber
}
DocumentIdentification1 *-- "1..1" BICIdentification1 : Submitter
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% TransportDetails4 recursion level 1 with max 1
TransportDetails4 *-- "1..0" DocumentIdentification7 : TransportDocumentReference
TransportDetails4 *-- "1..0" TransportedGoods1 : TransportedGoods
TransportDetails4 *-- "0..1" Consignment3 : Consignment
TransportDetails4 *-- "1..1" TransportMeans6 : RoutingSummary
TransportDetails4 *-- "1..1" IShipmentDate1Choice : ShipmentDate
TransportDetails4 *-- "0..1" Charge25 : FreightCharges
TransportDetails4 *-- "0..1" Incoterms4 : Incoterms
  

TransportDataSet5 members

InsuranceDataSet building block

Insurance information that is submitted to the matching application for processing. Formal document used to record a fact and used as proof of the fact that goods have been insured under an insurance policy. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% InsuranceDataSet1 recursion level 0 with max 1
class InsuranceDataSet1{
    IssueDate IsoISODate
    EffectiveDate IsoISODate
    InsuranceDocumentIdentification IsoMax35Text
    InsuredAmount IsoCurrencyAndAmount
    InsuredGoodsDescription IsoMax70Text
    InsuranceConditions IsoMax350Text
    InsuranceClauses InsuranceClauses1Code
    ClaimsPayableIn CurrencyCode
}
InsuranceDataSet1 *-- "1..1" DocumentIdentification1 : DataSetIdentification
InsuranceDataSet1 *-- "1..1" PartyIdentification26 : Issuer
InsuranceDataSet1 *-- "0..1" PostalAddress5 : PlaceOfIssue
InsuranceDataSet1 *-- "0..1" SingleTransport3 : Transport
InsuranceDataSet1 *-- "1..1" IPartyIdentification29Choice : Assured
InsuranceDataSet1 *-- "1..1" PostalAddress5 : ClaimsPayableAt
%% DocumentIdentification1 recursion level 1 with max 1
class DocumentIdentification1{
    Identification IsoMax35Text
    Version IsoNumber
}
DocumentIdentification1 *-- "1..1" BICIdentification1 : Submitter
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% PostalAddress5 recursion level 1 with max 1
class PostalAddress5{
    StreetName IsoMax70Text
    PostCodeIdentification IsoMax16Text
    TownName IsoMax35Text
    CountrySubDivision IsoMax35Text
    Country CountryCode
}
%% SingleTransport3 recursion level 1 with max 1
SingleTransport3 *-- "0..1" TransportByAir2 : TransportByAir
SingleTransport3 *-- "0..1" TransportBySea4 : TransportBySea
SingleTransport3 *-- "0..1" TransportByRoad2 : TransportByRoad
SingleTransport3 *-- "0..1" TransportByRail2 : TransportByRail
%% IPartyIdentification29Choice recursion level 1 with max 1
%% PostalAddress5 recursion level 1 with max 1
class PostalAddress5{
    StreetName IsoMax70Text
    PostCodeIdentification IsoMax16Text
    TownName IsoMax35Text
    CountrySubDivision IsoMax35Text
    Country CountryCode
}
  

InsuranceDataSet1 members

CertificateDataSet building block

Certificate information that is submitted to the matching application for processing. Formal document used to record a fact and used as proof of the fact, in the context of a commercial trade transaction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CertificateDataSet2 recursion level 0 with max 1
class CertificateDataSet2{
    CertificateType TradeCertificateType1Code
    IssueDate IsoISODate
    AuthorisedInspectorIndicator IsoYesNoIndicator
    CertificateIdentification IsoMax35Text
    GoodsDescription IsoMax70Text
    AdditionalInformation IsoMax350Text
}
CertificateDataSet2 *-- "1..1" DocumentIdentification1 : DataSetIdentification
CertificateDataSet2 *-- "0..0" LineItemAndPOIdentification1 : LineItem
CertificateDataSet2 *-- "1..1" ICertifiedCharacteristics2Choice : CertifiedCharacteristics
CertificateDataSet2 *-- "0..1" PostalAddress5 : PlaceOfIssue
CertificateDataSet2 *-- "1..1" PartyIdentification26 : Issuer
CertificateDataSet2 *-- "0..1" DatePeriodDetails : InspectionDate
CertificateDataSet2 *-- "0..1" SingleTransport3 : Transport
CertificateDataSet2 *-- "0..1" PartyIdentification26 : Consignor
CertificateDataSet2 *-- "0..1" PartyIdentification26 : Consignee
CertificateDataSet2 *-- "0..1" PartyIdentification26 : Manufacturer
%% DocumentIdentification1 recursion level 1 with max 1
class DocumentIdentification1{
    Identification IsoMax35Text
    Version IsoNumber
}
DocumentIdentification1 *-- "1..1" BICIdentification1 : Submitter
%% LineItemAndPOIdentification1 recursion level 1 with max 1
class LineItemAndPOIdentification1{
    LineItemIdentification IsoMax70Text
}
LineItemAndPOIdentification1 *-- "1..1" DocumentIdentification7 : PurchaseOrderReference
%% ICertifiedCharacteristics2Choice recursion level 1 with max 1
%% PostalAddress5 recursion level 1 with max 1
class PostalAddress5{
    StreetName IsoMax70Text
    PostCodeIdentification IsoMax16Text
    TownName IsoMax35Text
    CountrySubDivision IsoMax35Text
    Country CountryCode
}
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% DatePeriodDetails recursion level 1 with max 1
class DatePeriodDetails{
    FromDate IsoISODate
    ToDate IsoISODate
}
%% SingleTransport3 recursion level 1 with max 1
SingleTransport3 *-- "0..1" TransportByAir2 : TransportByAir
SingleTransport3 *-- "0..1" TransportBySea4 : TransportBySea
SingleTransport3 *-- "0..1" TransportByRoad2 : TransportByRoad
SingleTransport3 *-- "0..1" TransportByRail2 : TransportByRail
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
  

CertificateDataSet2 members

OtherCertificateDataSet building block

Other certificate information that is submitted to the matching application for processing. Formal document used to record a fact and used as proof of the fact, in the context of a commercial trade transaction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% OtherCertificateDataSet2 recursion level 0 with max 1
class OtherCertificateDataSet2{
    CertificateIdentification IsoMax35Text
    CertificateType IsoExact4AlphaNumericText
    IssueDate IsoISODate
    CertificateInformation IsoMax350Text
}
OtherCertificateDataSet2 *-- "1..1" DocumentIdentification1 : DataSetIdentification
OtherCertificateDataSet2 *-- "1..1" PartyIdentification26 : Issuer
%% DocumentIdentification1 recursion level 1 with max 1
class DocumentIdentification1{
    Identification IsoMax35Text
    Version IsoNumber
}
DocumentIdentification1 *-- "1..1" BICIdentification1 : Submitter
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
  

OtherCertificateDataSet2 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    DataSetSubmissionV05 --|> IOuterRecord : Implements
    DataSetSubmissionV05Document --|> IOuterDocument~DataSetSubmissionV05~ : Implements
    class IOuterDocument~DataSetSubmissionV05~ {
        DataSetSubmissionV05 Message
     }
  

Document wrapper for serialization

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

classDiagram
    DataSetSubmissionV05Document *-- DataSetSubmissionV05 : 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.014.001.05">
    <DataSetSubmissn>
        <SubmissnId>
            <!-- SubmissionIdentification inner content -->
        </SubmissnId>
        <RltdTxRefs>
            <!-- RelatedTransactionReferences inner content -->
        </RltdTxRefs>
        <CmonSubmissnRef>
            <!-- CommonSubmissionReference inner content -->
        </CmonSubmissnRef>
        <Instr>
            <!-- Instruction inner content -->
        </Instr>
        <BuyrBk>
            <!-- BuyerBank inner content -->
        </BuyrBk>
        <SellrBk>
            <!-- SellerBank inner content -->
        </SellrBk>
        <ComrclDataSet>
            <!-- CommercialDataSet inner content -->
        </ComrclDataSet>
        <TrnsprtDataSet>
            <!-- TransportDataSet inner content -->
        </TrnsprtDataSet>
        <InsrncDataSet>
            <!-- InsuranceDataSet inner content -->
        </InsrncDataSet>
        <CertDataSet>
            <!-- CertificateDataSet inner content -->
        </CertDataSet>
        <OthrCertDataSet>
            <!-- OtherCertificateDataSet inner content -->
        </OthrCertDataSet>
    </DataSetSubmissn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_h2S-cQgGEeSeS5xdjFfOTw"
  previousVersion="_zXROkdQrEeK0PPbKncCqzA"
  name="DataSetSubmissionV05"
  definition="Scope&#xD;&#xA;The DataSetSubmission message is sent by a party involved in the transaction to the matching application.&#xD;&#xA;This message is used to trigger either a match or a pre-match of the information submitted with the message.&#xD;&#xA;Usage&#xD;&#xA;The DataSetSubmission message can be sent by either party with the instruction pre-match. In the outlined scenario, the matching application will compare the data set(s) conveyed by the DataSetSubmission message with the established baseline and report the matching result to the requester of the data set pre-match by sending a DataSetMatchReport message.&#xD;&#xA;or&#xD;&#xA;The DataSetSubmission message can be sent by the party specified in the baseline as data set submitter with the instruction match. In the outlined scenario, the matching application will compare the data set(s) conveyed by the DataSetSubmission message with the established baseline and report the matching result to&#xD;&#xA;- the parties involved in a transaction established in the push-through mode, or&#xD;&#xA;- the initiator of a transaction established in the lodge mode.&#xD;&#xA;The DataSetSubmission message can be used to submit multiple data sets for multiple transactions (baselines) at the same time. However, all transactions (baselines) covered by the message must be for the same parties, that is transaction initiator and counterparty, as well as for the same buyer and seller.&#xD;&#xA;The DataSetSubmission message consists of data reflecting trade information related to the purchasing agreement covered by the transaction(s), for example shipment date, invoice amount."
  registrationStatus="Registered"
  messageSet="_1a374FXOEeOkkLyrDUP66g"
  xmlTag="DataSetSubmissn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <doclet
    xmi:id="_h2S-cwgGEeSeS5xdjFfOTw"
    type="purpose" />
  <messageBuildingBlock
    xmi:id="_h2S-dQgGEeSeS5xdjFfOTw"
    previousVersion="_zXROk9QrEeK0PPbKncCqzA"
    name="SubmissionIdentification"
    definition="Identifies the submitted information."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SubmissnId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_h2S-dwgGEeSeS5xdjFfOTw"
    previousVersion="_zXROldQrEeK0PPbKncCqzA"
    name="RelatedTransactionReferences"
    definition="Identifies the transactions that this submission relates to and provides associated information."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="RltdTxRefs"
    complexType="_RaCTE9p-Ed-ak6NoX_4Aeg_204942196" />
  <messageBuildingBlock
    xmi:id="_h2S-eQgGEeSeS5xdjFfOTw"
    previousVersion="_zXROl9QrEeK0PPbKncCqzA"
    name="CommonSubmissionReference"
    definition="This reference must be used for all data sets belonging to the same submission group."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="CmonSubmissnRef"
    complexType="_P-ile9p-Ed-ak6NoX_4Aeg_745508310" />
  <messageBuildingBlock
    xmi:id="_h2S-ewgGEeSeS5xdjFfOTw"
    previousVersion="_zXROmdQrEeK0PPbKncCqzA"
    name="Instruction"
    definition="Specifies the instruction given by the submitter."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Instr"
    complexType="_RJpGotp-Ed-ak6NoX_4Aeg_-1074370626" />
  <messageBuildingBlock
    xmi:id="_h2S-fQgGEeSeS5xdjFfOTw"
    previousVersion="_zXROm9QrEeK0PPbKncCqzA"
    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="_h2S-fwgGEeSeS5xdjFfOTw"
    previousVersion="_zXROndQrEeK0PPbKncCqzA"
    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="_h2S-gQgGEeSeS5xdjFfOTw"
    previousVersion="_zXROn9QrEeK0PPbKncCqzA"
    name="CommercialDataSet"
    definition="Commercial information that is submitted to the matching application for processing."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="ComrclDataSet"
    complexType="_L6FU0TckEeSaC-PiOaz_KQ" />
  <messageBuildingBlock
    xmi:id="_h2S-gwgGEeSeS5xdjFfOTw"
    previousVersion="_zXROodQrEeK0PPbKncCqzA"
    name="TransportDataSet"
    definition="Transport information that is submitted to the matching application for processing."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="TrnsprtDataSet"
    complexType="_2DIaMTckEeSaC-PiOaz_KQ" />
  <messageBuildingBlock
    xmi:id="_h2S-hQgGEeSeS5xdjFfOTw"
    previousVersion="_zXROo9QrEeK0PPbKncCqzA"
    name="InsuranceDataSet"
    definition="Insurance information that is submitted to the matching application for processing."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="InsrncDataSet"
    complexType="_Tm2v9tp-Ed-ak6NoX_4Aeg_888710434" />
  <messageBuildingBlock
    xmi:id="_h2S-hwgGEeSeS5xdjFfOTw"
    previousVersion="_zXROpdQrEeK0PPbKncCqzA"
    name="CertificateDataSet"
    definition="Certificate information that is submitted to the matching application for processing."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="CertDataSet"
    complexType="_2LOxkTANEeOKib24wnHaFg" />
  <messageBuildingBlock
    xmi:id="_h2S-iQgGEeSeS5xdjFfOTw"
    previousVersion="_zXROp9QrEeK0PPbKncCqzA"
    name="OtherCertificateDataSet"
    definition="Other certificate information that is submitted to the matching application for processing."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="OthrCertDataSet"
    complexType="_d3zy0QgKEeSeS5xdjFfOTw" />
  <messageDefinitionIdentifier
    businessArea="tsmt"
    messageFunctionality="014"
    flavour="001"
    version="05" />
</messageDefinition>

ISO Building Blocks

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