BaselineReSubmissionV05

tsmt.012.001.05

Scope The BaselineReSubmission message is sent by either the counterparty or the initiator of a transaction (baseline) to the matching application. This message is used by the counterparty to respond on the registration of a push-through transaction in the matching application or by the initiator or counterparty to re-send earlier mis-matched baseline information. Usage The BaselineReSubmission message can be sent by the counterparty of a transaction to the matching application in response to a FullPushThroughReport message received from the matching application conveying the details of an InitialBaselineSubmission message. The objective of the BaselineReSubmission message sent in the outlined scenario is to achieve a successful match of two baseline initiation messages in order to establish a transaction in the matching application. or The BaselineReSubmission message can be sent by the initiator of a transaction to the matching application in response to a BaselineMatchReport message indicating mis-matches. The objective of the BaselineReSubmission message sent in the outlined scenario is to correct an InitialBaselineSubmission or BaselineReSubmission message submitted earlier in order to achieve the establishment of a transaction in the matching application. or The BaselineReSubmission message can be sent by the counterparty of a transaction to the matching application in response to a BaselineMatchReport message indicating mis-matches. The objective of the BaselineReSubmission message sent in the outlined scenario is to correct a BaselineReSubmission message submitted earlier in order to achieve the 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
%% BaselineReSubmissionV05 recursion level 0 with max 0
BaselineReSubmissionV05 *-- "1..1" MessageIdentification1 : SubmissionIdentification
BaselineReSubmissionV05 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification
BaselineReSubmissionV05 *-- "0..1" SimpleIdentificationInformation : SubmitterTransactionReference
BaselineReSubmissionV05 *-- "1..1" Baseline5 : Baseline
BaselineReSubmissionV05 *-- "0..1" ContactIdentification1 : BuyerContactPerson
BaselineReSubmissionV05 *-- "0..1" ContactIdentification1 : SellerContactPerson
BaselineReSubmissionV05 *-- "1..1" IBankContactPerson1Choice : BankContactPerson
BaselineReSubmissionV05 *-- "0..1" ContactIdentification3 : OtherBankContactPerson
  

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

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

Baseline building block

Specifies the commercial details of the underlying transaction. Specifies the commercial details of the underlying transaction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Baseline5 recursion level 0 with max 1
class Baseline5{
    ServiceCode TradeFinanceService2Code
    LatestMatchDate IsoISODate
    IntentToPayExpected IsoYesNoIndicator
}
Baseline5 *-- "1..1" DocumentIdentification1 : SubmitterBaselineIdentification
Baseline5 *-- "1..1" DocumentIdentification7 : PurchaseOrderReference
Baseline5 *-- "1..1" PartyIdentification26 : Buyer
Baseline5 *-- "1..1" PartyIdentification26 : Seller
Baseline5 *-- "1..1" BICIdentification1 : BuyerBank
Baseline5 *-- "1..1" BICIdentification1 : SellerBank
Baseline5 *-- "0..0" BICIdentification1 : BuyerSideSubmittingBank
Baseline5 *-- "0..0" BICIdentification1 : SellerSideSubmittingBank
Baseline5 *-- "0..1" PartyIdentification26 : BillTo
Baseline5 *-- "0..1" PartyIdentification26 : ShipTo
Baseline5 *-- "0..1" PartyIdentification26 : Consignee
Baseline5 *-- "1..1" LineItem13 : Goods
Baseline5 *-- "1..0" PaymentTerms5 : PaymentTerms
Baseline5 *-- "0..1" SettlementTerms3 : SettlementTerms
Baseline5 *-- "0..0" PaymentObligation2 : PaymentObligation
Baseline5 *-- "1..1" RequiredSubmission2 : CommercialDataSetRequired
Baseline5 *-- "0..1" RequiredSubmission2 : TransportDataSetRequired
Baseline5 *-- "0..1" RequiredSubmission3 : InsuranceDataSetRequired
Baseline5 *-- "0..0" RequiredSubmission4 : CertificateDataSetRequired
Baseline5 *-- "0..0" RequiredSubmission6 : OtherCertificateDataSetRequired
%% DocumentIdentification1 recursion level 1 with max 1
class DocumentIdentification1{
    Identification IsoMax35Text
    Version IsoNumber
}
DocumentIdentification1 *-- "1..1" BICIdentification1 : Submitter
%% DocumentIdentification7 recursion level 1 with max 1
class DocumentIdentification7{
    Identification IsoMax35Text
    DateOfIssue 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
%% BICIdentification1 recursion level 1 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}
%% BICIdentification1 recursion level 1 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}
%% BICIdentification1 recursion level 1 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}
%% BICIdentification1 recursion level 1 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}
%% 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
%% LineItem13 recursion level 1 with max 1
class LineItem13{
    GoodsAndOrServicesDescription IsoMax70Text
    PartialShipment IsoYesNoIndicator
    TransShipment IsoYesNoIndicator
    LineItemsTotalAmount IsoCurrencyAndAmount
    TotalNetAmount IsoCurrencyAndAmount
}
LineItem13 *-- "0..1" ShipmentDateRange1 : ShipmentDateRange
LineItem13 *-- "1..0" LineItemDetails13 : LineItemDetails
LineItem13 *-- "0..1" TransportMeans5 : RoutingSummary
LineItem13 *-- "0..1" Incoterms4 : Incoterms
LineItem13 *-- "0..0" Adjustment7 : Adjustment
LineItem13 *-- "0..1" Charge24 : FreightCharges
LineItem13 *-- "0..0" Tax23 : Tax
LineItem13 *-- "0..0" UserDefinedInformation1 : BuyerDefinedInformation
LineItem13 *-- "0..0" UserDefinedInformation1 : SellerDefinedInformation
%% PaymentTerms5 recursion level 1 with max 1
PaymentTerms5 *-- "1..1" IPaymentCodeOrOther2Choice : PaymentTerms
PaymentTerms5 *-- "1..1" IAmountOrPercentage2Choice : AmountOrPercentage
%% SettlementTerms3 recursion level 1 with max 1
SettlementTerms3 *-- "0..1" IFinancialInstitutionIdentification4Choice : CreditorAgent
SettlementTerms3 *-- "1..1" CashAccount24 : CreditorAccount
%% PaymentObligation2 recursion level 1 with max 1
class PaymentObligation2{
    ExpiryDate IsoISODate
    ApplicableLaw CountryCode
}
PaymentObligation2 *-- "1..1" BICIdentification1 : ObligorBank
PaymentObligation2 *-- "1..1" BICIdentification1 : RecipientBank
PaymentObligation2 *-- "1..1" IAmountOrPercentage2Choice : PaymentObligationAmount
PaymentObligation2 *-- "0..0" Charges5 : Charges
PaymentObligation2 *-- "0..1" IBPOApplicableRules1Choice : ApplicableRules
PaymentObligation2 *-- "0..1" Location2 : PlaceOfJurisdiction
PaymentObligation2 *-- "0..0" PaymentTerms4 : PaymentTerms
PaymentObligation2 *-- "0..1" SettlementTerms3 : SettlementTerms
%% RequiredSubmission2 recursion level 1 with max 1
RequiredSubmission2 *-- "1..0" BICIdentification1 : Submitter
%% RequiredSubmission2 recursion level 1 with max 1
RequiredSubmission2 *-- "1..0" BICIdentification1 : Submitter
%% RequiredSubmission3 recursion level 1 with max 1
class RequiredSubmission3{
    MatchIssueDate IsoYesNoIndicator
    MatchTransport IsoYesNoIndicator
    MatchAmount IsoYesNoIndicator
    ClausesRequired InsuranceClauses1Code
    MatchAssuredParty AssuredType1Code
}
RequiredSubmission3 *-- "1..0" BICIdentification1 : Submitter
RequiredSubmission3 *-- "0..1" PartyIdentification27 : MatchIssuer
%% RequiredSubmission4 recursion level 1 with max 1
class RequiredSubmission4{
    CertificateType TradeCertificateType1Code
    MatchIssueDate IsoYesNoIndicator
    MatchInspectionDate IsoYesNoIndicator
    AuthorisedInspectorIndicator IsoYesNoIndicator
    MatchConsignee IsoYesNoIndicator
    LineItemIdentification IsoMax70Text
}
RequiredSubmission4 *-- "1..0" BICIdentification1 : Submitter
RequiredSubmission4 *-- "0..1" PartyIdentification27 : MatchIssuer
RequiredSubmission4 *-- "0..1" PartyIdentification27 : MatchManufacturer
%% RequiredSubmission6 recursion level 1 with max 1
class RequiredSubmission6{
    CertificateType IsoExact4AlphaNumericText
    CertificateTypeDescription IsoMax140Text
}
RequiredSubmission6 *-- "1..0" BICIdentification1 : Submitter
  

Baseline5 members

BuyerContactPerson building block

Person to be contacted in the organisation of the buyer. Information needed to contact a physical person. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ContactIdentification1 recursion level 0 with max 1
class ContactIdentification1{
    Name IsoMax35Text
    NamePrefix NamePrefix1Code
    GivenName IsoMax35Text
    Role IsoMax35Text
    PhoneNumber IsoPhoneNumber
    FaxNumber IsoPhoneNumber
    EmailAddress IsoMax256Text
}
  

ContactIdentification1 members

SellerContactPerson building block

Person to be contacted in the organisation of the seller. Information needed to contact a physical person. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ContactIdentification1 recursion level 0 with max 1
class ContactIdentification1{
    Name IsoMax35Text
    NamePrefix NamePrefix1Code
    GivenName IsoMax35Text
    Role IsoMax35Text
    PhoneNumber IsoPhoneNumber
    FaxNumber IsoPhoneNumber
    EmailAddress IsoMax256Text
}
  

ContactIdentification1 members

BankContactPerson building block

Person to be contacted in the seller’s bank or buyer’s bank. Contact person details in a bank. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IBankContactPerson1Choice recursion level 0 with max 1
  

BankContactPerson1Choice members

OtherBankContactPerson building block

Person to be contacted in another bank than the seller or buyer’s bank. Information needed to contact a physical person. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ContactIdentification3 recursion level 0 with max 1
class ContactIdentification3{
    BIC IsoBICIdentifier
    Name IsoMax35Text
    NamePrefix NamePrefix1Code
    GivenName IsoMax35Text
    Role IsoMax35Text
    PhoneNumber IsoPhoneNumber
    FaxNumber IsoPhoneNumber
    EmailAddress IsoMax256Text
}
  

ContactIdentification3 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    BaselineReSubmissionV05 --|> IOuterRecord : Implements
    BaselineReSubmissionV05Document --|> IOuterDocument~BaselineReSubmissionV05~ : Implements
    class IOuterDocument~BaselineReSubmissionV05~ {
        BaselineReSubmissionV05 Message
     }
  

Document wrapper for serialization

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

classDiagram
    BaselineReSubmissionV05Document *-- BaselineReSubmissionV05 : 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.012.001.05">
    <BaselnReSubmissn>
        <SubmissnId>
            <!-- SubmissionIdentification inner content -->
        </SubmissnId>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <SubmitrTxRef>
            <!-- SubmitterTransactionReference inner content -->
        </SubmitrTxRef>
        <Baseln>
            <!-- Baseline inner content -->
        </Baseln>
        <BuyrCtctPrsn>
            <!-- BuyerContactPerson inner content -->
        </BuyrCtctPrsn>
        <SellrCtctPrsn>
            <!-- SellerContactPerson inner content -->
        </SellrCtctPrsn>
        <BkCtctPrsn>
            <!-- BankContactPerson inner content -->
        </BkCtctPrsn>
        <OthrBkCtctPrsn>
            <!-- OtherBankContactPerson inner content -->
        </OthrBkCtctPrsn>
    </BaselnReSubmissn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_XtCPcQgGEeSeS5xdjFfOTw"
  previousVersion="_4PCl8dNTEeK-v49t1oWkNA"
  name="BaselineReSubmissionV05"
  definition="Scope&#xD;&#xA;The BaselineReSubmission message is sent by either the counterparty or the initiator of a transaction (baseline) to the matching application.&#xD;&#xA;This message is used by the counterparty to respond on the registration of a push-through transaction in the matching application or by the initiator or counterparty to re-send earlier mis-matched baseline information.&#xD;&#xA;Usage&#xD;&#xA;The BaselineReSubmission message can be sent by the counterparty of a transaction to the matching application in response to a FullPushThroughReport message received from the matching application conveying the details of an InitialBaselineSubmission message. The objective of the BaselineReSubmission message sent in the outlined scenario is to achieve a successful match of two baseline initiation messages in order to establish a transaction in the matching application.&#xD;&#xA;or&#xD;&#xA;The BaselineReSubmission message can be sent by the initiator of a transaction to the matching application in response to a BaselineMatchReport message indicating mis-matches. The objective of the BaselineReSubmission message sent in the outlined scenario is to correct an InitialBaselineSubmission or BaselineReSubmission message submitted earlier in order to achieve the establishment of a transaction in the matching application.&#xD;&#xA;or&#xD;&#xA;The BaselineReSubmission message can be sent by the counterparty of a transaction to the matching application in response to a BaselineMatchReport message indicating mis-matches. The objective of the BaselineReSubmission message sent in the outlined scenario is to correct a BaselineReSubmission message submitted earlier in order to achieve the establishment of a transaction in the matching application."
  registrationStatus="Registered"
  messageSet="_1a374FXOEeOkkLyrDUP66g"
  xmlTag="BaselnReSubmissn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <doclet
    xmi:id="_XtCPcwgGEeSeS5xdjFfOTw"
    type="purpose" />
  <messageBuildingBlock
    xmi:id="_XtCPdQgGEeSeS5xdjFfOTw"
    previousVersion="_4PDNA9NTEeK-v49t1oWkNA"
    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="_XtCPdwgGEeSeS5xdjFfOTw"
    previousVersion="_4PDNBdNTEeK-v49t1oWkNA"
    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="_XtCPeQgGEeSeS5xdjFfOTw"
    previousVersion="_4PDNB9NTEeK-v49t1oWkNA"
    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="_XtCPewgGEeSeS5xdjFfOTw"
    previousVersion="_4PDNCdNTEeK-v49t1oWkNA"
    name="Baseline"
    definition="Specifies the commercial details of the underlying transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Baseln"
    complexType="_Jxr5cQgHEeSeS5xdjFfOTw" />
  <messageBuildingBlock
    xmi:id="_XtCPfQgGEeSeS5xdjFfOTw"
    previousVersion="_4PDNC9NTEeK-v49t1oWkNA"
    name="BuyerContactPerson"
    definition="Person to be contacted in the organisation of the buyer."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="BuyrCtctPrsn"
    complexType="_QBOtE9p-Ed-ak6NoX_4Aeg_-1391367345" />
  <messageBuildingBlock
    xmi:id="_XtCPfwgGEeSeS5xdjFfOTw"
    previousVersion="_4PDNDdNTEeK-v49t1oWkNA"
    name="SellerContactPerson"
    definition="Person to be contacted in the organisation of the seller."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SellrCtctPrsn"
    complexType="_QBOtE9p-Ed-ak6NoX_4Aeg_-1391367345" />
  <messageBuildingBlock
    xmi:id="_XtCPgQgGEeSeS5xdjFfOTw"
    previousVersion="_4ljBcDAZEeOKib24wnHaFg"
    name="BankContactPerson"
    definition="Person to be contacted in the seller's bank or buyer's bank."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="BkCtctPrsn"
    complexType="_eCkSADAZEeOKib24wnHaFg" />
  <messageBuildingBlock
    xmi:id="_XtCPgwgGEeSeS5xdjFfOTw"
    previousVersion="_4PDNE9NTEeK-v49t1oWkNA"
    name="OtherBankContactPerson"
    definition="Person to be contacted in another bank than the seller or buyer's bank."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="OthrBkCtctPrsn"
    complexType="_QDTwsdp-Ed-ak6NoX_4Aeg_-1939165929" />
  <messageDefinitionIdentifier
    businessArea="tsmt"
    messageFunctionality="012"
    flavour="001"
    version="05" />
</messageDefinition>

ISO Building Blocks

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