Format Description CAMT.052 version 1.0. Rabo Direct Connect, SWIFT FileAct en Rabo Internetbankieren (Professional)

Transcription

1 Format Description CAMT.052 version 1.0 Rabo Direct Connect, SWIFT FileAct en Rabo Internetbankieren (Professional)

2 Contents 1 CAMT.052 Exportformat CAMT.052 description CAMT.052 structure Technical mapping Character set Message structure 5 2 Segment description Group header Report Segment Entry segment Entry details 13 3 CAMT.052 scenarios SEPA Credit Transfer and non-sepa transfer scenarios SEPA Direct Debit and non-sepa collection scenarios Related Parties 29 Appendix 1: Transaction type codes 30 Appendix 2: SEPA reason codes 31 Appendix 3: Future changes 32 Expected changes 32 Future changes 32 Change Log 33 Rabobank Format description CAMT.052 April 2018 Version 1.0 2

3 1 CAMT.052 Exportformat Rabobank introduces the CAMT.052 format for exporting intraday account reports. Intraday transactions are transactions that were booked on an account since the last book day closed. This reporting format, as implemented by Rabobank, is based on the guideline provided by the Nederlandse Vereniging van Banken (NVB). The guideline is available here CAMT.052 description The CAMT.052 Bank to Customer Account Report message is used to inform an account owner or authorized party of entries booked to the account. It may contain reports for more than one account. It contains information on booked entries only. The CAMT.052 as implemented by Rabobank is always downloaded as a single file. The CAMT.052 is available for Rabobank current accounts, Rabobank savings accounts, Multibank accounts (non-rabobank accounts) and Rabo Network Banking (=RNB) accounts (accounts which are held at our international Rabobank Branches in Germany, Belgium and the United Kingdom). Rabobank current accounts are accounts held at local branches of Rabobank or Corporate accounts held at WRR former Rabobank International. The table below describes which account type becomes available in Rabo Internetbanking (Professional) (RIB (Pro)), Rabo Direct Connect (RDC) and SWIFT FileAct. RIB RDC/SWIFT FileAct Rabobank accounts Available Available Multibank accounts Expected Q Expected Q RNB accounts Expected Q Expected Q This CAMT.052 description only applies to exports of Rabo Internetbanking (Professional), Rabo Direct Connect and SWIFT FileAct. 1.2 CAMT.052 structure The models in the ISO20022 document are described in ML using schemas. A specific description language (SD) is used in a schema. By using the schemes, a description can be given to the tags in the document, the structure and the concatenation of the beacons (the order of the tags) as well as the allowed codes for certain fields, the number of possible cases, mandatory or optional usage for certain fields. The general SD for camt is available here Rabobank Format description CAMT.052 April 2018 Version 1.0 3

4 1.3 Technical mapping The usage rules are strictly followed to avoid that the exported message is rejected or that the information within the message is refused. Only message elements described within the guidelines are used. Message elements not listed in chapter 2 are not available in the CAMT.052 as made available by Rabo Internetbanking (Professional), Rabo Direct Connect and SWIFT FileAct. The description of each message item contains: Column Description Index Number referring to the matching description in the UNIFI (ISO 20022) message definition for Bank-to-Customer Cash Management 2. Not all fields have a number. Fields without a number are under the parent tag. Gaps in numbering can occur because not all elements of ISO20022 are used within the CAMT.052 message as made available by Rabo Internetbanking (Professional), Rabo Direct Connect and SWIFT FileAct. Level Level of the element within CAMT.052 message. <Top> <Level 1> <Level 2> <Etc./> </Level 2> </Level 1> </Top> Name Name of the element within the CAMT.052 message. ML-Tag Short name to identify an element within a ML message, presented between brackets, e.g. <Amount>. This determines if an element is optional or mandatory, and how many times the element can be repeated. The number of times that an element can appear is presented between square brackets. For example: [0..1] Shows that the element can appear 0 or 1 time. The element is optional. [0..n] Shows that the element can appear 0 or n time(s). The element is optional. [1..1] Shows that the element is mandatory and must appear once. [1..n] Shows that the element is mandatory and must appear at least once. The element can be present n times. In case a lower level element is mandatory while its higher element is optional, the lower level is mandatory only if the higher level element is present. Rabobank Format description CAMT.052 April 2018 Version 1.0 4

5 Column Format Length Rabobank account: description Multibank/RNB account: description Description Field type indication: Numeric: only numbers are allowed Alphanumeric: may contain numbers and allowed characters (ref. 1.4 Character set) Date: CCYY-MM-DD Time: timestamp in various formats as explained in columns Description Amount: numbers, with a decimal point as separator. Maximum length is 9 digits before the separator, and two behind it. Exception for this rule is the control sum. Boolean: field with two options: true or false Code: usually a two to four character code, the description columns explains the code. Number of positions in the field. Additional information about usage of the element for Rabobank Account. Tag only indicates that the element is always followed by another tag. Additional information about usage of the element for Multibank Account. Tag only indicates that the element is always followed by another tag. 1.4 Character set In UNIFI messages the UTF8 character set must be used: 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 Y Z / -? : ( )., ' + space 1.5 Message structure The CAMT.052 message always contains two segments, a Group Header and at least one Report. Each Report contains one or more Entries. Each Entry may contain one or more Entry Details. The modular structure of the CAMT.052 file is depicted below. More information about the message structure is available via the following webpage: CAMT.052 Message GroupHeader Each CAMT.052 contains one Group Header Report Each CAMT.052 contains at least one Report Balance Each Report contains at least one Balance Entry Each Report may contain one or more Entries Entry details Each Entry may contain one or more Entry details Report Each CAMT.052 may contain more than one Report Rabobank Format description CAMT.052 April 2018 Version 1.0 5

6 2 Segment description 2.1 Group header The following elements are present in the Group Header of the CAMT.052 message. Index Level Name <ML Tag> Top Document <Document> [1..1] Always filled with <Document xmlns:xsi=" chema-instance" xmlns="urn:iso:std:iso:20022:tech:xsd:camt "> Top Message root <BkToCstmrAcctRpt> [1..1] Tag only. Tag only. 1.0 Top GroupHeader <GrpHdr> [1..1] Tag only. Tag only. Always filled with <Document xmlns:xsi=" chema-instance" xmlns="urn:iso:std:iso:20022:tech:xsd:camt "> MessageIdentification <MsgId> [1..1] Alphanumeric Max. length 35 <CAMT052><channel code><12-digit sequence number> The 12-digit sequence number is unique and random. Channel code: Code RIB = RIB (Pro) Code HHV = RDC / SWIFT FileAct <CAMT052><HHV><12-digit sequence number> The 12-digit number is unique and random. For example: CAMT052HHV For example: CAMT052HHV CreationDateTime <CreDtTm> [1..1] Date and Time Date and time when CAMT.052 is generated. For example: T11:20:45+01:00. Date and time when CAMT.052 is generated. For example: T11:20:45+01:00. Rabobank Format description CAMT.052 Maart 2018 Version 1.0 6

7 2.2 Report Segment The Report Segment first reports general report information: the account which is reported on and balance details for the current book date. The Entry segment that starts at Index 2.76 contains details of the transactions booked on the account. Index Level Name <ML Tag> Report <Rpt> [1..n] Tag only. Tag only Identification <Id> [1..1] Alphanumeric Max. length 35 CAMT052><12-digit sequence number> <5-digit subsequence number> The 12-digit number is unique and random. The 5-digit sequence number is unique within the message and account independently. The first report is assigned with subsequence number 1, the second subsequence number 2, etc. For example 3 reports of 3 accounts in 1 CAMT052 message. Report 1: <CAMT052>< ><00001> Report 2: <CAMT052>< ><00002> Report 3: <CAMT052>< ><00003> CreationDateTime <CreDtTm> [1..1] Date and time Timestamp on which the Report was created. For example: T11:20:45+01:00. CAMT052><12-digit sequence number> <5-digit subsequence number> The 12-digit number is unique and random. The 5-digit sequence number is unique within the message and account independently. The first report is assigned with subsequence number 1, the second subsequence number 2, etc. For example 3 reports of 3 accounts in 1 CAMT052 message. Report 1: <CAMT052>< ><00001> Report 2: <CAMT052>< ><00002> Report 3: <CAMT052>< ><00003> Timestamp on which the Report was created. For example: T11:20:45+01: Account <Acct> [1..1] Tag only. Tag only Identification <Id> [1..1] Tag only. Tag only IBAN <IBAN> {OR [1..1] Alphanumeric Max. length 34 IBAN account number in electronic format (without spaces), i.e. IBAN account number in electronic format (without spaces), i.e. Rabobank Format description CAMT.052 April 2018 Version 1.0 7

8 Index Level Name <ML Tag> NL44RABO , NL68RABO NL44RABO , NL68RABO Other <Othr> OR} [1..1] Not available. Tag only Identification <Id> [1..1] Not available. If IBAN is not available, the account is reported in another format. When the accountnumer has more than 34 positions, only the first 34 postions are reported Currency <Ccy> [0..1] Code Fixed length 3 Currency of the account in ISO 4217 currency code. Currency of the account in ISO 4217 currency code Balance <Bal> [0..n] Tag only. Not available Type <Tp> [1..1] Tag only. Not available CodeOrProprietary <CdOrPrtry> [1..1] Tag only. Not available Code <Cd> [1..1] Code Fixed length 4 ITBD = Interim Booked Not available Amount <Amt> [1..1] Currency code Amount Max. length 18, max. 5 decimals This is the interim booked balance after the last transaction in this report. Not available. Example: <Amt Ccy="EUR">500.00</Amt> <Amt Ccy="KWD">1.000</Amt> <Amt Ccy="JPY">100</Amt> CreditDebitIndicator <CdtDbtInd> [1..1] Code Fixed lenght 4 Value is CRDT if amount is zero or positive, DBIT if amount is negative. Not available Date <Dt> [1..1] Tag only. Not available Date <Dt> [1..1] Date Fixed length 10 Format: CCYY-MM-DD This is the date of the interim booked balance after the last transaction in this Not available. Rabobank Format description CAMT.052 April 2018 Version 1.0 8

9 Index Level Name <ML Tag> report TransactionsSummary <TxsSummry> [0..1] Tag only. Tag only TotalEntries <TtlNtries> [0..1] Tag only. Tag only NumberOfEntries <NbOfNtries> [0..1] Numeric Max. length 15 Number of individual entries included in the report. Number of individual entries included in the report Sum <Sum> [0..1] Numeric Max. length 18, max. 17 decimals The sum of all individual entries, regardless of or. For example, if 2 entries are reported of +100 and -100 the signs are ignored: the sum is = 200. The sum of all individual entries, regardless of or. For example, if 2 entries are reported of +100 and -100 the signs are ignored: the sum is = TotalNetEntryAmount <TtlNetNtryAmt> [0..1] Amount Max. length 18, max. 17 decimals The net sum of all individual entries. If 2 entries are reported of +100 and -100 the net sum is 0. The net sum of all individual entries. If 2 entries are reported of +100 and -100 the net sum is CreditDebitIndicator <CdtDbtInd> [0..1] Code Fixed length 4 Value is CRDT if total net entry amount is zero or positive, DBIT if amount is negative TotalCreditEntries <TtlCdtNtries> [0..1] Tag only. Tag is absent if no entries are in the report NumberOfEntries <NbOfNtries> [0..1] Alphanumeric Max. length 15 Number of all entries included in the report. Value is CRDT if total net entry amount is zero or positive, DBIT if amount is negative. Tag only. Tag is absent if no entries are in the report. Number of all entries included in the report Sum <Sum> [0..1] Numeric Max. length 18, max. 17 decimals Total of all individual entries included in the report. Total of all individual entries included in the report. Rabobank Format description CAMT.052 April 2018 Version 1.0 9

10 Index Level Name <ML Tag> TotalDebitEntries <TtlDbtNtries> [0..1] Tag only. Tag is absent if no debet entries are in the report NumberOfEntries <NbOfNtries> [0..1] Alphanumeric Max. length 15 Number of all entries included in the report. Tag only. Tag is absent if no debet entries are in the report. Number of all entries included in the report Sum <Sum> [0..1] Numeric Max. length 18, max. 17 decimals Total of all individual entries included in the report. Total of all individual entries included in the report TotalEntriesPerBank TransactionCode <TtlNtriesPerBkTxCd> [0..n] Tag only. Tag is not present if the report does not contain any transactions. Tag only. Tag is not present if the report does not contain any transactions NumberOfEntries <NbOfNtries> [0..1] Alphanumeric Max. length 15 Number of entries with the same bank transaction code. Number of entries with the same bank transaction code Sum <Sum> [0..1] Numeric Max. length 18, max. 17 decimals TotalNetEntryAmount <TtlNetNtryAmt> [0..1] Numeric Max. length 18, max. 17 decimals Sum of all entries with the same bank transaction code regardless of sign. Net sum of all entries with the same bank transaction code. Sum of all entries with the same bank transaction code regardless of sign. Net sum of all entries with the same bank transaction code CreditDebitIndicator <CdtDbtInd> [0..1] Code Fixed length 4 Value is CRDT if total net entry amount is zero or positive, DBIT if amount is negative. Value is CRDT if total net entry amount is zero or positive, DBIT if amount is negative BankTransactionCode <BkTxCd> [1..1] Tag only. Tag only Proprietary <Prtry> [0..1] Tag only. Tag only. Rabobank Format description CAMT.052 April 2018 Version

11 Index Level Name <ML Tag> Code <Cd> [1..1] Alphanumeric Max. length 35 The bank transactioncode is filled with a three or four postions alphanumeric code. The four positions alphanumeric code is for furture use. See Appendix 1. This tag is filled with the content of field- 61 sub-6 or?10 from field 86 of the incoming SWIFT MT Entry segment The Entry segment reports single intraday entries in the account. Single relates to not-cumulated individual booking where detailed information is available in section Transaction Details (2142). If applicable transactions are reported not-cumulated in CAMT.052. Submitted SEPA batches which are instructed with BatchBooking true or without BatchBooking indication are repoted as single transactions. Therefor details of underlying transactions within the SEPA batch are unavailable. Only details of the SEPA batch are available. In case of a SEPA batch submitted with BatchBooking false, then all transactions within the SEPA batch is reported as single transactions. Index Level Name <ML Tag> Entry <Ntry> [0..n] Tag only. Tag only Amount <Amt> [1..1] Currency code Amount Max. length 18, max. 5 decimals Example: <Amt Ccy="EUR">500.00</Amt> <Amt Ccy="KWD">1.000</Amt> <Amt Ccy="JPY">100</Amt> Example: <Amt Ccy="EUR">500.00</Amt> <Amt Ccy="KWD">1.000</Amt> <Amt Ccy="JPY">100</Amt> CreditDebitIndicator <CdtDbtInd> [1..1] Code Fixed length 4 Value is CRDT if amount is zero or positive, DBIT if amount is negative. Value is CRDT if amount is zero or positive, DBIT if amount is negative ReversalIndicator <RvslInd> [0..1] Code Value true or false. Value true or false. This tag is filled, based on the value of field-61 sub-3 of the incoming SWIFT MT940. Rabobank Format description CAMT.052 April 2018 Version

12 Index Level Name <ML Tag> More information about the usage of this tag is described in Chapter 3.3 "Related Parties" Status <Sts> [1..1] Code Always code BOOK, indicating the entry has been booked on the account. Reservations are not reported. Always code BOOK, indicating the entry has been booked on the account. Reservations are not reported BookingDate <BookgDt> [0..1] Tag only. Tag only Date <Dt> [1..1] Date Fixed length 10 Book date in format CCYY-MM-DD C = Century Y = Year M = Month D = Day Example: for December 16, Book date in format CCYY-MM-DD C = Century Y = Year M = Month D = Day Example: for December 16, ValueDate <ValDt> [0..1] Tag only. Tag only. This tag is filled with the date from field-61 sub-2 of the incoming SWIFT MT940. When the booking date is not available, the booking date is filled with the date from field-62f of the incoming SWIFT MT Date <Dt> [1..1] Date Fixed length 10 Value date in format CCYY-MM-DD C = Century Y = Year M = Month D = Day Example: for December 16, Value date in format CCYY-MM-DD C = Century Y = Year M = Month D = Day Example: for December 16, Rabobank Format description CAMT.052 April 2018 Version

13 Index Level Name <ML Tag> This tag is filled with the date from field-61 sub-1 of the incoming SWIFT MT AccountServicerReference <AcctSvcrRef> [0..1] Alphanumeric Max. length 35 Not Available. This tag is filled with the content from field- 61 sub-8 of the incoming SWIFT MT BankTransactionCode <BkTxCd> [1..1] Tag only. Tag only Proprietary <Prtry> [0..1] Tag only. Tag only Code <Cd> [1..1] Alphanumeric Max. length 35 The bank transactioncode is filled with a three or four postions alphanumeric code. The four positions alphanumeric code is for furture use. See Appendix 1. This tag is filled with the content of field-61 sub-6 or?10 from field-86 of the incoming MT Entry details Index Level Name <ML Tag> EntryDetails <NtryDtls> [0..n] Tag only. Tag only Batch <Btch> [0..1] Tag only. Tag only PaymentInformationIdentific ation <PmtInfId> [0..1] Alphanumeric Max. length 35 Payment information identification of a SEPA batch. content of code /PREF/ in field-86 of the incoming SWIFT MT TransactionDetails <TxDtls> [0..n] Tag only. Tag only References <Refs> [0..1] Tag only. Tag only PaymentInformation- Identification <PmtInfId> [0..1] Alphanumeric Max. length 35 Not available. Reference of the batch (Payment Information block) of which the Rabobank Format description CAMT.052 April 2018 Version

14 Index Level Name <ML Tag> transaction is part of. This tag is present only if both codes EREF (=End-to-End ID) and PREF (Payment Information ID) are present in the incoming SWIFT MT EndToEndIdentification <EndToEndId> [0..1] Alphanumeric Max. length 35 Unique payment reference throughout the chain (e2e). Concerning CAMT052 of savings accounts: This tag is absent for savings transfers. Usage of this tag is a future change. More information about future changes, see Appendix MandateIdentification <MndtId> [0..1] Alphanumeric Max. length 35 Mandate ID, unique identification, as assigned by the or, to unambiguously identify the mandate. Concerning CAMT052 of savings accounts: This tag is absent for savings transfers. Usage of this tag is a future change. More information about future changes, see Appendix 3. Unique payment reference throughout the chain (e2e). content of code /EREF/ in field-86 of the incoming SWIFT MT940. Mandate ID, unique identification, as assigned by the or, to unambiguously identify the mandate. content of code /MARF/ in field-86 of the incoming SWIFT MT AmountDetails <AmtDtls> [0..1] Tag only. Index AmountDetails clarified: For accounts held at Local Branches: the original transaction amount, currency and exchange rate can be found in this tag. If absent, please check for details tag Unstructured Remittance Information InstructedAmount <InstdAmt> [0..1] Tag only. This tag will be filled in case of non-sepa transactions even if the currency of the Tag only. Tag only. The instructed amount is present only if the currency of the transaction differs from Rabobank Format description CAMT.052 April 2018 Version

15 Index Level Name <ML Tag> Amount <Amt> [1..1] Currency amount Max. length 18, max. 5 decimals account is equal to the currency of the original payment order Example: <Amt Ccy="EUR">500.00</Amt> <Amt Ccy="KWD">1.000</Amt> <Amt Ccy="JPY">100</Amt> the currency of the account. content of code /OCMT/ in field-61 sub-9 or field-86 of the incoming SWIFT MT940. Example: <Amt Ccy="EUR">500.00</Amt> <Amt Ccy="KWD">1.000</Amt> <Amt Ccy="JPY">100</Amt> CurrencyExchange <Ccychg> [0..1] Tag only. Tag only. This tag is only present if both subtags SourceCurrency and ExchangeRate are present SourceCurrency <SrcCcy> [1..1] Currency Fixed length 3 Currency of the original transaction in ISO4217 currency code. Currency of the original transaction in ISO4217 currency code ExchangeRate <chgrate> [1..1] Exchange rate Max. length 11, max. 10 decimals If available the exchange rate used for conversion. The presentation of exchange rate is 1 unit currency unit of the account s currency in relation to the original payment order currency." currency extracted from the content of code /OCMT/ of field-61 sub-9 or field-86 of the incoming SWIFT MT940. content of code /ECH/ in field-61 sub-9 of field-86 of the incoming SWIFT MT940. For example: Account s currency = EUR Rabobank Format description CAMT.052 April 2018 Version

16 Index Level Name <ML Tag> Payment order currency = USD Present situation: 1 USD =....EUR New situation: 1 EUR =.....USD BankTransactionCode <BkTxCd> [0..1] Tag only. Tag only Proprietary <Prtry> [0..1] Tag only. Tag only Code <Cd> [1..1] Alphanumeric Max. length 35 The bank transactioncode is filled with a three or four postions alphanumeric code. The four positions alphanumeric code is for furture use. See Appendix Charges <Chrgs> [0..n] Tag only. Charges are available for all Rabobank s current accounts. This tag is filled with the content of field-61 sub-6 or?10 from field-86 of the incoming SWIFT MT940. Tag only Amount <Amt> [1..1] Currency code Amount Max. length 18, max. 5 decimals Charges included in the Entry amount (2.78). Charges are deducted form the original amount by the remitting bank. content of code /CHGS/ in field-86 of the incoming SWIFT MT CreditDebitIndicator <CdtDbtInd> [0..1] Code Fixed length 4 Value CRDT of DBIT This tag is filled with CRDT of DBIT only if the indicator is present in the content of code /CHGS/ in field-86 of the incoming SWIFT MT RelatedParties <RltdPties> [0..1] Tag only. Tag only Debtor <Dbtr> [0..1] Tag only. Only available if the debtor is the counterparty Name <Nm> [0..1] Alphanumeric Max. length 140 The name of the counterparty. Only available if the debtor is the counterparty. Tag only. Only available if the debtor is the counterparty. Usage of this tag (including subtags) is described in Chapter 3.3 Related Parties. The name of the counterparty. Rabobank Format description CAMT.052 April 2018 Version

17 Index Level Name <ML Tag> Concerning CAMT052 of savings accounts: This tag is absent for non-sepa savings transfers. Usage of this tag is a future change. More information about future changes, see Appendix 3. The name of the counterparty is availabe in the Unstructrured Remittance Information (tag 2.235) PostalAddress <PstlAdr> [0..1] Tag only. Postal address of counterparty. Available only if counterparty is debtor AddressType <AdrTp> [0..1] Code If subtag AddressType is filled than this tag is filled with ADDR. content of subcode /NAME/ of code /BENM/ or /ORDP/, or the content of codes?32 or?33 from field-86 of the incoming SWIFT MT940. Tag only. Postal address of counterparty. Available only if counterparty is debtor. If subtag AddressType is filled than this tag is filled with ADDR Country <Ctry> [0..1] Code Fixed length 2 Country in ISO 3166 country code. If available the country in ISO 3166 country code AddressLine <AdrLine> [0..7] Alphanumeric Max. length 70 Address of the counterparty. Address of the counterparty. content of subcode /ADDR/ of code /BENM/ or /ORDP/ from field-86 of the incoming SWIFT MT Identification <Id> [0..1] Tag only. Tag only OrganisationIdentification <OrgId> [1..1] Tag only. Tag only Other <Othr> [0..n] Tag only. Tag only Identification <Id> [1..1] Alphanumeric Max. length 35 Identification of the counterparty. Identification of the counterparty. content of subcode /ID/ of code /BENM/ or /ORDP/ from field-86 of the incoming SWIFT MT940. Rabobank Format description CAMT.052 April 2018 Version

18 Index Level Name <ML Tag> DebtorAccount <DbtrAcct> [0..1] Tag only. Only available if the debtor is the counterparty. Tag only. Only available if the debtor is the counterparty. Usage of this tag (includieng subtags) is described in Chapter 3.3 Related Parties Identification <Id> [1..1] Tag only. Tag only IBAN <IBAN> [1..1] Alphanumeric Max. length 34 IBAN accountnumber Not available Other <Othr> [1..1] Tag only. Tag only Identification <Id> [1..1] Alphanumeric Max. length 34 If IBAN is not available the non-iban is filled. If available, the accountnumber of the counterparty UltimateDebtor <UltmtDbtr> [0..1] Tag only. Tag only Name <Nm> [0..1] Alphanumeric Max. length 140 Name of the ultimate debtor. Name of the ultimate debtor. content of subcode /NAME/ of code /ULTD/ from field-86 of the incoming SWIFT MT Identification <Id> [0..1] Tag only. Tag only OrganisationIdentification <OrgId> [1..1] Tag only. Tag only Other <Othr> [0..n] Tag only. Tag only Identification <Id> [1..1] Alphanumeric Max. length 35 Identification of the ultimate debtor. This tag may be filled with BIC or BEI. Identification of the ultimate debtor. content of subcode /ID/ of code /ULTD/ from field-86 of the incoming SWIFT MT Creditor <Cdtr> [0..1] Tag only. Available if the counterparty is the or. Tag only. Available if counterparty is the or. Usage of this tag (includieng subtags) is described in Chapter 3.3 Related Parties. Rabobank Format description CAMT.052 April 2018 Version

19 Index Level Name <ML Tag> Name <Nm> [0..1] Alphanumeric Name of the counterparty. Concerning CAMT052 of savings accounts: This tag is absent for non-sepa savings transfers. Usage of this tag is a future change. More information about future changes, see Appendix 3. The name of the counterparty is availabe in the Unstructrured Remittance Information (tag 2.235). Name of the counterparty. content of subcode /NAME/ of code /BENM/ or /ORDP/, or the content of codes?32 or?33 from field-86 of the incoming SWIFT MT PostalAddress <PstlAdr> [0..1] Tag only. Postal address of counterparty. Available if the counterparty is the or. Tag only. Postal address of counterparty. Available if the counterparty is the or AddressType <AdrTp> [0..1] Code If subtag AddressType is filled than this tag is filled with ADDR. If subtag AddressType is filled than this tag is filled with ADDR Country <Ctry> [0..1] Code Fixed length 2 Country in ISO 3166 country code. Country in ISO 3166 country code AddressLine <AdrLine> [0..7] Alphanumeric Max. length 70 Address of counterparty. Address of counterparty. content of subcode /ADDR/ of code /BENM/ or /ORDP/ from field-86 of the incoming SWIFT MT Identification <Id> [0..1] Tag only. Tag only OrganisationIdentification <OrgId> [1..1] Tag only. Tag only Other <Othr> [0..n] Tag only. Tag only Identification <Id> [1..1] Alphanumeric Max. length 70 Identification of the counterparty. Identification of the counterparty. content of subcode /ID/ of code /BENM/ or /ORDP/ from field-86 of the incoming SWIFT MT940. Rabobank Format description CAMT.052 April 2018 Version

20 Index Level Name <ML Tag> CreditorAccount <CdtrAcct> [0..1] Tag only. Available if the counterparty is the or Identification <Id> [1..1] Tag only. Tag only IBAN <IBAN> [1..1] Alphanumeric Max. length 34 IBAN accountnumber. Not available Other <Othr> [1..1] Tag only. Tag only. Tag only. Available if the counterparty is the or. Usage of this tag (includieng subtags) is described in Chapter 3.3 Related Parties Identification <Id> [1..1] Alphanumeric Max. length 34 If available filled with non-iban account number. If available, the accountnumber of the counterparty UltimateCreditor <UltmtCdtr> [0..1] Tag only. Tag only Name <Nm> [0..1] Code Max. length 140 Name of the ultimate or. Name of the ultimate or. content of subcode /NAME/ of code /ULTB/ from field-86 of the incoming SWIFT MT Identification <Id> [0..1] Tag only. Tag only OrganisationIdentification <OrgId> [1..1] Tag only. Tag only Other <Othr> [0..n] Tag only. Tag only Identification <Id> [1..1] Alphanumeric Max. length 34 Identification of the ultimate or. This tag may be filled with BIC or BEI. Identification of the ultimate or. content of subcode /ID/ of code /ULTB/ from field-86 of the incoming SWIFT MT RelatedAgents <RltdAgts> [0..1] Tag only. Not available DebtorAgent <DbtrAgt> [0..1] Tag only. Aailable if the debtor is the counterparty. Not available FinancialInstitutionIdentifica <FinInstnId> [1..1] Tag only. Not available. Rabobank Format description CAMT.052 April 2018 Version

21 Index Level Name <ML Tag> tion BIC <BIC> [0..1] Alphanumeric Length 8 or 11 It is filled with the BIC of the financial institution of the counterparty. Not available CreditorAgent <CdtrAgt> [0..1] Tag only. Not available FinancialInstitutionIdentifica tion <FinInstnId> [1..1] Tag only. Not available BIC <BIC> [0..1] Alphanumeric Length 8 or 11 It is filled with the BIC of the financial institution of the counterparty. Not available Purpose <Purp> [0..1] Tag only. Tag only Code <Cd> [1..1] Code Max. length 4 List available on st.page RemittanceInformation <RmtInf> [0..1] Tag only. Tag only Unstructured <Ustrd> [0..n] Alphanumeric Max. length 140 Non-structured remittance information. Unstructured remittance information is not supplemented by Rabobank with extra (SEPA) information. (SEPA) information is available in the concerning tags of the CAMT message. content of subcode /CD/ of code /PURP/ from field-86 of the incoming MT940. If available this tags if filled with the content of tag /REMI/ or tags?20-?29 and?60-?63 from field-86 from the incoming SWIFT MT Structured <Strd> [0..n] Tag only. Structured tag is only filled if the Reference (2.262) is available. Tag only CreditorReferenceInformatio n <CdtrRefInf> [0..1] Tag only. Tag only Type <Tp> [0..1] Tag only. Tag only CodeOrProprietary <CdOrPrtry> [1..1] Tag only. Tag only. Rabobank Format description CAMT.052 April 2018 Version

22 Index Level Name <ML Tag> Code <Cd> [1..1] Code Fixed length 4 If available filled with SCOR. content of subcode /CD/ of code /REMI/ from field-86 of the incoming SWIFT MT Issuer <Issr> [0..1] Code Max. length 35 Only the Currence payment reference is supported. Issure is then filled with CUR. content of subcode /ISSR/ of code /REMI/ from field-86 of the incoming SWIFT MT940. This tag is not present if tag is absent Reference <Ref> [0..1] Alphanumeric Max. length 35 If available, contains Acceptgiro reference (Currence payment reference). content of ubtag /CDTRREF/ of tag /REMI/ of field-86 from the incoming SWIFT MT ReturnInformation <RtrInf> [0..1] Tag only. Tag only Reason <Rsn> [0..1] Tag only. Tag only Code <Cd> [1..1] Code Max. length 4 For a list of reason codes, see Appendix 2. content of tag /RTRN/ of field-86 from the incoming SWIFT MT AdditionalInformation < AddtlInf> [0..n] Alphanumeric Max. length 105 If available, the translation of the return reason code in Dutch language. Translation of the return reason code if available AdditionalTransactionInfor mation <AddtlTxInf> [0..1] Alphanumeric Max. length 500 Creditor scheme ID of the SEPA direct. Only in case of SDD debet of SDD-R, if available. Not available. The Creditor Identifier is available again since mid February 2018 with code word /CSID/. Rabobank Format description CAMT.052 April 2018 Version

23 Index Level Name <ML Tag> Regarding CAMT052 of savings accounts: This tag is absent for savings transfers. Usage of this tag is a future change. More information about future changes, see Appendix AdditionalEntryInformation <AddtlNtryInf> [0..1] Alphanumeric Max. length 500 Not available. content of field-86 of the incoming SWIFT MT940. Rabobank Format description CAMT.052 April 2018 Version

24 3 CAMT.052 scenarios This chapter describes the elements used in the scenarios. Chapters 3.1 and 3.2 describe the scenarios for Rabobank accounts. Chapter 3.3 describes the elements of Multibank/RNB accounts related to tag 2199 Related Parties. The table below inidicates the various possible payment scenarios for Rabobank accounts. 1a Reporting of a SEPA, account was 1b ed because: Scenario - Rabobank accounts You have made a SEPA payment from your account. You have made a SEPA batch payment from your account (batch booking TRUE). 2 A counterparty has ed your account via a SEPA direct. 3 A previous SEPA has been returned. 4 A previous SEPA direct has been returned. 5 Reporting of a SEPA A counterparty has made a SEPA payment to your account. 6, account was ed because: You have ed counterparty s account via a SEPA direct. 7 A previous outgoing SEPA transfer has been returned to your account. 8 You have been ed via a SEPA direct previously, this direct is returned. 9 Reporting of a non- You have made a non-sepa payment from your account. SEPA 10 Counterparty has ed your account via a non-sepa direct. 11 Reporting of a non- A counterparty has made a non-sepa payment to your account. SEPA 12 You have ed a counterparty s account via a non-sepa direct. Rabobank Format description CAMT.052 April 2018 Version

25 3.1 SEPA Credit Transfer and non-sepa transfer scenarios For SEPA and non-sepa transfers and for returned/rejected/recalled SEPA transfers, the table below indicates per scenario, which fields, if available, are present in the CAMT.052 export format. The presence is indicated by an or by displaying the reported value. No. Fields Usage rule Rabobank 1a 1b 7 Reverse booking 5 3 Reverse booking 9 non- SEPA transfer 11 non- SEPA transfer Single Batch 2.78 Amount 2.79 CreditDebitIndicator DBIT DBIT CRDT CRDT DBIT DBIT CRDT 2.80 ReversalIndicator required, value YES 2.81 Status 2.82 BookingDate 2.83 ValueDate 2.91 BankTransactionCode Rabobank specific transaction code PaymentInformation Identification EndToEnd Identification Equivalent value from pain.001 Equivalent value from pain.001 Equivalent value from pain.001 of original transaction AmountDetails If transaction currency is different from account currency BankTransactionCode BOOK BOOK BOOK BOOK BOOK BOOK BOOK Charges Debtor Details of originator of received payment DebtorAccount Details of originator account of received payment Details of beneficiary account of original UltimateDebtor Details of originator reference party of 3 For Recall: To be used for charges deducted Rabobank Format description CAMT.052 April 2018 Version

26 No. Fields Usage rule Rabobank 1a 1b 7 Reverse booking 5 3 Reverse booking 9 non- SEPA transfer 11 non- SEPA transfer Details of beneficiary reference party of original Details of originator reference party of received Creditor Details of beneficiary of payment Details of originator of original CreditorAccount Details of beneficiary account of payment Details of originator account of original UltimateCreditor Details of beneficiary reference party of Details of originator reference party of original Details of beneficiary reference party of received DebtorAgent Details of the originator bank of received payment Details of the beneficiary bank of the original CreditorAgent Details of beneficiary bank of payment Details of originator bank of original Purpose Equivalent value from pain.001 Equivalent value from pain.001 of original transaction Purpose of received passed through to beneficiary Remittance Information Equivalent value from payment Equivalent value from pain.001 of original transaction Single Batch 1 ¹ ¹ 1 Not in case of a batch booking Rabobank Format description CAMT.052 April 2018 Version

27 No. Fields Usage rule Rabobank 1a 1b 7 Reverse booking 5 3 Reverse booking 9 non- SEPA transfer 11 non- SEPA transfer Single Batch Passed through on statement information beneficiary ReturnInformation Required, value YES Reason Reasoncode 3.2 SEPA Direct Debit and non-sepa collection scenarios For SEPA and non-sepa direct s and for returned/rejected/recalled SEPA direct s, the table below indicates per scenario, which fields, if available, are present in the CAMT.052 export format. The presence is indicated by an or by displaying the reported value. No. Fields Usage rule Rabobank 2 SDD 2.78 Amount 4 Reverse booking SDD 6 SDD Batch 8 Reverse booking SDD 10 non-sepa collection 12 non-sepa collection 2.79 CreditDebitIndicator DBIT DBIT CRDT CRDT DBIT CRDT 2.80 ReversalIndicator required, value YES 2.81 Status 2.82 BookingDate 2.83 ValueDate 2.91 BankTransactionCode Rabobank specific transaction code PaymentInformation Identification EndToEnd Identification Equivalent value from pain.008 Equivalent value from pain.008 of original SDD Passed through on statement information of debtor MandateIdentification Equivalent value from pain.008 of original SDD BOOK BOOK BOOK BOOK BOOK BOOK Rabobank Format description CAMT.052 April 2018 Version

28 No. Fields Usage rule Rabobank 2 SDD AmountDetails Passed through on statement information of debtor 4 Reverse booking SDD 6 SDD Batch 8 Reverse booking SDD 10 non-sepa collection 12 non-sepa collection Debtor Details of debtor of DD Details of or of original SDD DebtorAccount Details of debtor account of DD Details of or account of original SDD UltimateDebtor Details of debtor reference party of SDD Details of debtor reference party of original SDD Creditor Details of or of SDD passed through to debtor Details of debtor of original SDD CreditorAccount Details of or account of SDD passed through to debtor Details of debtor account of original SDD UltimateCreditor Details of or reference party of SDD Details of debtor reference party of original SDD DebtorAgent Details of or agent of original SDD CreditorAgent Details of or agent of SDD passed through to debtor Details of debtor agent of original SDD Remittance Information Remittance information of SDD PaymentInformationId reference from pain ¹ 1 Not in case of a batch booking Rabobank Format description CAMT.052 April 2018 Version

29 No. Fields Usage rule Rabobank 2 SDD from original SDD. 4 Reverse booking SDD 6 SDD Batch 8 Reverse booking SDD 10 non-sepa collection 12 non-sepa collection Value from pain.008 of original SDD. Passed through on statement information of debtor ReturnInformation Reason Reasoncode AdditionalTransactionInformation 1 Details of or of SDD ¹ ¹ 3.3 Related Parties For Multibank/RNB accounts the type of transaction cannot be determined. Based on the content from the incoming MT942, the CAMT.052 is filled as follows, including the ReversalIndicator: Incoming MT942 Outgoing CAMT052 Related Parties tag Credit transaction Debtor false Debet transaction Creditor false RD (= ) transcation Debtor true RC (=debet) transaction Creditor true Outgoing CAMT.052 ReversalIndicator tag 2.80 When mentioned "Debtor" then this also applies to the child tags and Debtor Account. When mentioned "Creditor" then this also applies to the child tags and Creditor Account. 1 The Creditor identifier is available again since mid February 2018 with code word /CSID/. Rabobank Format description CAMT.052 April 2018 Version

30 Appendix 1: Transaction type codes Information described in this appendix is only applicable for Rabobank accounts. The Bank Transaction Codes are provided in tags 2.68, 2.98 and An overview of these transaction type codes can be found on Rabo Internetbankieren (Professional) under section Transaction reporting. Rabo Direct Connect: SWIFT FileAct: Please note: the transaction type codes are the Rabobank s own codes. Rabobank is entitled to adjust these transaction type codes and descriptions at any time without prior notice. Rabobank Format description CAMT.052 April 2018 Version

31 Appendix 2: SEPA reason codes If a SEPA Credit Transfer or Direct Debit is returned, a reason code or return code is provided. This table contains the most frequently applicable reason codes and description. Return reason code Description Return reason code Description AC01 AC04 AC06 AC13 Account number incorrect. Account number closed. Euro Direct Debit blocked. Debtor account is a consumer account. MD06 MD07 MS02 MS03 Return of funds requested by end customer. Administrative reason. Refused by debtor. Refused by bank. AG01 Administrative reason. PC01 Technical reason. AG02 Invalid file format. PC02 Technical reason. AGNT Incorrect BIC bank beneficiary. PC03 Technical reason. AM04 Administrative reason. RC01 BIC incorrect. AM05 Duplicate order. R001 Order not allowed. BE04 Address beneficiary missing. R002 Order too late or too early. BE05 Remitter unknown. R003 Account not found. CURR Incorrect currency. R004 Not allowed on G-account. CUST Debtor cancellation. RR01 Administrative reason. CUTA Rejected. RR02 No name and address debtor. DUPL Duplicate order. RR03 No name and address or. FF01 Invalid file format. RR04 Administrative reason. FF05 Direct type is not correct. SL01 Administrative reason. FOCR Cancellation request. TECH Technical reason. MD01 No mandate. TM01 Received after cut-off time. MD02 Incorrect mandate. UPAY Order not allowed. Rabobank Format description CAMT.052 April 2018 Version

32 Appendix 3: Future changes Expected changes The Dutch Payments Association (= De Betaalvereniging) has published in mid 2016 CAMT.053 version 2.0: v2.0.pdf Compared to version 1.1, version 2.0 includes changes of CAMT which ensures the compliance of Dutch guidelines towards the Common Global Implementation Guideline (CGI). Moreover, the changes puts the differences between the Dutch banks to a minimal. Most changes applicable to the CAMT.053 also applies for CAMT.052. Implementation of these changes has not yet been planned by Rabobank. More information will be published as soon as possible on the website Future changes Future versions of the CAMT052 as available through Rabo Internetbanking (Professional), Rabo Direct Connect and SWIFT FileAct may contain the additions listed in the table below. Index Name Addition Expected implementation Additional Transaction Information End To End Identification Mandate Identification Additional Transaction Information To supply the Creditor ID with code word /CSID/. For CAMT052 of savings account: Missing SEPA references of savings transactions will be reported. Available since mid February 2018 Unkown Debtor Name Creditor Name For CAMT052 of savings account: Missing the name of the counterparty of non-sepa savings transactions. Unkown Note: the name can now be found in the Unstructured Remittance Information (tag 2.235). Rabobank Format description CAMT.052 April 2018 Version

33 Change Log Title: Format Description CAMT.052 Rabo Internetbanking (Professional), Rabo Direct Connect and SWIFT FileAct Version: 1.0 Date: Contact: For RIB (Pro): Helpdesk Rabo Internet- and Mobielbanking For RDC and SWIFT FileAct: For RDC and SWIFT FileAct: corporatesupport@rabobank.com Date Version Type of change Reason change Format description available in English language for RIB (Pro). New For RIB (Pro), RDC and SWIFT FileAct it is expected that Multibank and Rabobank Network Banking accounts are available in Q Creditor Scheme Identification is available again since mid February Expected implementation Q Anouncement Rabobank Format description CAMT.052 April 2018 Version