Format description Generic Payment File version Rabo Direct Connect, SWIFT FileAct & Rabo Internet banking (Professional)

Transcription

1 Format description Generic Payment File version Rabo Direct Connect, SWIFT FileAct & Rabo Internet banking (Professional)

2 Contents 1 GENERAL GENERAL CHARACTERISTICS STRUCTURE Introduction Technical mapping Character set Compatibility Message structure PAYMENT DETERMINATION PROCESSING SCHEMA SEGMENT DESCRIPTION GROUP HEADER PAYMENT INFORMATION SEGMENT TRANSACTION INFORMATION SEGMENT APPENDI A PARTY IDENTIFIER APPENDI B PAYMENT INFORMATION PER COUNTRY CHANGELOG Rabobank Format description Generic Payment File December 2018 Version

3 1 General Rabobank offers the possibility to import batches with, Urgent, Urgent Domestic, Worldpayments and using one payment file format. This format concerns the pain standard which is already being used for within the Single Euro Payment Area (SEPA) and will be referred to by Rabobank - because of the broader usage of the format and differences between Euro- and Wordpayments - as the Generic Payment File format. A file in the Generic Payment File format may contain one (1) or more batches, and a batch can contain one or more payments being debited from a single current account. Furthermore the characteristics of a batch are that the payment(s) within the batch will be processed using the specified Requested Execution Date; And when the batch contains more than one payment, the payment type for all payments must be equal. When the Generic Payment File contains as well as Worldpayments these payments must be presented in separate batches - one batch may not contain both Euro- and Worldpayments. Both Urgent and Worldpayments may be present in one batch. 1.1 General characteristics The Generic Payment File format supported by Rabobank is based on the specifications which are published on the website of the International Organisation for Standardization (ML ISO20022) and complies to the Implementation Guidelines as specified by the Common Global Implementation 1. This document contains the format description for Generic Payment File format as supported by the Rabobank systems Rabo Direct Connect (RDC), SWIFT FileAct and Rabobank Internetbanking (Professional). 1.2 Structure Introduction A Generic Payment File contains (batches with) payments using the Extensible Markup Language (ML), which is a structured language containing all necessary attributes (tags and content) to be able to process payments. To be able to check if the structure and used attributes are correct the Generic Payment File can be validated against the ML Schema Definition (SD) which is published on the ISO20022 website. This SD can be obtained via Technical mapping To avoid rejection of payments and/or to prevent that instructions are ignored usage rules must be followed. Only message elements which are described within these guidelines are allowed to be used: 1 The Common Global Implementation (CGI) group aims to achieve a high degree of standardization as to limit the obstacles users encounter when implementing ML credit transfer formats. Please refer to for more information. Rabobank Format description Generic Payment File December 2018 Version

4 ML-tag ISO ref. Level Presence Name of the element within the Generic Payment File message Short name to identify an element within a ML message, presented between brackets, f.e. <Amt> which means Amount. Numbering following the ISO standard. Not all fields are numbered. Fields can be a subset of the parenting element. Gaps in the numbering do exist because not all elements of ISO20022 are supported. Level of the element within the Generic Payment File message <Top> <Level 1> <Level 2> <Etc.>..</Etc.> </Level 2> </Level 1> </Top> 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. [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 presented n times. Type Length Description Urgent Domestic Worldpayments + Urgent A sub level element is mandatory only if the (optional) element above is present. Field type indication: - Numeric: only numbers are allowed - Alphanumeric: may contain numbers and allowed characters (ref Character set) - Date: CCYY-MM-DD - Amount: numbers, with a decimal point as separator. The presentation of the number of decimals are compliant with ISO4217. The maximum length is 9 digits before the separator, and two behind it. - Boolean: field with two options: true or false Maximum number of characters in the field. Contains the definition of the message segment or element. Additional information about usage of the element. Indication '' means that this field is used for this type of payment. Indication '' means that this field is used for this type of payment. Indication '' means that this field is used for this type of payment. Indication '' means that this field is used for this type of payment. When a message contains end-of-line characters and/or tab-characters, Carriage Return and LineFeed (hexadecimal values 0x0D and 0x0A or decimal ASCII character values 13 and 10) respectively, or a tab - Horizontal Tab (hexadecimal value 0x09 or decimal ASCII character value 9), these characters are only allowed outside of the ML-tags; these characters are not allowed within the tags or as field values. The only practical use for these end-of-line and tab characters is for readability/presentation within an editor which does not support a ML formatted presentation/view of the information (and f.e. will present all the ML information in one line). Rabobank Format description Generic Payment File December 2018 Version

5 2 A Character set In Generic Payment File messages the standard UTF8 encoding must be used, using the Latin characters which are common for international communication. Rabobank accepts the following characters 1 : 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 UTF-8 must be used as the default way of encoding characters. Characters with a different coding (for example ISO ) may lead to rejected files. Rabobank accepts the extended character set as recommended by the EPC. Fields which are used to identify a batch or payment (transaction) are excluded from this extended character set. For pain.001 it includes the following fields: <PmtInfId>, <InstrId> and <EndToEndId> Compatibility Currently are completely processed via ML formatted messages by all parties involved in the payment chain. Worldpayments and Urgent however are not yet processed via ML formatted messages, these payments are processed and forwarded using legacy formats2 within the payment chain. These legacy formats offer limited or no support for certain tags/fields within the ML messages, which is why information within these tags/fields can be truncated or lost. Also there are options (fields) which are not allowed for yet relevant for World- or Urgent : For example for Worldpayments it is possible to present an address via the tag/field InstructionsForDebtorAgent to have the bank send a payment confirmation to this address. This option is not available for. The following payments are supported for Rabobank accounts including Rabo Network Banking accounts (=accounts which are held with Rabobank in Belgium, Germany and The United Kingdom: - payments in the EUR currency to a beneficiary in a SEPA country. Urgent Domestic - urgent payments in the EUR currency between Dutch bank accounts. Not available for Rabo Network Banking accounts. Urgent - urgent payments in the EUR currency to a beneficiary in a SEPA country. 1 Rabobank accepts diacritical characters, these characters will not be converted to the characters as specified in 2.3. Depending on the diacritical characters being used, there is a risk that payments containing these characters will not be processed by the bank of the beneficiary (when the bank of the beneficiary does not allow or support these characters). legacy format for customer to bank transfer (for Worldpayments) is the BTL91 format, between banks the SWIFT FIN MT103 message standard is used for non-sepa credit transfers. The term legacy format is used relative to the pain format, it does not mean that SWIFT FIN messages are old or outdated. Rabobank Format description Generic Payment File December 2018 Version

6 Worldpayments - payments in foreign currency and EUR outside the SEPA area. The following payments are supported for foreign non-rabobank accounts: - payments from accounts held with other banks. Important information about Urgent Domestic and Urgent : Whereas it is guaranteed in The Netherlands that an Urgent Domestic Europayment will be available on the account of the beneficiary within 1,5 hours, for an Urgent Europayment we can only guarantee that the bank of the beneficiary will have received the payment within 1,5 hours (not guaranteed for the beneficiary). Therefore Urgent Domestic payments are a separate type of payment from Urgent. Both Worldpayments and Urgent are processed equally (using the same fields/tags) and sent as urgent payments, the difference being that Worldpayments will by default always be treated as urgent payments whereas for Urgent it is mandatory to indicate that these (Euro)payments must be treated as urgent payments. Between Urgent Domestic and Urgent there are a few differences in which fields/tags must be used and filled, these differences can be found in the Description column of chapter 4.2 PaymentInformationSegment from page 12 onwards Message structure A Generic Payment File message contains 3 segments/building blocks: 1. Group Header; This building block is mandatory and present once. It contains elements such as Message Identification, Creation Date and Time. 2. Payment Information (this segment/building block is also referred to as batch level; This building block is mandatory and repetitive. Besides elements related to the debit side of the transaction, such as Debtor and Payment Type Information, it contains one or more Transaction Information Blocks. 3. (Credit Transfer) Transaction Information, this segment/building block is also referred to as payment level; This building block is mandatory and repetitive. It contains, amongst others, elements related to the credit side of the transaction, such as Creditor and Remittance Information. The number of occurrences of Payment Information Block and Transaction Information Block within a message is indicated by the Grouping field in the Group Header. Every segment/building block within the Generic Payment File must be opened and closed according to the SD defenition. Between the opening tag and closing tag the information for this tag is contained. Rabobank Format description Generic Payment File December 2018 Version

7 A ML-pain file/message has the following structure: Rabobank Format description Generic Payment File December 2018 Version

8 2 Payment determination This chapter provides information about the way in which Rabobank will determine and process payments on Payment Information Segment level and Transaction Information Segment level, called Batch level and Payment level respectively. Details about the index numbers used in the schema below can be found in the next chapter 3 Segment description. 2.1 Processing schema Batch level Payment level PaymentTypeInformation (2.6) PaymentTypeInformation (2.31) ServiceLevel Code ServiceLevel Code How payments will be processed Empty or SEPA Empty or SEPA Only to be used for. Not allowed for Worldpayments, Mu;tibank payments, Urgent, and Urgent Domestic, these will be rejected Other value than SEPA Payment containing ServiceLevel code other than SEPA will be rejected NURG or SDVA Empty Only allowed for Worldpayments and Multibank payments Any value No ServiceLevel code allowed on Payment level URGP Empty Only allowed for Worldpayments, Multibank payments, Urgent Domestic and Urgent. Any value No ServiceLevel code allowed on Payment level Rabobank Format description Generic Payment File December 2018 Version

9 3 Segment description This chapter describes all tags/fields which are relevant to, Urgent, Urgent Domestic, Worldpayments and Multibank payments. Tags/fields which are supported in the pain format but are not used or supported by Rabobank are omitted. If such fields are present in the file they will be ignored but have to comply with SD. 3.1 Group Header Name ML-tag Level Presence Type Length Description Document <Document> Top [1..1] <CstmrCdtTrfInitn> Top [1..1] GroupHeader 1.0 <GrpHdr> Top [1..1] MessageIdentification 1.1 <MsgId> 1 [1..1] Alphanumeric Max. 35 Unique file identification. CreationDateTime 1.2 <CreDtTm> 1 [1..1] Date and Creationdate and time of the file. time Example: T09:10:15. NumberOfTransactions 1.6 <NbOfTxs> 1 [1..1] Numeric Max. 15 Number of payments in the file. ControlSum 1.7 <CtrlSum> 1 [0..1] Numeric Max. 18 Total/sum of all the individual payments, regardless of the currency. Decimals are separated by a point.. Urgent Domestic Worldpayments + Urgent Rabobank Format description Generic Payment File December 2018 Version

10 ML-tag Level Presence Type Length Description InitiatingParty 1.8 <InitgPty> 1 [1..1] Name <Nm> 2 [0..1] Alphanumeric Max. 70 Name of the ordering party. Identification <Id> 2 [0..1] This tag/field is ignored for Worldpayments,, Urgent and Urgent Domestic. For please refer to appendix A. Urgent Domestic Worldpayments + Urgent Rabobank Format description Generic Payment File December 2018 Version

11 3.2 Payment Information Segment Name ML-tag Level Presence Type Length Description PaymentInformation 2.0 <PmtInf> Top [1..n] PaymentInformationIdentification 2.1 <PmtInfId> 1 [1..1] Alphanumeric Max. 35 Unique reference number for the batch/pi. For Worldpayments,, Urgent and Urgent Domestic this information is not presented in the account information (account statements, account information download formats). PaymentMethod 2.2 <PmtMtd> 1 [1..1] Alphanumeric 3 Fixed mandatory value TRF for payments. BatchBooking 2.3 <BtchBookg> 1 [0..1] Boolean 4 or 5 When the value true is provided for, only the total amount will be shown in one debit transaction in the account information. When the value false is provided all will be presented individually in the account information. When this tag is not provided Rabobank will use the value true when processing the. Note: in case of value false, there is a maximum of payments per batch. In case the batch exceeds the maximum of 5.000, the batch will be rejected. Urgent Domestic Worldpayments + Urgent Rabobank Format description Generic Payment File December 2018 Version

12 ML-tag Level Presence Type Length Description For Worldpayments,, Urgent and Urgent Domestic this tag is ignored, regardless if a value is provided all payments will be presented individually in the account information. NumberofTransactions 2.4 <NbOfTxs> 1 [0..1] Numeric Max. 15 Number of payents in the batch/pi. ControlSum 2.5 <CtrlSum> 1 [0..1] Amount Max. 18 Total/sum of all the individual payments in the batch (this segment). Decimals are separated by a point.. PaymentTypeInformation 2.6 <PmtTpInf> 1 [0..1] The subtags below may either be present on this level or on batch level (2.31), unless otherwise described. InstructionPriority 2.7 <InstrPrty> 2 [0..1] Alphanumeric 4 Any value specified will be ignored during processing, even if the value contradicts the value which is provided in tag 2.9 <Cd>. For the value NORM is commonly used (however, as mentioned, any value specified will be ignored). ServiceLevel 2.8 <SvcLvl> 2 [0..1] For this tag is not mandatory and SEPA may be presented on this (batch) level via 2.9 <Cd> or on 2.34 payment level, but not on both levels; For Worldpayments, Urgent, Urgent Domestic and it is mandatory to provide this tag for processing these Urgent Domestic Worldpayments + Urgent Rabobank Format description Generic Payment File December 2018 Version

13 ML-tag Level Presence Type Length Description payments in the Rabobank payment processing systems. Code 2.9 <Cd> 3 [1..1] Alphanumeric 4 The Rabobank only accepts one of the following values: NURG, URGP, SDVA, SEPA. Urgent Domestic Worldpayments + Urgent - SEPA for - URGP for Urgent Domestic and Urgent. - SDVA, NURG and URGP 1 for Worldpayments and Multibank Payments For Worldpayments, Urgent, Urgent Domestic Payments and it is mandatory to provide one of the mentioned values. When the Servicelevel/Code is omitted all payments will be processed as and consequently be rejected. This tag/field may only be provided on (this) batch level. LocalInstrument 2.11 <LclInstrm> 2 [0..1] This field/tag and underlying fields/tags are only used for. For Worldpayments, Urgent, Urgent Domestic and this field/tag will be ignored. 1 Worldpayments are always processed by Rabobank as urgent payments, provided that these payments are provided before cut-off time and correctly (Straight Through Processing, i.e. without manual intervention or correction by Rabobank); it remains possible to indicate that Worldpayments are to be processed as urgent payments, but regardless of the value provided all such payments are processed as urgent payments by default. Rabobank Format description Generic Payment File December 2018 Version

14 ML-tag Level Presence Type Length Description Urgent Domestic Worldpayments + Urgent Code 2.12 <Cd> 3 [1..1] {OR Alphanumeric Max. 35 For within The Netherlands only the value ACCEPT is allowed and relayed to the bank of the beneficiary, provided that the tag/field BatchBooking contain the value false. Should the tag/field contain the value true and LocalInstrument/Code contain the value ACCEPT the batch will be rejected. This tag can be presented on batch/pi level or on payment level (2.37), but not on both levels. Other values for this tag will be ignored. Proprietary 2.13 <Prtry> 3 [1..1] OR} Alphanumeric Max. 35 This information is not used for processing CategoryPurpose 2.14 <CtgyPurp> 2 [0..1] For Worldpayments, Urgent and Urgent Domestic this field/tag and underlying fields/tags will be ignored. Code 2.15 <Cd> 3 [1..1] {OR Alphanumeric 4 Rabobank accepts and forwards all ISO Category Purpose codes to the bank of the beneficiary. This tag can be presented on batch/pi level or on payment level (2.40), but not on both levels. For : The code INTC will be used by Rabobank for, other codes will be forwarded to the Servicing bank (where the payment will be Rabobank Format description Generic Payment File December 2018 Version

15 ML-tag Level Presence Type Length Description processed). Urgent Domestic Worldpayments + Urgent For : Only the code SALA for salary payments is being used by Rabobank to present and process such payments separately. When using the code SALA in combination with BatchBooking true only the total debited amount will be shown in the account information (no individual salary payment information will be available). Proprietary 2.16 <Prtry> 3 [1..1] OR} Alphanumeric Max. 35 With and the information provided in this field will be forwarded to the receiving bank, for this field can be used to provide codewords which are not available in the CategoryPurpose list (f.e. OTHR/ABCD). Rabobank ignores the value provided in this field for Worldpayments, Urgent and Urgent Domestic. This tag/field can be presented on batch/pi level or on payment level (2.41), not on both levels. RequestedExecutionDate 2.17 <ReqdExctnDt> 1 [1..1] Date This is the date on which the originator s account is to be debited. When a date is provided which is until Rabobank Format description Generic Payment File December 2018 Version

16 ML-tag Level Presence Type Length Description 14 days in the past this date is changed by Rabobank to the first possible processing date; when a date is provided which is older than 14 days the batch will be rejected. It is possible to provide a date for future processing until 365 calendar days. Debtor 2.19 <Dbtr> 1 [1..1] Name <Nm> 2 [1..1] Alphanumeric Max. 70 The name of the initiating party is mandatory. For Urgent Domestic the name provided in this tag/field will be used; For, Worldpayments, Multibank payments and Urgent Domestic the name provided will be overwritten with the statutory name as registered for the account by Rabobank. PostalAddress <PstlAdr> 2 [0..1] For and Urgent Domestic the fields Country and AddressLine are available, these are not mandatory. Urgent Domestic Worldpayments + Urgent For Worldpayments, Urgent and the fields StreetName, PostCode, TownName en Country are available. StreetName <StrtNm> 3 [0..1] Alphanumeric Max. 70 This field is only used for Worldpayments, Urgent and PostalCode <PstCd> 3 [0..1] Alphanumeric Max. 16 This field is only used for Worldpayments, Urgent Rabobank Format description Generic Payment File December 2018 Version

17 ML-tag Level Presence Type Length Description and TownName <TwnNm> 3 [0..1] Alphanumeric Max. 35 This field is only used for Worldpayments, Urgent and Country <Ctry> 3 [0..1] Alphanumeric 2 Country where the initiating party resides, used for, Urgent Domestic, Urgent, Worldpayments and. AddressLine <AdrLine> 3 [0..2] 1 Alphanumeric Max. 70 Address of the initiating party, used for and Urgent Domestic : 1 e line: Street and housenumber 2 e line: Postal code and city. Urgent Domestic Worldpayments + Urgent Voor Urgent Domestic only the first 35 positions from the 1 st address line will be used and the first 35 positions from the 2 nd address line. The positions after the 35 th position on the 1 st and 2 nd address lines will be ignored. Identification <Id> 2 [0..1] This tag/field is ignored for Worldpayments, Urgent, Urgent Domestic and. For please refer to appendix A. DebtorAccount 2.20 <DbtrAcct> 1 [1..1] 1 The ISO20022 standard allows up to 7 address lines, however the EPC has limited the number of lines to 2 address lines. Rabobank Format description Generic Payment File December 2018 Version

18 ML-tag Level Presence Type Length Description Identification <Id> 2 [1..1] IBAN <IBAN> 3 [1..1] {OR Alphanumeric Max. 34 IBAN account number of the initiating party. Only use numbers and capital letters in the IBAN, usage of spaces is not allowed. Other <Othr> 3 [0..1] OR} Identification <Id> 4 [1..1] Alfanumeriek Max. 34 This field is only allowed for, and when specified may only contain a BBAN. It is not allowed for to provide a value for both this field <Id> as well as the <IBAN> field. Currency <Ccy> 2 [0..1] Alphanumeric 3 ISO currency code of the account. For, Urgent, Urgent Domestic and the currency code of the account is not mandatory. For Worldpayments it is mandatory to provide the currency code of the account in this tag/field. - When the currency code of the account is provided, the following rules apply: EUR-account, payment currency non-eur, is allowed (will be processed). USD-account (example), payment currency JPY: will Urgent Domestic Worldpayments + Urgent Rabobank Format description Generic Payment File December 2018 Version

19 2 The Name ML-tag Level Presence Type Length Description be processed for Rabobank WRR 1 accounts. USD-account (example), payment currency JPY: will not be processed for Rabobank (Nederland) 2 accounts, the payment will be rejected. DebtorAgent 2.21 <DbtrAgt> 1 [1..1] FinancialInstitutionIdentification <FinInstnId> 2 [1..1] BIC <BIC> 3 [0..1] {OR Alphanumeric 8 of 11 SWIFT BIC code from the bank of the initiating party. This field/tag is optional [0..1] however necessary (and therefore mandatory) for when the account of the initiating party is held with a bank outside of the SEPA area. Only numbers and capital letters are allowed. Other <Othr> 3 [0..1] OR} Identification <Id> 4 [1..1] Alphanumeric 11 When present, i.e. when no BIC has been provided, Rabobank advises to provide the value NOTPROVIDED in this field, however this value is not validated by Rabobank. Urgent Domestic Worldpayments + Urgent UltimateDebtor 2.23 <UltmtDbtr> 1 [0..1] This field/tag and underlying fields/tags are ignored for Worldpayments, Urgent, Urgent 1 Wholesale, Rural and Retail (WRR) refers to the Rabobank Current Account system for customers from (previously called) Rabobank International, for accounts in this system it is possible to transfer an amount using a currency amount which is different from the currency of the account itself Current Account system for customers from Rabobank Memberbanks (previously called) Rabobank The Netherlands where, contrary to WRR accounts, it is not allowed to transfer an amount in a currency that is different from the currency of the account itself Rabobank Format description Generic Payment File December 2018 Version

20 ML-tag Level Presence Type Length Description Domestic Payments and. Urgent Domestic Worldpayments + Urgent This element may not be present together with element Both elements may be absent. Name <Nm> 2 [0..1] Alphanumeric Max. 70 Name of the (ultimate) initiating party. This name is transferred to the bank of the beneficiary. Identification <Id> 2 [0..1] For please refer to appendix A. ChargeBearer 2.24 <ChrgBr> 1 [0..1] Alphanumeric 4 - For only the value SLEV is allowed. - For Urgent Domestic Payments, Urgent, Worldpayments and within the EER only the value SHAR is allowed. - For all other Worldpayments and Multibank payments the following values are allowed: CRED - all costs for the beneficiary (BEN) DEBT - all costs for the initiating party (OUR) SHAR - costs are shared between the initiating party and the beneficiary (SHA) Note: When no value is provided the option SHAR will be used. Rabobank Format description Generic Payment File December 2018 Version

21 ML-tag Level Presence Type Length Description Urgent Domestic Worldpayments + Urgent ChargeBearer may be present on this level or transaction level (2.51) but not on both levels. Rabobank Format description Generic Payment File December 2018 Version

22 3.3 Transaction Information Segment Name ML-tag Level Presence Type Length Description CTTransactionInformation 2.27 <CdtTrfTxInf> 1 [1..n] PaymentIdentification 2.28 <PmtId> 2 [1..1] This tag/field and underlying tags/fields are used for, and will be ignored for Worldpayments,, Urgent Urgent and Urgent Domestic. Urgent Domestic Worldpayments + Urgent Important: Because of the fact that this tag/field is mandatory, according to the [1..1] presence (SD) a value must be provided for Worldpayments, Multibank payments, Urgent and Urgent Domestic in the underlying tag/field <EndToEndId> even though this value will not be used when processing these payments. InstructionIdentification 2.29 <InstrId> 3 [0..1] Alphanumeric Max. 35 Instructions from the initiating party for Rabobank. This tag/field is not forwarded to the bank of the beneficiary. EndToEndIdentification 2.30 <EndToEndId> 3 [1..1] Alphanumeric Max. 35 End-to-End ID for the payment, will be forwarded to the beneficiary bank for. PaymentTypeInformation 2.31 <PmtTpInf> 2 [0..1] The subtags below may either be present on this level or on batch level (2.6), unless otherwise described. InstructionPriority 2.32 <InstrPrty> 3 [0..1] Alphanumeric 4 Either the value NORM or HIGH is allowed. The value specified will be ignored during processing. Rabobank Format description Generic Payment File December 2018 Version

23 ML-tag Level Presence Type Length Description ServiceLevel 2.33 <SvcLvl> 3 [0..1] Code 2.34 <Cd> 4 [0..1] Alphanumeric 4 For via Generic Payment File this tag is not mandatory and may be presented on this (payment) level or on 2.8 batch level, but not on both levels. When specified on this level for, only the value SEPA is allowed. Urgent Domestic Worldpayments + Urgent For Worldpayments, Urgent, Urgent Domestic Payments and it is not allowed to provide a value for this tag/field, for these payments it is only allowed to provide a value on 2.9 batch level. CategoryPurpose 2.39 <CtgyPurp> 3 [0..1] For Worldpayments, Urgent and Urgent Domestic this field/tag and underlying fields/tags will be ignored. Code 2.40 <Cd> 4 [1..1] {OR Alphanumeric 4 Rabobank accepts and forwards all ISO Category Purpose codes to the bank of the beneficiary. This tag can be presented on batch/pi level (2.15) or on payment level, but not on both levels. For : The code INTC will be used by Rabobank for, other codes will be forwarded to the Servicing bank (where the payment will be processed). Rabobank Format description Generic Payment File December 2018 Version

24 ML-tag Level Presence Type Length Description For Worldpayments towards a Multibank account: The code INTC will only be used when the Rabobank recognizes the beneficiary account to be a Multibank account. Urgent Domestic Worldpayments + Urgent For : Only the code SALA for salary payments is being used by Rabobank to present and process such payments separately. When using the code SALA in combination with BatchBooking true only the total debited amount will be shown in the account information (no individual salary payment information will be available). Proprietary 2.41 <Prtry> 4 [1..1] OR} Alphanumeric Max. 35 With and the information provided in this field will be forwarded to the receiving bank, for this field can be used to provide codewords which are not available in the CategoryPurpose list (f.e. OTHR/ABCD). Only the first codeword will be forwarded to the receiving bank. Rabobank ignores the value provided in this field for Worldpayments, Urgent and Urgent Domestic. This tag/field can be presented on batch/pi level (2.16) or on payment level, not on both levels. Rabobank Format description Generic Payment File December 2018 Version

25 ML-tag Level Presence Type Length Description Amount 2.42 <Amt> 2 [1..1] InstructedAmount 2.43 <InstdAmt> 3 [1..1] Amount Max. 18 Amount of the payment. Decimals are separated with a point.. The amount provided must be a value between 0.01 and 999,999, (technical limit), where the real possible upper limit is determined by regulatory restrictions for the selected payment type. Urgent Domestic Worldpayments + Urgent The currency for the amount must be provided within the tag: <InstdAmt Ccy= > where must be a valid ISO currency code (f.e. EUR, USD, GBP, JPY, etc.). ChargeBearer 2.51 <ChrgBr> 2 [0..1] Alphanumeric 4 - For only the value SLEV is allowed. - For Urgent Domestic Payments, Urgent, Worldpayments and within the EER only the value SHAR is allowed. - For all other Worldpayments and Multibank payments the following values are allowed: CRED - all costs for the beneficiary (BEN) DEBT - all costs for the initiating party (OUR) SHAR - costs are shared between the initiating party and the beneficiary (SHA) Note: When no value is provided the option SHAR will be used. Rabobank Format description Generic Payment File December 2018 Version

26 ML-tag Level Presence Type Length Description Urgent Domestic Worldpayments + Urgent ChargeBearer may be present on this level or batch (2.24) but not on both levels. Ultimate Debtor 2.70 <UltmtDbtr> 2 [0..1] This tag/field and underlying tags/fields are ignored (not used) for Worldpayments,, Urgent and Urgent Domestic. This element may not be present together with element Both elements may be absent. Name <Nm> 3 [0..1] Alphanumeric Max. 70 Name of the ultimate debtor (ultimate initiating party). The information provided in this tag/field will not be sent to the bank of the beneficiary. Identification <Id> 3 [0..1] Please refer to appendix A. IntermediaryAgent This tag/field can only be used for Worldpayments <IntrmyAgt1> 2 [0..1] and is required when specific routing of the payment is required by the bank of the beneficiary. Usage of this tag/field will result in extra charges. For, and Urgent Domestic this tag/field is ignored. FinancialInstitutionIdentification <FinInstId> 3 [1..1] BIC <BIC> 4 [1..1] Alphanumeric Max 11 SWIFT BIC code of the bank of the intermediary agent. Only numbers and capital letters are allowed. ClearingSystemMember <ClrSysMmbId> 4 [0..1] Data from the underlying tags only used when the bank Identification (intermediary) cannot be retrieved from the provided BIC or name and location. Rabobank Format description Generic Payment File December 2018 Version

27 ML-tag Level Presence Type Length Description ClearingSystemIdentification <ClrSysId> 5 [1..1] This field is mandatory to identify the MemberID. Code <Cd> 6 [1..1] Alphanumeric Max 35 The bank code provided via this tag/field must be the code of the bank in the country where the bank resides, for example USABA for an ABA number for a payment towards a bank in the United States. A list of permitted National Bank codes can be found in Appendix B Payment information per country. Only codes mentioned in the Appendix may be used. Codes which are not mentioned in the appendix will be rejected. Urgent Domestic Worldpayments + Urgent Rabobank will not check if the bank code provided is a valid bank code, i.e. if the bank code matches with the provided BIC of the beneficiary bank. This tag/field will be relayed. MemberIdentification <MmbId> 5 [1..1] Alphanumeric Max 35 The national bank code for the Clearing System bank in the country where the intermediary bank resides. Specifications of which the National Bank Codes must fulfill can be found in Appendix B Payment information per country. CreditorAgent 2.77 <CdtrAgt> 2 [0..1] For and Urgent Domestic : Only BIC may be provided. For Worldpayments, and Urgent : Rabobank strongly recommends to Rabobank Format description Generic Payment File December 2018 Version

28 ML-tag Level Presence Type Length Description provide the BIC. When the BIC is not provided, it is mandatory to provide the name, country code and the townname from the bank of the beneficiary. If the BIC is not provided or the beneficiary s bank does not have a BIC, it is highly recommended to supply the National Bank Code in tags ClearingSystemIdentification and MemberId. Urgent Domestic Worldpayments + Urgent When 2.71 IntermediaryAgent information is provided the payment will be routed accordingly; when no information is provided via this tag/field, the payment will be routed via the CreditorAgent. FinancialInstitutionIdentification <FinInstnId> 3 [1..1] BIC <BIC> 4 [0..1] Alphanumeric 8 of 11 SWIFT BIC code from the bank of the beneficiary. Usage of this tag/field is optional. Only numbers and capital letters are allowed. For : Rabobank will always determine the BIC from the bank of the beneficiary; when the BIC can be determined, the BIC provided via this tag/field will be overwritten with the determined BIC; When Rabobank cannot determine the BIC, the BIC specified via this tag/field will be used; Should the BIC be invalid, the payment will be rejected. For Worldpayments,, Urgent Rabobank Format description Generic Payment File December 2018 Version

29 ClearingSystemMember Identification ML-tag Level Presence Type Length Description and Urgent Domestic Payments: When no BIC is specified Rabobank will try to determine the BIC from the bank of the beneficiary, and when the BIC can be found/determined it will be used for the payment; When no BIC is specified and Rabobank is not able to determine the BIC, the name country code and town name from the bank of the beneficiary will be used for the payment; When no BIC is provided, and no name and country code (from the beneficiary bank) are provided, the payment will be rejected. <ClrSysMmbId> 4 [0..1] This tag/field may only be used for Worldpayments and Urgent. Urgent Domestic Worldpayments + Urgent Rabobank will determine the National Bank Code on the basis of the specified IBAN or BBAN. If this cannot be derived, Rabobank uses the supplied National Bank Code to determine the BIC. Irrespective of whether or not Rabobank uses the information provided, it must comply with the SD. ClearingSystemIdentification <ClrSysId> 5 [1..1] This field is mandatory to identify the MemberID. Code <Cd> 6 [1..1] Alphanumeric Max. 5 The bank code provided via this tag/field must be the code of the bank in the country where the bank resides, for example USABA for an ABA number for a payment towards a bank in the United States. A list of permitted National Ban Codes can be found in Rabobank Format description Generic Payment File December 2018 Version

30 ML-tag Level Presence Type Length Description Appendix B Payment information per country. Only codes mentioned in the Appendix may be used. Codes which are not mentioned in the appendix will be rejected. Urgent Domestic Worldpayments + Urgent Rabobank will not check if the bank code provided is a valid bank code, i.e. if the bankcode matches with the provided BIC of the beneficiary bank. This tag/field will be relayed. MemberIdentification <MmbId> 5 [1..1] Alphanumeric Max. 35 The national bank code for the Clearing System bank in the country where the bank of the beneficiary resides. Specifications of which the National Bank codes must fulfill can be found in Appendix B Payment information per country. Name <Nm> 4 [0..1] Alphanumeric Max. 35 Name of the bank of the beneficiary. For Worldpayments, and Urgent it is mandatory to provide this name when no BIC is provided. PostalAddress <PstlAdr> 4 [1..1] Country <Ctry> 5 [1..1] Alphanumeric 2 Country code of the country where the bank of the beneficiary resides. For Worldpayments, Multibank payments and Urgent it is mandatory to provide this code when no BIC is provided. AddressLine <AdrLine> 5 [0..2] Alphanumeric Max. 70 Address details of the bank of the beneficiary. The townname of bank beneficiary must at least be Rabobank Format description Generic Payment File December 2018 Version

31 ML-tag Level Presence Type Length Description provided. Urgent Domestic Worldpayments + Urgent Please note! Only the first 35 positions from the 1 st and 2 nd address lines will be used. The positions after the 35 th position on the 1 st and 2 nd address lines will be ignored. Creditor 2.79 <Cdtr> 2 [1..1] 1 Name <Nm> 3 [1..1] Alphanumeric Max. 70 Name from the beneficiary, mandatory for all payment types. Note: for payments from RNB accounts applies that the name of the Creditor have a maximum length of 35. If exceeding, the payment will be rejected. PostalAddress <PstlAdr> 3 [0..1] For and Urgent Domestic fields Country and AddressLine must be used but are not mandatory, except for Country for Urgent Domestic. For Worldpayments, and Urgent the fields StreetName, PostCode, TownName and Country must be used but are not mandatory except for Country. Please note: it is highly recommended to provide postal address information because of inquiries in 1 This tag/field is optional according to the ISO20022 standard, however Rabobank requires (i.e. mandatory) that the field is present. Rabobank Format description Generic Payment File December 2018 Version

32 ML-tag Level Presence Type Length Description case the information is not complete. StreetName <StrtNm> 4 [0..1] Alphanumeric Max. 70 This tag/field is mandatory for Worldpayments, and Urgent and must contain the location address, it is not allowed to specify a postal box address. PostalCode <PstCd> 4 [0..1] Alphanumeric Max. 16 This tag/field is mandatory for Worldpayments, Urgent and TownName <TwnNm> 4 [0..1] Alphanumeric Max. 35 This tag/field is mandatory for Worldpayments, Urgent and Country <Ctry> 4 [1..1] Alphanumeric 2 Country code of the country where the beneficiary resides. This field is mandatory for Urgent Domestic, Worldpayments, and Urgent. AddressLine <AdrLine> 4 [0..2] Alphanumeric Max. 70 Address information of the beneficiary, only used for and Urgent Domestic. For max. 2x70 positions: 1 st line: Street and house number 2 nd line: Postal code (zipcode) and city Urgent Domestic Worldpayments + Urgent For Urgent Domestic : Please note!: Only the first 35 positions from the 1 st and 2 nd address lines will be used. The positions after the 35 th position on the 1 st and 2 nd address lines will be ignored. Identification <Id> 3 [0..1] This tag/field is only used for. Please refer to appendix A. Rabobank Format description Generic Payment File December 2018 Version

33 ML-tag Level Presence Type Length Description Creditor Account 2.80 <CdtrAcct> 2 [1..1] Identification <Id> 3 [1..1] IBAN <IBAN> 4 [0..1] {OR Alphanumeric Max. 34 IBAN account number of the beneficiary. Only use numbers and capital letters in the IBAN, usage of spaces is not allowed. For it is mandatory to provide the IBAN of the beneficiary, when the IBAN is omitted the payment will be rejected. Other <Othr> 4 [0..1] OR} Only allowed for Woldpayments, and Urgent Identification <Id> 5 [1..1] Alphanumeric Max. 34 Account number of the beneficiary; When a BBAN is specified for a country where usage of an IBAN is mandatory the payment will be rejected. Currency <Ccy> 3 [0..1] Alphanumeric 3 ISO currency code for the account. Name <Nm> 2 [0..1] Alphanumeric Max. 70 Ultimate Creditor 2.81 <UltmtCdtr> 2 [0..1] This tag/field and underlying tags/fields will be ignored for Worldpayments,, Urgent and Urgent Domestic Name <Nm> 3 [1..1] Alphanumeric Max. 70 Name of the ultimate beneficiary. Country <Ctry> 4 [1..1] Alphanumeric 2 Country of the ultimate beneficiary. AddressLine <AdrLine> 4 [0..2] Alphanumeric Max. 70 Address information of the ultimate beneficiary. Identification <Id> 3 [0..1] Please refer to appendix A. InstructionsForDebtorAgent 2.85 <InstrForDbtrAgt> 2 [0..1] Alphanumeric Max. 140 This tag/field is only used for Worldpayments and Urgent : Specific instructions for the Rabobank, for example to Urgent Domestic Worldpayments + Urgent Rabobank Format description Generic Payment File December 2018 Version

34 ML-tag Level Presence Type Length Description request alternative routing or request to send a payment confirmation. Purpose 2.86 <Purp> 2 [0..1] This tag/field and underlying tags/fields are ignored for Worldpayments,, Urgent and Urgent Domestic. Code 2.87 <Cd> 3 [1..1] Alphanumeric 4 The list of allowed purpose codes can be found here: tab 11-Purpose. RemittanceInformation 2.98 <RmtInf> 2 [0..1] For either the Structured or Unstructured tags/fields may contain a value, not both. When both Structured and Unstructured tags/fields contain a value the payment will be rejected. For Worldpayments,, Urgent and Urgent Domestic only the Unstructured tag/field may contain a value; when the Structured tag/field contains a value, this value will be ignored. Unstructured 2.99 <Ustrd> 3 [0..1] {OR Alphanumeric Max. 140 For all 140 positions will be read and processed. Urgent Domestic Worldpayments + Urgent 1 For Urgent Domestic only the first 96 positions will be read and processed. Rabobank Format description Generic Payment File December 2018 Version

35 ML-tag Level Presence Type Length Description For Worldpayments, and Urgent only the first 98 positions will be read and processed. Urgent Domestic Worldpayments + Urgent Please note: For all payments/payment types there is a maximum of only one (1) Unstructured remittance line. Structured <Strd> 3 [0..1] OR} Structured remittance information is only allowed for. For Worldpayments,, Urgent and Urgent Domestic this tag/field is ignored. CreditorReferenceInformation <CdtrRefInf> 4 [0..1] Type <Tp> 5 [1..1] CodeOrProprietary <CdOrPrtry> 6 [1..1] Code <Cd> 7 [1..1] Alphanumeric 4 Only SCOR is allowed. Issuer <Issr> 6 [0..1] Alphanumeric Max. 35 Value CUR, ISO, BBA and other issuers are allowed. Rabobank does not check the content. Reference <Ref> 5 [1..1] Alphanumeric Max. 35 The max. length of Currence payment reference is 16. The max. length of ISO payment reference is 25 and starts with RF. The length of Belgium payment reference is 12. Other/own payment reference have a max length of 35. Rabobank does not check the content. Rabobank Format description Generic Payment File December 2018 Version

36 Appendix A Party identifier This appendix describes how the Party Identifier should be filled. The described structure is applicable for the following fields: Organisation Identification For the identification of the organization the BIC must be filled. The three columns to the right indicate for each scenario whether the Party Identifier information is passed on to the beneficiary bank () or ignored and not passed on (-). Name ML-tag level Presence Type Length Description OrganisationIdentification <OrgId> +1 [1..1] BICorBEI <BICOrBEI> +2 [0..1] {OR Alphanumeric 11 BIC of the organization Other <Othr> +2 [0..1] OR} Identification <Id> +3 [1..1] Alphanumeric 35 SchemeName <SchmeNm> +3 [0..1] Code <Cd> +4 [1..1] Alphanumeric 4 The ExternalOrganisationIdentification1Code This code can be found on tab 9-OrganisationIdentification Proprietary <Prtry> +4 [1..1] {OR Issuer <Issr> +3 [0..1] OR} Alphanumeric Alphanumeric Rabobank Format description Generic Payment File December 2018 Version

37 Private identification For the private identification the date and place of birth must be filled. In one occurrence you can use other. The three columns to the right indicate for each scenario whether the information is passed on to the beneficiary bank () or ignored and not passed on (-). Name ML-tag level Presence Type Length Description Private Identification <PrvtId> +1 [1..1] Date And Place Of Birth <DtAndPlcOfBirth> +2 [0..1] Birth date <BirthDt> +3 [1..1] Date 10 Province of Birth <PrvcOfBirth> +3 [0..1] Alphanumeric 35 City of Birth <CityOfBirth> +3 [1..1] Alphanumeric 35 Country of Birth <CtryOfBirth> +3 [1..1] Alphanumeric 2 ISO country code Other <Othr> +2 [0..1] Identification <Id> +3 [1..1] Alphanumeric 35 Scheme Name <SchmeNm> +3 [0..1] Code <Cd> +4 [1..1] {OR Alphanumeric 4 The ExternalPersonIdentification1Code This code can be found on tab 10-PersonIdentification Proprietary <Prtry> +4 [1..1] OR} Alphanumeric 35 Issuer <Issr> +3 [0..1] Alphanumeric 35 Rabobank Format description Generic Payment File December 2018 Version

38 Appendix B Payment information per country A national bank code uniquely identifies a bank or bank branch. For SEPA payments, providing a national bank code with your payment is not necessary as the IBAN is mandatory. A national bank code is available within the IBAN. The same is true for countries outside of the SEPA area that use the IBAN account format. Please refer to the IBAN registry available - here - for an overview of countries that use the IBAN as account number format. For non-sepa payments, providing a national bankcode can be essential. If BIC is not provided or beneficairy s bank has no NIC then it is highly recommended to supply the National Bank Code. The table 1 below gives an overview of the Clearing Systems that are registered with ISO, including the corresponding specifications of which the bank code must meet. Information is extracted from the ISO External code list which can be found on see tab '5- ClearingSystemIdentification'. Please note: only National Bank Codes mentioned in the table underneath, are allowed. All codes which are mentioned in the table will be rejected. For other payment information of countries mentioned in the table and information of countries which are not mentioned in the table, please refer to the webpage where payment information is described per country: (Dutch language only). Country Country code Content tag 2.71 and tag 2.77 Clearing System Identification Content tag 2.71 and 2.77 Member Identification Remarks Abbreviation National Bank Code Length Australia AU AUBSB Fixed length 6 Numbers Australian Bank State Branch Code (BSB-code): Bank Branch code used in Australia. Austria AT ATBLZ Fixed length 5 Numbers Austrian BankLeitZahl: Bank Branch code used in Austria. Canada CA CACPA Fixed length 9 Numbers Canadian Payments Association Payment Routing Number: Bank Branch code used in Canada. China CN CNAPS Fixed length 12 Numbers CNAPS Identifier: Bank Branch code used in China. Germany DE DEBLZ Fixed length 8 Numbers German Bankleitzahl: Bank Branch code used in Germany. Greece GR GRBIC Fixed length 7 Numbers Helenic Bank Identification Code: Bank Branch code used in Greece. Type 1 Updated on 7th December Rabobank Format description Generic Payment File December 2018 Version

39 Country Country code Content tag 2.71 and tag 2.77 Clearing System Identification Content tag 2.71 and 2.77 Member Identification Remarks Abbreviation National Bank Code Length Hong Kong HK HKNCC Fixed length 3 Numbers Hong Kong Bank Code: Bank Branch code used in Hong Kong. India IN INFSC Fixed length 11 Numbers and letters Indian Financial System Code: Bank Branch code used in India. Ireland IE IENCC Fixed length 6 Numbers Irish National Clearing Code: Bank Branch code used in Ireland. Italy IT ITNCC Fixed length 10 Numbers Italian Domestic Identification Code: Bank Branch code used in Italy. Liechtenstein LI CHBCC Length 3 or 5 Numbers Swiss Financial Institution Identification (short): Financial Institution Identification (IID) used in Switserland without check digits. New Zealand NZ NZNCC Fixed length 6 Numbers New Zealand National Clearing Code: Bank Branch code used in New Zealand. Poland PL PLKNR Fixed length 8 Numbers Polish National Clearing Code: Bank Branch code used in Poland. Portugal PT PTNCC Fixed length 8 Numbers Portuguese National Clearing Code: Bank Branch code used in Portugal. Russia RU RUCBC Fixed length 9 Numbers Russian Central Bank Identification Code: Russian Central Bank Id Code. South Africa ZA ZANCC Fixed length 6 Numbers South African National Clearing Code: Bank Branch code used in South Africa. Spain ES ESNCC Length 8 or 9 Numbers Spanish Domestic Interbanking Code: Bank Branch code used in Spain. Switserland CH CHBCC Length 3 or 5 Numbers Swiss Financial Institution Identification (short): Financial Institution Identification (IID) used in Switserland without check digits. United Kingdom GB GBDSC Fixed length 6 Numbers UK Domestic Sort Code: Bank Branch code used in the United Kingdom. United States US USABA Fixed length 9 Numbers United States Routing Number (Fedwire, NACHA): Routing Transit number assigned by ABA for financial institutions in the United States. Type Rabobank Format description Generic Payment File December 2018 Version