MandateCancellationRequestV01

pain.011.001.01

Scope The MandateCancellationRequest message is sent by the initiator of the request to his agent. The initiator can either be the debtor or the creditor. The MandateCancellationRequest message is forwarded by the agent of the initiator to the agent of the counterparty. A MandateCancellationRequest message is used to request the cancellation of an existing mandate. If accepted, this MandateCancellationRequest message together with the MandateAcceptanceReport message confirming the acceptance will be considered a valid cancellation of an existing mandate, agreed upon by all parties. Usage The MandateCancellationRequest message can contain only one request to cancel one specific mandate. The messages can be exchanged between creditor and creditor agent or debtor and debtor agent and between creditor agent and debtor agent. The message can also be used by an initiating party that has authority to send the message on behalf of the creditor or debtor. The MandateCancellationRequest message can be used in domestic and cross-border scenarios.

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
%% MandateCancellationRequestV01 recursion level 0 with max 0
MandateCancellationRequestV01 *-- "1..1" GroupHeader31 : GroupHeader
MandateCancellationRequestV01 *-- "1..1" MandateCancellation1 : UnderlyingCancellationDetails
  

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

GroupHeader building block

Set of characteristics to identify the message and parties playing a role in the cancellation of the mandate, but which are not part of the mandate. Set of characteristics shared by all individual transactions included in the message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% GroupHeader31 recursion level 0 with max 1
class GroupHeader31{
    MessageIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
}
GroupHeader31 *-- "0..2" IAuthorisation1Choice : Authorisation
GroupHeader31 *-- "0..1" PartyIdentification32 : InitiatingParty
GroupHeader31 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : InstructingAgent
GroupHeader31 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : InstructedAgent
%% IAuthorisation1Choice recursion level 1 with max 1
%% PartyIdentification32 recursion level 1 with max 1
class PartyIdentification32{
    Name IsoMax140Text
    CountryOfResidence CountryCode
}
PartyIdentification32 *-- "0..1" PostalAddress6 : PostalAddress
PartyIdentification32 *-- "0..1" IParty6Choice : Identification
PartyIdentification32 *-- "0..1" ContactDetails2 : ContactDetails
%% BranchAndFinancialInstitutionIdentification4 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification4 *-- "1..1" FinancialInstitutionIdentification7 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification4 *-- "0..1" BranchData2 : BranchIdentification
%% BranchAndFinancialInstitutionIdentification4 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification4 *-- "1..1" FinancialInstitutionIdentification7 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification4 *-- "0..1" BranchData2 : BranchIdentification
  

GroupHeader31 members

UnderlyingCancellationDetails building block

Set of elements used to provide details on the cancellation request. Identifies the mandate to be cancelled. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MandateCancellation1 recursion level 0 with max 1
MandateCancellation1 *-- "0..1" OriginalMessageInformation1 : OriginalMessageInformation
MandateCancellation1 *-- "1..1" CancellationReasonInformation2 : CancellationReason
MandateCancellation1 *-- "1..1" IOriginalMandate1Choice : OriginalMandate
%% OriginalMessageInformation1 recursion level 1 with max 1
class OriginalMessageInformation1{
    MessageIdentification IsoMax35Text
    MessageNameIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
}
%% CancellationReasonInformation2 recursion level 1 with max 1
class CancellationReasonInformation2{
    AdditionalInformation IsoMax105Text
}
CancellationReasonInformation2 *-- "0..1" PartyIdentification32 : Originator
CancellationReasonInformation2 *-- "1..1" IMandateReason1Choice : Reason
%% IOriginalMandate1Choice recursion level 1 with max 1
  

MandateCancellation1 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    MandateCancellationRequestV01 --|> IOuterRecord : Implements
    MandateCancellationRequestV01Document --|> IOuterDocument~MandateCancellationRequestV01~ : Implements
    class IOuterDocument~MandateCancellationRequestV01~ {
        MandateCancellationRequestV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    MandateCancellationRequestV01Document *-- MandateCancellationRequestV01 : 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:pain.011.001.01">
    <MndtCxlReq>
        <GrpHdr>
            <!-- GroupHeader inner content -->
        </GrpHdr>
        <UndrlygCxlDtls>
            <!-- UnderlyingCancellationDetails inner content -->
        </UndrlygCxlDtls>
    </MndtCxlReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_GYEMStEvEd-BzquC8wXy7w_-879561385"
  nextVersions="_r0RuwFkyEeGeoaLUQk__nA_893031254"
  name="MandateCancellationRequestV01"
  definition="Scope&#xD;&#xA;The MandateCancellationRequest message is sent by the initiator of the request to his agent. The initiator can either be the debtor or the creditor.&#xD;&#xA;The MandateCancellationRequest message is forwarded by the agent of the initiator to the agent of the counterparty.&#xD;&#xA;A MandateCancellationRequest message is used to request the cancellation of an existing mandate. If accepted, this MandateCancellationRequest message together with the MandateAcceptanceReport message confirming the acceptance will be considered a valid cancellation of an existing mandate, agreed upon by all parties.&#xD;&#xA;Usage&#xD;&#xA;The MandateCancellationRequest message can contain only one request to cancel one specific mandate.&#xD;&#xA;The messages can be exchanged between creditor and creditor agent or debtor and debtor agent and between creditor agent and debtor agent.&#xD;&#xA;The message can also be used by an initiating party that has authority to send the message on behalf of the creditor or debtor.&#xD;&#xA;The MandateCancellationRequest message can be used in domestic and cross-border scenarios."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="MndtCxlReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_GYEMS9EvEd-BzquC8wXy7w_-1953287668"
    name="GroupHeader"
    definition="Set of characteristics to identify the message and parties playing a role in the cancellation of the mandate, but which are not part of the mandate."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="GrpHdr"
    complexType="_PrK9iNp-Ed-ak6NoX_4Aeg_-727218247" />
  <messageBuildingBlock
    xmi:id="_GYEMTNEvEd-BzquC8wXy7w_-1941282874"
    name="UnderlyingCancellationDetails"
    definition="Set of elements used to provide details on the cancellation request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="UndrlygCxlDtls"
    complexType="_RBmk8tp-Ed-ak6NoX_4Aeg_-1323180575" />
  <messageDefinitionIdentifier
    businessArea="pain"
    messageFunctionality="011"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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