tionv06 - payments canada€¦ · these messages was defined to align with cgi-mp usage guidelines....

Usage Guideline

CorporatetoBankCustomerDirectDebitInitia-tionV06

Corporate to Bank Messages Portfolio - Draft - January 31, 2017

This document describes a usage guideline restricting the base message MX pain.008.001.06. You can also consult thisinformation online.

Published by Payments Canada and generated by MyStandards.

30 January 2017

https://www2.swift.com/mystandards/standardsPractices/mpDescription.faces?marketpractice=mp/mx/_8LABsOctEeaCLcRTfGCsKA/version/1/_8LABsectEeaCLcRTfGCsKA

https://www2.swift.com/mystandards/standardsPractices/mpDescription.faces?marketpractice=mp/mx/_8LABsOctEeaCLcRTfGCsKA/version/1/_8LABsectEeaCLcRTfGCsKA

http://www.swift.com/mystandards

Usage Guideline

2 CorporatetoBankCustomerDirectDebitInitiationV06 - Corporate to Bank Messages Portfolio - Draft - January 31, 2017

Table of Contents

.Message Functionality ................................................................................................................................................. 3

1 Restriction summary ......................................................................................................................................... 5

2 Structure ................................................................................................................................................................. 6

3 Rules ......................................................................................................................................................................... 8

4 Message Building Blocks ............................................................................................................................... 9

5 Message Components .................................................................................................................................... 12

6 Message Datatypes ........................................................................................................................................ 156

.Legal Notices ............................................................................................................................................................... 191

Message Functionality

30 January 2017 3

Message Functionality

Overview

**The following DRAFT messages are made available in support of the CPA's ISO 20022 Payment Standards Initiative for general information only. Due to the draft nature of these messages, they should not be relied upon for system development or any other purpose. The CPA accepts no responsibility for any consequences arising from the use of the draft messages. All drafts are subject to change without notice.**

These messages was defined to align with CGI-MP Usage Guidelines.

ScopeThe CustomerDirectDebitInitiation message is sent by the initiating party to the forwarding agent or creditor agent. It is used to request single or bulk collection(s) of funds from one or various debtor's account(s) for a creditor.UsageThe CustomerDirectDebitInitiation message can contain one or more direct debit instructions.The message can be used in a direct or a relay scenario:- In a direct scenario, the message is sent directly to the creditor agent. The creditor agent is the account servicer of the creditor.- 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 CustomerDirectDebitInitiation message to the creditor agent.The message can also be used by an initiating party that has authority to send the message on behalf of the creditor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate.The CustomerDirectDebitInitiation message can be used in domestic and cross-border scenarios.The CustomerDirectDebitInitiation may or may not contain mandate related information, i.e. extracts from a mandate, such as MandateIdentification or DateOfSignature. The CustomerDirectDebitInitiation message must not be considered as a mandate.The CustomerDirectDebitInitiation message must not be used by the creditor agent to execute the direct debit instruction(s). The FIToFICustomerDirectDebit message must be used instead.

Usage Guideline Description

**The following DRAFT messages are made available in support of the CPA's ISO 20022 PaymentStandards Initiative for general information only. Due to the draft nature of these messages, they shouldnot be relied upon for system development or any other purpose. The CPA accepts no responsibility forany consequences arising from the use of the draft messages. All drafts are subject to change withoutnotice.**

These messages was defined to align with CGI-MP Usage Guidelines.

Outline

The Corporate to Bank Messages Portfolio - Draft - January 31, 2017 / CorporatetoBankCustomerDi-rectDebitInitiationV06 message is composed of 3 building blocks

a. GroupHeader

Set of characteristics shared by all individual transactions included in the message.

b. PaymentInformation

Set of characteristics that apply to the credit side of the payment transactions included in the directdebit transaction initiation.

c. SupplementaryData

Usage Guideline


Additional information that cannot be captured in the structured elements and/or any other specificblock.

Restriction summary

30 January 2017 5

1 Restriction summaryThis Usage Guideline restricts the pain.008.001.06 message.

Restriction Type See page

Removed elements 8, 11, 13, 13, 13, 22, 22, 22, 27,27, 27, 27, 27, 27, 27, 27, 29, 30,32, 32, 32, 32, 35, 35, 36, 36, 36,37, 38, 38, 39, 39, 39, 48, 48, 50,52, 53, 53, 55, 64, 64, 64, 65, 65,65, 66, 66, 66, 66, 66, 66, 73, 73,74, 74, 74, 74, 77, 77, 81, 88, 92,95, 96, 97, 98, 98, 100, 102, 102, 103,103, 107, 109, 113, 113, 114, 132, 163, 163,163, 185, 185, 186, 187, 187, 187

Make mandatory 47, 105, 112, 115

Reduce Multiplicity 54, 129, 130, 135

Ignore n.a.

Text rules 79, 114

Conditional rules n.a.

Fixed values n.a.

Truncates n.a.

Comments n.a.

Annotations n.a.

Changed datatypes n.a.

Extensions n.a.

Synonyms 29, 35, 37, 38, 48, 49, 51, 77, 79,80, 100, 105, 106, 107

Usage Guideline


2 Structure Removed - Ignored - ! Details below - Mandatory - R[x..x] Repeatability[details]

Index Message Item <XML Tag> Or Mult. UsageGuidelines

Page

CustomerDirectDebitInitiationV06 <CstmrDrctDbtInitn> [1..1]

GroupHeader <GrpHdr> [1..1] 9

MessageIdentification <MsgId> [1..1] ! 79

CreationDateTime <CreDtTm> [1..1] ! 79

Authorisation <Authstn> [0..2] 80

NumberOfTransactions <NbOfTxs> [1..1] 80

ControlSum <CtrlSum> [0..1] 80

InitiatingParty <InitgPty> [1..1] 80

ForwardingAgent <FwdgAgt> [0..1] 81

PaymentInformation <PmtInf> [1..*] 9

PaymentInformationIdentification <PmtInfId> [1..1] 103

PaymentMethod <PmtMtd> [1..1] 104

BatchBooking <BtchBookg> [0..1] 104



PaymentTypeInformation <PmtTpInf> [0..1] 104

RequestedCollectionDate <ReqdColltnDt> [1..1] ! 105

Creditor <Cdtr> [1..1] 105

CreditorAccount <CdtrAcct> [1..1] ! 106

CreditorAgent <CdtrAgt> [1..1] ! 106

CreditorAgentAccount <CdtrAgtAcct> [0..1] 107

UltimateCreditor <UltmtCdtr> [0..1] 107

ChargeBearer <ChrgBr> [0..1] 108

ChargesAccount <ChrgsAcct> [0..1] 108

ChargesAccountAgent <ChrgsAcctAgt> [0..1] 108

CreditorSchemeIdentification <CdtrSchmeId> [0..1] 109

DirectDebitTransactionInformation <DrctDbtTxInf> [1..*] 109

SupplementaryData <SplmtryData> [0..*] 10

PlaceAndName <PlcAndNm> [0..1] 139

Structure

30 January 2017 7


Page

Envelope <Envlp> [1..1] 139

Usage Guideline


3 RulesR1 SupplementaryDataRule

The SupplementaryData building block at message level must not be used to provide additionalinformation about a transaction. The SupplementaryData element at transaction level should beused for that purpose.

Error handling: Undefined

Usage Guideline restrictions for this element

– This rule(pain.008.001.06/SupplementaryDataRule) is removed.

Message Building Blocks

30 January 2017 9

4 Message Building Blocks

Note The following chapter identifies the building blocks of the CustomerDirectDebitInitiationV06message definition.

4.1 GroupHeaderXML Tag: GrpHdr

Presence: [1..1]

Definition: Set of characteristics shared by all individual transactions included in the message.

The GrpHdr block contains the following elements (see datatype "GroupHeader55__1" on page 78for details)

Removed - Ignored - ! Details below - Mandatory - R[x..x] Repeatability[details]


Page








4.2 PaymentInformationXML Tag: PmtInf

Presence: [1..*]

Definition: Set of characteristics that apply to the credit side of the payment transactions included in thedirect debit transaction initiation.

Usage Guideline


The PmtInf block contains the following elements (see datatype "PaymentInstruction18__1" onpage 100 for details)



Page


















4.3 SupplementaryDataXML Tag: SplmtryData

Presence: [0..*]

Definition: Additional information that cannot be captured in the structured elements and/or any otherspecific block.

The SplmtryData block contains the following elements (see datatype "SupplementaryData1" onpage 138 for details)



Page



Message Building Blocks

30 January 2017 11

Usage Guideline details

• This element(pain.008.001.06/SupplementaryData) is removed.

Usage Guideline


5 Message Components

Note The following chapter identifies the CustomerDirectDebitInitiationV06 message compo-nents.

5.1 AccountIdentification4ChoiceDefinition: Specifies the unique identification of an account as assigned by the account servicer.



Page

IBAN <IBAN> {Or [1..1] 12

Other <Othr> Or} [1..1] 12

Used in element(s)

"Identification" on page 24

5.1.1 IBANXML Tag: IBAN

Presence: [1..1]

Definition: International Bank Account Number (IBAN) - identifier used internationally by financial institu-tions to uniquely identify the account of a customer. Further specifications of the format and content ofthe IBAN can be found in the standard ISO 13616 "Banking and related financial services - InternationalBank Account Number (IBAN)" version 1997-10-01, or later revisions.

Datatype: "IBAN2007Identifier" on page 175

5.1.2 OtherXML Tag: Othr

Presence: [1..1]

Definition: Unique identification of an account, as assigned by the account servicer, using an identifica-tion scheme.

The Othr block contains the following elements (see datatype "GenericAccountIdentification1" onpage 72 for details)



Page

Identification <Id> [1..1] 72

SchemeName <SchmeNm> [0..1] 72

Issuer <Issr> [0..1] 72

Message Components

30 January 2017 13

5.2 AccountIdentification4Choice__1Definition: Specifies the unique identification of an account as assigned by the account servicer.



Page



Used in element(s)


5.2.1 IBANXML Tag: IBAN

Presence: [1..1]

Definition: International Bank Account Number (IBAN) - identifier used internationally by financial institu-tions to uniquely identify the account of a customer. Further specifications of the format and content ofthe IBAN can be found in the standard ISO 13616 "Banking and related financial services - InternationalBank Account Number (IBAN)" version 1997-10-01, or later revisions.

Datatype: "IBAN2007Identifier" on page 175


• This element(pain.008.001.06/PaymentInformation/CreditorAccount/Identification/IBAN) is re-moved.

• This element(pain.008.001.06/PaymentInformation/ChargesAccount/Identification/IBAN) is re-moved.

• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInforma-tion/DebtorAccount/Identification/IBAN) is removed.


Presence: [1..1]

Definition: Unique identification of an account, as assigned by the account servicer, using an identifica-tion scheme.

Usage Guideline


The Othr block contains the following elements (see datatype "GenericAccountIdentification1__1" onpage 73 for details)



Page




5.3 AccountSchemeName1ChoiceDefinition: Sets of elements to identify a name of the identification scheme



Page

Code <Cd> {Or [1..1] 14

Proprietary <Prtry> Or} [1..1] 14

Used in element(s)

"SchemeName" on page 72, "SchemeName" on page 73

5.3.1 CodeXML Tag: Cd

Presence: [1..1]

Definition: Name of the identification scheme, in a coded form as published in an external list.

Datatype: "ExternalAccountIdentification1Code" on page 168

5.3.2 ProprietaryXML Tag: Prtry

Presence: [1..1]

Definition: Name of the identification scheme, in a free text form.

Datatype: "Max35Text" on page 180

5.4 AmendmentInformationDetails10Definition: Provides further details on the list of direct debit mandate elements that have been modifiedwhen the amendment indicator has been set.

Message Components

30 January 2017 15



Page

OriginalMandateIdentification <OrgnlMndtId> [0..1] 15

OriginalCreditorSchemeIdentification <OrgnlCdtrSchmeId> [0..1] 15

OriginalCreditorAgent <OrgnlCdtrAgt> [0..1] 16

OriginalCreditorAgentAccount <OrgnlCdtrAgtAcct> [0..1] 16

OriginalDebtor <OrgnlDbtr> [0..1] 17

OriginalDebtorAccount <OrgnlDbtrAcct> [0..1] 17

OriginalDebtorAgent <OrgnlDbtrAgt> [0..1] 17

OriginalDebtorAgentAccount <OrgnlDbtrAgtAcct> [0..1] 18

OriginalFinalCollectionDate <OrgnlFnlColltnDt> [0..1] 18

OriginalFrequency <OrgnlFrqcy> [0..1] 18

OriginalReason <OrgnlRsn> [0..1] 19

Used in element(s)

"AmendmentInformationDetails" on page 83

5.4.1 OriginalMandateIdentificationXML Tag: OrgnlMndtId

Presence: [0..1]

Definition: Unique identification, as assigned by the creditor, to unambiguously identify the original man-date.


5.4.2 OriginalCreditorSchemeIdentificationXML Tag: OrgnlCdtrSchmeId

Presence: [0..1]

Definition: Original creditor scheme identification that has been modified.

Usage Guideline


The OrgnlCdtrSchmeId block contains the following elements (see datatype "PartyIdentification43" onpage 92 for details)



Page

Name <Nm> [0..1] 92

PostalAddress <PstlAdr> [0..1] 92


CountryOfResidence <CtryOfRes> [0..1] 93

ContactDetails <CtctDtls> [0..1] 93

5.4.3 OriginalCreditorAgentXML Tag: OrgnlCdtrAgt

Presence: [0..1]

Definition: Original creditor agent that has been modified.

The OrgnlCdtrAgt block contains the following elements (see datatype "BranchAndFinancialInstitu-tionIdentification5" on page 20 for details)



Page

FinancialInstitutionIdentification <FinInstnId> [1..1] 20

BranchIdentification <BrnchId> [0..1] 20

5.4.4 OriginalCreditorAgentAccountXML Tag: OrgnlCdtrAgtAcct

Presence: [0..1]

Definition: Original creditor agent account that has been modified.

The OrgnlCdtrAgtAcct block contains the following elements (see datatype "CashAccount24" onpage 24 for details)



Page


Type <Tp> [0..1] 25

Currency <Ccy> [0..1] 25

Name <Nm> [0..1] 25

Message Components

30 January 2017 17

5.4.5 OriginalDebtorXML Tag: OrgnlDbtr

Presence: [0..1]

Definition: Original debtor that has been modified.

The OrgnlDbtr block contains the following elements (see datatype "PartyIdentification43" onpage 92 for details)



Page

Name <Nm> [0..1] 92





5.4.6 OriginalDebtorAccountXML Tag: OrgnlDbtrAcct

Presence: [0..1]

Definition: Original debtor account that has been modified.

The OrgnlDbtrAcct block contains the following elements (see datatype "CashAccount24" onpage 24 for details)



Page


Type <Tp> [0..1] 25


Name <Nm> [0..1] 25

5.4.7 OriginalDebtorAgentXML Tag: OrgnlDbtrAgt

Presence: [0..1]

Definition: Original debtor agent that has been modified.

Usage Guideline


The OrgnlDbtrAgt block contains the following elements (see datatype "BranchAndFinancialInstitu-tionIdentification5" on page 20 for details)



Page



5.4.8 OriginalDebtorAgentAccountXML Tag: OrgnlDbtrAgtAcct

Presence: [0..1]

Definition: Original debtor agent account that has been modified.

The OrgnlDbtrAgtAcct block contains the following elements (see datatype "CashAccount24" onpage 24 for details)



Page


Type <Tp> [0..1] 25


Name <Nm> [0..1] 25

5.4.9 OriginalFinalCollectionDateXML Tag: OrgnlFnlColltnDt

Presence: [0..1]

Definition: Original final collection date that has been modified.

Datatype: "ISODate" on page 176

5.4.10 OriginalFrequencyXML Tag: OrgnlFrqcy

Presence: [0..1]

Definition: Original frequency that has been modified.

Message Components

30 January 2017 19

The OrgnlFrqcy block contains the following elements (see datatype "Frequency21Choice" onpage 66 for details)



Page

Type <Tp> {Or [1..1] 67

Period <Prd> Or} [1..1] 67

5.4.11 OriginalReasonXML Tag: OrgnlRsn

Presence: [0..1]

Definition: Original reason for the mandate to allow the user to distinguish between different mandatesfor the same creditor.

The OrgnlRsn block contains the following elements (see datatype "MandateSetupReason1Choice" onpage 85 for details)



Page

Code <Cd> {Or [1..1] 85


5.5 Authorisation1ChoiceDefinition: Provides the details on the user identification or any user key that allows to check if the initi-ating party is allowed to issue the transaction.



Page

Code <Cd> {Or [1..1] 19


Used in element(s)

"Authorisation" on page 80


Presence: [1..1]

Definition: Specifies the authorisation, in a coded form.

Datatype: "Authorisation1Code" on page 159

Usage Guideline



Presence: [1..1]

Definition: Specifies the authorisation, in a free text form.


5.6 BranchAndFinancialInstitutionIdentification5Definition: Set of elements used to uniquely and unambiguously identify a financial institution or abranch of a financial institution.



Page



Used in element(s)

"OriginalCreditorAgent" on page 16, "OriginalDebtorAgent" on page 17

5.6.1 FinancialInstitutionIdentificationXML Tag: FinInstnId

Presence: [1..1]

Definition: Unique and unambiguous identification of a financial institution, as assigned under an inter-nationally recognised or proprietary identification scheme.

The FinInstnId block contains the following elements (see datatype "FinancialInstitutionIdentification8"on page 61 for details)



Page

BICFI <BICFI> [0..1] 62

ClearingSystemMemberIdentification <ClrSysMmbId> [0..1] 62

Name <Nm> [0..1] 62


Other <Othr> [0..1] 63

5.6.2 BranchIdentificationXML Tag: BrnchId

Presence: [0..1]

Definition: Identifies a specific branch of a financial institution.

Message Components

30 January 2017 21

Usage: This component should be used in case the identification information in the financial institutioncomponent does not provide identification up to branch level.

The BrnchId block contains the following elements (see datatype "BranchData2" on page 22 for de-tails)



Page


Name <Nm> [0..1] 23


5.7 BranchAndFinancialInstitutionIdentification5__1Definition: Set of elements used to uniquely and unambiguously identify a financial institution or abranch of a financial institution.



Page



Used in element(s)

"ChargesAccountAgent" on page 108, "CreditorAgent" on page 106, "DebtorAgent" on page 49,"ForwardingAgent" on page 81

5.7.1 FinancialInstitutionIdentificationXML Tag: FinInstnId

Presence: [1..1]

Definition: Unique and unambiguous identification of a financial institution, as assigned under an inter-nationally recognised or proprietary identification scheme.

Usage Guideline


The FinInstnId block contains the following elements (see datatype "FinancialInstitutionIdentifica-tion8__1" on page 63 for details)



Page



Name <Nm> [0..1] 65



5.7.2 BranchIdentificationXML Tag: BrnchId

Presence: [0..1]

Definition: Identifies a specific branch of a financial institution.

Usage: This component should be used in case the identification information in the financial institutioncomponent does not provide identification up to branch level.

The BrnchId block contains the following elements (see datatype "BranchData2" on page 22 for de-tails)



Page


Name <Nm> [0..1] 23



• This element(pain.008.001.06/PaymentInformation/ChargesAccountAgent/BranchIdentifica-tion) is removed.

• This element(pain.008.001.06/PaymentInformation/CreditorAgent/BranchIdentification) is re-moved.

• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor-Agent/BranchIdentification) is removed.

5.8 BranchData2Definition: Information that locates and identifies a specific branch of a financial institution.

Message Components

30 January 2017 23



Page


Name <Nm> [0..1] 23


Used in element(s)

"BranchIdentification" on page 20, "BranchIdentification" on page 22

5.8.1 IdentificationXML Tag: Id

Presence: [0..1]

Definition: Unique and unambiguous identification of a branch of a financial institution.


5.8.2 NameXML Tag: Nm

Presence: [0..1]

Definition: Name by which an agent is known and which is usually used to identify that agent.


5.8.3 PostalAddressXML Tag: PstlAdr

Presence: [0..1]

Definition: Information that locates and identifies a specific address, as defined by postal services.

Usage Guideline


The PstlAdr block contains the following elements (see datatype "PostalAddress6" on page 117 fordetails)



Page

AddressType <AdrTp> [0..1] 117

Department <Dept> [0..1] 117

SubDepartment <SubDept> [0..1] 117

StreetName <StrtNm> [0..1] 118

BuildingNumber <BldgNb> [0..1] 118

PostCode <PstCd> [0..1] 118

TownName <TwnNm> [0..1] 118

CountrySubDivision <CtrySubDvsn> [0..1] 118

Country <Ctry> [0..1] 118

AddressLine <AdrLine> [0..7] 119

5.9 CashAccount24Definition: Provides the details to identify an account.



Page


Type <Tp> [0..1] 25


Name <Nm> [0..1] 25

Used in element(s)

"CreditorAgentAccount" on page 107, "DebtorAgentAccount" on page 49, "OriginalCreditorAgen-tAccount" on page 16, "OriginalDebtorAccount" on page 17, "OriginalDebtorAgentAccount" onpage 18


Presence: [1..1]

Definition: Unique and unambiguous identification for the account between the account owner and theaccount servicer.

Message Components

30 January 2017 25

The Id block contains the following elements (see datatype "AccountIdentification4Choice" onpage 12 for details)



Page



5.9.2 TypeXML Tag: Tp

Presence: [0..1]

Definition: Specifies the nature, or use of the account.

The Tp block contains the following elements (see datatype "CashAccountType2Choice" on page 28for details)



Page

Code <Cd> {Or [1..1] 28


5.9.3 CurrencyXML Tag: Ccy

Presence: [0..1]

Definition: Identification of the currency in which the account is held.

Usage: Currency should only be used in case one and the same account number covers several cur-rencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.

Datatype: "ActiveOrHistoricCurrencyCode" on page 156


Presence: [0..1]

Definition: Name of the account, as assigned by the account servicing institution, in agreement with theaccount owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in cer-tain user communities to provide a means of identifying the account, in addition to the account owner'sidentity and the account number.


Usage Guideline


5.10 CashAccount24__1Definition: Provides the details to identify an account.



Page


Type <Tp> [0..1] 26


Name <Nm> [0..1] 27

Used in element(s)

"ChargesAccount" on page 108, "CreditorAccount" on page 106, "DebtorAccount" on page 50


Presence: [1..1]

Definition: Unique and unambiguous identification for the account between the account owner and theaccount servicer.

The Id block contains the following elements (see datatype "AccountIdentification4Choice__1" onpage 13 for details)



Page




Presence: [0..1]

Definition: Specifies the nature, or use of the account.

The Tp block contains the following elements (see datatype "CashAccountType2Choice" on page 28for details)



Page

Code <Cd> {Or [1..1] 28


Message Components

30 January 2017 27


• This element(pain.008.001.06/PaymentInformation/ChargesAccount/Type) is removed.

• This element(pain.008.001.06/PaymentInformation/CreditorAccount/Type) is removed.

• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInforma-tion/DebtorAccount/Type) is removed.

5.10.3 CurrencyXML Tag: Ccy

Presence: [0..1]

Definition: Identification of the currency in which the account is held.

Usage: Currency should only be used in case one and the same account number covers several cur-rencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.

Datatype: "ActiveOrHistoricCurrencyCode" on page 156


• This element(pain.008.001.06/PaymentInformation/CreditorAccount/Currency) is removed.

• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInforma-tion/DebtorAccount/Currency) is removed.


Presence: [0..1]

Definition: Name of the account, as assigned by the account servicing institution, in agreement with theaccount owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in cer-tain user communities to provide a means of identifying the account, in addition to the account owner'sidentity and the account number.



• This element(pain.008.001.06/PaymentInformation/ChargesAccount/Name) is removed.

• This element(pain.008.001.06/PaymentInformation/CreditorAccount/Name) is removed.

• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInforma-tion/DebtorAccount/Name) is removed.

Usage Guideline


5.11 CashAccountType2ChoiceDefinition: Nature or use of the account.



Page

Code <Cd> {Or [1..1] 28


Used in element(s)

"Type" on page 25, "Type" on page 26


Presence: [1..1]

Definition: Account type, in a coded form.

Datatype: "ExternalCashAccountType1Code" on page 169


Presence: [1..1]

Definition: Nature or use of the account in a proprietary form.


5.12 CategoryPurpose1ChoiceDefinition: Specifies the high level purpose of the instruction based on a set of pre-defined categories.

Usage: This is used by the initiating party to provide information concerning the processing of the pay-ment. It is likely to trigger special processing by any of the agents involved in the payment chain.



Page

Code <Cd> {Or [1..1] 28

Proprietary <Prtry> Or} [1..1] ! 29

Used in element(s)

"CategoryPurpose" on page 112


Message Components

30 January 2017 29

Presence: [1..1]

Definition: Category purpose, as published in an external category purpose code list.

Datatype: "ExternalCategoryPurpose1Code" on page 169


• This element(pain.008.001.06/PaymentInformation/PaymentTypeInformation/CategoryPur-pose/Code) is removed.


Presence: [1..1]

Definition: Category purpose, in a proprietary form.



• on pain.008.001.06/PaymentInformation/PaymentTypeInformation/CategoryPurpose/Propri-etary

Synonym (Transaction Type): LR D - Data Element 04

5.13 CategoryPurpose1Choice__1Definition: Specifies the high level purpose of the instruction based on a set of pre-defined categories.




Page

Code <Cd> {Or [1..1] 29


Used in element(s)

"CategoryPurpose" on page 114


Presence: [1..1]

Definition: Category purpose, as published in an external category purpose code list.

Datatype: "ExternalCategoryPurpose1Code" on page 169

Usage Guideline



• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Pay-mentTypeInformation/CategoryPurpose/Code) is removed.


Presence: [1..1]

Definition: Category purpose, in a proprietary form.

Datatype: "Exact3NumericText" on page 168

5.14 ClearingSystemIdentification2ChoiceDefinition: Choice of a clearing system identifier.



Page

Code <Cd> {Or [1..1] 30


Used in element(s)

"ClearingSystemIdentification" on page 31, "ClearingSystemIdentification" on page 32


Presence: [1..1]

Definition: Identification of a clearing system, in a coded form as published in an external list.

Datatype: "ExternalClearingSystemIdentification1Code" on page 169


Presence: [1..1]

Definition: Identification code for a clearing system, that has not yet been identified in the list of clearingsystems.


5.15 ClearingSystemMemberIdentification2Definition: Unique identification, as assigned by a clearing system, to unambiguously identify a memberof the clearing system.

Message Components

30 January 2017 31



Page

ClearingSystemIdentification <ClrSysId> [0..1] 31

MemberIdentification <MmbId> [1..1] 31

Used in element(s)

"ClearingSystemMemberIdentification" on page 62

5.15.1 ClearingSystemIdentificationXML Tag: ClrSysId

Presence: [0..1]

Definition: Specification of a pre-agreed offering between clearing agents or the channel through whichthe payment instruction is processed.

The ClrSysId block contains the following elements (see datatype"ClearingSystemIdentification2Choice" on page 30 for details)



Page

Code <Cd> {Or [1..1] 30


5.15.2 MemberIdentificationXML Tag: MmbId

Presence: [1..1]

Definition: Identification of a member of a clearing system.


5.16 ClearingSystemMemberIdentification2__1Definition: Unique identification, as assigned by a clearing system, to unambiguously identify a memberof the clearing system.



Page



Used in element(s)

"ClearingSystemMemberIdentification" on page 64

Usage Guideline


5.16.1 ClearingSystemIdentificationXML Tag: ClrSysId

Presence: [0..1]

Definition: Specification of a pre-agreed offering between clearing agents or the channel through whichthe payment instruction is processed.

The ClrSysId block contains the following elements (see datatype"ClearingSystemIdentification2Choice" on page 30 for details)



Page

Code <Cd> {Or [1..1] 30



• This element(pain.008.001.06/PaymentInformation/CreditorAgent/FinancialInstitutionIdentifi-cation/ClearingSystemMemberIdentification/ClearingSystemIdentification) is removed.

• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor-Agent/FinancialInstitutionIdentification/ClearingSystemMemberIdentification/ClearingSys-temIdentification) is removed.

• This element(pain.008.001.06/PaymentInformation/ChargesAccountAgent/FinancialInstitu-tionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification) is re-moved.

• This element(pain.008.001.06/GroupHeader/ForwardingAgent/FinancialInstitutionIdentifica-tion/ClearingSystemMemberIdentification/ClearingSystemIdentification) is removed.

5.16.2 MemberIdentificationXML Tag: MmbId

Presence: [1..1]

Definition: Identification of a member of a clearing system.

Datatype: "CPA_Exact9NumericText" on page 161

5.17 ContactDetails2Definition: Communication device number or electronic address used for communication.

Message Components

30 January 2017 33



Page

NamePrefix <NmPrfx> [0..1] 33

Name <Nm> [0..1] 33

PhoneNumber <PhneNb> [0..1] 33

MobileNumber <MobNb> [0..1] 33

FaxNumber <FaxNb> [0..1] 34

EmailAddress <EmailAdr> [0..1] 34


Used in element(s)

"ContactDetails" on page 93

5.17.1 NamePrefixXML Tag: NmPrfx

Presence: [0..1]

Definition: Specifies the terms used to formally address a person.

Datatype: "NamePrefix1Code" on page 181


Presence: [0..1]

Definition: Name by which a party is known and which is usually used to identify that party.


5.17.3 PhoneNumberXML Tag: PhneNb

Presence: [0..1]

Definition: Collection of information that identifies a phone number, as defined by telecom services.

Datatype: "PhoneNumber" on page 183

5.17.4 MobileNumberXML Tag: MobNb

Presence: [0..1]

Definition: Collection of information that identifies a mobile phone number, as defined by telecom ser-vices.


Usage Guideline


5.17.5 FaxNumberXML Tag: FaxNb

Presence: [0..1]

Definition: Collection of information that identifies a FAX number, as defined by telecom services.


5.17.6 EmailAddressXML Tag: EmailAdr

Presence: [0..1]

Definition: Address for electronic mail (e-mail).



Presence: [0..1]

Definition: Contact details in an other form.


5.18 ContactDetails2__1Definition: Communication device number or electronic address used for communication.



Page


Name <Nm> [0..1] ! 35





Other <Othr> [0..1] ! 36

Used in element(s)



Presence: [0..1]

Message Components

30 January 2017 35




• This element(pain.008.001.06/PaymentInformation/Creditor/ContactDetails/NamePrefix) is re-moved.


Presence: [0..1]




• on pain.008.001.06/PaymentInformation/Creditor/ContactDetails/Name

Synonym (Originator Long Name): LR D - Data Element 13


Presence: [0..1]




• This element(pain.008.001.06/PaymentInformation/Creditor/ContactDetails/PhoneNumber) isremoved.


Presence: [0..1]



Usage Guideline



• This element(pain.008.001.06/PaymentInformation/Creditor/ContactDetails/MobileNumber) isremoved.


Presence: [0..1]




• This element(pain.008.001.06/PaymentInformation/Creditor/ContactDetails/FaxNumber) is re-moved.


Presence: [0..1]




• This element(pain.008.001.06/PaymentInformation/Creditor/ContactDetails/EmailAddress) isremoved.


Presence: [0..1]


Datatype: "CPA_Max15Text" on page 162

Message Components

30 January 2017 37


• on pain.008.001.06/PaymentInformation/Creditor/ContactDetails/Other

Synonym (Originator Short Name): LR D - Data Element 11

5.19 ContactDetails2__2Definition: Communication device number or electronic address used for communication.



Page


Name <Nm> [0..1] ! 37






Used in element(s)



Presence: [0..1]




• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor/ContactDetails/NamePrefix) is removed.


Presence: [0..1]



Usage Guideline



• on pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor/ContactDe-tails/Name

Synonym (Payor Name): LR D - Data Element 12


Presence: [0..1]




• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor/ContactDetails/PhoneNumber) is removed.


Presence: [0..1]




• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor/ContactDetails/MobileNumber) is removed.


Presence: [0..1]



Message Components

30 January 2017 39


• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor/ContactDetails/FaxNumber) is removed.


Presence: [0..1]




• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor/ContactDetails/EmailAddress) is removed.


Presence: [0..1]




• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor/ContactDetails/Other) is removed.

5.20 CreditorReferenceInformation2Definition: Reference information provided by the creditor to allow the identification of the underlyingdocuments.



Page

Type <Tp> [0..1] 40

Reference <Ref> [0..1] 40

Used in element(s)

"CreditorReferenceInformation" on page 136

Usage Guideline



Presence: [0..1]

Definition: Specifies the type of creditor reference.

The Tp block contains the following elements (see datatype "CreditorReferenceType2" on page 41for details)



Page

CodeOrProprietary <CdOrPrtry> [1..1] 41


5.20.2 ReferenceXML Tag: Ref

Presence: [0..1]

Definition: Unique reference, as assigned by the creditor, to unambiguously refer to the payment trans-action.

Usage: If available, the initiating party should provide this reference in the structured remittance infor-mation, to enable reconciliation by the creditor upon receipt of the amount of money.

If the business context requires the use of a creditor reference or a payment remit identification, and on-ly one identifier can be passed through the end-to-end chain, the creditor's reference or payment remit-tance identification should be quoted in the end-to-end transaction identification.


5.21 CreditorReferenceType1ChoiceDefinition: Specifies the type of document referred by the creditor.



Page

Code <Cd> {Or [1..1] 40


Used in element(s)

"CodeOrProprietary" on page 41


Presence: [1..1]

Message Components

30 January 2017 41

Definition: Type of creditor reference, in a coded form.

Datatype: "DocumentType3Code" on page 165


Presence: [1..1]

Definition: Creditor reference type, in a proprietary form.


5.22 CreditorReferenceType2Definition: Specifies the type of creditor reference.



Page



Used in element(s)

"Type" on page 40

5.22.1 CodeOrProprietaryXML Tag: CdOrPrtry

Presence: [1..1]

Definition: Coded or proprietary format creditor reference type.

The CdOrPrtry block contains the following elements (see datatype "CreditorReferenceType1Choice"on page 40 for details)



Page

Code <Cd> {Or [1..1] 40


5.22.2 IssuerXML Tag: Issr

Presence: [0..1]

Definition: Entity that assigns the credit reference type.


Usage Guideline


5.23 DateAndPlaceOfBirthDefinition: Date and place of birth of a person.



Page

BirthDate <BirthDt> [1..1] 42

ProvinceOfBirth <PrvcOfBirth> [0..1] 42

CityOfBirth <CityOfBirth> [1..1] 42

CountryOfBirth <CtryOfBirth> [1..1] 42

Used in element(s)

"DateAndPlaceOfBirth" on page 115

5.23.1 BirthDateXML Tag: BirthDt

Presence: [1..1]

Definition: Date on which a person is born.


5.23.2 ProvinceOfBirthXML Tag: PrvcOfBirth

Presence: [0..1]

Definition: Province where a person was born.


5.23.3 CityOfBirthXML Tag: CityOfBirth

Presence: [1..1]

Definition: City where a person was born.


5.23.4 CountryOfBirthXML Tag: CtryOfBirth

Presence: [1..1]

Definition: Country where a person was born.

Datatype: "CountryCode" on page 164

Message Components

30 January 2017 43

5.24 DatePeriodDetailsDefinition: Range of time defined by a start date and an end date.



Page

FromDate <FrDt> [1..1] 43

ToDate <ToDt> [1..1] 43

Used in element(s)

"FromToDate" on page 152

5.24.1 FromDateXML Tag: FrDt

Presence: [1..1]

Definition: Start date of the range.


5.24.2 ToDateXML Tag: ToDt

Presence: [1..1]

Definition: End date of the range.


5.25 DirectDebitTransaction8Definition: Provides further specific details on the direct debit transaction and the related mandate.



Page

MandateRelatedInformation <MndtRltdInf> [0..1] 44


PreNotificationIdentification <PreNtfctnId> [0..1] 45

PreNotificationDate <PreNtfctnDt> [0..1] 45

Used in element(s)

"DirectDebitTransaction" on page 48

Usage Guideline


5.25.1 MandateRelatedInformationXML Tag: MndtRltdInf

Presence: [0..1]

Definition: Provides further details of the direct debit mandate signed between the creditor and thedebtor.

The MndtRltdInf block contains the following elements (see datatype "MandateRelatedInformation10"on page 82 for details)



Page

MandateIdentification <MndtId> [0..1] 83

DateOfSignature <DtOfSgntr> [0..1] 83

AmendmentIndicator <AmdmntInd> [0..1] 83

AmendmentInformationDetails <AmdmntInfDtls> [0..1] 83

ElectronicSignature <ElctrncSgntr> [0..1] 84

FirstCollectionDate <FrstColltnDt> [0..1] 84

FinalCollectionDate <FnlColltnDt> [0..1] 84

Frequency <Frqcy> [0..1] 84

Reason <Rsn> [0..1] 85

5.25.2 CreditorSchemeIdentificationXML Tag: CdtrSchmeId

Presence: [0..1]

Definition: Credit party that signs the mandate.

The CdtrSchmeId block contains the following elements (see datatype "PartyIdentification43" onpage 92 for details)



Page

Name <Nm> [0..1] 92





Message Components

30 January 2017 45

5.25.3 PreNotificationIdentificationXML Tag: PreNtfctnId

Presence: [0..1]

Definition: Unique and unambiguous identification of the pre-notification which is sent separately fromthe direct debit instruction.

Usage: The direct debit pre-notification is used to reconcile separately sent collection information withthe direct debit transaction information.


5.25.4 PreNotificationDateXML Tag: PreNtfctnDt

Presence: [0..1]

Definition: Date on which the creditor notifies the debtor about the amount and date on which the directdebit instruction will be presented to the debtor's agent.


5.26 DirectDebitTransactionInformation19__1Definition: Provides further details specific to the individual direct debit transaction(s) included in themessage.

Usage Guideline




Page

PaymentIdentification <PmtId> [1..1] 46


InstructedAmount <InstdAmt> [1..1] ! 47


DirectDebitTransaction <DrctDbtTx> [0..1] 48


DebtorAgent <DbtrAgt> [1..1] ! 49

DebtorAgentAccount <DbtrAgtAcct> [0..1] 49

Debtor <Dbtr> [1..1] 50

DebtorAccount <DbtrAcct> [1..1] ! 50

UltimateDebtor <UltmtDbtr> [0..1] 51

InstructionForCreditorAgent <InstrForCdtrAgt> [0..1] 51

Purpose <Purp> [0..1] 52

RegulatoryReporting <RgltryRptg> [0..10] 52

Tax <Tax> [0..1] 53

RelatedRemittanceInformation <RltdRmtInf> [0..10] R[0..1] 53

RemittanceInformation <RmtInf> [0..1] 54


Guidelines

1. UltimateCreditorGuideline

UltimateCreditor may only be present if different from Creditor.

2. UltimateDebtorGuideline

UltimateDebtor may only be present if different from Debtor.

Used in element(s)

"DirectDebitTransactionInformation" on page 109

5.26.1 PaymentIdentificationXML Tag: PmtId

Presence: [1..1]

Definition: Set of elements used to reference a payment instruction.

Message Components

30 January 2017 47

The PmtId block contains the following elements (see datatype "PaymentIdentification1__1" onpage 99 for details)



Page

InstructionIdentification <InstrId> [0..1] 99

EndToEndIdentification <EndToEndId> [1..1] ! 100

5.26.2 PaymentTypeInformationXML Tag: PmtTpInf

Presence: [0..1]

Definition: Set of elements used to further specify the type of transaction.

The PmtTpInf block contains the following elements (see datatype "PaymentTypeInformation24__1" onpage 112 for details)



Page

InstructionPriority <InstrPrty> [0..1] 113

ServiceLevel <SvcLvl> [0..1] 113

LocalInstrument <LclInstrm> [0..1] 113

SequenceType <SeqTp> [0..1] ! 114

CategoryPurpose <CtgyPurp> [0..1] 114


• on pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/PaymentTypeIn-formation

This element is now mandatory, the minimum occurrence has been changed to : 1

5.26.3 InstructedAmountXML Tag: InstdAmt

Presence: [1..1]

Definition: Amount of money to be moved between the debtor and creditor, before deduction ofcharges, expressed in the currency as ordered by the initiating party.

Usage: This amount has to be transported unchanged through the transaction chain.

Datatype: "CPA_Amount" on page 161

Usage Guideline



• on pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/InstructedAmount

Synonym (Amount): LR D - Data Element 05

5.26.4 ChargeBearerXML Tag: ChrgBr

Presence: [0..1]

Definition: Specifies which party/parties will bear the charges associated with the processing of the pay-ment transaction.

Datatype: "ChargeBearerType1Code" on page 162


• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Charge-Bearer) is removed.

5.26.5 DirectDebitTransactionXML Tag: DrctDbtTx

Presence: [0..1]

Definition: Provides information specific to the direct debit mandate.

The DrctDbtTx block contains the following elements (see datatype "DirectDebitTransaction8" onpage 43 for details)



Page

MandateRelatedInformation <MndtRltdInf> [0..1] 44


PreNotificationIdentification <PreNtfctnId> [0..1] 45

PreNotificationDate <PreNtfctnDt> [0..1] 45


• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Direct-DebitTransaction) is removed.

5.26.6 UltimateCreditorXML Tag: UltmtCdtr

Presence: [0..1]

Message Components

30 January 2017 49

Definition: Ultimate party to which an amount of money is due.

The UltmtCdtr block contains the following elements (see datatype "PartyIdentification43" onpage 92 for details)



Page

Name <Nm> [0..1] 92





5.26.7 DebtorAgentXML Tag: DbtrAgt

Presence: [1..1]

Definition: Financial institution servicing an account for the debtor.

The DbtrAgt block contains the following elements (see datatype "BranchAndFinancialInstitutionIdenti-fication5__1" on page 21 for details)



Page




• on pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/DebtorAgent

Synonym (Institutional Identification Number): LR D - Data Element 07

5.26.8 DebtorAgentAccountXML Tag: DbtrAgtAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the debtor agent at its servicing agent in thepayment chain.

Usage Guideline


The DbtrAgtAcct block contains the following elements (see datatype "CashAccount24" on page 24for details)



Page


Type <Tp> [0..1] 25


Name <Nm> [0..1] 25


• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor-AgentAccount) is removed.

5.26.9 DebtorXML Tag: Dbtr

Presence: [1..1]

Definition: Party that owes an amount of money to the (ultimate) creditor.

The Dbtr block contains the following elements (see datatype "PartyIdentification43__2" on page 96for details)



Page

Name <Nm> [0..1] 97





5.26.10 DebtorAccountXML Tag: DbtrAcct

Presence: [1..1]

Definition: Unambiguous identification of the account of the debtor to which a debit entry will be madeas a result of the transaction.

Message Components

30 January 2017 51

The DbtrAcct block contains the following elements (see datatype "CashAccount24__1" on page 26for details)



Page


Type <Tp> [0..1] 26


Name <Nm> [0..1] 27


• on pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/DebtorAccount

Synonym (Payor Account): LR D - Data Element 08

5.26.11 UltimateDebtorXML Tag: UltmtDbtr

Presence: [0..1]

Definition: Ultimate party that owes an amount of money to the (ultimate) creditor.

The UltmtDbtr block contains the following elements (see datatype "PartyIdentification43" onpage 92 for details)



Page

Name <Nm> [0..1] 92





5.26.12 InstructionForCreditorAgentXML Tag: InstrForCdtrAgt

Presence: [0..1]

Definition: Further information, related to the processing of the payment instruction, that may need to beacted upon by the creditor agent, depending on agreement between creditor and the creditor agent.


Usage Guideline


5.26.13 PurposeXML Tag: Purp

Presence: [0..1]

Definition: Underlying reason for the payment transaction.

Usage: Purpose is used by the end-customers, that is initiating party, (ultimate) debtor, (ultimate) credi-tor to provide information concerning the nature of the payment. Purpose is a content element, which isnot used for processing by any of the agents involved in the payment chain.

The Purp block contains the following elements (see datatype "Purpose2Choice" on page 119 for de-tails)



Page

Code <Cd> {Or [1..1] 119



• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Pur-pose) is removed.

5.26.14 RegulatoryReportingXML Tag: RgltryRptg

Presence: [0..10]

Definition: Information needed due to regulatory and statutory requirements.

The RgltryRptg block contains the following elements (see datatype "RegulatoryReporting3" onpage 123 for details)



Page

DebitCreditReportingIndicator <DbtCdtRptgInd> [0..1] 123

Authority <Authrty> [0..1] 123

Details <Dtls> [0..*] 124

Message Components

30 January 2017 53


• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Regula-toryReporting) is removed.

5.26.15 TaxXML Tag: Tax

Presence: [0..1]

Definition: Provides details on the tax.

The Tax block contains the following elements (see datatype "TaxInformation3" on page 142 for de-tails)



Page



AdministrationZone <AdmstnZn> [0..1] 144

ReferenceNumber <RefNb> [0..1] 144

Method <Mtd> [0..1] 144

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] 144

TotalTaxAmount <TtlTaxAmt> [0..1] 144

Date <Dt> [0..1] 145

SequenceNumber <SeqNb> [0..1] 145

Record <Rcrd> [0..*] 145


• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Tax) isremoved.

5.26.16 RelatedRemittanceInformationXML Tag: RltdRmtInf

Presence: [0..10]

Definition: Provides information related to the handling of the remittance information by any of theagents in the transaction processing chain.

Usage Guideline


The RltdRmtInf block contains the following elements (see datatype "RemittanceLocation4" onpage 130 for details)



Page

RemittanceIdentification <RmtId> [0..1] 130

RemittanceLocationDetails <RmtLctnDtls> [0..*] 131


• on pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/RelatedRemit-tanceInformation

This element has change repeatability, the maximum occurrence has been changed to : 1

5.26.17 RemittanceInformationXML Tag: RmtInf

Presence: [0..1]

Definition: Information supplied to enable the matching of an entry with the items that the transfer is in-tended to settle, such as commercial invoices in an accounts' receivable system.

The RmtInf block contains the following elements (see datatype "RemittanceInformation11" onpage 128 for details)



Page

Unstructured <Ustrd> [0..*] R[0..1] 129

Structured <Strd> [0..*] R[0..100000] 129

5.26.18 SupplementaryDataXML Tag: SplmtryData

Presence: [0..*]

Definition: Additional information that cannot be captured in the structured elements and/or any otherspecific block.

The SplmtryData block contains the following elements (see datatype "SupplementaryData1" onpage 138 for details)



Page



Message Components

30 January 2017 55


• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Supple-mentaryData) is removed.

5.27 DiscountAmountAndType1Definition: Specifies the amount with a specific type.



Page

Type <Tp> [0..1] 55

Amount <Amt> [1..1] 55

Used in element(s)

"DiscountAppliedAmount" on page 125, "DiscountAppliedAmount" on page 127


Presence: [0..1]

Definition: Specifies the type of the amount.

The Tp block contains the following elements (see datatype "DiscountAmountType1Choice" onpage 55 for details)



Page

Code <Cd> {Or [1..1] 56


5.27.2 AmountXML Tag: Amt

Presence: [1..1]

Definition: Amount of money, which has been typed.

Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 156

5.28 DiscountAmountType1ChoiceDefinition: Specifies the amount type.

Usage Guideline




Page

Code <Cd> {Or [1..1] 56


Used in element(s)

"Type" on page 55


Presence: [1..1]

Definition: Specifies the amount type, in a coded form.

Datatype: "ExternalDiscountAmountType1Code" on page 170


Presence: [1..1]

Definition: Specifies the amount type, in a free-text form.


5.29 DocumentAdjustment1Definition: Set of elements used to provide information on the amount and reason of the document ad-justment.



Page


CreditDebitIndicator <CdtDbtInd> [0..1] 57


AdditionalInformation <AddtlInf> [0..1] 57

Used in element(s)

"AdjustmentAmountAndReason" on page 126, "AdjustmentAmountAndReason" on page 128


Presence: [1..1]

Message Components

30 January 2017 57

Definition: Amount of money of the document adjustment.


5.29.2 CreditDebitIndicatorXML Tag: CdtDbtInd

Presence: [0..1]

Definition: Specifies whether the adjustment must be substracted or added to the total amount.

Datatype: "CreditDebitCode" on page 165

5.29.3 ReasonXML Tag: Rsn

Presence: [0..1]

Definition: Specifies the reason for the adjustment.


5.29.4 AdditionalInformationXML Tag: AddtlInf

Presence: [0..1]

Definition: Provides further details on the document adjustment.


5.30 DocumentLineIdentification1Definition: Identifies the documents referred to in the remittance information.



Page

Type <Tp> [0..1] 57

Number <Nb> [0..1] 58

RelatedDate <RltdDt> [0..1] 58

Used in element(s)



Presence: [0..1]

Definition: Specifies the type of referred document line identification.

Usage Guideline


The Tp block contains the following elements (see datatype "DocumentLineType1" on page 59 fordetails)



Page



5.30.2 NumberXML Tag: Nb

Presence: [0..1]

Definition: Identification of the type specified for the referred document line.


5.30.3 RelatedDateXML Tag: RltdDt

Presence: [0..1]

Definition: Date associated with the referred document line.


5.31 DocumentLineInformation1Definition: Provides document line information.



Page

Identification <Id> [1..*] 58

Description <Desc> [0..1] 59


Used in element(s)

"LineDetails" on page 120


Presence: [1..*]

Definition: Provides identification of the document line.

Message Components

30 January 2017 59

The Id block contains the following elements (see datatype "DocumentLineIdentification1" onpage 57 for details)



Page

Type <Tp> [0..1] 57

Number <Nb> [0..1] 58


5.31.2 DescriptionXML Tag: Desc

Presence: [0..1]

Definition: Description associated with the document line.



Presence: [0..1]

Definition: Provides details on the amounts of the document line.

The Amt block contains the following elements (see datatype "RemittanceAmount3" on page 126 fordetails)



Page

DuePayableAmount <DuePyblAmt> [0..1] 127

DiscountAppliedAmount <DscntApldAmt> [0..*] 127

CreditNoteAmount <CdtNoteAmt> [0..1] 127

TaxAmount <TaxAmt> [0..*] 128

AdjustmentAmountAndReason <AdjstmntAmtAndRsn> [0..*] 128

RemittedAmount <RmtdAmt> [0..1] 128

5.32 DocumentLineType1Definition: Specifies the type of the document line identification.

Usage Guideline




Page



Used in element(s)

"Type" on page 57


Presence: [1..1]

Definition: Provides the type details of the referred document line identification.

The CdOrPrtry block contains the following elements (see datatype "DocumentLineType1Choice" onpage 60 for details)



Page

Code <Cd> {Or [1..1] 61



Presence: [0..1]

Definition: Identification of the issuer of the reference document line identificationtype.


5.33 DocumentLineType1ChoiceDefinition: Specifies the type of the document line identification.



Page

Code <Cd> {Or [1..1] 61


Used in element(s)


Message Components

30 January 2017 61


Presence: [1..1]

Definition: Line identification type in a coded form.

Datatype: "ExternalDocumentLineType1Code" on page 170


Presence: [1..1]

Definition: Proprietary identification of the type of the remittance document.


5.34 FinancialIdentificationSchemeName1ChoiceDefinition: Sets of elements to identify a name of the organisation identification scheme.



Page

Code <Cd> {Or [1..1] 61


Used in element(s)

"SchemeName" on page 74


Presence: [1..1]


Datatype: "ExternalFinancialInstitutionIdentification1Code" on page 170


Presence: [1..1]



5.35 FinancialInstitutionIdentification8Definition: Set of elements used to identify a financial institution.

Usage Guideline




Page



Name <Nm> [0..1] 62



Used in element(s)

"FinancialInstitutionIdentification" on page 20

5.35.1 BICFIXML Tag: BICFI

Presence: [0..1]

Definition: Code allocated to a financial institution by the ISO 9362 Registration Authority as describedin ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".

Datatype: "BICFIIdentifier" on page 160

5.35.2 ClearingSystemMemberIdentificationXML Tag: ClrSysMmbId

Presence: [0..1]

Definition: Information used to identify a member within a clearing system.

The ClrSysMmbId block contains the following elements (see datatype "ClearingSystemMemberIdenti-fication2" on page 30 for details)



Page




Presence: [0..1]



Message Components

30 January 2017 63


Presence: [0..1]





Page












Presence: [0..1]

Definition: Unique identification of an agent, as assigned by an institution, using an identificationscheme.

The Othr block contains the following elements (see datatype "GenericFinancialIdentification1" onpage 74 for details)



Page




5.36 FinancialInstitutionIdentification8__1Definition: Set of elements used to identify a financial institution.

Usage Guideline




Page



Name <Nm> [0..1] 65



Used in element(s)

"FinancialInstitutionIdentification" on page 21

5.36.1 BICFIXML Tag: BICFI

Presence: [0..1]

Definition: Code allocated to a financial institution by the ISO 9362 Registration Authority as describedin ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".

Datatype: "BICFIIdentifier" on page 160


• This element(pain.008.001.06/PaymentInformation/ChargesAccountAgent/FinancialInstitu-tionIdentification/BICFI) is removed.

• This element(pain.008.001.06/PaymentInformation/CreditorAgent/FinancialInstitutionIdentifi-cation/BICFI) is removed.

• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor-Agent/FinancialInstitutionIdentification/BICFI) is removed.

5.36.2 ClearingSystemMemberIdentificationXML Tag: ClrSysMmbId

Presence: [0..1]

Definition: Information used to identify a member within a clearing system.

The ClrSysMmbId block contains the following elements (see datatype "ClearingSystemMemberIdenti-fication2__1" on page 31 for details)



Page



Message Components

30 January 2017 65


Presence: [0..1]




• This element(pain.008.001.06/PaymentInformation/ChargesAccountAgent/FinancialInstitu-tionIdentification/Name) is removed.

• This element(pain.008.001.06/PaymentInformation/CreditorAgent/FinancialInstitutionIdentifi-cation/Name) is removed.

• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor-Agent/FinancialInstitutionIdentification/Name) is removed.


Presence: [0..1]





Page











Usage Guideline



• This element(pain.008.001.06/PaymentInformation/ChargesAccountAgent/FinancialInstitu-tionIdentification/PostalAddress) is removed.

• This element(pain.008.001.06/PaymentInformation/CreditorAgent/FinancialInstitutionIdentifi-cation/PostalAddress) is removed.

• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor-Agent/FinancialInstitutionIdentification/PostalAddress) is removed.


Presence: [0..1]

Definition: Unique identification of an agent, as assigned by an institution, using an identificationscheme.

The Othr block contains the following elements (see datatype "GenericFinancialIdentification1" onpage 74 for details)



Page





• This element(pain.008.001.06/PaymentInformation/ChargesAccountAgent/FinancialInstitu-tionIdentification/Other) is removed.

• This element(pain.008.001.06/PaymentInformation/CreditorAgent/FinancialInstitutionIdentifi-cation/Other) is removed.

• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor-Agent/FinancialInstitutionIdentification/Other) is removed.

5.37 Frequency21ChoiceDefinition: Choice of format for a frequency, for example, the frequency of payment.



Page

Type <Tp> {Or [1..1] 67


Message Components

30 January 2017 67

Used in element(s)

"Frequency" on page 84, "OriginalFrequency" on page 18


Presence: [1..1]

Definition: Frequency expressed as an ISO 20022 code.

Datatype: "Frequency6Code" on page 174

5.37.2 PeriodXML Tag: Prd

Presence: [1..1]

Definition: Frequency expressed as a proprietary code.

The Prd block contains the following elements (see datatype "FrequencyPeriod1" on page 67 for de-tails)



Page

Type <Tp> [1..1] 67

CountPerPeriod <CntPerPrd> [1..1] 68

5.38 FrequencyPeriod1Definition: Defines a frequency in terms on counts per period for a specific period type.



Page

Type <Tp> [1..1] 67

CountPerPeriod <CntPerPrd> [1..1] 68

Used in element(s)

"Period" on page 67


Presence: [1..1]

Definition: Period for which the number of instructions are to be created and processed.

Datatype: "Frequency6Code" on page 174

Usage Guideline


5.38.2 CountPerPeriodXML Tag: CntPerPrd

Presence: [1..1]

Definition: Number of instructions to be created and processed during the specified period

Datatype: "DecimalNumber" on page 165

5.39 Garnishment1Definition: Provides remittance information about a payment for garnishment-related purposes.



Page

Type <Tp> [1..1] 68

Garnishee <Grnshee> [0..1] 68

GarnishmentAdministrator <GrnshmtAdmstr> [0..1] 69


Date <Dt> [0..1] 69


FamilyMedicalInsuranceIndicator <FmlyMdclInsrncInd> [0..1] 70

EmployeeTerminationIndicator <MplyeeTermntnInd> [0..1] 70

Used in element(s)

"GarnishmentRemittance" on page 137


Presence: [1..1]

Definition: Specifies the type of garnishment.

The Tp block contains the following elements (see datatype "GarnishmentType1" on page 70 for de-tails)



Page



5.39.2 GarnisheeXML Tag: Grnshee

Message Components

30 January 2017 69

Presence: [0..1]

Definition: Ultimate party that owes an amount of money to the (ultimate) creditor, in this case, to thegarnisher.

The Grnshee block contains the following elements (see datatype "PartyIdentification43" on page 92for details)



Page

Name <Nm> [0..1] 92





5.39.3 GarnishmentAdministratorXML Tag: GrnshmtAdmstr

Presence: [0..1]

Definition: Party on the credit side of the transaction who administers the garnishment on behalf of theultimate beneficiary.

The GrnshmtAdmstr block contains the following elements (see datatype "PartyIdentification43" onpage 92 for details)



Page

Name <Nm> [0..1] 92





5.39.4 ReferenceNumberXML Tag: RefNb

Presence: [0..1]

Definition: Reference information that is specific to the agency receiving the garnishment.


5.39.5 DateXML Tag: Dt

Usage Guideline


Presence: [0..1]

Definition: Date of payment which garnishment was taken from.


5.39.6 RemittedAmountXML Tag: RmtdAmt

Presence: [0..1]

Definition: Amount of money remitted for the referred document.


5.39.7 FamilyMedicalInsuranceIndicatorXML Tag: FmlyMdclInsrncInd

Presence: [0..1]

Definition: Indicates if the person to whom the garnishment applies (that is, the ultimate debtor) hasfamily medical insurance coverage available.

Datatype: "TrueFalseIndicator" on page 190

5.39.8 EmployeeTerminationIndicatorXML Tag: MplyeeTermntnInd

Presence: [0..1]

Definition: Indicates if the employment of the person to whom the garnishment applies (that is, the ulti-mate debtor) has been terminated.


5.40 GarnishmentType1Definition: Specifies the type of garnishment.



Page



Used in element(s)

"Type" on page 68


Presence: [1..1]

Definition: Provides the type details of the garnishment.

Message Components

30 January 2017 71

The CdOrPrtry block contains the following elements (see datatype "GarnishmentType1Choice" onpage 71 for details)



Page

Code <Cd> {Or [1..1] 71



Presence: [0..1]

Definition: Identification of the issuer of the garnishment type.


5.41 GarnishmentType1ChoiceDefinition: Specifies the type of garnishment.



Page

Code <Cd> {Or [1..1] 71


Used in element(s)



Presence: [1..1]

Definition: Garnishment type in a coded form.

Would suggest this to be an External Code List to contain:

GNCS Garnishment from a third party payer for Child Support

GNDP Garnishment from a Direct Payer for Child Support

GTPP Garnishment from a third party payer to taxing agency

Datatype: "ExternalGarnishmentType1Code" on page 171


Usage Guideline


Presence: [1..1]

Definition: Proprietary identification of the type of garnishment.


5.42 GenericAccountIdentification1Definition: Information related to a generic account identification.



Page




Used in element(s)

"Other" on page 12


Presence: [1..1]

Definition: Identification assigned by an institution.


5.42.2 SchemeNameXML Tag: SchmeNm

Presence: [0..1]

Definition: Name of the identification scheme.

The SchmeNm block contains the following elements (see datatype "AccountSchemeName1Choice"on page 14 for details)



Page

Code <Cd> {Or [1..1] 14



Presence: [0..1]

Definition: Entity that assigns the identification.

Message Components

30 January 2017 73


5.43 GenericAccountIdentification1__1Definition: Information related to a generic account identification.



Page




Used in element(s)

"Other" on page 13


Presence: [1..1]




Presence: [0..1]


The SchmeNm block contains the following elements (see datatype "AccountSchemeName1Choice"on page 14 for details)



Page

Code <Cd> {Or [1..1] 14



• This element(pain.008.001.06/PaymentInformation/CreditorAccount/Identification/Oth-er/SchemeName) is removed.

• This element(pain.008.001.06/PaymentInformation/ChargesAccount/Identification/Oth-er/SchemeName) is removed.

Usage Guideline


• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInforma-tion/DebtorAccount/Identification/Other/SchemeName) is removed.


Presence: [0..1]




• This element(pain.008.001.06/PaymentInformation/CreditorAccount/Identification/Other/Is-suer) is removed.

• This element(pain.008.001.06/PaymentInformation/ChargesAccount/Identification/Other/Is-suer) is removed.

• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInforma-tion/DebtorAccount/Identification/Other/Issuer) is removed.

5.44 GenericFinancialIdentification1Definition: Information related to an identification of a financial institution.



Page




Used in element(s)

"Other" on page 63, "Other" on page 66


Presence: [1..1]

Definition: Unique and unambiguous identification of a person.



Message Components

30 January 2017 75

Presence: [0..1]


The SchmeNm block contains the following elements (see datatype"FinancialIdentificationSchemeName1Choice" on page 61 for details)



Page

Code <Cd> {Or [1..1] 61



Presence: [0..1]



5.45 GenericOrganisationIdentification1Definition: Information related to an identification of an organisation.



Page




Used in element(s)

"Other" on page 87


Presence: [1..1]




Presence: [0..1]


Usage Guideline


The SchmeNm block contains the following elements (see datatype"OrganisationIdentificationSchemeName1Choice" on page 89 for details)



Page

Code <Cd> {Or [1..1] 89



Presence: [0..1]



5.46 GenericOrganisationIdentification1__1Definition: Information related to an identification of an organisation.



Page

Identification <Id> [1..1] ! 76



Used in element(s)

"Other" on page 88


Presence: [1..1]



Message Components

30 January 2017 77


• on pain.008.001.06/PaymentInformation/Creditor/Identification/OrganisationIdentification/Oth-er/Identification

Synonym (Originating Direct Clearer's User's ID): LR D - Data Element 14


Presence: [0..1]


The SchmeNm block contains the following elements (see datatype"OrganisationIdentificationSchemeName1Choice" on page 89 for details)



Page

Code <Cd> {Or [1..1] 89



• This element(pain.008.001.06/PaymentInformation/Creditor/Identification/OrganisationIdentifi-cation/Other/SchemeName) is removed.


Presence: [0..1]




• This element(pain.008.001.06/PaymentInformation/Creditor/Identification/OrganisationIdentifi-cation/Other/Issuer) is removed.

5.47 GenericPersonIdentification1Definition: Information related to an identification of a person.

Usage Guideline




Page




Used in element(s)

"Other" on page 116


Presence: [1..1]

Definition: Unique and unambiguous identification of a person.



Presence: [0..1]


The SchmeNm block contains the following elements (see datatype"PersonIdentificationSchemeName1Choice" on page 116 for details)



Page

Code <Cd> {Or [1..1] 116



Presence: [0..1]



5.48 GroupHeader55__1Definition: Set of characteristics shared by all individual transactions included in the message.

Message Components

30 January 2017 79



Page








Used in element(s)

"GroupHeader" on page 9

5.48.1 MessageIdentificationXML Tag: MsgId

Presence: [1..1]

Definition: Point to point reference, assigned by the instructing party and sent to the next party in thechain, to unambiguously identify the message.

Usage: The instructing party has to make sure that MessageIdentification is unique per instructed partyfor a pre-agreed period.



• on pain.008.001.06/GroupHeader/MessageIdentification

Synonym (File Creation Number): LR A - Data Element 04

5.48.2 CreationDateTimeXML Tag: CreDtTm

Presence: [1..1]

Definition: Date and time at which a (group of) payment instruction(s) was created by the instructingparty.

Datatype: "ISODateTime" on page 176


• on pain.008.001.06/GroupHeader/CreationDateTime

– CPA_C2B_CreationDateTime_Guideline:

Usage Guideline


This element shall be populated by the Instructing Agent with the date and local time that the message was created. This element may be used for tracing and processing, but shall not be used for validation.

• on pain.008.001.06/GroupHeader/CreationDateTime

Synonym (Creation Date): LR A - Data Element 05

5.48.3 AuthorisationXML Tag: Authstn

Presence: [0..2]

Definition: User identification or any user key that allows to check if the initiating party is allowed to initi-ate transactions from the account specified in the initiation.

Usage: The content is not of a technical nature, but reflects the organisational structure at the initiatingside. The authorisation element can typically be used in relay scenarios, payment initiations, paymentreturns or payment reversals that are initiated on behalf of a different party than the initiating party.

The Authstn block contains the following elements (see datatype "Authorisation1Choice" onpage 19 for details)



Page

Code <Cd> {Or [1..1] 19


5.48.4 NumberOfTransactionsXML Tag: NbOfTxs

Presence: [1..1]

Definition: Number of individual transactions contained in the message.

Datatype: "Max15NumericText" on page 178

5.48.5 ControlSumXML Tag: CtrlSum

Presence: [0..1]

Definition: Total of all individual amounts included in the message, irrespective of currencies.


5.48.6 InitiatingPartyXML Tag: InitgPty

Presence: [1..1]

Definition: Party that initiates the payment.

Message Components

30 January 2017 81

Usage: This can either be the creditor or a party that initiates the direct debit on behalf of the creditor.

The InitgPty block contains the following elements (see datatype "PartyIdentification43" on page 92for details)



Page

Name <Nm> [0..1] 92





5.48.7 ForwardingAgentXML Tag: FwdgAgt

Presence: [0..1]

Definition: Financial institution that receives the instruction from the initiating party and forwards it to thenext agent in the payment chain for execution.

The FwdgAgt block contains the following elements (see datatype "BranchAndFinancialInstitutionIden-tification5__1" on page 21 for details)



Page




• This element(pain.008.001.06/GroupHeader/ForwardingAgent) is removed.

5.49 LocalInstrument2ChoiceDefinition: Set of elements that further identifies the type of local instruments being requested by the ini-tiating party.



Page

Code <Cd> {Or [1..1] 82


Usage Guideline


Used in element(s)

"LocalInstrument" on page 111, "LocalInstrument" on page 113


Presence: [1..1]

Definition: Specifies the local instrument, as published in an external local instrument code list.

Datatype: "ExternalLocalInstrument1Code" on page 171


Presence: [1..1]

Definition: Specifies the local instrument, as a proprietary code.


5.50 MandateRelatedInformation10Definition: Provides further details related to a direct debit mandate signed between the creditor and thedebtor.



Page

MandateIdentification <MndtId> [0..1] 83

DateOfSignature <DtOfSgntr> [0..1] 83

AmendmentIndicator <AmdmntInd> [0..1] 83

AmendmentInformationDetails <AmdmntInfDtls> [0..1] 83

ElectronicSignature <ElctrncSgntr> [0..1] 84

FirstCollectionDate <FrstColltnDt> [0..1] 84

FinalCollectionDate <FnlColltnDt> [0..1] 84

Frequency <Frqcy> [0..1] 84


Rules

R9 AmendmentIndicatorTrueRule ✓

If AmendmentIndicator is true, then AmendementInformationDetails must be present.

Error handling:

– Error severity: Fatal

– Error Code: X00012

Message Components

30 January 2017 83

– Error Text: Invalid message content for true amendment indicator and details.

R10 AmendmentIndicatorFalseRule ✓

If AmendmentIndicator is false, then AmendmentInformationDetails is not allowed.

Error handling:



– Error Text: Invalid message content for false amendment indicator and details.

Used in element(s)

"MandateRelatedInformation" on page 44

5.50.1 MandateIdentificationXML Tag: MndtId

Presence: [0..1]

Definition: Unique identification, as assigned by the creditor, to unambiguously identify the mandate.


5.50.2 DateOfSignatureXML Tag: DtOfSgntr

Presence: [0..1]

Definition: Date on which the direct debit mandate has been signed by the debtor.


5.50.3 AmendmentIndicatorXML Tag: AmdmntInd

Presence: [0..1]

Definition: Indicator notifying whether the underlying mandate is amended or not.


5.50.4 AmendmentInformationDetailsXML Tag: AmdmntInfDtls

Presence: [0..1]

Definition: List of mandate elements that have been modified.

Usage Guideline


The AmdmntInfDtls block contains the following elements (see datatype "AmendmentInformationDe-tails10" on page 14 for details)



Page

OriginalMandateIdentification <OrgnlMndtId> [0..1] 15

OriginalCreditorSchemeIdentification <OrgnlCdtrSchmeId> [0..1] 15

OriginalCreditorAgent <OrgnlCdtrAgt> [0..1] 16

OriginalCreditorAgentAccount <OrgnlCdtrAgtAcct> [0..1] 16

OriginalDebtor <OrgnlDbtr> [0..1] 17

OriginalDebtorAccount <OrgnlDbtrAcct> [0..1] 17

OriginalDebtorAgent <OrgnlDbtrAgt> [0..1] 17

OriginalDebtorAgentAccount <OrgnlDbtrAgtAcct> [0..1] 18

OriginalFinalCollectionDate <OrgnlFnlColltnDt> [0..1] 18

OriginalFrequency <OrgnlFrqcy> [0..1] 18

OriginalReason <OrgnlRsn> [0..1] 19

5.50.5 ElectronicSignatureXML Tag: ElctrncSgntr

Presence: [0..1]

Definition: Additional security provisions, such as a digital signature, as provided by the debtor.


5.50.6 FirstCollectionDateXML Tag: FrstColltnDt

Presence: [0..1]

Definition: Date of the first collection of a direct debit as per the mandate.


5.50.7 FinalCollectionDateXML Tag: FnlColltnDt

Presence: [0..1]

Definition: Date of the final collection of a direct debit as per the mandate.


5.50.8 FrequencyXML Tag: Frqcy

Message Components

30 January 2017 85

Presence: [0..1]

Definition: Regularity with which direct debit instructions are to be created and processed.

The Frqcy block contains the following elements (see datatype "Frequency21Choice" on page 66 fordetails)



Page

Type <Tp> {Or [1..1] 67


5.50.9 ReasonXML Tag: Rsn

Presence: [0..1]

Definition: Reason for the direct debit mandate to allow the user to distinguish between different man-dates for the same creditor.

The Rsn block contains the following elements (see datatype "MandateSetupReason1Choice" onpage 85 for details)



Page

Code <Cd> {Or [1..1] 85


5.51 MandateSetupReason1ChoiceDefinition: Specifies the reason for the setup of the mandate.



Page

Code <Cd> {Or [1..1] 85


Used in element(s)

"OriginalReason" on page 19, "Reason" on page 85


Presence: [1..1]

Definition: Reason for the return, as published in an external reason code list.

Usage Guideline


Datatype: "ExternalMandateSetupReason1Code" on page 171


Presence: [1..1]

Definition: Reason for the return, in a proprietary form.


5.52 NameAndAddress10Definition: Information that locates and identifies a party.



Page

Name <Nm> [1..1] 86

Address <Adr> [1..1] 86

Used in element(s)

"PostalAddress" on page 132


Presence: [1..1]

Definition: Name by which a party is known and is usually used to identify that identity.


5.52.2 AddressXML Tag: Adr

Presence: [1..1]

Definition: Postal address of a party.

Message Components

30 January 2017 87

The Adr block contains the following elements (see datatype "PostalAddress6" on page 117 for de-tails)



Page











5.53 OrganisationIdentification8Definition: Unique and unambiguous way to identify an organisation.



Page

AnyBIC <AnyBIC> [0..1] 87

Other <Othr> [0..*] 87

Used in element(s)

"OrganisationIdentification" on page 90

5.53.1 AnyBICXML Tag: AnyBIC

Presence: [0..1]

Definition: Code allocated to a financial institution or non financial institution by the ISO 9362 Registra-tion Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Businessidentifier code (BIC)".

Datatype: "AnyBICIdentifier" on page 158


Usage Guideline


Presence: [0..*]

Definition: Unique identification of an organisation, as assigned by an institution, using an identificationscheme.

The Othr block contains the following elements (see datatype "GenericOrganisationIdentification1" onpage 75 for details)



Page




5.54 OrganisationIdentification8__1Definition: Unique and unambiguous way to identify an organisation.



Page



Used in element(s)

"OrganisationIdentification" on page 91

5.54.1 AnyBICXML Tag: AnyBIC

Presence: [0..1]

Definition: Code allocated to a financial institution or non financial institution by the ISO 9362 Registra-tion Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Businessidentifier code (BIC)".

Datatype: "AnyBICIdentifier" on page 158


• This element(pain.008.001.06/PaymentInformation/Creditor/Identification/OrganisationIdentifi-cation/AnyBIC) is removed.


Presence: [0..*]

Message Components

30 January 2017 89

Definition: Unique identification of an organisation, as assigned by an institution, using an identificationscheme.

The Othr block contains the following elements (see datatype "GenericOrganisationIdentification1__1"on page 76 for details)



Page

Identification <Id> [1..1] ! 76



5.55 OrganisationIdentificationSchemeName1ChoiceDefinition: Sets of elements to identify a name of the organisation identification scheme.



Page

Code <Cd> {Or [1..1] 89


Used in element(s)

"SchemeName" on page 75, "SchemeName" on page 77


Presence: [1..1]


Datatype: "ExternalOrganisationIdentification1Code" on page 172


Presence: [1..1]



5.56 Party11ChoiceDefinition: Nature or use of the account.

Usage Guideline




Page

OrganisationIdentification <OrgId> {Or [1..1] 90

PrivateIdentification <PrvtId> Or} [1..1] 90

Used in element(s)

"Identification" on page 93, "Identification" on page 97

5.56.1 OrganisationIdentificationXML Tag: OrgId

Presence: [1..1]

Definition: Unique and unambiguous way to identify an organisation.

The OrgId block contains the following elements (see datatype "OrganisationIdentification8" onpage 87 for details)



Page



5.56.2 PrivateIdentificationXML Tag: PrvtId

Presence: [1..1]

Definition: Unique and unambiguous identification of a person, eg, passport.

The PrvtId block contains the following elements (see datatype "PersonIdentification5" on page 115for details)



Page

DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] 115

Other <Othr> [0..*] 116

5.57 Party11Choice__1Definition: Nature or use of the account.

Message Components

30 January 2017 91



Page



Used in element(s)


5.57.1 OrganisationIdentificationXML Tag: OrgId

Presence: [1..1]

Definition: Unique and unambiguous way to identify an organisation.

The OrgId block contains the following elements (see datatype "OrganisationIdentification8__1" onpage 88 for details)



Page



5.57.2 PrivateIdentificationXML Tag: PrvtId

Presence: [1..1]

Definition: Unique and unambiguous identification of a person, eg, passport.

The PrvtId block contains the following elements (see datatype "PersonIdentification5" on page 115for details)



Page


Other <Othr> [0..*] 116

Usage Guideline



• This element(pain.008.001.06/PaymentInformation/Creditor/Identification/PrivateIdentification)is removed.

5.58 PartyIdentification43Definition: Set of elements used to identify a person or an organisation.



Page

Name <Nm> [0..1] 92





Used in element(s)

"CreditorSchemeIdentification" on page 44, "CreditorSchemeIdentification" on page 109, "Gar-nishee" on page 68, "GarnishmentAdministrator" on page 69, "InitiatingParty" on page 80, "In-voicee" on page 136, "Invoicer" on page 136, "OriginalCreditorSchemeIdentification" on page 15,"OriginalDebtor" on page 17, "UltimateCreditor" on page 107, "UltimateCreditor" on page 48,"UltimateDebtor" on page 51


Presence: [0..1]




Presence: [0..1]


Message Components

30 January 2017 93




Page












Presence: [0..1]

Definition: Unique and unambiguous identification of a party.

The Id block contains the following elements (see datatype "Party11Choice" on page 89 for details)



Page



5.58.4 CountryOfResidenceXML Tag: CtryOfRes

Presence: [0..1]

Definition: Country in which a person resides (the place of a person's home). In the case of a company,it is the country from which the affairs of that company are directed.


5.58.5 ContactDetailsXML Tag: CtctDtls

Presence: [0..1]

Usage Guideline


Definition: Set of elements used to indicate how to contact the party.

The CtctDtls block contains the following elements (see datatype "ContactDetails2" on page 32 fordetails)



Page


Name <Nm> [0..1] 33






5.59 PartyIdentification43__1Definition: Set of elements used to identify a person or an organisation.



Page

Name <Nm> [0..1] 94





Used in element(s)

"Creditor" on page 105


Presence: [0..1]




Presence: [0..1]

Message Components

30 January 2017 95





Page












• This element(pain.008.001.06/PaymentInformation/Creditor/PostalAddress) is removed.


Presence: [0..1]


The Id block contains the following elements (see datatype "Party11Choice__1" on page 90 for de-tails)



Page




Presence: [0..1]

Usage Guideline





• This element(pain.008.001.06/PaymentInformation/Creditor/CountryOfResidence) is removed.


Presence: [0..1]


The CtctDtls block contains the following elements (see datatype "ContactDetails2__1" on page 34for details)



Page


Name <Nm> [0..1] ! 35





Other <Othr> [0..1] ! 36

5.60 PartyIdentification43__2Definition: Set of elements used to identify a person or an organisation.



Page

Name <Nm> [0..1] 97





Message Components

30 January 2017 97

Used in element(s)

"Debtor" on page 50


Presence: [0..1]




Presence: [0..1]





Page












• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor/PostalAddress) is removed.


Presence: [0..1]


Usage Guideline


The Id block contains the following elements (see datatype "Party11Choice" on page 89 for details)



Page




• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor/Identification) is removed.


Presence: [0..1]




• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Debtor/CountryOfResidence) is removed.


Presence: [0..1]


Message Components

30 January 2017 99

The CtctDtls block contains the following elements (see datatype "ContactDetails2__2" on page 37for details)



Page


Name <Nm> [0..1] ! 37






5.61 PaymentIdentification1__1Definition: Set of elements used to provide further means of referencing a payment transaction.



Page

InstructionIdentification <InstrId> [0..1] 99

EndToEndIdentification <EndToEndId> [1..1] ! 100

Used in element(s)

"PaymentIdentification" on page 46

5.61.1 InstructionIdentificationXML Tag: InstrId

Presence: [0..1]

Definition: Unique identification as assigned by an instructing party for an instructed party to unambigu-ously identify the instruction.

Usage: the instruction identification is a point to point reference that can be used between the instruct-ing party and the instructed party to refer to the individual instruction. It can be included in several mes-sages related to the instruction.


Usage Guideline



• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Pay-mentIdentification/InstructionIdentification) is removed.

5.61.2 EndToEndIdentificationXML Tag: EndToEndId

Presence: [1..1]

Definition: Unique identification assigned by the initiating party to unambiguously identify the transac-tion. This identification is passed on, unchanged, throughout the entire end-to-end chain.

Usage: The end-to-end identification can be used for reconciliation or to link tasks relating to the trans-action. It can be included in several messages related to the transaction.

Datatype: "CPA_Max19Text" on page 162


• on pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/PaymentIdentifi-cation/EndToEndIdentification

Synonym (Originator's Cross Reference Number): LR D - Data Element 15

5.62 PaymentInstruction18__1Definition: Characteristics that apply to the credit side of the payment transactions included in the directdebit initiation.

Message Components

30 January 2017 101



Page


















Rules

R11 ChargeBearerRule ✓

If ChargeBearer is present, then DirectDebitTransactionInformation/ChargeBearer is not al-lowed.

If DirectDebitTransactionInformation/ChargeBearer is present, then ChargeBearer is not al-lowed.

DirectDebitTransactionInformation/ChargeBearer and ChargeBearer may both be absent.

Error handling:



– Error Text: Invalid message content for charge bearer.

Usage Guideline



– This rule(pain.008.001.06/PaymentInformation/ChargeBearerRule) is removed.

R12 ChargesAccountRule ✓

If ChargesAccountAgent is present, then ChargesAccount must be present.

Error handling:



– Error Text: Invalid message content for charges agent account.


– This rule(pain.008.001.06/PaymentInformation/ChargesAccountRule) is re-moved.

R13 PaymentTypeInformationRule ✓

If PaymentTypeInformation is present, then DirectDebitTransactionInformation/PaymentTypeIn-formation is not allowed.

Error handling:



– Error Text: Invalid message content for payment type information.

R14 CreditorSchemeIdentificationRule ✓

If CreditorSchemeIdentification is present, then DirectDebitTransactionInformation/Credi-torSchemeIdentification is not allowed.

If DirectDebitTransactionInformation/CreditorSchemeIdentification is present, then Credi-torSchemeIdentification is not allowed.

DirectDebitTransactionInformation/CreditorSchemeIdentification and CreditorSchemeIdentifica-tion may both be absent.

Error handling:



– Error Text: Invalid message content for credit scheme identification.

Message Components

30 January 2017 103


– This rule(pain.008.001.06/PaymentInformation/CreditorSchemeIdentification-Rule) is removed.

R15 UltimateCreditorRule ✓

If UltimateCreditor is present, then DirectDebitTransactionInformation/UltimateCreditor is not al-lowed.

If DirectDebitTransactionInformation/UltimateCreditor is present, then UltimateCreditor is not al-lowed.

DirectDebitTransactionInformation/UltimateCreditor and UltimateCreditor may both be absent.

Error handling:



– Error Text: Invalid message content for ultimate creditor.

R16 ChargesAccountAgentRule

If ChargesAccountAgent is present, then it must contain a branch of the CreditorAgent. It mustnot contain a completely different agent.



– This rule(pain.008.001.06/PaymentInformation/ChargesAccountAgentRule) isremoved.

Guidelines

1. UltimateCreditorGuideline

UltimateCreditor may only be present if different from Creditor.

Used in element(s)

"PaymentInformation" on page 9

5.62.1 PaymentInformationIdentificationXML Tag: PmtInfId

Presence: [1..1]

Definition: Unique identification, as assigned by a sending party, to unambiguously identify the paymentinformation group within the message.


Usage Guideline


5.62.2 PaymentMethodXML Tag: PmtMtd

Presence: [1..1]

Definition: Specifies the means of payment that will be used to move the amount of money.

Datatype: "PaymentMethod2Code" on page 182

5.62.3 BatchBookingXML Tag: BtchBookg

Presence: [0..1]

Definition: Identifies whether a single entry per individual transaction or a batch entry for the sum of theamounts 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.

Datatype: "BatchBookingIndicator" on page 161

5.62.4 NumberOfTransactionsXML Tag: NbOfTxs

Presence: [0..1]

Definition: Number of individual transactions contained in the payment information group.

Datatype: "Max15NumericText" on page 178

5.62.5 ControlSumXML Tag: CtrlSum

Presence: [0..1]

Definition: Total of all individual amounts included in the group, irrespective of currencies.


5.62.6 PaymentTypeInformationXML Tag: PmtTpInf

Presence: [0..1]

Definition: Set of elements used to further specify the type of transaction.

Message Components

30 January 2017 105

The PmtTpInf block contains the following elements (see datatype "PaymentTypeInformation24" onpage 110 for details)



Page




SequenceType <SeqTp> [0..1] 111



• on pain.008.001.06/PaymentInformation/PaymentTypeInformation


5.62.7 RequestedCollectionDateXML Tag: ReqdColltnDt

Presence: [1..1]

Definition: Date and time at which the creditor requests that the amount of money is to be collected fromthe debtor.



• on pain.008.001.06/PaymentInformation/RequestedCollectionDate

Synonym (Due Date): LR D - Data Element 06

5.62.8 CreditorXML Tag: Cdtr

Presence: [1..1]

Definition: Party to which an amount of money is due.

Usage Guideline


The Cdtr block contains the following elements (see datatype "PartyIdentification43__1" on page 94for details)



Page

Name <Nm> [0..1] 94





5.62.9 CreditorAccountXML Tag: CdtrAcct

Presence: [1..1]

Definition: Unambiguous identification of the account of the creditor to which a credit entry will be post-ed as a result of the payment transaction.

The CdtrAcct block contains the following elements (see datatype "CashAccount24__1" on page 26for details)



Page


Type <Tp> [0..1] 26


Name <Nm> [0..1] 27


• on pain.008.001.06/PaymentInformation/CreditorAccount

Synonym (Account Number for Returns (Payee Account)): LR D - Data Element 17

5.62.10 CreditorAgentXML Tag: CdtrAgt

Presence: [1..1]

Definition: Financial institution servicing an account for the creditor.

Message Components

30 January 2017 107

The CdtrAgt block contains the following elements (see datatype "BranchAndFinancialInstitutionIdenti-fication5__1" on page 21 for details)



Page




• on pain.008.001.06/PaymentInformation/CreditorAgent

Synonym (Institutional ID Number for Returns): LR D - Data Element 16

5.62.11 CreditorAgentAccountXML Tag: CdtrAgtAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the creditor agent at its servicing agent in thepayment chain.

The CdtrAgtAcct block contains the following elements (see datatype "CashAccount24" on page 24for details)



Page


Type <Tp> [0..1] 25


Name <Nm> [0..1] 25


• This element(pain.008.001.06/PaymentInformation/CreditorAgentAccount) is removed.

5.62.12 UltimateCreditorXML Tag: UltmtCdtr

Presence: [0..1]

Definition: Ultimate party to which an amount of money is due.

Usage Guideline


The UltmtCdtr block contains the following elements (see datatype "PartyIdentification43" onpage 92 for details)



Page

Name <Nm> [0..1] 92





5.62.13 ChargeBearerXML Tag: ChrgBr

Presence: [0..1]

Definition: Specifies which party/parties will bear the charges associated with the processing of the pay-ment transaction.

Datatype: "ChargeBearerType1Code" on page 162

5.62.14 ChargesAccountXML Tag: ChrgsAcct

Presence: [0..1]

Definition: Account used to process charges associated with a transaction.

Usage: Charges account should be used when charges have to be booked to an account different fromthe account identified in debtor's account.

The ChrgsAcct block contains the following elements (see datatype "CashAccount24__1" onpage 26 for details)



Page


Type <Tp> [0..1] 26


Name <Nm> [0..1] 27

5.62.15 ChargesAccountAgentXML Tag: ChrgsAcctAgt

Presence: [0..1]

Definition: Agent that services a charges account.

Message Components

30 January 2017 109

Usage: Charges account agent should only be used when the charges account agent is different fromthe creditor agent.

The ChrgsAcctAgt block contains the following elements (see datatype "BranchAndFinancialInstitu-tionIdentification5__1" on page 21 for details)



Page



5.62.16 CreditorSchemeIdentificationXML Tag: CdtrSchmeId

Presence: [0..1]

Definition: Credit party that signs the mandate.

The CdtrSchmeId block contains the following elements (see datatype "PartyIdentification43" onpage 92 for details)



Page

Name <Nm> [0..1] 92






• This element(pain.008.001.06/PaymentInformation/CreditorSchemeIdentification) is removed.

5.62.17 DirectDebitTransactionInformationXML Tag: DrctDbtTxInf

Presence: [1..*]

Definition: Provides information on the individual transaction(s) included in the message.

Usage Guideline


The DrctDbtTxInf block contains the following elements (see datatype "DirectDebitTransactionInforma-tion19__1" on page 45 for details)



Page

PaymentIdentification <PmtId> [1..1] 46


InstructedAmount <InstdAmt> [1..1] ! 47


DirectDebitTransaction <DrctDbtTx> [0..1] 48


DebtorAgent <DbtrAgt> [1..1] ! 49

DebtorAgentAccount <DbtrAgtAcct> [0..1] 49


DebtorAccount <DbtrAcct> [1..1] ! 50


InstructionForCreditorAgent <InstrForCdtrAgt> [0..1] 51

Purpose <Purp> [0..1] 52

RegulatoryReporting <RgltryRptg> [0..10] 52

Tax <Tax> [0..1] 53

RelatedRemittanceInformation <RltdRmtInf> [0..10] R[0..1] 53

RemittanceInformation <RmtInf> [0..1] 54


5.63 PaymentTypeInformation24Definition: Set of elements used to provide further details of the type of payment.



Page




SequenceType <SeqTp> [0..1] 111


Message Components

30 January 2017 111

Used in element(s)

"PaymentTypeInformation" on page 104

5.63.1 InstructionPriorityXML Tag: InstrPrty

Presence: [0..1]

Definition: Indicator of the urgency or order of importance that the instructing party would like the in-structed party to apply to the processing of the instruction.

Datatype: "Priority2Code" on page 183

5.63.2 ServiceLevelXML Tag: SvcLvl

Presence: [0..1]

Definition: Agreement under which or rules under which the transaction should be processed.

The SvcLvl block contains the following elements (see datatype "ServiceLevel8Choice" on page 132for details)



Page

Code <Cd> {Or [1..1] 132


5.63.3 LocalInstrumentXML Tag: LclInstrm

Presence: [0..1]

Definition: User community specific instrument.

Usage: This element is used to specify a local instrument, local clearing option and/or further qualify theservice or service level.

The LclInstrm block contains the following elements (see datatype "LocalInstrument2Choice" onpage 81 for details)



Page

Code <Cd> {Or [1..1] 82


5.63.4 SequenceTypeXML Tag: SeqTp

Usage Guideline


Presence: [0..1]

Definition: Identifies the direct debit sequence, such as first, recurrent, final or one-off.

Datatype: "SequenceType3Code" on page 186

5.63.5 CategoryPurposeXML Tag: CtgyPurp

Presence: [0..1]

Definition: Specifies the high level purpose of the instruction based on a set of pre-defined categories.


The CtgyPurp block contains the following elements (see datatype "CategoryPurpose1Choice" onpage 28 for details)



Page

Code <Cd> {Or [1..1] 28

Proprietary <Prtry> Or} [1..1] ! 29


• on pain.008.001.06/PaymentInformation/PaymentTypeInformation/CategoryPurpose


5.64 PaymentTypeInformation24__1Definition: Set of elements used to provide further details of the type of payment.



Page




SequenceType <SeqTp> [0..1] ! 114


Used in element(s)

"PaymentTypeInformation" on page 47

Message Components

30 January 2017 113

5.64.1 InstructionPriorityXML Tag: InstrPrty

Presence: [0..1]

Definition: Indicator of the urgency or order of importance that the instructing party would like the in-structed party to apply to the processing of the instruction.

Datatype: "Priority2Code" on page 183


• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Pay-mentTypeInformation/InstructionPriority) is removed.

5.64.2 ServiceLevelXML Tag: SvcLvl

Presence: [0..1]

Definition: Agreement under which or rules under which the transaction should be processed.

The SvcLvl block contains the following elements (see datatype "ServiceLevel8Choice" on page 132for details)



Page

Code <Cd> {Or [1..1] 132



• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Pay-mentTypeInformation/ServiceLevel) is removed.

5.64.3 LocalInstrumentXML Tag: LclInstrm

Presence: [0..1]

Definition: User community specific instrument.

Usage: This element is used to specify a local instrument, local clearing option and/or further qualify theservice or service level.

Usage Guideline


The LclInstrm block contains the following elements (see datatype "LocalInstrument2Choice" onpage 81 for details)



Page

Code <Cd> {Or [1..1] 82



• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Pay-mentTypeInformation/LocalInstrument) is removed.

5.64.4 SequenceTypeXML Tag: SeqTp

Presence: [0..1]

Definition: Identifies the direct debit sequence, such as first, recurrent, final or one-off.

Datatype: "SequenceType3Code" on page 186


• on pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/PaymentTypeIn-formation/SequenceType

– CPA_C2B_Sequence_Type_Guideline:

This element shall only be used in the event of a re-presentment of a Debit that was intiatially returned within 30 days or less.

The amount of the transaction shall be exactly the same as the original.

5.64.5 CategoryPurposeXML Tag: CtgyPurp

Presence: [0..1]

Definition: Specifies the high level purpose of the instruction based on a set of pre-defined categories.


Message Components

30 January 2017 115

The CtgyPurp block contains the following elements (see datatype "CategoryPurpose1Choice__1" onpage 29 for details)



Page

Code <Cd> {Or [1..1] 29



• on pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/PaymentTypeIn-formation/CategoryPurpose


5.65 PersonIdentification5Definition: Unique and unambiguous way to identify a person.



Page


Other <Othr> [0..*] 116

Used in element(s)

"PrivateIdentification" on page 90, "PrivateIdentification" on page 91

5.65.1 DateAndPlaceOfBirthXML Tag: DtAndPlcOfBirth

Presence: [0..1]

Definition: Date and place of birth of a person.

The DtAndPlcOfBirth block contains the following elements (see datatype "DateAndPlaceOfBirth" onpage 42 for details)



Page

BirthDate <BirthDt> [1..1] 42

ProvinceOfBirth <PrvcOfBirth> [0..1] 42

CityOfBirth <CityOfBirth> [1..1] 42

CountryOfBirth <CtryOfBirth> [1..1] 42

Usage Guideline



Presence: [0..*]

Definition: Unique identification of a person, as assigned by an institution, using an identificationscheme.

The Othr block contains the following elements (see datatype "GenericPersonIdentification1" onpage 77 for details)



Page




5.66 PersonIdentificationSchemeName1ChoiceDefinition: Sets of elements to identify a name of the identification scheme.



Page

Code <Cd> {Or [1..1] 116


Used in element(s)

"SchemeName" on page 78


Presence: [1..1]


Datatype: "ExternalPersonIdentification1Code" on page 172


Presence: [1..1]



Message Components

30 January 2017 117

5.67 PostalAddress6Definition: Information that locates and identifies a specific address, as defined by postal services.



Page











Used in element(s)

"Address" on page 86, "PostalAddress" on page 63, "PostalAddress" on page 23, "Postal-Address" on page 92, "PostalAddress" on page 65, "PostalAddress" on page 94, "PostalAd-dress" on page 97

5.67.1 AddressTypeXML Tag: AdrTp

Presence: [0..1]

Definition: Identifies the nature of the postal address.

Datatype: "AddressType2Code" on page 157

5.67.2 DepartmentXML Tag: Dept

Presence: [0..1]

Definition: Identification of a division of a large organisation or building.


5.67.3 SubDepartmentXML Tag: SubDept

Presence: [0..1]

Definition: Identification of a sub-division of a large organisation or building.

Usage Guideline



5.67.4 StreetNameXML Tag: StrtNm

Presence: [0..1]

Definition: Name of a street or thoroughfare.


5.67.5 BuildingNumberXML Tag: BldgNb

Presence: [0..1]

Definition: Number that identifies the position of a building on a street.


5.67.6 PostCodeXML Tag: PstCd

Presence: [0..1]

Definition: Identifier consisting of a group of letters and/or numbers that is added to a postal address toassist the sorting of mail.


5.67.7 TownNameXML Tag: TwnNm

Presence: [0..1]

Definition: Name of a built-up area, with defined boundaries, and a local government.


5.67.8 CountrySubDivisionXML Tag: CtrySubDvsn

Presence: [0..1]

Definition: Identifies a subdivision of a country such as state, region, county.


5.67.9 CountryXML Tag: Ctry

Presence: [0..1]

Definition: Nation with its own government.


Message Components

30 January 2017 119

5.67.10 AddressLineXML Tag: AdrLine

Presence: [0..7]

Definition: Information that locates and identifies a specific address, as defined by postal services, pre-sented in free format text.


5.68 Purpose2ChoiceDefinition: Specifies the underlying reason for the payment transaction.

Usage: Purpose is used by the end-customers, that is initiating party, (ultimate) debtor, (ultimate) credi-tor to provide information concerning the nature of the payment. Purpose is a content element, which isnot used for processing by any of the agents involved in the payment chain.



Page

Code <Cd> {Or [1..1] 119


Used in element(s)

"Purpose" on page 52


Presence: [1..1]

Definition: Underlying reason for the payment transaction, as published in an external purpose code list.

Datatype: "ExternalPurpose1Code" on page 173


Presence: [1..1]

Definition: Purpose, in a proprietary form.


5.69 ReferredDocumentInformation7Definition: Set of elements used to identify the documents referred to in the remittance information.

Usage Guideline




Page

Type <Tp> [0..1] 120

Number <Nb> [0..1] 120


LineDetails <LineDtls> [0..*] 120

Used in element(s)

"ReferredDocumentInformation" on page 135


Presence: [0..1]

Definition: Specifies the type of referred document.

The Tp block contains the following elements (see datatype "ReferredDocumentType4" on page 121for details)



Page



5.69.2 NumberXML Tag: Nb

Presence: [0..1]

Definition: Unique and unambiguous identification of the referred document.


5.69.3 RelatedDateXML Tag: RltdDt

Presence: [0..1]

Definition: Date associated with the referred document.


5.69.4 LineDetailsXML Tag: LineDtls

Presence: [0..*]

Message Components

30 January 2017 121

Definition: Set of elements used to provide the content of the referred document line.

The LineDtls block contains the following elements (see datatype "DocumentLineInformation1" onpage 58 for details)



Page

Identification <Id> [1..*] 58

Description <Desc> [0..1] 59


5.70 ReferredDocumentType3ChoiceDefinition: Specifies the type of the document referred in the remittance information.



Page

Code <Cd> {Or [1..1] 121


Used in element(s)



Presence: [1..1]

Definition: Document type in a coded form.

Datatype: "DocumentType6Code" on page 166


Presence: [1..1]

Definition: Proprietary identification of the type of the remittance document.


5.71 ReferredDocumentType4Definition: Specifies the type of the document referred in the remittance information.

Usage Guideline




Page



Used in element(s)

"Type" on page 120


Presence: [1..1]

Definition: Provides the type details of the referred document.

The CdOrPrtry block contains the following elements (see datatype "ReferredDocumentType3Choice"on page 121 for details)



Page

Code <Cd> {Or [1..1] 121



Presence: [0..1]

Definition: Identification of the issuer of the reference document type.


5.72 RegulatoryAuthority2Definition: Entity requiring the regulatory reporting information.



Page

Name <Nm> [0..1] 123


Used in element(s)

"Authority" on page 123

Message Components

30 January 2017 123


Presence: [0..1]

Definition: Name of the entity requiring the regulatory reporting information.



Presence: [0..1]

Definition: Country of the entity that requires the regulatory reporting information.


5.73 RegulatoryReporting3Definition: Information needed due to regulatory and/or statutory requirements.



Page

DebitCreditReportingIndicator <DbtCdtRptgInd> [0..1] 123

Authority <Authrty> [0..1] 123


Used in element(s)

"RegulatoryReporting" on page 52

5.73.1 DebitCreditReportingIndicatorXML Tag: DbtCdtRptgInd

Presence: [0..1]

Definition: Identifies whether the regulatory reporting information applies to the debit side, to the creditside or to both debit and credit sides of the transaction.

Datatype: "RegulatoryReportingType1Code" on page 184

5.73.2 AuthorityXML Tag: Authrty

Presence: [0..1]

Definition: Entity requiring the regulatory reporting information.

Usage Guideline


The Authrty block contains the following elements (see datatype "RegulatoryAuthority2" on page 122for details)



Page

Name <Nm> [0..1] 123


5.73.3 DetailsXML Tag: Dtls

Presence: [0..*]

Definition: Set of elements used to provide details on the regulatory reporting information.

The Dtls block contains the following elements (see datatype "StructuredRegulatoryReporting3" onpage 133 for details)



Page

Type <Tp> [0..1] 133

Date <Dt> [0..1] 133


Code <Cd> [0..1] 134

Amount <Amt> [0..1] 134

Information <Inf> [0..*] 134

5.74 RemittanceAmount2Definition: Nature of the amount and currency on a document referred to in the remittance section, typ-ically either the original amount due/payable or the amount actually remitted for the referenced docu-ment.



Page







Message Components

30 January 2017 125

Used in element(s)

"ReferredDocumentAmount" on page 135

5.74.1 DuePayableAmountXML Tag: DuePyblAmt

Presence: [0..1]

Definition: Amount specified is the exact amount due and payable to the creditor.


5.74.2 DiscountAppliedAmountXML Tag: DscntApldAmt

Presence: [0..*]

Definition: Amount specified for the referred document is the amount of discount to be applied to theamount due and payable to the creditor.

The DscntApldAmt block contains the following elements (see datatype "DiscountAmountAndType1"on page 55 for details)



Page

Type <Tp> [0..1] 55


5.74.3 CreditNoteAmountXML Tag: CdtNoteAmt

Presence: [0..1]

Definition: Amount specified for the referred document is the amount of a credit note.


5.74.4 TaxAmountXML Tag: TaxAmt

Presence: [0..*]

Definition: Quantity of cash resulting from the calculation of the tax.

Usage Guideline


The TaxAmt block contains the following elements (see datatype "TaxAmountAndType1" onpage 140 for details)



Page

Type <Tp> [0..1] 140

Amount <Amt> [1..1] 141

5.74.5 AdjustmentAmountAndReasonXML Tag: AdjstmntAmtAndRsn

Presence: [0..*]

Definition: Specifies detailed information on the amount and reason of the document adjustment.

The AdjstmntAmtAndRsn block contains the following elements (see datatype "DocumentAdjust-ment1" on page 56 for details)



Page






Presence: [0..1]

Definition: Amount of money remitted for the referred document.


5.75 RemittanceAmount3Definition: Nature of the amount and currency on a document referred to in the remittance section, typ-ically either the original amount due/payable or the amount actually remitted for the referenced docu-ment.

Message Components

30 January 2017 127



Page







Used in element(s)

"Amount" on page 59

5.75.1 DuePayableAmountXML Tag: DuePyblAmt

Presence: [0..1]

Definition: Amount specified is the exact amount due and payable to the creditor.


5.75.2 DiscountAppliedAmountXML Tag: DscntApldAmt

Presence: [0..*]

Definition: Amount of discount to be applied to the amount due and payable to the creditor.

The DscntApldAmt block contains the following elements (see datatype "DiscountAmountAndType1"on page 55 for details)



Page

Type <Tp> [0..1] 55


5.75.3 CreditNoteAmountXML Tag: CdtNoteAmt

Presence: [0..1]

Definition: Amount of a credit note.


Usage Guideline



Presence: [0..*]

Definition: Amount of the tax.

The TaxAmt block contains the following elements (see datatype "TaxAmountAndType1" onpage 140 for details)



Page

Type <Tp> [0..1] 140

Amount <Amt> [1..1] 141

5.75.5 AdjustmentAmountAndReasonXML Tag: AdjstmntAmtAndRsn

Presence: [0..*]

Definition: Specifies detailed information on the amount and reason of the adjustment.

The AdjstmntAmtAndRsn block contains the following elements (see datatype "DocumentAdjust-ment1" on page 56 for details)



Page






Presence: [0..1]

Definition: Amount of money remitted.


5.76 RemittanceInformation11Definition: Information supplied to enable the matching/reconciliation of an entry with the items that thepayment is intended to settle, such as commercial invoices in an accounts' receivable system.

Message Components

30 January 2017 129



Page

Unstructured <Ustrd> [0..*] R[0..1] 129

Structured <Strd> [0..*] R[0..100000] 129

Used in element(s)

"RemittanceInformation" on page 54

5.76.1 UnstructuredXML Tag: Ustrd

Presence: [0..*]

Definition: Information supplied to enable the matching/reconciliation of an entry with the items that thepayment is intended to settle, such as commercial invoices in an accounts' receivable system, in an un-structured form.



• on pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/RemittanceInfor-mation/Unstructured


5.76.2 StructuredXML Tag: Strd

Presence: [0..*]

Definition: Information supplied to enable the matching/reconciliation of an entry with the items thatthe payment is intended to settle, such as commercial invoices in an accounts' receivable system, in astructured form.

Usage Guideline


The Strd block contains the following elements (see datatype "StructuredRemittanceInformation13" onpage 134 for details)



Page

ReferredDocumentInformation <RfrdDocInf> [0..*] R[0..1] 135

ReferredDocumentAmount <RfrdDocAmt> [0..1] 135

CreditorReferenceInformation <CdtrRefInf> [0..1] 136

Invoicer <Invcr> [0..1] 136

Invoicee <Invcee> [0..1] 136

TaxRemittance <TaxRmt> [0..1] 137

GarnishmentRemittance <GrnshmtRmt> [0..1] 137

AdditionalRemittanceInformation <AddtlRmtInf> [0..3] 138


• on pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/RemittanceInfor-mation/Structured


5.77 RemittanceLocation4Definition: Set of elements used to provide information on the remittance advice.



Page

RemittanceIdentification <RmtId> [0..1] 130

RemittanceLocationDetails <RmtLctnDtls> [0..*] 131

Used in element(s)

"RelatedRemittanceInformation" on page 53

5.77.1 RemittanceIdentificationXML Tag: RmtId

Presence: [0..1]

Definition: Unique identification, as assigned by the initiating party, to unambiguously identify the remit-tance information sent separately from the payment instruction, such as a remittance advice.


Message Components

30 January 2017 131

5.77.2 RemittanceLocationDetailsXML Tag: RmtLctnDtls

Presence: [0..*]

Definition: Set of elements used to provide information on the location and/or delivery of the remittanceinformation.

The RmtLctnDtls block contains the following elements (see datatype "RemittanceLocationDetails1" onpage 131 for details)



Page

Method <Mtd> [1..1] 131

ElectronicAddress <ElctrncAdr> [0..1] 131


5.78 RemittanceLocationDetails1Definition: Provides information on the remittance advice.



Page

Method <Mtd> [1..1] 131

ElectronicAddress <ElctrncAdr> [0..1] 131


Used in element(s)

"RemittanceLocationDetails" on page 131

5.78.1 MethodXML Tag: Mtd

Presence: [1..1]

Definition: Method used to deliver the remittance advice information.

Datatype: "RemittanceLocationMethod2Code" on page 185

5.78.2 ElectronicAddressXML Tag: ElctrncAdr

Presence: [0..1]

Definition: Electronic address to which an agent is to send the remittance information.


Usage Guideline



Presence: [0..1]

Definition: Postal address to which an agent is to send the remittance information.

The PstlAdr block contains the following elements (see datatype "NameAndAddress10" on page 86for details)



Page

Name <Nm> [1..1] 86

Address <Adr> [1..1] 86


• This element(pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/Relate-dRemittanceInformation/RemittanceLocationDetails/PostalAddress) is removed.

5.79 ServiceLevel8ChoiceDefinition: Specifies the service level of the transaction.



Page

Code <Cd> {Or [1..1] 132


Used in element(s)

"ServiceLevel" on page 111, "ServiceLevel" on page 113


Presence: [1..1]

Definition: Specifies a pre-agreed service or level of service between the parties, as published in an ex-ternal service level code list.

Datatype: "ExternalServiceLevel1Code" on page 173


Presence: [1..1]

Message Components

30 January 2017 133

Definition: Specifies a pre-agreed service or level of service between the parties, as a proprietary code.


5.80 StructuredRegulatoryReporting3Definition: Information needed due to regulatory and statutory requirements.



Page

Type <Tp> [0..1] 133

Date <Dt> [0..1] 133


Code <Cd> [0..1] 134

Amount <Amt> [0..1] 134

Information <Inf> [0..*] 134

Used in element(s)

"Details" on page 124


Presence: [0..1]

Definition: Specifies the type of the information supplied in the regulatory reporting details.



Presence: [0..1]

Definition: Date related to the specified type of regulatory reporting details.



Presence: [0..1]

Definition: Country related to the specified type of regulatory reporting details.


Usage Guideline



Presence: [0..1]

Definition: Specifies the nature, purpose, and reason for the transaction to be reported for regulatoryand statutory requirements in a coded form.



Presence: [0..1]

Definition: Amount of money to be reported for regulatory and statutory requirements.


5.80.6 InformationXML Tag: Inf

Presence: [0..*]

Definition: Additional details that cater for specific domestic regulatory requirements.


5.81 StructuredRemittanceInformation13Definition: Information supplied to enable the matching/reconciliation of an entry with the items thatthe payment is intended to settle, such as commercial invoices in an accounts' receivable system, in astructured form.



Page

ReferredDocumentInformation <RfrdDocInf> [0..*] R[0..1] 135

ReferredDocumentAmount <RfrdDocAmt> [0..1] 135

CreditorReferenceInformation <CdtrRefInf> [0..1] 136

Invoicer <Invcr> [0..1] 136

Invoicee <Invcee> [0..1] 136

TaxRemittance <TaxRmt> [0..1] 137

GarnishmentRemittance <GrnshmtRmt> [0..1] 137

AdditionalRemittanceInformation <AddtlRmtInf> [0..3] 138

Used in element(s)

"Structured" on page 129

Message Components

30 January 2017 135

5.81.1 ReferredDocumentInformationXML Tag: RfrdDocInf

Presence: [0..*]

Definition: Provides the identification and the content of the referred document.

The RfrdDocInf block contains the following elements (see datatype "ReferredDocumentInformation7"on page 119 for details)



Page

Type <Tp> [0..1] 120

Number <Nb> [0..1] 120


LineDetails <LineDtls> [0..*] 120


• on pain.008.001.06/PaymentInformation/DirectDebitTransactionInformation/RemittanceInfor-mation/Structured/ReferredDocumentInformation


5.81.2 ReferredDocumentAmountXML Tag: RfrdDocAmt

Presence: [0..1]

Definition: Provides details on the amounts of the referred document.

The RfrdDocAmt block contains the following elements (see datatype "RemittanceAmount2" onpage 124 for details)



Page







Usage Guideline


5.81.3 CreditorReferenceInformationXML Tag: CdtrRefInf

Presence: [0..1]

Definition: Reference information provided by the creditor to allow the identification of the underlyingdocuments.

The CdtrRefInf block contains the following elements (see datatype "CreditorReferenceInformation2"on page 39 for details)



Page

Type <Tp> [0..1] 40

Reference <Ref> [0..1] 40

5.81.4 InvoicerXML Tag: Invcr

Presence: [0..1]

Definition: Identification of the organisation issuing the invoice, when it is different from the creditor orultimate creditor.

The Invcr block contains the following elements (see datatype "PartyIdentification43" on page 92 fordetails)



Page

Name <Nm> [0..1] 92





5.81.5 InvoiceeXML Tag: Invcee

Presence: [0..1]

Definition: Identification of the party to whom an invoice is issued, when it is different from the debtor orultimate debtor.

Message Components

30 January 2017 137

The Invcee block contains the following elements (see datatype "PartyIdentification43" on page 92for details)



Page

Name <Nm> [0..1] 92





5.81.6 TaxRemittanceXML Tag: TaxRmt

Presence: [0..1]

Definition: Provides remittance information about a payment made for tax-related purposes.

The TaxRmt block contains the following elements (see datatype "TaxInformation4" on page 145 fordetails)



Page




AdministrationZone <AdmstnZone> [0..1] 147


Method <Mtd> [0..1] 147



Date <Dt> [0..1] 148



5.81.7 GarnishmentRemittanceXML Tag: GrnshmtRmt

Presence: [0..1]

Definition: Provides remittance information about a payment for garnishment-related purposes.

Usage Guideline


The GrnshmtRmt block contains the following elements (see datatype "Garnishment1" on page 68for details)



Page

Type <Tp> [1..1] 68

Garnishee <Grnshee> [0..1] 68

GarnishmentAdministrator <GrnshmtAdmstr> [0..1] 69


Date <Dt> [0..1] 69


FamilyMedicalInsuranceIndicator <FmlyMdclInsrncInd> [0..1] 70

EmployeeTerminationIndicator <MplyeeTermntnInd> [0..1] 70

5.81.8 AdditionalRemittanceInformationXML Tag: AddtlRmtInf

Presence: [0..3]

Definition: Additional information, in free text form, to complement the structured remittance information.


5.82 SupplementaryData1Definition: Additional information that can not be captured in the structured fields and/or any other spe-cific block.



Page



Rules

R7 SupplementaryDataRule

This component may not be used without the explicit approval of a SEG and submission to theRA of ISO 20022 compliant structure(s) to be used in the Envelope element.


Used in element(s)

"SupplementaryData" on page 10, "SupplementaryData" on page 54

Message Components

30 January 2017 139

5.82.1 PlaceAndNameXML Tag: PlcAndNm

Presence: [0..1]

Definition: Unambiguous reference to the location where the supplementary data must be inserted inthe message instance.

In the case of XML, this is expressed by a valid XPath.


5.82.2 EnvelopeXML Tag: Envlp

Presence: [1..1]

Definition: Technical element wrapping the supplementary data.

5.83 TaxAmount1Definition: Set of elements used to provide information on the tax amount(s) of tax record.



Page

Rate <Rate> [0..1] 139

TaxableBaseAmount <TaxblBaseAmt> [0..1] 139

TotalAmount <TtlAmt> [0..1] 140


Used in element(s)

"TaxAmount" on page 154

5.83.1 RateXML Tag: Rate

Presence: [0..1]

Definition: Rate used to calculate the tax.

Datatype: "PercentageRate" on page 182

5.83.2 TaxableBaseAmountXML Tag: TaxblBaseAmt

Presence: [0..1]

Definition: Amount of money on which the tax is based.


Usage Guideline


5.83.3 TotalAmountXML Tag: TtlAmt

Presence: [0..1]

Definition: Total amount that is the result of the calculation of the tax for the record.


5.83.4 DetailsXML Tag: Dtls

Presence: [0..*]

Definition: Set of elements used to provide details on the tax period and amount.

The Dtls block contains the following elements (see datatype "TaxRecordDetails1" on page 154 fordetails)



Page

Period <Prd> [0..1] 155

Amount <Amt> [1..1] 155

5.84 TaxAmountAndType1Definition: Specifies the amount with a specific type.



Page

Type <Tp> [0..1] 140

Amount <Amt> [1..1] 141

Used in element(s)

"TaxAmount" on page 125, "TaxAmount" on page 128


Presence: [0..1]

Definition: Specifies the type of the amount.

Message Components

30 January 2017 141

The Tp block contains the following elements (see datatype "TaxAmountType1Choice" on page 141for details)



Page

Code <Cd> {Or [1..1] 141



Presence: [1..1]

Definition: Amount of money, which has been typed.


5.85 TaxAmountType1ChoiceDefinition: Specifies the amount type.



Page

Code <Cd> {Or [1..1] 141


Used in element(s)

"Type" on page 140


Presence: [1..1]

Definition: Specifies the amount type, in a coded form.

Datatype: "ExternalTaxAmountType1Code" on page 174


Presence: [1..1]

Definition: Specifies the amount type, in a free-text form.


Usage Guideline


5.86 TaxAuthorisation1Definition: Details of the authorised tax paying party.



Page

Title <Titl> [0..1] 142

Name <Nm> [0..1] 142

Used in element(s)

"Authorisation" on page 151

5.86.1 TitleXML Tag: Titl

Presence: [0..1]

Definition: Title or position of debtor or the debtor's authorised representative.



Presence: [0..1]

Definition: Name of the debtor or the debtor's authorised representative.


5.87 TaxInformation3Definition: Details about tax paid, or to be paid, to the government in accordance with the law, includingpre-defined parameters such as thresholds and type of account.

Message Components

30 January 2017 143



Page



AdministrationZone <AdmstnZn> [0..1] 144


Method <Mtd> [0..1] 144



Date <Dt> [0..1] 145



Used in element(s)

"Tax" on page 53


Presence: [0..1]

Definition: Party on the credit side of the transaction to which the tax applies.

The Cdtr block contains the following elements (see datatype "TaxParty1" on page 149 for details)



Page

TaxIdentification <TaxId> [0..1] 149

RegistrationIdentification <RegnId> [0..1] 149

TaxType <TaxTp> [0..1] 150


Presence: [0..1]

Definition: Set of elements used to identify the party on the debit side of the transaction to which the taxapplies.

Usage Guideline


The Dbtr block contains the following elements (see datatype "TaxParty2" on page 150 for details)



Page





5.87.3 AdministrationZoneXML Tag: AdmstnZn

Presence: [0..1]

Definition: Territorial part of a country to which the tax payment is related.



Presence: [0..1]

Definition: Tax reference information that is specific to a taxing agency.



Presence: [0..1]

Definition: Method used to indicate the underlying business or how the tax is paid.


5.87.6 TotalTaxableBaseAmountXML Tag: TtlTaxblBaseAmt

Presence: [0..1]

Definition: Total amount of money on which the tax is based.


5.87.7 TotalTaxAmountXML Tag: TtlTaxAmt

Presence: [0..1]

Definition: Total amount of money as result of the calculation of the tax.


Message Components

30 January 2017 145


Presence: [0..1]

Definition: Date by which tax is due.


5.87.9 SequenceNumberXML Tag: SeqNb

Presence: [0..1]

Definition: Sequential number of the tax report.

Datatype: "Number" on page 181

5.87.10 RecordXML Tag: Rcrd

Presence: [0..*]

Definition: Record of tax details.

The Rcrd block contains the following elements (see datatype "TaxRecord1" on page 152 for details)



Page

Type <Tp> [0..1] 152

Category <Ctgy> [0..1] 153

CategoryDetails <CtgyDtls> [0..1] 153

DebtorStatus <DbtrSts> [0..1] 153

CertificateIdentification <CertId> [0..1] 153

FormsCode <FrmsCd> [0..1] 153

Period <Prd> [0..1] 153

TaxAmount <TaxAmt> [0..1] 154


5.88 TaxInformation4Definition: Details about tax paid, or to be paid, to the government in accordance with the law, includingpre-defined parameters such as thresholds and type of account.

Usage Guideline




Page




AdministrationZone <AdmstnZone> [0..1] 147


Method <Mtd> [0..1] 147



Date <Dt> [0..1] 148



Used in element(s)

"TaxRemittance" on page 137


Presence: [0..1]

Definition: Party on the credit side of the transaction to which the tax applies.

The Cdtr block contains the following elements (see datatype "TaxParty1" on page 149 for details)



Page





Presence: [0..1]

Definition: Identifies the party on the debit side of the transaction to which the tax applies.

Message Components

30 January 2017 147

The Dbtr block contains the following elements (see datatype "TaxParty2" on page 150 for details)



Page





5.88.3 UltimateDebtorXML Tag: UltmtDbtr

Presence: [0..1]

Definition: Ultimate party that owes an amount of money to the (ultimate) creditor, in this case, to thetaxing authority.

The UltmtDbtr block contains the following elements (see datatype "TaxParty2" on page 150 for de-tails)



Page





5.88.4 AdministrationZoneXML Tag: AdmstnZone

Presence: [0..1]

Definition: Territorial part of a country to which the tax payment is related.



Presence: [0..1]

Definition: Tax reference information that is specific to a taxing agency.



Usage Guideline


Presence: [0..1]

Definition: Method used to indicate the underlying business or how the tax is paid.


5.88.7 TotalTaxableBaseAmountXML Tag: TtlTaxblBaseAmt

Presence: [0..1]

Definition: Total amount of money on which the tax is based.


5.88.8 TotalTaxAmountXML Tag: TtlTaxAmt

Presence: [0..1]

Definition: Total amount of money as result of the calculation of the tax.



Presence: [0..1]

Definition: Date by which tax is due.


5.88.10 SequenceNumberXML Tag: SeqNb

Presence: [0..1]

Definition: Sequential number of the tax report.

Datatype: "Number" on page 181

5.88.11 RecordXML Tag: Rcrd

Presence: [0..*]

Definition: Record of tax details.

Message Components

30 January 2017 149

The Rcrd block contains the following elements (see datatype "TaxRecord1" on page 152 for details)



Page

Type <Tp> [0..1] 152






Period <Prd> [0..1] 153



5.89 TaxParty1Definition: Details about the entity involved in the tax paid or to be paid.



Page




Used in element(s)

"Creditor" on page 143, "Creditor" on page 146

5.89.1 TaxIdentificationXML Tag: TaxId

Presence: [0..1]

Definition: Tax identification number of the creditor.


5.89.2 RegistrationIdentificationXML Tag: RegnId

Presence: [0..1]

Definition: Unique identification, as assigned by an organisation, to unambiguously identify a party.

Usage Guideline



5.89.3 TaxTypeXML Tag: TaxTp

Presence: [0..1]

Definition: Type of tax payer.


5.90 TaxParty2Definition: Details about the entity involved in the tax paid or to be paid.



Page





Used in element(s)

"Debtor" on page 143, "Debtor" on page 146, "UltimateDebtor" on page 147

5.90.1 TaxIdentificationXML Tag: TaxId

Presence: [0..1]

Definition: Tax identification number of the debtor.


5.90.2 RegistrationIdentificationXML Tag: RegnId

Presence: [0..1]

Definition: Unique identification, as assigned by an organisation, to unambiguously identify a party.


5.90.3 TaxTypeXML Tag: TaxTp

Presence: [0..1]

Definition: Type of tax payer.


Message Components

30 January 2017 151

5.90.4 AuthorisationXML Tag: Authstn

Presence: [0..1]

Definition: Details of the authorised tax paying party.

The Authstn block contains the following elements (see datatype "TaxAuthorisation1" on page 142for details)



Page

Title <Titl> [0..1] 142

Name <Nm> [0..1] 142

5.91 TaxPeriod1Definition: Period of time details related to the tax payment.



Page

Year <Yr> [0..1] 151

Type <Tp> [0..1] 151

FromToDate <FrToDt> [0..1] 152

Used in element(s)

"Period" on page 155, "Period" on page 153

5.91.1 YearXML Tag: Yr

Presence: [0..1]

Definition: Year related to the tax payment.



Presence: [0..1]

Definition: Identification of the period related to the tax payment.

Datatype: "TaxRecordPeriod1Code" on page 188

Usage Guideline


5.91.3 FromToDateXML Tag: FrToDt

Presence: [0..1]

Definition: Range of time between a start date and an end date for which the tax report is provided.

The FrToDt block contains the following elements (see datatype "DatePeriodDetails" on page 43 fordetails)



Page

FromDate <FrDt> [1..1] 43

ToDate <ToDt> [1..1] 43

5.92 TaxRecord1Definition: Set of elements used to define the tax record.



Page

Type <Tp> [0..1] 152






Period <Prd> [0..1] 153



Used in element(s)

"Record" on page 145, "Record" on page 148


Presence: [0..1]

Definition: High level code to identify the type of tax details.


Message Components

30 January 2017 153

5.92.2 CategoryXML Tag: Ctgy

Presence: [0..1]

Definition: Specifies the tax code as published by the tax authority.


5.92.3 CategoryDetailsXML Tag: CtgyDtls

Presence: [0..1]

Definition: Provides further details of the category tax code.


5.92.4 DebtorStatusXML Tag: DbtrSts

Presence: [0..1]

Definition: Code provided by local authority to identify the status of the party that has drawn up the set-tlement document.


5.92.5 CertificateIdentificationXML Tag: CertId

Presence: [0..1]

Definition: Identification number of the tax report as assigned by the taxing authority.


5.92.6 FormsCodeXML Tag: FrmsCd

Presence: [0..1]

Definition: Identifies, in a coded form, on which template the tax report is to be provided.



Presence: [0..1]

Definition: Set of elements used to provide details on the period of time related to the tax payment.

Usage Guideline


The Prd block contains the following elements (see datatype "TaxPeriod1" on page 151 for details)



Page

Year <Yr> [0..1] 151

Type <Tp> [0..1] 151



Presence: [0..1]

Definition: Set of elements used to provide information on the amount of the tax record.

The TaxAmt block contains the following elements (see datatype "TaxAmount1" on page 139 for de-tails)



Page

Rate <Rate> [0..1] 139

TaxableBaseAmount <TaxblBaseAmt> [0..1] 139

TotalAmount <TtlAmt> [0..1] 140


5.92.9 AdditionalInformationXML Tag: AddtlInf

Presence: [0..1]

Definition: Further details of the tax record.


5.93 TaxRecordDetails1Definition: Provides information on the individual tax amount(s) per period of the tax record.



Page

Period <Prd> [0..1] 155

Amount <Amt> [1..1] 155

Message Components

30 January 2017 155

Used in element(s)

"Details" on page 140


Presence: [0..1]

Definition: Set of elements used to provide details on the period of time related to the tax payment.

The Prd block contains the following elements (see datatype "TaxPeriod1" on page 151 for details)



Page

Year <Yr> [0..1] 151

Type <Tp> [0..1] 151



Presence: [1..1]

Definition: Underlying tax amount related to the specified period.


Usage Guideline


6 Message Datatypes

Note The following chapter identifies the datatypes that are used in the CustomerDirectDebitIni-tiationV06 message.

6.1 ActiveOrHistoricCurrencyAndAmountDefinition: A number of monetary units specified in an active or a historic currency where the unit of cur-rency is explicit and compliant with ISO 4217.

Type: Amount

This data type must be used with the following XML Attributes:

Attribute Tag Datatype

Currency Ccy "ActiveOrHistoricCurrencyCode" on page 156

Format

minInclusive 0

totalDigits 18

fractionDigits 5

Rules

R8 CurrencyAmount ✓

The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

Error handling:


– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

Used in element(s)

"Amount" on page 56, "Amount" on page 155, "Amount" on page 55, "Amount" on page 141,"Amount" on page 134, "CreditNoteAmount" on page 125, "CreditNoteAmount" on page 127, "Due-PayableAmount" on page 125, "DuePayableAmount" on page 127, "RemittedAmount" on page 126,"RemittedAmount" on page 70, "RemittedAmount" on page 128, "TaxableBaseAmount" on page 139,"TotalAmount" on page 140, "TotalTaxAmount" on page 144, "TotalTaxAmount" on page 148, "Total-TaxableBaseAmount" on page 144, "TotalTaxableBaseAmount" on page 148

6.2 ActiveOrHistoricCurrencyCodeDefinition: A code allocated to a currency by a Maintenance Agency under an international identificationscheme, as described in the latest edition of the international standard ISO 4217 "Codes for the repre-sentation of currencies and funds".

Message Datatypes

30 January 2017 157

Type: Code

Format

pattern [A-Z]{3,3}

Rules

R6 ActiveOrHistoricCurrency ✓

The Currency Code must be registered, or have already been registered. Valid active or historiccurrency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) con-tiguous letters, and may be or not be withdrawn on the day the message containing the Curren-cy is exchanged.

Error handling:



– Error Text: Invalid currency code.

Used in element(s)

"Currency" on page 25, "Currency" on page 27

Used in attribute(s)

"ActiveOrHistoricCurrencyAndAmount" on page 156, "CPA_Amount" on page 161

6.3 AddressType2CodeDefinition: Specifies the type of address.

Type: Code

Code Name Definition

ADDR Postal Address is the complete postal address.

BIZZ Business Address is the business address.

DLVY DeliveryTo Address is the address to which deliveryis to take place.

HOME Residential Address is the home address.

MLTO MailTo Address is the address to which mail issent.

PBOX POBox Address is a postal office (PO) box.

Used in element(s)

"AddressType" on page 117

Restricts

"AddressTypeCode" on page 158

Usage Guideline


6.4 AddressTypeCodeDefinition: Specifies the type of address.

Type: Code


ADDR Postal Address is the complete postal address.

BIZZ Business Address is the business address.

DLVY DeliveryTo Address is the address to which deliveryis to take place.

HOME Residential Address is the home address.

MLTO MailTo Address is the address to which mail issent.

PBOX POBox Address is a postal office (PO) box.

Is restricted by

"AddressType2Code" on page 157

6.5 AmountDirectionCodeDefinition: Specifies if an operation is an increase or a decrease or the result of a reversal operation.

Type: Code


CRDT Credit Operation is an increase.

DBIT Debit Operation is a decrease.

RVCD ReversalCredit Debit entry used to reverse a previouslybooked credit entry.

RVDB ReversalDebit Credit entry used to reverse a previouslybooked debit entry.

Is restricted by

"CreditDebitCode" on page 165

6.6 AnyBICIdentifierDefinition: Code allocated to a financial or non-financial institution by the ISO 9362 Registration Author-ity, as described in ISO 9362 "Banking - Banking telecommunication messages - Business identifiercode (BIC)".

Type: IdentifierSet

Format

pattern [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}

Message Datatypes

30 January 2017 159

Rules

R5 AnyBIC ✓

Only a valid Business identifier code is allowed. Business identifier codes for financial or non-financial institutions are registered by the ISO 9362 Registration Authority in the BIC directory,and consists of eight (8) or eleven (11) contiguous characters.

Error handling:



– Error Text: Invalid BIC.

Used in element(s)

"AnyBIC" on page 87, "AnyBIC" on page 88

6.7 Authorisation1CodeDefinition: Specifies the level of approval depending on a number of factors, including payment type,threshold amount or local country or operations practice.

Type: Code


AUTH PreAuthorisedFile Indicates a file has been pre authorisedor approved within the originating cus-tomer environment and no further ap-proval is required.

FDET FileLevelAuthorisationDetails Indicates that a file requires additionalfile level approval, with the ability to viewboth the payment information block andsupporting customer credit transactiondetail.

FSUM FileLevelAuthorisationSummary Indicates that a file requires additionalfile level approval, with the ability to viewonly the payment information block levelinformation.

ILEV InstructionLevelAuthorisation Indicates that a file requires all customertransactions to be authorised or ap-proved.

Used in element(s)

"Code" on page 19

Restricts

"AuthorisationCode" on page 159

6.8 AuthorisationCodeDefinition: Specifies the level of approval depending on a number of factors, including payment type,threshold amount or local country or operations practice.

Usage Guideline


Type: Code


AUTH PreAuthorisedFile Indicates a file has been pre authorisedor approved within the originating cus-tomer environment and no further ap-proval is required.

FDET FileLevelAuthorisationDetails Indicates that a file requires additionalfile level approval, with the ability to viewboth the payment information block andsupporting customer credit transactiondetail.

FSUM FileLevelAuthorisationSummary Indicates that a file requires additionalfile level approval, with the ability to viewonly the payment information block levelinformation.

ILEV InstructionLevelAuthorisation Indicates that a file requires all customertransactions to be authorised or ap-proved.

Is restricted by

"Authorisation1Code" on page 159

6.9 BICFIIdentifierDefinition: Code allocated to a financial institution by the ISO 9362 Registration Authority as describedin ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".

Type: IdentifierSet

Format

pattern [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}

Rules

R3 BICFI ✓

Valid BICs for financial institutions are registered by the ISO 9362 Registration Authority in theBIC directory, and consist of eight (8) or eleven (11) contiguous characters.

Error handling:



– Error Text: Invalid FI BIC.

Used in element(s)

"BICFI" on page 62, "BICFI" on page 64

Message Datatypes

30 January 2017 161

6.10 BatchBookingIndicatorDefinition: Identifies whether the sending party requests a single debit or credit entry per individualtransaction or a batch entry for the sum of the amounts of all transactions.

Type: Indicator

Meaning When True: Identifies that a batch entry for the sum of the amounts of all transactions in thebatch or message is requested.

Meaning When False: Identifies that a single entry for each of the transactions in the batch or messageis requested.

Used in element(s)

"BatchBooking" on page 104

6.11 CPA_AmountDefinition:

This datatype has been created by the Publisher of this Usage Guideline.

Type: Amount

This data type must be used with the following XML Attributes:

Attribute Tag Datatype

CPA_CurrencyCode Ccy "ActiveOrHistoricCurrencyCode" on page 156

Format

maxInclusive 999999999.99

totalDigits 11

fractionDigits 2

Used in element(s)

"InstructedAmount" on page 47

6.12 CPA_Exact9NumericTextDefinition:


Type: Text

Format

length 9

Usage Guideline


Used in element(s)

"MemberIdentification" on page 32

6.13 CPA_Max15TextDefinition:


Type: Text

Format

length 15

Used in element(s)

"Other" on page 36

6.14 CPA_Max19TextDefinition: Specifies a character string with a maximum length of 19 characters.


Type: Text

Format

length 19

Used in element(s)

"EndToEndIdentification" on page 100

6.15 ChargeBearerType1CodeDefinition: Specifies which party(ies) will pay charges due for processing of the instruction.

Type: Code


CRED BorneByCreditor All transaction charges are to be borneby the creditor.

DEBT BorneByDebtor All transaction charges are to be borneby the debtor.

Message Datatypes

30 January 2017 163


Usage Guideline restrictions for thiscode

• This code(pain.008.001.06/Pay-mentInformation/ChargeBear-er/BorneByDebtor) is removed.

SHAR Shared In a credit transfer context, means thattransaction charges on the sender sideare to be borne by the debtor, transac-tion charges on the receiver side are tobe borne by the creditor. In a direct debitcontext, means that transaction chargeson the sender side are to be borne bythe creditor, transaction charges on thereceiver side are to be borne by thedebtor.


• This code(pain.008.001.06/Paymen-tInformation/ChargeBearer/Shared)is removed.

SLEV FollowingServiceLevel Charges are to be applied following therules agreed in the service level and/orscheme.


• This code(pain.008.001.06/Paymen-tInformation/ChargeBearer/Follow-ingServiceLevel) is removed.

Used in element(s)

"ChargeBearer" on page 108, "ChargeBearer" on page 48

Restricts

"ChargeBearerTypeCode" on page 163

6.16 ChargeBearerTypeCodeDefinition: Specifies which party(ies) will pay charges due for processing of the instruction.

Type: Code

Usage Guideline



CRED BorneByCreditor All transaction charges are to be borneby the creditor.

DEBT BorneByDebtor All transaction charges are to be borneby the debtor.

SHAR Shared In a credit transfer context, means thattransaction charges on the sender sideare to be borne by the debtor, transac-tion charges on the receiver side are tobe borne by the creditor. In a direct debitcontext, means that transaction chargeson the sender side are to be borne bythe creditor, transaction charges on thereceiver side are to be borne by thedebtor.

SLEV FollowingServiceLevel Charges are to be applied following therules agreed in the service level and/orscheme.

Is restricted by

"ChargeBearerType1Code" on page 162

6.17 CountryCodeDefinition: Code to identify a country, a dependency, or another area of particular geopolitical interest,on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).

Type: Code

Format

pattern [A-Z]{2,2}

Rules

R2 Country ✓

The code is checked against the list of country names obtained from the United Nations (ISO3166, Alpha-2 code).

Error handling:



– Error Text: Invalid Country Code.

Used in element(s)

"Country" on page 118, "Country" on page 123, "Country" on page 133, "CountryOfBirth" on page 42,"CountryOfResidence" on page 93, "CountryOfResidence" on page 95, "CountryOfResidence" onpage 98

Message Datatypes

30 January 2017 165

6.18 CreditDebitCodeDefinition: Specifies if an operation is an increase or a decrease.

Type: Code


CRDT Credit Operation is an increase.

DBIT Debit Operation is a decrease.

Used in element(s)

"CreditDebitIndicator" on page 57

Restricts

"AmountDirectionCode" on page 158

6.19 DecimalNumberDefinition: Number of objects represented as a decimal number, eg, 0.75 or 45.6.

Type: Quantity

Format

totalDigits 18

fractionDigits 17

Used in element(s)

"ControlSum" on page 80, "ControlSum" on page 104, "CountPerPeriod" on page 68

6.20 DocumentType3CodeDefinition: Specifies a type of financial or commercial document.

Type: Code


DISP DispatchAdvice Document is a dispatch advice.

FXDR ForeignExchangeDealReference Document is a pre-agreed or pre-arranged foreign exchange transactionto which the payment transaction refers.

PUOR PurchaseOrder Document is a purchase order.

RADM RemittanceAdviceMessage Document is a remittance advice sentseparately from the current transaction.

RPIN RelatedPaymentInstruction Document is a linked payment instruc-tion to which the current payment in-struction is related, eg, in a cover sce-nario.

Usage Guideline



SCOR StructuredCommunicationReference Document is a structured communica-tion reference provided by the creditor toidentify the referred transaction.

Used in element(s)

"Code" on page 40

Restricts

"DocumentTypeCode" on page 167

6.21 DocumentType6CodeDefinition: Specifies a type of financial or commercial document.

Type: Code


AROI AccountReceivableOpenItem Document is a payment that applies to aspecific source document.

BOLD BillOfLading Document is a shipping notice.

CINV CommercialInvoice Document is an invoice.

CMCN CommercialContract Document is an agreement between theparties, stipulating the terms and condi-tions of the delivery of goods or services.

CNFA CreditNoteRelatedToFinancialAdjustment Document is a credit note for the finalamount settled for a commercial transac-tion.

CREN CreditNote Document is a credit note.

DEBN DebitNote Document is a debit note.


DNFA DebitNoteRelatedToFinancialAdjustment Document is a debit note for the finalamount settled for a commercial transac-tion.

HIRI HireInvoice Document is an invoice for the hiring ofhuman resources or renting goods orequipment.

MSIN MeteredServiceInvoice Document is an invoice claiming pay-ment for the supply of metered services,for example gas or electricity supplied toa fixed meter.


SBIN SelfBilledInvoice Document is an invoice issued by thedebtor.

SOAC StatementOfAccount Document is a statement of the transac-tions posted to the debtor's account atthe supplier.

Message Datatypes

30 January 2017 167


TSUT TradeServicesUtilityTransaction Document is a transaction identifier asassigned by the Trade Services Utility.

VCHR Voucher Document is an electronic payment doc-ument.

Used in element(s)

"Code" on page 121

Restricts

"DocumentTypeCode" on page 167

6.22 DocumentTypeCodeDefinition: Specifies a type of financial or commercial document.

Type: Code


AROI AccountReceivableOpenItem Document is a payment that applies to aspecific source document.

BOLD BillOfLading Document is a shipping notice.

CINV CommercialInvoice Document is an invoice.

CMCN CommercialContract Document is an agreement between theparties, stipulating the terms and condi-tions of the delivery of goods or services.

CNFA CreditNoteRelatedToFinancialAdjustment Document is a credit note for the finalamount settled for a commercial transac-tion.

CREN CreditNote Document is a credit note.

DEBN DebitNote Document is a debit note.


DNFA DebitNoteRelatedToFinancialAdjustment Document is a debit note for the finalamount settled for a commercial transac-tion.

FXDR ForeignExchangeDealReference Document is a pre-agreed or pre-arranged foreign exchange transactionto which the payment transaction refers.

HIRI HireInvoice Document is an invoice for the hiring ofhuman resources or renting goods orequipment.

MSIN MeteredServiceInvoice Document is an invoice claiming pay-ment for the supply of metered services,for example gas or electricity supplied toa fixed meter.


RADM RemittanceAdviceMessage Document is a remittance advice sentseparately from the current transaction.

Usage Guideline



RPIN RelatedPaymentInstruction Document is a linked payment instruc-tion to which the current payment in-struction is related, eg, in a cover sce-nario.

SBIN SelfBilledInvoice Document is an invoice issued by thedebtor.

SCOR StructuredCommunicationReference Document is a structured communica-tion reference provided by the creditor toidentify the referred transaction.

SOAC StatementOfAccount Document is a statement of the transac-tions posted to the debtor's account atthe supplier.

TSUT TradeServicesUtilityTransaction Document is a transaction identifier asassigned by the Trade Services Utility.

VCHR Voucher Document is an electronic payment doc-ument.

Is restricted by

"DocumentType3Code" on page 165, "DocumentType6Code" on page 166

6.23 Exact3NumericTextDefinition: Specifies a numeric string with an exact length of 3 digits.

Type: Text

Format

pattern [0-9]{3}

Used in element(s)

"Proprietary" on page 30

6.24 ExternalAccountIdentification1CodeDefinition: Specifies the external account identification scheme name code in the format of characterstring with a maximum length of 4 characters.

The list of valid codes is an external code list published separately.

External code sets can be downloaded from www.iso20022.org.

Type: Code

Format

minLength 1

maxLength 4

Message Datatypes

30 January 2017 169

Used in element(s)

"Code" on page 14

6.25 ExternalCashAccountType1CodeDefinition: Specifies the nature, or use, of the cash account in the format of character string with a maxi-mum length of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 28

6.26 ExternalCategoryPurpose1CodeDefinition: Specifies the category purpose, as published in an external category purpose code list.


Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 28, "Code" on page 29

6.27 ExternalClearingSystemIdentification1CodeDefinition: Specifies the clearing system identification code, as published in an external clearing systemidentification code list.


Type: Code

Format

minLength 1

maxLength 5

Usage Guideline


Used in element(s)

"Code" on page 30

6.28 ExternalDiscountAmountType1CodeDefinition: Specifies the nature, or use, of the amount in the format of character string with a maximumlength of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 56

6.29 ExternalDocumentLineType1CodeDefinition: Specifies the document line type as published in an external document type code list.

Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 61

6.30 ExternalFinancialInstitutionIdentification1CodeDefinition: Specifies the external financial institution identification scheme name code in the format ofcharacter string with a maximum length of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Message Datatypes

30 January 2017 171

Used in element(s)

"Code" on page 61

6.31 ExternalGarnishmentType1CodeDefinition: Specifies the garnishment type as published in an external document type code list.

Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 71

6.32 ExternalLocalInstrument1CodeDefinition: Specifies the external local instrument code in the format of character string with a maximumlength of 35 characters.



Type: Code

Format

minLength 1

maxLength 35

Used in element(s)

"Code" on page 82

6.33 ExternalMandateSetupReason1CodeDefinition: Specifies the external mandate setup reason code in the format of character string with amaximum length of 4 characters.


Type: Code

Format

minLength 1

maxLength 4

Usage Guideline


Used in element(s)

"Code" on page 85

Restricts

"ExternalMandateSetupReasonCode" on page 172

6.34 ExternalMandateSetupReasonCodeDefinition: Specifies the external mandate setup reason code in the format of character string with amaximum length of 4 characters.


Type: Code

Format

minLength 1

maxLength 4

Is restricted by

"ExternalMandateSetupReason1Code" on page 171

6.35 ExternalOrganisationIdentification1CodeDefinition: Specifies the external organisation identification scheme name code in the format of charac-ter string with a maximum length of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 89

6.36 ExternalPersonIdentification1CodeDefinition: Specifies the external person identification scheme name code in the format of characterstring with a maximum length of 4 characters.



Message Datatypes

30 January 2017 173

Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 116

6.37 ExternalPurpose1CodeDefinition: Specifies the external purpose code in the format of character string with a maximum lengthof 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 119

6.38 ExternalServiceLevel1CodeDefinition: Specifies the external service level code in the format of character string with a maximumlength of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 132

Usage Guideline


6.39 ExternalTaxAmountType1CodeDefinition: Specifies the nature, or use, of the amount in the format of character string with a maximumlength of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 141

6.40 Frequency6CodeDefinition: Specifies the regularity of an event.

Type: Code


ADHO Adhoc Event takes place on request or as nec-essary.

DAIL Daily Event takes place every day.

FRTN Fortnightly Event takes place every two weeks.

INDA IntraDay Event takes place several times a day.

MIAN SemiAnnual Event takes place every six months ortwo times a year.

MNTH Monthly Event takes place every month or once amonth.

QURT Quarterly Event takes place every three months orfour times a year.

WEEK Weekly Event takes place once a week.

YEAR Annual Event takes place every year or once ayear.

Used in element(s)

"Type" on page 67, "Type" on page 67

Restricts

"FrequencyCode" on page 175

Message Datatypes

30 January 2017 175

6.41 FrequencyCodeDefinition: Specifies the regularity of an event.

Type: Code


ADHO Adhoc Event takes place on request or as nec-essary.

DAIL Daily Event takes place every day.

FRTN Fortnightly Event takes place every two weeks.

INDA IntraDay Event takes place several times a day.

MIAN SemiAnnual Event takes place every six months ortwo times a year.

MNTH Monthly Event takes place every month or once amonth.

MOVE TriggeredByMovement Event takes place at the end of the dayif there was a movement on the account,otherwise nothing is sent that day.

NEVR Never Event does never take place.

OVNG Overnight Event takes place overnight.

QURT Quarterly Event takes place every three months orfour times a year.

RATE Rate Event takes place based on a change ofa rate.

TEND TenDays Event takes place every ten businessdays.

WEEK Weekly Event takes place once a week.

YEAR Annual Event takes place every year or once ayear.

Is restricted by

"Frequency6Code" on page 174

6.42 IBAN2007IdentifierDefinition: An identifier used internationally by financial institutions to uniquely identify the account ofa customer at a financial institution, as described in the latest edition of the international standard ISO13616:2007 - "Banking and related financial services - International Bank Account Number (IBAN)".

Type: IdentifierSet

Format

pattern [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}

Usage Guideline


Rules

R4 IBAN ✓

A valid IBAN consists of all three of the following components: Country Code, check digits andBBAN.

Error handling:



– Error Text: Invalid IBAN format or invalid check digits.

Used in element(s)

"IBAN" on page 12, "IBAN" on page 13

6.43 ISODateDefinition: A particular point in the progression of time in a calendar year expressed in the YYYY-MM-DD format. This representation is defined in "XML Schema Part 2: Datatypes Second Edition - W3CRecommendation 28 October 2004" which is aligned with ISO 8601.

Type: Date

Used in element(s)

"BirthDate" on page 42, "Date" on page 145, "Date" on page 133, "Date" on page 69, "Date" onpage 148, "DateOfSignature" on page 83, "FinalCollectionDate" on page 84, "FirstCollectionDate" onpage 84, "FromDate" on page 43, "OriginalFinalCollectionDate" on page 18, "PreNotificationDate"on page 45, "RelatedDate" on page 58, "RelatedDate" on page 120, "RequestedCollectionDate" onpage 105, "ToDate" on page 43, "Year" on page 151

6.44 ISODateTimeDefinition: A particular point in the progression of time defined by a mandatory date and a mandato-ry time component, expressed in either UTC time format (YYYY-MM-DDThh:mm:ss.sssZ), local timewith UTC offset format (YYYY-MM-DDThh:mm:ss.sss+/-hh:mm), or local time format (YYYY-MM-DDThh:mm:ss.sss). These representations are defined in "XML Schema Part 2: Datatypes Second Edi-tion - W3C Recommendation 28 October 2004" which is aligned with ISO 8601.

Note on the time format:

1) beginning / end of calendar day

00:00:00 = the beginning of a calendar day

24:00:00 = the end of a calendar day

2) fractions of second in time format

Decimal fractions of seconds may be included. In this case, the involved parties shall agree on the max-imum number of digits that are allowed.

Type: DateTime

Message Datatypes

30 January 2017 177

Used in element(s)

"CreationDateTime" on page 79

6.45 Max1025TextDefinition: Specifies a character string with a maximum length of 1025 characters.

Type: Text

Format

minLength 1

maxLength 1025

Used in element(s)

"ElectronicSignature" on page 84


Type: Text

Format

minLength 1

maxLength 10

Used in element(s)

"Code" on page 134, "Identification" on page 76


Type: Text

Format

minLength 1

maxLength 128

Used in element(s)

"Proprietary" on page 20


Type: Text

Usage Guideline


Format

minLength 1

maxLength 12

Used in element(s)



Type: Text

Format

minLength 1

maxLength 140

Used in element(s)

"AdditionalInformation" on page 57, "AdditionalInformation" on page 154, "AdditionalRemittanceIn-formation" on page 138, "InstructionForCreditorAgent" on page 51, "Name" on page 62, "Name" onpage 23, "Name" on page 33, "Name" on page 92, "Name" on page 86, "Name" on page 142, "Name"on page 123, "Name" on page 65, "Name" on page 94, "Name" on page 97, "ReferenceNumber"on page 144, "ReferenceNumber" on page 69, "ReferenceNumber" on page 147, "Unstructured" onpage 129

6.50 Max15NumericTextDefinition: Specifies a numeric string with a maximum length of 15 digits.

Type: Text

Format

pattern [0-9]{1,15}

Used in element(s)

"NumberOfTransactions" on page 80, "NumberOfTransactions" on page 104


Type: Text

Format

minLength 1

maxLength 16

Message Datatypes

30 January 2017 179

Used in element(s)

"BuildingNumber" on page 118, "PostCode" on page 118


Type: Text

Format

minLength 1

maxLength 2048

Used in element(s)

"Description" on page 59, "ElectronicAddress" on page 131, "EmailAddress" on page 34, "EmailAd-dress" on page 36, "EmailAddress" on page 39


Type: Text

Format

maxLength 30

Used in element(s)

"Name" on page 35, "Name" on page 37


Type: Text

Format

minLength 1

maxLength 34

Used in element(s)



Type: Text

Usage Guideline


Format

minLength 1

maxLength 350

Used in element(s)

"PlaceAndName" on page 139


Type: Text

Format

minLength 1

maxLength 35

Used in element(s)

"AdministrationZone" on page 144, "AdministrationZone" on page 147, "Category" on page 153, "Cat-egoryDetails" on page 153, "CertificateIdentification" on page 153, "CityOfBirth" on page 42, "Coun-trySubDivision" on page 118, "DebtorStatus" on page 153, "FormsCode" on page 153, "Identifica-tion" on page 74, "Identification" on page 23, "Identification" on page 75, "Identification" on page 78,"Information" on page 134, "InstructionIdentification" on page 99, "Issuer" on page 75, "Issuer" onpage 72, "Issuer" on page 76, "Issuer" on page 78, "Issuer" on page 41, "Issuer" on page 60, "Issuer"on page 71, "Issuer" on page 122, "Issuer" on page 77, "Issuer" on page 74, "MandateIdentification"on page 83, "MemberIdentification" on page 31, "MessageIdentification" on page 79, "Method" onpage 144, "Method" on page 147, "Number" on page 58, "Number" on page 120, "OriginalMandateI-dentification" on page 15, "Other" on page 34, "Other" on page 39, "PaymentInformationIdentifica-tion" on page 103, "PreNotificationIdentification" on page 45, "Proprietary" on page 30, "Proprietary" onpage 61, "Proprietary" on page 14, "Proprietary" on page 28, "Proprietary" on page 89, "Proprietary"on page 116, "Proprietary" on page 119, "Proprietary" on page 41, "Proprietary" on page 56, "Propri-etary" on page 141, "Proprietary" on page 132, "Proprietary" on page 82, "Proprietary" on page 29,"Proprietary" on page 61, "Proprietary" on page 71, "Proprietary" on page 121, "ProvinceOfBirth" onpage 42, "Reference" on page 40, "RegistrationIdentification" on page 149, "RegistrationIdentification"on page 150, "RemittanceIdentification" on page 130, "TaxIdentification" on page 149, "TaxIdentifica-tion" on page 150, "TaxType" on page 150, "TaxType" on page 150, "Title" on page 142, "TownName"on page 118, "Type" on page 152, "Type" on page 133


Type: Text

Format

minLength 1

maxLength 4

Message Datatypes

30 January 2017 181

Used in element(s)

"Reason" on page 57

6.58 Max70TextDefinition: Specifies a character string with a maximum length of 70characters.

Type: Text

Format

minLength 1

maxLength 70

Used in element(s)

"AddressLine" on page 119, "Department" on page 117, "Name" on page 25, "Name" on page 27, "Pro-prietary" on page 86, "StreetName" on page 118, "SubDepartment" on page 117

6.59 NamePrefix1CodeDefinition: Specifies the terms used to formally address a person.

Type: Code


DOCT Doctor Title of the person is Doctor or Dr.

MADM Madam Title of the person is Madam.

MISS Miss Title of the person is Miss.

MIST Mister Title of the person is Mister or Mr.

Used in element(s)

"NamePrefix" on page 33, "NamePrefix" on page 34, "NamePrefix" on page 37

6.60 NumberDefinition: Number of objects represented as an integer.

Type: Quantity

Format

totalDigits 18

fractionDigits 0

Used in element(s)

"SequenceNumber" on page 145, "SequenceNumber" on page 148

Usage Guideline


6.61 PaymentMethod2CodeDefinition: Specifies the transfer method that will be used to transfer the cash.

Type: Code


DD DirectDebit Collection of an amount of money fromthe debtor's bank account by the credi-tor. The amount of money and dates ofcollections may vary.

Used in element(s)

"PaymentMethod" on page 104

Restricts

"PaymentMethodCode" on page 182

6.62 PaymentMethodCodeDefinition: Specifies the transfer method that will be used to transfer the cash.

Type: Code


CHK Cheque Written order to a bank to pay a certainamount of money from one person to an-other person.

CLAS Classical Classical method.

DD DirectDebit Collection of an amount of money fromthe debtor's bank account by the credi-tor. The amount of money and dates ofcollections may vary.

DIRE Direct Direct method.

TRA TransferAdvice Transfer of an amount of money in thebooks of the account servicer. An adviceshould be sent back to the account own-er.

TRF CreditTransfer Transfer of an amount of money in thebooks of the account servicer.

Is restricted by

"PaymentMethod2Code" on page 182

6.63 PercentageRateDefinition: Rate expressed as a percentage, ie, in hundredths, eg, 0.7 is 7/10 of a percent, and 7.0 is7%.

Type: Rate

Message Datatypes

30 January 2017 183

Format

totalDigits 11

fractionDigits 10

Used in element(s)

"Rate" on page 139

6.64 PhoneNumberDefinition: The collection of information which identifies a specific phone or FAX number as defined bytelecom services.

It consists of a "+" followed by the country code (from 1 to 3 characters) then a "-" and finally, any com-bination of numbers, "(", ")", "+" and "-" (up to 30 characters).

Type: Text

Format

pattern \+[0-9]{1,3}-[0-9()+\-]{1,30}

Used in element(s)

"FaxNumber" on page 34, "FaxNumber" on page 36, "FaxNumber" on page 38, "MobileNumber" onpage 33, "MobileNumber" on page 35, "MobileNumber" on page 38, "PhoneNumber" on page 33, "Pho-neNumber" on page 35, "PhoneNumber" on page 38

6.65 Priority2CodeDefinition: Specifies the priority level of an event.

Type: Code


HIGH High Priority level is high.

NORM Normal Priority level is normal.

Used in element(s)

"InstructionPriority" on page 111, "InstructionPriority" on page 113

Restricts

"PriorityCode" on page 183

6.66 PriorityCodeDefinition: Specifies the priority level of an event.

Type: Code

Usage Guideline



HIGH High Priority level is high.

LOWW Low Priority level is low.

NORM Normal Priority level is normal.

URGT Urgent Priority level is urgent (highest prioritypossible)

Is restricted by

"Priority2Code" on page 183

6.67 RegulatoryReportingType1CodeDefinition: Identifies whether the regulatory reporting information applies to the debit side, to the creditside or to both debit and credit sides of the transaction.

Type: Code


BOTH Both Regulatory information applies to bothcredit and debit sides.

CRED Credit Regulatory information applies to thecredit side.

DEBT Debit Regulatory information applies to thedebit side.

Used in element(s)

"DebitCreditReportingIndicator" on page 123

Restricts

"RegulatoryReportingTypeCode" on page 184

6.68 RegulatoryReportingTypeCodeDefinition: Identifies whether the regulatory reporting information applies to the debit side, to the creditside or to both debit and credit sides of the transaction.

Type: Code


BOTH Both Regulatory information applies to bothcredit and debit sides.

CRED Credit Regulatory information applies to thecredit side.

DEBT Debit Regulatory information applies to thedebit side.

Is restricted by

"RegulatoryReportingType1Code" on page 184

Message Datatypes

30 January 2017 185

6.69 RemittanceLocationMethod2CodeDefinition: Specifies the method used to deliver the remittance advice information.

Type: Code


EDIC ElectronicDataInterchange Remittance advice information must besent through Electronic Data Interchange(EDI).

EMAL EMail Remittance advice information must besent through e-mail.

FAXI Fax Remittance advice information must befaxed.

POST Post Remittance advice information must besent through postal services.


• This code(pain.008.001.06/Pay-mentInformation/DirectDebitTrans-actionInformation/RelatedRemit-tanceInformation/RemittanceLo-cationDetails/Method/Post) is re-moved.

SMSM SMS Remittance advice information must besent through by phone as a short mes-sage service (SMS).


• This code(pain.008.001.06/Pay-mentInformation/DirectDebitTrans-actionInformation/RelatedRemit-tanceInformation/RemittanceLo-cationDetails/Method/SMS) is re-moved.

URID UniformResourceIdentifier Remittance advice information needsto be sent to a Uniform Resource Iden-tifier (URI). URI is a compact string ofcharacters that uniquely identify an ab-stract or physical resource. URI's are thesuper-set of identifiers, such as URLs,email addresses, ftp sites, etc, and assuch, provide the syntax for all of theidentification schemes.

Used in element(s)

"Method" on page 131

Usage Guideline


Restricts

"RemittanceLocationMethodCode" on page 186

6.70 RemittanceLocationMethodCodeDefinition: Specifies the method used to deliver the remittance advice information.

Type: Code


EDIC ElectronicDataInterchange Remittance advice information must besent through Electronic Data Interchange(EDI).

EMAL EMail Remittance advice information must besent through e-mail.

FAXI Fax Remittance advice information must befaxed.

POST Post Remittance advice information must besent through postal services.

SMSM SMS Remittance advice information must besent through by phone as a short mes-sage service (SMS).

URID UniformResourceIdentifier Remittance advice information needsto be sent to a Uniform Resource Iden-tifier (URI). URI is a compact string ofcharacters that uniquely identify an ab-stract or physical resource. URI's are thesuper-set of identifiers, such as URLs,email addresses, ftp sites, etc, and assuch, provide the syntax for all of theidentification schemes.

Is restricted by

"RemittanceLocationMethod2Code" on page 185

6.71 SequenceType3CodeDefinition: Specifies the type of the current transaction that belongs to a sequence of transactions.

Type: Code


FNAL Final Final collection of a series of direct debitinstructions.


• This code(pain.008.001.06/Paymen-tInformation/DirectDebitTransac-tionInformation/PaymentTypeInfor-

Message Datatypes

30 January 2017 187


mation/SequenceType/Final) is re-moved.

FRST First First collection of a series of direct debitinstructions.


• This code(pain.008.001.06/Paymen-tInformation/DirectDebitTransac-tionInformation/PaymentTypeInfor-mation/SequenceType/First) is re-moved.

OOFF OneOff Direct debit instruction where thedebtor's authorisation is used to initiateone single direct debit transaction.


• This code(pain.008.001.06/Paymen-tInformation/DirectDebitTransac-tionInformation/PaymentTypeInfor-mation/SequenceType/OneOff) isremoved.

RCUR Recurring Direct debit instruction where thedebtor's authorisation is used for regulardirect debit transactions initiated by thecreditor.


• This code(pain.008.001.06/Paymen-tInformation/DirectDebitTransac-tionInformation/PaymentTypeInfor-mation/SequenceType/Recurring)is removed.

RPRE Represented Collection used to re-present previouslyreversed or returned direct debit transac-tions.

Used in element(s)

"SequenceType" on page 111, "SequenceType" on page 114

Restricts

"SequenceTypeCode" on page 188

Usage Guideline


6.72 SequenceTypeCodeDefinition: Specifies the type of the current transaction that belongs to a sequence of transactions.

Type: Code


FNAL Final Final collection of a series of direct debitinstructions.

FRST First First collection of a series of direct debitinstructions.

OOFF OneOff Direct debit instruction where thedebtor's authorisation is used to initiateone single direct debit transaction.

RCUR Recurring Direct debit instruction where thedebtor's authorisation is used for regulardirect debit transactions initiated by thecreditor.

RPRE Represented Collection used to re-present previouslyreversed or returned direct debit transac-tions.

Is restricted by

"SequenceType3Code" on page 186

6.73 TaxRecordPeriod1CodeDefinition: Specifies the period related to the tax payment.

Type: Code


HLF1 FirstHalf Tax is related to the first half of the peri-od.

HLF2 SecondHalf Tax is related to the second half of theperiod.

MM01 FirstMonth Tax is related to the second month of theperiod.

MM02 SecondMonth Tax is related to the first month of theperiod.

MM03 ThirdMonth Tax is related to the third month of theperiod.

MM04 FourthMonth Tax is related to the fourth month of theperiod.

MM05 FifthMonth Tax is related to the fifth month of theperiod.

MM06 SixthMonth Tax is related to the sixth month of theperiod.

MM07 SeventhMonth Tax is related to the seventh month ofthe period.

Message Datatypes

30 January 2017 189


MM08 EighthMonth Tax is related to the eighth month of theperiod.

MM09 NinthMonth Tax is related to the ninth month of theperiod.

MM10 TenthMonth Tax is related to the tenth month of theperiod.

MM11 EleventhMonth Tax is related to the eleventh month ofthe period.

MM12 TwelfthMonth Tax is related to the twelfth month of theperiod.

QTR1 FirstQuarter Tax is related to the first quarter of theperiod.

QTR2 SecondQuarter Tax is related to the second quarter ofthe period.

QTR3 ThirdQuarter Tax is related to the third quarter of theperiod.

QTR4 FourthQuarter Tax is related to the forth quarter of theperiod.

Used in element(s)

"Type" on page 151

Restricts

"TaxRecordPeriodCode" on page 189

6.74 TaxRecordPeriodCodeDefinition: Specifies the period related to the tax payment.

Type: Code


HLF1 FirstHalf Tax is related to the first half of the peri-od.

HLF2 SecondHalf Tax is related to the second half of theperiod.

MM01 FirstMonth Tax is related to the second month of theperiod.

MM02 SecondMonth Tax is related to the first month of theperiod.

MM03 ThirdMonth Tax is related to the third month of theperiod.

MM04 FourthMonth Tax is related to the fourth month of theperiod.

MM05 FifthMonth Tax is related to the fifth month of theperiod.

Usage Guideline



MM06 SixthMonth Tax is related to the sixth month of theperiod.

MM07 SeventhMonth Tax is related to the seventh month ofthe period.

MM08 EighthMonth Tax is related to the eighth month of theperiod.

MM09 NinthMonth Tax is related to the ninth month of theperiod.

MM10 TenthMonth Tax is related to the tenth month of theperiod.

MM11 EleventhMonth Tax is related to the eleventh month ofthe period.

MM12 TwelfthMonth Tax is related to the twelfth month of theperiod.

QTR1 FirstQuarter Tax is related to the first quarter of theperiod.

QTR2 SecondQuarter Tax is related to the second quarter ofthe period.

QTR3 ThirdQuarter Tax is related to the third quarter of theperiod.

QTR4 FourthQuarter Tax is related to the forth quarter of theperiod.

Is restricted by

"TaxRecordPeriod1Code" on page 188

6.75 TrueFalseIndicatorDefinition: A flag indicating a True or False value.

Type: Indicator

Meaning When True: True

Meaning When False: False

Used in element(s)

"AmendmentIndicator" on page 83, "EmployeeTerminationIndicator" on page 70, "FamilyMedicalIn-suranceIndicator" on page 70

Legal Notices

30 January 2017 191

Legal Notices

Copyright

SWIFT © 2017. All rights reserved.

This material is a component of MyStandards, the SWIFT collaborative Web application used to man-age standards definitions and industry usage. It can only be used and distributed in accordance withMyStandards Terms of Use.

Unless otherwise agreed in writing with SWIFT SCRL, you have no right to:

- authorise external end users to use this component for other purposes than their internal use.

- remove, alter, cover, obfuscate or cancel from view any copyright or other proprietary rights noticesappearing in this physical medium.

- re-sell or authorise another party e.g. software and service providers, to re-sell this component.

Confidentiality

This publication may contain SWIFT or third-party confidential information. Only disclose it outside yourorganisation in accordance with MyStandards Terms of Use and your related license rights.

This component is provided 'AS IS'. SWIFT does not give and excludes any express or implied war-ranties with respect to this component such as but not limited to any guarantee as to its quality, supplyor availability.

Any and all rights, including title, ownership rights, copyright, trademark, patents, and any other intellec-tual property rights of whatever nature in this component will remain the exclusive property of SWIFT orits licensors.

Trademarks and Patents

SWIFT is the trade name of S.W.I.F.T. SCRL. The following are registered trademarks of SWIFT:SWIFT, the SWIFT logo, 3SKey, Innotribe, Sibos, SWIFTNet, MyStandards, SWIFTReady, and Accord.Other product, service, or company names in this publication are trade names, trademarks, or regis-tered trademarks of their respective owners.

tionv06 - payments canada€¦ · these messages was defined to align with cgi-mp usage guidelines....

Documents