DemandWithdrawalNotificationV01

tsrv.017.001.01

The DemandWithdrawalNotification message is sent by the beneficiary to the party that issued the undertaking, either directly or via a presenting or nominated party, to inform the issuer or nominated party that it has elected to withdraw its demand under the demand guarantee or standby letter of credit.

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
%% DemandWithdrawalNotificationV01 recursion level 0 with max 0
DemandWithdrawalNotificationV01 *-- "1..1" UndertakingDemandWithdrawal1 : DemandWithdrawalNotificationDetails
DemandWithdrawalNotificationV01 *-- "0..1" PartyAndSignature2 : DigitalSignature
  

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

DemandWithdrawalNotificationDetails building block

Details of the demand withdrawal notification. Details of the demand withdrawal notification. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% UndertakingDemandWithdrawal1 recursion level 0 with max 1
class UndertakingDemandWithdrawal1{
    AdvisingPartyReferenceNumber IsoMax35Text
    ConfirmerReferenceNumber IsoMax35Text
}
UndertakingDemandWithdrawal1 *-- "1..1" Undertaking6 : UndertakingIdentification
UndertakingDemandWithdrawal1 *-- "1..1" Demand3 : DemandDetails
%% Undertaking6 recursion level 1 with max 1
class Undertaking6{
    Identification IsoMax35Text
    BeneficiaryReferenceNumber IsoMax35Text
}
Undertaking6 *-- "1..1" PartyIdentification43 : Issuer
%% Demand3 recursion level 1 with max 1
class Demand3{
    Identification IsoMax35Text
    SubmissionDateTime IsoISODateTime
    Amount IsoActiveCurrencyAndAmount
}
  

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

classDiagram
    class IOuterRecord
    DemandWithdrawalNotificationV01 --|> IOuterRecord : Implements
    DemandWithdrawalNotificationV01Document --|> IOuterDocument~DemandWithdrawalNotificationV01~ : Implements
    class IOuterDocument~DemandWithdrawalNotificationV01~ {
        DemandWithdrawalNotificationV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    DemandWithdrawalNotificationV01Document *-- DemandWithdrawalNotificationV01 : 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.017.001.01">
    <DmndWdrwlNtfctn>
        <DmndWdrwlNtfctnDtls>
            <!-- DemandWithdrawalNotificationDetails inner content -->
        </DmndWdrwlNtfctnDtls>
        <DgtlSgntr>
            <!-- DigitalSignature inner content -->
        </DgtlSgntr>
    </DmndWdrwlNtfctn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_9hWQMnltEeG7BsjMvd1mEw_1943951405"
  name="DemandWithdrawalNotificationV01"
  definition="The DemandWithdrawalNotification message is sent by the beneficiary to the party that issued the undertaking, either directly or via a presenting or nominated party, to inform the issuer or nominated party that it has elected to withdraw its demand under the demand guarantee or standby letter of credit."
  registrationStatus="Registered"
  messageSet="_SiMuI9n1EeGEPsbnW6ebrw"
  xmlTag="DmndWdrwlNtfctn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_9hWQM3ltEeG7BsjMvd1mEw_234628498"
    name="DemandWithdrawalNotificationDetails"
    definition="Details of the demand withdrawal notification."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="DmndWdrwlNtfctnDtls"
    complexType="_-Br9JnltEeG7BsjMvd1mEw_1678341433" />
  <messageBuildingBlock
    xmi:id="_9hWQNHltEeG7BsjMvd1mEw_-1538509071"
    name="DigitalSignature"
    definition="Digital signature of the notification."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="DgtlSgntr"
    complexType="_k4nFNZKuEeGnRMFvqYmPBQ" />
  <messageDefinitionIdentifier
    businessArea="tsrv"
    messageFunctionality="017"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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