Iso20022

MandateInitiationRequestV06

pain.009.001.06

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 setup 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 one or more request(s) to setup 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 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
%% MandateInitiationRequestV06 recursion level 0 with max 0
MandateInitiationRequestV06 *-- "1..1" GroupHeader80 : GroupHeader
MandateInitiationRequestV06 *-- "1..1" Mandate13 : Mandate
MandateInitiationRequestV06 *-- "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 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
%% 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

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. PartyIdentification135 - 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
%% Mandate13 recursion level 0 with max 1
class Mandate13{
    MandateIdentification IsoMax35Text
    MandateRequestIdentification IsoMax35Text
    TrackingIndicator IsoTrueFalseIndicator
    FirstCollectionAmount IsoActiveCurrencyAndAmount
    CollectionAmount IsoActiveCurrencyAndAmount
    MaximumAmount IsoActiveCurrencyAndAmount
    MandateReference IsoMax35Text
}
Mandate13 *-- "0..1" MandateAuthentication1 : Authentication
Mandate13 *-- "0..1" MandateTypeInformation2 : Type
Mandate13 *-- "0..1" MandateOccurrences4 : Occurrences
Mandate13 *-- "0..1" MandateAdjustment1 : Adjustment
Mandate13 *-- "0..1" IMandateSetupReason1Choice : Reason
Mandate13 *-- "0..1" PartyIdentification135 : CreditorSchemeIdentification
Mandate13 *-- "1..1" PartyIdentification135 : Creditor
Mandate13 *-- "0..1" CashAccount38 : CreditorAccount
Mandate13 *-- "0..1" BranchAndFinancialInstitutionIdentification6 : CreditorAgent
Mandate13 *-- "0..1" PartyIdentification135 : UltimateCreditor
Mandate13 *-- "1..1" PartyIdentification135 : Debtor
Mandate13 *-- "0..1" CashAccount38 : DebtorAccount
Mandate13 *-- "1..1" BranchAndFinancialInstitutionIdentification6 : DebtorAgent
Mandate13 *-- "0..1" PartyIdentification135 : UltimateDebtor
Mandate13 *-- "0..0" ReferredMandateDocument1 : ReferredDocument
Mandate13 *-- "0..0" SupplementaryData1 : SupplementaryData
%% MandateAuthentication1 recursion level 1 with max 1
class MandateAuthentication1{
    MessageAuthenticationCode IsoMax16Text
    Date IsoISODate
}
MandateAuthentication1 *-- "0..1" IAuthenticationChannel1Choice : Channel
%% MandateTypeInformation2 recursion level 1 with max 1
MandateTypeInformation2 *-- "0..1" IServiceLevel8Choice : ServiceLevel
MandateTypeInformation2 *-- "0..1" ILocalInstrument2Choice : LocalInstrument
MandateTypeInformation2 *-- "0..1" ICategoryPurpose1Choice : CategoryPurpose
MandateTypeInformation2 *-- "0..1" IMandateClassification1Choice : Classification
%% MandateOccurrences4 recursion level 1 with max 1
class MandateOccurrences4{
    SequenceType SequenceType2Code
    FirstCollectionDate IsoISODate
    FinalCollectionDate IsoISODate
}
MandateOccurrences4 *-- "0..1" IFrequency36Choice : Frequency
MandateOccurrences4 *-- "0..1" DatePeriodDetails1 : Duration
%% MandateAdjustment1 recursion level 1 with max 1
class MandateAdjustment1{
    DateAdjustmentRuleIndicator IsoTrueFalseIndicator
    Amount IsoActiveCurrencyAndAmount
    Rate IsoPercentageRate
}
MandateAdjustment1 *-- "0..1" IFrequency37Choice : Category
%% IMandateSetupReason1Choice 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
%% 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
%% CashAccount38 recursion level 1 with max 1
class CashAccount38{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount38 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount38 *-- "0..1" ICashAccountType2Choice : Type
CashAccount38 *-- "0..1" ProxyAccountIdentification1 : Proxy
%% BranchAndFinancialInstitutionIdentification6 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification6 *-- "1..1" FinancialInstitutionIdentification18 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification6 *-- "0..1" BranchData3 : BranchIdentification
%% 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
%% 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
%% CashAccount38 recursion level 1 with max 1
class CashAccount38{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount38 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount38 *-- "0..1" ICashAccountType2Choice : Type
CashAccount38 *-- "0..1" ProxyAccountIdentification1 : Proxy
%% BranchAndFinancialInstitutionIdentification6 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification6 *-- "1..1" FinancialInstitutionIdentification18 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification6 *-- "0..1" BranchData3 : BranchIdentification
%% 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
%% ReferredMandateDocument1 recursion level 1 with max 1
class ReferredMandateDocument1{
    Number IsoMax35Text
    CreditorReference IsoMax35Text
    RelatedDate IsoISODate
}
ReferredMandateDocument1 *-- "0..1" ReferredDocumentType4 : Type
%% SupplementaryData1 recursion level 1 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope

Mandate13 members

Member name Description Data Type / Multiplicity
MandateIdentification Unique identification, as assigned by the responsible party (such as the creditor) or agent (such as the debtor agent), to unambiguously identify the mandate. IsoMax35Text - Unknown 0..0
MandateRequestIdentification Identification for the mandate request, as assigned by the initiating party. IsoMax35Text - Required 1..1
Authentication Specifies the transport authentication details related to the mandate. MandateAuthentication1 - Optional 0..1
Type Specifies the type of mandate, such as paper, electronic or scheme. MandateTypeInformation2 - Optional 0..1
Occurrences Provides details of the duration of the mandate and occurrence of the underlying transactions. MandateOccurrences4 - Optional 0..1
TrackingIndicator Specifies whether the direct debit instructions should be automatically re-submitted periodically when bilaterally agreed. IsoTrueFalseIndicator - Required 1..1
FirstCollectionAmount Amount different from the collection amount, as it includes the costs associated with the first debited amount. IsoActiveCurrencyAndAmount - 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
Adjustment Specifies the characteristics of the adjustment applied to the collection amount of a direct debit instruction. MandateAdjustment1 - Optional 0..1
Reason Provides the reason for the setup of the mandate. IMandateSetupReason1Choice - Optional 0..1
CreditorSchemeIdentification Credit party that signs the mandate. PartyIdentification135 - Optional 0..1
Creditor Party that signs the mandate and to whom an amount of money is due. PartyIdentification135 - 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. CashAccount38 - Optional 0..1
CreditorAgent Financial institution servicing an account for the creditor. BranchAndFinancialInstitutionIdentification6 - Optional 0..1
UltimateCreditor Ultimate party to which an amount of money is due. PartyIdentification135 - Optional 0..1
Debtor Party that signs the mandate and owes an amount of money to the (ultimate) creditor. PartyIdentification135 - 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. CashAccount38 - Optional 0..1
DebtorAgent Financial institution servicing an account for the debtor. BranchAndFinancialInstitutionIdentification6 - Required 1..1
UltimateDebtor Ultimate party that owes an amount of money to the (ultimate) creditor. PartyIdentification135 - Optional 0..1
MandateReference Reference assigned by a creditor or ultimate creditor for internal usage for the mandate. IsoMax35Text - Optional 0..1
ReferredDocument Provides information to identify the underlying documents associated with the mandate. ReferredMandateDocument1 - Unknown 0..0
SupplementaryData Additional information that cannot be captured in the structured elements within the message component. SupplementaryData1 - Unknown 0..0

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

Member name Description Data Type / Multiplicity
PlaceAndName Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. IsoMax350Text - Optional 0..1
Envelope Technical element wrapping the supplementary data. IsoSupplementaryDataEnvelope1 - Required 1..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    MandateInitiationRequestV06 --|> IOuterRecord : Implements
    MandateInitiationRequestV06Document --|> IOuterDocument~MandateInitiationRequestV06~ : Implements
    class IOuterDocument~MandateInitiationRequestV06~ {
        MandateInitiationRequestV06 Message
     }

Document wrapper for serialization

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

classDiagram
    MandateInitiationRequestV06Document *-- MandateInitiationRequestV06 : 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.06">
    <MndtInitnReq>
        <GrpHdr>
            <!-- GroupHeader inner content -->
        </GrpHdr>
        <Mndt>
            <!-- Mandate inner content -->
        </Mndt>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </MndtInitnReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_bf9SE22PEei3KuUgpx7Xcw"
  nextVersions="_rUYN39cBEeq_l4BJLVUF2Q"
  previousVersion="_ecUrgUjuEeaVLL5QKJ4f-A"
  name="MandateInitiationRequestV06"
  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 setup 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 one or more request(s) to setup 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 MandateInitiationRequest message can be used in domestic and cross-border scenarios."
  registrationStatus="Registered"
  messageSet="_wRx2wU2rEeG_I4xRYCA_7g"
  xmlTag="MndtInitnReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_bf9SFW2PEei3KuUgpx7Xcw"
    nextVersions="_rUYN4dcBEeq_l4BJLVUF2Q"
    previousVersion="_ecUrg0juEeaVLL5QKJ4f-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="_bf9SF22PEei3KuUgpx7Xcw"
    nextVersions="_rUYN59cBEeq_l4BJLVUF2Q"
    previousVersion="_ecUrhUjuEeaVLL5QKJ4f-A"
    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="_G-MfEW49EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_bf9SGW2PEei3KuUgpx7Xcw"
    nextVersions="_rUYN6dcBEeq_l4BJLVUF2Q"
    previousVersion="_ecUrh0juEeaVLL5QKJ4f-A"
    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"
    minOccurs="1"
    xmlTag="Mndt"
    complexType="_Qzd7EW49EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_bf9SG22PEei3KuUgpx7Xcw"
    nextVersions="_rUYN69cBEeq_l4BJLVUF2Q"
    previousVersion="_ecUriUjuEeaVLL5QKJ4f-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="009"
    flavour="001"
    version="06" />
</messageDefinition>

ISO Building Blocks

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