UndertakingAmendmentNotificationV01

tsrv.007.001.01

The UndertakingAmendmentNotification message is sent by the party that issued the undertaking to the applicant to notify it of the contents of a proposed amendment to the undertaking (issued electronically or on paper). The undertaking could be a demand guarantee, standby letter of credit, counter-undertaking (counter-guarantee or counter-standby), or suretyship undertaking. In addition to providing the proposed terms of the amendment and details on proposed changes to the undertaking, the message may provide other supporting information from the sender. It may also be used to notify the proposed termination or cancellation of the undertaking.

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
%% UndertakingAmendmentNotificationV01 recursion level 0 with max 0
UndertakingAmendmentNotificationV01 *-- "1..1" Amendment6 : UndertakingAmendmentNotificationDetails
UndertakingAmendmentNotificationV01 *-- "0..1" PartyAndSignature2 : DigitalSignature
  

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

UndertakingAmendmentNotificationDetails building block

Details related to the notification of the proposed amended undertaking. Details of the amendment. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Amendment6 recursion level 0 with max 1
class Amendment6{
    ApplicantReferenceNumber IsoMax35Text
    AdditionalInformation IsoMax2000Text
}
Amendment6 *-- "1..1" UndertakingAmendmentMessage1 : UndertakingAmendmentMessage
%% UndertakingAmendmentMessage1 recursion level 1 with max 1
UndertakingAmendmentMessage1 *-- "1..1" Amendment1 : UndertakingAmendmentDetails
UndertakingAmendmentMessage1 *-- "0..1" PartyAndSignature2 : DigitalSignature
  

Amendment6 members

DigitalSignature building block

Digital signature of the notification. Entity involved in an activity. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PartyAndSignature2 recursion level 0 with max 1
PartyAndSignature2 *-- "1..1" PartyIdentification43 : Party
PartyAndSignature2 *-- "1..1" ProprietaryData3 : Signature
%% PartyIdentification43 recursion level 1 with max 1
class PartyIdentification43{
    Name IsoMax140Text
    CountryOfResidence CountryCode
}
PartyIdentification43 *-- "0..1" PostalAddress6 : PostalAddress
PartyIdentification43 *-- "0..1" IParty11Choice : Identification
PartyIdentification43 *-- "0..1" ContactDetails2 : ContactDetails
%% ProprietaryData3 recursion level 1 with max 1
ProprietaryData3 *-- "1..1" SkipProcessing : Any
  

PartyAndSignature2 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    UndertakingAmendmentNotificationV01 --|> IOuterRecord : Implements
    UndertakingAmendmentNotificationV01Document --|> IOuterDocument~UndertakingAmendmentNotificationV01~ : Implements
    class IOuterDocument~UndertakingAmendmentNotificationV01~ {
        UndertakingAmendmentNotificationV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    UndertakingAmendmentNotificationV01Document *-- UndertakingAmendmentNotificationV01 : 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:tsrv.007.001.01">
    <UdrtkgAmdmntNtfctn>
        <UdrtkgAmdmntNtfctnDtls>
            <!-- UndertakingAmendmentNotificationDetails inner content -->
        </UdrtkgAmdmntNtfctnDtls>
        <DgtlSgntr>
            <!-- DigitalSignature inner content -->
        </DgtlSgntr>
    </UdrtkgAmdmntNtfctn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_9g6LUnltEeG7BsjMvd1mEw_1297611038"
  name="UndertakingAmendmentNotificationV01"
  definition="The UndertakingAmendmentNotification message is sent by the party that issued the undertaking to the applicant to notify it of the contents of a proposed amendment to the undertaking (issued electronically or on paper). The undertaking could be a demand guarantee, standby letter of credit, counter-undertaking (counter-guarantee or counter-standby), or suretyship undertaking. In addition to providing the proposed terms of the amendment and details on proposed changes to the undertaking, the message may provide other supporting information from the sender. It may also be used to notify the proposed termination or cancellation of the undertaking."
  registrationStatus="Registered"
  messageSet="_SiMuI9n1EeGEPsbnW6ebrw"
  xmlTag="UdrtkgAmdmntNtfctn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_9g6LU3ltEeG7BsjMvd1mEw_1612122638"
    name="UndertakingAmendmentNotificationDetails"
    definition="Details related to the notification of the proposed amended undertaking."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="UdrtkgAmdmntNtfctnDtls"
    complexType="_9_TXgXltEeG7BsjMvd1mEw_678552493" />
  <messageBuildingBlock
    xmi:id="_9g6LVHltEeG7BsjMvd1mEw_1241284917"
    name="DigitalSignature"
    definition="Digital signature of the notification."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="DgtlSgntr"
    complexType="_k4nFNZKuEeGnRMFvqYmPBQ" />
  <messageDefinitionIdentifier
    businessArea="tsrv"
    messageFunctionality="007"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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