BaselineAmendmentRequestV03

tsmt.009.001.03

Scope The BaselineAmendmentRequest message is sent by a primary party involved in a transaction to the matching application. The message is used to request the amendment of an established baseline. Usage The BaselineAmendmentRequest message may only be sent if the transaction is in the state Established or Active. The BaselineAmendmentRequest message can be sent to the matching application by one of the primary parties involved in a transaction established in the push-through mode to request the amendment of an established baseline. The matching application acknowledges the receipt of the amendment request by sending a DeltaReport message to the submitter of the BaselineAmendmentRequest message. It passes on the newly proposed baseline to the counterparty by sending a FullPushThroughReport message, a DeltaReport message and a pre-calculated BaselineReport message. The counterparty is expected to either accept or reject the amendment request by submitting an AmendmentAcceptance or AmendmentRejection message. or The BaselineAmendmentRequest message can be sent by the party involved in a transaction established in the lodge mode to the matching application to amend an established baseline. The matching application amends the baseline according to the BaselineAmendmentRequest message and confirms the execution of the request by sending a DeltaReport and calculated BaselineReport message to the requester of the amendment.

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
%% BaselineAmendmentRequestV03 recursion level 0 with max 0
BaselineAmendmentRequestV03 *-- "1..1" MessageIdentification1 : RequestIdentification
BaselineAmendmentRequestV03 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification
BaselineAmendmentRequestV03 *-- "0..1" SimpleIdentificationInformation : SubmitterTransactionReference
BaselineAmendmentRequestV03 *-- "1..1" Baseline3 : Baseline
BaselineAmendmentRequestV03 *-- "0..1" ContactIdentification1 : BuyerContactPerson
BaselineAmendmentRequestV03 *-- "0..1" ContactIdentification1 : SellerContactPerson
BaselineAmendmentRequestV03 *-- "0..1" ContactIdentification1 : BuyerBankContactPerson
BaselineAmendmentRequestV03 *-- "0..1" ContactIdentification1 : SellerBankContactPerson
BaselineAmendmentRequestV03 *-- "0..1" ContactIdentification3 : OtherBankContactPerson
  

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

RequestIdentification building block

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

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
%% Baseline3 recursion level 0 with max 1
class Baseline3{
    ServiceCode TradeFinanceService2Code
    LatestMatchDate IsoISODate
    IntentToPayExpected IsoYesNoIndicator
}
Baseline3 *-- "1..1" DocumentIdentification1 : SubmitterBaselineIdentification
Baseline3 *-- "1..1" DocumentIdentification7 : PurchaseOrderReference
Baseline3 *-- "1..1" PartyIdentification26 : Buyer
Baseline3 *-- "1..1" PartyIdentification26 : Seller
Baseline3 *-- "1..1" BICIdentification1 : BuyerBank
Baseline3 *-- "1..1" BICIdentification1 : SellerBank
Baseline3 *-- "0..0" BICIdentification1 : BuyerSideSubmittingBank
Baseline3 *-- "0..0" BICIdentification1 : SellerSideSubmittingBank
Baseline3 *-- "0..1" PartyIdentification26 : BillTo
Baseline3 *-- "0..1" PartyIdentification26 : ShipTo
Baseline3 *-- "0..1" PartyIdentification26 : Consignee
Baseline3 *-- "1..1" LineItem7 : Goods
Baseline3 *-- "1..0" PaymentTerms1 : PaymentTerms
Baseline3 *-- "0..1" SettlementTerms2 : SettlementTerms
Baseline3 *-- "0..0" PaymentObligation1 : PaymentObligation
Baseline3 *-- "1..1" RequiredSubmission2 : CommercialDataSetRequired
Baseline3 *-- "0..1" RequiredSubmission2 : TransportDataSetRequired
Baseline3 *-- "0..1" RequiredSubmission3 : InsuranceDataSetRequired
Baseline3 *-- "0..0" RequiredSubmission4 : CertificateDataSetRequired
Baseline3 *-- "0..0" RequiredSubmission5 : 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
%% LineItem7 recursion level 1 with max 1
class LineItem7{
    GoodsDescription IsoMax70Text
    PartialShipment IsoYesNoIndicator
    TransShipment IsoYesNoIndicator
    LineItemsTotalAmount IsoCurrencyAndAmount
    TotalNetAmount IsoCurrencyAndAmount
}
LineItem7 *-- "0..1" ShipmentDateRange1 : ShipmentDateRange
LineItem7 *-- "1..0" LineItemDetails7 : LineItemDetails
LineItem7 *-- "0..1" TransportMeans1 : RoutingSummary
LineItem7 *-- "0..0" Incoterms1 : Incoterms
LineItem7 *-- "0..0" Adjustment3 : Adjustment
LineItem7 *-- "0..1" Charge12 : FreightCharges
LineItem7 *-- "0..0" Tax13 : Tax
LineItem7 *-- "0..0" UserDefinedInformation1 : BuyerDefinedInformation
LineItem7 *-- "0..0" UserDefinedInformation1 : SellerDefinedInformation
%% PaymentTerms1 recursion level 1 with max 1
class PaymentTerms1{
    OtherPaymentTerms IsoMax140Text
    Percentage IsoPercentageRate
    Amount IsoCurrencyAndAmount
}
PaymentTerms1 *-- "1..1" PaymentPeriod1 : PaymentCode
%% SettlementTerms2 recursion level 1 with max 1
SettlementTerms2 *-- "0..1" IFinancialInstitutionIdentification4Choice : CreditorAgent
SettlementTerms2 *-- "1..1" CashAccount7 : CreditorAccount
%% PaymentObligation1 recursion level 1 with max 1
class PaymentObligation1{
    Amount IsoCurrencyAndAmount
    Percentage IsoPercentageRate
    ChargesAmount IsoCurrencyAndAmount
    ChargesPercentage IsoPercentageRate
    ExpiryDate IsoISODate
    ApplicableLaw CountryCode
}
PaymentObligation1 *-- "1..1" BICIdentification1 : ObligorBank
PaymentObligation1 *-- "1..1" BICIdentification1 : RecipientBank
PaymentObligation1 *-- "0..0" PaymentTerms2 : PaymentTerms
PaymentObligation1 *-- "0..1" SettlementTerms2 : 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
%% RequiredSubmission5 recursion level 1 with max 1
class RequiredSubmission5{
    CertificateType TradeCertificateType2Code
}
RequiredSubmission5 *-- "1..0" BICIdentification1 : Submitter
  

Baseline3 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

BuyerBankContactPerson building block

Person to be contacted in the buyer’s bank. 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

SellerBankContactPerson building block

Person to be contacted in the seller’s bank. 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

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

classDiagram
    class IOuterRecord
    BaselineAmendmentRequestV03 --|> IOuterRecord : Implements
    BaselineAmendmentRequestV03Document --|> IOuterDocument~BaselineAmendmentRequestV03~ : Implements
    class IOuterDocument~BaselineAmendmentRequestV03~ {
        BaselineAmendmentRequestV03 Message
     }
  

Document wrapper for serialization

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

classDiagram
    BaselineAmendmentRequestV03Document *-- BaselineAmendmentRequestV03 : 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.009.001.03">
    <BaselnAmdmntReq>
        <ReqId>
            <!-- RequestIdentification inner content -->
        </ReqId>
        <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>
        <BuyrBkCtctPrsn>
            <!-- BuyerBankContactPerson inner content -->
        </BuyrBkCtctPrsn>
        <SellrBkCtctPrsn>
            <!-- SellerBankContactPerson inner content -->
        </SellrBkCtctPrsn>
        <OthrBkCtctPrsn>
            <!-- OtherBankContactPerson inner content -->
        </OthrBkCtctPrsn>
    </BaselnAmdmntReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_lGO21tE8Ed-BzquC8wXy7w_-1621087191"
  nextVersions="_glyJkdM7EeK-v49t1oWkNA"
  name="BaselineAmendmentRequestV03"
  definition="Scope&#xD;&#xA;The BaselineAmendmentRequest message is sent by a primary party involved in a transaction to the matching application.&#xD;&#xA;The message is used to request the amendment of an established baseline.&#xD;&#xA;Usage&#xD;&#xA;The BaselineAmendmentRequest message may only be sent if the transaction is in the state Established or Active.&#xD;&#xA;The BaselineAmendmentRequest message can be sent to the matching application by one of the primary parties involved in a transaction established in the push-through mode to request the amendment of an established baseline.&#xD;&#xA;The matching application acknowledges the receipt of the amendment request by sending a DeltaReport message to the submitter of the BaselineAmendmentRequest message. It passes on the newly proposed baseline to the counterparty by sending a FullPushThroughReport message, a DeltaReport message and a pre-calculated BaselineReport message.&#xD;&#xA;The counterparty is expected to either accept or reject the amendment request by submitting an AmendmentAcceptance or AmendmentRejection message.&#xD;&#xA;or&#xD;&#xA;The BaselineAmendmentRequest message can be sent by the party involved in a transaction established in the lodge mode to the matching application to amend an established baseline.&#xD;&#xA;The matching application amends the baseline according to the BaselineAmendmentRequest message and confirms the execution of the request by sending a DeltaReport and calculated BaselineReport message to the requester of the amendment."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="BaselnAmdmntReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_lGO219E8Ed-BzquC8wXy7w_-1621087155"
    nextVersions="_glywodM7EeK-v49t1oWkNA"
    name="RequestIdentification"
    definition="Identifies the request message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="ReqId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_lGO22NE8Ed-BzquC8wXy7w_-1621087078"
    nextVersions="_glywo9M7EeK-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="_lGO22dE8Ed-BzquC8wXy7w_-1621087120"
    nextVersions="_glywpdM7EeK-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="_lGO22tE8Ed-BzquC8wXy7w_-1621087174"
    nextVersions="_glywp9M7EeK-v49t1oWkNA"
    name="Baseline"
    definition="Specifies the commercial details of the underlying transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Baseln"
    complexType="_Sq9IZdp-Ed-ak6NoX_4Aeg_-88106768" />
  <messageBuildingBlock
    xmi:id="_lGO229E8Ed-BzquC8wXy7w_-1724579248"
    nextVersions="_glywqdM7EeK-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="_lGYn0NE8Ed-BzquC8wXy7w_-1282211094"
    nextVersions="_glywq9M7EeK-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="_lGYn0dE8Ed-BzquC8wXy7w_-1166771083"
    nextVersions="_glywrdM7EeK-v49t1oWkNA"
    name="BuyerBankContactPerson"
    definition="Person to be contacted in the buyer's bank."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="BuyrBkCtctPrsn"
    complexType="_QBOtE9p-Ed-ak6NoX_4Aeg_-1391367345" />
  <messageBuildingBlock
    xmi:id="_lGYn0tE8Ed-BzquC8wXy7w_-825993983"
    nextVersions="_glywr9M7EeK-v49t1oWkNA"
    name="SellerBankContactPerson"
    definition="Person to be contacted in the seller's bank."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SellrBkCtctPrsn"
    complexType="_QBOtE9p-Ed-ak6NoX_4Aeg_-1391367345" />
  <messageBuildingBlock
    xmi:id="_lGYn09E8Ed-BzquC8wXy7w_-491678031"
    nextVersions="_glywsdM7EeK-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="009"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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