MandateInitiationRequestV01

pain.009.001.01

Scope The MandateInitiationRequest message is sent by the initiator of the request to his agent. The initiator can either be the debtor or the creditor. The MandateInitiationRequest message is forwarded by the agent of the initiator to the agent of the counterparty. The MandateInitiationRequest message is used to set-up the instruction that allows the debtor agent to accept instructions from the creditor, through the creditor agent, to debit the account of the debtor. Usage The MandateInitiationRequest message can contain only one request to set-up 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 MandateInitiationRequest 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
%% MandateInitiationRequestV01 recursion level 0 with max 0
MandateInitiationRequestV01 *-- "1..1" GroupHeader31 : GroupHeader
MandateInitiationRequestV01 *-- "1..1" MandateInformation2 : Mandate

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 mandate initiation, 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.

Mandate building block

Set of elements used to provide the details of the mandate signed between the (ultimate) creditor and the (ultimate) debtor. Information that serves as a basis to debit an account. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MandateInformation2 recursion level 0 with max 1
class MandateInformation2{
    MandateIdentification IsoMax35Text
    MandateRequestIdentification IsoMax35Text
    CollectionAmount IsoActiveCurrencyAndAmount
    MaximumAmount IsoActiveCurrencyAndAmount
}
MandateInformation2 *-- "0..1" MandateTypeInformation1 : Type
MandateInformation2 *-- "0..1" MandateOccurrences1 : Occurrences
MandateInformation2 *-- "0..1" PartyIdentification32 : CreditorSchemeIdentification
MandateInformation2 *-- "1..1" PartyIdentification32 : Creditor
MandateInformation2 *-- "0..1" CashAccount16 : CreditorAccount
MandateInformation2 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : CreditorAgent
MandateInformation2 *-- "0..1" PartyIdentification32 : UltimateCreditor
MandateInformation2 *-- "1..1" PartyIdentification32 : Debtor
MandateInformation2 *-- "0..1" CashAccount16 : DebtorAccount
MandateInformation2 *-- "1..1" BranchAndFinancialInstitutionIdentification4 : DebtorAgent
MandateInformation2 *-- "0..1" PartyIdentification32 : UltimateDebtor
MandateInformation2 *-- "0..1" ReferredDocumentInformation3 : ReferredDocument
%% MandateTypeInformation1 recursion level 1 with max 1
MandateTypeInformation1 *-- "0..1" IServiceLevel8Choice : ServiceLevel
MandateTypeInformation1 *-- "0..1" ILocalInstrument2Choice : LocalInstrument
%% MandateOccurrences1 recursion level 1 with max 1
class MandateOccurrences1{
    SequenceType SequenceType2Code
    Frequency Frequency1Code
    FirstCollectionDate IsoISODate
    FinalCollectionDate IsoISODate
}
MandateOccurrences1 *-- "0..1" DatePeriodDetails1 : Duration
%% 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
%% 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
%% CashAccount16 recursion level 1 with max 1
class CashAccount16{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount16 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount16 *-- "0..1" CashAccountType2 : Type
%% BranchAndFinancialInstitutionIdentification4 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification4 *-- "1..1" FinancialInstitutionIdentification7 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification4 *-- "0..1" BranchData2 : BranchIdentification
%% 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
%% 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
%% CashAccount16 recursion level 1 with max 1
class CashAccount16{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount16 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount16 *-- "0..1" CashAccountType2 : Type
%% BranchAndFinancialInstitutionIdentification4 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification4 *-- "1..1" FinancialInstitutionIdentification7 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification4 *-- "0..1" BranchData2 : BranchIdentification
%% 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
%% ReferredDocumentInformation3 recursion level 1 with max 1
class ReferredDocumentInformation3{
    Number IsoMax35Text
    RelatedDate IsoISODate
}
ReferredDocumentInformation3 *-- "0..1" ReferredDocumentType2 : Type

MandateInformation2 members

Member name	Description	Data Type / Multiplicity
MandateIdentification	Unique identification, as assigned by the creditor, to unambiguously identify the mandate.	IsoMax35Text - Optional 0..1
MandateRequestIdentification	Identification for the mandate request, as assigned by the initiating party.	IsoMax35Text - Required 1..1
Type	Specifies the type of mandate, such as paper, electronic or scheme.	MandateTypeInformation1 - Optional 0..1
Occurrences	Set of elements used to provide details of the duration of the mandate and occurrence of the underlying transactions.	MandateOccurrences1 - Optional 0..1
CollectionAmount	Fixed amount to be collected from the debtor’s account.	IsoActiveCurrencyAndAmount - Optional 0..1
MaximumAmount	Maximum amount that may be collected from the debtor’s account, per instruction.	IsoActiveCurrencyAndAmount - Optional 0..1
CreditorSchemeIdentification	Credit party that signs the mandate.	PartyIdentification32 - Optional 0..1
Creditor	Party that signs the mandate and to whom an amount of money is due.	PartyIdentification32 - Required 1..1
CreditorAccount	Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.	CashAccount16 - Optional 0..1
CreditorAgent	Financial institution servicing an account for the creditor.	BranchAndFinancialInstitutionIdentification4 - Optional 0..1
UltimateCreditor	Ultimate party to which an amount of money is due.	PartyIdentification32 - Optional 0..1
Debtor	Party that signs the mandate and owes an amount of money to the (ultimate) creditor.	PartyIdentification32 - Required 1..1
DebtorAccount	Unambiguous identification of the account of the debtor, to which a debit entry will be made as a result of the transaction.	CashAccount16 - Optional 0..1
DebtorAgent	Financial institution servicing an account for the debtor.	BranchAndFinancialInstitutionIdentification4 - Required 1..1
UltimateDebtor	Ultimate party that owes an amount of money to the (ultimate) creditor.	PartyIdentification32 - Optional 0..1
ReferredDocument	Set of elements used to provide information to identify the underlying documents associated with the mandate.	ReferredDocumentInformation3 - Optional 0..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    MandateInitiationRequestV01 --|> IOuterRecord : Implements
    MandateInitiationRequestV01Document --|> IOuterDocument~MandateInitiationRequestV01~ : Implements
    class IOuterDocument~MandateInitiationRequestV01~ {
        MandateInitiationRequestV01 Message
     }

Document wrapper for serialization

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

classDiagram
    MandateInitiationRequestV01Document *-- MandateInitiationRequestV01 : 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.009.001.01">
    <MndtInitnReq>
        <GrpHdr>
            <!-- GroupHeader inner content -->
        </GrpHdr>
        <Mndt>
            <!-- Mandate inner content -->
        </Mndt>
    </MndtInitnReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_GYN9SdEvEd-BzquC8wXy7w_93398652"
  nextVersions="_r1UQkFkyEeGeoaLUQk__nA_-422128939"
  name="MandateInitiationRequestV01"
  definition="Scope&#xD;&#xA;The MandateInitiationRequest 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 MandateInitiationRequest message is forwarded by the agent of the initiator to the agent of the counterparty.&#xD;&#xA;The MandateInitiationRequest message is used to set-up the instruction that allows the debtor agent to accept instructions from the creditor, through the creditor agent, to debit the account of the debtor.&#xD;&#xA;Usage&#xD;&#xA;The MandateInitiationRequest message can contain only one request to set-up 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 MandateInitiationRequest message can be used in domestic and cross-border scenarios."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="MndtInitnReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_GYN9StEvEd-BzquC8wXy7w_508184194"
    name="GroupHeader"
    definition="Set of characteristics to identify the message and parties playing a role in the mandate initiation, 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="_GYN9S9EvEd-BzquC8wXy7w_77760662"
    name="Mandate"
    definition="Set of elements used to provide the details of the mandate signed between the (ultimate) creditor and the (ultimate) debtor."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Mndt"
    complexType="_T28aaNp-Ed-ak6NoX_4Aeg_-1312343153" />
  <messageDefinitionIdentifier
    businessArea="pain"
    messageFunctionality="009"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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