XML message for Statement

Transcription

1 XML message for Statement Implementation Guidelines Version 2.0

2 Table of Contents 1. Introduction Scope General principles Contents of the message: Periodicity of the message Use of these guidelines Characteristics Message structure Message Description - detail Message description - high- level Message Item Description GroupHeader MessageIdentification < MsgId> CreationDateTime <CreDtTm> MessageRecipient <MsgRcpt> Name <Nm> MessagePagination <MsgPgntn> PageNumber <PgNb> LastPageIndicator <LastPgInd> AdditionalInformation <AddtlInf> Statement Identification ElectronicSequenceNumber <ElctrncSeqNb> LegalSequenceNumber <LglSeqNb> CreationDateTime <CreDtTm> FromToDate <FrToDt> FromDateTime <FrDtTm> ToDateTime <ToDtTm> CopyDuplicateIndicator <CpyDplctInd> Account <Acct> Identification <Id> IBAN <IBAN> Type <Tp> Proprietary <Prtry> Currency <Ccy> Name <Nm> Owner <Ownr> Name <Nm> Identification <Id> OrganisationIdentification <OrgId> Other <Othr> Identification <Id> Servicer <Svcr> FinancialInstitutionIdentification <FinInstnId> /176

3 BIC <BIC> RelatedAccount <RltdAcct> Identification <Id> IBAN <IBAN> Other <Othr> Identification <Id> Balance <Bal> Type <Tp> CodeOrProprietary <CdOrPrtry> Code <Cd> Proprietary <Prtry> SubType <SubTp> Code <Cd> Amount <Amt> CreditDebitIndicator <CdtDbtInd> Date <Dt> Date <Dt> TransactionsSummary <TxsSummry> TotalEntries <TtlNtries> NumberOfEntries <NbOfNtries> Sum <Sum> TotalNetEntryAmount <TtlNetNtryAmt> CreditDebitIndicator <CdtDbtInd> TotalCreditEntries <TtlCdtNtries> NumberOfEntries <NbOfNtries> Sum <Sum> TotalDebitEntries <TtlDbtNtries> NumberOfEntries <NbOfNtries> Sum <Sum> Entry <Ntry> EntryReference <NtryRef> Amount <Amt> CreditDebitIndicator <CdtDbtInd> ReversalIndicator <RvslInd> Status <Sts> BookingDate <BookgDt> Date <Dt> ValueDate <ValDt> Date <Dt> AccountServicerReference <AcctSvcrRef> BankTransactionCode <BkTxCd> Domain <Domn> Code <Cd> Family <Fmly> Code <Cd> SubFamilyCode <SubFmlyCd> Proprietary <Prtry> Code <Cd> Issuer <Issr> AdditionalInformationIndicator <AddtlInfInd> /176

4 2.102 MessageNameIdentification <MsgNmId> MessageIdentification <MsgId> AmountDetails <AmtDtls> InstructedAmount <InstdAmt> Amount <Amt> TransactionAmount <TxAmt> Amount <Amt> CounterValueAmount <CntrValAmt> Amount <Amt> CurrencyExchange <CcyXchg> SourceCurrency <SrcCcy> TargetCurrency <TrgtCcy> UnitCurrency <UnitCcy> ExchangeRate <XchgRate> ProprietaryAmount <PrtryAmt> Type <Tp> Amount <Amt> Charges <Chrgs> Amount <Amt> CreditDebitIndicator <CdtDbtInd> Type <Tp> Proprietary <Prtry> Identification <Id> Issuer <Issr> Rate <Rate> Tax <Tax> Identification <Id> Rate <Rate> Amount <Amt> EntryDetails <NtryDtls> Batch <Btch> MessageIdentification <MsgId> PaymentInformationIdentification <PmtInfId> NumberOfTransactions <NbOfTxs> TotalAmount <TtlAmt> CreditDebitIndicator <CdtDbtInd> TransactionDetails <TxDtls> References <Refs> MessageIdentification <MsgId> AccountServicerReference <AcctSvcrRef> PaymentInformationIdentification <PmtInfId> InstructionIdentification <InstrId> EndToEndIdentification <EndToEndId> TransactionIdentification <TxId> MandateIdentification <MndtId> ChequeNumber <ChqNb> AmountDetails <AmtDtls> InstructedAmount <InstdAmt> Amount <Amt> TransactionAmount <TxAmt> /176

5 Amount <Amt> CounterValueAmount <CntrValAmt> Amount <Amt> CurrencyExchange <CcyXchg> SourceCurrency <SrcCcy> TargetCurrency <TrgtCcy> UnitCurrency <UnitCcy> ExchangeRate <XchgRate> ProprietaryAmount <PrtryAmt> Type <Tp> Amount <Amt> BankTransactionCode <BkTxCd> Domain <Domn> Code <Cd> Family <Fmly> Code <Cd> SubFamilyCode <SubFmlyCd> Proprietary <Prtry> Code <Cd> Issuer <Issr> Charges <Chrgs> Amount <Amt> CreditDebitIndicator <CdtDbtInd> Type <Tp> Proprietary <Prtry> Identification <Id> Issuer <Issr> Rate <Rate> Tax <Tax> Identification <Id> Rate <Rate> Amount <Amt> Interest <Intrst> Amount <Amt> CreditDebitIndicator <CdtDbtInd> Type <Tp> Proprietary <Prtry> Rate <Rate> Type <Tp> Percentage <Pctg> Other <Othr> FromToDate <FrToDt> FromDateTime <FrDtTm> ToDateTime <ToDtTm> RelatedParties <RltdPties> InitiatingParty <InitgPty> Name <Nm> PostalAddress <PstlAdr> StreetName <StrtNm> BuildingNumber <BldgNb> /176

6 9.1.7 PostCode <PstCd> TownName <TwnNm> Country <Ctry> AddressLine <AdrLine> Debtor <Dbtr> Name <Nm> PostalAddress <PstlAdr> StreetName <StrtNm> BuildingNumber <BldgNb> PostCode <PstCd> TownName <TwnNm> Country <Ctry> AddressLine <AdrLine> Identification <Id> OrganisationIdentification <OrgId> BICOrBEI <BICOrBEI> DebtorAccount <DbtrAcct> Identification <Id> IBAN <IBAN> Other <Othr> Identification <Id> Issuer <Issr> UltimateDebtor <UltmtDbtr> Name <Nm> PostalAddress <PstlAdr> StreetName <StrtNm> BuildingNumber <BldgNb> PostCode <PstCd> TownName <TwnNm> Country <Ctry> AddressLine <AdrLine> Creditor <Cdtr> Name <Nm> PostalAddress <PstlAdr> StreetName <StrtNm> BuildingNumber <BldgNb> PostCode <PstCd> TownName <TwnNm> Country <Ctry> AddressLine <AdrLine> Identification <Id> OrganisationIdentification <OrgId> BICOrBEI <BICOrBEI> Other <Othr> Identification <Id> CreditorAccount <CdtrAcct> Identification <Id> IBAN <IBAN> Other <Othr> Identification <Id> /176

7 1.1.7 Issuer <Issr> UltimateCreditor <UltmtCdtr> Name <Nm> PostalAddress <PstlAdr> StreetName <StrtNm> BuildingNumber <BldgNb> PostCode <PstCd> TownName <TwnNm> Country <Ctry> AddressLine <AdrLine> RelatedAgents <RltdAgts> DebtorAgent <DbtrAgt> FinancialInstitutionIdentification <FinInstnId> BIC <BIC> CreditorAgent <CdtrAgt> FinancialInstitutionIdentification <FinInstnId> BIC <BIC> Purpose <Purp> Code <Cd> RemittanceInformation <RmtInf> Unstructured <Ustrd> Structured <Strd> CreditorReferenceInformation <CdtrRefInf> Type <Tp> CodeOrProprietary <CdOrPrtry> <Cd> Issuer <Issr> Reference <Ref> RelatedDates <RltdDts> AcceptanceDateTime <AccptncDtTm> Tax <Tax> TotalTaxAmount <TtlTaxAmt> Record <Rcrd> Type <Tp> TaxAmount <TaxAmt> Rate <Rate> TaxableBaseAmount <TaxblBaseAmt> TotalAmount <TtlAmt> ReturnInformation <RtrInf> OriginalBankTransactionCode <OrgnlBkTxCd> Domain <Domn> Code <Cd> Family <Fmly> Code <Cd> SubFamilyCode <SubFmlyCd> Proprietary <Prtry> Code <Cd> Issuer <Issr> Originator <Orgtr> Name <Nm> /176

8 2.304 Reason <Rsn> Code <Cd> AdditionalInformation <AddtlInf> AdditionalTransactionInformation <AddtlTxInf> AdditionalEntryInformation <AddtlNtryInf> AdditionalStatementInformation <AddtlStmtInf> Principles governing the structure of reporting General principles Information registered under the Entry item 2.76 : Information registered under the Entry details item : Partial / gross amounts versus net amount : Reporting of Structured Creditor References to RemittanceInformation Item : Reporting of costs, fees and taxes : Reporting of Customer References from Pain- messages : Reporting of the different kinds of amounts: Reporting of the TransactionsSummary 2.43 item: Bank Transaction Codes Transaction codes defined in Luxembourg Appendix Purpose Code List Examples XMLHeader GroupHeader Statement Entries SCT Transfer - single International transfers - collective Received payments with a Structured Creditor Reference Mapping MT940 étendu vs camt.053: Contact Details : /176

9 1. Introduction This document sets out the Luxembourg Implementation Guidelines for the XML B2C Statement message ISO XML - camt The purpose of these Implementation Guidelines is to provide guidance on the use of the Statement Message sent by the banks to the enterprises in Luxembourg. These Implementation Guidelines have been developed by ABBL (Luxembourg Bankers Association) and are greatly inspired by the Febelfin one. The utmost has been done to make sure the information in this publication is correct. However, ABBL by no means can be held liable for any loss or damage incurred due to any incorrect or incomplete information mentioned in this publication. Please contact your bank for any further information. This publication is only available in English Scope This message is sent by the bank to an account holder or a third person mandated by him. It is used for informing the account holder or the third person mandated of the account balances and account transactions General principles Contents of the message: The message can hold the reporting on one or more accounts. The contents of the message will be limited to information about the transactions that have been entered into bookkeeping Reporting will be done in the account currency. Any transaction in another currency first will be converted into the account currency. Reporting as for the transactions that have been entered into bookkeeping, will be carried out through MX camt BankToCustomerStatementV02 The message can be split up into several messages depending on the volume of data to be transferred. 9/176

10 Periodicity of the message As a matter of principle, a message will be created each bank working day when transactions are taking place. Exceptionally, with a bilateral agreement, this may also be the case on a day without any transactions (empty message) Use of these guidelines Each item of the BankToCustomer Cash Management Standards message is referring to the corresponding index of the item in the (ISO 20022) Message Definition Report for Bank-to- Customer Cash Management. This Report can be found on under Catalogue of UNIFI messages, with camt as reference for the EoD reporting. Any gaps in the index numbering are due to the fact that some message elements of the MX.CAMT message are not supported in the Luxembourg subset. Message elements not described in these guidelines must not be supported. The description of each message item contains: Index Definition Usage XML Tag Presence Number referring to the corresponding description in the MX.CAMT Message Definition Report for Bank-to-Customer Cash Management Statements. This contains the definition of the message set or element. Additional info on how this element must be used. Short name identifying an element within an XML message, which is put between brackets, e.g. <Ntry>. This shows if an element is optional or obligatory as well as the number of times it can be repeated. The occurrence is mentioned between square brackets. For example : [0..1] indicates that the element can occur 0 times or 1 time. The element is optional. [1..1] indicates that the element must not occur more than once. The element is obligatory. [1..n] indicates that the element is obligatory and can occur between 1 and n times An element, which is part of a set of elements is obligatory, in so far as the set it is part of, is mentioned in the message. If only one element among others may be present, this will be indicated by {OR OR} in front of the elements concerned Format Rules Specification of the values and format allowed Any specific rules which could have an impact on the presence or the values of an element. The use of optional fields may be subject to a bilateral agreement with the bank. 10/176

11 1.3. Characteristics The characters allowed in the UNIFI messages are those of the UTF8 standard. However, only the set of Latin characters generally used in international communication will be allowed. These are as follows a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z / -? : ( )., ' + Space 1.4. Message structure XML Schemes : The description of the UNIFI document models can be found in a number of schemes. A specific description language (XSD) is used in those schemes. The schemes make it possible to give a description of the tags in the document, the structure and sequence of those beacons (hierarchy of tags) as well as the codes which are allowed for some specific data, the number of possible cases, the obligatory or optional character of some of the data, etc. The general XSD for camt can be found on > Catalogue of UNIFI Messages > Payments > cash Management > A data record, which contains an XML camt message, has the following structure: <?xml version = "1.0" encoding = "UTF-8"?> <Document xmlns = "urn:iso:std:iso:20022:tech:xsd:camt " xmlns:xsi = " <camt > message contained </camt > </Document> MX.CAMT.053 sets The message described in this document (Camt ) consists of the following sets: A. Group Header : this is an obligatory block which occurs only once. It contains information proper to the message (identification, creation date, addressee) B. Statement : this block is obligatory and occurs more than once. It will be repeated, as many times as there are different accounts and/or dates in that particular message. This set contains information pertaining to the balances and the transactions. 11/176

12 12/176

13 The message may have one of the following characteristics : a message for one account for one bank working date. This message will contain a GroupHeader-block and one Statement-block: GroupHeader Statement Account 1 This is the preferred and default option in Luxembourg, unless otherwise agreed between parties. a message for several accounts for one bank working date. This message will contain a GroupHeader-block and for each account one Statement-block: GroupHeader Statement Account 1 Date 1 Statement Account 2 Date 1 Statement Account 3 Date 1 13/176

14 2. Message Description - detail Note :the index numbering in the table below is a copy of the numbering in the (ISO 20022) Message Definition Report MX camt BankToCustomerStatementV01 document. Index Long Name L. Or Pres. Rule Tag Name GroupHeader 1 [1..1] TAG GrpHdr MessageIdentification 2 [1..1] string maxlength: 35 MsgId CreationDateTime 2 [1..1] datetime CreDtTm MessageRecipient 2 [0..1] TAG MsgRcpt Name 3 [0..1] string maxlength: 70 Nm MessagePagination 2 [0..1] TAG MsgPgntn PageNumber 3 [1..1] string pattern: [0-9]{1,5} PgNb LastPageIndicator 3 [1..1] boolean LastPgInd AdditionalInformation 2 [0..1] string maxlength: 500 AddtlInf Statement 1 [1..n] TAG Stmt Identification 2 [1..1] string maxlength: 35 Id ElectronicSequenceNumber 2 [0..1] decimal fractiondigits: 0 totaldigits: 18 ElctrncSeqNb LegalSequenceNumber 2 [0..1] decimal fractiondigits: 0 totaldigits: 18 LglSeqNb CreationDateTime 2 [1..1] datetime CreDtTm FromToDate 2 [0..1] TAG FrToDt FromDateTime 3 [1..1] datetime FrDtTm ToDateTime 3 [1..1] datetime ToDtTm CopyDuplicateIndicator 2 [0..1] string enumeration: CODU COPY DUPL CpyDplctInd Account 2 [1..1] TAG Acct Identification 3 [1..1] TAG Id IBAN 4 {Or [1..1] string pattern: [a-za-z]{2,2}[0-9]{2,2}[aza-z0-9]{1,30} IBAN Type 3 [0..1] string enumeration: Tp Proprietary 4 [1..1] string maxlength: 35 Prtry Currency 3 [0..1] string pattern: [A-Z]{3,3} Ccy Name 3 [0..1] string maxlength: 70 Nm Owner 3 [0..1] TAG Ownr Name 4 [0..1] string maxlength: 140 Nm Identification 4 [0..1] TAG Id OrganisationIdentification 5 [1..1] TAG OrgId Other 6 [0..n] TAG Othr Identification 7 [1..1] string maxlength: 35 Id Servicer 3 [0..1] TAG Svcr FinancialInstitutionIdentification 4 [1..1] TAG FinInstnId BIC 5 [1..1] string pattern: [A-Z]{6,6}[A-Z2-9][A-NP- Z0-9]([A-Z0-9]{3,3}){0,1} BIC RelatedAccount 2 [0..1] TAG RltdAcct Identification 3 [1..1] TAG Id 14/176

15 IBAN 4 {Or [1..1] string pattern: [a-za-z]{2,2}[0-9]{2,2}[aza-z0-9]{1,30} IBAN Other 4 Or} [1..1] TAG Othr Identification 5 [1..1] Max34Text Id Balance 2 [1..n] TAG Bal Type 3 [1..1] TAG Tp CodeOrProprietary 4 [1..1] TAG CdOrPrtry Code 5 {Or [1..1] string enumeration cfr Message Item Description Cd Proprietary 5 Or} [1..1] string maxlength: 35 Prtry subtype 4 [0..1] TAG SubTp Code 5 {Or [1..1] string enumeration cfr Message Item Description Cd Amount 3 [1..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required Amt CreditDebitIndicator 3 [1..1] string enumeration: cfr Message Item Description CdtDbtInd Date 3 [1..1] TAG Dt Date 4 [1..1] date Dt TransactionsSummary 2 [0..1] TAG TxsSummry TotalEntries 3 [0..1] TAG TtlNtries NumberOfEntries 4 [0..1] string pattern: [0-9]{1,15} NbOfNtries Sum 4 [0..1] TotalNetEntryAmount 4 [0..1] CreditDebitIndicator 4 [0..1] decimal fractiondigits: 17 totaldigits: 18 decimal fractiondigits: 17 totaldigits: 18 string enumeration: cfr Message Item Description Sum TtlNetNtryAmt CdtDbtInd TotalCreditEntries 3 [0..1] TAG TtlCdtNtries NumberOfEntries 4 [0..1] string pattern: [0-9]{1,15} NbOfNtries Sum 4 [0..1] decimal fractiondigits: 17 totaldigits: 18 Sum TotalDebitEntries 3 [0..1] TAG TtlDbtNtries NumberOfEntries 4 [0..1] string pattern: [0-9]{1,15} NbOfNtries Sum 4 [0..1] decimal fractiondigits: 17 totaldigits: 18 Sum Entry 2 [0..n] TAG Ntry EntryReference 3 [0..1] string maxlength: 35 NtryRef Amount 3 [1..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required Amt CreditDebitIndicator 3 [1..1] string enumeration: cfr Message Item Description CdtDbtInd ReversalIndicator 3 [0..1] boolean RvslInd Status 3 [1..1] string enumeration: BOOK Sts BookingDate 3 [0..1] TAG BookgDt Date 4 [1..1] date Dt 15/176

16 ValueDate 3 [0..1] TAG ValDt Date 4 [1..1] date Dt AccountServicerReference 3 [0..1] string maxlength: 35 AcctSvcrRef BankTransactionCode 3 [1..1] TAG BkTxCd Domain 4 [0..1] TAG Domn Code 5 [1..1] string maxlength: 4 Cd Family 5 [1..1] TAG Fmly Code 6 [1..1] string maxlength: 4 Cd SubFamilyCode 6 [1..1] string maxlength: 4 SubFmlyCd Proprietary 4 [0..1] TAG Prtry Code 5 [1..1] string maxlength: 35 Cd Issuer 5 [0..1] string maxlength: 35 Issr AdditionalInformationIndicator 3 [0..1] string maxlength: 35 AddtlInfInd MessageNameIdentification 4 [0..1] string maxlength: 35 MsgNmId MessageIdentification 4 [0..1] string maxlength: 35 MsgId AmountDetails 3 [0..1] TAG AmtDtls InstructedAmount 4 [0..1] TAG InstdAmt Amount 5 [1..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required Amt TransactionAmount 4 [0..1] TAG TxAmt Amount 5 [1..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required Amt CounterValueAmount 4 [0..1] TAG CntrValAmt Amount 5 [1..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required Amt CurrencyExchange 5 [0..1] TAG CcyXchg SourceCurrency 6 [1..1] string pattern: [A-Z]{3,3} SrcCcy TargetCurrency 6 [0..1] string pattern: [A-Z]{3,3} TrgtCcy UnitCurrency 6 [0..1] string pattern: [A-Z]{3,3} UnitCcy ExchangeRate 6 [1..1] decimal fractiondigits: 10 totaldigits: 11 XchgRate ProprietaryAmount 4 [0..1] TAG PrtryAmt Type 5 [1..1] string maxlength: 35 Tp Amount 5 [1..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required Amt Charges 3 [0..n] TAG Chrgs Amount 4 [1..1] CreditDebitIndicator 4 [0..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required string enumeration: cfr Message Item Description Amt CdtDbtInd Type 4 [0..1] TAG Tp Proprietary 5 [1..1] string pattern: [a-za-z0-9]{1,4} Prtry Identification 6 [1..1] string maxlength: 35 Id Issuer 6 [0..1] string maxlength: 35 Issr Rate 4 [0..1] decimal fractiondigits: 10 totaldigits: 11 Rate Tax 4 [0..1] TAG Tax Identification 5 [0..1] string maxlength: 35 Id 16/176

17 Rate 5 [0..1] Amount 5 [0..1] decimal fractiondigits: 10 totaldigits: 11 decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required Rate Amt EntryDetails 3 [0..n] TAG NtryDtls Batch 4 [0..1] TAG Btch MessageIdentification 5 [0..1] string maxlength: 35 MsgId PaymentInformationIdentification 5 [0..1] string maxlength: 35 PmtInfId NumberOfTransactions 5 [0..1] string pattern: [0-9]{1,15} NbOfTxs TotalAmount 5 [0..1] CreditDebitIndicator 5 [0..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required string enumeration: cfr Message Item Description TtlAmt CdtDbtInd TransactionDetails 4 [0..n] TAG TxDtls References 5 [0..1] TAG Refs MessageIdentification 6 [0..1] string maxlength: 35 MsgId AccountServicerReference 6 [0..1] string maxlength: 35 AcctSvcrRef PaymentInformationIdentification 6 [0..1] string maxlength: 35 PmtInfId InstructionIdentification 6 [0..1] string maxlength: 35 InstrId EndToEndIdentification 6 [0..1] string maxlength: 35 EndToEndId TransactionIdentification 6 [0..1] string maxlength: 35 <TxId> MandateIdentification 6 [0..1] string maxlength: 35 MndtId ChequeNumber 6 [0..1] string maxlength: 35 ChqNb AmountDetails 5 [0..1] TAG AmtDtls InstructedAmount 6 [0..1] TAG InstdAmt Amount 7 [1..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required Amt TransactionAmount 6 [0..1] TAG TxAmt Amount 7 [1..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required Amt CounterValueAmount 6 [0..1] TAG CntrValAmt Amount 7 [1..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required Amt CurrencyExchange 7 [0..1] TAG CcyXchg SourceCurrency 8 [1..1] string pattern: [A-Z]{3,3} SrcCcy TargetCurrency 8 [0..1] string pattern: [A-Z]{3,3} TrgtCcy UnitCurrency 8 [0..1] string pattern: [A-Z]{3,3} UnitCcy ExchangeRate 8 [1..1] decimal fractiondigits: 10 totaldigits: 11 XchgRate ProprietaryAmount 6 [0..1] TAG PrtryAmt Type 7 [1..1] string maxlength: 35 Tp Amount 7 [1..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required Amt BankTransactionCode 5 [0..1] TAG BkTxCd Domain 6 [0..1] TAG Domn Code 7 [1..1] string maxlength: 4 Cd Family 7 [1..1] TAG Fmly Code 8 [1..1] string maxlength: 4 Cd SubFamilyCode 8 [1..1] string maxlength: 4 SubFmlyCd 17/176

18 Proprietary 6 [0..1] TAG Prtry Code 7 [1..1] string maxlength: 35 Cd Issuer 7 [0..1] string maxlength: 35 Issr Charges 5 [0..n] TAG Chrgs Amount 6 [1..1] CreditDebitIndicator 6 [0..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required string enumeration: cfr Message Item Description Amt CdtDbtInd Type 6 [0..1] TAG Tp Proprietary 7 [1..1] TAG Prtry Identification 8 [1..1] string maxlength: 35 Id Issuer 8 [0..1] string maxlength: 35 Issr Rate 6 [0..1] decimal fractiondigits: 10 totaldigits: 11 Rate Tax 6 [0..1] TAG Tax Identification 7 [0..1] string maxlength: 35 Id Rate 7 [0..1] Amount 7 [0..1] decimal fractiondigits: 10 totaldigits: 11 decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required Rate Amt Interest 5 [0..n] TAG Intrst Amount 6 [1..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required Amt CreditDebitIndicator 6 [1..1] string enumeration: CRDT DBIT CdtDbtInd Type 6 [0..1] TAG Tp Proprietary 7 [1..1] string maxlength: 35 totaldigits: 11 Prtry Rate 6 [0..n] TAG Rate Type 7 [1..1] TAG Tp Percentage 8 {Or [1..1] PercentageRate fractiondigits: 10 Pctg Other 8 Or} [1..1] string maxlength: 35 Othr FromToDate 6 [0..1] TAG FrToDt FromDateTime 7 [1..1] datetime FrDtTm ToDateTime 7 [1..1] datetime ToDtTm RelatedParties 5 [0..1] TAG RltdPties InitiatingParty 6 [0..1] TAG InitgPty Name 7 [0..1] string maxlength: 70 Nm PostalAddress 7 [0..1] TAG PstlAdr StreetName 8 [0..1] string maxlength: 70 StrtNm BuildingNumber 8 [0..1] string maxlength: 16 BldgNb PostalCode 8 [0..1] string maxlength: 16 PstCd Townname 8 [0..1] string maxlength: 35 TwnNm Country 8 [0..1] string pattern: [A-Z]{2,2} Ctry AddressLine 8 [0..7] string maxlength: 70 AdrLine Debtor 6 [0..1] TAG Dbtr Name 7 [0..1] string maxlength: 70 Nm PostalAddress 7 [0..1] TAG PstlAdr StreetName 8 [0..1] string maxlength: 70 StrtNm BuildingNumber 8 [0..1] string maxlength: 16 BldgNb 18/176

19 PostalCode 8 [0..1] string maxlength: 16 PstCd Townname 8 [0..1] string maxlength: 35 TwnNm Country 8 [0..1] string pattern: [A-Z]{2,2} Ctry AddressLine 8 [0..7] string maxlength: 70 AdrLine Identification 7 [0..1] TAG Id OrganisationIdentification 8 [1..1] TAG OrgId BICOrBEI 9 [0..1] string pattern: [A-Z]{6,6}[A-Z2-9][A-NP- Z0-9]([A-Z0-9]{3,3}){0,1} BICOrBEI DebtorAccount 6 [0..1] TAG DbtrAcct Identification 7 [1..1] TAG Id IBAN 8 {Or [1..1] string pattern: [a-za-z]{2,2}[0-9]{2,2}[aza-z0-9]{1,30} IBAN Other 8 Or} [1..1] TAG Othr Identification 9 [1..1] Max34Text Id Issuer 8 [0..1] Max35Text Issr UltimateDebtor 6 [0..1] TAG UltmtDbtr Name 7 [0..1] string maxlength: 70 Nm PostalAddress 7 [0..1] TAG PstlAdr StreetName 8 [0..1] string maxlength: 70 StrtNm BuildingNumber 8 [0..1] string maxlength: 16 BldgNb PostalCode 8 [0..1] string maxlength: 16 PstCd Townname 8 [0..1] string maxlength: 35 TwnNm Country 8 [0..1] string pattern: [A-Z]{2,2} Ctry AddressLine 8 [0..7] string maxlength: 70 AdrLine Creditor 6 [0..1] TAG Cdtr Name 7 [0..1] string maxlength: 70 Nm PostalAddress 7 [0..1] TAG PstlAdr StreetName 8 [0..1] string maxlength: 70 StrtNm BuildingNumber 8 [0..1] string maxlength: 16 BldgNb PostalCode 8 [0..1] string maxlength: 16 PstCd Townname 8 [0..1] string maxlength: 35 TwnNm Country 8 [0..1] string pattern: [A-Z]{2,2} Ctry AddressLine 8 [0..7] string maxlength: 70 AdrLine Identification 7 [0..1] TAG Id OrganisationIdentification 8 [1..1] TAG OrgId BICOrBEI 9 [0..1] string pattern: [A-Z]{6,6}[A-Z2-9][A-NP- Z0-9]([A-Z0-9]{3,3}){0,1} BICOrBEI Other 9 [0..n] TAG Othr Identification 10 [1..1] string maxlength: 35 Id CreditorAccount 6 [0..1] TAG CdtrAcct Identification 7 [1..1] TAG Id IBAN 8 {Or [1..1] string pattern: [a-za-z]{2,2}[0-9]{2,2}[aza-z0-9]{1,30} IBAN Other 8 Or} [1..1] TAG Othr Identification 9 [1..1] Max34Text Id Issuer 8 [0..1] Max35Text Issr 19/176

20 UltimateCreditor 6 [0..1] TAG UltmtCdtr Name 7 [0..1] string maxlength: 70 Nm PostalAddress 7 [0..1] TAG PstlAdr StreetName 8 [0..1] string maxlength: 70 StrtNm BuildingNumber 8 [0..1] string maxlength: 16 BldgNb PostalCode 8 [0..1] string maxlength: 16 PstCd Townname 8 [0..1] string maxlength: 35 TwnNm Country 8 [0..1] string pattern: [A-Z]{2,2} Ctry AddressLine 8 [0..7] string maxlength: 70 AdrLine RelatedAgents 5 [0..1] TAG RltdAgts DebtorAgent 6 [0..1] TAG DbtrAgt FinancialInstitutionIdentification 7 [1..1] TAG FinInstnId BIC 8 [0..1] string pattern: [A-Z]{6,6}[A-Z2-9][A-NP- Z0-9]([A-Z0-9]{3,3}){0,1} BIC CreditorAgent 6 [0..1] TAG <CdtrAgt> FinancialInstitutionIdentification 7 [1..1] TAG FinInstnId BIC 8 [0..1] string pattern: [A-Z]{6,6}[A-Z2-9][A-NP- Z0-9]([A-Z0-9]{3,3}){0,1} BIC Purpose 5 [0..1] TAG Purp Code 6 [1..1] string maxlength: 4 Cd RemittanceInformation 5 [0..1] TAG RmtInf Unstructured 6 [0..n] string maxlength: 140 Ustrd Structured 6 [0..n] TAG Strd CreditorReferenceInformation 7 [0..1] TAG CdtrRefInf Type 8 [0..1] TAG Tp CodeOrProprietary 9 [1..1] TAG CdOrPrtry Code 10 [1..1] string enumeration cfr Message Item Description Cd Issuer 9 [0..1] string maxlength: 35 Issr Reference 8 [0..1] string maxlength: 35 Ref RelatedDates 5 [0..1] TAG RltdDts AcceptanceDateTime 6 [0..1] datetime AccptncDtTm Tax 5 [0..1] TAG Tax TotalTaxAmount 6 [0..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required TtlTaxAmt Record 6 [0..n] TAG Rcrd Type 7 [0..1] string maxlength: 35 Tp TaxAmount 7 [0..1] TaxAmt Rate 8 [0..1] TaxableBaseAmount 8 [0..1] TotalAmount 8 [0..1] decimal fractiondigits: 10 totaldigits: 11 decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required Rate TaxblBaseAmt TtlAmt ReturnInformation 5 [0..1] TAG RtrInf OriginalBankTransactionCode 6 [0..1] TAG OrgnlBkTxCd Domain 7 [0..1] TAG Domn Code 8 [1..1] string maxlength: 4 Cd Family 8 [1..1] TAG Fmly 20/176

21 Code 9 [1..1] string maxlength: 4 Cd SubFamilyCode 9 [1..1] string maxlength: 4 SubFmlyCd Proprietary 7 [0..1] TAG Prtry Code 8 [1..1] string maxlength: 35 Cd Issuer 8 [0..1] string maxlength: 35 Issr Originator 6 [0..1] TAG Orgtr Name 7 [0..1] string maxlength: 70 Nm Reason 6 [0..1] TAG Rsn Code 7 [1..1] string enumeration cfr Message Item Description Cd AdditionalInformation 6 [0..n] string maxlength: 105 AddtlInf AdditionalTransactionInformation 5 [0..1] string maxlength: 500 AddtlTxInf AdditionalEntryInformation 3 [0..1] string maxlength: 500 AddtlNtryInf AdditionalStatementInformation 2 [0..1] string maxlength: 500 AddtlStmtInf 21/176

22 2.1. Message description - high-level Index Long Name L. Or Pres. Rule Tag Name GroupHeader 1 [1..1] TAG GrpHdr MessageIdentification 2 [1..1] string maxlength: 35 MsgId CreationDateTime 2 [1..1] datetime CreDtTm MessageRecipient 2 [0..1] TAG MsgRcpt MessagePagination 2 [0..1] TAG MsgPgntn AdditionalInformation 2 [0..1] string maxlength: 500 AddtlInf Statement 1 [1..n] TAG Stmt Identification 2 [1..1] string maxlength: 35 Id ElectronicSequenceNumber 2 [0..1] decimal fractiondigits: 0 totaldigits: 18 ElctrncSeqNb LegalSequenceNumber 2 [0..1] decimal fractiondigits: 0 totaldigits: 18 LglSeqNb CreationDateTime 2 [1..1] datetime CreDtTm FromToDate 2 [0..1] TAG FrToDt CopyDuplicateIndicator 2 [0..1] string enumeration: CODU COPY DUPL CpyDplctInd Account 2 [1..1] TAG Acct RelatedAccount 2 [0..1] TAG RltdAcct Balance 2 [1..n] TAG Bal TransactionsSummary 2 [0..1] TAG TxsSummry Entry 2 [0..n] TAG Ntry EntryReference 3 [0..1] string maxlength: 35 NtryRef Amount 3 [1..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required Amt CreditDebitIndicator 3 [1..1] string enumeration: cfr Message Item Description CdtDbtInd ReversalIndicator 3 [0..1] boolean RvslInd Status 3 [1..1] string enumeration: BOOK Sts BookingDate 3 [0..1] TAG BookgDt ValueDate 3 [0..1] TAG ValDt AccountServicerReference 3 [0..1] string maxlength: 35 AcctSvcrRef BankTransactionCode 3 [1..1] TAG BkTxCd AdditionalInformationIndicator 3 [0..1] string maxlength: 35 AddtlInfInd AmountDetails 3 [0..1] TAG AmtDtls Charges 3 [0..n] TAG Chrgs EntryDetails 3 [0..n] TAG NtryDtls Batch 4 [0..1] TAG Btch MessageIdentification 5 [0..1] string maxlength: 35 MsgId PaymentInformationIdentification 5 [0..1] string maxlength: 35 PmtInfId NumberOfTransactions 5 [0..1] string pattern: [0-9]{1,15} NbOfTxs TotalAmount 5 [0..1] decimal mininclusive: 0 fractiondigits: 5 totaldigits: 18 Attribute Ccy: required TtlAmt 22/176

23 CreditDebitIndicator 5 [0..1] string enumeration: cfr Message Item Description CdtDbtInd TransactionDetails 4 [0..n] TAG TxDtls References 5 [0..1] TAG Refs AmountDetails 5 [0..1] TAG AmtDtls BankTransactionCode 5 [0..1] TAG BkTxCd Charges 5 [0..n] TAG Chrgs Interest 5 [0..n] TAG Intrst RelatedParties 5 [0..1] TAG RltdPties RelatedAgents 5 [0..1] TAG RltdAgts Purpose 5 [0..1] TAG Purp RemittanceInformation 5 [0..1] TAG RmtInf RelatedDates 5 [0..1] TAG RltdDts Tax 5 [0..1] TAG Tax ReturnInformation 5 [0..1] TAG RtrInf AdditionalTransactionInformation 5 [0..1] string maxlength: 500 AddtlTxInf AdditionalEntryInformation 3 [0..1] string maxlength: 500 AddtlNtryInf AdditionalStatementInformation 2 [0..1] string maxlength: 500 AddtlStmtInf 23/176

24 3. Message Item Description 1.0. GroupHeader Common information for the message. Type: The GroupHeader block is composed of the following GroupHeader42 element(s): 24/176

25 1.1. MessageIdentification < MsgId> Usage: Data Type: Max35Text Point to point reference assigned by the account servicing institution and sent to the account owner to unambiguously identify the message. The account servicing institution has to make sure that 'MessageIdentification' is unique per instructed party for a pre-agreed period. Format: maxlength: CreationDateTime <CreDtTm> Date and time at which the message was created. Data Type: ISODateTime 1.3. MessageRecipient <MsgRcpt> Party authorised by the account owner to receive information about movements on the account. Usage: MessageRecipient should only be identified when different from the account owner. Type: This message item is composed of the following PartyIdentification32 element(s): 25/176

26 9.1.0 Name <Nm> Data Type: Max140Text Name by which a party is known and which is usually used to identify that party. Format: maxlength: MessagePagination <MsgPgntn> Pagination of the message. Usage: The pagination of the message is only allowed when agreed between the parties. Type: This message item is composed of the following Pagination element(s): Additional Info: depending on the volume of information to be forwarded, it will be possible to split up the message. 1. if there is no separation (one single file), item always must be completed by «1» and item by «TRUE». 2. if there is separation, item always must be completed by a pagenumber and item by «FALSE», except for the last page, where item is «TRUE». In that case, the intermediary balances will be reported under item 2.27 <Prtry>. By default in Luxembourg, option 1. will be applied. 26/176

27 8.2.0 PageNumber <PgNb> Page number. Data Type: Max5NumericText Format: [0-9]{1,5} LastPageIndicator <LastPgInd> Indicates the last page. Data Type: One of the following YesNoIndicator values must be used: MeaningWhenTrue: Yes MeaningWhenFalse: No 1.5. AdditionalInformation <AddtlInf> Further details on the message. Data Type: Max500Text Format: maxlength: /176

28 2.0 Statement Presence: Type: [1..n] Reports on booked entries and balances for a cash account. The Statement block is composed of the following AccountStatement1 element(s): 2.1 Identification Unique identification, as assigned by the account servicer, to unambiguously identify the account statement. Data Type: Max35Text Format: maxlength: 35 28/176

29 2.2 ElectronicSequenceNumber <ElctrncSeqNb> Usage: Data Type: Number Sequential number of the statement, as assigned by the account servicer. The sequential number is increased incrementally for each statement sent electronically. Format: fractiondigits: 0 totaldigits: 18 Additional info: If not used, then field 2.3 has to be used 2.3 LegalSequenceNumber <LglSeqNb> Legal sequential number of the statement, as assigned by the account servicer. It is increased incrementally for each statement sent. Usage: Data Type: Number Where a paper statement is a legal requirement, it may have a number different from the electronic sequential number. Paper statements could for instance only be sent if movement on the account has taken place, whereas electronic statements could be sent at the end of each reporting period, regardless of whether movements have taken place or not. Format: fractiondigits: 0 totaldigits: 18 Additional info: If not used, then field 2.2 has to be used 2.4 CreationDateTime <CreDtTm> Date and time at which the message was created. Data Type: ISODateTime 29/176

30 2.5 FromToDate <FrToDt> Type: Range of time between the start date and the end date for which the account statement is issued. This message item is composed of the following DateTimePeriodDetails element(s): FromDateTime <FrDtTm> Date and time at which the range starts. Data Type: ISODateTime ToDateTime <ToDtTm> Date and time at which the range ends. Data Type: ISODateTime 30/176

31 2.6 CopyDuplicateIndicator <CpyDplctInd> Specifies if this document is a copy, a duplicate, or a duplicate of a copy. Usage: This field is not used in Luxembourg Data Type: Code When this message item is present, only the following CopyDuplicate1Code value must be used: 2.10 Account <Acct> Unambiguous identification of the account to which credit and debit entries are made. Type: This message item is composed of the following CashAccount20 element(s): 31/176

32 1.2.0 Identification <Id> Unique and unambiguous identification of the account between the account owner and the account servicer. Type: This message item is composed of one of the following AccountIdentification3Choice element(s): IBAN <IBAN> This message item is part of choice 1.1 AccountIdentification3Choice. International Bank Account Number (IBAN) - identifier used internationally by financial institutions to uniquely identify the account of a customer. Further specifications of the format and content of the IBAN can be found in the standard ISO "Banking and related financial services - International Bank Account Number (IBAN)" version , or later revisions. Data Type: IBANIdentifier Format: Rule(s): [a-za-z]{2,2}[0-9]{2,2}[a-za-z0-9]{1,30} For Luxembourg banks, IBAN format (ISO 13616) must always be used. 32/176

33 1.2.8 Type <Tp> Nature, or use, of the account. Type: This message item is composed of one of the following CashAccountType2 element(s): Proprietary <Prtry> This message item is part of choice Type. Proprietary nature or use of the account. Data Type: Max35Text Format: maxlength: Currency <Ccy> Identification of the currency in which the account is held. Data Type: ActiveOrHistoricCurrencyCode Format: [A-Z]{3,3} Rule(s): ActiveOrHistoricCurrency The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged. Additional Info: Banks active in Multiline will always used this field. 33/176

34 Name <Nm> Usage: Data Type: Max70Text Name of the account, as assigned by the account servicing institution, in agreement with the account owner in order to provide an additional means of identification of the account. The account name is different from the account owner name. The account name is used in certain user communities to provide a means of identifying the account, in addition to the account owner's identity and the account number. Format: maxlength: Owner <Ownr> Party that legally owns the account. Type: This message item is composed of the following PartyIdentification8 element(s): Name <Nm> Name by which a party is known and which is usually used to identify that party. Data Type: Max70Text Format: maxlength: /176

35 Identification <Id> Unique and unambiguous way of identifying an organisation or an individual person. Type: This message item is composed of one of the following Party6Choice element(s): OrganisationIdentification <OrgId> This message item is part of choice Identification. Unique and unambiguous way to identify an organisation. Type: This message item is composed of the following OrganisationIdentification4 element(s): Other <Othr> Presence: Type: [0..n] Unique identification of an organisation, as assigned by an institution, using an identification scheme. This message item is composed of the following GenericOrganisationIdentification1 element(s): 35/176

36 Identification <Id> Identification assigned by an institution. Data Type: Max35Text Format: maxlength: 35 36/176

37 Servicer <Svcr> Party that manages the account on behalf of the account owner: party that manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account. Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification4 element(s): FinancialInstitutionIdentification <FinInstnId> Unique and unambiguous identification of a financial institution, as assigned under an internationally recognised or proprietary identification scheme. Type: This message item is composed of the following FinancialInstitutionIdentification7 element(s) 37/176

38 BIC <BIC> Data Type: BICIdentifier Format: Rule(s): Bank Identifier Code. Code allocated to financial institutions by the Registration Authority, under an international identification scheme, as described in the latest version of the standard ISO 9362 Banking (Banking telecommunication messages, Bank Identifier Codes). [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1} BIC Valid BICs are registered with the ISO 9362 Registration Authority, and consist of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: BANK CODE, COUNTRY CODE, LOCATION CODE, BRANCH CODE. The bank code, country code and location code are mandatory, while the branch code is optional RelatedAccount <RltdAcct> Type: Identifies the parent account of the account for which the statement has been issued. This message item is composed of the following CashAccount16 element(s): Identification <Id> 38/176

39 Unique and unambiguous identification for the account between the account owner and the account servicer. Type: This message item is composed of one of the following AccountIdentification4Choice element(s): IBAN <IBAN> This message item is part of choice Identification. International Bank Account Number (IBAN) - identifier used internationally by financial institutions to uniquely identify the account of a customer. Further specifications of the format and content of the IBAN can be found in the standard ISO "Banking and related financial services - International Bank Account Number (IBAN)" version , or later revisions. Data Type: IBAN2007Identifier Format: Rule(s): [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30} IBAN Other <Othr> This message item is part of choice Identification. Unique identification of an account, as assigned by the account servicer, using an identification scheme. Type: This message item is composed of the following GenericAccountIdentification1 element(s): 39/176

40 1.1.3 Identification <Id> Data Type: Max34Text Identification assigned by an institution. Format: maxlength: 34 40/176

41 2.23 Balance <Bal> Presence: Type: Rule(s): [1..n] Set of elements defining the balance(s). This message item is composed of the following CashBalance3 element(s): AvailabilityAndTypeRule 41/176

42 2.24 Type <Tp> Type: Specifies the nature of a balance, eg, opening booked balance. This message item is composed of one of the following BalanceType12Choice element(s): 2.25 CodeOrProprietary <CdOrPrtry> Type: Coded or proprietary format balance type. This message item is composed of one of the following BalanceType5Choice element(s): 2.26 Code <Cd> This message item is part of choice 2.25 CodeOrProprietary. Balance type, in a coded form. Data Type: Code One of the following BalanceType12Code values must be used: CLBD ClosingBooked Balance of the account at the end of the pre-agreed account reporting period. It is the sum of the opening booked balance at the beginning of the period and all entries booked to the 42/176

43 account during the pre-agreed account reporting period. OPBD CLAV OpeningBooked Book balance of the account at the beginning of the account reporting period. It always equals the closing book balance from the previous report. ClosingAvailable Closing balance of amount of money that is at the disposal of the account owner on the date specified. Additional info: Some other codes (see list of BalanceType12Code) may be used with a preagreement between parties Proprietary <Prtry> This message item is part of choice 2.25 CodeOrProprietary. Balance type, in a proprietary form. Data Type: Max35Text Format: maxlength: SubType <SubTp> Type: Specifies the balance sub-type. This message item is composed of one of the following BalanceSubType1Choice element(s): Additional info: This field will not be used. 43/176

44 2.29 Code <Cd> This message item is part of choice 2.28 SubType. Specifies the code for the type of a balance, eg, opening booked balance. Data Type: ExternalBalanceSubType1Code Format: maxlength: Amount <Amt> Amount of money of the cash balance. Data Type: ActiveOrHistoricCurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode. Format: ActiveOrHistoricCurrencyAndAmount fractiondigits: 5 mininclusive: 0 totaldigits: 18 ActiveOrHistoricCurrencyCode [A-Z]{3,3} Rule(s): ActiveOrHistoricCurrencyAndAmount CurrencyAmount The number of fractional digits (or minor unit of currency) must comply with ISO Note: The decimal separator is a dot. ActiveOrHistoricCurrencyCode ActiveOrHistoricCurrency The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged. 44/176

45 2.35 CreditDebitIndicator <CdtDbtInd> Data Type: Code Indicates whether the balance is a credit or a debit balance. A zero balance is considered to be a credit balance One of the following CreditDebitCode values must be used: 2.36 Date <Dt> Type: Specifies the date (and time) of the balance. This message item is composed of one of the following DateAndDateTimeChoice element(s): Date <Dt> This message item is part of choice 4.1 DateAndDateTimeChoice. Specified date. Data Type: ISODate 45/176

46 2.43 TransactionsSummary <TxsSummry> Set of element providing summary information on entries. Type: This message item is composed of the following TotalTransactions1 element(s): 2.44 TotalEntries <TtlNtries> Specifies the total number and sum of debit and credit entries. Type: This message item is composed of the following NumberAndSumOfTransactions2 element(s): 46/176

47 2.45 NumberOfEntries <NbOfNtries> Number of individual entries included in the report. Data Type: Max15NumericText Format: [0-9]{1,15} 2.46 Sum <Sum> Total of all individual entries included in the report. Data Type: DecimalNumber Format: fractiondigits: 17 totaldigits: TotalNetEntryAmount <TtlNetNtryAmt> Resulting amount of the netted amounts for all debit and credit entries. Data Type: DecimalNumber Format: fractiondigits: 17 totaldigits: CreditDebitIndicator <CdtDbtInd> Indicates whether the total net entry amount is a credit or a debit amount. Data Type: Code When this message item is present, one of the following CreditDebitCode values must be used: 47/176

48 2.49 TotalCreditEntries <TtlCdtNtries> Indicates the total number and sum of credit entries. Type: This message item is composed of the following NumberAndSumOfTransactions1 element(s): 2.50 NumberOfEntries <NbOfNtries> Number of individual entries included in the report. Data Type: Max15NumericText Format: [0-9]{1,15} 2.51 Sum <Sum> Total of all individual entries included in the report. Data Type: DecimalNumber Format: fractiondigits: 17 totaldigits: 18 48/176

49 2.52 TotalDebitEntries <TtlDbtNtries> Indicates the total number and sum of debit entries. Type: This message item is composed of the following NumberAndSumOfTransactions1 element(s): 2.53 NumberOfEntries <NbOfNtries> Number of individual entries included in the report. Data Type: Max15NumericText Format: [0-9]{1,15} 2.54 Sum <Sum> Total of all individual entries included in the report. Data Type: DecimalNumber Format: fractiondigits: 17 totaldigits: 18 49/176

50 2.76 Entry <Ntry> Presence: Usage: Type: [0..n] Specifies the elements of an entry in the statement. At least one reference must be provided to identify the entry and its underlying transaction(s). This message item is composed of the following StatementEntry1 element(s): 50/176

51 2.77 EntryReference <NtryRef> Data Type: Max35Text Unique reference for the entry. Format: maxlength: Amount <Amt> Amount of money in the cash entry. Data Type: ActiveOrHistoricCurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode. Format: ActiveOrHistoricCurrencyAndAmount fractiondigits: 5 mininclusive: 0 totaldigits: 18 ActiveOrHistoricCurrencyCode 51/176

52 [A-Z]{3,3} Rule(s): CurrencyAmount ActiveOrHistoricCurrencyAndAmount The number of fractional digits (or minor unit of currency) must comply with ISO Note: The decimal separator is a dot. (Fatal) Error Code: Sw.Stds.D00007 ActiveOrHistoricCurrencyCode ActiveOrHistoricCurrency The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged CreditDebitIndicator <CdtDbtInd> Specifies if an entry is a credit or a debit. Data Type: Code One of the following CreditDebitCode values must be used: 2.80 ReversalIndicator <RvslInd> Usage: Indicates whether the entry is the result of a reversal operation. this element should only be present if the entry is the result of a reversal operation. If the CreditDebitIndicator is CRDT and ReversalIndicator is Yes, the original operation was a debit entry. If the CreditDebitIndicator is DBIT and ReversalIndicator is Yes, the original operation was a credit entry. Data Type: One of the following TrueFalseIndicator values must be used: MeaningWhenTrue: True MeaningWhenFalse: False 52/176

53 2.81 Status <Sts> Status of an entry on the books of the account servicer. Data Type: Code Only the following EntryStatus3Code values must be used: 2.82 BookingDate <BookgDt> Type: Date and time when an entry is posted to an account on the account servicer's books. This message item is composed of the following DateAndDateTimeChoice element: 53/176

54 4.1.0 Date <Dt> This message item is part of choice 4.1 DateAndDateTimeChoice. Specified date. Data Type: ISODate 2.83 ValueDate <ValDt> Usage: Type: Date and time assets become available to the account owner (in a credit entry), or cease to be available to the account owner (in a debit entry). For entries which are subject to availability/float (and for which availability information is present), value date must not be used, as the availability component identifies the number of availability days. This message item is composed of the following DateAndDateTimeChoice element: Date <Dt> This message item is part of choice 4.1 DateAndDateTimeChoice. Specified date. Data Type: ISODate 54/176

55 2.84 AccountServicerReference <AcctSvcrRef> Data Type: Max35Text Unique reference as assigned by the account servicing institution to unambiguously identify the entry. Format: maxlength: 35 Additional info: It is known as the bank's reference 2.91 BankTransactionCode <BkTxCd> Type: Rule(s): Set of elements to fully identify the type of underlying transaction resulting in an entry. This message item is composed of the following BankTransactionCodeStructure1 element(s): DomainOrProprietaryRule Either Proprietary or Domain or both must be present. FamilyAndSubFamilyRule If a specific (non-generic) Family code is not present, then a specific (non-generic) SubFamily code is not allowed. 55/176

56 Additional info: It is known as the accounting code 2.92 Domain <Domn> Presence: Usage: Type: [0..1], R2 Set of elements used to provide the domain, the family and the sub-family of the bank transaction code, in a structured and hierarchical format. If a specific family or sub-family code cannot be provided, the generic family code defined for the domain or the generic sub-family code defined for the family should be provided. This message item is composed of the following BankTransactionCodeStructure5 element(s): Additional info: This structured information is not currently used; field 2.97 is preferred Code <Cd> Specifies the business area of the underlying transaction. Data Type: ExternalBankTransactionDomainCode Format: maxlength: 4 56/176

57 2.94 Family <Fmly> Type: Specifies the family and the sub-family of the bank transaction code, within a specific domain, in a structured and hierarchical format. This message item is composed of the following BankTransactionCodeStructure3 element(s): 2.95 Code <Cd> Specifies the family within a domain. Data Type: ExternalBankTransactionFamilyCode Format: maxlength: SubFamilyCode <SubFmlyCd> Specifies the sub-product family within a specific family. Data Type: ExternalBankTransactionSubFamilyCode Format: maxlength: 4 57/176

58 2.97 Proprietary <Prtry> Proprietary identification of the bank transaction code, as defined by the issuer. Type: This message item is composed of the following ProprietaryBankTransactionCodeStructure1 element(s): 2.98 Code <Cd> Proprietary bank transaction code to identify the underlying transaction. Data Type: Max35Text Format: maxlength: Issuer <Issr> Identification of the issuer of the proprietary bank transaction code. Data Type: Max35Text Format: maxlength: 35 58/176

59 2.101 AdditionalInformationIndicator <AddtlInfInd> Type: Indicates whether the underlying transaction details are provided through a separate message, as in the case of aggregate bookings. This message item is composed of the following MessageIdentification2 element(s): Additional info: In Luxembourg, this field is not used MessageNameIdentification <MsgNmId> Specifies the message name identifier of the message that will be used to provide additional details. Data Type: Max35Text Format: maxlength: MessageIdentification <MsgId> Specifies the identification of the message that will be used to provide additional details. Data Type: Max35Text Format: maxlength: 35 59/176

60 2.104 AmountDetails <AmtDtls> Usage : Type: Set of elements providing information on the original amount. This component (on entry level) should be used when a total original batch or aggregate amount has to be provided. (If required, the original amounts for each individual transaction can be included in the same component on transaction details level.) This message item is composed of the following AmountAndCurrencyExchange3 element(s): Additional info: Generally, this field is not used on the level "Entry", but on the TransactionDetails level. 60/176

61 2.1.0 InstructedAmount <InstdAmt> Identifies the amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party and provides currency exchange info in case the instructed amount and/or currency is/are different from the entry amount and/or currency. Type: This message item is composed of the following AmountAndCurrencyExchangeDetails3 element(s): Amount <Amt> Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. Data Type: CurrencyAndAmount Format: fractiondigits: 5 mininclusive: 0 totaldigits: 18 CurrencyCode [A-Z]{3,3} Rule(s): ValidationByTable This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode. CurrencyAndAmount CurrencyCode 61/176

62 2.1.9 TransactionAmount <TxAmt> Amount of the underlying transaction. Type: This message item is composed of the following AmountAndCurrencyExchangeDetails3 element(s): Amount <Amt> Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. Data Type: ActiveOrHistoricCurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode. Format: fractiondigits: 5 mininclusive: 0 totaldigits: 18 ActiveOrHistoricCurrencyAndAmount ActiveOrHistoricCurrencyCode [A-Z]{3,3} Rule(s): CurrencyAmount ActiveOrHistoricCurrencyAndAmount 62/176

63 CounterValueAmount <CntrValAmt> Usage: Set of elements used to provide the countervalue amount and currency exchange information. This can be either the counter amount quoted in an FX deal, or the result of the currency information applied to an instructed amount, before deduction of charges. Type: This message item is composed of the following AmountAndCurrencyExchangeDetails3 element(s): Amount <Amt> Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. Data Type: CurrencyAndAmount Format: fractiondigits: 5 mininclusive: 0 totaldigits: 18 CurrencyCode [A-Z]{3,3} Rule(s): ValidationByTable This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode. CurrencyAndAmount CurrencyCode 63/176

64 CurrencyExchange <CcyXchg> Type: Reports on currency exchange information. This message item is composed of the following CurrencyExchange3 element(s): SourceCurrency <SrcCcy> UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007 Message Item Types Page 343 Currency of the amount to be converted in a currency conversion. Data Type: CurrencyCode Format: Rule(s): [A-Z]{3,3} ValidationByTable TargetCurrency <TrgtCcy> Currency into which an amount is to be converted in a currency conversion. Data Type: CurrencyCode Format: Rule(s): [A-Z]{3,3} ValidationByTable 64/176

65 UnitCurrency <UnitCcy> Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxcur, the unit currency is GBP. Data Type: CurrencyCode Format: Rule(s): [A-Z]{3,3} ValidationByTable ExchangeRate <XchgRate> Synonym(s): :92A::EXCH (ISO 15022) Usage: Data Type: BaseOneRate Factor used for the conversion of an amount from one currency into another. This reflects the price at which one currency was bought with another currency. ExchangeRate expresses the ratio between UnitCurrency and QuotedCurrency (ExchangeRate = UnitCurrency/QuotedCurrency). Format: fractiondigits: 10 ; totaldigits: ProprietaryAmount <PrtryAmt> Presence: [0..n] Set of elements used to provide information on the original amount and currency exchange. Type: This message item is composed of the following AmountAndCurrencyExchangeDetails4 element(s): 65/176

66 Type <Tp> Specifies the type of amount. Data Type: Max35Text Format: maxlength: Amount <Amt> Amount of money to be exchanged against another amount of money in the counter currency. Data Type: ActiveOrHistoricCurrencyAndAmount Format: fractiondigits: 5 mininclusive: 0 totaldigits: 18 This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode. ActiveOrHistoricCurrencyAndAmount ActiveOrHistoricCurrencyCode [A-Z]{3,3} Rule(s): CurrencyAmount ActiveOrHistoricCurrencyAndAmount The number of fractional digits (or minor unit of currency) must comply with ISO Note: The decimal separator is a dot. ActiveOrHistoricCurrencyCode ActiveOrHistoricCurrency The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged. 66/176

67 2.105 Charges <Chrgs> Presence: Usage: Type: [0..n] Provides information on the charges included in the entry amount. This component is used on entry level in case of batch or aggregate bookings. This message item is composed of the following ChargesInformation6 element(s): Amount <Amt> Transaction charges to be paid by the charge bearer. Data Type: ActiveOrHistoricCurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode. Format: ActiveOrHistoricCurrencyAndAmount fractiondigits: 5 mininclusive: 0 totaldigits: 18 ActiveOrHistoricCurrencyCode 67/176

68 [A-Z]{3,3} Rule(s): CurrencyAmount ActiveOrHistoricCurrencyAndAmount The number of fractional digits (or minor unit of currency) must comply with ISO Note: The decimal separator is a dot. ActiveOrHistoricCurrencyCode ActiveOrHistoricCurrency The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged CreditDebitIndicator <CdtDbtInd> Indicates whether the charges amount is a credit or a debit amount. Usage: A zero amount is considered to be a credit. Data Type: Code When this message item is present, one of the following CreditDebitCode values must be used: Type <Tp> Specifies the type of charge. Type: This message item is composed of the following ChargeType2Choice element: 68/176

69 2.111 Proprietary <Prtry> This message item is part of choice Type. Type of charge in a proprietary form, as defined by the issuer. Type: This message item is composed of the following GenericIdentification3 element(s): Identification <Id> Name or number assigned by an entity to enable recognition of that entity, eg, account identifier. Data Type: Max35Text Format: maxlength: Issuer <Issr> Data Type: Max35Text Entity that assigns the identification. Format: maxlength: 35 69/176

70 2.112 Rate <Rate> Rate used to calculate the amount of the charge or fee. Data Type: PercentageRate Format: fractiondigits: 10 totaldigits: Tax <Tax> Type: Set of elements used to provide details on the tax applied to charges. This message item is composed of the following TaxCharges2 element(s): Identification <Id> Unique reference to unambiguously identify the nature of the tax levied, such as Value Added Tax (VAT) Data Type: Max35Text Format: maxlength: 35 70/176

71 2.117 Rate <Rate> Rate used to calculate the tax. Data Type: PercentageRate Format: fractiondigits: 10 totaldigits: Amount <Amt> Amount of money resulting from the calculation of the tax. Data Type: ActiveOrHistoricCurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode. Format: ActiveOrHistoricCurrencyAndAmount fractiondigits: 5 mininclusive: 0 totaldigits: 18 ActiveOrHistoricCurrencyCode [A-Z]{3,3} Rule(s): ActiveOrHistoricCurrencyAndAmount CurrencyAmount The number of fractional digits (or minor unit of currency) must comply with ISO Note: The decimal separator is a dot. ActiveOrHistoricCurrencyCode ActiveOrHistoricCurrency The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged. 71/176

72 2.135 EntryDetails <NtryDtls> Presence: Type: [0..n] Set of elements used to provide details on the entry. This message item is composed of the following EntryDetails1 element(s): USAGE: In case of n single transactions, the field EntryDetails will be used n-times; Batch <Btch> Set of elements used to provide details on batched transactions. Type: This message item is composed of the following BatchInformation2 element(s): USAGE: This item will be used only in case of reporting related to globalized transactions booked on the account. 72/176

73 2.137 MessageIdentification <MsgId> Point to point reference, as assigned by the sending party, to unambiguously identify the batch of transactions. Data Type: Max35Text Format: maxlength: PaymentInformationIdentification <PmtInfId> Unique identification, as assigned by a sending party, to unambiguously identify the payment information group within the message. Data Type: Max35Text Format: maxlength: 35 73/176

74 2.139 NumberOfTransactions <NbOfTxs> Number of individual transactions included in the batch. Data Type: Max15NumericText Format: [0-9]{1,15} TotalAmount <TtlAmt> Total amount of money reported in the batch entry. Data Type: ActiveOrHistoricCurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode. Format: ActiveOrHistoricCurrencyAndAmount fractiondigits: 5 mininclusive: 0 totaldigits: 18 ActiveOrHistoricCurrencyCode [A-Z]{3,3} Rule(s): ActiveOrHistoricCurrencyAndAmount CurrencyAmount The number of fractional digits (or minor unit of currency) must comply with ISO Note: The decimal separator is a dot. ActiveOrHistoricCurrencyCode ActiveOrHistoricCurrency The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged. 74/176

75 2.141 CreditDebitIndicator <CdtDbtInd> Indicates whether the batch entry is a credit or a debit entry. Data Type: Code When this message item is present, one of the following CreditDebitCode values must be used: TransactionDetails <TxDtls> Presence: [0..n] 75/176

76 Type: Set of elements providing information on the underlying transaction (s). This message item is composed of the following EntryTransaction2 element(s): References <Refs> Type: Set of elements used to provide the identification of the underlying transaction. This message item is composed of the following TransactionReferences2 element(s): 76/176

77 2.144 MessageIdentification <MsgId> Point to point reference assigned by the instructing party of the underlying message. Data Type: Max35Text Format: maxlength: AccountServicerReference <AcctSvcrRef> The account servicing institution's reference for the transaction. Data Type: Max35Text Format: maxlength: PaymentInformationIdentification <PmtInfId> 77/176

78 Unique identification, as assigned by a sending party, to unambiguously identify the payment information group within the message InstructionIdentification <InstrId> Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. Usage: Data Type: Max35Text the instruction identification is a point-to-point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction. Format: maxlength: EndToEndIdentification <EndToEndId> Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. Usage: Data Type: Max35Text The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. In case there are technical limitations to pass on multiple references, the end-to-end identification must be passed on throughout the entire end-to-end chain. Format: maxlength: 35 78/176

79 2.149 TransactionIdentification <TxId> Usage: Usage: Data Type: Max35Text Unique identification, as assigned by the first instructing agent, to unambiguously identify the transaction that is passed on, unchanged, throughout the entire interbank chain. The transaction identification can be used for reconciliation, tracking or to link tasks relating to the transaction on the interbank level. The instructing agent has to make sure that the transaction identification is unique for a pre-agreed period. Format: maxlength: MandateIdentification <MndtId> Reference of the direct debit mandate that has been signed between by the debtor and the creditor. Data Type: Max35Text Format: maxlength: ChequeNumber <ChqNb> Unique and unambiguous identifier for a cheque as assigned by the agent. Data Type: Max35Text Format: maxlength: 35 79/176

80 2.156 AmountDetails <AmtDtls> Usage: Type: Set of elements providing details information on the original amount. This component (on transaction level) should be used in case booking is for a single transaction and the original amount is different from the entry amount. It can also be used in case individual original amounts are provided in case of a batch or aggregate booking. This message item is composed of the following AmountAndCurrencyExchange3 element(s): 80/176

81 2.1.0 InstructedAmount <InstdAmt> Identifies the amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party and provides currency exchange info in case the instructed amount and/or currency is/are different from the entry amount and/or currency. Type: This message item is composed of the following AmountAndCurrencyExchangeDetails3 element(s): Amount <Amt> Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. Data Type: CurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode. Format: fractiondigits: 5 mininclusive: 0 totaldigits: 18 CurrencyCode [A-Z]{3,3} Rule(s): ValidationByTable CurrencyAndAmount CurrencyCode 81/176

82 2.1.9 TransactionAmount <TxAmt> Amount of the underlying transaction. Type: This message item is composed of the following AmountAndCurrencyExchangeDetails3 element(s): Amount <Amt> Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. Data Type: ActiveOrHistoricCurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode. Format: fractiondigits: 5 mininclusive: 0 totaldigits: 18 ActiveOrHistoricCurrencyAndAmount ActiveOrHistoricCurrencyCode [A-Z]{3,3} Rule(s): CurrencyAmount ActiveOrHistoricCurrencyAndAmount 82/176

83 CounterValueAmount <CntrValAmt> Usage: Set of elements used to provide the countervalue amount and currency exchange information. This can be either the counter amount quoted in an FX deal, or the result of the currency information applied to an instructed amount, before deduction of charges. Type: This message item is composed of the following AmountAndCurrencyExchangeDetails3 element(s): Amount <Amt> Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. Data Type: CurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode. Format: fractiondigits: 5 mininclusive: 0 totaldigits: 18 CurrencyCode [A-Z]{3,3} Rule(s): ValidationByTable CurrencyAndAmount CurrencyCode 83/176

84 CurrencyExchange <CcyXchg> Type: Reports on currency exchange information. This message item is composed of the following CurrencyExchange5 element(s): SourceCurrency <SrcCcy> UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007 Message Item Types Page 343 Currency of the amount to be converted in a currency conversion. Data Type: CurrencyCode Format: Rule(s): [A-Z]{3,3} ValidationByTable TargetCurrency <TrgtCcy> Currency into which an amount is to be converted in a currency conversion. Data Type: CurrencyCode Format: Rule(s): [A-Z]{3,3} ValidationByTable 84/176

85 UnitCurrency <UnitCcy> Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxcur, the unit currency is GBP. Data Type: CurrencyCode Format: Rule(s): [A-Z]{3,3} ValidationByTable ExchangeRate <XchgRate> Synonym(s): :92A::EXCH (ISO 15022) Factor used for the conversion of an amount from one currency into another. This reflects the price at which one currency was bought with another currency. Usage: Data Type: BaseOneRate ExchangeRate expresses the ratio between UnitCurrency and QuotedCurrency (ExchangeRate = UnitCurrency/QuotedCurrency). Format: fractiondigits: 10 ; totaldigits: ProprietaryAmount <PrtryAmt> Presence: [0..n] Set of elements used to provide information on the original amount and currency exchange. Type: This message item is composed of the following AmountAndCurrencyExchangeDetails4 element(s): 85/176

86 Type <Tp> Specifies the type of amount. Data Type: Max35Text Format: maxlength: Amount <Amt> Amount of money to be exchanged against another amount of money in the counter currency. Data Type: ActiveOrHistoricCurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode. Format: fractiondigits: 5 mininclusive: 0 totaldigits: 18 ActiveOrHistoricCurrencyAndAmount ActiveOrHistoricCurrencyCode [A-Z]{3,3} Rule(s): CurrencyAmount ActiveOrHistoricCurrencyAndAmount The number of fractional digits (or minor unit of currency) must comply with ISO Note: The decimal separator is a dot. ActiveOrHistoricCurrencyCode 86/176

87 ActiveOrHistoricCurrency The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged BankTransactionCode <BkTxCd> Set of elements used to fully identify the type of underlying transaction resulting in an entry. Type: This message item is composed of the following BankTransactionCodeStructure4 element(s): 87/176

88 2.164 Domain <Domn> Presence: Usage: Type: [0..1], R2 Set of elements used to provide the domain, the family and the sub-family of the bank transaction code, in a structured and hierarchical format. If a specific family or sub-family code cannot be provided, the generic family code defined for the domain or the generic sub-family code defined for the family should be provided. This message item is composed of the following BankTransactionCodeStructure5 element(s): Code <Cd> Specifies the business area of the underlying transaction. Data Type: ExternalBankTransactionDomainCode Format: maxlength: Family <Fmly> Specifies the family and the sub-family of the bank transaction code, within a specific domain, in a structured and hierarchical format. Type: This message item is composed of the following BankTransactionCodeStructure6 element(s): 88/176

89 2.167 Code <Cd> Specifies the family within a domain. Data Type: ExternalBankTransactionFamilyCode Format: maxlength: SubFamilyCode <SubFmlyCd> Specifies the sub-product family within a specific family. Data Type: ExternalBankTransactionSubFamily1Code Format: maxlength: Proprietary <Prtry> Presence: [0..1], R2 Bank transaction code in a proprietary form, as defined by the issuer. 89/176

90 Type: This message item is composed of the following ProprietaryBankTransactionCodeStructure1 element(s): Code <Cd> Proprietary bank transaction code to identify the underlying transaction. Data Type: Max35Text Format: maxlength: Issuer <Issr> Identification of the issuer of the proprietary bank transaction code. Data Type: Max35Text Format: maxlength: 35 90/176

91 2.172 Charges <Chrgs> Presence: Usage: Type: [0..n] Provides information on the charges included in the entry amount. This component is used on entry level in case of batch or aggregate bookings. This message item is composed of the following ChargesInformation6 element(s): Amount <Amt> Transaction charges to be paid by the charge bearer. Data Type: ActiveOrHistoricCurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode. Format: ActiveOrHistoricCurrencyAndAmount fractiondigits: 5 mininclusive: 0 totaldigits: 18 ActiveOrHistoricCurrencyCode 91/176

92 [A-Z]{3,3} Rule(s): CurrencyAmount ActiveOrHistoricCurrencyAndAmount The number of fractional digits (or minor unit of currency) must comply with ISO Note: The decimal separator is a dot. ActiveOrHistoricCurrencyCode ActiveOrHistoricCurrency The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged CreditDebitIndicator <CdtDbtInd> Indicates whether the charges amount is a credit or a debit amount. Usage: A zero amount is considered to be a credit. Data Type: Code When this message item is present, one of the following CreditDebitCode values must be used: Type <Tp> Type: Specifies the type of charge. This message item is composed of the following ChargeType2Choice element: 92/176

93 2.178 Proprietary <Prtry> This message item is part of choice Type. Type of charge in a proprietary form, as defined by the issuer. Type: This message item is composed of the following GenericIdentification3 element(s): Identification <Id> Name or number assigned by an entity to enable recognition of that entity, eg, account identifier. Data Type: Max35Text Format: maxlength: Issuer <Issr> Entity that assigns the identification. Data Type: Max35Text 93/176

94 Format: maxlength: Rate <Rate> Rate used to calculate the amount of the charge or fee. Data Type: PercentageRate Format: fractiondigits: 10 totaldigits: Tax <Tax> Type: Set of elements used to provide details on the tax applied to charges. This message item is composed of the following TaxCharges2 element(s): 94/176

95 2.183 Identification <Id> Data Type: Max35Text Unique reference to unambiguously identify the nature of the tax levied, such as Value Added Tax (VAT) Format: maxlength: Rate <Rate> Rate used to calculate the tax. Data Type: PercentageRate Format: fractiondigits: 10 totaldigits: Amount <Amt> Amount of money resulting from the calculation of the tax. Data Type: ActiveOrHistoricCurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode. Format: ActiveOrHistoricCurrencyAndAmount fractiondigits: 5 mininclusive: 0 totaldigits: 18 ActiveOrHistoricCurrencyCode [A-Z]{3,3} Rule(s): ActiveOrHistoricCurrencyAndAmount CurrencyAmount 95/176

96 The number of fractional digits (or minor unit of currency) must comply with ISO Note: The decimal separator is a dot. ActiveOrHistoricCurrencyCode ActiveOrHistoricCurrency The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged Interest <Intrst> Presence: Usage: Type: [0..n] Set of elements used to provide details of the interest amount included in the entry amount. This component (on transaction level) can be used if the booking is for a single transaction, and interest amount is included in the entry amount. It can also be used if individual interest amounts are applied to individual transactions in the case of a batch or aggregate amount booking. This message item is composed of the following TransactionInterest2 element(s): 96/176

97 2.187 Amount <Amt> Amount of interest included in the entry amount. Data Type: ActiveOrHistoricCurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode. Format: ActiveOrHistoricCurrencyAndAmount fractiondigits: 5 mininclusive: 0 totaldigits: 18 ActiveOrHistoricCurrencyCode [A-Z]{3,3} Rule(s): ActiveOrHistoricCurrencyAndAmount CurrencyAmount The number of fractional digits (or minor unit of currency) must comply with ISO Note: The decimal separator is a dot. (Fatal) Error Code: Sw.Stds.D00007 ActiveOrHistoricCurrencyCode ActiveOrHistoricCurrency The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged. 97/176

98 2.188 CreditDebitIndicator <CdtDbtInd> Indicates whether the interest amount included in the entry is credit or debit amount. Data Type: Code One of the following CreditDebitCode values must be used: Type <Tp> Type: Specifies the type of interest. This message item is composed of the following InterestType1Choice element: Proprietary <Prtry> This message item is part of choice Type. Specifies the type of interest in uncoded form. Data Type: Max35Text Format: maxlength: 35 98/176

99 2.192 Rate <Rate> Presence: Type: [0..n] Set of elements used to qualify the interest rate. This message item is composed of the following Rate3 element(s): Type <Tp> Type: Specifies the type of interest rate. This message item is composed of one of the following RateType4Choice element(s): Percentage <Pctg> This message item is part of choice Type. Ratio of the amount of interest paid during a certain period of time compared to the principal amount of the interest bearing financial instrument. Data Type: PercentageRate Format: fractiondigits: 10 totaldigits: 11 99/176

100 2.195 Other <Othr> This message item is part of choice Type. Data Type: Max35Text Rate type expressed, in an other form. Format: maxlength: FromToDate <FrToDt> Type: Range of time between a start date and an end date for the calculation of the interest. This message item is composed of the following DateTimePeriodDetails element(s): For additional Type information, please refer to DateTimePeriodDetails p.611 in 'Message Item Types' section FromDateTime <FrDtTm> Date and time at which the range starts. Data Type: ISODateTime 100/176

101 5.1.1 ToDateTime <ToDtTm> Date and time at which the range ends. Data Type: ISODateTime RelatedParties <RltdPties> Set of elements used to identify the parties related to the underlying transaction. Type: This message item is composed of the following TransactionParty2 element(s): 101/176

102 2.200 InitiatingParty <InitgPty> Party that initiated the payment that is reported in the entry. Type: This message item is composed of the following PartyIdentification32 element(s): Name <Nm> Name by which a party is known and which is usually used to identify that party. Data Type: Max140Text Format: maxlength: /176

103 9.1.1 PostalAddress <PstlAdr> Type: Information that locates and identifies a specific address, as defined by postal services. This message item is composed of the following PostalAddress6 element(s): StreetName <StrtNm> Name of a street or thoroughfare. Data Type: Max70Text Format: maxlength: /176

104 9.1.6 BuildingNumber <BldgNb> Data Type: Max16Text Number that identifies the position of a building on a street. Format: maxlength: PostCode <PstCd> Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail. Data Type: Max16Text Format: maxlength: TownName <TwnNm> Name of a built-up area, with defined boundaries, and a local government. Data Type: Max35Text Format: maxlength: /176

105 Country <Ctry> Data Type: CountryCode Format: Rule(s): Nation with its own government. [A-Z]{2,2} Country The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code) AddressLine <AdrLine> Presence: [0..7] Information that locates and identifies a specific address, as defined by postal services, presented in free format text. Data Type: Max70Text Format: maxlength: /176

106 2.201 Debtor <Dbtr> Type: Party that owes an amount of money to the (ultimate) creditor. This message item is composed of the following PartyIdentification32 element(s): For additional Type information, please refer to PartyIdentification32 p.882 in 'Message Item Types' section Name <Nm> Name by which a party is known and which is usually used to identify that party. Data Type: Max140Text Format: maxlength: /176

107 9.1.1 PostalAddress <PstlAdr> Type: Information that locates and identifies a specific address, as defined by postal services. This message item is composed of the following PostalAddress6 element(s): StreetName <StrtNm> Name of a street or thoroughfare. Data Type: Max70Text Format: maxlength: /176

108 9.1.6 BuildingNumber <BldgNb> Data Type: Max16Text Number that identifies the position of a building on a street. Format: maxlength: PostCode <PstCd> Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail. Data Type: Max16Text Format: maxlength: TownName <TwnNm> Name of a built-up area, with defined boundaries, and a local government. Data Type: Max35Text Format: maxlength: /176

109 Country <Ctry> Data Type: CountryCode Format: Rule(s): Nation with its own government. [A-Z]{2,2} Country The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code) AddressLine <AdrLine> Presence: [0..7] Information that locates and identifies a specific address, as defined by postal services, presented in free format text. Data Type: Max70Text Format: maxlength: Identification <Id> Type: Unique and unambiguous identification of a party. This message item is composed of one of the following Party6Choice element(s): 109/176

110 OrganisationIdentification <OrgId> This message item is part of choice Identification. Type: Unique and unambiguous way to identify an organisation. This message item is composed of the following OrganisationIdentification4 element(s): BICOrBEI <BICOrBEI> Code allocated to organisations by the ISO 9362 Registration Authority, under an international identification scheme, as described in the latest version of the standard ISO 9362 Banking (Banking telecommunication messages, Bank Identifier Codes). The Ba Data Type: AnyBICIdentifier Format: Rule(s): [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1} AnyBIC Only a valid BIC or BEI is allowed. Valid BEI and BIC are registered with the ISO 9362 Registration Authority, and consists of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: BANK CODE, COUNTRY CODE, LOCATION CODE, BRANCH CODE. The bank code, country code and location code are mandatory, while the branch code is optional. 110/176

111 2.202 DebtorAccount <DbtrAcct> Type: Unambiguous identification of the account of the debtor. This message item is composed of the following CashAccount16 element(s): Identification <Id> Unique and unambiguous identification for the account between the account owner and the account servicer. Type: This message item is composed of one of the following AccountIdentification4Choice element(s): 111/176

112 1.1.1 IBAN <IBAN> This message item is part of choice Identification. International Bank Account Number (IBAN) - identifier used internationally by financial institutions to uniquely identify the account of a customer. Further specifications of the format and content of the IBAN can be found in the standard ISO "Banking and related financial services - International Bank Account Number (IBAN)" version , or later revisions. Data Type: IBAN2007Identifier Format: Rule(s): [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30} IBAN Other <Othr> This message item is part of choice Identification. Unique identification of an account, as assigned by the account servicer, using an identification scheme. Type: This message item is composed of the following GenericAccountIdentification1 element(s): 112/176

113 1.1.3 Identification <Id> Data Type: Max34Text Identification assigned by an institution. Format: maxlength: Issuer <Issr> Entity that assigns the identification. Data Type: Max35Text Format: maxlength: UltimateDebtor <UltmtDbtr> Ultimate party that owes an amount of money to the (ultimate) creditor. Type: This message item is composed of the following PartyIdentification32 element(s): 113/176

114 9.1.0 Name <Nm> Data Type: Max140Text Name by which a party is known and which is usually used to identify that party. Format: maxlength: PostalAddress <PstlAdr> Information that locates and identifies a specific address, as defined by postal services. Type: This message item is composed of the following PostalAddress6 element(s): 114/176

115 9.1.5 StreetName <StrtNm> Data Type: Max70Text Name of a street or thoroughfare. Format: maxlength: BuildingNumber <BldgNb> Number that identifies the position of a building on a street. Data Type: Max16Text Format: maxlength: PostCode <PstCd> Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail. Data Type: Max16Text Format: maxlength: /176

116 9.1.8 TownName <TwnNm> Data Type: Max35Text Name of a built-up area, with defined boundaries, and a local government. Format: maxlength: Country <Ctry> Nation with its own government. Data Type: CountryCode Format: [A-Z]{2,2} Rule(s): Country The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code) AddressLine <AdrLine> Presence: [0..7] Information that locates and identifies a specific address, as defined by postal services, presented in free format text. Data Type: Max70Text Format: maxlength: /176

117 2.204 Creditor <Cdtr> Party to which an amount of money is due. Type: This message item is composed of the following PartyIdentification32 element(s): Name <Nm> Name by which a party is known and which is usually used to identify that party. Data Type: Max140Text Format: maxlength: /176

118 9.1.1 PostalAddress <PstlAdr> Type: Information that locates and identifies a specific address, as defined by postal services. This message item is composed of the following PostalAddress6 element(s): StreetName <StrtNm> Name of a street or thoroughfare. Data Type: Max70Text Format: maxlength: /176

119 9.1.6 BuildingNumber <BldgNb> Data Type: Max16Text Number that identifies the position of a building on a street. Format: maxlength: PostCode <PstCd> Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail. Data Type: Max16Text Format: maxlength: TownName <TwnNm> Name of a built-up area, with defined boundaries, and a local government. Data Type: Max35Text Format: maxlength: /176

120 Country <Ctry> Data Type: CountryCode Format: Rule(s): Nation with its own government. [A-Z]{2,2} Country The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code) AddressLine <AdrLine> Presence: [0..7] Information that locates and identifies a specific address, as defined by postal services, presented in free format text. Data Type: Max70Text Format: maxlength: Identification <Id> Unique and unambiguous identification of a party. 120/176

121 Type: This message item is composed of one of the following Party6Choice element(s): OrganisationIdentification <OrgId> This message item is part of choice Identification. Unique and unambiguous way to identify an organisation. Type: This message item is composed of the following OrganisationIdentification4 element(s): BICOrBEI <BICOrBEI> Code allocated to organisations by the ISO 9362 Registration Authority, under an international identification scheme, as described in the latest version of the standard ISO 9362 Banking (Banking telecommunication messages, Bank Identifier Codes). The Ba Data Type: AnyBICIdentifier Format: Rule(s): [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1} AnyBIC Only a valid BIC or BEI is allowed. Valid BEI and BIC are registered with the ISO 9362 Registration Authority, and consists of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: BANK CODE, COUNTRY CODE, LOCATION CODE, BRANCH CODE. The bank code, country code and location code are mandatory, while the branch code is optional. 121/176

122 Other <Othr> Presence: [0..n] Unique identification of an organisation, as assigned by an institution, using an identification scheme Identification <Id> Identification assigned by an institution. Data Type: Max35Text Format: maxlength: CreditorAccount <CdtrAcct> Unambiguous identification of the account of the creditor of the payment transaction. Type: This message item is composed of the following CashAccount16 element(s): 122/176

123 1.1.0 Identification <Id> Unique and unambiguous identification for the account between the account owner and the account servicer. Type: This message item is composed of the following AccountIdentification4Choice element: IBAN <IBAN> This message item is part of choice Identification. International Bank Account Number (IBAN) - identifier used internationally by financial institutions to uniquely identify the account of a customer. Further specifications of the format and content of the IBAN can be found in the standard ISO "Banking and related financial services - International Bank Account Number (IBAN)" version , or later revisions. Data Type: IBAN2007Identifier Format: Rule(s): [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30} IBAN 123/176

124 1.1.2 Other <Othr> This message item is part of choice Identification. Type: Unique identification of an account, as assigned by the account servicer, using an identification scheme. This message item is composed of the following GenericAccountIdentification1 element(s): Identification <Id> Identification assigned by an institution. Data Type: Max34Text Format: maxlength: Issuer <Issr> Entity that assigns the identification. Data Type: Max35Text Format: maxlength: /176

125 2.206 UltimateCreditor <UltmtCdtr> Ultimate party to which an amount of money is due. Type: This message item is composed of the following PartyIdentification32 element(s): Name <Nm> Name by which a party is known and which is usually used to identify that party. Data Type: Max140Text Format: maxlength: /176

126 9.1.1 PostalAddress <PstlAdr> Type: Information that locates and identifies a specific address, as defined by postal services. This message item is composed of the following PostalAddress6 element(s): StreetName <StrtNm> Name of a street or thoroughfare. Data Type: Max70Text Format: maxlength: /176

127 9.1.6 BuildingNumber <BldgNb> Data Type: Max16Text Number that identifies the position of a building on a street. Format: maxlength: PostCode <PstCd> Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail. Data Type: Max16Text Format: maxlength: TownName <TwnNm> Name of a built-up area, with defined boundaries, and a local government. Data Type: Max35Text Format: maxlength: /176

128 Country <Ctry> Data Type: CountryCode Format: Rule(s): Nation with its own government. [A-Z]{2,2} Country The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code) AddressLine <AdrLine> Presence: [0..7] Information that locates and identifies a specific address, as defined by postal services, presented in free format text. Data Type: Max70Text Format: maxlength: /176

129 2.211 RelatedAgents <RltdAgts> Set of elements used to identify the agents related to the underlying transaction. Type: This message item is composed of the following TransactionAgents2 element(s): DebtorAgent <DbtrAgt> Financial institution servicing the account of the debtor. Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification4 element(s): For additional Type information, please refer to BranchAndFinancialInstitutionIdentification4 in 'Message Item Types' section. 129/176

130 6.1.0 FinancialInstitutionIdentification <FinInstnId> Unique and unambiguous identification of a financial institution, as assigned under an internationally recognised or proprietary identification scheme. Type: This message item is composed of the following FinancialInstitutionIdentification element BIC <BIC> Bank Identifier Code. Code allocated to financial institutions by the Registration Authority, under an international identification scheme, as described in the latest version of the standard ISO 9362 Banking (Banking telecommunication messages, Bank Identifier Codes). Data Type: BICIdentifier Format: Rule(s): [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1} BIC Valid BICs are registered with the ISO 9362 Registration Authority, and consist of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: BANK CODE COUNTRY CODE, LOCATION CODE, BRANCH CODE. The bank code, country code and location code are mandatory, while the branch code is optional CreditorAgent <CdtrAgt> Financial institution servicing the account of the creditor. Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification4 element(s): 130/176

131 For additional Type information, please refer to BranchAndFinancialInstitutionIdentification4 in 'Message Item Types' section FinancialInstitutionIdentification <FinInstnId> Unique and unambiguous identification of a financial institution, as assigned under an internationally recognised or proprietary identification scheme. Type: This message item is composed of the following FinancialInstitutionIdentification element BIC <BIC> Bank Identifier Code. Code allocated to financial institutions by the Registration Authority, under an international identification scheme, as described in the latest version of the standard ISO 9362 Banking (Banking telecommunication messages, Bank Identifier Codes). Data Type: BICIdentifier Format: Rule(s): [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1} BIC Valid BICs are registered with the ISO 9362 Registration Authority, and consist of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: BANK CODE COUNTRY CODE, LOCATION CODE, BRANCH CODE. The bank code, country code and location code are mandatory, while the branch code is optional. 131/176

132 2.224 Purpose <Purp> Usage: Type: Underlying reason for the payment transaction. Purpose is used by the end-customers, that is initiating party, (ultimate) debtor, (ultimate) creditor to provide information concerning the nature of the payment. Purpose is a content element, which is not used for processing by any of the agents involved in the payment chain. This message item is composed of the following Purpose2Choice element: Code <Cd> This message item is part of choice Purpose. Underlying reason for the payment transaction, as published in an external purpose code list. Data Type: ExternalPurpose1Code Format: maxlength: 4 Purpose code list (see appendix 6.1) 132/176

133 2.234 RemittanceInformation <RmtInf> Type: Structured information that enables the matching, ie, reconciliation, of a payment with the items that the payment is intended to settle, such as commercial invoices in an account receivable system. This message item is composed of the following RemittanceInformation5 element(s): Unstructured <Ustrd> Presence: Data Type: Max140Text [0..n] Information supplied to enable the matching/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts' receivable system, in an unstructured form. Format: maxlength: Structured <Strd> 133/176

134 Presence: [0..n] Information supplied to enable the matching/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts' receivable system, in a structured form. Type: This message item is composed of the following StructuredRemittanceInformation7 element(s): USAGE: see 4.2 Reporting of Structured Creditor references to RemittanceInformation item CreditorReferenceInformation <CdtrRefInf> Type: Reference information provided by the creditor to allow the identification of the underlying documents. This message item is composed of the following CreditorReferenceInformation2 element(s): 134/176

135 2.257 Type <Tp> Type: Specifies the type of creditor reference. This message item is composed of the following CreditorReferenceType2 element(s): CodeOrProprietary <CdOrPrtry> Coded or proprietary format creditor reference type. Type: This message item is composed of the following CreditorReferenceType1Choice element: <Cd> This message item is part of choice CodeOrProprietary. 135/176

136 Type of creditor reference, in a coded form. Data Type: Code One of the following DocumentType3Code values must be used: Issuer <Issr> Entity that assigns the credit reference type. Data Type: Max35Text Format: maxlength: Reference <Ref> Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. Usage: Data Type: Max35Text If available, the initiating party should provide this reference in the structured remittance information, 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 only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification. Format: maxlength: /176

137 2.266 RelatedDates <RltdDts> Set of elements identifying the dates related to the underlying transactions. Type: This message item is composed of the following TransactionDates2 element(s): AcceptanceDateTime <AccptncDtTm> Point in time when the payment order from the initiating party meets the processing conditions of the account servicing agent. This means that the account servicing agent has received the payment order and has applied checks such as authorisation, availability of funds. Data Type: ISODateTime Tax <Tax> Set of elements used to provide details on the tax. Amount of money due to the government or tax authority, according to various pre-defined parameters such as thresholds or income. Type: This message item is composed of the following TaxInformation3 element(s): 137/176

138 TotalTaxAmount <TtlTaxAmt> Total amount of money as result of the calculation of the tax. Data Type: ActiveOrHistoricCurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode. Format: ActiveOrHistoricCurrencyAndAmount fractiondigits: 5 mininclusive: 0 totaldigits: 18 ActiveOrHistoricCurrencyCode [A-Z]{3,3} Rule(s): ActiveOrHistoricCurrencyAndAmount CurrencyAmount The number of fractional digits (or minor unit of currency) must comply with ISO Note: The decimal separator is a dot. ActiveOrHistoricCurrencyCode ActiveOrHistoricCurrency The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged. USAGE: See Reporting of costs, fees and taxes 138/176

139 Record <Rcrd> Presence: Type: [0..n] Record of tax details. This message item is composed of the following TaxRecord1 element(s): Type <Tp> High level code to identify the type of tax details. Data Type: Max35Text Format: maxlength: /176

140 TaxAmount <TaxAmt> Set of elements used to provide information on the amount of the tax record. Type: This message item is composed of the following TaxAmount1 element(s): Rate <Rate> Rate used to calculate the tax. Data Type: PercentageRate Format: fractiondigits: 10 - totaldigits: TaxableBaseAmount <TaxblBaseAmt> Amount of money on which the tax is based. Data Type: ActiveOrHistoricCurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode. Format: ActiveOrHistoricCurrencyAndAmount 140/176

141 fractiondigits: 5 - mininclusive: 0 - totaldigits: 18 ActiveOrHistoricCurrencyCode [A-Z]{3,3} Rule(s): CurrencyAmount ActiveOrHistoricCurrencyAndAmount The number of fractional digits (or minor unit of currency) must comply with ISO Note: The decimal separator is a dot. ActiveOrHistoricCurrencyCode ActiveOrHistoricCurrency The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged TotalAmount <TtlAmt> Total amount that is the result of the calculation of the tax for the record. Data Type: ActiveOrHistoricCurrencyAndAmount This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyCode. Format: ActiveOrHistoricCurrencyAndAmount fractiondigits: 5 mininclusive: 0 totaldigits: 18 ActiveOrHistoricCurrencyCode [A-Z]{3,3} Rule(s): ActiveOrHistoricCurrencyAndAmount CurrencyAmount The number of fractional digits (or minor unit of currency) must comply with ISO Note: The decimal separator is a dot. ActiveOrHistoricCurrencyCode ActiveOrHistoricCurrency The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged. 141/176

142 2.293 ReturnInformation <RtrInf> Set of elements used to provide the return information. Type: This message item is composed of the following ReturnReasonInformation10 element(s): Rule(s): ReturnReasonRule If Reason/Code is equal to NARR, then AdditionalInformation must be present. 142/176

143 2.294 OriginalBankTransactionCode <OrgnlBkTxCd> Set of elements to fully identify the type of underlying transaction resulting in an entry. Type: This message item is composed of the following BankTransactionCodeStructure1 element(s): UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007 MX camt BankToCustomerStatementV01 Page Domain <Domn> Presence: Usage: [0..1], R2 Set of elements used to provide the domain, the family and the sub-family of the bank transaction code, in a structured and hierarchical format. If a specific family or sub-family code cannot be provided, the generic family code defined for the domain or the generic sub-family code defined for the family should be provided. 143/176

144 Type: This message item is composed of the following BankTransactionCodeStructure5 element(s): Code <Cd> Specifies the business area of the underlying transaction. Data Type: ExternalBankTransactionDomainCode Format: maxlength: Family <Fmly> Specifies the family and the sub-family of the bank transaction code, within a specific domain, in a structured and hierarchical format. Type: This message item is composed of the following BankTransactionCodeStructure6 element(s): 144/176

145 2.298 Code <Cd> Specifies the family within a domain. Data Type: ExternalBankTransactionFamilyCode Format: maxlength: SubFamilyCode <SubFmlyCd> Specifies the sub-product family within a specific family. Data Type: ExternalBankTransactionSubFamily1Code Format: maxlength: Proprietary <Prtry>, R2 Bank transaction code in a proprietary form, as defined by the issuer. Type: This message item is composed of the following ProprietaryBankTransactionCodeStructure1 element(s): 145/176

146 2.301 Code <Cd> Data Type: Max35Text Proprietary bank transaction code to identify the underlying transaction. Format: maxlength: Issuer <Issr> Identification of the issuer of the proprietary bank transaction code. Data Type: Max35Text Format: maxlength: Originator <Orgtr> Party that issues the return. Type: This message item is composed of the following PartyIdentification32 element(s): 146/176

147 9.1.0 Name <Nm> Data Type: Max140Text Name by which a party is known and which is usually used to identify that party. Format: maxlength: Reason <Rsn> Specifies the reason for the return. Type: This message item is composed of one of the following ReturnReason5Choice element(s): Code <Cd> Reason for the return. Data Type: ExternalReturnReason1Code Format: maxlength: 4 USAGE: Only codes below will are supported 147/176

148 Code Name Definition AC01 IncorrectAccountNumber Account number is invalid or missing. Formerly: Format of the account number specified is not correct. AC04 ClosedAccountNumber Account number specified has been closed on the bank of account s books. AC06 BlockedAccount Account specified is blocked, prohibiting posting of transactions against it. AC13 InvalidDebtorAccountType Debtor account is a consumer account (B2B Only) AG01 TransactionForbidden Transaction forbidden on this type of account (formerly NoAgreement) AG02 InvalidBankOperationCode Bank Operation code specified in the message is not valid for receiver AM04 InsufficientFunds Amount of funds available to cover specified message amount is insufficient. AM05 Duplication Duplication BE01 InconsistenWithEndCustomer Identification of end customer is not consistent with associated account number. (formerly CreditorConsistency). BE04 MissingCreditorAddress Specification of creditor s address, which is required for payment, is missing/not correct (formerly IncorrectCreditorAddress). BE05 UnrecognisedInitiatingParty Party who initiated the message is not recognised by the end customer FF05 InvalidLocalInstrumentCode Local Instrument code is missing or invalid FOCR FollowingCancellationRequest Following Cancellation Request MD01 NoMandate No Mandate MD02 MD03 MissingMandatoryInformationIn Mandate InvalidFileFormatForOtherReasonThanGr oupingindicator Mandate related information data required by the scheme is missing. File format incomplete or invalid MD06 RefundRequestByEndCustomer Return of funds requested by end customer MD07 EndCustomerDeceased End customer is deceased. MS02 MS03 NotSpecifiedReasonCustomer Generated NotSpecifiedReasonAgent Generated Reason has not been specified by end customer Reason has not been specified by agent. NARR Narrative Reason is provided as narrative information in the additional reason information. RC01 BankIdentifierIncorrect Bank Identifier coe specified in the message has an incorrect format (formerly IncorrectFormatForRoutingCode). RC02 InvalidBankIdentifier Bank identifier is invalid or missing. Generic usage if cannot specify between debit or credit account RR01 Missing Debtor Account or Identification Specification of the debtor s account or unique identification needed for reasons of regulatory requirements is insufficient or missing 148/176

149 RR02 RR03 Missing Debtor Name or Address Missing Creditor Name or Address RR04 Regulatory Reason Regulatory Reason Specification of the debtor s name and/or address needed for regulatory requirements is insufficient or missing. Specification of the creditor s name and/or address needed for regulatory requirements is insufficient or missing. SL01 Specific Service offered by Debtor Agent Due to specific service offered by the Debtor Agent AdditionalInformation <AddtlInf> Presence: [0..n], R3 Further details on the return reason. Data Type: Max105Text Format: maxlength: AdditionalTransactionInformation <AddtlTxInf> Further details of the transaction. Data Type: Max500Text Format: maxlength: AdditionalEntryInformation <AddtlNtryInf> Further details of the entry. 149/176

150 Data Type: Max500Text Format: maxlength: AdditionalStatementInformation <AddtlStmtInf> Further details of the account statement. Data Type: Max500Text Format: maxlength: /176

151 4. Principles governing the structure of reporting In this chapter, we often make references to XML-examples in chapter 7. The examples in chapter 7 are preceeded by two indexes: A = Example-Index: This example-index is made to facilitate the reading of these guidelines. All items are numbered consecutively, in order to have unique references to the examples. B = MX.CAMT Index: This index represents the exact index numbering of the CAMT General principles The use of optional fields may be subject to a bilateral agreement with the bank Information registered under the Entry item 2.76 : Both for simple and globalised transactions, information can be retrieved from the following items : - Amount item : the net amount that has been booked - Creditdebitindicator 2.79 item : the direction of the transaction - Reversalindicator 2.80 item: the question whether one is dealing with a correction in writing or with R-transactions (SCT-SDD) - Status 2.81 item : always booked in the EoD reporting - BookingDate 2.82 item : the booking date of the transaction - ValueDate 2.83 item: the value date of the transaction - Accountservicereference 2.84 item : the reference of the transaction generated by the bank - BankTransactionCode 2.91 item : the transaction type If the charges are linked to a globalised transaction, information also can be retrieved from the following items : - Charges item : if there is a link between the costs/fees/taxes and the globalisation - AdditionalEntryInformation item: additional information, if any, about the globalised transaction. XML-example : see example-index 3.2 to Information registered under the Entry details item : The modus-operandi is defined in a bilateral agreement with the bank. as for a single transaction, information can be retrieved from the following items : - TransactionDetails item : any additional information about the transaction as for globalised transactions, information can be retrieved from the following items : - Batch item : all batch elements 151/176

152 - TransactionDetails 2.141item: all information about the details of a globalized transaction - AdditionalEntyInformation item : additional information, if any, about the transaction XML-example : see example-index 4.25 to Partial / gross amounts versus net amount : In case a transaction consists of several partial amounts (eg. a batch-booking or a transaction where charges or taxes are included), the net amount will be reported under the Amount 2.78 item, and the partial amounts will be reported under EntryDetails item. The sum of all partial amounts should equal the net amount. Depending on your bank, in case the gross amount equals the net amount, the gross amount will not be reported under the EntryDetails item Reporting of Structured Creditor References to RemittanceInformation Item : When the field 2.98 RemittanceInformation of the pain.001 xml message is filled, the information is provided in the corresponding fields of the camt.053 xml message. The Structured Creditor Reference defined in Luxembourg, contains a 14 digit structured communication, with the last 2 digits as check digits (modulo 97) of the first 12 digits; but if the result is 0, then the check digits are 97. Only Luxembourg banks support this national standardized reference. 4.3 Reporting of costs, fees and taxes : Use of the Charges item under TransactionDetails item Use of the Tax item, if tax is levied on a part of or on the whole of the costs and fees concerned Whenever charges are reported the Charges item will be used as many times as there are different charges related to the same transaction to be reported, XML-example : see If the costs, fees and taxes pertain to a globalised transaction, the information will be given under the Charges item Reporting of Customer References from Pain-messages : A Pain-message can contain different customer references such as MessageIdentification, PaymentInformationIdentification, InstructionIdentification and EndToEndInformation. If they occur in a Pain-message transaction, they will be reported as follows : 152/176

153 For single transactions in the following items : o Under the References item : MessageIdentification item PaymentInformationIdentification item InstructionIdentification item EndToEndIdentification item For globalised transactions : o Under the Batch item : MessageIdentification item PaymentInformationIdentification item o Under the References item : InstructionIdentification item EndToEndIdentification item Pain-message 153/176

154 4.5. Reporting of the different kinds of amounts: The use of optional fields may be subject to a bilateral agreement with the bank. Booked amount on the account (globalised or single): Use of the Amount 2.78 item Other kinds of amounts: Use of AmountDetails item in accordance with the following rules: Amount related to a detail of a globalised transaction: ª Use of the TransactionAmount item Gross amount (before deduction of costs, fees and taxes) labeled in the currency of the reported account: ª Use of the InstructedAmount item Gross amount (before deduction of costs, fees and taxes) not labeled in the currency of the reported account: ª Use of the InstructedAmount item to report the gross amount of the original transaction in its original currency ª Use of the CounterValueAmount item for the reporting of the counter value labeled in the currency of the reported account, of the original amount. All useful information about currency conversion will be given under this item. ª Use of the ProprietaryAmount item with one of the category codes mentioned in 6.2 Category being included in the type item for the reporting of more specific amounts (capital of a long-term investment ):... Attention : if the amounts are related to a globalised transaction, the information will be given under the AmountDetails XML-example : see example-index 4.37 to Reporting of the TransactionsSummary 2.43 item: Let s assume we have to report the following transactions in a statement : , , , ,00 442,00 The reporting of the TransactionSummary 2.43 item will be as follows : <TxsSummry> <TtlNtries> <NbOfNtries>5</NbOfNtries> <Sum> </Sum> è The sum off all transactions, 154/176

155 regardless whether they are credit- or debet-transactions. <TtlNetNtryAmt> </TtlNetNtryAmt> è The sum off all transactions, taken in account whether they are credit- or debettransactions. <CdtDbtInd>CRDT</CdtDbtInd> è Indicates whether the total net entry amount is a credit or a debit balance. </TtlNtries> <TtlCdtNtries> <NbOfNtries>4</NbOfNtries> è Number of individual credit entries included in the report. <Sum> </Sum> è Total of all individual credit entries included in the report. </TtlCdtNtries> <TtlDbtNtries> <NbOfNtries>1</NbOfNtries> è Number of individual debit entries included in the report. <Sum>442.00</Sum> è Total of all individual debit entries included in the report. </TtlDbtNtries> </TxsSummry> XML-example : see 7.3 example-index 2.58 to /176

156 5. Bank Transaction Codes The Bank Transaction Codes structure is defined as follow: The Structure (Domain, Family, Sub-family) is not currently used in Luxembourg. Only proprietary codes will be used Transaction codes defined in Luxembourg Common list to be provided by banks. 156/176