DemandRefusalNotificationV01

tsrv.016.001.01

The DemandRefusalNotification message is sent to the beneficiary or presenter by the party obligated on the undertaking and to whom a demand for payment has been made, either directly or via one or more advising parties. It notifies the beneficiary or presenter that the demand has been refused.

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
%% DemandRefusalNotificationV01 recursion level 0 with max 0
DemandRefusalNotificationV01 *-- "0..1" DemandRefusal1 : DemandRefusalNotificationDetails
DemandRefusalNotificationV01 *-- "0..1" PartyAndSignature2 : DigitalSignature
  

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

DemandRefusalNotificationDetails building block

Details of the demand refusal notification. Information about the refusal of a demand. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% DemandRefusal1 recursion level 0 with max 1
class DemandRefusal1{
    AdvisingPartyReferenceNumber IsoMax35Text
    SecondAdvisingPartyReferenceNumber IsoMax35Text
    ConfirmerReferenceNumber IsoMax35Text
    Status IsoRefused7Text
    DispositionOfDocuments IsoMax2000Text
    AdditionalInformation IsoMax2000Text
}
DemandRefusal1 *-- "1..1" Undertaking9 : UndertakingIdentification
DemandRefusal1 *-- "1..1" Demand2 : DemandDetails
DemandRefusal1 *-- "0..0" Discrepancy1 : Discrepancy
%% Undertaking9 recursion level 1 with max 1
class Undertaking9{
    Identification IsoMax35Text
    ApplicantReferenceNumber IsoMax35Text
}
Undertaking9 *-- "1..1" PartyIdentification43 : Issuer
%% Demand2 recursion level 1 with max 1
class Demand2{
    Identification IsoMax35Text
    SubmissionDateTime IsoISODateTime
    Amount IsoActiveCurrencyAndAmount
    AdditionalInformation IsoMax2000Text
}
%% Discrepancy1 recursion level 1 with max 1
class Discrepancy1{
    Identification IsoMax35Text
    Narrative IsoMax20000Text
}
  

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

classDiagram
    class IOuterRecord
    DemandRefusalNotificationV01 --|> IOuterRecord : Implements
    DemandRefusalNotificationV01Document --|> IOuterDocument~DemandRefusalNotificationV01~ : Implements
    class IOuterDocument~DemandRefusalNotificationV01~ {
        DemandRefusalNotificationV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    DemandRefusalNotificationV01Document *-- DemandRefusalNotificationV01 : 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.016.001.01">
    <DmndRfslNtfctn>
        <DmndRfslNtfctnDtls>
            <!-- DemandRefusalNotificationDetails inner content -->
        </DmndRfslNtfctnDtls>
        <DgtlSgntr>
            <!-- DigitalSignature inner content -->
        </DgtlSgntr>
    </DmndRfslNtfctn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_9iijAHltEeG7BsjMvd1mEw_2131850524"
  name="DemandRefusalNotificationV01"
  definition="The DemandRefusalNotification message is sent to the beneficiary or presenter by the party obligated on the undertaking and to whom a demand for payment has been made, either directly or via one or more advising parties. It notifies the beneficiary or presenter that the demand has been refused."
  registrationStatus="Registered"
  messageSet="_SiMuI9n1EeGEPsbnW6ebrw"
  xmlTag="DmndRfslNtfctn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_9iijAXltEeG7BsjMvd1mEw_1591105840"
    name="DemandRefusalNotificationDetails"
    definition="Details of the demand refusal notification."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="DmndRfslNtfctnDtls"
    complexType="_-FHEkHltEeG7BsjMvd1mEw_-1919643766" />
  <messageBuildingBlock
    xmi:id="_9iijAnltEeG7BsjMvd1mEw_-509775412"
    name="DigitalSignature"
    definition="Digital signature of the notification."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="DgtlSgntr"
    complexType="_k4nFNZKuEeGnRMFvqYmPBQ" />
  <messageDefinitionIdentifier
    businessArea="tsrv"
    messageFunctionality="016"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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