pain.010.001.01
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 only one request to amend 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 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
%% MandateAmendmentRequestV01 recursion level 0 with max 0
MandateAmendmentRequestV01 *-- "1..1" GroupHeader31 : GroupHeader
MandateAmendmentRequestV01 *-- "1..1" MandateAmendment1 : UnderlyingAmendmentDetails
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
%% 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
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MessageIdentification | Point to point reference, as assigned by the instructing party, and sent to the instructed party, to unambiguously identify the message. | Usage: The instructing party has to make sure that MessageIdentification is unique per instructed party for a pre-agreed period. |
| CreationDateTime | Date and time at which the message was created. | IsoISODateTime - Required 1..1 |
| Authorisation | User identification or any user key to be used to check the authority of the initiating party. | |
| InitiatingParty | Party that initiates the mandate message. | PartyIdentification32 - Optional 0..1 |
| InstructingAgent | Agent that instructs the next party in the chain to carry out an instruction. | |
| InstructedAgent | Agent that is instructed by the previous party in the chain to carry out an instruction. |
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
%% MandateAmendment1 recursion level 0 with max 1
MandateAmendment1 *-- "0..1" OriginalMessageInformation1 : OriginalMessageInformation
MandateAmendment1 *-- "1..1" AmendmentReasonInformation1 : AmendmentReason
MandateAmendment1 *-- "1..1" MandateInformation3 : Mandate
MandateAmendment1 *-- "1..1" IOriginalMandate1Choice : OriginalMandate
%% OriginalMessageInformation1 recursion level 1 with max 1
class OriginalMessageInformation1{
MessageIdentification IsoMax35Text
MessageNameIdentification IsoMax35Text
CreationDateTime IsoISODateTime
}
%% AmendmentReasonInformation1 recursion level 1 with max 1
class AmendmentReasonInformation1{
AdditionalInformation IsoMax105Text
}
AmendmentReasonInformation1 *-- "0..1" PartyIdentification32 : Originator
AmendmentReasonInformation1 *-- "1..1" IMandateReason1Choice : Reason
%% MandateInformation3 recursion level 1 with max 1
class MandateInformation3{
MandateIdentification IsoMax35Text
MandateRequestIdentification IsoMax35Text
CollectionAmount IsoActiveCurrencyAndAmount
MaximumAmount IsoActiveCurrencyAndAmount
}
MandateInformation3 *-- "0..1" MandateTypeInformation1 : Type
MandateInformation3 *-- "0..1" MandateOccurrences1 : Occurrences
MandateInformation3 *-- "0..1" PartyIdentification32 : CreditorSchemeIdentification
MandateInformation3 *-- "0..1" PartyIdentification32 : Creditor
MandateInformation3 *-- "0..1" CashAccount16 : CreditorAccount
MandateInformation3 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : CreditorAgent
MandateInformation3 *-- "0..1" PartyIdentification32 : UltimateCreditor
MandateInformation3 *-- "0..1" PartyIdentification32 : Debtor
MandateInformation3 *-- "0..1" CashAccount16 : DebtorAccount
MandateInformation3 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : DebtorAgent
MandateInformation3 *-- "0..1" PartyIdentification32 : UltimateDebtor
MandateInformation3 *-- "0..1" ReferredDocumentInformation3 : ReferredDocument
%% IOriginalMandate1Choice recursion level 1 with max 1
MandateAmendment1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| OriginalMessageInformation | Set of elements used to provide information on the original messsage. | OriginalMessageInformation1 - Optional 0..1 |
| AmendmentReason | Set of elements used to provide detailed information on the amendment reason. | AmendmentReasonInformation1 - Required 1..1 |
| Mandate | Set of elements used to provide the amended mandate data. | MandateInformation3 - Required 1..1 |
| OriginalMandate | Set of elements used to provide the original mandate data. | IOriginalMandate1Choice - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the MandateAmendmentRequestV01 implementation follows a specific implementaiton pattern. First of all, MandateAmendmentRequestV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MandateAmendmentRequestV01Document implements IOuterDocument. Because MandateAmendmentRequestV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MandateAmendmentRequestV01.
classDiagram
class IOuterRecord
MandateAmendmentRequestV01 --|> IOuterRecord : Implements
MandateAmendmentRequestV01Document --|> IOuterDocument~MandateAmendmentRequestV01~ : Implements
class IOuterDocument~MandateAmendmentRequestV01~ {
MandateAmendmentRequestV01 Message
}
Document wrapper for serialization
The only real purpose MandateAmendmentRequestV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:pain.010.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MandateAmendmentRequestV01.ToDocument() method. The returned MandateAmendmentRequestV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
MandateAmendmentRequestV01Document *-- MandateAmendmentRequestV01 : 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.01">
<MndtAmdmntReq>
<GrpHdr>
<!-- GroupHeader inner content -->
</GrpHdr>
<UndrlygAmdmntDtls>
<!-- UnderlyingAmendmentDetails inner content -->
</UndrlygAmdmntDtls>
</MndtAmdmntReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_GX7CXtEvEd-BzquC8wXy7w_-355407990"
nextVersions="_rye_AFkyEeGeoaLUQk__nA_1884403542"
name="MandateAmendmentRequestV01"
definition="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 only one request to amend 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 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."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="MndtAmdmntReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_GX7CX9EvEd-BzquC8wXy7w_65717989"
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="_PrK9iNp-Ed-ak6NoX_4Aeg_-727218247" />
<messageBuildingBlock
xmi:id="_GYEMQNEvEd-BzquC8wXy7w_-389718479"
name="UnderlyingAmendmentDetails"
definition="Set of elements used to provide details on the amendment request."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="UndrlygAmdmntDtls"
complexType="_RBcz9tp-Ed-ak6NoX_4Aeg_-453440412" />
<messageDefinitionIdentifier
businessArea="pain"
messageFunctionality="010"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.