Iso20022

CustomerCreditTransferInitiationV06

pain.001.001.06

Scope The CustomerCreditTransferInitiation message is sent by the initiating party to the forwarding agent or debtor agent. It is used to request movement of funds from the debtor account to a creditor. Usage The CustomerCreditTransferInitiation message can contain one or more customer credit transfer instructions. The CustomerCreditTransferInitiation message is used to exchange:

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
%% CustomerCreditTransferInitiationV06 recursion level 0 with max 0
CustomerCreditTransferInitiationV06 *-- "1..1" GroupHeader48 : GroupHeader
CustomerCreditTransferInitiationV06 *-- "1..1" PaymentInstruction16 : PaymentInformation
CustomerCreditTransferInitiationV06 *-- "0..1" SupplementaryData1 : SupplementaryData

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

GroupHeader building block

Set of characteristics shared by all individual transactions included in the message. Set of characteristics shared by all individual transactions included in the message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% GroupHeader48 recursion level 0 with max 1
class GroupHeader48{
    MessageIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
    NumberOfTransactions IsoMax15NumericText
    ControlSum IsoDecimalNumber
}
GroupHeader48 *-- "0..2" IAuthorisation1Choice : Authorisation
GroupHeader48 *-- "1..1" PartyIdentification43 : InitiatingParty
GroupHeader48 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : ForwardingAgent
%% IAuthorisation1Choice recursion level 1 with max 1
%% PartyIdentification43 recursion level 1 with max 1
class PartyIdentification43{
    Name IsoMax140Text
    CountryOfResidence CountryCode
}
PartyIdentification43 *-- "0..1" PostalAddress6 : PostalAddress
PartyIdentification43 *-- "0..1" IParty11Choice : Identification
PartyIdentification43 *-- "0..1" ContactDetails2 : ContactDetails
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification

GroupHeader48 members

Member name Description Data Type / Multiplicity
MessageIdentification Point to point reference, as assigned by the instructing party, and sent to the next party in the chain 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 whether the initiating party is allowed to initiate transactions from the account specified in the message.
NumberOfTransactions Number of individual transactions contained in the message. IsoMax15NumericText - Required 1..1
ControlSum Total of all individual amounts included in the message, irrespective of currencies. IsoDecimalNumber - Optional 0..1
InitiatingParty Party that initiates the payment.
ForwardingAgent Financial institution that receives the instruction from the initiating party and forwards it to the next agent in the payment chain for execution. BranchAndFinancialInstitutionIdentification5 - Optional 0..1

PaymentInformation building block

Set of characteristics that applies to the debit side of the payment transactions included in the credit transfer initiation. Characteristics that apply to the debit side of the payment transactions included in the credit transfer initiation. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PaymentInstruction16 recursion level 0 with max 1
class PaymentInstruction16{
    PaymentInformationIdentification IsoMax35Text
    PaymentMethod PaymentMethod3Code
    BatchBooking IsoBatchBookingIndicator
    NumberOfTransactions IsoMax15NumericText
    ControlSum IsoDecimalNumber
    RequestedExecutionDate IsoISODate
    PoolingAdjustmentDate IsoISODate
    InstructionForDebtorAgent IsoMax140Text
    ChargeBearer ChargeBearerType1Code
}
PaymentInstruction16 *-- "0..1" PaymentTypeInformation19 : PaymentTypeInformation
PaymentInstruction16 *-- "1..1" PartyIdentification43 : Debtor
PaymentInstruction16 *-- "1..1" CashAccount24 : DebtorAccount
PaymentInstruction16 *-- "1..1" BranchAndFinancialInstitutionIdentification5 : DebtorAgent
PaymentInstruction16 *-- "0..1" CashAccount24 : DebtorAgentAccount
PaymentInstruction16 *-- "0..1" PartyIdentification43 : UltimateDebtor
PaymentInstruction16 *-- "0..1" CashAccount24 : ChargesAccount
PaymentInstruction16 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : ChargesAccountAgent
PaymentInstruction16 *-- "1..0" CreditTransferTransaction20 : CreditTransferTransactionInformation
%% PaymentTypeInformation19 recursion level 1 with max 1
class PaymentTypeInformation19{
    InstructionPriority Priority2Code
}
PaymentTypeInformation19 *-- "0..1" IServiceLevel8Choice : ServiceLevel
PaymentTypeInformation19 *-- "0..1" ILocalInstrument2Choice : LocalInstrument
PaymentTypeInformation19 *-- "0..1" ICategoryPurpose1Choice : CategoryPurpose
%% PartyIdentification43 recursion level 1 with max 1
class PartyIdentification43{
    Name IsoMax140Text
    CountryOfResidence CountryCode
}
PartyIdentification43 *-- "0..1" PostalAddress6 : PostalAddress
PartyIdentification43 *-- "0..1" IParty11Choice : Identification
PartyIdentification43 *-- "0..1" ContactDetails2 : ContactDetails
%% CashAccount24 recursion level 1 with max 1
class CashAccount24{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount24 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount24 *-- "0..1" ICashAccountType2Choice : Type
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% CashAccount24 recursion level 1 with max 1
class CashAccount24{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount24 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount24 *-- "0..1" ICashAccountType2Choice : Type
%% PartyIdentification43 recursion level 1 with max 1
class PartyIdentification43{
    Name IsoMax140Text
    CountryOfResidence CountryCode
}
PartyIdentification43 *-- "0..1" PostalAddress6 : PostalAddress
PartyIdentification43 *-- "0..1" IParty11Choice : Identification
PartyIdentification43 *-- "0..1" ContactDetails2 : ContactDetails
%% CashAccount24 recursion level 1 with max 1
class CashAccount24{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount24 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount24 *-- "0..1" ICashAccountType2Choice : Type
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% CreditTransferTransaction20 recursion level 1 with max 1
class CreditTransferTransaction20{
    ChargeBearer ChargeBearerType1Code
    InstructionForDebtorAgent IsoMax140Text
}
CreditTransferTransaction20 *-- "1..1" PaymentIdentification1 : PaymentIdentification
CreditTransferTransaction20 *-- "0..1" PaymentTypeInformation19 : PaymentTypeInformation
CreditTransferTransaction20 *-- "1..1" IAmountType4Choice : Amount
CreditTransferTransaction20 *-- "0..1" ExchangeRate1 : ExchangeRateInformation
CreditTransferTransaction20 *-- "0..1" Cheque7 : ChequeInstruction
CreditTransferTransaction20 *-- "0..1" PartyIdentification43 : UltimateDebtor
CreditTransferTransaction20 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : IntermediaryAgent1
CreditTransferTransaction20 *-- "0..1" CashAccount24 : IntermediaryAgent1Account
CreditTransferTransaction20 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : IntermediaryAgent2
CreditTransferTransaction20 *-- "0..1" CashAccount24 : IntermediaryAgent2Account
CreditTransferTransaction20 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : IntermediaryAgent3
CreditTransferTransaction20 *-- "0..1" CashAccount24 : IntermediaryAgent3Account
CreditTransferTransaction20 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : CreditorAgent
CreditTransferTransaction20 *-- "0..1" CashAccount24 : CreditorAgentAccount
CreditTransferTransaction20 *-- "0..1" PartyIdentification43 : Creditor
CreditTransferTransaction20 *-- "0..1" CashAccount24 : CreditorAccount
CreditTransferTransaction20 *-- "0..1" PartyIdentification43 : UltimateCreditor
CreditTransferTransaction20 *-- "0..0" InstructionForCreditorAgent1 : InstructionForCreditorAgent
CreditTransferTransaction20 *-- "0..1" IPurpose2Choice : Purpose
CreditTransferTransaction20 *-- "0..10" RegulatoryReporting3 : RegulatoryReporting
CreditTransferTransaction20 *-- "0..1" TaxInformation3 : Tax
CreditTransferTransaction20 *-- "0..10" RemittanceLocation4 : RelatedRemittanceInformation
CreditTransferTransaction20 *-- "0..1" RemittanceInformation10 : RemittanceInformation
CreditTransferTransaction20 *-- "0..0" SupplementaryData1 : SupplementaryData

PaymentInstruction16 members

Member name Description Data Type / Multiplicity
PaymentInformationIdentification Unique identification, as assigned by a sending party, to unambiguously identify the payment information group within the message. IsoMax35Text - Required 1..1
PaymentMethod Specifies the means of payment that will be used to move the amount of money. PaymentMethod3Code - Required 1..1
BatchBooking Identifies whether a single entry per individual transaction or a batch entry for the sum of the amounts of all transactions within the group of a message is requested. Usage: Batch booking is used to request and not order a possible batch booking.
NumberOfTransactions Number of individual transactions contained in the payment information group. IsoMax15NumericText - Optional 0..1
ControlSum Total of all individual amounts included in the group, irrespective of currencies. IsoDecimalNumber - Optional 0..1
PaymentTypeInformation Set of elements used to further specify the type of transaction. PaymentTypeInformation19 - Optional 0..1
RequestedExecutionDate Date at which the initiating party requests the clearing agent to process the payment. Usage: This is the date on which the debtor’s account is to be debited. If payment by cheque, the date when the cheque must be generated by the bank.
PoolingAdjustmentDate Date used for the correction of the value date of a cash pool movement that has been posted with a different value date. IsoISODate - Optional 0..1
Debtor Party that owes an amount of money to the (ultimate) creditor. PartyIdentification43 - 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. CashAccount24 - Required 1..1
DebtorAgent Financial institution servicing an account for the debtor. BranchAndFinancialInstitutionIdentification5 - Required 1..1
DebtorAgentAccount Unambiguous identification of the account of the debtor agent at its servicing agent in the payment chain. CashAccount24 - Optional 0..1
InstructionForDebtorAgent Further information related to the processing of the payment instruction, that may need to be acted upon by the debtor agent, depending on agreement between debtor and the debtor agent. Usage: when present, then the instructions for the debtor agent apply for all credit transfer transaction information occurrences, present in the payment information. IsoMax140Text - Optional 0..1
UltimateDebtor Ultimate party that owes an amount of money to the (ultimate) creditor. PartyIdentification43 - Optional 0..1
ChargeBearer Specifies which party/parties will bear the charges associated with the processing of the payment transaction. ChargeBearerType1Code - Optional 0..1
ChargesAccount Account used to process charges associated with a transaction.
ChargesAccountAgent Agent that services a charges account.
CreditTransferTransactionInformation Provides information on the individual transaction(s) included in the message. CreditTransferTransaction20 - Unknown 1..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 CustomerCreditTransferInitiationV06 implementation follows a specific implementaiton pattern. First of all, CustomerCreditTransferInitiationV06 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, CustomerCreditTransferInitiationV06Document implements IOuterDocument. Because CustomerCreditTransferInitiationV06 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type CustomerCreditTransferInitiationV06.

classDiagram
    class IOuterRecord
    CustomerCreditTransferInitiationV06 --|> IOuterRecord : Implements
    CustomerCreditTransferInitiationV06Document --|> IOuterDocument~CustomerCreditTransferInitiationV06~ : Implements
    class IOuterDocument~CustomerCreditTransferInitiationV06~ {
        CustomerCreditTransferInitiationV06 Message
     }

Document wrapper for serialization

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

classDiagram
    CustomerCreditTransferInitiationV06Document *-- CustomerCreditTransferInitiationV06 : 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.001.001.06">
    <CstmrCdtTrfInitn>
        <GrpHdr>
            <!-- GroupHeader inner content -->
        </GrpHdr>
        <PmtInf>
            <!-- PaymentInformation inner content -->
        </PmtInf>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </CstmrCdtTrfInitn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_NasXMRPeEeSVo-TFVwFHvA"
  nextVersions="_akmd6zqxEeWZFYSPlduMhw"
  previousVersion="_So2iISGmEeKjd4jizyIDGA"
  name="CustomerCreditTransferInitiationV06"
  definition="Scope&#xD;&#xA;The CustomerCreditTransferInitiation message is sent by the initiating party to the forwarding agent or debtor agent. It is used to request movement of funds from the debtor account to a creditor.&#xD;&#xA;Usage&#xD;&#xA;The CustomerCreditTransferInitiation message can contain one or more customer credit transfer instructions.&#xD;&#xA;The CustomerCreditTransferInitiation message is used to exchange:&#xD;&#xA;- One or more instances of a credit transfer initiation;&#xD;&#xA;- Payment transactions that result in book transfers at the debtor agent or payments to another financial institution;&#xD;&#xA;- Payment transactions that result in an electronic cash transfer to the creditor account or in the emission of a cheque.&#xD;&#xA;The message can be used in a direct or a relay scenario:&#xD;&#xA;- In a direct scenario, the message is sent directly to the debtor agent. The debtor agent is the account servicer of the debtor.&#xD;&#xA;- In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerCreditTransferInitiation message to the 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 debtor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate.&#xD;&#xA;The CustomerCreditTransferInitiation message can be used in domestic and cross-border scenarios.&#xD;&#xA;The CustomerCreditTransferInitiation message must not be used by the debtor agent to execute the credit transfer instruction(s). The FIToFICustomerCreditTransfer message must be used instead."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="CstmrCdtTrfInitn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_NasXMxPeEeSVo-TFVwFHvA"
    nextVersions="_akmd7TqxEeWZFYSPlduMhw"
    previousVersion="_fUu2ySHZEeKGEZlIMFwKzg"
    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="_NasXNRPeEeSVo-TFVwFHvA"
    nextVersions="_akmd7zqxEeWZFYSPlduMhw"
    previousVersion="_SpATISGmEeKjd4jizyIDGA"
    name="GroupHeader"
    definition="Set of characteristics shared by all individual transactions included in the message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="GrpHdr"
    complexType="_s4XpAFkyEeGeoaLUQk__nA_671246466" />
  <messageBuildingBlock
    xmi:id="_NasXNxPeEeSVo-TFVwFHvA"
    nextVersions="_akmd8TqxEeWZFYSPlduMhw"
    previousVersion="_SpATJSGmEeKjd4jizyIDGA"
    name="PaymentInformation"
    definition="Set of characteristics that applies to the debit side of the payment transactions included in the credit transfer initiation."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="PmtInf"
    complexType="_euj3ER77EeSxevWRRWxNAg" />
  <messageBuildingBlock
    xmi:id="_NasXORPeEeSVo-TFVwFHvA"
    nextVersions="_akmd8zqxEeWZFYSPlduMhw"
    previousVersion="_SpATKSGmEeKjd4jizyIDGA"
    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="001"
    flavour="001"
    version="06" />
</messageDefinition>

ISO Building Blocks

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