Iso20022

CustomerCreditTransferInitiationV03

pain.001.001.03

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
%% CustomerCreditTransferInitiationV03 recursion level 0 with max 0
CustomerCreditTransferInitiationV03 *-- "1..1" GroupHeader32 : GroupHeader
CustomerCreditTransferInitiationV03 *-- "1..1" PaymentInstructionInformation3 : PaymentInformation

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
%% GroupHeader32 recursion level 0 with max 1
class GroupHeader32{
    MessageIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
    NumberOfTransactions IsoMax15NumericText
    ControlSum IsoDecimalNumber
}
GroupHeader32 *-- "0..2" IAuthorisation1Choice : Authorisation
GroupHeader32 *-- "1..1" PartyIdentification32 : InitiatingParty
GroupHeader32 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : ForwardingAgent
%% 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

GroupHeader32 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. BranchAndFinancialInstitutionIdentification4 - 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. Set of 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
%% PaymentInstructionInformation3 recursion level 0 with max 1
class PaymentInstructionInformation3{
    PaymentInformationIdentification IsoMax35Text
    PaymentMethod PaymentMethod3Code
    BatchBooking IsoBatchBookingIndicator
    NumberOfTransactions IsoMax15NumericText
    ControlSum IsoDecimalNumber
    RequestedExecutionDate IsoISODate
    PoolingAdjustmentDate IsoISODate
    ChargeBearer ChargeBearerType1Code
}
PaymentInstructionInformation3 *-- "0..1" PaymentTypeInformation19 : PaymentTypeInformation
PaymentInstructionInformation3 *-- "1..1" PartyIdentification32 : Debtor
PaymentInstructionInformation3 *-- "1..1" CashAccount16 : DebtorAccount
PaymentInstructionInformation3 *-- "1..1" BranchAndFinancialInstitutionIdentification4 : DebtorAgent
PaymentInstructionInformation3 *-- "0..1" CashAccount16 : DebtorAgentAccount
PaymentInstructionInformation3 *-- "0..1" PartyIdentification32 : UltimateDebtor
PaymentInstructionInformation3 *-- "0..1" CashAccount16 : ChargesAccount
PaymentInstructionInformation3 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : ChargesAccountAgent
PaymentInstructionInformation3 *-- "1..0" CreditTransferTransactionInformation10 : 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
%% 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
%% CashAccount16 recursion level 1 with max 1
class CashAccount16{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount16 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount16 *-- "0..1" CashAccountType2 : Type
%% 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
%% CreditTransferTransactionInformation10 recursion level 1 with max 1
class CreditTransferTransactionInformation10{
    ChargeBearer ChargeBearerType1Code
    InstructionForDebtorAgent IsoMax140Text
}
CreditTransferTransactionInformation10 *-- "1..1" PaymentIdentification1 : PaymentIdentification
CreditTransferTransactionInformation10 *-- "0..1" PaymentTypeInformation19 : PaymentTypeInformation
CreditTransferTransactionInformation10 *-- "1..1" IAmountType3Choice : Amount
CreditTransferTransactionInformation10 *-- "0..1" ExchangeRateInformation1 : ExchangeRateInformation
CreditTransferTransactionInformation10 *-- "0..1" Cheque6 : ChequeInstruction
CreditTransferTransactionInformation10 *-- "0..1" PartyIdentification32 : UltimateDebtor
CreditTransferTransactionInformation10 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : IntermediaryAgent1
CreditTransferTransactionInformation10 *-- "0..1" CashAccount16 : IntermediaryAgent1Account
CreditTransferTransactionInformation10 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : IntermediaryAgent2
CreditTransferTransactionInformation10 *-- "0..1" CashAccount16 : IntermediaryAgent2Account
CreditTransferTransactionInformation10 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : IntermediaryAgent3
CreditTransferTransactionInformation10 *-- "0..1" CashAccount16 : IntermediaryAgent3Account
CreditTransferTransactionInformation10 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : CreditorAgent
CreditTransferTransactionInformation10 *-- "0..1" CashAccount16 : CreditorAgentAccount
CreditTransferTransactionInformation10 *-- "0..1" PartyIdentification32 : Creditor
CreditTransferTransactionInformation10 *-- "0..1" CashAccount16 : CreditorAccount
CreditTransferTransactionInformation10 *-- "0..1" PartyIdentification32 : UltimateCreditor
CreditTransferTransactionInformation10 *-- "0..0" InstructionForCreditorAgent1 : InstructionForCreditorAgent
CreditTransferTransactionInformation10 *-- "0..1" IPurpose2Choice : Purpose
CreditTransferTransactionInformation10 *-- "0..10" RegulatoryReporting3 : RegulatoryReporting
CreditTransferTransactionInformation10 *-- "0..1" TaxInformation3 : Tax
CreditTransferTransactionInformation10 *-- "0..10" RemittanceLocation2 : RelatedRemittanceInformation
CreditTransferTransactionInformation10 *-- "0..1" RemittanceInformation5 : RemittanceInformation

PaymentInstructionInformation3 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 paymnet 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. 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 - Required 1..1
DebtorAgent Financial institution servicing an account for the debtor. BranchAndFinancialInstitutionIdentification4 - Required 1..1
DebtorAgentAccount Unambiguous identification of the account of the debtor agent at its servicing agent in the payment chain. CashAccount16 - Optional 0..1
UltimateDebtor Ultimate party that owes an amount of money to the (ultimate) creditor. PartyIdentification32 - 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 Set of elements used to provide information on the individual transaction(s) included in the message. CreditTransferTransactionInformation10 - Unknown 1..0

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    CustomerCreditTransferInitiationV03 --|> IOuterRecord : Implements
    CustomerCreditTransferInitiationV03Document --|> IOuterDocument~CustomerCreditTransferInitiationV03~ : Implements
    class IOuterDocument~CustomerCreditTransferInitiationV03~ {
        CustomerCreditTransferInitiationV03 Message
     }

Document wrapper for serialization

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

classDiagram
    CustomerCreditTransferInitiationV03Document *-- CustomerCreditTransferInitiationV03 : 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.03">
    <CstmrCdtTrfInitn>
        <GrpHdr>
            <!-- GroupHeader inner content -->
        </GrpHdr>
        <PmtInf>
            <!-- PaymentInformation inner content -->
        </PmtInf>
    </CstmrCdtTrfInitn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_GWk-idEvEd-BzquC8wXy7w_-923555762"
  nextVersions="_r-Z7IFkyEeGeoaLUQk__nA_834448268"
  previousVersion="_GWb0ldEvEd-BzquC8wXy7w_1535349168"
  name="CustomerCreditTransferInitiationV03"
  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">
  <messageBuildingBlock
    xmi:id="_GWk-itEvEd-BzquC8wXy7w_-923555699"
    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="_PzqyMtp-Ed-ak6NoX_4Aeg_21204997" />
  <messageBuildingBlock
    xmi:id="_GWk-i9EvEd-BzquC8wXy7w_-916171020"
    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="_PjuRudp-Ed-ak6NoX_4Aeg_316731131" />
  <messageDefinitionIdentifier
    businessArea="pain"
    messageFunctionality="001"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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