Format description Generic Payment File. Rabo Direct Connect & Rabo Internet banking (Professional)

Transcription

1 Format description Generic Payment File Rabo Direct Connect & 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 APPENDIX A PARTY IDENTIFIER APPENDIX B NATIONAL BANKCODE CHANGELOG Rabobank Format description Generic Payment File April 2018 Version 1.6 2

3 1 General Rabobank offers the possibility to import batches with Europayments, Urgent Europayments, Urgent Domestic Europayments, Worldpayments and Multibank payments using one payment file format. This format concerns the pain standard which is already being used for Europayments 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 then one payment, the payment type for all payments must be equal. When the Generic Payment File contains Europayments as well as Worldpayments these payments must be presented in separate batches - one batch may not contain both Euro- and Worldpayments. Both Urgent Europayments 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 (XML 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 system called Rabo Direct Connect (RDC). 1.2 Structure Introduction A Generic Payment File contains (batches with) payments using the Extensible Markup Language (XML), 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 XML Schema Definition (XSD) which is published on the ISO20022 website. This XSD 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 XML credit transfer formats. Please refer to for more information. Rabobank Format description Generic Payment File April 2018 Version 1.6 3

4 XML-tag ISO reference Level Presence Name of the element within the Generic Payment File message Short name to identify an element within a XML message, presented between brackets, f.e. <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. Type Length Description [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. 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: YYYY-MM-DD Amount: numbers, with a decimal point as separator. 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. 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 XML-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 XML formatted presentation/view of the information (and f.e. will present all the XML information in one line) Character set In Generic Payment File messages the standard standaard UTF8 encoding must be used, using the Latin characters which are common for international communication. Rabobank Format description Generic Payment File April 2018 Version 1.6 4

5 2 A 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 X 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 Europayments are completely processed via XML formatted messages by all parties involved in the payment chain. Worldpayments and Urgent Europayments however are not yet processed via XML 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 XML messages, which is why information within these tags/fields can be truncated or lost. Also there are options (fields) which are not allowed for Europayments yet relevant for World- or Urgent Europayments: 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 Europayments. The following payments are supported for Dutch Rabobank accounts: Europayments - payments in the EUR currency to a beneficiary in a SEPA country. Urgent Domestic Europayments - urgent payments in the EUR currency between Dutch bank accounts. Urgent Europayments - urgent payments in the EUR currency to a beneficiary in a SEPA country. Worldpayments - payments to a beneficiary in a non-sepa country in any currency (also EUR). The following payments are supported for foreign Rabobank accounts and non-rabobank accounts: Multibank payments - payments from accounts held with other banks Network banking payments - payments from Rabobank bank accounts held in Belgium, the United Kingdom and in Germany 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 April 2018 Version 1.6 5

6 As of Q both Multibank payments and Network Banking payments will be supported and processed by Rabobank. Important information about Urgent Domestic Europayments and Urgent Europayments: 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 Europayments. Both Worldpayments and Urgent Europayments 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 Europayments it is mandatory to indicate that these (Euro)payments must be treated as urgent payments. Between Urgent Domestic Europayments and Urgent Europayments 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 XSD defenition. Between the opening tag and closing tag the information for this tag is contained. Rabobank Format description Generic Payment File April 2018 Version 1.6 6

7 A XML-pain file/message has the following structure:. Rabobank Format description Generic Payment File April 2018 Version 1.6 7

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 PaymentTypeInformation (2.6) Payment level PaymentTypeInformation (2.31) ServiceLevel Code ServiceLevel Code How payments will be processed Empty or SEPA Empty or SEPA Only to be used for Europayments. Not allowed for Worldpayments, Mu;tibank payments, Urgent Europayments, and Urgent Domestic Europayments, 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 Europayments and Urgent Europayments. Any value No ServiceLevel code allowed on Payment level Rabobank Format description Generic Payment File April 2018 Version 1.6 8

9 3 Segment description This chapter describes all tags/fields which are relevant to Europayments, Urgent Europayments, Urgent Domestic Europayments, 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 XSD. 3.1 Group Header Name Document <Document> Top [1..1] XML-tag level Presence Type Length Description <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 time Creationdate and time of the file. 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.. 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] Alphanumeric This tag/field is ignored for Worldpayments, Multibank payments, Urgent Europayments and Urgent Domestic Europayments. For Europayments please refer to appendix A. Rabobank Format description Generic Payment File April 2018 Version 1.6 9

10 3.2 Payment Information Segment Name 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, Multibank payments, Urgent Europayments and Urgent Domestic Europayments 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 Europayments, only the total amount will be shown in one debit transaction in the account information. When the value false is provided all Europayments will be presented individually in the account information. When this tag is not provided Rabobank will use the value true when processing the Europayments. For Worldpayments, Multibank payments, Urgent Europayments and Urgent Domestic Europayments 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 Europayments the value NORM is commonly used (however, as mentioned, any value specified will be ignored). Rabobank Format description Generic Payment File April 2018 Version

11 ServiceLevel 2.8 <SvcLvl> 2 [0..1] For Europayments 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 Europayments, Urgent Domestic Europayments and Multibank payments it is mandatory to provide this tag for processing these 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. - SEPA for Europayments - URGP for Urgent Domestic Europayments - SDVA, NURG and URGP 1 for Worldpayments, Urgent Domestic Payments and Multibank Payments For Worldpayments, Urgent Europayments, Urgent Domestic Payments and Multibank payments it is mandatory to provide one of the mentioned values. When the Servicelevel/Code is omitted all payments will be processed as Europayments 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 Europayments. For Worldpayments, Urgent Europayments, Urgent Domestic Europayments and Multibank payments this field/tag will be ignored. Code 2.12 <Cd> 3 [1..1] of Alphanumeric Max. 35 For Europayments 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. 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 April 2018 Version

12 Other values for this tag will be ignored. Proprietary 2.13 <Prtry> 3 [1..1] Alphanumeric Max. 35 This information is not used for processing CategoryPurpose 2.14 <CtgyPurp> 2 [0..1] For Worldpayments, Urgent Europayments and Urgent Domestic Europayments this field/tag and underlying fields/tags will be ignored. Code 2.15 <Cd> 3 [1..1] of 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 Multibank payments: The code INTC will be used by Rabobank for Multibank payments, other codes will be forwarded to the Servicing bank (where the payment will be processed). For Europayments: 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] Alphanumeric Max. 35 With Europayments and Multibank payments the information provided in this field will be forwarded to the receiving bank, for Multibank payments 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 Europayments and Urgent Domestic Europayments. 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 14 days in the past this date is changed by Rabobank to the first possible processing date; when a date is provided which is Rabobank Format description Generic Payment File April 2018 Version

13 Debtor 2.19 <Dbtr> 1 [1..1] older than 14 days the batch will be rejected. It is possible to provide a date for future processing until 365 calendar days. Name <Nm> 2 [1..1] Alphanumeric Max. 70 The name of the initiating party is mandatory. For Urgent Domestic Europayments the name provided in this tag/field will be used; For Europayments, Worldpayments, Multibank payments and Urgent Domestic Europayments the name provided will be overwritten with the statutory name as registered for the account by Rabobank. PostalAddress <PstlAdr> 2 [0..1] Alphanumeric For Europayments and Urgent Domestic Europayments the fields Country and AddressLine are available, these are not mandatory. For Worldpayments, Urgent Europayments and Multibank payments the fields StreetName, PostCode, TownName en Country are available. StreetName <StrtNm> 3 [0..1] Alphanumeric This field is only used for Worldpayments, Urgent Europayments and Multibank payments PostalCode <PstCd> 3 [0..1] This field is only used for Worldpayments, Urgent Europayments and Multibank payments TownName <TwnNm> 3 [0..1] This field is only used for Worldpayments, Urgent Europayments and Multibank payments Country <Ctry> 3 [0..1] Alphanumeric 2 Country where the initiating party resides, used for Europayments, Urgent Domestic Europayments, Urgent Europayments, Worldpayments and Multibank payments. AddressLine <AdrLine> 3 [0..2] 1 Alphanumeric Max. 70 Address of the initiating party, used for Europayments and Urgent Domestic Europayments: 1 e line: Street and housenumber 2 e line: Postal code and city. Voor Urgent Domestic Europayments only the first 35 positions from the 1 st address line will be used and the first 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 April 2018 Version

14 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] Alphanumeric This tag/field is ignored for Worldpayments, Urgent Europayments, Urgent Domestic Europayments and Multibank payments. For Europayments please refer to appendix A. DebtorAccount 2.20 <DbtrAcct> 1 [1..1] 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] Identification <Id> 4 [1..1] Alfanumeriek Max. 34 This field is only allowed for Multibank payments, and when specified may only contain a BBAN. It is not allowed for Multibank payments 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 Europayments, Urgent Europayments, Urgent Domestic Europayments and Multibank payments 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 be processed for Rabobank WRR 1 accounts. USD-account (example), payment currency JPY: will not be 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 Rabobank Format description Generic Payment File April 2018 Version

15 DebtorAgent 2.21 <DbtrAgt> 1 [1..1] FinancialInstitutionIdentification <FinInstnId> 2 [1..1] processed for Rabobank (Nederland) 1 accounts, the payment will be rejected. BIC <BIC> 3 [0..1] of 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 Multibank payments 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] 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. UltimateDebtor 2.23 <UltmtDbtr> 1 [0..1] This field/tag and underlying fields/tags are ignored for Worldpayments, Urgent Europayments, Urgent Domestic Payments and Multibank payments. 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] Alphanumeric For Europayments please refer to appendix A. ChargeBearer 2.24 <ChrgBr> 1 [0..1] Alphanumeric 4 - For Europayments only the value SLEV is allowed. - For Urgent Domestic Payments, Urgent Europayments, Worldpayments and Multibank payments within the EER only the value SHAR is allowed. - For all other Worldpayments and Multibank payments the following values are allowed: 1 The 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 April 2018 Version

16 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. ChargeBearer may be present on this level or transaction level (2.51) but not on both levels. Rabobank Format description Generic Payment File April 2018 Version

17 3.3 Transaction Information Segment Name CTTransactionInformation 2.27 <CdtTrfTxInf> 1 [1..n] PaymentIdentification 2.28 <PmtId> 2 [1..1] This tag/field and underlying tags/fields are used for Europayments, and will be ignored for Worldpayments, Multibank payments, Urgent Urgent Europayments and Urgent Domestic Europayments. Important: Because of the fact that this tag/field is mandatory, according to the [1..1] presence (XSD) a value must be provided for Worldpayments, Multibank payments, Urgent Europayments and Urgent Domestic Europayments 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 Europayments. 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. ServiceLevel 2.33 <SvcLvl> 3 [0..1] Code 2.34 <Cd> 3 [0..1] Alphanumeric 4 For Europayments 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 Europayments, only the value SEPA is allowed. For Worldpayments, Urgent Europayments, Urgent Domestic Payments and Multibank payments 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. LocalInstrument 2.36 <LclInstrm> 3 [0..1] This field/tag and underlying fields/tags are only used for Rabobank Format description Generic Payment File April 2018 Version

18 Europayments. For Worldpayments, Multibank payments, Urgent Europayments and Urgent Domestic Europayments this field/tag will be ignored. Code 2.37 <Cd> 4 [1..1] Alphanumeric Max. 35 For Europayments 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/field can be presented on batch/pi level (2.12) or on payment level, not on both levels. Other values for this tag will be ignored. Proprietary 2.38 <Prtry> 4 [1..1] Alphanumeric Max. 35 This information is not used for processing This tag/field can be provided on batch/pi level (2.13) or on payment level, but not on both levels. CategoryPurpose 2.39 <CtgyPurp> 3 [0..1] For Worldpayments, Urgent Europayments and Urgent Domestic Europayments this field/tag and underlying fields/tags will be ignored. Code 2.40 <Cd> 4 [1..1] 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 Multibank payments: The code INTC will be used by Rabobank for Multibank payments, other codes will be forwarded to the Servicing bank (where the payment will be processed). 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. For Europayments: Only the code SALA for salary payments is being used by Rabobank to present and process such payments Rabobank Format description Generic Payment File April 2018 Version

19 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] Alphanumeric Max. 35 With Europayments and Multibank payments the information provided in this field will be forwarded to the receiving bank, for Multibank payments 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 Europayments and Urgent Domestic Europayments. Amount 2.42 <Amt> 2 [1..1] InstructedAmount 2.43 <InstdAmt> 3 [1..1] Amount Max. 18 This tag/field can be presented on batch/pi level (2.16) or on payment level, not on both levels. 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. The currency for the amount must be provided within the tag: <InstdAmt Ccy= XXX > where XXX must be a valid ISO currency code (f.e. EUR, USD, GBP, JPY, etc.). ChargeBearer 2.51 <ChrgBr> 2 [0..1] Alphanumeric 4 - For Europayments only the value SLEV is allowed. - For Urgent Domestic Payments, Urgent Europayments, Worldpayments and Multibank payments within the EER only the value SHAR is allowed. - For all other Worldpayments and Multibank payments the following values are allowed: Rabobank Format description Generic Payment File April 2018 Version

20 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. 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, Multibank payments, Urgent Europayments and Urgent Domestic Europayments. 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 <IntrmyAgt1> 3 [0..1] FinancialInstitutionIdentification <FinInstId> 3 [1..1] This tag/field can only be used for Worldpayments and only for payments from WRR accounts 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 Multibank payments, Europayments and Urgent Domestic Europayments this tag/field is ignored. 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. ClearingSystemMemberIdentificatio n <ClrSysMmbld> 4 [0..1] ClearingSystemIdentification <ClrSysId> 5 [0..1] 1 Wholesale, Rural and Retail (WRR) refers to the Rabobank Current Account system for customers from (previously called) Rabobank International, please contact the Rabobank Corporate Support desk for more information about specific and/or alternative payment routing - and other information - regarding additional costs and possible additional requirements for non-straight Through Processing (STP) of payments. Rabobank Format description Generic Payment File April 2018 Version

21 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. The list of allowed bank codes can be found here: tab-5 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. Proprietary <Prtry> 6 [1..1] Alphanumeric Max 35 Via this tag/field the national bank code can be provided, this code will not be checked by Rabobank and is relayed. MemberIdentification <Mmbld> 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. CreditorAgent 2.77 <CdtrAgt> 2 [0..1] For Europayments and Urgent Domestic Europayments: Only the BIC may be provided. FinancialInstitutionIdentification <FinInstnId> 3 [1..1] For Worldpayments, Multibank payments and Urgent Europayments: Rabobank advises to provide the BIC. When the BIC is not provided, it is mandatory to provide the name and countrycode from the bank of the beneficiary. Optional additional information may be provided by specifying the ClearingSystemIdentification and MemberId. Rabobank will then determine the BIC of the beneficiary bank via the provided IBAN or national bank code. When this BIC cannot be determined, the information provided will be used by Rabobank, should this information be incorrect the payment will be rejected. Additional charges may be applied when no BIC is provided. When 2.71 IntermediaryAgent information is provided the payment will be routed accordingly; when no informaton is provided via this tag/field, the payment will be routed via the CreditorAgent. BIC <BIC> 4 [0..1] Alphanumeric 8 of 11 SWIFT BIC code from the bank of the beneficiary. Usage of Rabobank Format description Generic Payment File April 2018 Version

22 this tag/field is optional. Only numbers and capital letters are allowed. For Europayments: 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. ClearingSystemMemberIdentificatio n ClearingSystemIdentification <ClrSysId> 5 [0..1] For Worldpayments, Multibank payments, Urgent Europayments 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 and country code 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. <ClrSysMmbld> 4 [0..1] This tag/field may only be used for Worldpayments and Urgent Europayments and must be provided for payments towards countries where providing this national bank code is mandatory. Code <Cd> 6 [1..1] 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. The list of allowed bank codes can be found here: tab-5 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. Rabobank Format description Generic Payment File April 2018 Version

23 Proprietary <Prtry> 6 [1..1] MemberIdentification <Mmbld> 5 [1..1] Name <Nm> 4 [0..1] Alphanumeric Max. 35 Name of the bank of the beneficiary. For Worldpayments, Multibank payments and Urgent Europayments 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 Europayments 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. Creditor 2.79 <Cdtr> 2 [1..1] 1 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. Name <Nm> 3 [1..1] Alphanumeric Max. 70 Name from the beneficiary, mandatory for all payment types. PostalAddress <PstlAdr> 3 [1..1] Alphanumeric For Europayments and Urgent Domestic Europayments the fields Country and AddressLine must be provided. For Worldpayments, Multibank payments and Urgent Europayments the fields StreetName, PostCode, TownName and Country must be provided.. StreetName <StrtNm> 4 [0..1] Alphanumeric Max. 70 This tag/field is mandatory for Worldpayments, Multibank payments and Urgent Europayments 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 Europayments and Multibank payments TownName <TwnNm> 4 [0..1] Alphanumeric Max. 35 This tag/field is mandatory for Worldpayments, Urgent Europayments and Multibank payments 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 April 2018 Version

24 Country <Ctry> 4 [1..1] Alphanumeric 2 Country code of the country where the beneficiary resides. AddressLine <AdrLine> 4 [0..2] Alphanumeric Max. 70 Address information of the beneficiary, only used for Europayments and Urgent Domestic Europayments. For Europayments max. 2x70 positions: 1 st line: Street and house number 2 nd line: Postal code (zipcode) and city For Urgent Domestic Europayments: 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] Alphanumeric This tag/field is only used for Europayments. Please refer to appendix A. 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 Europayments 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] Only allowed for Woldpayments, Multibank payments and Urgent Europayments 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, Multibank payments, Urgent Europayments and Urgent Domestic Europayments Rabobank Format description Generic Payment File April 2018 Version

25 Name <Nm> 3 [1..1] Alphanumeric Max. 70 Name of the ultimate beneficiary. Country <Ctry> 4 [1..1] Country of the ultimate beneficiary. AddressLine <AdrLine> 4 [0..2] Max. 70 Address information of the ultimate beneficiary. Identification <Id> 3 [0..1] Alphanumeric 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 Europayments: Specific instructions for the Rabobank, for example to 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, Multibank payments, Urgent Europayments and Urgent Domestic Europayments Code 2.87 <Cd> 3 [1..1] Alphanumeric 4 RemittanceInformation 2.98 <RmtInf> 2 [0..1] For Europayments 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. Unstructured 2.99 <Ustrd> 3 [0..1] Alphanumeric Max. 140 For Worldpayments, Multibank payments, Urgent Europayments and Urgent Domestic Europayments only the Unstructured tag/field may contain a value; when the Structured tag/field contains a value, this value will be ignored. For Europayments all 140 positions will be read and processed. For Urgent Domestic Europayments only the first 96 positions will be read and processed. For Worldpayments, Multibank payments and Urgent Europayments only the first 98 positions will be read and processed. Please note!: For all payments/payment types there is a maximum of only one (1) Unstructured remittance line. Rabobank Format description Generic Payment File April 2018 Version

26 Structured <Strd> 3 [0..n] Structured remittance information is only allowed for Europayments, and only accepted and processed when paying towards a Dutch IBAN (beneficiary) and Currence (CUR) payment reference. 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 Only CUR is allowed. For Worldpayments, Multibank payments, Urgent Europayments and Urgent Domestic Europayments this tag/field is ignored. Reference <Ref> 5 [1..1] Alphanumeric Max. 35 Only a Currence payment reference is allowed. Rabobank Format description Generic Payment File April 2018 Version

27 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 (X) or ignored and not passed on (-). Name XML-tag level Presence Type Length Description OrganizationIdentification <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] Issuer <Issr> +3 [0..1] Alphanumeric Alphanumeric Rabobank Format description Generic Payment File April 2018 Version

28 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 (X) or ignored and not passed on (-). Name XML-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] Alphanumeric 4 The ExternalPersonIdentification1Code This code can be found on Tab 10: PersonIdentification Proprietary <Prtry> +4 [1..1] Alphanumeric 35 Issuer <Issr> +3 [0..1] Alphanumeric 35 Rabobank Format description Generic Payment File April 2018 Version

29 Appendix B National bankcode 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 41TUhereU41T for an overview of countries that use the IBAN as account number format. For non-sepa payments, providing a national bankcode can be essential. For some countries, providing a national bank code is mandatory, for others it s optional. In the latter case, providing a national bank code is preferred: the presence of this code may result in lower deducted charges as the bank of the beneficiary can be uniquely identified immediately. Payment information per country is available on the webpage (Dutch language only). Rabobank Format description Generic Payment File April 2018 Version

30 Changelog Titel : Format description Generic Payment File Version : 1.60 Date : On behalf of : Rabobank Internet Banking professional Rabobank Direct Connect Contact : Corporatesupport@rabobank.com Date Version Change Reason Initial Generic Payment File format description for RDC Description updated Description updated Minor changes, textual corrections and removal of redundant information Description updated Major changes to unambiguously describe Urgent Europayment s, Urgent Domestic Europayments and Worldpayments, removal of footnotes in favour of full textual descriptions Table updated/simplified chapter 3.1 Minor textual changes, usage of capital letters Cost option adjustment For Urgent Domestic (Euro)payments Rabobank does not allow DEBT or CRED, only SHAR is allowed Multibank initiation added to the GPF description Cost option SHAR 2.24 and 2.51 Support for Network banking payments as of Q Functionality added to the GPF format For Worldpayments and Urgent payments within the EER as of it is only allowed to use the cost option SHAR Charge Bearer 2.24 en 2.51 changed. Charge Bearer is allowed on batch or transaction level PaymentTypeInformation changed. The subtags of PaymentTypeInformation may be present on batch or transaction level unless described otherwise Appendix B changed Referred to payment information per Rabobank Format description Generic Payment File April 2018 Version

31 country on webpage and table removed Document changed - Clarification of payment types, paragraph Tags which are ignored must comply with XSD. Rabobank Format description Generic Payment File April 2018 Version