tusReportV07 pain.002.001 - Payments Canada€¦ · Message Building Blocks 30 January 2017 9 4...

Usage Guideline

CorporatetoBankCustomerPaymentSta-tusReportV07_pain.002.001.07

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

This document describes a usage guideline restricting the base message MX pain.002.001.07. 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/_8LAowOctEeaCLcRTfGCsKA

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

http://www.swift.com/mystandards

Usage Guideline

2 CorporatetoBankCustomerPaymentStatusReportV07_pain.002.001.07 - Corporate to Bank Messages Portfolio - Draft- January 31, 2017

Table of Contents

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

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

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

3 Rules ......................................................................................................................................................................... 7

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

5 Message Components .................................................................................................................................... 13

6 Message Datatypes ........................................................................................................................................ 148

.Legal Notices ............................................................................................................................................................... 182

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 CustomerPaymentStatusReport message is sent by an instructed agent to the previous party in the payment chain. It is used to inform this party about the positive or negative status of an instruction (either single or file). It is also used to report on a pending instruction.UsageThe CustomerPaymentStatusReport message is exchanged between an agent and a non-financial institution customer to provide status information on instructions previously sent. Its usage will always be governed by a bilateral agreement between the agent and the non-financial institution customer.The CustomerPaymentStatusReport message can be used to provide information about the status (e.g. rejection, acceptance) of the initiation of a credit transfer, a direct debit, as well as on the initiation of other customer instructions.The CustomerPaymentStatusReport message refers to the original instruction(s) by means of references only or by means of references and a set of elements from the original instruction.The CustomerPaymentStatusReport message can be used in domestic and cross-border scenarios.

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 /CorporatetoBankCustomerPaymentStatusReportV07_pain.002.001.07 message is composed of 4building blocks

a. GroupHeader

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

b. OriginalGroupInformationAndStatus

Original group information concerning the group of transactions, to which the status report mes-sage refers to.

c. OriginalPaymentInformationAndStatus

Information concerning the original payment information, to which the status report message refers.

d. 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.002.001.07 message.

Restriction Type See page

Removed elements 12, 14, 14, 21, 23, 23, 28, 28, 28,28, 28, 28, 34, 34, 34, 35, 35, 35,36, 36, 36, 50, 50, 50, 51, 51, 51,52, 52, 52, 53, 53, 53, 61, 61, 61,61, 64, 64, 64, 64, 67, 68, 68, 75,75, 79, 82, 84, 84, 85, 86, 87, 87,88, 88, 90, 91, 94, 96, 96, 96, 96,96, 97, 98, 99, 100, 101, 102, 103, 103,103, 105, 127, 177, 177, 178, 178, 178, 178,178, 179, 179, 179, 179, 180, 180, 180, 181

Make mandatory 95

Reduce Multiplicity 78, 129

Ignore n.a.

Text rules 11, 66, 78, 101

Conditional rules 10

Fixed values 126

Truncates n.a.

Comments n.a.

Annotations n.a.

Changed datatypes n.a.

Extensions n.a.

Synonyms n.a.

Other restrictions

Usage Guideline


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

Index Message Item <XML Tag> Or Mult. UsageGuidelines

Page

CustomerPaymentStatusReportV07 <CstmrPmtStsRpt> [1..1] ! 9

GroupHeader <GrpHdr> [1..1] 9

MessageIdentification <MsgId> [1..1] 66

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

InitiatingParty <InitgPty> [0..1] 66

ForwardingAgent <FwdgAgt> [0..1] 67

DebtorAgent <DbtrAgt> [0..1] 67

CreditorAgent <CdtrAgt> [0..1] 68

OriginalGroupInformationAndStatus <OrgnlGrpInfAndSts> [1..1] ! 9

OriginalMessageIdentification <OrgnlMsgId> [1..1] 77

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] 77

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] 77

OriginalNumberOfTransactions <OrgnlNbOfTxs> [0..1] 77

OriginalControlSum <OrgnlCtrlSum> [0..1] 78

GroupStatus <GrpSts> [0..1] 78

StatusReasonInformation <StsRsnInf> [0..*] ! R[0..1] 78

NumberOfTransactionsPerStatus <NbOfTxsPerSts> [0..*] 78

OriginalPaymentInformationAndStatus <OrgnlPmtInfAndSts> [0..*] ! 10

OriginalPaymentInformationIdentification <OrgnlPmtInfId> [1..1] 80



PaymentInformationStatus <PmtInfSts> [0..1] 81

StatusReasonInformation <StsRsnInf> [0..*] 81


TransactionInformationAndStatus <TxInfAndSts> [0..*] 82

SupplementaryData <SplmtryData> [0..*] 12

PlaceAndName <PlcAndNm> [0..1] 134

Envelope <Envlp> [1..1] 134

Rules

30 January 2017 7

3 RulesR1 GroupStatusAcceptedRule ✓

If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to ACTC (Accept-edTechnicalValidation), ACCP (AcceptedCustomerProfile), ACSP (AcceptedSettlementIn-Process), ACSC (AcceptedSettlementCompleted) or ACWC (AcceptedWithChange), then Orig-inalPaymentInformationAndStatus/PaymentInformationStatus must be different from RJCT (Re-jected).

Error handling:

– Error severity: Fatal

– Error Code: X00063

– Error Text: Invalid message content for group and payment information statuses.

R2 GroupStatusPendingRule ✓

If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to PDNG (Pending),then OriginalPaymentInformationAndStatus/PaymentInformationStatus must be different fromRJCT (Rejected).

Error handling:




R3 GroupStatusRejectedRule ✓

If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to RJCT (Reject-ed), then OriginalPaymentInformationAndStatus/PaymentInformationStatus, if present, must beequal to RJCT (Rejected).

Error handling:




R4 GroupStatusReceivedRule ✓

If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to RCVD (Re-ceived), then OriginalPaymentInformationAndStatus/PaymentInformationStatus is not allowed.

Error handling:




Usage Guideline


R5 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

Message Building Blocks

30 January 2017 9

4 Message Building Blocks

Note The following chapter identifies the building blocks of the CustomerPaymentStatusRe-portV07 message definition.

Usage Guideline on Root Node

• on pain.002.001.07/

– CPA_Group_Status_Additional_Information_complexRule:

For each [CustomerPaymentStatusReportV07], if [OriginalGroupInformationAndStatus/StatusReasonInformation/Reason/Code] has value included in the following list 'NARR' , then there must be maximum '6' occurrences of [OriginalGroupInformationAndStatus/StatusReasonInformation/AdditionalInformation]

4.1 GroupHeaderXML Tag: GrpHdr

Presence: [1..1]

Definition: Set of characteristics shared by all individual transactions included in the status report mes-sage.

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

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


Page







4.2 OriginalGroupInformationAndStatusXML Tag: OrgnlGrpInfAndSts

Presence: [1..1]

Definition: Original group information concerning the group of transactions, to which the status reportmessage refers to.

Usage Guideline


The OrgnlGrpInfAndSts block contains the following elements (see datatype "OriginalGroupHead-er1__1" on page 76 for details)



Page









Usage Guideline details

• on pain.002.001.07/OriginalGroupInformationAndStatus

– CPA_OriginalGroupInformationAndStatus/GroupStatusRule:

If If GroupStatus is equal to PART

Then OriginalPaymentInformationAndStatus must be present

Else OriginalPaymentInformationAndStatus must not be present

4.3 OriginalPaymentInformationAndStatusXML Tag: OrgnlPmtInfAndSts

Presence: [0..*]

Definition: Information concerning the original payment information, to which the status report messagerefers.

Message Building Blocks

30 January 2017 11

The OrgnlPmtInfAndSts block contains the following elements (see datatype "OriginalPaymentInstruc-tion18__1" on page 79 for details)



Page

OriginalPaymentInformationIdentifica-tion

<OrgnlPmtInfId> [1..1] 80








• on pain.002.001.07/OriginalPaymentInformationAndStatus

– CPA_OriginalPaymentInformationAndStatus:

Only rejected transactions shall be identified in this message segment.

• on pain.002.001.07/

– CPA_No_Status_Reason_for_PDNG_ComplexRule:

For each [CustomerPaymentStatusReportV07], if the following element(s) [OriginalGroupInformationAndStatus/GroupStatus/Pending] is (are) present , then the following element(s) [OriginalPaymentInformationAndStatus] must be absent

• on pain.002.001.07/

– CPA_Partially_Accepted_ComplexRule:

For each [CustomerPaymentStatusReportV07], if the following element(s) [OriginalGroupInformationAndStatus/GroupStatus/PartiallyAccepted] is (are) present , then the following element(s) [OriginalPaymentInformationAndStatus] must be present

• on pain.002.001.07/

– CPA_If_Partially_Accepted_Rule:

Usage Guideline


For each [CustomerPaymentStatusReportV07], [OriginalPaymentInformationAndStatus] must be present when [OriginalGroupInformationAndStatus/GroupStatus/PartiallyAccepted] is present

• on pain.002.001.07/

– CPA_No_Status_Reason_for_ACTC_ComplexRule:

For each [CustomerPaymentStatusReportV07], if the following element(s) [OriginalGroupInformationAndStatus/GroupStatus/AcceptedTechnicalValidation] is (are) present , then the following element(s) [OriginalPaymentInformationAndStatus] must be absent

• on pain.002.001.07/

– CPA_No_Status_Reason_for_RCVD_ComplexRule:

For each [CustomerPaymentStatusReportV07], if the following element(s) [OriginalGroupInformationAndStatus/GroupStatus/Received] is (are) present , then the following element(s) [OriginalPaymentInformationAndStatus] must be absent

4.4 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 133 for details)



Page




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

Message Components

30 January 2017 13

5 Message Components

Note The following chapter identifies the CustomerPaymentStatusReportV07 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] 13

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

Used in element(s)

"Identification" on page 25

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 164

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 59 for details)



Page

Identification <Id> [1..1] 59

SchemeName <SchmeNm> [0..1] 59

Issuer <Issr> [0..1] 59

Usage Guideline


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 164


• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/DebtorAccount/Identification/IBAN) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/CreditorAccount/Identification/IBAN) is removed.


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__1" onpage 60 for details)



Page




Message Components

30 January 2017 15

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



Page

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

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

Used in element(s)

"SchemeName" on page 59, "SchemeName" on page 60

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 157

5.3.2 ProprietaryXML Tag: Prtry

Presence: [1..1]

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

Datatype: "Max35Text" on page 168

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

Usage Guideline




Page

OriginalMandateIdentification <OrgnlMndtId> [0..1] 16

OriginalCreditorSchemeIdentification <OrgnlCdtrSchmeId> [0..1] 16

OriginalCreditorAgent <OrgnlCdtrAgt> [0..1] 17

OriginalCreditorAgentAccount <OrgnlCdtrAgtAcct> [0..1] 17

OriginalDebtor <OrgnlDbtr> [0..1] 18

OriginalDebtorAccount <OrgnlDbtrAcct> [0..1] 18

OriginalDebtorAgent <OrgnlDbtrAgt> [0..1] 18

OriginalDebtorAgentAccount <OrgnlDbtrAgtAcct> [0..1] 19

OriginalFinalCollectionDate <OrgnlFnlColltnDt> [0..1] 19

OriginalFrequency <OrgnlFrqcy> [0..1] 19

OriginalReason <OrgnlRsn> [0..1] 20

Used in element(s)

"AmendmentInformationDetails" on page 70

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.

Message Components

30 January 2017 17

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



Page

Name <Nm> [0..1] 95

PostalAddress <PstlAdr> [0..1] 95


CountryOfResidence <CtryOfRes> [0..1] 96

ContactDetails <CtctDtls> [0..1] 96

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 21 for details)



Page

FinancialInstitutionIdentification <FinInstnId> [1..1] 21

BranchIdentification <BrnchId> [0..1] 22

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 25 for details)



Page


Type <Tp> [0..1] 26

Currency <Ccy> [0..1] 26

Name <Nm> [0..1] 26

Usage Guideline


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 94 for details)



Page

Name <Nm> [0..1] 95





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 25 for details)



Page


Type <Tp> [0..1] 26


Name <Nm> [0..1] 26

5.4.7 OriginalDebtorAgentXML Tag: OrgnlDbtrAgt

Presence: [0..1]

Definition: Original debtor agent that has been modified.

Message Components

30 January 2017 19

The OrgnlDbtrAgt block contains the following elements (see datatype "BranchAndFinancialInstitu-tionIdentification5" on page 21 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 25 for details)



Page


Type <Tp> [0..1] 26


Name <Nm> [0..1] 26

5.4.9 OriginalFinalCollectionDateXML Tag: OrgnlFnlColltnDt

Presence: [0..1]

Definition: Original final collection date that has been modified.

Datatype: "ISODate" on page 164

5.4.10 OriginalFrequencyXML Tag: OrgnlFrqcy

Presence: [0..1]

Definition: Original frequency that has been modified.

Usage Guideline


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



Page

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

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

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 72 for details)



Page

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


5.5 AmountType4ChoiceDefinition: Specifies the amount of money to be moved between the debtor and creditor, before deduc-tion of charges, expressed in the currency as ordered by the initiating party.



Page

InstructedAmount <InstdAmt> {Or [1..1] 20

EquivalentAmount <EqvtAmt> Or} [1..1] 21

Used in element(s)

"Amount" on page 84

5.5.1 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.

Message Components

30 January 2017 21

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

Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 148

5.5.2 EquivalentAmountXML Tag: EqvtAmt

Presence: [1..1]

Definition: Amount of money to be moved between the debtor and creditor, expressed in the currency ofthe debtor's account, and the currency in which the amount is to be moved.

The EqvtAmt block contains the following elements (see datatype "EquivalentAmount2" on page 46for details)



Page

Amount <Amt> [1..1] 47

CurrencyOfTransfer <CcyOfTrf> [1..1] 47


• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/Amount/EquivalentAmount) is removed.

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)

"Agent" on page 30, "CreditorAgent" on page 68, "DebtorAgent" on page 67, "InstructedReim-bursementAgent" on page 123, "InstructingReimbursementAgent" on page 123, "OriginalCreditorA-gent" on page 17, "OriginalDebtorAgent" on page 18, "ThirdReimbursementAgent" on page 124

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.

Usage Guideline


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



Page

BICFI <BICFI> [0..1] 48

ClearingSystemMemberIdentification <ClrSysMmbId> [0..1] 48

Name <Nm> [0..1] 48


Other <Othr> [0..1] 49

5.6.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 24 for de-tails)



Page


Name <Nm> [0..1] 24


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)

"CreditorAgent" on page 90, "DebtorAgent" on page 89, "ForwardingAgent" on page 67

Message Components

30 January 2017 23

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.

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



Page



Name <Nm> [0..1] 51



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 24 for de-tails)



Page


Name <Nm> [0..1] 24



• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/DebtorAgent/BranchIdentification) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/CreditorAgent/BranchIdentification) is removed.

Usage Guideline


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



Page


Name <Nm> [0..1] 24


Used in element(s)

"BranchIdentification" on page 22, "BranchIdentification" on page 23

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.

Message Components

30 January 2017 25

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



Page

AddressType <AdrTp> [0..1] 109

Department <Dept> [0..1] 109

SubDepartment <SubDept> [0..1] 109

StreetName <StrtNm> [0..1] 109

BuildingNumber <BldgNb> [0..1] 110

PostCode <PstCd> [0..1] 110

TownName <TwnNm> [0..1] 110

CountrySubDivision <CtrySubDvsn> [0..1] 110

Country <Ctry> [0..1] 110

AddressLine <AdrLine> [0..7] 110

5.9 CashAccount24Definition: Provides the details to identify an account.



Page


Type <Tp> [0..1] 26


Name <Nm> [0..1] 26

Used in element(s)

"CreditorAgentAccount" on page 91, "DebtorAgentAccount" on page 90, "InstructedReimburse-mentAgentAccount" on page 124, "InstructingReimbursementAgentAccount" on page 123, "Origi-nalCreditorAgentAccount" on page 17, "OriginalDebtorAccount" on page 18, "OriginalDebtorA-gentAccount" on page 19, "SettlementAccount" on page 122, "ThirdReimbursementAgentAccount"on page 125


Presence: [1..1]

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

Usage Guideline


The Id block contains the following elements (see datatype "AccountIdentification4Choice" onpage 13 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 29for details)



Page

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


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 148


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.


Message Components

30 January 2017 27

5.10 CashAccount24__1Definition: Provides the details to identify an account.



Page


Type <Tp> [0..1] 27


Name <Nm> [0..1] 28

Used in element(s)

"CreditorAccount" on page 91, "DebtorAccount" on page 89


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 14 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 29for details)



Page

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


Usage Guideline



• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/DebtorAccount/Type) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/CreditorAccount/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.



• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/DebtorAccount/Currency) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/CreditorAccount/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.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/DebtorAccount/Name) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/CreditorAccount/Name) is removed.

Message Components

30 January 2017 29

5.11 CashAccountType2ChoiceDefinition: Nature or use of the account.



Page

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


Used in element(s)

"Type" on page 26, "Type" on page 27


Presence: [1..1]

Definition: Account type, in a coded form.

Datatype: "ExternalCashAccountType1Code" on page 157


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] 29


Used in element(s)

"CategoryPurpose" on page 106


Usage Guideline


Presence: [1..1]

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

Datatype: "ExternalCategoryPurpose1Code" on page 158


Presence: [1..1]

Definition: Category purpose, in a proprietary form.


5.13 Charges2Definition: Set of elements used to provide information on the charges related to the payment transac-tion.



Page


Agent <Agt> [1..1] 30

Used in element(s)

"ChargesInformation" on page 102

5.13.1 AmountXML Tag: Amt

Presence: [1..1]

Definition: Transaction charges to be paid by the charge bearer.


5.13.2 AgentXML Tag: Agt

Presence: [1..1]

Definition: Agent that takes the transaction charges or to which the transaction charges are due.

Message Components

30 January 2017 31

The Agt block contains the following elements (see datatype "BranchAndFinancialInstitutionIdentifica-tion5" on page 21 for details)



Page



5.14 ClearingSystemIdentification2ChoiceDefinition: Choice of a clearing system identifier.



Page

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


Used in element(s)

"ClearingSystemIdentification" on page 32, "ClearingSystemIdentification" on page 33


Presence: [1..1]

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

Datatype: "ExternalClearingSystemIdentification1Code" on page 158


Presence: [1..1]

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


5.15 ClearingSystemIdentification3ChoiceDefinition: Specifies the clearing system identification.

Usage Guideline




Page

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


Used in element(s)

"ClearingSystem" on page 122


Presence: [1..1]

Definition: Infrastructure through which the payment instruction is processed, as published in an exter-nal clearing system identification code list.

Datatype: "ExternalCashClearingSystem1Code" on page 157


Presence: [1..1]

Definition: Clearing system identification in a proprietary form.


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



Page

ClearingSystemIdentification <ClrSysId> [0..1] 32

MemberIdentification <MmbId> [1..1] 33

Used in element(s)

"ClearingSystemMemberIdentification" on page 48

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.

Message Components

30 January 2017 33

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



Page

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


5.16.2 MemberIdentificationXML Tag: MmbId

Presence: [1..1]

Definition: Identification of a member of a clearing system.


5.17 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 50

5.17.1 ClearingSystemIdentificationXML Tag: ClrSysId

Presence: [0..1]


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



Page

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


Usage Guideline



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

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInforma-tionAndStatus/OriginalTransactionReference/DebtorAgent/FinancialInstitutionIdentifica-tion/ClearingSystemMemberIdentification/ClearingSystemIdentification) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInforma-tionAndStatus/OriginalTransactionReference/CreditorAgent/FinancialInstitutionIdentifica-tion/ClearingSystemMemberIdentification/ClearingSystemIdentification) is removed.

5.17.2 MemberIdentificationXML Tag: MmbId

Presence: [1..1]

Definition: Identification of a member of a clearing system.

Datatype: "CPA_Exact9NumericText" on page 151

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



Page

NamePrefix <NmPrfx> [0..1] 34

Name <Nm> [0..1] 35

PhoneNumber <PhneNb> [0..1] 35

MobileNumber <MobNb> [0..1] 35

FaxNumber <FaxNb> [0..1] 35

EmailAddress <EmailAdr> [0..1] 36


Used in element(s)

"ContactDetails" on page 96, "ContactDetails" on page 99

5.18.1 NamePrefixXML Tag: NmPrfx

Presence: [0..1]

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

Datatype: "NamePrefix1Code" on page 169

Message Components

30 January 2017 35


• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/Debtor/ContactDetails/NamePrefix) is removed.


Presence: [0..1]

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


5.18.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 172


• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/Debtor/ContactDetails/PhoneNumber) is removed.

5.18.4 MobileNumberXML Tag: MobNb

Presence: [0..1]

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



• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/Debtor/ContactDetails/MobileNumber) is removed.

5.18.5 FaxNumberXML Tag: FaxNb

Presence: [0..1]

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


Usage Guideline



• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/Debtor/ContactDetails/FaxNumber) is removed.

5.18.6 EmailAddressXML Tag: EmailAdr

Presence: [0..1]

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



• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/Debtor/ContactDetails/EmailAddress) is removed.


Presence: [0..1]

Definition: Contact details in an other form.



• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/Debtor/ContactDetails/Other) is removed.

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



Page

Type <Tp> [0..1] 37

Reference <Ref> [0..1] 37

Used in element(s)

"CreditorReferenceInformation" on page 130

Message Components

30 January 2017 37


Presence: [0..1]

Definition: Specifies the type of creditor reference.

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



Page

CodeOrProprietary <CdOrPrtry> [1..1] 38


5.19.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.20 CreditorReferenceType1ChoiceDefinition: Specifies the type of document referred by the creditor.



Page

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


Used in element(s)

"CodeOrProprietary" on page 38


Presence: [1..1]

Usage Guideline


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

Datatype: "DocumentType3Code" on page 154


Presence: [1..1]

Definition: Creditor reference type, in a proprietary form.


5.21 CreditorReferenceType2Definition: Specifies the type of creditor reference.



Page



Used in element(s)

"Type" on page 37

5.21.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 37 for details)



Page

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


5.21.2 IssuerXML Tag: Issr

Presence: [0..1]

Definition: Entity that assigns the credit reference type.


Message Components

30 January 2017 39

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



Page

BirthDate <BirthDt> [1..1] 39

ProvinceOfBirth <PrvcOfBirth> [0..1] 39

CityOfBirth <CityOfBirth> [1..1] 39

CountryOfBirth <CtryOfBirth> [1..1] 39

Used in element(s)

"DateAndPlaceOfBirth" on page 107

5.22.1 BirthDateXML Tag: BirthDt

Presence: [1..1]

Definition: Date on which a person is born.


5.22.2 ProvinceOfBirthXML Tag: PrvcOfBirth

Presence: [0..1]

Definition: Province where a person was born.


5.22.3 CityOfBirthXML Tag: CityOfBirth

Presence: [1..1]

Definition: City where a person was born.


5.22.4 CountryOfBirthXML Tag: CtryOfBirth

Presence: [1..1]

Definition: Country where a person was born.

Datatype: "CountryCode" on page 153

Usage Guideline


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



Page

FromDate <FrDt> [1..1] 40

ToDate <ToDt> [1..1] 40

Used in element(s)

"FromToDate" on page 144

5.23.1 FromDateXML Tag: FrDt

Presence: [1..1]

Definition: Start date of the range.


5.23.2 ToDateXML Tag: ToDt

Presence: [1..1]

Definition: End date of the range.


5.24 DiscountAmountAndType1Definition: Specifies the amount with a specific type.



Page

Type <Tp> [0..1] 40


Used in element(s)

"DiscountAppliedAmount" on page 114, "DiscountAppliedAmount" on page 116


Presence: [0..1]

Definition: Specifies the type of the amount.

Message Components

30 January 2017 41

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



Page

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



Presence: [1..1]

Definition: Amount of money, which has been typed.


5.25 DiscountAmountType1ChoiceDefinition: Specifies the amount type.



Page

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


Used in element(s)

"Type" on page 40


Presence: [1..1]

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

Datatype: "ExternalDiscountAmountType1Code" on page 158


Presence: [1..1]

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


Usage Guideline


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



Page


CreditDebitIndicator <CdtDbtInd> [0..1] 42

Reason <Rsn> [0..1] 42

AdditionalInformation <AddtlInf> [0..1] 42

Used in element(s)

"AdjustmentAmountAndReason" on page 115, "AdjustmentAmountAndReason" on page 117


Presence: [1..1]

Definition: Amount of money of the document adjustment.


5.26.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 153

5.26.3 ReasonXML Tag: Rsn

Presence: [0..1]

Definition: Specifies the reason for the adjustment.


5.26.4 AdditionalInformationXML Tag: AddtlInf

Presence: [0..1]

Definition: Provides further details on the document adjustment.


Message Components

30 January 2017 43

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



Page

Type <Tp> [0..1] 43

Number <Nb> [0..1] 43

RelatedDate <RltdDt> [0..1] 43

Used in element(s)



Presence: [0..1]

Definition: Specifies the type of referred document line identification.

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



Page



5.27.2 NumberXML Tag: Nb

Presence: [0..1]

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


5.27.3 RelatedDateXML Tag: RltdDt

Presence: [0..1]

Definition: Date associated with the referred document line.


Usage Guideline


5.28 DocumentLineInformation1Definition: Provides document line information.



Page

Identification <Id> [1..*] 44

Description <Desc> [0..1] 44


Used in element(s)

"LineDetails" on page 112


Presence: [1..*]

Definition: Provides identification of the document line.

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



Page

Type <Tp> [0..1] 43

Number <Nb> [0..1] 43


5.28.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.

Message Components

30 January 2017 45

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



Page

DuePayableAmount <DuePyblAmt> [0..1] 116

DiscountAppliedAmount <DscntApldAmt> [0..*] 116

CreditNoteAmount <CdtNoteAmt> [0..1] 116

TaxAmount <TaxAmt> [0..*] 117

AdjustmentAmountAndReason <AdjstmntAmtAndRsn> [0..*] 117

RemittedAmount <RmtdAmt> [0..1] 117

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



Page



Used in element(s)

"Type" on page 43


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 46 for details)



Page

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



Usage Guideline


Presence: [0..1]

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


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



Page

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


Used in element(s)



Presence: [1..1]

Definition: Line identification type in a coded form.

Datatype: "ExternalDocumentLineType1Code" on page 159


Presence: [1..1]

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


5.31 EquivalentAmount2Definition: Amount of money to be moved between the debtor and creditor, expressed in the currency ofthe debtor's account, and the currency in which the amount is to be moved.



Page


CurrencyOfTransfer <CcyOfTrf> [1..1] 47

Used in element(s)

"EquivalentAmount" on page 21

Message Components

30 January 2017 47


Presence: [1..1]

Definition: Amount of money to be moved between debtor and creditor, before deduction of charges,expressed in the currency of the debtor's account, and to be moved in a different currency.

Usage: The first agent will convert the equivalent amount into the amount to be moved.


5.31.2 CurrencyOfTransferXML Tag: CcyOfTrf

Presence: [1..1]

Definition: Specifies the currency of the to be transferred amount, which is different from the currency ofthe debtor's account.


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



Page

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


Used in element(s)

"SchemeName" on page 62


Presence: [1..1]


Datatype: "ExternalFinancialInstitutionIdentification1Code" on page 159


Presence: [1..1]



Usage Guideline


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



Page



Name <Nm> [0..1] 48



Used in element(s)

"FinancialInstitutionIdentification" on page 21

5.33.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 151

5.33.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 32 for details)



Page




Presence: [0..1]



Message Components

30 January 2017 49


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 61 for details)



Page




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

Usage Guideline




Page



Name <Nm> [0..1] 51



Used in element(s)

"FinancialInstitutionIdentification" on page 23

5.34.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 151


• This element(pain.002.001.07/GroupHeader/ForwardingAgent/FinancialInstitutionIdentifica-tion/BICFI) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInforma-tionAndStatus/OriginalTransactionReference/DebtorAgent/FinancialInstitutionIdentifica-tion/BICFI) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInforma-tionAndStatus/OriginalTransactionReference/CreditorAgent/FinancialInstitutionIdentifica-tion/BICFI) is removed.

5.34.2 ClearingSystemMemberIdentificationXML Tag: ClrSysMmbId

Presence: [0..1]

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

Message Components

30 January 2017 51

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



Page




Presence: [0..1]




• This element(pain.002.001.07/GroupHeader/ForwardingAgent/FinancialInstitutionIdentifica-tion/Name) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInforma-tionAndStatus/OriginalTransactionReference/DebtorAgent/FinancialInstitutionIdentifica-tion/Name) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInforma-tionAndStatus/OriginalTransactionReference/CreditorAgent/FinancialInstitutionIdentifica-tion/Name) is removed.


Presence: [0..1]


Usage Guideline





Page












• This element(pain.002.001.07/GroupHeader/ForwardingAgent/FinancialInstitutionIdentifica-tion/PostalAddress) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInforma-tionAndStatus/OriginalTransactionReference/DebtorAgent/FinancialInstitutionIdentifica-tion/PostalAddress) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInforma-tionAndStatus/OriginalTransactionReference/CreditorAgent/FinancialInstitutionIdentifica-tion/PostalAddress) is removed.


Presence: [0..1]

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

Message Components

30 January 2017 53

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



Page





• This element(pain.002.001.07/GroupHeader/ForwardingAgent/FinancialInstitutionIdentifica-tion/Other) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/DebtorAgent/FinancialInstitutionIdentification/Oth-er) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInforma-tionAndStatus/OriginalTransactionReference/CreditorAgent/FinancialInstitutionIdentifica-tion/Other) is removed.

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



Page

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


Used in element(s)

"Frequency" on page 71, "OriginalFrequency" on page 19


Presence: [1..1]

Definition: Frequency expressed as an ISO 20022 code.

Datatype: "Frequency6Code" on page 162

5.35.2 PeriodXML Tag: Prd

Usage Guideline


Presence: [1..1]

Definition: Frequency expressed as a proprietary code.

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



Page

Type <Tp> [1..1] 54

CountPerPeriod <CntPerPrd> [1..1] 54

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



Page

Type <Tp> [1..1] 54

CountPerPeriod <CntPerPrd> [1..1] 54

Used in element(s)

"Period" on page 53


Presence: [1..1]

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

Datatype: "Frequency6Code" on page 162

5.36.2 CountPerPeriodXML Tag: CntPerPrd

Presence: [1..1]

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

Datatype: "DecimalNumber" on page 153

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

Message Components

30 January 2017 55



Page

Type <Tp> [1..1] 55

Garnishee <Grnshee> [0..1] 55

GarnishmentAdministrator <GrnshmtAdmstr> [0..1] 56

ReferenceNumber <RefNb> [0..1] 56

Date <Dt> [0..1] 56


FamilyMedicalInsuranceIndicator <FmlyMdclInsrncInd> [0..1] 57

EmployeeTerminationIndicator <MplyeeTermntnInd> [0..1] 57

Used in element(s)

"GarnishmentRemittance" on page 132


Presence: [1..1]

Definition: Specifies the type of garnishment.

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



Page



5.37.2 GarnisheeXML Tag: Grnshee

Presence: [0..1]

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

Usage Guideline


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



Page

Name <Nm> [0..1] 95





5.37.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 94 for details)



Page

Name <Nm> [0..1] 95





5.37.4 ReferenceNumberXML Tag: RefNb

Presence: [0..1]

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


5.37.5 DateXML Tag: Dt

Presence: [0..1]

Definition: Date of payment which garnishment was taken from.

Message Components

30 January 2017 57


5.37.6 RemittedAmountXML Tag: RmtdAmt

Presence: [0..1]

Definition: Amount of money remitted for the referred document.


5.37.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 181

5.37.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.38 GarnishmentType1Definition: Specifies the type of garnishment.



Page



Used in element(s)

"Type" on page 55


Presence: [1..1]

Definition: Provides the type details of the garnishment.

Usage Guideline


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



Page

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



Presence: [0..1]

Definition: Identification of the issuer of the garnishment type.


5.39 GarnishmentType1ChoiceDefinition: Specifies the type of garnishment.



Page

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


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 159


Message Components

30 January 2017 59

Presence: [1..1]

Definition: Proprietary identification of the type of garnishment.


5.40 GenericAccountIdentification1Definition: Information related to a generic account identification.



Page




Used in element(s)

"Other" on page 13


Presence: [1..1]

Definition: Identification assigned by an institution.


5.40.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 15 for details)



Page

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



Presence: [0..1]

Definition: Entity that assigns the identification.

Usage Guideline



5.41 GenericAccountIdentification1__1Definition: Information related to a generic account identification.



Page




Used in element(s)

"Other" on page 14


Presence: [1..1]




Presence: [0..1]


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



Page

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


Message Components

30 January 2017 61


• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/DebtorAccount/Identification/Other/SchemeName)is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInforma-tionAndStatus/OriginalTransactionReference/CreditorAccount/Identification/Other/Scheme-Name) is removed.


Presence: [0..1]




• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/DebtorAccount/Identification/Other/Issuer) is re-moved.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/CreditorAccount/Identification/Other/Issuer) is re-moved.

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



Page




Used in element(s)

"Other" on page 49, "Other" on page 52


Presence: [1..1]

Definition: Unique and unambiguous identification of a person.

Usage Guideline




Presence: [0..1]


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



Page

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



Presence: [0..1]



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



Page




Used in element(s)

"Other" on page 74


Presence: [1..1]



Message Components

30 January 2017 63


Presence: [0..1]


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



Page

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



Presence: [0..1]



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



Page




Used in element(s)

"Other" on page 75


Presence: [1..1]


Datatype: "CPA_Exact9NumericText" on page 151

Usage Guideline



Presence: [0..1]


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



Page

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



• This element(pain.002.001.07/GroupHeader/InitiatingParty/Identification/OrganisationIdentifi-cation/Other/SchemeName) is removed.

• This element(pain.002.001.07/OriginalGroupInformationAndStatus/StatusReasonInforma-tion/Originator/Identification/OrganisationIdentification/Other/SchemeName) is removed.


Presence: [0..1]




• This element(pain.002.001.07/GroupHeader/InitiatingParty/Identification/OrganisationIdentifi-cation/Other/Issuer) is removed.

• This element(pain.002.001.07/OriginalGroupInformationAndStatus/StatusReasonInforma-tion/Originator/Identification/OrganisationIdentification/Other/Issuer) is removed.

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

Message Components

30 January 2017 65



Page




Used in element(s)

"Other" on page 107


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 108 for details)



Page

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



Presence: [0..1]



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

Usage Guideline




Page







Used in element(s)

"GroupHeader" on page 9

5.46.1 MessageIdentificationXML Tag: MsgId

Presence: [1..1]

Definition: Point to point reference, as 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.


5.46.2 CreationDateTimeXML Tag: CreDtTm

Presence: [1..1]

Definition: Date and time at which the message was created.

Datatype: "ISODateTime" on page 165


• on pain.002.001.07/GroupHeader/CreationDateTime

– CPA_C2B_CreationDateTime_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.

5.46.3 InitiatingPartyXML Tag: InitgPty

Presence: [0..1]

Message Components

30 January 2017 67

Definition: Party that initiates the status message.

The InitgPty block contains the following elements (see datatype "PartyIdentification43__1" onpage 97 for details)



Page

Name <Nm> [0..1] 97





5.46.4 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.

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



Page




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

5.46.5 DebtorAgentXML Tag: DbtrAgt

Presence: [0..1]

Definition: Financial institution servicing an account for the debtor.

Usage Guideline


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



Page




• This element(pain.002.001.07/GroupHeader/DebtorAgent) is removed.

5.46.6 CreditorAgentXML Tag: CdtrAgt

Presence: [0..1]

Definition: Financial institution servicing an account for the creditor.

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



Page




• This element(pain.002.001.07/GroupHeader/CreditorAgent) is removed.

5.47 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] 69


Used in element(s)

"LocalInstrument" on page 106

Message Components

30 January 2017 69


Presence: [1..1]

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

Datatype: "ExternalLocalInstrument1Code" on page 160


Presence: [1..1]

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


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



Page

MandateIdentification <MndtId> [0..1] 70

DateOfSignature <DtOfSgntr> [0..1] 70

AmendmentIndicator <AmdmntInd> [0..1] 70

AmendmentInformationDetails <AmdmntInfDtls> [0..1] 70

ElectronicSignature <ElctrncSgntr> [0..1] 71

FirstCollectionDate <FrstColltnDt> [0..1] 71

FinalCollectionDate <FnlColltnDt> [0..1] 71

Frequency <Frqcy> [0..1] 71


Rules

R22 AmendmentIndicatorTrueRule ✓

If AmendmentIndicator is true, then AmendementInformationDetails must be present.

Error handling:



Usage Guideline


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

R23 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 87

5.48.1 MandateIdentificationXML Tag: MndtId

Presence: [0..1]

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


5.48.2 DateOfSignatureXML Tag: DtOfSgntr

Presence: [0..1]

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


5.48.3 AmendmentIndicatorXML Tag: AmdmntInd

Presence: [0..1]

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


5.48.4 AmendmentInformationDetailsXML Tag: AmdmntInfDtls

Presence: [0..1]

Definition: List of mandate elements that have been modified.

Message Components

30 January 2017 71

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



Page

OriginalMandateIdentification <OrgnlMndtId> [0..1] 16

OriginalCreditorSchemeIdentification <OrgnlCdtrSchmeId> [0..1] 16

OriginalCreditorAgent <OrgnlCdtrAgt> [0..1] 17

OriginalCreditorAgentAccount <OrgnlCdtrAgtAcct> [0..1] 17

OriginalDebtor <OrgnlDbtr> [0..1] 18

OriginalDebtorAccount <OrgnlDbtrAcct> [0..1] 18

OriginalDebtorAgent <OrgnlDbtrAgt> [0..1] 18

OriginalDebtorAgentAccount <OrgnlDbtrAgtAcct> [0..1] 19

OriginalFinalCollectionDate <OrgnlFnlColltnDt> [0..1] 19

OriginalFrequency <OrgnlFrqcy> [0..1] 19

OriginalReason <OrgnlRsn> [0..1] 20

5.48.5 ElectronicSignatureXML Tag: ElctrncSgntr

Presence: [0..1]

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


5.48.6 FirstCollectionDateXML Tag: FrstColltnDt

Presence: [0..1]

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


5.48.7 FinalCollectionDateXML Tag: FnlColltnDt

Presence: [0..1]

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


5.48.8 FrequencyXML Tag: Frqcy

Usage Guideline


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 53 fordetails)



Page

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



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 72 for details)



Page

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


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



Page

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


Used in element(s)

"OriginalReason" on page 20, "Reason" on page 72


Presence: [1..1]

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

Message Components

30 January 2017 73

Datatype: "ExternalMandateSetupReason1Code" on page 160


Presence: [1..1]

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


5.50 NumberOfTransactionsPerStatus3Definition: Set of elements used to provide detailed information on the number of transactions that arereported with a specific transaction status.



Page

DetailedNumberOfTransactions <DtldNbOfTxs> [1..1] 73

DetailedStatus <DtldSts> [1..1] 73

DetailedControlSum <DtldCtrlSum> [0..1] 73

Used in element(s)

"NumberOfTransactionsPerStatus" on page 78, "NumberOfTransactionsPerStatus" on page 81

5.50.1 DetailedNumberOfTransactionsXML Tag: DtldNbOfTxs

Presence: [1..1]

Definition: Number of individual transactions contained in the message, detailed per status.

Datatype: "Max15NumericText" on page 166

5.50.2 DetailedStatusXML Tag: DtldSts

Presence: [1..1]

Definition: Common transaction status for all individual transactions reported.

Datatype: "TransactionIndividualStatus3Code" on page 180

5.50.3 DetailedControlSumXML Tag: DtldCtrlSum

Presence: [0..1]

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


Usage Guideline


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



Page

AnyBIC <AnyBIC> [0..1] 74

Other <Othr> [0..*] 74

Used in element(s)

"OrganisationIdentification" on page 93

5.51.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 150


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 62 for details)



Page




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

Message Components

30 January 2017 75



Page



Used in element(s)

"OrganisationIdentification" on page 93

5.52.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 150


• This element(pain.002.001.07/GroupHeader/InitiatingParty/Identification/OrganisationIdentifi-cation/AnyBIC) is removed.

• This element(pain.002.001.07/OriginalGroupInformationAndStatus/StatusReasonInforma-tion/Originator/Identification/OrganisationIdentification/AnyBIC) is removed.


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__1"on page 63 for details)



Page




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

Usage Guideline




Page

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


Used in element(s)

"SchemeName" on page 63, "SchemeName" on page 64


Presence: [1..1]


Datatype: "ExternalOrganisationIdentification1Code" on page 161


Presence: [1..1]



5.54 OriginalGroupHeader1__1Definition: Provides details on the original group, to which the message refers.



Page









Message Components

30 January 2017 77

Rules

R24 StatusReasonInformationRule ✓

If GroupStatus is present and is different from RJCT or PDNG then StatusReasonInforma-tion/AdditionalInformation must be absent.

Error handling:



– Error Text: Invalid message content for additional status reason.

Guidelines

1. NumberOfTransactionPerStatusGuideline

OriginalGroupInformationAndStatus/NumberOfTransactionsPerStatus should only be present ifGroupStatus equals 'PART'.

Used in element(s)

"OriginalGroupInformationAndStatus" on page 9

5.54.1 OriginalMessageIdentificationXML Tag: OrgnlMsgId

Presence: [1..1]

Definition: Point to point reference, as assigned by the original instructing party, to unambiguously iden-tify the original message.


5.54.2 OriginalMessageNameIdentificationXML Tag: OrgnlMsgNmId

Presence: [1..1]

Definition: Specifies the original message name identifier to which the message refers.


5.54.3 OriginalCreationDateTimeXML Tag: OrgnlCreDtTm

Presence: [0..1]

Definition: Date and time at which the original message was created.


5.54.4 OriginalNumberOfTransactionsXML Tag: OrgnlNbOfTxs

Presence: [0..1]

Usage Guideline


Definition: Number of individual transactions contained in the original message.


5.54.5 OriginalControlSumXML Tag: OrgnlCtrlSum

Presence: [0..1]

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


5.54.6 GroupStatusXML Tag: GrpSts

Presence: [0..1]

Definition: Specifies the status of a group of transactions.

Datatype: "TransactionGroupStatus3Code" on page 177

5.54.7 StatusReasonInformationXML Tag: StsRsnInf

Presence: [0..*]

Definition: Provides detailed information on the status reason.

The StsRsnInf block contains the following elements (see datatype "StatusReasonInformation9__1" onpage 127 for details)



Page

Originator <Orgtr> [0..1] 128

Reason <Rsn> [0..1] 128

AdditionalInformation <AddtlInf> [0..*] R[0..6] 129


• on pain.002.001.07/OriginalGroupInformationAndStatus/StatusReasonInformation

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

• on pain.002.001.07/OriginalGroupInformationAndStatus/StatusReasonInformation

– CPA_Status_Reason_Guideline:

This element should be populated with content from the External code list.

5.54.8 NumberOfTransactionsPerStatusXML Tag: NbOfTxsPerSts

Message Components

30 January 2017 79

Presence: [0..*]

Definition: Detailed information on the number of transactions for each identical transaction status.

The NbOfTxsPerSts block contains the following elements (see datatype "NumberOfTransaction-sPerStatus3" on page 73 for details)



Page





• This element(pain.002.001.07/OriginalGroupInformationAndStatus/NumberOfTransaction-sPerStatus) is removed.

5.55 OriginalPaymentInstruction18__1Definition: Provides details information on the original transactions, to which the status report messagerefers.



Page

OriginalPaymentInformationIdentifica-tion

<OrgnlPmtInfId> [1..1] 80







Rules

R26 PaymentInformationStatusAcceptedRule ✓

If OriginalPaymentInformationAndStatus/PaymentInformationStatus is present and is equal toACTC (AcceptedTechnicalValidation), ACCP (AcceptedCustomerProfile), ACSP (AcceptedSet-tlementInProcess), ACSC (AcceptedSettlementCompleted) or ACWC (AcceptedWithChange),then TransactionInformationAndStatus/TransactionStatus must be different from RJCT (Reject-ed).

Usage Guideline


Error handling:




R27 PaymentInformationStatusPendingRule ✓

If OriginalPaymentInformationAndStatus/PaymentInformationStatus is present and is equal toPDNG (Pending), then TransactionInformationAndStatus/TransactionStatus must be differentfrom RJCT (Rejected).

Error handling:




R28 PaymentInformationStatusRejectedRule ✓

If OriginalPaymentInformationAndStatus/PaymentInformationStatus is present and is equal toRJCT (Rejceted), then TransactionInformationAndStatus/TransactionStatus, if present, must beequal to RJCT (Rejected).

Error handling:




R29 PaymentInformationStatusReceivedRule ✓

If OriginalPaymentInformationAndStatus/PaymentInformationStatus is present and is equal toRCVD (Received), then TransactionInformationAndStatus/TransactionStatus is not allowed.

Error handling:




Used in element(s)

"OriginalPaymentInformationAndStatus" on page 10

5.55.1 OriginalPaymentInformationIdentificationXML Tag: OrgnlPmtInfId

Presence: [1..1]

Definition: Unique identification, as assigned by the original sending party, to unambiguously identify theoriginal payment information group.


Message Components

30 January 2017 81

5.55.2 OriginalNumberOfTransactionsXML Tag: OrgnlNbOfTxs

Presence: [0..1]

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


5.55.3 OriginalControlSumXML Tag: OrgnlCtrlSum

Presence: [0..1]

Definition: Total of all individual amounts included in the original payment information group, irrespec-tive of currencies.


5.55.4 PaymentInformationStatusXML Tag: PmtInfSts

Presence: [0..1]

Definition: Specifies the status of the payment information group.

Datatype: "TransactionGroupStatus3Code" on page 177


Presence: [0..*]


The StsRsnInf block contains the following elements (see datatype "StatusReasonInformation9" onpage 126 for details)



Page


Reason <Rsn> [0..1] 127

AdditionalInformation <AddtlInf> [0..*] 127

5.55.6 NumberOfTransactionsPerStatusXML Tag: NbOfTxsPerSts

Presence: [0..*]

Definition: Detailed information on the number of transactions for each identical transaction status.

Usage Guideline


The NbOfTxsPerSts block contains the following elements (see datatype "NumberOfTransaction-sPerStatus3" on page 73 for details)



Page





• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/NumberOfTransaction-sPerStatus) is removed.

5.55.7 TransactionInformationAndStatusXML Tag: TxInfAndSts

Presence: [0..*]

Definition: Provides information on the original transactions to which the status report message refers.

The TxInfAndSts block contains the following elements (see datatype "PaymentTransaction68__1" onpage 100 for details)



Page

StatusIdentification <StsId> [0..1] 100

OriginalInstructionIdentification <OrgnlInstrId> [0..1] 100

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] ! 101

TransactionStatus <TxSts> [0..1] 101


ChargesInformation <ChrgsInf> [0..*] 102

AcceptanceDateTime <AccptncDtTm> [0..1] 102

AccountServicerReference <AcctSvcrRef> [0..1] 103

ClearingSystemReference <ClrSysRef> [0..1] 103

OriginalTransactionReference <OrgnlTxRef> [0..1] 103


5.56 OriginalTransactionReference22__1Definition: Key elements used to refer the original transaction.

Message Components

30 January 2017 83



Page

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] 83


InterbankSettlementDate <IntrBkSttlmDt> [0..1] 84

RequestedCollectionDate <ReqdColltnDt> [0..1] 84

RequestedExecutionDate <ReqdExctnDt> [0..1] 84

CreditorSchemeIdentification <CdtrSchmeId> [0..1] 85

SettlementInformation <SttlmInf> [0..1] 85

PaymentTypeInformation <PmtTpInf> [0..1] 86

PaymentMethod <PmtMtd> [0..1] 87

MandateRelatedInformation <MndtRltdInf> [0..1] 87

RemittanceInformation <RmtInf> [0..1] 88

UltimateDebtor <UltmtDbtr> [0..1] 88

Debtor <Dbtr> [0..1] 89

DebtorAccount <DbtrAcct> [0..1] 89


DebtorAgentAccount <DbtrAgtAcct> [0..1] 90


CreditorAgentAccount <CdtrAgtAcct> [0..1] 91

Creditor <Cdtr> [0..1] 91

CreditorAccount <CdtrAcct> [0..1] 91

UltimateCreditor <UltmtCdtr> [0..1] 92

Used in element(s)

"OriginalTransactionReference" on page 103

5.56.1 InterbankSettlementAmountXML Tag: IntrBkSttlmAmt

Presence: [0..1]

Definition: Amount of money moved between the instructing agent and the instructed agent.


Usage Guideline



• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/InterbankSettlementAmount) is removed.


Presence: [0..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.

The Amt block contains the following elements (see datatype "AmountType4Choice" on page 20 fordetails)



Page

InstructedAmount <InstdAmt> {Or [1..1] 20

EquivalentAmount <EqvtAmt> Or} [1..1] 21

5.56.3 InterbankSettlementDateXML Tag: IntrBkSttlmDt

Presence: [0..1]

Definition: Date on which the amount of money ceases to be available to the agent that owes it andwhen the amount of money becomes available to the agent to which it is due.



• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/InterbankSettlementDate) is removed.

5.56.4 RequestedCollectionDateXML Tag: ReqdColltnDt

Presence: [0..1]

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


5.56.5 RequestedExecutionDateXML Tag: ReqdExctnDt

Presence: [0..1]

Message Components

30 January 2017 85

Definition: Date at which the initiating party requests the clearing agent to process the payment.

Usage: This is the date on which the debtor's account is to be debited. If payment by cheque, the datewhen the cheque must be generated by the bank.


5.56.6 CreditorSchemeIdentificationXML Tag: CdtrSchmeId

Presence: [0..1]

Definition: Credit party that signs the mandate.

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



Page

Name <Nm> [0..1] 95






• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/CreditorSchemeIdentification) is removed.

5.56.7 SettlementInformationXML Tag: SttlmInf

Presence: [0..1]

Definition: Specifies the details on how the settlement of the original transaction(s) between the instruct-ing agent and the instructed agent was completed.

Usage Guideline


The SttlmInf block contains the following elements (see datatype "SettlementInstruction4" onpage 119 for details)



Page

SettlementMethod <SttlmMtd> [1..1] 122

SettlementAccount <SttlmAcct> [0..1] 122

ClearingSystem <ClrSys> [0..1] 122

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] 123

InstructingReimbursementAgentAc-count

<InstgRmbrsmntAgtAcct> [0..1] 123

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] 123

InstructedReimbursementAgentAc-count

<InstdRmbrsmntAgtAcct> [0..1] 124

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] 124

ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> [0..1] 125


• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/SettlementInformation) is removed.

5.56.8 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 "PaymentTypeInformation25" onpage 105 for details)



Page

InstructionPriority <InstrPrty> [0..1] 105

ClearingChannel <ClrChanl> [0..1] 105

ServiceLevel <SvcLvl> [0..1] 106

LocalInstrument <LclInstrm> [0..1] 106

SequenceType <SeqTp> [0..1] 106

CategoryPurpose <CtgyPurp> [0..1] 106

Message Components

30 January 2017 87


• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/PaymentTypeInformation) is removed.

5.56.9 PaymentMethodXML Tag: PmtMtd

Presence: [0..1]

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

Datatype: "PaymentMethod4Code" on page 170


• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/PaymentMethod) is removed.

5.56.10 MandateRelatedInformationXML Tag: MndtRltdInf

Presence: [0..1]

Definition: Provides further details of the mandate signed between the creditor and the debtor.

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



Page

MandateIdentification <MndtId> [0..1] 70

DateOfSignature <DtOfSgntr> [0..1] 70

AmendmentIndicator <AmdmntInd> [0..1] 70

AmendmentInformationDetails <AmdmntInfDtls> [0..1] 70

ElectronicSignature <ElctrncSgntr> [0..1] 71

FirstCollectionDate <FrstColltnDt> [0..1] 71

FinalCollectionDate <FnlColltnDt> [0..1] 71

Frequency <Frqcy> [0..1] 71


Usage Guideline



• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/MandateRelatedInformation) is removed.

5.56.11 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 117 for details)



Page

Unstructured <Ustrd> [0..*] 118

Structured <Strd> [0..*] 118


• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/RemittanceInformation) is removed.

5.56.12 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 94 for details)



Page

Name <Nm> [0..1] 95





Message Components

30 January 2017 89

5.56.13 DebtorXML Tag: Dbtr

Presence: [0..1]

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

The Dbtr block contains the following elements (see datatype "PartyIdentification43" on page 94 fordetails)



Page

Name <Nm> [0..1] 95





5.56.14 DebtorAccountXML Tag: DbtrAcct

Presence: [0..1]

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

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



Page


Type <Tp> [0..1] 27


Name <Nm> [0..1] 28

5.56.15 DebtorAgentXML Tag: DbtrAgt

Presence: [0..1]

Definition: Financial institution servicing an account for the debtor.

Usage Guideline


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



Page



5.56.16 DebtorAgentAccountXML Tag: DbtrAgtAcct

Presence: [0..1]

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

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



Page


Type <Tp> [0..1] 26


Name <Nm> [0..1] 26


• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/DebtorAgentAccount) is removed.

5.56.17 CreditorAgentXML Tag: CdtrAgt

Presence: [0..1]

Definition: Financial institution servicing an account for the creditor.

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



Page



Message Components

30 January 2017 91

5.56.18 CreditorAgentAccountXML Tag: CdtrAgtAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the creditor agent at its servicing agent to whicha credit entry will be made as a result of the payment transaction.

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



Page


Type <Tp> [0..1] 26


Name <Nm> [0..1] 26


• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/CreditorAgentAccount) is removed.

5.56.19 CreditorXML Tag: Cdtr

Presence: [0..1]

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

The Cdtr block contains the following elements (see datatype "PartyIdentification43" on page 94 fordetails)



Page

Name <Nm> [0..1] 95





5.56.20 CreditorAccountXML Tag: CdtrAcct

Presence: [0..1]

Usage Guideline


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 27for details)



Page


Type <Tp> [0..1] 27


Name <Nm> [0..1] 28

5.56.21 UltimateCreditorXML Tag: UltmtCdtr

Presence: [0..1]

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

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



Page

Name <Nm> [0..1] 95





5.57 Party11ChoiceDefinition: Nature or use of the account.



Page

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

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

Used in element(s)


Message Components

30 January 2017 93

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" onpage 74 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 107for details)



Page

DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] 107

Other <Othr> [0..*] 107

5.58 Party11Choice__1Definition: Nature or use of the account.



Page



Used in element(s)


5.58.1 OrganisationIdentificationXML Tag: OrgId

Usage Guideline


Presence: [1..1]

Definition: Unique and unambiguous way to identify an organisation.

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



Page



5.58.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 107for details)



Page


Other <Othr> [0..*] 107


• This element(pain.002.001.07/OriginalGroupInformationAndStatus/StatusReasonInforma-tion/Originator/Identification/PrivateIdentification) is removed.

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



Page

Name <Nm> [0..1] 95





Message Components

30 January 2017 95

Used in element(s)

"Creditor" on page 91, "CreditorSchemeIdentification" on page 85, "Debtor" on page 89,"Garnishee" on page 55, "GarnishmentAdministrator" on page 56, "Invoicee" on page 131,"Invoicer" on page 131, "OriginalCreditorSchemeIdentification" on page 16, "OriginalDebtor"on page 18, "Originator" on page 126, "UltimateCreditor" on page 92, "UltimateDebtor" onpage 88


Presence: [0..1]




• on pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformationAndSta-tus/OriginalTransactionReference/Debtor/Name

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


Presence: [0..1]





Page











Usage Guideline



• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/Debtor/PostalAddress) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/Creditor/PostalAddress) is removed.


Presence: [0..1]

Definition: Unique and unambiguous identification of a party.

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



Page




• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/Creditor/Identification) is removed.

5.59.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.



• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/Debtor/CountryOfResidence) is removed.

• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/Creditor/CountryOfResidence) is removed.

5.59.5 ContactDetailsXML Tag: CtctDtls

Presence: [0..1]

Message Components

30 January 2017 97

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

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



Page


Name <Nm> [0..1] 35







• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalTransactionReference/Creditor/ContactDetails) is removed.

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



Page

Name <Nm> [0..1] 97





Used in element(s)

"InitiatingParty" on page 66, "Originator" on page 128


Presence: [0..1]


Usage Guideline




Presence: [0..1]





Page












• This element(pain.002.001.07/OriginalGroupInformationAndStatus/StatusReasonInforma-tion/Originator/PostalAddress) is removed.


Presence: [0..1]

Definition: Unique and unambiguous identification of a party.

Message Components

30 January 2017 99

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



Page



5.60.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.



• This element(pain.002.001.07/OriginalGroupInformationAndStatus/StatusReasonInforma-tion/Originator/CountryOfResidence) is removed.

5.60.5 ContactDetailsXML Tag: CtctDtls

Presence: [0..1]

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

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



Page


Name <Nm> [0..1] 35






Usage Guideline



• This element(pain.002.001.07/OriginalGroupInformationAndStatus/StatusReasonInforma-tion/Originator/ContactDetails) is removed.

5.61 PaymentTransaction68__1Definition: Provides further details on the original transactions, to which the status report messagerefers.



Page

StatusIdentification <StsId> [0..1] 100

OriginalInstructionIdentification <OrgnlInstrId> [0..1] 100

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] ! 101

TransactionStatus <TxSts> [0..1] 101


ChargesInformation <ChrgsInf> [0..*] 102

AcceptanceDateTime <AccptncDtTm> [0..1] 102

AccountServicerReference <AcctSvcrRef> [0..1] 103

ClearingSystemReference <ClrSysRef> [0..1] 103

OriginalTransactionReference <OrgnlTxRef> [0..1] 103


Used in element(s)

"TransactionInformationAndStatus" on page 82

5.61.1 StatusIdentificationXML Tag: StsId

Presence: [0..1]

Definition: Unique identification, as assigned by an instructing party for an instructed party, to unam-biguously identify the reported status.

Usage: The instructing party is the party sending the status message and not the party that sent theoriginal instruction that is being reported on.


5.61.2 OriginalInstructionIdentificationXML Tag: OrgnlInstrId

Message Components

30 January 2017 101

Presence: [0..1]

Definition: Unique identification, as assigned by the original instructing party for the original instructedparty, to unambiguously identify the original instruction.



• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/OriginalInstructionIdentification) is removed.

5.61.3 OriginalEndToEndIdentificationXML Tag: OrgnlEndToEndId

Presence: [0..1]

Definition: Unique identification, as assigned by the original initiating party, to unambiguously identifythe original transaction.



• on pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformationAndSta-tus/OriginalEndToEndIdentification

– CPA_End_to_End_Identification:

This element shall contain max 19 text for use in AFT.

5.61.4 TransactionStatusXML Tag: TxSts

Presence: [0..1]

Definition: Specifies the status of a transaction, in a coded form.

Datatype: "TransactionIndividualStatus3Code" on page 180


Presence: [0..*]


Usage Guideline


The StsRsnInf block contains the following elements (see datatype "StatusReasonInformation9" onpage 126 for details)



Page


Reason <Rsn> [0..1] 127


5.61.6 ChargesInformationXML Tag: ChrgsInf

Presence: [0..*]

Definition: Provides information on the charges related to the processing of the rejection of the instruc-tion.

Usage: This is passed on for information purposes only. Settlement of the charges will be done sepa-rately.

The ChrgsInf block contains the following elements (see datatype "Charges2" on page 30 for de-tails)



Page


Agent <Agt> [1..1] 30


• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/ChargesInformation) is removed.

5.61.7 AcceptanceDateTimeXML Tag: AccptncDtTm

Presence: [0..1]

Definition: Point in time when the payment order from the initiating party meets the processing condi-tions of the account servicing agent. This means that the account servicing agent has received the pay-ment order and has applied checks such as authorisation, availability of funds.


Message Components

30 January 2017 103


• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/AcceptanceDateTime) is removed.

5.61.8 AccountServicerReferenceXML Tag: AcctSvcrRef

Presence: [0..1]

Definition: Unique reference, as assigned by the account servicing institution, to unambiguously identifythe instruction.



• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/AccountServicerReference) is removed.

5.61.9 ClearingSystemReferenceXML Tag: ClrSysRef

Presence: [0..1]

Definition: Unique reference, as assigned by a clearing system, to unambiguously identify the instruc-tion.



• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/ClearingSystemReference) is removed.

5.61.10 OriginalTransactionReferenceXML Tag: OrgnlTxRef

Presence: [0..1]

Definition: Key elements used to identify the original transaction that is being referred to.

Usage Guideline


The OrgnlTxRef block contains the following elements (see datatype "OriginalTransactionRefer-ence22__1" on page 82 for details)



Page

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] 83


InterbankSettlementDate <IntrBkSttlmDt> [0..1] 84

RequestedCollectionDate <ReqdColltnDt> [0..1] 84

RequestedExecutionDate <ReqdExctnDt> [0..1] 84

CreditorSchemeIdentification <CdtrSchmeId> [0..1] 85

SettlementInformation <SttlmInf> [0..1] 85

PaymentTypeInformation <PmtTpInf> [0..1] 86

PaymentMethod <PmtMtd> [0..1] 87

MandateRelatedInformation <MndtRltdInf> [0..1] 87

RemittanceInformation <RmtInf> [0..1] 88



DebtorAccount <DbtrAcct> [0..1] 89


DebtorAgentAccount <DbtrAgtAcct> [0..1] 90


CreditorAgentAccount <CdtrAgtAcct> [0..1] 91


CreditorAccount <CdtrAcct> [0..1] 91

UltimateCreditor <UltmtCdtr> [0..1] 92

5.61.11 SupplementaryDataXML Tag: SplmtryData

Presence: [0..*]

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

Message Components

30 January 2017 105

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



Page




• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/TransactionInformatio-nAndStatus/SupplementaryData) is removed.

5.62 PaymentTypeInformation25Definition: Set of elements used to provide further details of the type of payment.



Page

InstructionPriority <InstrPrty> [0..1] 105

ClearingChannel <ClrChanl> [0..1] 105

ServiceLevel <SvcLvl> [0..1] 106

LocalInstrument <LclInstrm> [0..1] 106

SequenceType <SeqTp> [0..1] 106

CategoryPurpose <CtgyPurp> [0..1] 106

Used in element(s)

"PaymentTypeInformation" on page 86

5.62.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 172

5.62.2 ClearingChannelXML Tag: ClrChanl

Presence: [0..1]

Usage Guideline


Definition: Specifies the clearing channel to be used to process the payment instruction.

Datatype: "ClearingChannel2Code" on page 152

5.62.3 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 119for details)



Page

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


5.62.4 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 68 for details)



Page

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


5.62.5 SequenceTypeXML Tag: SeqTp

Presence: [0..1]

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

Datatype: "SequenceType3Code" on page 173

5.62.6 CategoryPurposeXML Tag: CtgyPurp

Presence: [0..1]

Message Components

30 January 2017 107

Definition: 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.

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



Page

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


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



Page


Other <Othr> [0..*] 107

Used in element(s)

"PrivateIdentification" on page 93, "PrivateIdentification" on page 94

5.63.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 39 for details)



Page

BirthDate <BirthDt> [1..1] 39

ProvinceOfBirth <PrvcOfBirth> [0..1] 39

CityOfBirth <CityOfBirth> [1..1] 39

CountryOfBirth <CtryOfBirth> [1..1] 39


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 64 for details)



Page




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



Page

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


Used in element(s)

"SchemeName" on page 65


Presence: [1..1]


Datatype: "ExternalPersonIdentification1Code" on page 161


Presence: [1..1]



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

Message Components

30 January 2017 109



Page











Used in element(s)

"PostalAddress" on page 49, "PostalAddress" on page 24, "PostalAddress" on page 95,"PostalAddress" on page 98, "PostalAddress" on page 51

5.65.1 AddressTypeXML Tag: AdrTp

Presence: [0..1]

Definition: Identifies the nature of the postal address.

Datatype: "AddressType2Code" on page 149

5.65.2 DepartmentXML Tag: Dept

Presence: [0..1]

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


5.65.3 SubDepartmentXML Tag: SubDept

Presence: [0..1]

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


5.65.4 StreetNameXML Tag: StrtNm

Usage Guideline


Presence: [0..1]

Definition: Name of a street or thoroughfare.


5.65.5 BuildingNumberXML Tag: BldgNb

Presence: [0..1]

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


5.65.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.65.7 TownNameXML Tag: TwnNm

Presence: [0..1]

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


5.65.8 CountrySubDivisionXML Tag: CtrySubDvsn

Presence: [0..1]

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


5.65.9 CountryXML Tag: Ctry

Presence: [0..1]

Definition: Nation with its own government.


5.65.10 AddressLineXML Tag: AdrLine

Presence: [0..7]

Message Components

30 January 2017 111

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


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



Page

Type <Tp> [0..1] 111

Number <Nb> [0..1] 111


LineDetails <LineDtls> [0..*] 112

Used in element(s)

"ReferredDocumentInformation" on page 130


Presence: [0..1]

Definition: Specifies the type of referred document.

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



Page



5.66.2 NumberXML Tag: Nb

Presence: [0..1]

Definition: Unique and unambiguous identification of the referred document.


5.66.3 RelatedDateXML Tag: RltdDt

Presence: [0..1]

Usage Guideline


Definition: Date associated with the referred document.


5.66.4 LineDetailsXML Tag: LineDtls

Presence: [0..*]

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 44 for details)



Page

Identification <Id> [1..*] 44

Description <Desc> [0..1] 44


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



Page

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


Used in element(s)



Presence: [1..1]

Definition: Document type in a coded form.

Datatype: "DocumentType6Code" on page 154


Presence: [1..1]

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


Message Components

30 January 2017 113

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



Page



Used in element(s)

"Type" on page 111


Presence: [1..1]

Definition: Provides the type details of the referred document.

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



Page

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



Presence: [0..1]

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


5.69 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.

Usage Guideline




Page







Used in element(s)

"ReferredDocumentAmount" on page 130

5.69.1 DuePayableAmountXML Tag: DuePyblAmt

Presence: [0..1]

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


5.69.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 40 for details)



Page

Type <Tp> [0..1] 40


5.69.3 CreditNoteAmountXML Tag: CdtNoteAmt

Presence: [0..1]

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


Message Components

30 January 2017 115

5.69.4 TaxAmountXML Tag: TaxAmt

Presence: [0..*]

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

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



Page

Type <Tp> [0..1] 135

Amount <Amt> [1..1] 136

5.69.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 42 for details)



Page






Presence: [0..1]

Definition: Amount of money remitted for the referred document.


5.70 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.

Usage Guideline




Page







Used in element(s)

"Amount" on page 44

5.70.1 DuePayableAmountXML Tag: DuePyblAmt

Presence: [0..1]

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


5.70.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 40 for details)



Page

Type <Tp> [0..1] 40


5.70.3 CreditNoteAmountXML Tag: CdtNoteAmt

Presence: [0..1]

Definition: Amount of a credit note.


Message Components

30 January 2017 117


Presence: [0..*]

Definition: Amount of the tax.

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



Page

Type <Tp> [0..1] 135

Amount <Amt> [1..1] 136

5.70.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 42 for details)



Page






Presence: [0..1]

Definition: Amount of money remitted.


5.71 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.

Usage Guideline




Page

Unstructured <Ustrd> [0..*] 118

Structured <Strd> [0..*] 118

Used in element(s)

"RemittanceInformation" on page 88

5.71.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.


5.71.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.

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



Page

ReferredDocumentInformation <RfrdDocInf> [0..*] 130

ReferredDocumentAmount <RfrdDocAmt> [0..1] 130

CreditorReferenceInformation <CdtrRefInf> [0..1] 130

Invoicer <Invcr> [0..1] 131

Invoicee <Invcee> [0..1] 131

TaxRemittance <TaxRmt> [0..1] 132

GarnishmentRemittance <GrnshmtRmt> [0..1] 132

AdditionalRemittanceInformation <AddtlRmtInf> [0..3] 133

Message Components

30 January 2017 119

5.72 ServiceLevel8ChoiceDefinition: Specifies the service level of the transaction.



Page

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


Used in element(s)

"ServiceLevel" on page 106


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 161


Presence: [1..1]

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


5.73 SettlementInstruction4Definition: Provides further details on the settlement of the instruction.

Usage Guideline




Page

SettlementMethod <SttlmMtd> [1..1] 122

SettlementAccount <SttlmAcct> [0..1] 122

ClearingSystem <ClrSys> [0..1] 122

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] 123

InstructingReimbursementAgentAc-count

<InstgRmbrsmntAgtAcct> [0..1] 123

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] 123

InstructedReimbursementAgentAc-count

<InstdRmbrsmntAgtAcct> [0..1] 124

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] 124

ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> [0..1] 125

Rules

R13 ThirdReimbursementAgentRule ✓

If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and Instructe-dReimbursementAgent must both be present.

Error handling:



– Error Text: Invalid message content for third reimbursement agent.

R14 SettlementMethodAgentRule ✓

If SettlementMethod is equal to INDA or INGA, then ReimbursementAgent(s) and ClearingSys-tem are not allowed.

Error handling:



– Error Text: Invalid message content for settlement method INGA or INDA.

R15 SettlementMethodCoverRule ✓

If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not al-lowed.

Error handling:



Message Components

30 January 2017 121

– Error Text: Invalid message content for cover settlement method with settlement accountand clearing system.

R16 SettlementMethodCoverAgentRule ✓

If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or InstructingRe-imbursementAgent must be present.

Error handling:



– Error Text: Invalid message content for cover settlement method and reimbursement agents.

R17 SettlementMethodClearingRule ✓

If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s)are not allowed.

Error handling:



– Error Text: Invalid message content for settlement method CLRG.

R18 InstructingReimbursementAgentAccountRule ✓

If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgentmust be present.

Error handling:



– Error Text: Invalid message content for instructing reimbursement agent account.

R19 InstructedReimbursementAgentAccountRule ✓

If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgentmust be present.

Error handling:



– Error Text: Invalid message content for instructed reimbursement agent account.

R20 ThirdReimbursementAgentAccountRule ✓

If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must bepresent.

Error handling:



Usage Guideline


– Error Text: Invalid message content for third reimbursement agent account.

Used in element(s)

"SettlementInformation" on page 85

5.73.1 SettlementMethodXML Tag: SttlmMtd

Presence: [1..1]

Definition: Method used to settle the (batch of) payment instructions.

Datatype: "SettlementMethod1Code" on page 174

5.73.2 SettlementAccountXML Tag: SttlmAcct

Presence: [0..1]

Definition: A specific purpose account used to post debit and credit entries as a result of the transaction.

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



Page


Type <Tp> [0..1] 26


Name <Nm> [0..1] 26

5.73.3 ClearingSystemXML Tag: ClrSys

Presence: [0..1]


The ClrSys block contains the following elements (see datatype "ClearingSystemIdentification3Choice"on page 31 for details)



Page

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


Message Components

30 January 2017 123

5.73.4 InstructingReimbursementAgentXML Tag: InstgRmbrsmntAgt

Presence: [0..1]

Definition: Agent through which the instructing agent will reimburse the instructed agent.

Usage: If InstructingAgent and InstructedAgent have the same reimbursement agent, then only Instruct-ingReimbursementAgent must be used.

The InstgRmbrsmntAgt block contains the following elements (see datatype "BranchAndFinancialIn-stitutionIdentification5" on page 21 for details)



Page



5.73.5 InstructingReimbursementAgentAccountXML Tag: InstgRmbrsmntAgtAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the instructing reimbursement agent account atits servicing agent in the payment chain.

The InstgRmbrsmntAgtAcct block contains the following elements (see datatype "CashAccount24" onpage 25 for details)



Page


Type <Tp> [0..1] 26


Name <Nm> [0..1] 26

5.73.6 InstructedReimbursementAgentXML Tag: InstdRmbrsmntAgt

Presence: [0..1]

Definition: Agent at which the instructed agent will be reimbursed.

Usage: If InstructedReimbursementAgent contains a branch of the InstructedAgent, then the party in In-structedAgent will claim reimbursement from that branch/will be paid by that branch.

Usage: If InstructingAgent and InstructedAgent have the same reimbursement agent, then only Instruct-ingReimbursementAgent must be used.

Usage Guideline


The InstdRmbrsmntAgt block contains the following elements (see datatype "BranchAndFinancialIn-stitutionIdentification5" on page 21 for details)



Page



5.73.7 InstructedReimbursementAgentAccountXML Tag: InstdRmbrsmntAgtAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the instructed reimbursement agent account atits servicing agent in the payment chain.

The InstdRmbrsmntAgtAcct block contains the following elements (see datatype "CashAccount24" onpage 25 for details)



Page


Type <Tp> [0..1] 26


Name <Nm> [0..1] 26

5.73.8 ThirdReimbursementAgentXML Tag: ThrdRmbrsmntAgt

Presence: [0..1]

Definition: Agent at which the instructed agent will be reimbursed.

Usage: If ThirdReimbursementAgent contains a branch of the InstructedAgent, then the party in In-structedAgent will claim reimbursement from that branch/will be paid by that branch.

The ThrdRmbrsmntAgt block contains the following elements (see datatype "BranchAndFinancialInsti-tutionIdentification5" on page 21 for details)



Page



Message Components

30 January 2017 125

5.73.9 ThirdReimbursementAgentAccountXML Tag: ThrdRmbrsmntAgtAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the third reimbursement agent account at itsservicing agent in the payment chain.

The ThrdRmbrsmntAgtAcct block contains the following elements (see datatype "CashAccount24" onpage 25 for details)



Page


Type <Tp> [0..1] 26


Name <Nm> [0..1] 26

5.74 StatusReason6ChoiceDefinition: Specifies the reason for the status of the transaction.



Page

Code <Cd> {Or [1..1] ! 125


Used in element(s)

"Reason" on page 127, "Reason" on page 128


Presence: [1..1]

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

Datatype: "ExternalStatusReason1Code" on page 162

Usage Guideline



• on pain.002.001.07/OriginalGroupInformationAndStatus/StatusReasonInformation/Rea-son/Code

Single value: NARR


Presence: [1..1]

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


5.75 StatusReasonInformation9Definition: Set of elements used to provide information on the status reason of the transaction.



Page


Reason <Rsn> [0..1] 127


Rules

R21 StatusReasonRule ✓

If Reason/Code is equal to NARR, then AddititionalInformation must be present.

Error handling:




Used in element(s)

"StatusReasonInformation" on page 81, "StatusReasonInformation" on page 101

5.75.1 OriginatorXML Tag: Orgtr

Presence: [0..1]

Definition: Party that issues the status.

Message Components

30 January 2017 127

The Orgtr block contains the following elements (see datatype "PartyIdentification43" on page 94 fordetails)



Page

Name <Nm> [0..1] 95






• This element(pain.002.001.07/OriginalPaymentInformationAndStatus/StatusReasonInforma-tion/Originator) is removed.


Presence: [0..1]

Definition: Specifies the reason for the status report.

The Rsn block contains the following elements (see datatype "StatusReason6Choice" on page 125for details)



Page

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



Presence: [0..*]

Definition: Further details on the status reason.

Usage: Additional information can be used for several purposes such as the reporting of repaired infor-mation.


5.76 StatusReasonInformation9__1Definition: Set of elements used to provide information on the status reason of the transaction.

Usage Guideline




Page


Reason <Rsn> [0..1] 128

AdditionalInformation <AddtlInf> [0..*] R[0..6] 129

Rules

R25 StatusReasonRule ✓

If Reason/Code is equal to NARR, then AddititionalInformation must be present.

Error handling:




Used in element(s)

"StatusReasonInformation" on page 78

5.76.1 OriginatorXML Tag: Orgtr

Presence: [0..1]

Definition: Party that issues the status.

The Orgtr block contains the following elements (see datatype "PartyIdentification43__1" onpage 97 for details)



Page

Name <Nm> [0..1] 97






Presence: [0..1]

Definition: Specifies the reason for the status report.

Message Components

30 January 2017 129

The Rsn block contains the following elements (see datatype "StatusReason6Choice" on page 125for details)



Page

Code <Cd> {Or [1..1] ! 125



Presence: [0..*]

Definition: Further details on the status reason.

Usage: Additional information can be used for several purposes such as the reporting of repaired infor-mation.



• on pain.002.001.07/OriginalGroupInformationAndStatus/StatusReasonInformation/Addition-alInformation

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

5.77 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..*] 130

ReferredDocumentAmount <RfrdDocAmt> [0..1] 130

CreditorReferenceInformation <CdtrRefInf> [0..1] 130

Invoicer <Invcr> [0..1] 131

Invoicee <Invcee> [0..1] 131

TaxRemittance <TaxRmt> [0..1] 132

GarnishmentRemittance <GrnshmtRmt> [0..1] 132

AdditionalRemittanceInformation <AddtlRmtInf> [0..3] 133

Usage Guideline


Used in element(s)

"Structured" on page 118

5.77.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 111 for details)



Page

Type <Tp> [0..1] 111

Number <Nb> [0..1] 111


LineDetails <LineDtls> [0..*] 112

5.77.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 113 for details)



Page







5.77.3 CreditorReferenceInformationXML Tag: CdtrRefInf

Presence: [0..1]

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

Message Components

30 January 2017 131

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



Page

Type <Tp> [0..1] 37

Reference <Ref> [0..1] 37

5.77.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 94 fordetails)



Page

Name <Nm> [0..1] 95





5.77.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.

Usage Guideline


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



Page

Name <Nm> [0..1] 95





5.77.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 137 fordetails)



Page




AdministrationZone <AdmstnZone> [0..1] 139


Method <Mtd> [0..1] 139

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] 140

TotalTaxAmount <TtlTaxAmt> [0..1] 140

Date <Dt> [0..1] 140

SequenceNumber <SeqNb> [0..1] 140

Record <Rcrd> [0..*] 140

5.77.7 GarnishmentRemittanceXML Tag: GrnshmtRmt

Presence: [0..1]

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

Message Components

30 January 2017 133

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



Page

Type <Tp> [1..1] 55

Garnishee <Grnshee> [0..1] 55

GarnishmentAdministrator <GrnshmtAdmstr> [0..1] 56


Date <Dt> [0..1] 56


FamilyMedicalInsuranceIndicator <FmlyMdclInsrncInd> [0..1] 57

EmployeeTerminationIndicator <MplyeeTermntnInd> [0..1] 57

5.77.8 AdditionalRemittanceInformationXML Tag: AddtlRmtInf

Presence: [0..3]

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


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



Page



Rules

R11 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.

Error handling: Undefined

Used in element(s)

"SupplementaryData" on page 12, "SupplementaryData" on page 104

Usage Guideline


5.78.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.78.2 EnvelopeXML Tag: Envlp

Presence: [1..1]

Definition: Technical element wrapping the supplementary data.

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



Page

Rate <Rate> [0..1] 134

TaxableBaseAmount <TaxblBaseAmt> [0..1] 134

TotalAmount <TtlAmt> [0..1] 135

Details <Dtls> [0..*] 135

Used in element(s)

"TaxAmount" on page 146

5.79.1 RateXML Tag: Rate

Presence: [0..1]

Definition: Rate used to calculate the tax.

Datatype: "PercentageRate" on page 172

5.79.2 TaxableBaseAmountXML Tag: TaxblBaseAmt

Presence: [0..1]

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


Message Components

30 January 2017 135

5.79.3 TotalAmountXML Tag: TtlAmt

Presence: [0..1]

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


5.79.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 146 fordetails)



Page

Period <Prd> [0..1] 147

Amount <Amt> [1..1] 147

5.80 TaxAmountAndType1Definition: Specifies the amount with a specific type.



Page

Type <Tp> [0..1] 135

Amount <Amt> [1..1] 136

Used in element(s)

"TaxAmount" on page 115, "TaxAmount" on page 117


Presence: [0..1]

Definition: Specifies the type of the amount.

Usage Guideline


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



Page

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



Presence: [1..1]

Definition: Amount of money, which has been typed.


5.81 TaxAmountType1ChoiceDefinition: Specifies the amount type.



Page

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


Used in element(s)

"Type" on page 135


Presence: [1..1]

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

Datatype: "ExternalTaxAmountType1Code" on page 162


Presence: [1..1]

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


Message Components

30 January 2017 137

5.82 TaxAuthorisation1Definition: Details of the authorised tax paying party.



Page

Title <Titl> [0..1] 137

Name <Nm> [0..1] 137

Used in element(s)

"Authorisation" on page 143

5.82.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.83 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] 139


Method <Mtd> [0..1] 139

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] 140

TotalTaxAmount <TtlTaxAmt> [0..1] 140

Date <Dt> [0..1] 140

SequenceNumber <SeqNb> [0..1] 140

Record <Rcrd> [0..*] 140

Used in element(s)

"TaxRemittance" on page 132

5.83.1 CreditorXML Tag: Cdtr

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 141 for details)



Page

TaxIdentification <TaxId> [0..1] 141

RegistrationIdentification <RegnId> [0..1] 141

TaxType <TaxTp> [0..1] 142

5.83.2 DebtorXML Tag: Dbtr

Presence: [0..1]

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

Message Components

30 January 2017 139

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



Page




Authorisation <Authstn> [0..1] 143

5.83.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 142 for de-tails)



Page





5.83.4 AdministrationZoneXML Tag: AdmstnZone

Presence: [0..1]

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


5.83.5 ReferenceNumberXML Tag: RefNb

Presence: [0..1]

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


5.83.6 MethodXML Tag: Mtd

Usage Guideline


Presence: [0..1]

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


5.83.7 TotalTaxableBaseAmountXML Tag: TtlTaxblBaseAmt

Presence: [0..1]

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


5.83.8 TotalTaxAmountXML Tag: TtlTaxAmt

Presence: [0..1]

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


5.83.9 DateXML Tag: Dt

Presence: [0..1]

Definition: Date by which tax is due.


5.83.10 SequenceNumberXML Tag: SeqNb

Presence: [0..1]

Definition: Sequential number of the tax report.

Datatype: "Number" on page 169

5.83.11 RecordXML Tag: Rcrd

Presence: [0..*]

Definition: Record of tax details.

Message Components

30 January 2017 141

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



Page

Type <Tp> [0..1] 144

Category <Ctgy> [0..1] 145

CategoryDetails <CtgyDtls> [0..1] 145

DebtorStatus <DbtrSts> [0..1] 145

CertificateIdentification <CertId> [0..1] 145

FormsCode <FrmsCd> [0..1] 145

Period <Prd> [0..1] 145

TaxAmount <TaxAmt> [0..1] 146


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



Page




Used in element(s)

"Creditor" on page 138

5.84.1 TaxIdentificationXML Tag: TaxId

Presence: [0..1]

Definition: Tax identification number of the creditor.


5.84.2 RegistrationIdentificationXML Tag: RegnId

Presence: [0..1]

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

Usage Guideline



5.84.3 TaxTypeXML Tag: TaxTp

Presence: [0..1]

Definition: Type of tax payer.


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



Page





Used in element(s)

"Debtor" on page 138, "UltimateDebtor" on page 139

5.85.1 TaxIdentificationXML Tag: TaxId

Presence: [0..1]

Definition: Tax identification number of the debtor.


5.85.2 RegistrationIdentificationXML Tag: RegnId

Presence: [0..1]

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


5.85.3 TaxTypeXML Tag: TaxTp

Presence: [0..1]

Definition: Type of tax payer.


Message Components

30 January 2017 143

5.85.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 137for details)



Page

Title <Titl> [0..1] 137

Name <Nm> [0..1] 137

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



Page

Year <Yr> [0..1] 143

Type <Tp> [0..1] 143

FromToDate <FrToDt> [0..1] 144

Used in element(s)

"Period" on page 147, "Period" on page 145

5.86.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 175

Usage Guideline


5.86.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 40 fordetails)



Page

FromDate <FrDt> [1..1] 40

ToDate <ToDt> [1..1] 40

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



Page

Type <Tp> [0..1] 144

Category <Ctgy> [0..1] 145

CategoryDetails <CtgyDtls> [0..1] 145

DebtorStatus <DbtrSts> [0..1] 145

CertificateIdentification <CertId> [0..1] 145

FormsCode <FrmsCd> [0..1] 145

Period <Prd> [0..1] 145

TaxAmount <TaxAmt> [0..1] 146


Used in element(s)

"Record" on page 140


Presence: [0..1]

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


Message Components

30 January 2017 145

5.87.2 CategoryXML Tag: Ctgy

Presence: [0..1]

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


5.87.3 CategoryDetailsXML Tag: CtgyDtls

Presence: [0..1]

Definition: Provides further details of the category tax code.


5.87.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.87.5 CertificateIdentificationXML Tag: CertId

Presence: [0..1]

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


5.87.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 143 for details)



Page

Year <Yr> [0..1] 143

Type <Tp> [0..1] 143



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 134 for de-tails)



Page

Rate <Rate> [0..1] 134

TaxableBaseAmount <TaxblBaseAmt> [0..1] 134

TotalAmount <TtlAmt> [0..1] 135

Details <Dtls> [0..*] 135


Presence: [0..1]

Definition: Further details of the tax record.


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



Page

Period <Prd> [0..1] 147

Amount <Amt> [1..1] 147

Message Components

30 January 2017 147

Used in element(s)

"Details" on page 135


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 143 for details)



Page

Year <Yr> [0..1] 143

Type <Tp> [0..1] 143



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 CustomerPaymentSta-tusReportV07 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 148

Format

minInclusive 0

totalDigits 18

fractionDigits 5

Rules

R12 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 42, "Amount" on page 147, "Amount" on page 41, "Amount" on page 136, "Amount"on page 47, "Amount" on page 30, "CreditNoteAmount" on page 114, "CreditNoteAmount" onpage 116, "DuePayableAmount" on page 114, "DuePayableAmount" on page 116, "InstructedAmount"on page 20, "InterbankSettlementAmount" on page 83, "RemittedAmount" on page 115, "Remit-tedAmount" on page 57, "RemittedAmount" on page 117, "TaxableBaseAmount" on page 134, "Tota-lAmount" on page 135, "TotalTaxAmount" on page 140, "TotalTaxableBaseAmount" on page 140

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 149

Type: Code

Format

pattern [A-Z]{3,3}

Rules

R10 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 26, "Currency" on page 28, "CurrencyOfTransfer" on page 47

Used in attribute(s)

"ActiveOrHistoricCurrencyAndAmount" on page 148

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 109

Restricts

"AddressTypeCode" on page 150

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 149

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 153

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 151

Rules

R9 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 74, "AnyBIC" on page 75

6.7 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

R7 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 48, "BICFI" on page 50

6.8 CPA_Exact9NumericTextDefinition:

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

Type: Text

Usage Guideline


Format

length 9

Used in element(s)

"Identification" on page 63, "MemberIdentification" on page 34

6.9 ClearingChannel2CodeDefinition: Specifies the clearing channel for the routing of the transaction, as part of the payment typeidentification.

Type: Code


BOOK BookTransfer Payment through internal book transfer.

MPNS MassPaymentNetSystem Clearing channel is a mass payment netsettlement system.

RTGS RealTimeGrossSettlementSystem Clearing channel is a real-time gross set-tlement system.

RTNS RealTimeNetSettlementSystem Clearing channel is a real-time net settle-ment system.

Used in element(s)

"ClearingChannel" on page 105

Restricts

"ClearingChannelCode" on page 152

6.10 ClearingChannelCodeDefinition: Specifies the clearing channel for the routing of the transaction, as part of the payment typeidentification.

Type: Code


BOOK BookTransfer Payment through internal book transfer.

MPNS MassPaymentNetSystem Clearing channel is a mass payment netsettlement system.

RTGS RealTimeGrossSettlementSystem Clearing channel is a real-time gross set-tlement system.

RTNS RealTimeNetSettlementSystem Clearing channel is a real-time net settle-ment system.

Is restricted by

"ClearingChannel2Code" on page 152

Message Datatypes

30 January 2017 153

6.11 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

R6 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 110, "CountryOfBirth" on page 39, "CountryOfResidence" on page 96, "Country-OfResidence" on page 99

6.12 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 42

Restricts

"AmountDirectionCode" on page 150

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

Type: Quantity

Usage Guideline


Format

totalDigits 18

fractionDigits 17

Used in element(s)

"CountPerPeriod" on page 54, "DetailedControlSum" on page 73, "OriginalControlSum" on page 78,"OriginalControlSum" on page 81

6.14 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.

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

Used in element(s)

"Code" on page 37

Restricts

"DocumentTypeCode" on page 155

6.15 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.

Message Datatypes

30 January 2017 155


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.

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 112

Restricts

"DocumentTypeCode" on page 155

6.16 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.

Usage Guideline



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.

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 154, "DocumentType6Code" on page 154

Message Datatypes

30 January 2017 157

6.17 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

Used in element(s)

"Code" on page 15

6.18 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 29

6.19 ExternalCashClearingSystem1CodeDefinition: Specifies the cash clearing system, as published in an external cash clearing system codelist.


Type: Code

Format

minLength 1

maxLength 3

Usage Guideline


Used in element(s)

"Code" on page 32

6.20 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 29

6.21 ExternalClearingSystemIdentification1CodeDefinition: Specifies the clearing system identification code, as published in an external clearing systemidentification code list.


Type: Code

Format

minLength 1

maxLength 5

Used in element(s)

"Code" on page 31

6.22 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

Message Datatypes

30 January 2017 159

Used in element(s)

"Code" on page 41

6.23 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 46

6.24 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

Used in element(s)

"Code" on page 47

6.25 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 58

Usage Guideline


6.26 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 69

6.27 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

Used in element(s)

"Code" on page 72

Restricts

"ExternalMandateSetupReasonCode" on page 160

6.28 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

Message Datatypes

30 January 2017 161

maxLength 4

Is restricted by

"ExternalMandateSetupReason1Code" on page 160

6.29 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 76

6.30 ExternalPersonIdentification1CodeDefinition: Specifies the external person identification scheme name code in the format of characterstring with a maximum length of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 108

6.31 ExternalServiceLevel1CodeDefinition: Specifies the external service level code in the format of character string with a maximumlength of 4 characters.


Usage Guideline



Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 119

6.32 ExternalStatusReason1CodeDefinition: Specifies the status reason, as published in an external status reason code list.


Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 125

6.33 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 136

6.34 Frequency6CodeDefinition: Specifies the regularity of an event.

Message Datatypes

30 January 2017 163

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 53, "Type" on page 54

Restricts

"FrequencyCode" on page 163

6.35 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.

Usage Guideline



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 162

6.36 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}

Rules

R8 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 13, "IBAN" on page 14

6.37 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

Message Datatypes

30 January 2017 165

Used in element(s)

"BirthDate" on page 39, "Date" on page 56, "Date" on page 140, "DateOfSignature" on page 70, "Fi-nalCollectionDate" on page 71, "FirstCollectionDate" on page 71, "FromDate" on page 40, "Inter-bankSettlementDate" on page 84, "OriginalFinalCollectionDate" on page 19, "RelatedDate" on page 43,"RelatedDate" on page 111, "RequestedCollectionDate" on page 84, "RequestedExecutionDate" onpage 84, "ToDate" on page 40, "Year" on page 143

6.38 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

Used in element(s)

"AcceptanceDateTime" on page 102, "CreationDateTime" on page 66, "OriginalCreationDateTime" onpage 77

6.39 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 71


Usage Guideline


Type: Text

Format

minLength 1

maxLength 105

Used in element(s)

"AdditionalInformation" on page 127, "AdditionalInformation" on page 129


Type: Text

Format

minLength 1

maxLength 12

Used in element(s)



Type: Text

Format

minLength 1

maxLength 140

Used in element(s)

"AdditionalInformation" on page 42, "AdditionalInformation" on page 146, "AdditionalRemittanceIn-formation" on page 133, "Name" on page 48, "Name" on page 24, "Name" on page 35, "Name" onpage 95, "Name" on page 137, "Name" on page 97, "Name" on page 51, "ReferenceNumber" onpage 56, "ReferenceNumber" on page 139, "Unstructured" on page 118

6.43 Max15NumericTextDefinition: Specifies a numeric string with a maximum length of 15 digits.

Type: Text

Format

pattern [0-9]{1,15}

Message Datatypes

30 January 2017 167

Used in element(s)

"DetailedNumberOfTransactions" on page 73, "OriginalNumberOfTransactions" on page 77, "Original-NumberOfTransactions" on page 81


Type: Text

Format

minLength 1

maxLength 16

Used in element(s)

"BuildingNumber" on page 110, "PostCode" on page 110


Type: Text

Format

minLength 1

maxLength 2048

Used in element(s)

"Description" on page 44, "EmailAddress" on page 36


Type: Text

Format

minLength 1

maxLength 34

Used in element(s)



Usage Guideline


Type: Text

Format

minLength 1

maxLength 350

Used in element(s)

"PlaceAndName" on page 134


Type: Text

Format

minLength 1

maxLength 35

Used in element(s)

"AccountServicerReference" on page 103, "AdministrationZone" on page 139, "Category" on page 145,"CategoryDetails" on page 145, "CertificateIdentification" on page 145, "CityOfBirth" on page 39, "Clear-ingSystemReference" on page 103, "CountrySubDivision" on page 110, "DebtorStatus" on page 145,"FormsCode" on page 145, "Identification" on page 61, "Identification" on page 24, "Identification" onpage 62, "Identification" on page 65, "Issuer" on page 62, "Issuer" on page 59, "Issuer" on page 63, "Is-suer" on page 65, "Issuer" on page 38, "Issuer" on page 45, "Issuer" on page 58, "Issuer" on page 113,"Issuer" on page 64, "Issuer" on page 61, "MandateIdentification" on page 70, "MemberIdentifica-tion" on page 33, "MessageIdentification" on page 66, "Method" on page 139, "Number" on page 43,"Number" on page 111, "OriginalEndToEndIdentification" on page 101, "OriginalInstructionIdentifi-cation" on page 100, "OriginalMandateIdentification" on page 16, "OriginalMessageIdentification" onpage 77, "OriginalMessageNameIdentification" on page 77, "OriginalPaymentInformationIdentification"on page 80, "Other" on page 36, "Proprietary" on page 32, "Proprietary" on page 31, "Proprietary" onpage 47, "Proprietary" on page 15, "Proprietary" on page 29, "Proprietary" on page 76, "Proprietary"on page 108, "Proprietary" on page 38, "Proprietary" on page 41, "Proprietary" on page 136, "Propri-etary" on page 119, "Proprietary" on page 69, "Proprietary" on page 30, "Proprietary" on page 126,"Proprietary" on page 46, "Proprietary" on page 58, "Proprietary" on page 112, "ProvinceOfBirth" onpage 39, "Reference" on page 37, "RegistrationIdentification" on page 141, "RegistrationIdentification"on page 142, "StatusIdentification" on page 100, "TaxIdentification" on page 141, "TaxIdentification"on page 142, "TaxType" on page 142, "TaxType" on page 142, "Title" on page 137, "TownName" onpage 110, "Type" on page 144


Type: Text

Format

minLength 1

Message Datatypes

30 January 2017 169

maxLength 4

Used in element(s)

"Reason" on page 42

6.50 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 110, "Department" on page 109, "Name" on page 26, "Name" on page 28, "Pro-prietary" on page 73, "StreetName" on page 109, "SubDepartment" on page 109

6.51 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 34

6.52 NumberDefinition: Number of objects represented as an integer.

Type: Quantity

Format

totalDigits 18

fractionDigits 0

Used in element(s)

"SequenceNumber" on page 140

Usage Guideline


6.53 PaymentMethod4CodeDefinition: Specifies the transfer method that will be used to transfer an amount of money.

Type: Code


CHK Cheque Written order to a bank to pay a certainamount of money from one person to an-other person.

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.

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.

Used in element(s)

"PaymentMethod" on page 87

Restricts

"PaymentMethodCode" on page 170

6.54 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.

Message Datatypes

30 January 2017 171

Is restricted by

"PaymentMethod4Code" on page 170

6.55 PaymentStatusCodeDefinition: Indicates the status of a single payment transaction or of a group of payment transactions.

Type: Code


ACCP AcceptedCustomerProfile Preceding check of technical validationwas successful. Customer profile checkwas also successful.

ACCR AcceptedCancellationRequest Cancellation is accepted.

ACPT Accepted Request is accepted.

ACSC AcceptedSettlementCompleted Settlement on the debtor's account hasbeen completed.

Usage : this can be used by the firstagent to report to the debtor that thetransaction has been completed. Warn-ing : this status is provided for transac-tion status reasons, not for financial in-formation. It can only be used after bilat-eral agreement

ACSP AcceptedSettlementInProcess All preceding checks such as technicalvalidation and customer profile were suc-cessful and therefore the payment initia-tion has been accepted for execution.

ACTC AcceptedTechnicalValidation Authentication and syntactical and se-mantical validation are successful.

ACWC AcceptedWithChange Instruction is accepted but a change willbe made, such as date or remittance notsent.

PACR PartiallyAcceptedCancellationRequest Cancellation is partially accepted.

PART PartiallyAccepted A number of transactions have beenaccepted, whereas another number oftransactions have not yet achieved 'ac-cepted' status.

PDCR PendingCancellationRequest Cancellation request is pending.

PDNG Pending Payment initiation or individual transac-tion included in the payment initiation ispending. Further checks and status up-date will be performed.

RCVD Received Payment initiation has been received bythe receiving agent.

RJCR RejectedCancellationRequest Cancellation request is rejected

RJCT Rejected Payment initiation or individual transac-tion included in the payment initiationhas been rejected.

Usage Guideline


Is restricted by

"TransactionGroupStatus3Code" on page 177, "TransactionIndividualStatus3Code" on page 180

6.56 PercentageRateDefinition: Rate expressed as a percentage, ie, in hundredths, eg, 0.7 is 7/10 of a percent, and 7.0 is7%.

Type: Rate

Format

totalDigits 11

fractionDigits 10

Used in element(s)

"Rate" on page 134

6.57 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 35, "MobileNumber" on page 35, "PhoneNumber" on page 35

6.58 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 105

Restricts

"PriorityCode" on page 173

Message Datatypes

30 January 2017 173

6.59 PriorityCodeDefinition: Specifies the priority level of an event.

Type: Code


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 172

6.60 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.

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.

Used in element(s)

"SequenceType" on page 106

Restricts

"SequenceTypeCode" on page 173

6.61 SequenceTypeCodeDefinition: Specifies the type of the current transaction that belongs to a sequence of transactions.

Type: Code

Usage Guideline



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 173

6.62 SettlementMethod1CodeDefinition: Specifies the method used to settle the credit transfer instruction.

Type: Code


CLRG ClearingSystem Settlement is done through a paymentclearing system.

COVE CoverMethod Settlement is done through a cover pay-ment.

INDA InstructedAgent Settlement is done by the agent instruct-ed to execute a payment instruction.

INGA InstructingAgent Settlement is done by the agent instruct-ing and forwarding the payment to thenext party in the payment chain.

Used in element(s)

"SettlementMethod" on page 122

Restricts

"SettlementMethodCode" on page 174

6.63 SettlementMethodCodeDefinition: Specifies the method used to settle the payment instruction.

Type: Code

Message Datatypes

30 January 2017 175


CLRG ClearingSystem Settlement is done through a paymentclearing system.

COVE CoverMethod Settlement is done through a cover pay-ment.

INDA InstructedAgent Settlement is done by the agent instruct-ed to execute a payment instruction.

INGA InstructingAgent Settlement is done by the agent instruct-ing and forwarding the payment to thenext party in the payment chain.

Is restricted by

"SettlementMethod1Code" on page 174

6.64 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.

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.

Usage Guideline



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 143

Restricts

"TaxRecordPeriodCode" on page 176

6.65 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.

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.

Message Datatypes

30 January 2017 177


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 175

6.66 TransactionGroupStatus3CodeDefinition: Specifies the status of a group of payment instructions.

Type: Code



Usage Guideline restrictions for thiscode

• This code(pain.002.001.07/Orig-inalGroupInformationAndSta-tus/GroupStatus/AcceptedCus-tomerProfile) is removed.

• This code(pain.002.001.07/Orig-inalPaymentInformationAndSta-tus/PaymentInformationStatus/Ac-ceptedCustomerProfile) is re-moved.


Usage : this can be used by the firstagent to report to the debtor that thetransaction has been completed. Warn-ing : this status is provided for transac-tion status reasons, not for financial in-

Usage Guideline



formation. It can only be used after bilat-eral agreement


• This code(pain.002.001.07/Orig-inalGroupInformationAndSta-tus/GroupStatus/AcceptedSettle-mentCompleted) is removed.

• This code(pain.002.001.07/Orig-inalPaymentInformationAndSta-tus/PaymentInformationStatus/Ac-ceptedSettlementCompleted) is re-moved.



• This code(pain.002.001.07/Orig-inalGroupInformationAndSta-tus/GroupStatus/AcceptedSettle-mentInProcess) is removed.

• This code(pain.002.001.07/Orig-inalPaymentInformationAndSta-tus/PaymentInformationStatus/Ac-ceptedSettlementInProcess) is re-moved.



• This code(pain.002.001.07/Orig-inalPaymentInformationAndSta-tus/PaymentInformationStatus/Ac-ceptedTechnicalValidation) is re-moved.


Message Datatypes

30 January 2017 179



• This code(pain.002.001.07/Orig-inalGroupInformationAndSta-tus/GroupStatus/AcceptedWith-Change) is removed.

• This code(pain.002.001.07/Orig-inalPaymentInformationAndSta-tus/PaymentInformationStatus/Ac-ceptedWithChange) is removed.

PART PartiallyAccepted A number of transactions have beenaccepted, whereas another number oftransactions have not yet achieved 'ac-cepted' status.



• This code(pain.002.001.07/Orig-inalPaymentInformationAndS-tatus/PaymentInformationSta-tus/Pending) is removed.

RCVD Received Payment initiation has been received bythe receiving agent.


• This code(pain.002.001.07/Orig-inalPaymentInformationAndSta-tus/PaymentInformationStatus/Re-ceived) is removed.


Used in element(s)

"GroupStatus" on page 78, "PaymentInformationStatus" on page 81

Restricts

"PaymentStatusCode" on page 171

Usage Guideline


6.67 TransactionIndividualStatus3CodeDefinition: Specifies the status of a single payment instruction.

Type: Code




• This code(pain.002.001.07/Orig-inalPaymentInformationAndSta-tus/TransactionInformationAndS-tatus/TransactionStatus/Accepted-CustomerProfile) is removed.


Usage : this can be used by the firstagent to report to the debtor that thetransaction has been completed. Warn-ing : this status is provided for transac-tion status reasons, not for financial in-formation. It can only be used after bilat-eral agreement


• This code(pain.002.001.07/Orig-inalPaymentInformationAndSta-tus/TransactionInformationAndS-tatus/TransactionStatus/Accept-edSettlementCompleted) is re-moved.



• This code(pain.002.001.07/Orig-inalPaymentInformationAndSta-tus/TransactionInformationAndS-tatus/TransactionStatus/Accept-

Message Datatypes

30 January 2017 181


edSettlementInProcess) is re-moved.




• This code(pain.002.001.07/Orig-inalPaymentInformationAndSta-tus/TransactionInformationAndS-tatus/TransactionStatus/Accepted-WithChange) is removed.



Used in element(s)

"DetailedStatus" on page 73, "TransactionStatus" on page 101

Restricts

"PaymentStatusCode" on page 171

6.68 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 70, "EmployeeTerminationIndicator" on page 57, "FamilyMedicalIn-suranceIndicator" on page 57

Usage Guideline


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.

tusReportV07 pain.002.001 - Payments Canada€¦ · Message Building Blocks 30 January 2017 9 4...

Documents

Transcript of tusReportV07 pain.002.001 - Payments Canada€¦ · Message Building Blocks 30 January 2017 9 4...