MandateAmendmentRequestV06

pain.010.001.06

Scope The MandateAmendmentRequest message is sent by the initiator of the request to his agent and/or counterparty. The initiator can both be the debtor or the creditor (or where appropriate the debtor agent). The MandateAmendmentRequest message is forwarded by the agent of the initiator to the agent of the counterparty. A MandateAmendmentRequest message is used to request the amendment of specific information in an existing mandate. The MandateAmendmentRequest message must reflect the new data of the element(s) to be amended and at a minimum a unique reference to the existing mandate. If accepted, this MandateAmendmentRequest message together with the MandateAcceptanceReport message confirming the acceptance will be considered as a valid amendment on an existing mandate, agreed upon by all parties. The amended mandate will from then on be considered the valid mandate. Usage The MandateAmendmentRequest message can contain one or more request(s) to amend a 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 MandateAmendmentRequest message can be used in domestic and cross-border scenarios. If all elements in the existing Mandate need to be amended or the underlying contract is different, then the MandateAmendmentRequest message should not be used. The existing Mandate has to be cancelled and a new Mandate has to be initiated.

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
%% MandateAmendmentRequestV06 recursion level 0 with max 0
MandateAmendmentRequestV06 *-- "1..1" GroupHeader80 : GroupHeader
MandateAmendmentRequestV06 *-- "1..1" MandateAmendment6 : UnderlyingAmendmentDetails
MandateAmendmentRequestV06 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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 amendment 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
%% GroupHeader80 recursion level 0 with max 1
class GroupHeader80{
    MessageIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
}
GroupHeader80 *-- "0..2" IAuthorisation1Choice : Authorisation
GroupHeader80 *-- "0..1" PartyIdentification135 : InitiatingParty
GroupHeader80 *-- "0..1" BranchAndFinancialInstitutionIdentification6 : InstructingAgent
GroupHeader80 *-- "0..1" BranchAndFinancialInstitutionIdentification6 : InstructedAgent
%% IAuthorisation1Choice recursion level 1 with max 1
%% PartyIdentification135 recursion level 1 with max 1
class PartyIdentification135{
    Name IsoMax140Text
    CountryOfResidence CountryCode
}
PartyIdentification135 *-- "0..1" PostalAddress24 : PostalAddress
PartyIdentification135 *-- "0..1" IParty38Choice : Identification
PartyIdentification135 *-- "0..1" Contact4 : ContactDetails
%% BranchAndFinancialInstitutionIdentification6 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification6 *-- "1..1" FinancialInstitutionIdentification18 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification6 *-- "0..1" BranchData3 : BranchIdentification
%% BranchAndFinancialInstitutionIdentification6 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification6 *-- "1..1" FinancialInstitutionIdentification18 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification6 *-- "0..1" BranchData3 : BranchIdentification
  

GroupHeader80 members

UnderlyingAmendmentDetails building block

Set of elements used to provide details on the amendment request. Identifies the mandate to be amended and gives details of the new mandate. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MandateAmendment6 recursion level 0 with max 1
MandateAmendment6 *-- "0..1" OriginalMessageInformation1 : OriginalMessageInformation
MandateAmendment6 *-- "1..1" MandateAmendmentReason2 : AmendmentReason
MandateAmendment6 *-- "1..1" Mandate14 : Mandate
MandateAmendment6 *-- "1..1" IOriginalMandate6Choice : OriginalMandate
MandateAmendment6 *-- "0..0" SupplementaryData1 : SupplementaryData
%% OriginalMessageInformation1 recursion level 1 with max 1
class OriginalMessageInformation1{
    MessageIdentification IsoMax35Text
    MessageNameIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
}
%% MandateAmendmentReason2 recursion level 1 with max 1
class MandateAmendmentReason2{
    AdditionalInformation IsoMax105Text
}
MandateAmendmentReason2 *-- "0..1" PartyIdentification135 : Originator
MandateAmendmentReason2 *-- "1..1" IMandateReason1Choice : Reason
%% Mandate14 recursion level 1 with max 1
class Mandate14{
    MandateIdentification IsoMax35Text
    MandateRequestIdentification IsoMax35Text
    TrackingIndicator IsoTrueFalseIndicator
    FirstCollectionAmount IsoActiveCurrencyAndAmount
    CollectionAmount IsoActiveCurrencyAndAmount
    MaximumAmount IsoActiveCurrencyAndAmount
    MandateReference IsoMax35Text
}
Mandate14 *-- "0..1" MandateAuthentication1 : Authentication
Mandate14 *-- "0..1" MandateTypeInformation2 : Type
Mandate14 *-- "0..1" MandateOccurrences4 : Occurrences
Mandate14 *-- "0..1" MandateAdjustment1 : Adjustment
Mandate14 *-- "0..1" IMandateSetupReason1Choice : Reason
Mandate14 *-- "0..1" PartyIdentification135 : CreditorSchemeIdentification
Mandate14 *-- "0..1" PartyIdentification135 : Creditor
Mandate14 *-- "0..1" CashAccount38 : CreditorAccount
Mandate14 *-- "0..1" BranchAndFinancialInstitutionIdentification6 : CreditorAgent
Mandate14 *-- "0..1" PartyIdentification135 : UltimateCreditor
Mandate14 *-- "0..1" PartyIdentification135 : Debtor
Mandate14 *-- "0..1" CashAccount38 : DebtorAccount
Mandate14 *-- "0..1" BranchAndFinancialInstitutionIdentification6 : DebtorAgent
Mandate14 *-- "0..1" PartyIdentification135 : UltimateDebtor
Mandate14 *-- "0..0" ReferredMandateDocument1 : ReferredDocument
%% IOriginalMandate6Choice recursion level 1 with max 1
%% SupplementaryData1 recursion level 1 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
  

MandateAmendment6 members

SupplementaryData building block

Additional information that cannot be captured in the structured elements and/or any other specific block. Additional information that can not be captured in the structured fields and/or any other specific block. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SupplementaryData1 recursion level 0 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
%% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1
  

SupplementaryData1 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    MandateAmendmentRequestV06 --|> IOuterRecord : Implements
    MandateAmendmentRequestV06Document --|> IOuterDocument~MandateAmendmentRequestV06~ : Implements
    class IOuterDocument~MandateAmendmentRequestV06~ {
        MandateAmendmentRequestV06 Message
     }
  

Document wrapper for serialization

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

classDiagram
    MandateAmendmentRequestV06Document *-- MandateAmendmentRequestV06 : 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.010.001.06">
    <MndtAmdmntReq>
        <GrpHdr>
            <!-- GroupHeader inner content -->
        </GrpHdr>
        <UndrlygAmdmntDtls>
            <!-- UnderlyingAmendmentDetails inner content -->
        </UndrlygAmdmntDtls>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </MndtAmdmntReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_bf9SHW2PEei3KuUgpx7Xcw"
  nextVersions="_rUYN7dcBEeq_l4BJLVUF2Q"
  previousVersion="_cn3EQUjuEeaVLL5QKJ4f-A"
  name="MandateAmendmentRequestV06"
  definition="Scope&#xD;&#xA;The MandateAmendmentRequest message is sent by the initiator of the request to his agent and/or counterparty. The initiator can both be the debtor or the creditor (or where appropriate the debtor agent).&#xD;&#xA;The MandateAmendmentRequest message is forwarded by the agent of the initiator to the agent of the counterparty.&#xD;&#xA;A MandateAmendmentRequest message is used to request the amendment of specific information in an existing mandate. The MandateAmendmentRequest message must reflect the new data of the element(s) to be amended and at a minimum a unique reference to the existing mandate. If accepted, this MandateAmendmentRequest message together with the MandateAcceptanceReport message confirming the acceptance will be considered as a valid amendment on an existing mandate, agreed upon by all parties. The amended mandate will from then on be considered the valid mandate.&#xD;&#xA;Usage&#xD;&#xA;The MandateAmendmentRequest message can contain one or more request(s) to amend a 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 MandateAmendmentRequest message can be used in domestic and cross-border scenarios.&#xD;&#xA;If all elements in the existing Mandate need to be amended or the underlying contract is different, then the MandateAmendmentRequest message should not be used. The existing Mandate has to be cancelled and a new Mandate has to be initiated."
  registrationStatus="Registered"
  messageSet="_wRx2wU2rEeG_I4xRYCA_7g"
  xmlTag="MndtAmdmntReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_bf9SH22PEei3KuUgpx7Xcw"
    nextVersions="_rUYN79cBEeq_l4BJLVUF2Q"
    previousVersion="_cn3EQ0juEeaVLL5QKJ4f-A"
    name="SupplementaryDataRule"
    definition="The SupplementaryData building block at message level must not be used to provide additional information about a transaction. The SupplementaryData element at transaction level should be used for that purpose."
    registrationStatus="Provisionally Registered" />
  <messageBuildingBlock
    xmi:id="_bf9SIW2PEei3KuUgpx7Xcw"
    nextVersions="_rUYN99cBEeq_l4BJLVUF2Q"
    previousVersion="_cn3ERUjuEeaVLL5QKJ4f-A"
    name="GroupHeader"
    definition="Set of characteristics to identify the message and parties playing a role in the amendment of the mandate, but which are not part of the mandate."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="GrpHdr"
    complexType="_G-MfEW49EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_bf9SI22PEei3KuUgpx7Xcw"
    nextVersions="_rUYN-dcBEeq_l4BJLVUF2Q"
    previousVersion="_cn3ER0juEeaVLL5QKJ4f-A"
    name="UnderlyingAmendmentDetails"
    definition="Set of elements used to provide details on the amendment request."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="UndrlygAmdmntDtls"
    complexType="_RwtmcW49EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_bf9SJW2PEei3KuUgpx7Xcw"
    nextVersions="_rUYN-9cBEeq_l4BJLVUF2Q"
    previousVersion="_cn3ESUjuEeaVLL5QKJ4f-A"
    name="SupplementaryData"
    definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SplmtryData"
    complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
  <messageDefinitionIdentifier
    businessArea="pain"
    messageFunctionality="010"
    flavour="001"
    version="06" />
</messageDefinition>

ISO Building Blocks

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