Access Online Payment Upload Formats. June 2012

Transcription

1 Access Online Payment Upload Formats June 2012

2 If you have questions and/or remarks regarding this document, please contact the following department: ABN AMRO Bank N.V. COO C&MB / E-Channels / Global Cash Channels Postbus EA Amsterdam PAC HQ [email protected] ABN AMRO Bank N.V All rights reserved. Apart from those exceptions stipulated in or by virtue of the 1912 Copyright Law, no part of this publication may be reproduced and/or made public through print, photocopy, microfilm, or in any other manner whatsoever, nor may it be stored in a data retrieval system without express written permission from ABN AMRO Bank N.V. Even though the information in this document has been meticulously compiled, we accept no liability for any errors or inaccuracies it may contain. We maintain the right to modify the (technical) data regarding the products discussed at any time without further notification. Should you use the information contained in this document for the benefit of third parties, you indemnify us against any claims by these third parties. 2

3 Contents 1. Introduction Target group Access Online Document Structure 8 2. Validation Introduction Validation rules Validation result 11 Pain XML formats SEPA region Pain formats Introduction Assumptions & Principles File Structure SEPA Credit Transfer (SCT) Introduction SEPA Credit Transfer SEPA Direct Debit (SDD) Introduction SEPA Direct Debit SEPA Validation rules 38 ClieOp03 The Netherlands ClieOp Introduction Assumptions & Principles Records File header record Batch header record 45

4 7.6 Fixed description record Customer record Transaction record Debtor name record Debtor address record Payment reference number record Description record Creditor name record Creditor address record Batch trailer record File trailer record Validation rules 49 BTL91 The Netherlands BTL Introduction Assumptions & Principles File Structure Header record Payment record part Payment record part Payment record part Payment record part Total record Trailer record Validation rules Payments Complete 59 CIRI Belgium CIRI Introduction Assumptions & Principles CIRI FBF Domestic Payment Orders Introduction Scope File format 64 4

5 10.4 Header record Data record Data record Trailer record Validation rules CIRI VME Foreign Payment Orders Introduction Scope File format Header record Data record 1, sub-division Data record 1, sub-division Data record 1, sub-division Data record 1, sub-division Data record 1, sub-division Data record 1, sub-division Data record 1, sub-division Data record 1, sub-division Data record 1, sub-division Data record 1, sub-division Data record 1, sub-division 11 through Trailer record Validation rules 79 DTAus/zv Germany DTAus Introduction Assumptions & Principles File Structure Error messages DTAus Payments Introduction Header record Data record C, Fixed Part Data record C, Variable Part Trailer record E 91 5

6 13.6 Validation rules DTAzv Foreign Payment Orders Introduction Scope File format Header record Data record T Trailer record Validation rules 100 CFONB France CONFB Introduction Assumptions & Principles File Structure CFONB Transfer Introduction Header record Transaction record Transaction record Total record Central Bank Reporting CFONB Direct debit Introduction Header record Transaction record Transaction record Total record CFONB Validation rules 113 Appendices Character Sets 116 6

7 20. ISO Codes ISO Country Code ISO Currency Code Economic activity code (CFONB) 119 7

8 1. Introduction This document describes the various payment file upload formats used by Access Online. 1.1 Target group This information is intended for the IT departments in companies that use electronic files or for their software suppliers. This document can serve as a reference when developing and maintaining automated funds flow processing between your company and the bank. 1.2 Access Online Access Online is ABN AMRO s Internet Banking platform, which has been developed specifically to optimise the management of your working capital. Via Access Online you have access to your bank accounts any time and any place. With Access Online, you can conduct Internet banking worldwide. You also have insight into all national and international payment streams within your company. 1.3 Document Structure This document describes the formats available in Access Online. The agreement between the client and ABN AMRO determines whether or not these formats are visible and can be used. The general standard is described for each format, along with information that specifically applies to Access Online Version History Version Date Author Role Remark 1.0 June 2012 COO Global Cash Channels Channel manager Initial version Layout used Examples showing file contents are display using the Courier font Icon used Remark Paragraphs with this icon contain extra information regarding the subject in question. 8

9 1.3.4 Table Legend Column Value Description Explanation Field Fld Code/ Number Contains a (sequence) number of a specific format-dependent code that supports mutual references Status M Mandatory Item must be used O Optional Item may be used C Conditional Item may and/or must be used depending on the presence or value of other items Type N Numeric Figures, 0-9 A Amount This type is used for amounts. There must be at least one position before the decimal. The decimal indicator. is mandatory and counts as part of the total length. A Alphabetic Letters, A-Z (capital letters) X Alphanumeric Combination of figures, capital letters and characters from a specific set. See Appendix 19 Character Sets. number Fixed number Item contains exactly x positions (underscored) Length Number Variable number Item may contain a maximum of x positions. If this applies to a mandatory item, at least 1 number must appear. Number Count indicating how frequently an item, record, tag or field may occur Repeat 0 None Error No Validation rule is defined for the item or The validation rule for this item is positive; OK Validation result L99 Logical Error Logical validation rule for the item is negative; this must be corrected in Access Online. VR T99 Total Error Technical validation rule for the item is negative; file is completely or partially rejected. 9

10 2. Validation 2.1 Introduction Files that are read into Access Online must comply with specific format specifications. Validation involves checking whether these files actually comply with these format specifications. Validation rules are drawn up in order to check this. These rules must ensure that the information is correct and are only subject to one interpretation. This makes it possible for the bank to process the files automatically; no manual processing is required. 2.2 Validation rules During the validation process, the validation rules that have been stipulated for a particular format are tested. These rules can apply to various levels and components, for example: File(s): structure for this format type; Batch(es); Record(s): use of the correct types and sequence; (Sub)-field(s), contents and mutual (conditional) dependencies; Control counts in total record(s) and/or trailer record; Symbol(s)/characters and the use of the correct data types; Technical validation These rules (syntax) involve (among other things) the file structure, the record sequence and the field data types Logical validation During logical validation (semantics) checks are performed to ensure that the file complies with the following rules: A field contains the right value; A conditional field is filled correctly. In this phase, orders are also automatically enriched and/or corrected. A notification regarding this is created. For example in the event of: empty code fields that are assigned the standard value; replacement of characters that are not part of the character set. After being loaded, the status of the file changes to Checked. Then the user can zoom in on individual orders in the file, view any messages and make whatever changes may be necessary to correct the order. Depending on the format type, information for optimising the order processing process is also reported during the validation process. Feedback regarding logical errors and other messages appear in the language the user has stipulated as his/her preferred language. 10

11 2.3 Validation result The extent to which the validation rules have been satisfied determines the ultimate result of the validation process. If errors are detected, the following situations can arise depending on the nature of the errors: The file is partially approved The content of the file is displayed in Access Online, indicating the orders that must be manually corrected before processing can continue. The file is rejected A message is displayed specifying the errors found, indicating the specific location and/or line number of the error(s) in the file, if possible. Generally, the recommendation is to correct the original file and to submit it again. Examples of a generic message: An error has been encountered while processing your file. A mandatory record <Record name> or Field <Field name> is missing. Please make the necessary change(s) and upload the file again. We have registered this error under ID: <%fileid%>. An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%record Identification%> is "0", but the value received in the file is <%actualvalue%>. Please make the necessary change (s) and upload the file again. We have registered this error under ID: <%fileid%>. Remark These technical messages are always in English. An error ID in the message consists of an 8-digit number. 11

12 Pain XML formats SEPA region 12

13 3. Pain formats 3.1 Introduction The Pain format is the European file format for customer delivery of SEPA payments to the bank, the socalled PAyment INitiation domain, within the Single Euro Payments Area consisting of 32 countries in Europe (at the end of 2011). The Pain format was developed by ISO (International Standards Organization). The EPC, the European Payment Council, a partnership agreement among the European banks, is responsible for the development and maintenance of the SEPA standards External Documentation & Information Author Title / Source Date EPC Customer Credit Transfer Initiation (pain ) November 2010 ( NVB XML message for SEPA Credit Transfer Initiation February 2011 ( EPC Customer Direct Debit Initiation (pain ) November 2010 ( NVB XML message for SEPA Direct Debit Initiation February 2011 ( ISO Catalogue or ISO messages ( ISO External Purpose Code List ( 1_v2.xls) Remark The documentation mentioned only relates to the ABN AMRO Access Online application in which these formats are supported. 3.2 Assumptions & Principles Standard upload profile In Access Online, the upload profile for the SEPA Transfers (Credit Transfer) and SEPA Collections (Direct Debit) XML format can further specify how the upload file must be processed. The description of the Pain format in this chapter is based on an upload profile with standard settings. If non-standard settings are used in the upload profile, this can affect the validation/control and the messages described in this chapter Number of Orders For delivery and processing via Access Online, the maximum number of orders per file is set at 10,

14 3.2.3 Batch Orders The file submitted for loading contains one or more batches with SEPA payment orders. By default, Access Online handles the files submitted as batch orders. The only exception is SEPA Credit Transfers, for which the user can define that the batch file must be split into individual SEPA Credit transfers after the file has been read into Access Online. Batch Transfers The Account number of the commissioning/paying party the Debtor Account message element at the batch level - is used as the debit account number for all orders in the batch. A payment can be a normal payment or a salary payment. This is indicated in the Category Purpose message element at the batch level. Batch Direct debits The Account number of the commissioning/collecting party the Creditor Account message element at the batch level - is used as the credit account number for all orders in the batch. A Direct debit batch may only consist of direct debit mandates of the same type, indicated in the Sequence Type message element at the batch level. The possibilities are One-off, Recurrent First, Recurrent and Recurrent Last. 3.3 File Structure An XML - pain file with SEPA payments has the following root structure: <?xml version= 1.0 encoding= UTF-8?> <Document xmlns= urn:iso:std:iso:20022:tech:xsd:pain xmlns:xsi= > <CstmrCdtTrfInitn> File contents, see Chapter 4 SEPA Credit Transfer (SCT) </CstmrCdtTrfInitn> </Document> An XML - pain file with SEPA direct debits has the following root structure: <?xml version= 1.0 encoding= UTF-8?> <Document xmlns= urn:iso:std:iso:20022:tech:xsd:pain xmlns:xsi= > <CstmrDrctDbtInitn> File contents, see Chapter 5 SEPA Direct Debit (SDD) </CstmrDrctDbtInitn> </Document> Technical File The XML file must comply with the XSD definitions, published by ISO for the Pain format in question (see Catalogue of ISO messages). 14

15 3.3.2 Character set See chapter 19 Character Sets for an overview of the characters that can be used in the Pain file format Logical File Level Block Repeat File Group Header 1 Customer Payment Information 1-n Contra account Transaction Information 1 10,000 The XML file has the following structure: The file consists of 1 Group Header block. The Group Header block contains information regarding the file, such as totals, file identifier, etc. The Group Header block contains 1-n Payment Information blocks. A Payment Information block contains information related to the customer such as payment order type and Customer Account Number. For payments, the debtor is the principle; for direct debits, the creditor is the principle. A Payment Information block (batch) contains a maximum of 1-10,000 Transaction Information blocks with information regarding the contra accounts in the batch. For payments, this is the creditor, for direct debits, this is debtor. An XML file contains a maximum of 10,000 Transaction Information blocks (transactions). 15

16 4. SEPA Credit Transfer (SCT) 4.1 Introduction This chapter describes the pain format as used for offering batches with SEPA payment orders. 4.2 SEPA Credit Transfer The following table defines the ISO message elements and their use in a pain Use of colour in the Index column Message element is a mandatory part of the SEPA messages format Message element is defined in ISO 20022, but is not used within the SEPA messages format. The presence of such a message element is ignored provided this complies with ISO Index (ISO) Mult. (ISO) Message element SEPA (EPC) Condition / Remark VR [1..1] + Message Root 1.0 [1..1] + Group Header File data 1.1 [1..1] ++ Message Identification Is used to detect duplicate files; it must be unique within a period of the last 90 days. 1.2 [1..1] ++ Creation Date Time Moment at which the file was created. Must contain a valid date time designator. The date format is yyyymm-dd. The time format is hh:mm:ss. 1.3 [0..2] ++ Authorisation Is ignored 1.6 [1..1] ++ Number Of Transactions Total number of transactions for the batches in the file E [0..1] ++ Control Sum Total amount for the batches in the file E [1..1] ++ Initiating Party All message sub-elements are ignored in Access Online. The name is overwritten with the data specified in the bank s administration. 1.8 [0..1] +++ Name 1.8 [0..1] +++ Postal Address 1.8 [0..1] +++ Identification 1.8 [1..1] {Or ++++ Organisation Identification 1.8 [0..1] BIC or BEI [0..1] {Or 1.8 [0..n] Other [0..1] Or} 1.8 [1..1] Or} ++++ Private Identification 1.8 [0..1] Date and Place of Birth [0..1] {Or 1.8 [0..n] Other [0..1] Or} 1.8 [0..1] +++ Country of Residence 1.8 [0..1] +++ Contact Details 1.9 [0..1] ++ Forwarding Agent 16

17 Index (ISO) Mult. (ISO) Message element SEPA (EPC) 2.0 [1..n] + Payment Information 1-n batches in the file 2.1 [1..1] ++ Payment Information Identification Condition / Remark VR Contains the reference for the batch that is taken over on the customer s statement. Batch compression is standard unless stipulated otherwise in the output contract. 2.2 [1..1] ++ Payment Method Must contain the value TRF E [0..1] ++ Batch Booking 2.4 [0..1] ++ Number of Transactions 2.5 [0..1] ++ Control Sum 2.6 [0..1] ++ Payment Type Information Not used; is taken over from the output contract with true as the standard value. Total number of transactions in the batch; If this appears, it is ignored. Total batch amount; If this appears, it is ignored. 2.7 [0..1] +++ Instruction Priority If this appears, it is ignored. 2.8 [0..1] +++ Service Level 2.9 [1..1] {Or ++++ Code 2.10 [1..1] Or} ++++ Proprietary (AT-40 Scheme Identification Code) Must contain the value SEPA 2.11 [0..1] +++ Local Instrument If this appears, it is ignored [1..1] {Or ++++ Code 2.13 [1..1] Or} ++++ Proprietary 2.14 [0..1] +++ Category Purpose 2.15 [1..1] {Or ++++ Code (AT-45 Category purpose of the Credit Transfer) Indicates whether the batch contains salary payments. If this indicator does not appear, it is assumed that the file involves ordinary payments. If present, only the value SALA is permitted as a designation of salary payments [1..1] Or} ++++ Proprietary If this appears, it is ignored [1..1] ++ Requested Execution Date 2.18 [0..1] ++ Pooling Adjustment Date 2.19 [1..1] ++ Debtor 2.19 [0..1] +++ Name [1..1] Must be a target date. The date may not be more than 364 days in the future. A date in the past or an invalid target date is changed to reflect the first possible processing date. A nonexistent date is rejected. All message sub-elements are ignored in Access Online and are overwritten with the account holder data specified in the bank s administration. (AT-02 Originator s name) A maximum of 70 positions 2.19 [0..1] +++ Postal Address (AT-03 Originator s address) 2.19 [0..1] ++++ Address Type E061 E075 E151 E157 E071 17

18 Index (ISO) Mult. (ISO) Message element 2.19 [0..1] ++++ Department 2.19 [0..1] ++++ Sub-department 2.19 [0..1] ++++ Street name 2.19 [0..1] ++++ Building Number 2.19 [0..1] ++++ Post Code 2.19 [0..1] ++++ Town Name 2.19 [0..1] ++++ Country Sub-division 2.19 [0..1] ++++ Country 2.19 [0..7] ++++ Address Line [0..2] SEPA (EPC) Condition / Remark VR If filled, contains an Alpha-2 ISO 3166 country code in the SEPA region. A maximum of 2 lines with a maximum of 70 positions is supported [0..1] +++ Identification (AT-10 Originator Identification Code) 2.19 [1..1] {Or ++++ Organisation Identification If filled, Private ID may not appear [0..1] BIC or BEI [0..1] {Or If filled, Other may not occur [0..n] Other [0..1] Or} If filled, BIC or BEI may not occur [1..1] Identification 2.19 [0..1] Scheme name 2.19 [1..1] {Or Code A value other than BIC or BEI that identifies the Originator as an organisation [1..1] Or} Proprietary Description of the Other identification 2.19 [0..1] Issuer Description of the body that issues the Other identification [1..1] Or} ++++ Private Identification If filled, Organisation ID may not occur. E [0..1] Date and Place of Birth [0..1] {Or If filled, Other may not occur [1..1] Birth Date 2.19 [0..1] Province of Birth 2.19 [1..1] City of Birth 2.19 [1..1] Country of Birth 2.19 [0..n] Other [0..1] Or} 2.19 [1..1] Identification 2.19 [0..1] Scheme name 2.19 [1..1] {Or Code If filled, Date and Place of Birth may not occur. Identifier other than Date and Place of Birth that identifies the Originator as a private person [1..1] Or} Proprietary Description of the Other identification 2.19 [0..1] Issuer 2.19 [0..1] +++ Country of Residence 2.19 [0..1] +++ Contact Details Description of the body that issues the Other identification [1..1] ++ Debtor Account (AT-01 Originator s Account Number) 2.20 [1..1] +++ Identification Only IBAN is supported [1..1] {Or ++++ IBAN Must contain a valid IBAN E [1..1] Or} ++++ Other E084 18

19 Index (ISO) Mult. (ISO) Message element 2.20 [0..1] +++ Type 2.20 [0..1] +++ Currency 2.20 [0..1] +++ Name 2.21 [1..1] ++ Debtor Agent 2.21 [1..1] +++ Financial Institution Identification 2.21 [0..1] ++++ BIC 2.22 [0..1] ++ Debtor Agent Account 2.23 [0..1] ++ Ultimate Debtor 2.23 [0..1] +++ Name 2.23 [0..1] +++ Postal Address 2.23 [0..1] +++ Identification 2.23 [1..1] {Or ++++ Organisation Identification SEPA (EPC) Condition / Remark VR Must contain a valid currency code, if present. Only EUR is permitted. (AT-06 BIC code of the Originator Bank) Only BIC may occur. Identifies the debtor s bank and must contain a valid Swift code If filled, Ultimate Debtor may not occur at the post level. (AT-08 Name of the Originator Reference Party) A maximum of 70 positions (AT-09 Identification code of the Originator Reference Party) If filled, Private ID may not occur [0..1] BIC or BEI [0..1] {Or If filled, Other may not occur [0..n] Other [0..1] Or} If filled, BIC or BEI may not occur [1..1] Identification 2.23 [0..1] Scheme name 2.23 [1..1] {Or Code Value other than BIC or BEI that identifies the Originator Reference Party as an organisation [1..1] Or} Proprietary Description of the Other identification [0..1] Issuer Description of the body that issued the Other identification [1..1] Or} ++++ Private Identification If filled, Organisation ID may not occur. E [0..1] Date and Place of Birth [0..1] {Or If filled, Other may not occur [1..1] Birth Date 2.23 [0..1] Province of Birth 2.23 [1..1] City of Birth 2.23 [1..1] Country of Birth 2.23 [0.. n] Other [0..1] Or} 2.23 [1..1] Identification 2.23 [0..1] Scheme name 2.23 [1..1] {Or Code If filled, Date and Place of Birth may not occur. Value other than BIC or BEI that identifies the Originator Reference Party as a private person [1..1] Or} Proprietary Description of the Other identification 2.23 [0..1] Issuer Description of the body that issued the E077 E068 E155 E084 19

20 Index (ISO) Mult. (ISO) Message element 2.23 [0..1] +++ Country of Residence 2.23 [0..1] +++ Contact Details SEPA (EPC) Condition / Remark VR Other identification [0..1] ++ Charge Bearer If filled, must contain the value SLEV E [0..1] ++ Charges Account 2.26 [0..1] ++ Charges Account Agent 2.27 [1..n] ++ Credit Transfer Transaction Information 2.28 [1..1] +++ Payment Identification 2.29 [0..1] ++++ Instruction Identification Is ignored [1..1] ++++ End-to-end Identification 2.31 [0..1] +++ Payment Type Information 2.32 [0..1] ++++ Instruction Priority 2.33 [0..1] ++++ Service Level 2.34 [1..1] {Or Code 2.35 [1..1] Or} Proprietary 2.36 [0..1] ++++ Local Instrument 2.37 [1..1] {Or Code 2.38 [1..1] Or} Proprietary 2.39 [0..1] ++++ Category Purpose 2.40 [1..1] {Or Code 1-10,000 transfers in a batch (AT-41 Originator s Reference to the Credit Transfer) The customer reference is passed on unchanged by all the parties involved in the transaction. (AT-40 Identification code of the Scheme) Must be filled with SEPA (AT-45 Category purpose of the Credit Transfer) If this appears, the entry must be identical to Category Purpose at the batch level If this appears, only the value SALA is permitted to designate a salary payment [1..1] Or} Proprietary Is ignored if it appears 2.42 [1..1] +++ Amount 2.43 [1..1] {Or ++++ Instructed Amount [1..1] 2.44 [1..1] Or} ++++ Equivalent Amount 2.47 [0..1] +++ Exchange Rate Information (AT-04 Amount of the Credit Transfer in Euros). Minimum amount is 0.01 and maximum amount is The maximum number of decimal positions is 2. E.g is Euro. If no decimal point is used, it is assumed that the amount is in whole Euros. E.g. 10 is Euro. E061 E075 E157 E151 E087 E074 E158 20

21 Index (ISO) Mult. (ISO) Message element SEPA (EPC) Condition / Remark VR 2.51 [0..1] +++ Charge Bearer If filled, the value must be SLEV 2.52 [0..1] +++ Cheque Instruction 2.70 [0..1] +++ Ultimate Debtor 2.70 [0..1] ++++ Name 2.70 [0..1] +++ Postal Address 2.70 [0..1] ++++ Identification 2.70 [1..1] {Or Organisation Identification If filled, Originator Reference Party may not occur at the batch level. (AT-08 Name of the Originator Reference Party) A maximum of 70 positions (AT-09 Identification code for the Originator Reference Party) If filled, Private ID may not occur [0..1] BIC or BEI [0..1] {Or If filled, Other may not occur [0..n] Other [0..1] Or} If filled, BIC or BEI may not occur [1..1] Identification 2.70 [0..1] Scheme name 2.70 [1..1] {Or Code Value other than BIC or BEI that identifies the Originator Reference Party as an organisation [1..1] Or} Proprietary Description of the Other identification 2.70 [0..1] Issuer Description of the body that issued the Other identifier [1..1] Or} Private Identification If filled, Organisation ID may not occur. E [0..1] Date and Place of Birth 2.70 [1..1] Birth Date 2.70 [0..1] Province of Birth 2.70 [1..1] City of Birth 2.70 [1..1] Country of Birth 2.70 [0..n] Other [0..1] Or} 2.70 [1..1] Identification 2.70 [0..1] Scheme name 2.70 [1..1] {Or Code [0..1] {Or If filled, Other may not occur. If filled, Date and Place of Birth may not occur. Value other than Date and Place of Birth that identifies the Originator Reference Party as a private person [1..1] Or} Proprietary Description of the Other identification 2.70 [0..1] Issuer 2.70 [0..1] ++++ Country of Residence 2.70 [0..1] ++++ Contact Details 2.71 [0..1] +++ Intermediary Agent [0..1] +++ Intermediary Agent 1 Account 2.73 [0..1] +++ Intermediary Agent [0..1] +++ Intermediary Agent 2 Description of the body that issued the Other identifier. E155 E084 21

22 Index (ISO) Mult. (ISO) Message element Account 2.75 [0..1] +++ Intermediary Agent [0..1] +++ Intermediary Agent 3 Account SEPA (EPC) Condition / Remark VR 2.77 [0..1] +++ Creditor Agent (AT-23 BIC of the Beneficiary Bank) 2.77 [1..1] ++++ Financial Institution Identification 2.77 [0..1] BIC 2.78 [0..1] +++ Creditor Agent Account 2.79 [0..1] +++ Creditor [1..1] 2.79 [0..1] ++++ Name [1..1] The BIC of the creditor s bank. Must contain a valid value. (AT-21 Beneficiary s name) A maximum of 70 positions 2.79 [0..1] ++++ Postal Address (AT-22 Beneficiary s address) 2.79 [0..1] ++++ Address Type 2.79 [0..1] Department 2.79 [0..1] Sub-department 2.79 [0..1] Street name 2.79 [0..1] Building Number 2.79 [0..1] Post Code 2.79 [0..1] Town Name 2.79 [0..1] Country Subdivision 2.79 [0..1] Country 2.79 [0..7] Address Line [0..2] If present, must contain a 2-position ISO country code Only 2 lines are supported. If present, 2.79 Country is mandatory [0..1] ++++ Identification (AT-24 Beneficiary Identification Code) 2.79 [1..1] {Or Organisation Identification If filled, Private ID may not occur [0..1] BIC or BEI [0..1] {Or If filled, Other may not occur [0..n] Other [0..1] Or} If filled, BIC or BEI may not occur [1..1] Identification 2.79 [0..1] Scheme name 2.79 [1..1] {Or Code Value other than BIC or BEI that identifies the Beneficiary as an organisation [1..1] Or} Proprietary Description of the Other identification 2.79 [0..1] Issuer Description of the body that issued the Other identification [0..1] Or} Private Identification If filled, Organisation ID may not occur. E [0..1] Date and Place of Birth 2.79 [1..1] Birth Date 2.79 [0..1] Province of Birth 2.79 [1..1] City of Birth 2.79 [1..1] Country of Birth [0..1] {Or If filled, Other may not occur. E065 E069 E084 22

23 Index (ISO) Mult. (ISO) Message element SEPA (EPC) 2.79 [0..n] Other [0..1] Or} 2.79 [1..1] Identification 2.79 [0..1] Scheme name 2.79 [1..1] {Or Code Condition / Remark VR If filled, Date and Place of Birth may not occur. Value other than Date and Place of Birth that identifies the Beneficiary as a private person [1..1] Or} Proprietary Description of the Other identification 2.79 [0..1] Issuer 2.79 [0..1] +++ Country of Residence 2.79 [0..1] +++ Contact Details Description of the body that issued the Other identification [0..1] +++ Creditor Account [1..1] (AT-20 Beneficiary s Account number) 2.80 [1..1] ++++ Identification Only IBAN is supported [1..1] {Or IBAN Must contain a valid IBAN E [1..1] Or} Other 2.81 [0..1] +++ Ultimate Creditor 2.81 [0..1] ++++ Name 2.81 [0..1] ++++ Postal Address 2.81 [0..1] ++++ Identification 2.81 [0..1] {Or Organisation Identification (AT-28 Name of the Beneficiary Reference Party) A maximum of 70 positions (AT-29 Identification Code of the Beneficiary Reference Party) If filled, Private ID may not occur [0..1] BIC or BEI [0..1] {Or If filled, Other may not occur [0..n] Other [0..1] Or} If filled, BIC or BEI may not occur [1..1] Identification 2.81 [0..1] Scheme name 2.81 [1..1] {Or Code Value other than BIC or BEI that identifies the Beneficiary Reference Party as an organisation [1..1] Or} Proprietary Description of the Other identification 2.81 [0..1] Issuer Description of the body that issued the Other identification [0..1] Or} Private Identification If filled, Organisation ID may not occur. E [0..1] Date and Place of Birth 2.81 [1..1] Birth Date 2.81 [0..1] Province of Birth 2.81 [1..1] City of Birth 2.81 [1..1] Country of Birth 2.81 [0..n] Other [0..1] Or} 2.81 [1..1] Identification [0..1] {Or If filled, Other may not occur. Value other than Date and Place of Birth that identifies the Beneficiary Reference Party as a private person. E084 23

24 Index (ISO) Mult. (ISO) Message element 2.81 [0..1] Scheme name 2.81 [1..1] {Or Code SEPA (EPC) Condition / Remark VR 2.81 [1..1] Or} Proprietary Description of the Other identification [0..1] Issuer 2.81 [0..1] ++++ Country of Residence 2.81 [0..1] ++++ Contact Details 2.82 [0..1] 2.85 [0..1] +++ Instruction for Creditor Agent +++ instruction for Debtor Agent Description of the body that issued the Other identification [0..1] +++ Purpose (AT-44 Purpose of the Credit Transfer) 2.87 [1..1] {Or ++++ Code [1..1] 2.88 [1..1] Or} ++++ Proprietary 2.89 [0..10] +++ Regulatory Reporting 2.90 [0..1] +++ Tax 2.91 [0..10] +++ Related Remittance Information 2.98 [0..1] +++ Remittance Information 2.99 [0..n] ++++ Unstructured [0..1] {Or [0..n] ++++ Structured [0..1] Or} [0..n] [0..n] [0..1] Referred Document Information Referred Document Amount Creditor Reference Information [0..1] Type [1..1] Code or Proprietary Only codes from the ISO External Purpose Code List are permitted. (AT-05 Remittance Information) Only one or the two options Structured or Unstructured is permitted as a description A maximum of 140 positions is permitted for the description A maximum of 140 positions is permitted for the description, including tags If used, both Type and Reference must appear [1..1] {Or Code [1..1] Must be filled with SCOR [1..1] Or} Proprietary [0..1] Issuer Possible values if filled: ISO if ISO RF Creditor Reference (ISO 11649) is used CUR if Payment reference number is used (only in the Netherlands) BBA when Structured Announcement is used (only Belgium) E156 E159 E067 E091 E153 24

25 Index (ISO) Mult. (ISO) Message element [0..1] Reference [0..1] Invoicer [0..1] Invoicee [0..3] Additional Remittance Information SEPA (EPC) Condition / Remark VR Other when Reference is used in other cases This entry depends on the Issuer s E154 entry for

26 5. SEPA Direct Debit (SDD) 5.1 Introduction This chapter describes the pain format as used for offering batches with SEPA direct debit mandate. 5.2 SEPA Direct Debit The following table defines the ISO message elements and their use in a pain Use of colour in the index column Message element is a mandatory part of the SEPA messages format. Message element is defined in ISO 20022, but is not used within the SEPA messages format. The presence of such a message element is ignored provided this complies with ISO Index (ISO) Mult. (ISO) Message element SEPA (EPC) Condition / Remark VR [1..1] + Message Root 1.0 [1..1] + Group Header File data 1.1 [1..1] ++ Message Identification Is used to detect duplicate files; it must be unique within a period of the last 90 days. 1.2 [1..1] ++ Creation Date Time Moment at which the file was created. Must contain a valid date time designator. The date format is yyyymm-dd. The time format is hh:mm:ss. 1.3 [0..2] ++ Authorisation 1.6 [1..1] ++ Number of Transactions Total number of transactions for the batches in the file E [0..1] ++ Control Sum Total number of the batches in the file E [1..1] ++ Initiating Party All message sub-elements are ignored in Access Online. The name is overwritten with the data stored in the bank s administration. 1.8 [0..1] +++ Name 1.8 [0..1] +++ Postal Address 1.8 [0..1] +++ Identification ++++ Organisation 1.8 [0..1] IDentification [0..1] {Or 1.8 [0..n] ++++ Private Identification [0..1] Or} 1.8 [0..1] +++ Country of Residence 1.8 [0..1] +++ Contact Details 1.9 [0..1] ++ Forwarding Agent 2.0 [1..n] + Payment Information 1-n batches in the file Contains the reference for the batch ++ Payment Information 2.1 [1..1] that is taken over on the customer s Identification statement. 2.2 [1..1] ++ Payment Method Must contain the value DD E060 26

27 Index (ISO) Mult. (ISO) Message element SEPA (EPC) 2.3 [0..1] ++ Batch Booking Not used. 2.4 [0..1] ++ Number of Transactions 2.5 [0..1] ++ Control Sum 2.6 [0..1] ++ Payment Type Information [1..1] 2.7 [0..1] +++ Instruction Priority 2.8 [0..1] +++ Service Level [1..1] 2.9 [1..1] {Or ++++ Code 2.10 [1..1] Or} ++++ Proprietary 2.11 [0..1] +++ Local Instrument [1..1] 2.12 [1..1] {Or ++++ Code [1..1] 2.13 [1..1] Or} ++++ Proprietary 2.14 [0..1] +++ Sequence Type [1..1] 2.15 [0..1] +++ Category Purpose Condition / Remark VR Total number of transactions in the batch; the maximum number of transactions in the batch is stipulated in the SEPA contract. Total batch amount; the maximum batch amount is specified in the SEPA contract. (AT-20 Scheme Identification Code) Must contain the value SEPA (AT-20 Scheme Identification Code) Possible values CORE or B2B. Combining the two SDD schemes in 1 file is forbidden. For the moment, only CORE is supported. (AT-21 Transaction Type) Permitted values OOFF, FRST, RCUR, FNAL Must contain the value FRST if Amendment Indicator = true and Original Debtor Agent is SMNDA. (AT-59 Category purpose of the Direct debit) Use is not supported [1..1] {Or ++++ Code If present, the contents are ignored [1..1] Or} ++++ Proprietary If present, the contents are ignored [1..1] ++ Requested Collection Date 2.19 [1..1] ++ Creditor (AT-11 Due Date for the Collection) Must be an existing Target date. The date may not be more than 364 days in the future (scheduling). A date in the past is changed to reflect the first possible processing date. All message sub-elements are ignored in Access Online and are overwritten with the account holder data specified in the bank s administration [0..1] +++ Name [1..1] (AT-03 Creditor s name) 2.19 [0..1] +++ Postal Address (AT-05 Creditor s address) 2.19 [0..1] ++++ Address Type 2.19 [0..1] ++++ Department E061 E075 E062 E063 E076 E259 E071 27

28 Index (ISO) Mult. (ISO) Message element 2.19 [0..1] ++++ Sub-department 2.19 [0..1] ++++ Street name 2.19 [0..1] ++++ Building Number 2.19 [0..1] ++++ Post Code 2.19 [0..1] ++++ Town Name 2.19 [0..1] ++++ Country Subdivision 2.19 [0..1] ++++ Country 2.19 [0..7] ++++ Address Line [0..2] 2.19 [0..1] +++ Identification 2.19 [0..1] +++ Country of Residence 2.19 [0..1] +++ Contact Details SEPA (EPC) Condition / Remark VR If filled, contains an Alpha-2 ISO 3166 country code in the SEPA region. A maximum of 2 lines with a maximum of 70 positions is supported [1..1] ++ Creditor Account (AT-04 Creditor s account number) 2.20 [1..1] +++ Identification Only IBAN is supported [1..1] {Or ++++ IBAN Must contain a valid IBAN E [1..1] Or} ++++ Other 2.20 [0..1] +++ Type 2.20 [0..1] +++ Currency 2.20 [0..1] +++ Name Is ignored If this appears, it must contain a valid currency code. Only EUR is permitted [1..1] ++ Creditor Agent (AT-12 Creditor Bank BIC code) 2.21 [1..1] +++ Financial Institution Identification 2.21 [0..1] ++++ BIC 2.22 [0..1] ++Creditor Agent Account 2.23 [0..1] ++ Ultimate Creditor 2.23 [0..1] +++ Name 2.23 [0..1] +++ Postal Address 2.23 [0..1] +++ Identification 2.23 [1..1] {Or ++++ Organisation IDentification 2.23 [0..1] BIC or BEI [0..1] {Or 2.23 [0..n] Other [0..1] Or} 2.23 [1..1] Identification Creditor bank s BIC. Must contain a valid value. If filled, Ultimate Creditor may not occur at the post level. (AT-38 Creditor Reference Party s name) A maximum of 70 positions (AT-39 Creditor Reference Party s Identification Code) If filled, Private ID may not occur. Valid BIC or BEI (Business Entity Identification) that identifies the Creditor Reference Party as an organisation. If BIC or BEI is used, Other is not permitted. If Other is used, BIC or BEI may not occur. Value other than BIC or BEI that identifies the Creditor Reference Party E069 E077 E068 E251 E084 28

29 Index (ISO) Mult. (ISO) Message element 2.23 [0..1] Scheme name 2.23 [1..1] {Or Code SEPA (EPC) Condition / Remark VR as an organisation [1..1] Or} Proprietary Description of the Other identification [0..1] Issuer Description of the body that issued the Other identification [1..1] Or} ++++ Private Identification If filled, Organisation ID may not occur. E [0..1] Date and Place of Birth [0..1] {Or 2.23 [1..1] Birth Date 2.23 [0..1] Province of Birth 2.23 [1..1] City of Birth 2.23 [1..1] Country of Birth 2.23 [0..n] Other [0..1] Or} 2.23 [1..1] Identification 2.23 [0..1] Scheme name 2.23 [1..1] {Or Code 2.23 [1..1] Or} Proprietary 2.23 [0..1] Issuer 2.23 [0..1] +++ Country of Residence 2.23 [0..1] +++ Contact Details Valid birth date and city that identifies the Creditor Reference Party as a private person. If Other is used, Date and Place of Birth may not occur. If Date and Place of Birth is used, Other is not permitted. Value other than Date and Place of Birth that identifies the Creditor Reference Party as a private person. E.g. a passport number of a driving licence number. A description of the Other identification e.g., the text passport or driving licence.. Description of the body that issued the Other identification. E.g. the text municipality as the passport issuing 2.24 [0..1] ++ Charge Bearer If filled, the value must be SLEV. E [0..1] ++ Charges Account 2.26 [0..1] ++ Charges Account Agent 2.27 [0..1] ++ Creditor Scheme Identification 2.27 [0..1] +++ Name 2.27 [0..1] +++ Postal Address 2.27 [0..1] +++ Identification [1..1] 2.27 [0..1] {Or ++++ Organisation IDentification 2.27 [0..1] Or} ++++ Private Identification [1..1] body. If filled, Creditor Scheme Identification may not occur at the post level. Identifies an involved party as an organisation or a private person E252 29

30 Index (ISO) Mult. (ISO) Message element 2.27 [0..1] Date And Place of Birth 2.27 [0..n] Other [1..1] 2.27 [0..1] Identification [1..1] 2.27 [0..1] Scheme Name 2.27 [1..1] {Or Code SEPA (EPC) Condition / Remark VR (AT-02 Creditor Identifier) Identifies the creditor; this identifier must be unique within the SEPA region. Is assigned once by the bank when the SEPA direct debit contract is concluded. The Business Code in positions 5-7 is not part of the SEPA direct debit contract and may deviate from the standard value of ZZZ [1..1] Or} Proprietary Must contain the value SEPA 2.27 [0..1] Issuer 2.27 [0..1] +++ Country of Residence 2.27 [0..1] +++ Contact Details 2.28 [1..n] ++ Direct Debit Transaction Information 2.29 [1..1] +++ Payment Identification 2.30 [0..1] ++++ Instruction Identification Is ignored 2.31 [0..1] ++++ End-to-end Identification 2.32 [0..1] +++ Payment Type Information 2.44 [1..1] +++ Instructed Amount 1-10,000 direct debit items in a batch (AT-10 Creditor s Reference for the Direct Debit Collection) Can be filled with a reference to the collection post assigned by the creditor. The contents are passed on unchanged by all the parties involved in the. A maximum of 35 positions is permitted. (AT-06 Direct debit amount in Euros). The minimum amount is 0.01; the maximum amount is The maximum number of decimal positions is 2. E.g is Euro. If no decimal point is used, it is assumed that the amount is in whole Euros. E.g. 10 is Euro [0..1] +++ Charge Bearer If filled, the value must be SLEV. E [0..1] +++ Direct Debit Transaction [1..1] Mandatory E [0..1] ++++ Mandate Related Information 2.48 [0..1] Mandate Identification [1..1] [1..1] Mandatory (AT-01 Unique Mandate Reference) Feature of the authorisation; must be unique in connection with Creditor Scheme ID 2. The entry is not case sensitive; in other words 123AAa45678, 123aaA45678, E158 E074 E087 30

31 Index (ISO) Mult. (ISO) Message element SEPA (EPC) Condition / Remark VR 123aaa45678 and 123AAA45678 are all considered identical [0..1] Date Of Signature [1..1] (AT-25 Date the Mandate was Signed) 2.50 [0..1] Amendment Indicator 2.51 [0..1] 2.52 [0..1] 2.53 [0..1] Amendment Information Details Original Mandate Identification Original Creditor Scheme Identification 2.53 [0..1] Name 2.53 [0..1] Postal Address 2.53 [0..1] Identification [1..1] 2.53 [0..1] {Or Organisation IDentification 2.53 [0..1] Or} Private Identification [1..1] 2.53 [0..1] Date And Place of Birth 2.53 [0..n] Other [0..1] 2.53 [1..1] Identification 2.53 [0..1] Scheme Name 2.53 [1..1] {Or Code If true, this indicates that the mandate data have been modified. (AT-24 Reason for Amending the Mandate) If Amendment Indicator has the value true, at least one of the following message elements must appear: - Original Mandate ID. - Original Creditor Scheme ID. - Original Debtor Account - Original Debtor Agent (AT-19 Unique Mandate Reference as stipulated by the original Creditor who issued the Mandate). May only appear if the authorisation characteristic is modified. (AT-03 Name of the Original Creditor) Is not supported. Name of the creditor is specified in the SEPA contract and cannot be modified via file upload. Is ignored Identifies a party involved as an organisation or as a private person. (AT-18 Identifier of the Original Creditor who issued the Mandate) May only appear if the Creditor ID used for collection deviates from the Creditor ID for the authorisation [1..1] Or} Proprietary Must contain the value SEPA. E [0..1] Issuer 2.53 [0..1] Country of Residence 2.53 [0..1] Contact Details E081 E082 31

32 Index (ISO) Mult. (ISO) Message element 2.54 [0..1] Original Creditor Agent 2.55 [0..1] Original Creditor Agent Account 2.56 [0..1] Original Debtor 2.57 [0..1] Original Debtor Account 2.57 [1..1] Identification SEPA (EPC) Condition / Remark VR May only appear if the IBAN of the authorisation deviates from the IBAN used for collection [1..1] {Or IBAN IBAN for the authorisation. E [1..1] Or} Other 2.58 [0..1] Original Debtor Agent 2.58 [1..1] Financial Institution Identification May only appear if the IBAN used for collection by another bank differs from the IBAN used for the authorisation 2.58 [0..1] BIC If this appears, it is ignored [0..1] Clearing System Member Identification If this appears, it is ignored [0..1] Name If this appears, it is ignored [0..1] Postal Address If this appears, it is ignored [0..1] Other 2.58 [1..1] Identification 2.58 [0..1] Scheme name 2.58 [0..1] Issuer 2.59 [0..1] 2.60 [0..1] Original Debtor Agent Account Original Final Collection Date 2.61 [0..1] Original Frequency 2.62 [0..1] Electronic Signature 2.63 [0..1] First Collection Date 2.64 [0..1] Final Collection Date 2.65 [0..1] Frequency 2.66 [0..1] ++++ Creditor Scheme Identification 2.66 [0..1] Name May only be contain the value SMNDA ( Same Mandate New Debtor Agent ) if the IBAN used for collection by another bank differs from the IBAN for the authorisation. (AT-16 The placeholder for the electronic signature data) Does not apply if a paper authorisation is used. Is provisionally not supported. If filled, Creditor Scheme Identification may not occur at the batch level. Creditor Scheme Identification must be the same for all collection items. E080 E252 E066 32

33 Index (ISO) Mult. (ISO) Message element 2.66 [0..1] Postal Address 2.66 [0..1] Identification 2.66 [0..1] {Or Organisation IDentification 2.66 [0..1] Or} Private Identification [1..1] 2.66 [0..1] Date And Place of Birth 2.66 [0..n] Other [1..1] SEPA (EPC) Condition / Remark VR Identifies a party involved as an organisation or a private person 2.66 [1..1] Identification [1..1] (AT-02 Creditor Identifier) 2.66 [0..1] Scheme Name 2.66 [1..1] {Or Code 2.66 [1..1] Or} Proprietary Must contain the value SEPA 2.66 [0..1] Issuer 2.66 [0..1] Country of Residence 2.66 [0..1] Contact Details 2.67 [0..1] ++++ Pre Notification Identification 2.68 [0..1] ++++ Pre Notification Date 2.69 [0..1] +++ Ultimate Creditor 2.69 [0..1] ++++ Name 2.69 [0..1] +++ Postal Address 2.69 [0..1] ++++ Identification 2.69 [1..1] {Or Organisation IDentification If filled, Ultimate Creditor may not occur at the batch level. (AT-38 Creditor Reference Party s name) A maximum of 70 positions (AT-39 Identification code for the Creditor Reference Party) If filled, Private ID may not occur [0..1] BIC or BEI [0..1] {Or If filled, Other may not occur [0..n] Other [0..1] Or} If filled, BIC or BEI may not occur [1..1] Identification 2.69 [0..1] Scheme name 2.69 [1..1] {Or Code Value other than BIC or BEI that identifies the Ultimate Creditor Reference Party as an organisation [1..1] Or} Proprietary A description of the Other identification 2.69 [0..1] Issuer Description of the party that issued the Other identification [1..1] Or} Private Identification E [0..1] Date and Place of Birth 2.69 [1..1] Birth Date 2.69 [0..1] Province of Birth 2.69 [1..1] City of Birth [0..1] {Or If filled, Other may not occur. E061 E075 E084 33

34 Index (ISO) Mult. (ISO) Message element 2.69 [1..1] Country of Birth SEPA (EPC) 2.69 [0..n] Other [0..1] Or} 2.69 [1..1] Identification 2.69 [0..1] Scheme name 2.69 [1..1] {Or Code 2.69 [1..1] Or} Proprietary 2.69 [0..1] Issuer 2.69 [0..1] ++++ Country of Residence 2.69 [0..1] ++++ Contact Details Condition / Remark VR If filled, Date and Place of Birth may not occur. Value other than Date and Place of Birth that identifies the Ultimate Creditor Reference Party as a private person. E.g. a passport number of a driving licence number. A description of the Other identification e.g. the text passport or driving licence. Description of the party that issued the Other identification. E.g. the text municipality as the issuing body for a passport [1..1] +++ Debtor Agent (AT-13 BIC for the Debtor Bank) 2.70 [1..1] ++++ Financial Institution Identification 2.70 [0..1] BIC Debtor Agent Account 2.72 [1..1] +++ Debtor 2.72 [0..1] ++++ Name [1..1] The BIC of the debtor s bank. Must contain a valid value. (AT-14 Debtor name) A maximum of 70 positions 2.72 [0..1] ++++ Postal Address (AT-09 Debtor s address) 2.72 [0..1] Address Type 2.72 [0..1] Department 2.72 [0..1] Sub-department 2.72 [0..1] Street name 2.72 [0..1] Building Number 2.72 [0..1] Post Code 2.72 [0..1] Town Name 2.72 [0..1] Country Sub-division 2.72 [0..1] Country If an ISO country code appears, it must contain 2 positions [0..7] Address Line [0..2] Only 2 lines are supported [0..1] ++++ Identification (AT-27 Debtor Identification Code) 2.72 [1..1] {Or Organisation IDentification If filled, Private ID may not occur [0..1] BIC or BEI [0..1] {Or If filled, Other may not occur [0..n] Other [0..1] Or} If filled, BIC or BEI may not occur [1..1] Identification Value other than BIC or BEI that E068 E069 E084 34

35 Index (ISO) Mult. (ISO) Message element 2.72 [0..1] Scheme name 2.72 [1..1] {Or Code SEPA (EPC) Condition / Remark VR identifies the Originator as an organisation [1..1] Or} Proprietary Description of the Other identification 2.72 [0..1] Issuer Description of the body that issued the Other identification [0..1] Or} Private Identification If filled, Organisation ID may not occur. E [0..1] Date and Place of Birth 2.72 [1..1] Birth Date 2.72 [0..1] Province of Birth 2.72 [1..1] City of Birth 2.72 [1..1] Country of Birth 2.72 [0..n] Other [0..1] Or} 2.72 [1..1] Identification 2.72 [0..1] Scheme name 2.72 [1..1] {Or Code 2.72 [1..1] Or} Proprietary 2.72 [0..1] Issuer 2.72 [0..1] ++++ Country of Residence 2.72 [0..1] ++++ Contact Details [0..1] {Or If filled, Other may not occur. If filled, Date and Place of Birth may not occur. Value other than Date and Place of Birth that identifies the Debtor as a private person. E.g. a passport number of a driving licence number. A description of the Other identification e.g. the text passport or driving licence. Description of the party that issued the Other identification. E.g. the text municipality as the issuing party for a passport [1..1] +++ Debtor Account (AT-07 Debtor Account Number) 2.73 [1..1] ++++ Identification Only IBAN is supported [1..1] {Or IBAN Must contain a valid IBAN E [1..1] Or} Other 2.74 [0..1] +++ Ultimate Debtor 2.74 [0..1] ++++ Name 2.74 [0..1] ++++ Postal Address 2.74 [0..1] ++++ Identification 2.74 [0..1] {Or Organisation IDentification (AT-15 Reference Party Debtor name ) A maximum of 70 positions (AT-37 Debtor Reference Party identification code) If filled Private ID may not occur [0..1] BIC or BEI [0..1] {Or If filled, Other may not occur [0..n] Other [0..1] Or} If filled, BIC or BEI may not occur [0..1] Or} Private Identification If filled, Organisation ID may not occur. E084 E084 35

36 Index (ISO) Mult. (ISO) 2.74 [0..1] Message element Date and Place of Birth 2.74 [1..1] Birth Date 2.74 [0..1] Province of Birth 2.74 [1..1] City of Birth 2.74 [1..1] Country of Birth SEPA (EPC) 2.74 [0..n] Other [0..1] Or} 2.74 [1..1] Identification 2.74 [0..1] Scheme name 2.74 [1..1] {Or Code [1..1] Or} Proprietary [0..1] Issuer 2.74 [0..1] ++++ Country of Residence 2.74 [0..1] ++++ Contact Details 2.75 [0..1] +++ Instruction For Creditor Agent Condition / Remark VR [0..1] {Or If filled, Other may not occur. If filled, Date and Place of Birth may not occur. Value other than Date and Place of Birth that identifies the Ultimate Debtor as a private person. E.g. a passport number of a driving licence number. A description of the Other identification e.g. the text passport or driving licence. Description of the party that issued the Other identification. E.g. the text municipality as the issuing party for a passport [0..1] +++ Purpose (AT-58 Purpose of the Collection) 2.77 [1..1] {Or ++++ Code [1..1] 2.78 [1..1] Or} ++++ Proprietary 2.79 [0..10] +++ Regulatory Reporting 2.80 [0..1] +++ Tax 2.81 [0..10] +++ Related Remittance Information 2.88 [0..1] +++ Remittance Information 2.89 [0..n] ++++ Unstructured [0..1] {Or Only codes from the ISO External Purpose Code List are permitted. (AT-22 Remittance information from the Creditor) Only one of the options Structured or Unstructured - is permitted as a description A maximum of 140 positions is permitted for the description E156 E [0..n] ++++ Structured [0..1] Or} 2.91 [0..n] Referred Document Information A maximum of 140 positions, including tags, is permitted as a description 36

37 Index (ISO) Mult. (ISO) 2.99 [0..1] [0..1] Message element Referred Document Amount Creditor Reference Information [0..1] Type [1..1] Code or Proprietary SEPA (EPC) Condition / Remark VR If used, both Type and Reference must appear [1..1] {Or Code [1..1] Must contain the value SCOR [1..1] Or} Proprietary [0..1] Issuer [0..1] Reference [0..1] Invoicer [0..1] Invoicee [0..3] Additional Remittance Information Possible values, if filled: - ISO if ISO RF Creditor Reference (ISO 11649) is used - CUR if Payment reference number is used (only in the Netherlands) - BBA if Structured Announcement is used (only in Belgium) - Other if Reference is used in the other cases A maximum of 35 positions; the entry depends on the user s entry for E067 E091 E153 E154 37

38 6. SEPA Validation rules For SEPA file formats, the entire file is rejected in the event of a technical error in a validation rule. Status VR Scheme Rejection Message Field Rejected E060 SDD File Payment Method: DD does not appear in tag number Payment <%tagnumber%>; thus, the file is rejected. Method Scheme Scheme Identification Code: SEPA does not appear in tag Rejected E061 SCT File Identification number <%tagnumber%>; thus, the file is rejected. Code Local Local instrument Code: CORE does not appear; thus, the Rejected E062 SDD File instrument file is rejected Code Invalid Transaction Type Code: OOFF, FRST, RCUR, Transaction Rejected E063 SDD File FNAL does not appear in tag number <%line number%>; thus, the file is rejected. Type Rejected E065 SCT File Financial (Creditor) Incorrect Creditor Bank BIC appears in tag number <%line Institution number%>; thus, the file is rejected.. Identification Creditor ID is not the same for all the debits in the file / or is Creditor Rejected E066 SDD File missing / or fails the check digit validation test; thus, the file is rejected. Scheme ID Structured Rejected E067 SDD, Structured Remittance Code: SCOR does not appear in tag File Message SCT number <%line number%>; thus, the file is rejected. Type Rejected E068 Bank SDD, Bank Identifier Code does not appear in tag number <%line File Identifier SCT number%>; thus, the file is rejected. Code Rejected E069 Country Code received in the file is <%Actual Value%> SDD, Country File which is not a valid ISO Country Code; thus, the file is SCT Code rejected. Rejected E070 SDD, Incorrect IBAN present in tag number <%line number%>; File SCT thus, the file is rejected. IBAN An error has been encountered in tag number <%line number%> while processing your file. The tag contains an Requested Rejected E071 SDD, invalid date. The expected date format is YYYY-MM-DD, but Execution / File SCT the format received in the file is <%actualvalue%>. Please Collection make the requisite change (s) and upload the file again. We date have registered this error under ID: <%fileid%>. Rejected E072 An error has been encountered in tag number <%line number%> while processing your file. The expected length SDD, or the tag should not exceed <%expectedvalue%>, while File SCT the length received in the file is <%actualvalue%>. Please Generic make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected E073 An error has been encountered while processing your file. SDD, Please check the hierarchy of the tags, make the requisite File SCT modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Generic Rejected E074 SDD, An error has been encountered in tag number <%line Instructed File SCT number%> while processing your file. The tag contains an Amount 38

39 Status VR Scheme Rejection Message Field invalid amount format or is missing. Please make the Rejected E075 SDD, SCT File Rejected E076 SDD File Rejected Rejected Rejected E077 E078 E079 SDD, SCT SDD, SCT SDD, SCT File File File Rejected E080 SDD File Rejected E081 SDD File Rejected E082 SDD File Rejected E084 SDD, SCT File Rejected E085 SDD File Rejected Rejected Rejected E086 E087 E090 SDD, SCT SDD, SCT SDD, SCT File File File requisite changes(s) and upload the file again. We have registered this error under ID: <%fileid%> Scheme Identification Code: SEPA does not appear; thus, the file is rejected. Transaction Type Code: OOFF, FRST, RCUR, FNAL does not appear; thus, the file is rejected. The Currency Code received in the file is <%Actual Value%> which is not a valid ISO Currency Code; thus, the file is rejected. The Number of Transactions specified in tag name <NbOfTxs> in the file does not match the total transaction count; thus, the file is rejected. The total sum of the individual debit amounts does not match the sum provided in tag name <CtrlSum> in the file; thus, the file is rejected. Original Debtor Agent: SMNDA does not appear; thus, the file is rejected. No details provided, even though the tag <AmdmntInd> is set to TRUE; thus, the file is rejected. Incorrect combination of Amendment Information Details in tag <AmdmntInfDtls>; thus, the file is rejected. More than one Organisational ID or Private ID appears in tag <%tag name%>; thus, the file is rejected. Direct Debit Transaction Information tag name <DrctDbtTxInf> could not be found. An error has been encountered in tag number <%line number%> while processing your file. The expected length of the tag should not be less than <%expectedvalue%>, but the length received in the file is <%actualvalue%>. Please make the requisite change (s) and upload the file again. We have registered this error under ID: <%fileid%> An error has been encountered while processing your file. The tag contains an invalid amount format. Please make the requisite change (s) and upload the file again. We have registered this error under ID: <%fileid%>. An error has been encountered in tag number <%line number%> while processing your file. The tag value contains some special characters (<, >, &, "or ') that need to be escaped. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%> Scheme Identification Code Transaction Type Currency Code Number of Transactions Total sum for Transactions Original Debtor Agent Amendment Information Details Amendment Information Details Organisation al ID/ Private ID Direct Debit Transaction Information Generic Instructed Amount Generic Rejected E091 SDD, File Structured Remittance Code: SCOR does not appear; thus, Structured 39

40 Status VR Scheme Rejection Message Field SCT the file is rejected. Message Rejected E150 SCT File Rejected E151 SCT File Rejected Rejected Rejected E152 E153 E154 SDD, SCT SDD, SCT SDD, SCT File File File Rejected E155 SCT File Rejected Rejected Rejected Rejected Rejected Rejected E156 E157 E158 E159 E160 E161 SDD, SCT SDD, SCT SDD, SCT SDD, SCT SDD, SCT SDD, SCT File File File File File File Rejected E251 SDD File Rejected E252 SDD File Payment Method: TRF does not appear; thus, the file is rejected. Category Purpose: SALA does not appear; thus, the file is rejected. Charge Bearer: SLEV does not appear; thus, the file is rejected. Creditor Ref Info Type under Structured Remittance: Issuer does not appear; thus, the file is rejected. Creditor Reference Info under Structured Remittance: Reference does not appear; thus, the file is rejected. Ultimate Debtor is present at both the Batch and Transaction level, though it is expected at only one level. Therefore the file is rejected. Purpose Code: The tag contains an invalid purpose code which is not part of the External Code List as defined under ISO. Please make the requisite modification(s) and upload the file again. Category Purpose: The value of this tag differs for the batch level and transaction level. Please make the requisite modification(s) and upload the file again. An error has been encountered in tag number <%line number%> while processing your file. The tag contains a value that is less than 0.01 or greater than Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%> Remittance Info: More than one Remittance info value appears; thus, the file is rejected. Debtor IBAN does not appear; thus, the file is rejected. Creditor IBAN does not appear; thus, the file is rejected. Ultimate Creditor appears at both the Batch and Transaction level, even though it is expected at only one level. Therefore, the file is rejected. Creditor Scheme Identification appears at both the Batch and Transaction level, even though it is expected at only one level. Therefore the file is rejected. Rejected E258 SDD File Incorrect IBAN; thus, the file is rejected. Rejected E259 SDD File Sequence Type mismatch: Batch contains at least one direct debit with a Debtor Account Number held with a bank other than the one originally stored in the mandate, which requires a batch Sequence Type equal to Recurrent First. Type Payment method Category Purpose Charge Bearer Creditor Reference Information - Issuer Creditor Reference Information - Reference Ultimate Debtor Purpose Code Category Purpose Amount Remittance information IBAN - Debtor IBAN - Creditor Ultimate Creditor Creditor Scheme Identification Original Debtor IBAN Sequence Type 40

41 ClieOp03 The Netherlands 41

42 7. ClieOp Introduction The ClieOp03 format is a file format for domestic payments and direct debits within the Netherlands. The format is maintained by Equens External Documentation & Information Author Title / Source Version / Date Equens CLIEOP Client Orders, File description. Version 03 ( 1 March Assumptions & Principles Character set ClieOp03 has a fixed line length of 50 positions. Each line concludes with a return; a carriage return and line feed character (hexadecimal x0d x0a), referred to in this description as CRLF. File A ClieOp03 file can contain one or more batches. A file can only contain one transaction type: payments or direct debits. Batch A batch can contain one or more transactions and can only contain one transaction type: payments or direct debits Number of Orders According to the official description, a file may consist of a maximum of 100,000 batches, each with a maximum of 9,999,999 orders. For delivery and processing via Access Online, the maximum number of orders is set at 10,000. Thus, it is possible to deliver 10,000 batches of 1 transaction in a file. 7.3 Records Explanation The Form description is taken over from Equens without any change. The generic Form description of this document is used in the record description. See Table legend. 42

43 9(n): the item is numeric and has n positions. X(n): the item is alphanumeric and has n positions. Name Form Contents File header record Record code Version code 9(4) X(1) 0001 A File creation date File name Submitter identification File identification Duplicate code Filler 9(6) X(8) X(5) X(4) 9(1) X(21) Batch header record Record code Version code 9(4) X(1) 0010 A or C Transaction group Customer Account Number Batch sequence number Delivery currency Batch identification Filler X(2) 9(10) 9(4) X(3) X(16) X(10) Fixed description record Record code Version code 9(4) X(1) 0020 A Fixed description Filler X(32) X(13) Customer record Record code Version code 9(4) X(1) 0030 A Name and address code Desired processing date Customer name Test code Filler 9(1) 9(6) X(35) X(1) X(2) Transaction record Record code Version code 9(4) X(1) 0100 A Transaction type Amount Debtor account number Creditor account number Filler X(4) 9(12) 9(10) 9(10) X(9) Debtor name record Record code Version code Debtor name Filler 9(4) X(1) X(35) X(10) 0110 A 43

44 Name Form Contents Debtor address record Record code Version code Filler 9(4) X(1) X(45) 0113 A Equens ignores the Debtor address record, so this can be deleted from the programs. Payment reference number record Record code Version code 9(4) X(1) 0150 A Payment reference number Filler X(16) X(29) Description record Record code Version code 9(4) X(1) X(32) 0160 A Description Filler X(13) Creditor name record Record code Version code 9(4) X(1) 0170 A Creditor name Filler X(35) X(10) Creditor address record Record code Version code Filler 9(4) X(1) X(45) 0173 A Equens ignores the Creditor address record, so this can be deleted from the programs. Batch trailer record Record code Version code 9(4) X(1) 9990 A Total amount Total account numbers Number of items Filler 9(18) 9(10) 9(7) X(10) File trailer record Record code Version code Filler 9(4) X(1) X(45) 9999 A Optional records are not included in the file / batch if they are not used. Optional fields within a record are filled with spaces if they are not used. 44

45 7.4 File header record File header record Status Mandatory Field Name Type in. Repeat 1 Stat. Validation / Remark VR 1 Record code N4 M Fixed value0001 T01 2 Version code X1 M Fixed valuea T01 3 File creation date N6 M Form: DDMMYY 4 File name X8 M Fixed valueclieop03 T01 5 Submitter identification X5 O 6 File identification X4 O A unique identification number within a month. Position 1-2 = Day number from the file creation date Position 3-4 = Sequence number, incremented by 1 per day per time of delivery 7 Duplicate code N1 M Specifies whether a file is a duplicate of a previously delivered file. 1 = Unique 8 Filler X21 O Spaces 2 = Duplicate T Batch header record Batch header record Status Mandatory Field Name Type in. Repeat 1-10,000 Stat. Validation / Remark VR 1 Record code N4 M Fixed value0010 T01 2 Version code X1 M Fixed valuea C is reserved for future use 3 Transaction group X2 M Identifies the transaction types in the batch 4 Customer Account Number 5 Batch sequence number 00 = payment 10 = collection N10 M Account must appear as the customer s account. Form: 10 figures, filled with leading zeroes N4 M Sequential number incremented by 1 per batch T01 6 Delivery currency X3 M Fixed valueeur T01 7 Filler X26 O Spaces T01 T01 T01 45

46 7.6 Fixed description record Fixed description record Status Remark Field Name Type in. Repeat 0-4 Optional A transaction may have a maximum of 4 Descriptions, or 3 Descriptions and a Payment Reference Number. Stat. Validation / Remark VR 1 Record code N4 M Fixed value0020 T01 2 Version code X1 M Fixed valuea T01 3 Fixed description X32 O Optional. If used, a maximum of 3 lines is displayed. 4 Filler X13 O Spaces 7.7 Customer record Customer record Status Mandatory Field Name Type in. Repeat 1 Stat. Validation / Remark VR 1 Record code N4 M Fixed value0030 T01 2 Version code X1 M Fixed valuea T01 3 Name and address code 4 Desired processing date 5 Customer name X35 O N1 O Specifies whether the commissioning party wishes to receive the name and address of the creditor. 1 = Name and address not desired 2 = Name and address desired N6 O Form: DDMMYY A maximum of 1 year minus 1 day in the future. If the date is in past, the current or next bank working day is used. 6 Test code X1 M Specifies whether a file must be processed as Production or as Test. P = Production T = Test Remark 7 Filler X2 O Spaces In Access Online Test is processed as Production. T01 L01 T01 46

47 7.8 Transaction record Transaction record Status Mandatory Field Name Type in. Repeat 1-10,000 Remark In Access Online, the maximum is restricted. See Number of Orders Stat. Validation / Remark VR 1 Record code N4 M Fixed value0100 T01 2 Version code A1 M Fixed valuea T01 3 Transaction type N4 M Possible value: 0000 = gross accounts payable 0003 = gross salary payment 0005 = net accounts payable 0008 = net salary payment 1001 = net collection 1002 = gross collection 4 Amount N12 M Amount > 0, maximum amount: 999,999, (1 billion minus 5 Debtor account number 6 Creditor account number 1 cent) Amount in EUR, including 2 decimals, without decimal point, right justified, filled with leading zeroes. N10 M An 11 validation control is performed on a 10-digit account number. N10 M An 11 validation control is performed on a 10-digit account number. 7 Filler X9 O Spaces T01 T01 T01 T Debtor name record Debtor name record Status Optional Field Name Type in. Repeat 0-1 Stat. Validation / Remark VR 1 Record code N4 M Fixed value0110 T01 2 Version code X1 M Fixed valuea T01 3 Debtor name X35 O Only positions 1-24 is used. 4 Filler X10 O Spaces 7.10 Debtor address record Debtor address record Status Optional Field Name Type in. Repeat 0-1 Stat. Validation / Remark VR 1 Record code N4 M Fixed value0113 T01 2 Version code X1 M Fixed valuea T01 3 Debtor city X35 O Spaces 4 Filler X10 O Spaces 47

48 7.11 Payment reference number record Payment reference number record Status Field Name Type in. Repeat 0-1 Optional A transaction may have a maximum of 4 Descriptions, or 3 Descriptions and a Payment reference number. Stat. Validation / Remark VR 1 Record code N4 M Fixed value0150 T01 2 Version code X1 M Fixed valuea T01 3 Payment reference number 4 Filler X29 O Spaces X16 M If this field is used as a Transaction Reference number, this must be unique for a period of 1 year. The content of this field is placed in the field RFF+CR. L Description record Description record Status Optional Field Name Type in. Repeat 0-4 A transaction may have a maximum of 4 Descriptions, or 3 Descriptions and a Payment reference number. Stat. Validation / Remark VR 1 Record code N4 M Fixed value0160 T01 2 Version code X1 M Fixed valuea T01 3 Description X32 O 4 Filler X13 O Spaces 7.13 Creditor name record Creditor name record Status Optional Field Name Type in. Repeat 0-1 Stat. Validation / Remark VR 1 Record code N4 M Fixed value0170 T01 2 Version code X1 M Fixed valuea T01 3 Creditor name X35 O Optional for transactions to bank numbers, mandatory for transactions to 7-digit account numbers if the transaction type is gross. 4 Filler X10 O Spaces 7.14 Creditor address record Creditor address record Status Optional Field Name Type in. Repeat 0-1 Stat. Validation / Remark VR 1 Record code N4 M Fixed value0173 T01 2 Version code X1 M Fixed valuea T01 3 Filler X45 O Spaces 48

49 7.15 Batch trailer record Batch trailer record Status Mandatory Field Name Type in. Repeat 1-n Stat. Validation / Remark VR 1 Record code N4 M Fixed value9990 T01 2 Version code X1 M Fixed valuea T01 3 Total amount N18 M A maximum of 45,378,021, Account numbers total Total count of all amounts within the batch. N10 M The last 10 figures of the total count. Total count of all debit and credit account numbers within the batch. 5 Number of items N7 M A maximum of 10,000 transactions per file. 6 Filler X10 O Spaces Total count of all transactions within the batch. T01 T01 T File trailer record File trailer record Status Mandatory Field Name Type in. Repeat 1 Stat. Validation / Remark VR 1 Record code N4 M Fixed value9999 T01 2 Version code X1 M Fixed valuea T01 3 Filler X45 O Spaces 7.17 Validation rules Technical Validation In the event of a technical error in a validation line for this file format, the total file is rejected. Consequently, only the generic message is described. Status VR Rejection Message Field Rejected T01 File An error has been encountered while processing your file. The expected value of the field <%Field Name%> in record type <%Record Type%>???, while the value received in the file is <%ActualValue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. various This is a generic message. An approximate specification of the erroneous record/field and line number is included. 49

50 BTL91 The Netherlands 50

51 8. BTL Introduction The BTL91 format is a file format for international payments. The format was developed by ABN AMRO in External Documentation & Information Author Title / Source Version / Date ABN AMRO SEPA: a single European payments market Assumptions & Principles Standard upload profile In Access Online, instructions regarding how the upload file must be processed can be specified in more detail in the upload profile for the BLT91 format. The description of the BTL91 in this chapter is based on an upload profile with standard settings. If non-standard settings are used in the upload profile, this can affect the validation/control and the messages described in this chapter Security file hash BTL91 supports the use of file hash integrity checks in the Trailer record. In Access Online, when managing upload profiles, it is possible to specify whether such a check must be performed while uploading BTL91 files. The description of the various file hash methods and the use of this form of security fall outside the scope of this document. 8.3 File Structure Technical File BTL91 has a fixed line length of 192 positions. Each line concludes with a return; a carriage return and line feed character (hexadecimal x0d x0a), designated in this description using CRLF. Remark In Access Online, it is possible to deviate from this rule. Optional fields at the end of a record may be missing Character set See Chapter 19 Character Sets for an overview of the characters that can be used in the BTL91 file format. 51

52 8.3.3 Logical File A BTL91 file contains 1 header record, 1 batch and 1 trailer record. A batch consists of a maximum of 9,999 payment orders followed by one or more total records. There is one total record per ISO-Currency Code Order used in the payment orders. A payment order consists of 4 payment records. The payment orders have a unique number and are sorted in ascending order. Level Record Type Repeat File Header record 11 1 Batch Payment order Payment record , Total record 31 1 n Trailer record Header record Header record The header record is the first record of the file and contains information regarding the commissioning client. Status Mandatory Repeat 1x per File Field Name Type Stat Condition / Remark VR 11-1 Record code N2 M Fixed value11 T Exchange Bank X4 O Fixed valueabna 11-3 Medium code X1 O Fixed valuex 11-4 Version number N2 O Value between Date Create File N8 O Layout ccyymmdd 11-6 Batch number N3 O Value between Customer Name X35 O 11-8 Customer Address X35 O 11-9 Customer City X35 O Customer Country X35 O Industry N4 O Desired Execution Date N8 O Layout ccyymmdd Not Used X20 O 52

53 8.5 Payment record part 1 Payment record 1 of 4 First record in the transaction Status Mandatory Repeat 1x per Transaction Field Name Type Stat Condition / Remark VR 21-1 Record code N2 M Fixed value21 T Order number N4 M Value between ISO Currency Code A3 O Customer Account Number 21-4 Customer Account N10 M T02 Number 21-5 ISO Currency Code Order A3 M T03 L Order Amount N15 M Amount > 0 and less than 90 billion. Amount with 3 decimal places, the third decimal place of which must be 0, without a decimal point, right justified, and filled with leading zeroes, where necessary. L08 If the Currency Code is JPY or ISK, the 3 decimals must T03 be Desired Processing N8 M Date in the format ccyymmdd L06 Date L Code Costs BNL N1 C If empty, the standard value1is used. L03 In conjunction with field 21-9, this field specifies how costs L05 for the execution of the transaction are allocated between the commissioning bank and the creditor bank. Supported values: 1 (OUR): Costs for bank customer 2 (BEN): Costs for creditor bank 3 (SHA): Costs shared between bank customer and creditor bank. Value is specified as follows: If field 21-8 = 1 and field 21-9 = 1 then OUR If field 21-8 = 3 and field 21-9 = 3 then BEN If field 21-8 = 1 and field 21-9 = 3 then SHA Other combinations: If field 21-8 = 1 and field 21-9 = 2 then OUR If field 21-8 = 2 and field 21-9 = 1 then OUR If field 21-8 = 2 and field 21-9 = 2 then OUR If field 21-8 = 2 and field 21-9 = 3 then SHA If field 21-8 = 3 and field 21-9 = 1 then OUR If field 21-8 = 3 and field 21-9 = 2 then OUR 21-9 Costs Corr Code N1 C If empty, the standard value3is used L03 53

54 Payment record 1 of 4 First record in the transaction Status Mandatory Repeat 1x per Transaction Field Name Type Stat Condition / Remark VR See field 21-8 for an explanation. L Type of Order Code N1 C Standard value0 0 = Transfer 1 = Cheque payment Type of Execution Code N1 C Standard value0 0 = Normal 1 = Urgent Only applies in the event of a Transfer Cheque Cross Code X1 O If not used: space. Y = Crosses This field is no longer used Cheque Dispatch Code X1 C Cheque address L07 1 = Customer Office 2 = Customer 3 = Creditor Mandatory for a Cheque payment Payment instructions 1 Code X2 O Instructions intended for the receiving bank. 01 or 02 = Notify the creditor by telephone 07 = Keep available for the creditor Only applies in the event of an Urgent Transfer Payment instructions 2 X2 O This field is no longer used. Code Payment instructions 3 X2 O This field is no longer used. Code Payment instructions 4 X2 O This field is no longer used. Code Filler X133 O 8.6 Payment record part 2 Payment record 2 of 4 Second record of the transaction. Contains information regarding the Creditor Status Mandatory Repeat 1x per Transaction Field Name Type Stat Condition / Remark VR 22-1 Record code N2 M Fixed value22 T Order number N4 M Value between Identical to the value in field Creditor account number X34 C Mandatory: if Payment and/or Creditor ISO Country Code are NL, the number consists of figures and (capital) letters, L04 L20 is left justified and is filled with spaces, where necessary. Preferably an IBAN; otherwise a Bank Code + account number. Cheque: Empty 22-4 Creditor name X35 M The first 24 characters are used. L01 L10 54

55 Payment record 2 of 4 Second record of the transaction. Contains information regarding the Creditor Status Mandatory Repeat 1x per Transaction Field Name Type Stat Condition / Remark VR L Creditor Address X35 C Payment: Optional L01 Cheque: Mandatory 22-6 Creditor City X35 M The first 20 characters are used. L01 L12 L Creditor ISO Country A2 C May be left empty if field 22-3 Creditor Account Number L14 Code contains an IBAN number. Mandatory if field 22-3 does not contain an IBAN number Creditor Country A35 O This field is no longer used Filler X10 O 8.7 Payment record part 3 Payment record 3 of 4 Third record of the transaction. Contains information regarding the Creditor s bank Status Mandatory Repeat 1x per Transaction Field Name Type Stat Condition / Remark VR 23-1 Record code N2 M Fixed value23 T Order number N4 M Value between Identical to the value in field Swift-BIC for the Creditor s bank X11 C The BIC code (SWIFT address) for the creditor s bank. Contains a valid BIC code consisting of 8 or 11 consecutive positions. Positions 5 and 6 contain the ISO Country Code of the Creditor s bank and, if filled, must correspond to field L02 L04 L16 Mandatory in the event of: - payment in EUROS - payments for which field 23-7 is empty 23-4 Name of the Creditor s X35 M L01 bank L Creditor bank address X35 O L Creditor bank city X35 O L Creditor bank ISO A2 C If 23-3 is filled, this field must: L17 Country Code - be empty L18 - correspond to position 5-6 in field Creditor bank country A35 O This field is no longer used Filler X33 O Spaces 55

56 8.8 Payment record part 4 Payment record 4 of 4 Fourth record of the transaction. Contains information regarding the Payment Status Mandatory Repeat 1x per Transaction Field Name Type Stat Condition / Remark VR 24-1 Record code N2 M Fixed value24 T Order number N4 M Value between Identical to the value in field Reason for Payment 1 X35 O 24-4 Reason for Payment 2 X35 O 24-5 Reason for Payment 3 X35 O 24-6 Reason for Payment 4 X35 O 24-7 Filler X46 O Spaces 8.9 Total record Total record Contains information for file control. The Total records are calculated for each ISO Currency Code Order that appears. Status Mandatory Repeat 1-n (1x per ISO Currency Code / per file) Field Name Type Stat Condition / Remark VR 31-1 Record code N2 M Fixed value31 T ISO Currency Code for A3 M Refers to value in field 21-5 T04 the Order Total 31-3 Total Order Amount N15 M The total of the Order Amounts (field 21-6) in the ISO Currency Code as specified in record T04 Amount specified to 3 decimal places, the third of which must be 0, without a decimal point, right justified, filled with leading zeroes. If the total exceeds the field length, the leftmost positions are truncated Number of Orders N4 M The Number of Orders in the ISO Currency Code as specified in record Filler X168 O Spaces T04 56

57 8.10 Trailer record Trailer record The trailer record is the last record of the file and contains information for file control. Status Mandatory Repeat 1 Field Name Type Stat Condition / Remark VR 41-1 Record code N2 M Fixed value41 T Total Number of N6 M Total number of records in the file including header record, T04 Records the payment records, total records and the trailer record Total Number of Orders N4 M The Total Number of Orders T File hash X24 O Hash code for integrity control See Security file hash 41-5 Filler X156 O Spaces 8.11 Validation rules Technical Validation Status VR Rejection Message Field Syntax error T01 File An error has been encountered while processing your file. A mandatory record and/or field is missing. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: An error has been encountered in record number 1 while processing your file. The syntax for field 2 is wrong. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: These are generic messages. An approximate specification of the incorrect record/field and line number is included. Rejected T02 Payment Payment is rejected in the event of an improper debit account number in 21-4 the file. T03 Payment Decimals in the upload file are not permitted for this currency Invalid T04 File An error has been encountered in record number # while processing your 31-2 Trailer file. Either a mismatch in the total amount, the total number of records, the 31-3 record total number of payments or the total number of orders in your file caused 31-4 this error in the trailer record. Please make the requisite modification(s) 41-2 and upload the file again. We have registered this error under ID: This message is also generated if: - ISO Currency Code Order is empty 57

58 Logical Validation Status VR Message Field Entered Messages are for notification purposes. Orders are executable. L01 Name / Address / City [of the bank] creditor contains non-supported characters. These characters are either deleted or changed into characters that are supported. This payment can be specified as a SEPA transfer. See explanation SEPA Orders. L02 SWIFT address of the creditor s bank. This is recommended for this payment L03 The cost option is set to SHA. (If 21-8 and 21-9 are empty or contain an incorrect value.) 21-8 L04 As of 1 January 2007, the IBAN and BIC (SWIFT ID) of the creditor bank are required for cross-border payments within the EU/EEA. L05 Costs options may not be used for this payment L06 L07 The selected value date is in the past. ABN AMRO will process the payment on the next value date. Selected Cheque to code may not be used for this payment. (1 = Office Customer) Incomplete Messages require additional action. Orders will only be executable after correction. L08 Transfer amount must be greater than L09 The selected value date is more than ninety days in the future. ABN AMRO cannot 21-7 schedule anything for this value date. L10 Creditor name is mandatory L11 Creditor name is invalid (length must be between 1 and 24) L12 Creditor city is mandatory L13 Creditor city is invalid (length must be between 1 and 20) L14 Creditor country is mandatory L15 Name of creditor bank is mandatory L16 SWIFT address of the creditor bank is mandatory L17 Country of the creditor bank is mandatory L18 Country of the creditor bank is an invalid country Rejected Messages are for notification purposes. Orders are not executable. L19 Transfer currency is mandatory L20 Creditor account is mandatory

59 8.12 Payments Complete This table shows the fields and the values that must be used (at a minimum) for various types of orders. Payment Type Then Value Normal EUR payment to EU country with a ISO_Currency code_order EUR correct IBAN and BIC, costs shared, no Code_Costs_BNL (1 = Euro account) 1 instructions. Code_Costs_Corr (3 = Creditor) 3 (=SEPA) Type of Order Code (0 = Transfer) 0 Type of Execution Code (0 = Normal) 0 Account number_creditor IBAN Name_Creditor Filled City_Creditor Filled Swift_BIC_Bank_of_Creditor BIC Name_Bank_of_Creditor Filled Normal non-eur payment to EU country with correct IBAN and BIC, costs shared, no instructions. ISO_Currency code_order <>EUR Code_Costs_BNL (1 = Euro account) 1 Code_Costs_Corr (3 = Creditor) 3 Type of Order Code (0 = Transfer) 0 Type of Execution Code (0 = Normal) 0 Account number_creditor IBAN Name_Creditor Filled City_Creditor Filled Swift_BIC_Bank_of_Creditor BIC Name_Bank_of_Creditor Filled Urgent non EUR payment outside the EU with correct BBAN and BIC, costs shared, with instruction: Notify the creditor (telephone) ISO_Currency code_order <>EUR Code_Costs_BNL (1 = Euro account) 1 Code_Costs_Corr (3 = Creditor) 3 Type of Order Code (0 = Transfer) 0 Type of Execution Code (1 = Urgent) 1 Account number_creditor BBAN Name_Creditor Filled City_Creditor Filled Swift_BIC_Bank_of_Creditor BIC Name_Bank_of_Creditor Filled Cheque ISO_Currency code_order Filled Type of Order Code (1 = Cheque) 1 Cheque Dispatch Code (Check Address) 2 or 3 2 = Customer 3 = Creditor Name_Creditor Filled Address_Creditor Filled City_Creditor Filled ISO Country Code Creditor Filled 59

60 EC criteria for Payments The BTL91 format supports EU payments. An EU payment must satisfy the EC criteria in order to be processed at the domestic rate: The payment is within/between EU countries (see 20.1 ISO Country Code); The amount of the payment is in EUR; The amount does not exceed the maximum of 50, euros; The creditor account number for the payment is correct and complete and is specified in IBAN format; The payment includes a correct and complete Swift-BIC for the creditor s bank; The payment is based on shared costs with the creditor (shared); The payment does not contain any supplemental payment instructions. Field Name Condition / Remark 21-5 ISO Currency Code Order ValueEUR 21-6 Order Amount Amount > 0 and <= Code Costs BNL Value1 Costs charged to: Euro account 21-9 Costs Corr Code Value3 Correspondent Costs charged to: Creditor 21-14/ Code for Payment instructions 1 through 4 Empty Creditor account number IBAN (International Bank Account Number) 23-3 Swift-BIC code of the Creditor s bank BIC Code (SWIFT address) 23-7 ISO Country Code of the Creditor s bank Empty SEPA Orders The BTL91 file format is not appropriate for SEPA Orders. Special XML file formats have been developed for SEPA Orders. However, BTL91 can contain the basic information after which the order can be subsequently enriched to a SEPA order via Access Online. The following conditions apply for this: The creditor bank is located within the SEPA zone (see 20.1 Country code); The amount of the payment is specified in EUR; The payment includes the correct and complete creditor account number specified in IBAN format; The payment includes a correct and complete Swift-BIC for the creditor bank; The payment takes place based on shared costs with the creditor (shared); The payment does not contain any supplemental payment instructions. Field Name Condition / Remark 21-5 ISO Currency Code for the Order ValueEUR 21-8 Costs BNL Code Value1 Costs charged to: Euro account 21-9 Costs Corr Code Value3 Correspondent Costs charged to: Creditor 21-14/ Code Payment instructions 1 through 4 Empty Creditor account number IBAN (International Bank Account Number) 23-3 Swift-BIC of the Creditor bank BIC Code (SWIFT address) 23-7 ISO Country Code of the Creditor bank Empty 60

61 In Access Online, whether or not transactions must be executed by default as SEPA Credit Transfers if they satisfy these criteria can be specified in the Upload profile. 61

62 CIRI Belgium 62

63 9. CIRI 9.1 Introduction CIRI = Centre Interbank de Recherche Informatique. The CIRI protocol is the current standard format for payments in Belgium External Documentation & Information Author Involves Source Febelfin: Comprehensive federation for the Information with regard Belgian financial sector. to payments in Belgium 9.2 Assumptions & Principles Number of Orders According to the official description, there may be a maximum of 9,999,999 records in a file. For the delivery and processing via Access Online, the maximum Number of Orders is set at 10,000. Remark The column Fld (field) in the record tables is not part of the official Febelfin format description. These are added to simplify searches for mutual references. 63

64 10. CIRI FBF Domestic Payment Orders 10.1 Introduction This chapter describes the Belgian CIRI FBF format that is used to offer domestic payment orders Scope The CIRI FBF has 2 record types: layout 360 and layout 128. Access Online only supports the CIRI FBF lay-out 128. This chapter is thus limited to the Belgian CIRI FBF file format lay-out 128 used for domestic payment orders. This chapter describes the following aspects regarding the FBF (lay-out 128) file format: the technical file structure; the validation rules and the error messages Payment versions The CIRI FBF 128 file format does not contain a specific indicator with which a batch can be designated. Access Online implicitly deals with the files submitted as batch files containing domestic standard salary transfers. After reading the file, it can be specified in Access Online whether the batch file must be split into individual orders External Documentation & Information Author Title / Source Version / Date Febelfin Payment orders, Bank Standard No. I.1 version 5 edition ( November File format Each logical file may only include payment orders for one account number to be debited, one desired Execution Date, one type of payment and one interbank clearing code; Each file contains: one header record 0 with identification data data records 1 with the mandatory basic data and data records 2 with optional additional data. Data record 2 may appear if a second line notice is required (optional for Type Transfer 5 to 8). a single trailer record containing control data. Several logical CIRI files may be combined into a single physical file. If a file does not satisfy these validation conditions, the result is negative and the entire file is rejected. Level File Customer Header record 0 1 Payment order 1-10,000 Data record Data record Trailer record

65 10.4 Header record The header record is the first record of the logical file. It contains information regarding the commissioning client; the identification information. This record may only appear once in a logical file. Header record Status Mandatory Fld Name Type in. Repeat 1 Stat Condition / Remark VR H1 Record code N1 M Fixed value0 T01 H2 Interbank clearing N1 O Ignored in Access Online H3 Filler X1 O Reserved H4 Payment Type N2 M Numeric value in series: 00: Not defined 01: Pensions 02: Wages 03: Child allowance 04: Replacement income (unemployment, disability) 05: Government payment 06: Social Secretariat 07: Suppliers 08: Vacation pay 09: Intra-company 10: Invoice 11: Treasury, 12: Social Secretariat procedure 2 H5 Creation date N6 O Ignored in Access Online H6 Code number for the Consignee s Financial Institution N3 O Ignored in Access Online H7 Application code N2 M Fixed value01 T03 H8 Desired Execution Date N6 M Desired Execution Date for the payment order. Possible value: - Date in the format DDMMYY H9 Duplicate code X1 O Ignored in Access Online H10 Filler N3 O Reserved - 6 zeroes; is interpreted as the current date during processing. H11 Account number N12 M Value 12-digit number > 0. Account number must be expressed in EUR and linked to the BE country code via the bank code. Customer account number. Payment orders are charged to this account number. H12 Customer name X26 O Ignored in Access Online. T02 T04 T05 T06 T07 H13 Customer Address X26 O Ignored in Access Online. Access Online retrieves data from its own administration. H14 Customer Postal Code X4 O Ignored in Access Online. Access Online retrieves data from its own administration. H15 Customer City X22 O Ignored in Access Online. Access Online retrieves data from its own administration. 65

66 Header record Status Mandatory Fld Name Type in. Repeat 1 Stat Condition / Remark VR Access Online retrieves data from its own administration. H16 Customer Language N1 O Ignored in Access Online Code H17 File Reference X10 O If empty, NONREF is used. The file reference is passed on by the Customer. This can be used for reconciliation. The value is taken over in Batch Reference. H18 Version Code N1 M Fixed value5 = Euro payment orders T Data record 1 Data records 1 and 2 contain information regarding the order. Data record 1 Status Mandatory Repeat 1 10,000 Fld Name Type Stat Condition / Remark VR in. D1 Record code N1 M Fixed value1 T01 D2 Sequence number N4 M Value 4-digit number T09 Ascending sequence number: starts with0001 and is incremented by 1 for each subsequent data record. (after9999 numbering starts over with 0000, 0001, 0002 ) D3 Customer Reference number X8 O Reference number assigned by the Customer. If empty,nonref is used. D4 Filler X10 O Reserved D5 Creditor account N12 M Value 12-digit number > 0. T10 number D6 Order amount N12 M Value > 0 Amount in EUR, including 2 decimals, without a decimal point. T11 T12 D7 Creditor name X26 O D8 Beneficiary language N1 O Ignored in Access Online code D9 Description 1 X12 O Information for Creditor, depending on Type in D11 If D11 = 3 then Unstructured announcement (info part 1) If D11 = 8 then Structured announcement (exclusively numeric) D10 Description 2 X41 O Information for Creditor, depending on Type in D11 T13 If D11 = 3 then Unstructured announcement (continuation of info part 2) If D11 = 8 then Spaces D11 Transfer Type N1 M Value: 3 or8 3: ordinary transfer T14 66

67 Data record 1 Status Mandatory Repeat 1 10,000 Fld Name Type Stat Condition / Remark VR in. 8: transfer with structured announcement See D9 and D Data record 2 Data record 2 Status Optional Fld Name Type in. Repeat 0 10,000 Stat Condition / Remark VR D12 Record code N1 M Fixed value2 T01 D13 Sequence number N4 M Value: 4-digit number Sequence number identical to the previous record, Record code 1 D14 Code Title N1 O Ignored in Access Online D15 Creditor Address X26 O D16 Creditor Postal Code X4 O D17 Creditor City N22 O D18 Description 3 X53 O Information for Creditor, depending on Type in D11 If D11 = 3 then Unstructured announcement (continuation of info part 3) D19 Code Costs N1 O Value: 0-2, standard value0 If D11 = 3 then 1: costs charged to the customer 2: costs charged to the creditor D20 Filler X16 O Reserved T15 T Trailer record The trailer record is the last record in the logical file. It contains information for file control. This record may only appear once in a logical file. Trailer record Status Mandatory Fld Name Type in. Repeat 1 Stat Condition / Remark VR T1 Record code N1 M Fixed value9 T01 T2 Number of Data records N4 M Number of Data records. (the last 4 figures to the right; for example: 2523 in the event of 12,523 Data records) Data Record Count (Record code1 and 2). See D1 and D12. T3 Number of Orders N4 M Number of Payment orders. (Last 4 figures to the right; for example: 2523 in the event of 12,523 orders) Payment Order Count (Record code1). See D1 and D12. T17 T18 67

68 Trailer record Status Mandatory Fld Name Type in. T4 T5 T6 Total Amount for the Orders Total Creditor Account numbers Sender Identification number Repeat 1 Stat Condition / Remark VR N12 M Sum of Order amounts Sum of Order amount in Data records with Record code = 1. See D6. N15 M Sum of Creditor Account numbers. Total number of Account numbers in D5. If the first 3 figures are zeroes, the control is limited to the last twelve figures. N11 O Ignored in Access Online T7 File reference 2 X12 O Ignored in Access Online T8 Filler X49 O Reserved T9 Filler X20 O Reserved T19 T Validation rules Technical Validation In the event of a technical error in a validation rule for this file format, the entire file is rejected. Consequently, only the generic message is described. Status VR Rejection Message Field Rejected T01 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%record Identification%> is "#", but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. H1 D1 D12 T1 # is 0, 1, 2 or 9 Rejected T02 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%Object of payment%> is: 00, 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11 or 12,, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T03 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%application code%> is: 01, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T04 File An error has been encountered in record number <%recordnumber%> while processing your file. The field <%excecution date%> contains an invalid date. The expected date format is numeric DDMMYY, but the format received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. H4 H7 H8 68

69 Status VR Rejection Message Field Rejected T05 File An error has been encountered in record number <%recordnumber%> H11 while processing your file. The expected value of the field <%ordering Customer Account Number%> is 12N, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T06 File An error has been encountered in record number <%recordnumber%> H11 while processing your file. The expected currency of the field <%ordering Customer Account Number%> is "Euro", but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T07 File An error has been encountered in record number <%recordnumber%> H11 while processing your file. The expected country of the field <%ordering Customer Account Number%> is "BE", but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T08 File An error has been encountered in record number <%recordnumber%> H18 while processing your file. The expected value of the field <%version code%> is "5", but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T09 File An error has been encountered in record number <%recordnumber%> D2 while processing your file. The expected value of the field <%sequence number> is N4 starting at 0001 but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T10 File An error has been encountered in record number <%recordnumber%> D5 while processing your file. The expected value of the field <%beneficiary Customer Account Number%> is 12N, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T11 File An error has been encountered in record number <%recordnumber%> D6 while processing your file. The expected value of the field <%amount%> is greater than 0, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T12 File An error has been encountered in record number <%recordnumber%> D6 while processing your file. The expected format of the field <%amount%> is <%expectedvalue%> in Euro Cents, but the format received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T13 File An error has been encountered in record number <%recordnumber%> while processing your file. Since the Type code is "8" the expected format for the field <%first continuation of ordinary message %> is blank, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. D10 69

70 Status VR Rejection Message Field Rejected T14 File An error has been encountered in record number <%recordnumber%> D11 while processing your file. The expected value of the field <%type code%> is "3" or "8"., but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T15 File An error has been encountered in record number <%recordnumber%> D13 while processing your file. The expected value of the field <%sequence number> is N4 starting at 0001 but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T16 File An error has been encountered in record number <%recordnumber%> D13 while processing your file. The expected value of the field <%sequence number> is <%expectedvalue%> starting at 0001, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T17 File An error has been encountered in record number <%recordnumber%> T2 while processing your file. The expected value of the field <%number of data records 1 and 2%> is the total of 1 and 2 records in the file, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T18 File An error has been encountered in record number <%recordnumber%> T3 while processing your file. The expected value of the field <%number of payment orders%> is the total of data records 1 in the file, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T19 File An error has been encountered in record number <%recordnumber%> T4 while processing your file. The expected value of the field <%total of amounts%> is the total of all amounts specified in data record 1 in the file, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T20 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%total of account numbers to be credited%> is the total of all beneficiary accounts specified in data record 1 in the file, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. T5 70

71 11. CIRI VME Foreign Payment Orders 11.1 Introduction This chapter describes the Belgian CIRI VME format that is used to offer foreign payment orders Scope This chapter describes the following aspects of the CIRI VME (lay-out 128) file format: the technical file structure; the validation rules and the error messages Payment versions The CIRI VME format supports the following versions: Standard transfers (international) Urgent transfers (international) Bank Cheques External Documentation & Information Author Title / Source Version / Date Febelfin Foreign Payment orders, Bank Standard No. I.4, version 3.1 edition ( September File format Each file contains: one header record 0 with identification data Data records, with data regarding the debiting party (principal), the crediting party (creditor) and the details regarding the payments. Access Online supports the following sub-divisions: 01 (mandatory), 03 (optional), 04 (optional), 05 (optional), 06 (mandatory), 07 (optional), 08 (optional), 09 (optional) & 10 (mandatory). If delivered, sub-divisions 11, 12 & 13 are ignored by Access Online. one trailer record with control data. Level File Customer Header record 0 1 Payment order 1-10,000 Transaction record, sub-division Transaction record, sub-division Transaction record, sub-division Transaction record, sub-division Transaction record, sub-division Transaction record, sub-division Transaction record, sub-division Transaction record, sub-division Transaction record, sub-division Transaction record, sub-division Transaction record, sub-division

72 Level Transaction record, sub-division Transaction record, sub-division Trailer record Header record The header record is the first record of the logical file. It contains information regarding the commissioning client; the identification information. This record may only occur once in a logical file. Header record Status Mandatory Fld Name Type in. Repeat 1 Stat Condition / Remark VR H1 Record code N1 M Fixed value 0 T01 H2 File creation date N6 O Ignored in Access Online. H3 Filler X12 O Reserved H4 Protocol code number N3 O Ignored in Access Online. H5 Application code N2 M Fixed value 51 T02 H6 File reference N10 O Reference passed on by the commissioning party/debtor. This reference is used as the set name in Access Online. If empty, the value is taken over from the Access Online upload profile as the set name. H7 Sender Identification N11 O Ignored in Access Online number H8 Customer Identification N11 O Ignored in Access Online number H9 Duplicate code X1 O Ignored in Access Online H10 Version Code N1 M Fixed value 3 T03 H11 Zone intended for X12 O Ignored in Access Online bilateral relations or blanks H12 Globalisation code N1 O Ignored in Access Online H13 Filler X4 O Reserved H14 Version sub-code N1 M Fixed value 1 T04 H15 Filler X52 O Reserved 11.5 Data record 1, sub-division 01 Data record 1 Status Mandatory Repeat 1 10,000 Fld Name Type Stat Condition / Remark VR in. D1-1 Record code N1 M Fixed value 1 T01 D1-2 Sequence number N4 M Value 4-digit number Ascending sequence number: starts with0001 and is incremented by 1 for each data record. (after9999 the numbering starts over with 0000, 0001, 0002 ) T05 T06 72

73 Data record 1 Status Mandatory Repeat 1 10,000 Fld Name Type Stat Condition / Remark VR in. D1-3 Sub-division N2 M Fixed value 01 T07 D1-4 Desired Execution X6 M Desired Execution Date of payment order. T08 Date Possible value: - Date with the layout DDMMYY - 6 zeroes; is interpreted as the current date during processing. D1-5 Customer Reference number X16 O Reference number assigned by the Customer. If empty,nonref is used. D1-6 Currency type order A3 M ISO currency type order amount T09 amount D1-7 Filler X1 O Reserved D1-8 Code for order X1 M Fixed value C T10 amount D1-9 Order amount N15 M Value > 0 Amount in cents, including 2 decimal places, without a decimal T11 T12 point. D1-10 Filler X1 O Reserved D1-11 Debit account A3 O ISO currency type debit account currency type D1-12 Filler X6 O Reserved D1-13 Debit account N12 M Customer account number. Orders are charged to this account number. Value 12-digit number > 0. T13 T14 D1-14 Filler X22 O Reserved D1-15 Designation X1 O Ignored in Access Online regarding the requested date D1-4 D1-16 Filler X34 O Reserved 11.6 Data record 1, sub-division 02 Data record 1 Status Optional Fld Name Type in. Repeat 0 10,000 Stat Condition / Remark VR D2-1 Record code N1 M Fixed value 1 T01 D2-2 Sequence number N4 M Value 4-digit number Identical to the data record 1 (data record 1, sub-division 01) that immediately precedes this record D2-3 Sub-division N2 M Fixed value 02 T07 D2-4 Customer name X35 O Ignored in Access Online. T05 T06 Access Online retrieves data from its own administration. D2-5 Address Customer X70 O Ignored in Access Online. Access Online retrieves data from its own administration. D2-6 Filler X16 O Reserved 73

74 11.7 Data record 1, sub-division 03 Data record 1 Status Optional Fld Name Type in. Repeat 0 10,000 Stat Condition / Remark VR D3-1 Record code N1 M Fixed value 1 T01 D3-2 Sequence number N4 M Value 4-digit number Identical to data record 1 (data record 1, sub-division 01) that immediately precedes this record D3-3 Sub-division N2 M Fixed value 03 T07 D3-4 Address Customer X35 O Ignored in Access Online. D3-5 Filler X10 O Reserved D3-6 Identification of the intermediary bank D3-7 Filler X65 O Reserved Access Online retrieves data from its own administration. X11 O If filled, the intermediary bank data is enriched. T05 T Data record 1, sub-division 04 Data record 1 Status Optional Fld Name Type in. Repeat 0 10,000 Stat Condition / Remark VR D4-1 Record code N1 M Fixed value 1 T01 D4-2 Sequence number N4 M Value 4-digit number Identical to data record 1 (data record 1, sub-division 01) that immediately precedes this record D4-3 Sub-division N2 M Fixed value 04 T07 D4-4 Filler X80 O Reserved D4-5 Identification of the creditor bank D4-6 Identification Code for the creditor bank X35 M Identification of the creditor bank This can be: - a BIC (recommended identification) and/or the identification code of the national clearing house followed by the clearing number: or - a name - blank for cheques Pos : 11AN : BIC (SWIFT address) Pos 99 : 1AN : blank Pos : 2AN : identification code for the national clearing house Pos : 21AN : clearing number If not, Pos : name of the creditor bank X1 O Designation specifying the identification of the creditor s bank: - 1 : as in positions , BIC - 2 : as in positions , name - blank D4-7 Filler X5 O Reserved T05 T06 74

75 11.9 Data record 1, sub-division 05 Data record 1 Status Optional Fld Name Type in. Repeat 0 10,000 Stat Condition / Remark VR D5-1 Record code N1 M Fixed value 1 T01 D5-2 Sequence number N4 M Value 4-digit number Identical to data record 1 (data record 1, sub-division 01) that immediately precedes this record D5-3 Sub-division N2 M Fixed value 05 T07 D5-4 Branch Name X35 O Bank Branch Name Creditor D5-5 Branch Address X35 O Street address for the creditor s bank branch D5-6 Branch Address X35 O City, province/(sub-)state and country of the creditor s bank branch D5-7 Filler X16 O Reserved T05 T Data record 1, sub-division 06 Data record 1 Status Mandatory Fld Name Type in. Repeat 1 10,000 Stat Condition / Remark VR D6-1 Record code N1 M Fixed value 1 T01 D6-2 Sequence number N4 M Value 4-digit number Identical to data record 1 (data record 1, sub-division 01) that immediately precedes this record D6-3 Sub-division N2 M Fixed value 06 T07 D6-4 Creditor account number X34 O Account number of the creditor: - IBAN: recommended for cross-border payments - Or for domestic payments. 1 blank D6-5 Creditor name X35 O Creditor name. alphabetic ISO Currency Code of the account to be credited, only if this differs from the payment currency; if this does not differ, this is filled with blanks.. 6 blanks. structured account number (pos 18-29). 12 blanks - Or, free use of 34 AN characters D6-6 Creditor Address X35 O Creditor address: possibly followed by the street name and number. T05 T06 If this is a continuation of the name, the street and number must appear in sub-division 07 under positions 8-42 D6-7 Creditor account X1 O Ignored in Access Online number indicator D6-8 Creditor bank country A2 O ISO country code for the creditor s bank code D6-9 Filler X14 O Reserved 75

76 11.11 Data record 1, sub-division 07 Data record 1 Status Optional Fld Name Type in. Repeat 0 10,000 Stat Condition / Remark VR D7-1 Record code N1 M Fixed value 1 T01 D7-2 Sequence number N4 M Value 4-digit number Identical to data record 1 (data record 1, sub-division 01) that immediately precedes this record D7-3 Sub-division N2 M Fixed value 07 T07 D7-4 Continuation of the Creditor Address D7-5 Continuation of the Creditor Address X35 O Street and house number D7-6 Filler X10 O Reserved X35 O City, province/(sub-)state and country of the creditor D7-7 Description line 1 X35 O Information for the creditor, line 1 D7-8 Filler X6 O Reserved T05 T Data record 1, sub-division 08 Data record 1 Status Optional Fld Name Type in. Repeat 0 10,000 Stat Condition / Remark VR D8-1 Record code N1 M Fixed value 1 T01 D8-2 Sequence number N4 M Value 4-digit number Identical to data record 1 (data record 1, sub-division 01) that immediately precedes this record D8-3 Sub-division N2 M Fixed value 08 T07 D8-4 Description line 2 X35 O Information for the creditor, line 2 D8-5 Description line 3 X35 O Information for the creditor, line 3 D8-6 Description line 4 X35 O Information for the creditor, line 4 D8-7 Filler X16 O Reserved T05 T Data record 1, sub-division 09 Data record 1 Status Optional Fld Name Type in. Repeat 0 10,000 Stat Condition / Remark VR D9-1 Record code N1 M Fixed value 1 T01 D9-2 Sequence number N4 M Value 4-digit number Identical to data record 1 (data record 1, sub-division 01) that immediately precedes this record D9-3 Sub-division N2 M Fixed value 09 T07 D9-4 Bank instruction for the creditor bank X35 O Supported values: TELB : Inform creditor /TELB/ : Inform creditor PHOB : Inform creditor via telephone T05 T06 76

77 Data record 1 Status Optional Fld Name Type in. Repeat 0 10,000 Stat Condition / Remark VR /PHOB/ : Inform creditor via telephone INTC : Intracompany payment /INTC/ : Intracompany payment HOLD : Creditor must identify himself /HOLD/ : Creditor must identify himself CORT : Trade transaction /CORT/ : Trade transaction CORPTRAD : Trade transaction /CORPTRAD/ : Trade transaction Other values are ignored. D9-5 Bank instruction for X35 O Is ignored in Access Online the creditor s bank D9-6 Notification to the X35 O Is ignored in Access Online customer bank D9-7 Filler X16 O Reserved Data record 1, sub-division 10 Data record 1 Status Mandatory Fld Name Type in. Repeat 1 10,000 Stat Condition / Remark VR D10-1 Record code N1 M Fixed value 1 T01 D10-2 Sequence number N4 M Value 4-digit number Identical to data record 1 (data record 1, sub-division 01) that immediately precedes this record D10-3 Sub-division N2 M Fixed value 10 T07 D10-4 Notification to the customer s bank D10-5 Payment method code X35 O Is ignored in Access Online X3 M The following values are supported: CHC: Bank cheque / send to beneficiary CHD: Bank cheque / send to ordering customer CHA: Bank cheque / send to ordering bank TLX: Wire URG: Wire NOR: ACH EUR: ACH 3 blanks: ACH T05 T06 T15 If CDA, CDC, CDD: reject entire file For any other value: if a clearing code is delivered and this is RT or FW, then Wire. D10-6 Cost code X3 M The following values are supported: 77

78 Data record 1 Status Mandatory Fld Name Type in. Repeat 1 10,000 D10-7 Filler X1 O Reserved D10-8 Currency type costs account number Stat Condition / Remark VR OUR, costs borne by the Customer BEN, costs borne by the Creditor SHA, costs shared between the Customer and the Creditor A3 O Ignored in Access Online D10-9 Filler X6 O Reserved D10-10 Costs account number N12 O Ignored in Access Online D10-11 Filler X1 O Reserved D10-12 Country code creditor X2 O ISO country code of the creditor D10-13 Filler X55 O Reserved Data record 1, sub-division 11 through 13 As of 01/01/2006, the client s payment balance reports to the National Bank of Belgium no longer go via the banks. Because of this, as of 01/01/06 this data is no longer mandatory and this is ignored by Access Online Trailer record The trailer record is the last record of the logical file and contains information for file control. This record may only appear once in a logical file. Trailer record Status Mandatory Fld Name Type in. Repeat 1 Stat Condition / Remark VR T1 Record code N1 M Fixed value 9 T01 T2 Number of Data records N6 M Number of data record 1 records in this file (number of records with record code 1) T3 Number of Orders N6 M Number of payment orders in this file (number of records with record code 1 - sub-division 01) T4 Total Amount for the N15 M Total of the amounts (positions 35 to 49 for record code 1 subdivision Orders 01) not including the figures that exceed the length T5 Filler X100 O Reserved. T16 T17 T18 78

79 11.17 Validation rules Technical Validation In the event of a technical error in a validation rule for this file format, the entire file is rejected. Consequently, only the generic message is described. Status VR Rejection Message Field Rejected T01 File An error has been encountered while processing your file. The expected value of the field <%Field Name%> in the record type <%Record Type%>???, while the value received in the file is <%ActualValue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. various This is a generic message. An approximate specification of the incorrect record/field and line number is included. Rejected T02 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%application code%> is: 51, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T03 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%version code%> is '3', but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T04 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%version sub-code%> is '1', but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T05 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%sequence number> is 4N starting at 0001 but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T06 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%sequence number> is sequential starting at 0001, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T07 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%Subdivision of record identification%> is '##', but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. H5 H10 H14 Various Various Various Note: Values for ## are 01, 02, 03, 04, 05, 06, 07, 08, 09 or 10 Rejected T08 File An error has been encountered in record number <%recordnumber%> D1-4 79

80 Status VR Rejection Message Field while processing your file. The field <%order execution date%> contains an invalid date. The expected date format is DDMMYY, but the format received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T09 File An error has been encountered in record number <%recordnumber%> while processing your file. The field <%ISO currency code%> contains an invalid ISO currency code. The value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T10 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%Code for the Amount to be paid%> is 'C', but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T11 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%amount to be paid to beneficiary%> is greater than 0, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T12 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected format of the field <%amount to be paid to beneficiary%> is numeric <%expectedvalue%> but the format received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T13 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%account number to be debited%> is 12N, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T14 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%account number to be debited%> should not be blank, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T15 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%Method of payment code%> is either 'CHC,CHD,CHA,TLX,URG,NOR,EUR, or blank', but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T16 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%number of data records 1%> is the total number of data records 1 in the file, but the value received in the file is <%actualvalue%>. Please make the requisite D1-6 D1-8 D1-9 D1-9 D1-13 D1-13 D10-5 T2 80

81 Status VR Rejection Message Field modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T17 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%number of payment orders%> is the total of data records 1 in the file, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T18 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%total of amounts%> is the total of all amounts specified in data records 1 in the file, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. T3 T4 81

82 DTAus/zv Germany 82

83 12. DTAus 12.1 Introduction In Germany, a generic file format is used for offering payment orders to the bank. During the 1990s, the DTAus file format was defined for use on diskettes. This format specifies the use of variable extensions and sequential classification. The format can be used for different types of direct debits, as well as for payment orders. The only difference between the files with direct debits and payment orders is a simple indicator. Access Online does not support direct debits. The following chapters describe the German DTAus format at the detail level. The following subjects are dealt with: The file structure from a technical perspective; The technical checks and error messages; The logical checks and error messages External Documentation & Information Author Title / Source Version / Date Zentraler Kredietausschus Specification of Data Formats Version 2.5 ( June 10th, 2010 Specification_of_Data_Formats_2-5_FinalVersion_01.pdf) 12.2 Assumptions & Principles Number of Orders According to the official description, the file may contain a maximum of 9,999,999 data records. For delivery and processing via Access Online, the maximum Number of Orders is set at 10, Batch Orders The DTAus file format does not contain a specific indicator with which a batch can be designated. Access Online implicitly deals with the files submitted as batch orders, unless they are recognised as urgent files. After reading the file, it is possible to specify whether the batch file must be split into individual orders in Access Online. Batch Payments The Account number for the commissioning/paying party s debit account, field A09 in the header record, applies as the debit account number for all orders in the entire file submitted. This applies no matter what the contents of the Account number, field C11 in the data record, whose contents are ignored. Supplemental condition: the extension of the file submitted must not be: dte Urgent Payment Orders (Payments) In the DTAus file format, it is impossible to specify whether or not payment orders must be processed as urgent. The payment orders in the file submitted are handed separately as urgent payment orders if the extension of the file being submitted is dte. In that case, no batch is compiled. The Account number of the commissioning/paying party s debit account, field C11 in the data record, is 83

84 used; this results in single urgent orders. The content of field A09 in the header record, commissioning/paying party s debit account number, is ignored. Remark The urgent and batch orders are mutually exclusive Character set DTAus supports the letters A, O and U with umlaut and the special Eszett (Ringel S) character. Access Online does not support these characters; instead, it translates them into spaces. See Chapter 19 Character Sets for an overview of the characters that can be used in the DTAus file format File Structure The records in a DTAus file have a semi-fixed structure, with the exception of the data record. This depends on the quantity of information that is passed on with the order. The files does not contain any carriage returns and line feeds. The header and trailer records have a fixed length of 128 characters. The data records consist of various information extensions, each of which has a fixed length of 128 characters. In other words, the total size of the file is a multiple of 128. See the explanation in 13.4 Data record C, Variable Part for more information. Since the file structure is semi-fixed, an initial control cannot be performed without supplemental record and value checks. The position of the fields and the correct record length must be calculated during processing, based on the value in special fields. A logical DTAus file contains 3 record types: a header record, a data record and a trailer record. One or more logical files can be collected into a single physical file. Structure Record Type Repeat Field Value Header record A 1 A A02 A03 A A12 1 Data record C 1 10,000 C02 C Trailer record E 1 E E02 GK for Payments LK for Collection E 12.4 Error messages After the reading process in Access Online, the file is tested for both technical and logical contents. Depending on the nature of any error detected, a file may be entirely rejected. Depending on the conditions that specific fields must satisfy, orders that are incomplete may have to be correctly manually in Access Online. 84

85 Fixed values If a mandatory field does not contain the correct fixed value, a generic error message is displayed specifying the incorrect value and the expected value. The standard text for this is: An error has been encountered while processing your file. The expected value of the field [Field Name] in the [Record Type] is [Expected Value] but the value received in the file is [Actual Value]. Please make the requisite modification(s)and upload the file again. We have registered this error under ID: [Field reference number]. 85

86 13. DTAus Payments 13.1 Introduction This chapter describes the German DTAus format at this is used for offering payment orders, or Gutschriften Header record In the file, the header record is designated as type A. This is the first record of the logical file, which contains information regarding the commissioning party. This record type may only appear once in a logical file. Header record (type A) Status Mandatory Field Name Type in. Repeat 1 Stat. Condition / Remark VR A01 Record Length N4 M Fixed value0128 T01 A02 Record Type A1 M Fixed valuea T02 A03 Type Indicator A2 M Fixed valuegk (Gutschrift-Kunden) T03 A04 Bank Code N8 O Bank Code (Bankleitzahl) for the bank that maintains the account. Recipient of the file. See also field C10. The Value is implicitly in Access Online. A05 Bank Code N8 O Ignored in Access Online A06 Client Name X27 O Ignored in Access Online A07 Create Date N6 O Ignored in Access Online A08 File Identification Number N4 O Ignored in Access Online A09 Account number N10 C Value 10-digit number > 0 Account number of commissioning/paying party. Urgent: This Account number is not used. Orders are charged to the Account number in field C11. Batch: Orders are charged to this account number. The account number in field C11 is not used. See field C11. A10 Reference Number N10 O If 0, then NONREF is used as batch/set reference. T04 Number is passed on by the commissioning/paying party. This can be used for reconciliation. Urgent: The value is taken over in Set Name. Batch: The value is taken over in Batch Set Reference. A11a Space x15 O Reserved A11b Execution Date X8 O Desired Execution Date. Possible value: - Date in the format ddmmccyy - Spaces or zeroes; is interpreted as the current date during processing. A11c Space x15 O Reserved 86

87 Header record (type A) Status Mandatory Field Name Type in. Repeat 1 Stat. Condition / Remark VR A12 Currency code N1 M Fixed value1(=eur) T Data record C, Fixed Part The data record is designated as type C. The data record consists of a fixed and a variable part, which collectively comprises the order. Data record (type C) Fixed Part Status Field Name Type in. Mandatory Repeat 1 10,000 Stat. Validation / Remark VR C01 Record Length N4 M If no Variable Part is used, this field contains the actual technical length: 0187 If the Variable Part is used, this field contains the logical value of the length of the Information Extensions. This is the length of the Fixed Part of 0187 characters, plus a multiple of 29 characters for each section used up to the maximum of C02 Record Type A1 M Fixed valuec T07 C03 Bank Code N8 O Ignored in Access Online C04 Bank Code N8 O Code of the bank that maintains the Creditor account. See also field C05 T06 C05 Account number N10 M The account number (10 figures) of the Creditor, specified in Name in field C14a. C06 1 Label N13 O 01-01: Label Identification; must be 0 for DTA payments Identification 02-12: Reference number Payment; if 0, then NONREF is used 2 Reference as the customer reference. Payment 3 Filler 13-13: Filler = 0 Only the value from is used. C07a Payment Type N2 C Urgent: n.a. Batch: the value must be 51 or 53. Payment order (Gutschrift) Value 51: Überweisungs-Gutschrift (Commercial payment) Value 53: Lohn-, Gehalts-, Renten-Gutschrift (Salary or pension payment) C07b Payment Type N3 O As C07a = 51 then value = 000 or 888 As C07a = 53 then value = 000 or 888 T08 T in the event that the order amount is greater than 12,500 and the commissioning party is not a resident and the creditor is a resident. 000 In other situations. C08 Space X1 O Ignored in Access Online C09 Zeroes N11 O Reserved 87

88 Data record (type C) Fixed Part Status Field Name Type in. Mandatory Repeat 1 10,000 Stat. Validation / Remark VR C10 Bank Code N8 O Code of the bank (Bankleitzahl) that maintains the account to be debited. (Commissioning party). This value is not taken over; it is derived by Access Online. See fields A04 and C11. C11 Account number N10 C Value 10-digit number > 0 T10 Commissioning/paying party s account number (debit account). Urgent: Orders are charged to this account number. The account number in field A09 is not used. Batch: This Account number is not used. Orders are charged to the account number in field A09. See field A09. C12 Amount N11 M Value > 0 Amount in EUR, including 2 decimals, without decimal separator. T11 T12 C13 Space X3 O Reserved C14a Credit Party Name X27 O Creditor name. See field C04 and C05. C14b Space X8 O Reserved C15 Debit Party Name X27 O Name of the commissioning party. The value is not taken over; it is derived by Access Online. See field C10 and C11. C16 Information for the X27 O For example: an insurance or invoice number. Creditor C17a Currency code X1 M Fixed value1(=eur) T13 C17b Filler X2 O Reserved C18 Extension Indicator Number N2 M Value between 00 and 15 Number of Extensions in the Variable Part of the data record. 00 = no Extensions in the Variable Part are used. However, the technical length always contains (empty) fields up to and including the second section = number of Extensions used in the Variable Part T Data record C, Variable Part The fixed part and the variable part collectively comprise the data record; type C. The variable part is only used if the fixed part does not provide all the requisite information. A maximum of 6 variable parts may be used in the data record that can contain a total of 15 information extensions. Even if only 1 extension is filled, the entire section must be used. In other words, the record length in field C01 specifies how much of the record is used for relevant data. It does not contain the actual record length. If only Extension 01 is used, the value in C01=0216 and the technical record length

89 Remark In the event of refunds, the bank does not use the information from the variable parts. Thus, relevant information for the creditor must be stored in the fixed part of data record type C. See field C16. See field C19 and C20 for the description/value. This applies for the rest of the extensions. Data record (type C) Variable Part Status Optional See also par Extension types. Repeat Field Name Type in. Section 2 C19 Extension Type Indicator no. 01 n.a. Stat. Validation / Remark VR N2 C Specifies the type of information that the Payment information field contains: 01 = Creditor name 02 = Payment information 03 = Payment Initiator Name T15 If used C01> 0187 If C18 = 00 No validation. If C18 = 01-15, then the value is 01, 02 or 03. C20 Payment information no. 01 X27 O Contains information of the type specified in the related Extension Type Indicator C21 Extension Type N2 C If C18 = 02-15, then the value is 01, 02 or 03. T16 Indicator no. 02 C22 Payment X27 O Information no. 02 C23 Space X11 O Reserved Section 3 C24 Extension Type N2 C If C18 = 03-15, then the value is 01, 02 or 03. T17 Indicator no. 03 C25 Payment X27 O information no. 03 C26 Extension Type N2 C If C18 = 04-15, then the value is 01, 02 or 03. T18 Indicator no. 04 C27 Payment X27 O information no. 04 C28 Extension Type N2 C If C18 = 05-15, then the value is 01, 02 or 03. T19 Indicator no. 05 C29 Payment X27 O information no. 05 C30 Extension Type N2 C If C18 = 06-15, then the value is 01, 02 or 03. T20 Indicator no. 06 C31 Payment X27 O information no. 06 C32 Space X12 O Reserved Section 4 C33 Extension Type N2 C If C18 = 07-15, then the value is 01, 02 or 03. T21 Indicator no. 07 C34 Payment X27 O 89

90 Data record (type C) Variable Part Status Optional See also par Extension types. Repeat Field Name Type in. C35 C36 C37 C38 C39 C40 information no. 07 Extension Type Indicator no. 08 Payment information no. 08 Extension Type Indicator no. 09 Payment information no. 09 Extension Type Indicator no. 10 Payment information no. 10 n.a. Stat. Validation / Remark VR N2 C If C18 = 08-15, then the value is 01, 02 or 03. T22 X27 O N2 C If C18 = 09-15, then the value is 01, 02 or 03. T23 X27 O N2 C If C18 = 10-15, then the value is 01, 02 or 03. T24 X27 C41 Space X12 O Reserved Section 5 C42 C43 C44 C45 C46 C47 C48 C49 Extension Type Indicator no. 11 Payment information no. 11 Extension Type Indicator no. 12 Payment information no. 12 Extension Type Indicator no. 13 Payment information no. 13 Extension Type Indicator no. 14 Payment information no. 14 O N2 C If C18 = 11-15, then the value is 01, 02 or 03. T25 X27 O N2 C If C18 = 12-15, then the value is 01, 02 or 03. T26 X27 O N2 C If C18 = 13-15, then the value is 01, 02 or 03. T27 X27 O N2 C If C18 = 14-15, then the value is 01, 02 or 03. T28 X27 C50 Space X12 O Reserved Section 6 C51 C52 Extension Type Indicator no. 15 Payment information no. 15 O N2 C If C18 = 15-15, then the value is 01, 02 or 03. T29 X27 C53 Space X99 O Reserved O 90

91 Extension Types The use of the Extension Type must satisfy the following validation: Type, see Description Repeat Validation result C19 01 Creditor name Can only occur once T00 02 Payment information Cannot occur more than 13 times T00 03 Payment Initiator s Name Can only occur once T Trailer record E Record type E is the the logical file trailer record. It contains information for the execution of file and payments checks. This record type may only occur once in a logical file. Trailer record (type E) Status Mandatory Field Name Type in. Repeat 1 Stat. Validation / Remark VR E01 Record Length N4 M Fixed value0128 T30 E02 Record Type A1 M Fixed valuee T31 E03 Space X5 O Reserved E04 Number of Records N7 M Number of data records with type C T32 E05 Zeroes N13 O Reserved E06 Sum of Account numbers N17 M Sum of the Account numbers in field C05 T33 E07 Sum of Bank Codes N17 M Sum of the Bank Codes in field C04 T34 E08 Sum of Amounts N13 M Sum of the EUR amounts in field C12 T35 E09 Space X51 O Reserved 13.6 Validation rules Technical Validation A technical error in a validation rule for this file format results in rejection of the entire file. Thus, only the generic message is described. Status VR Rejection Message Field Rejected T00 File An error has been encountered while processing your file. The expected count of the extension type indicator is 1, 13 and 1 for values "01, "02" and "03, while the count received in the file is <%actual count%> for value "01" (Note: The value displayed here is the one that has an erroneous count. If multiple values have erroneous counts, they would also be displayed, separated by a, ). Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T01 File An error has been encountered while processing your file. The expected value of the field <%record length%> in the header record is "0128" but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T02 File An error has been encountered while processing your file. The expected A02 A01 91

92 Status VR Rejection Message Field value of the field <%record type %> in the header record is "A" but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T03 File An error has been encountered while processing your file. The expected value of the field <%label identifier%> in the header record is "GK" but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T04 File An error has been encountered while processing your file. The expected value of the field <%account number%> of the ordering party in the header record is a full 10 digits number greater than 0, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T05 File An error has been encountered while processing your file. The expected value of the field <% currency type %> in the header record is "1" but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T06 File An error has been encountered while processing your file. The expected value of the field <%record length%> in data record type C, Constant part, must include the extension fields, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T07 File An error has been encountered while processing your file. The expected value of the field <%record type%> in data record type C, Constant part, is "C" but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T08 File An error has been encountered while processing your file. The expected value of the field <%account number%> (beneficiary) in data record type C, Constant part, is a full 10 digits number greater than 0, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T09 File An error has been encountered while processing your file. The expected value of the field <%Payment type %> is "51" or "53" but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T10 File An error has been encountered while processing your file. The expected value of the field <%account number %> of the ordering party in data record type C, Constant part, is a full 10 digits number greater than 0 but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T11 File An error has been encountered while processing your file. The expected C12 A03 A09 A12 C01 C02 C05 C07a C11 92

93 Status VR Rejection Message Field value of the field <%amount %> in data record type C, Constant part, is greater than 0, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T12 File An error has been encountered while processing your file. The expected format of the field <%amount%> in data record type C, Constant part, is <%expectedvalue%> but the format received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T13 File An error has been encountered while processing your file. The expected value of the field <%currency type %> in data record type C, Constant part, is "1" but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T14 File An error has been encountered while processing your file. The expected value of the field <% extension indicator%> is between "00 and 15", but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T15 File An error has been encountered while processing your file. Since the value of the field extension indicator is between "01 and 15, the expected value of the field <%extension type indicator no. 01 %> is "01" or "02" or 03, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T16 File An error has been encountered while processing your file. Since the value of the field extension indicator is between "02 and 15, the expected value of the field <%extension type indicator no. 02 %> is "01" or "02" or 03, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T17 File An error has been encountered while processing your file. Since the value of the field extension indicator is between "03 and 15, the expected value of the field <%extension type indicator no. 03%> is "01" or "02" or 03, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T18 File An error has been encountered while processing your file. Since the value of the field extension indicator is between "04 and 15, the expected value of the field <%extension type indicator no. 04%> is "01" or "02" or "03", but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T19 File An error has been encountered while processing your file. Since the value of the field extension indicator is between "05 and 15, the expected value of the field <%extension type indicator no. 05%> is "01" or "02" or 03, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We C12 C17a C18 C19 C21 C24 C26 C28 93

94 Status VR Rejection Message Field have registered this error under ID: <%fileid%>. Rejected T20 File An error has been encountered while processing your file. Since the value of the field extension indicator is between "06 and 15, the expected value of the field <%extension type indicator no. 06%> is "01" or "02" or "03", but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T21 File An error has been encountered while processing your file. Since the value of the field extension indicator is between "07 and 15, the expected value of the field <%extension type indicator no. 07%> is "01" or "02" or 03, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T22 File An error has been encountered while processing your file. Since the value of the field extension indicator is between "08 and 15, the expected value of the field <%extension type indicator no. 08%> is "01" or "02" or "03", but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T23 File An error has been encountered while processing your file. Since the value of the field extension indicator is between "09 and 15, the expected value of the field <%extension type indicator no. 09%> is "01" or "02" or 03, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T24 File An error has been encountered while processing your file. Since the value of the field extension indicator is between "10 and 15, the expected value of the field <%extension type indicator no. 10%> is "01" or "02" or "03", but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T25 File An error has been encountered while processing your file. Since the value of the field extension indicator is between "11 and 15, the expected value of the field <%extension type indicator no. 11%> is "01" or "02" or 03, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T26 File An error has been encountered while processing your file. Since the value of the field extension indicator is between "12 and 15, the expected value of the field <%extension type indicator no. 12%> is "01" or "02" or "03", but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T27 File An error has been encountered while processing your file. Since the value of the field extension indicator is between "13 and 15, the expected value of the field <%extension type indicator no. 13%> is "01" or "02" or "03", but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. C30 C33 C35 C37 C39 C42 C44 C46 94

95 Status VR Rejection Message Field Rejected T28 File An error has been encountered while processing your file. Since the C48 value of the field extension indicator is between "14 and 15, the expected value of the field <%extension type indicator no. 14%> is "01" or "02" or 03, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T29 File An error has been encountered while processing your file. Since the C51 value of the field extension indicator is "15, the expected value of the field <%extension type indicator no. 15%> is "01" or "02" or 03, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T30 File An error has been encountered processing your file. The expected E01 value of the field <%record length%> in the trailer record is "0128" but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T31 File An error has been encountered processing your file. The expected E02 value of the field <%record type%> in the trailer record is "E" but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T32 File An error has been encountered while processing your file. There is an E04 inconsistency in the total number of data records with type C in the file and in the trailer record. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T33 File An error has been encountered while processing your file. There is an E06 inconsistency in the total number of beneficiary accounts in data records with type C, Constant part in the file and in the trailer record. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T34 File An error has been encountered while processing your file. There is an E07 inconsistency in the total number of bank codes in data record type C, Constant part, in the file and in the trailer record. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T35 File An error has been encountered while processing your file. There is an inconsistency in the sum of the amounts in data record type C, Constant part, in the file and in the trailer record. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. E08 95

96 14. DTAzv Foreign Payment Orders 14.1 Introduction This chapter describes the German DTAZV format that is used for offering foreign payment orders Scope This chapter describes the following aspects of the DTAZV file format: the technical file structure; the validation rules and error messages Payment versions The following versions are supported with the DTAZV format: Standard transfer (international) Urgent transfer (international) Bank Cheques 14.3 File format Each file contains: one header record Q with identification data Data records T, with data regarding the debiting (customer), crediting (creditor) and details regarding the payments. one trailer record with control data. Level Record Type Repeat File 1 Customer Header record Q 1 Payment order 1 9,999 Transaction record T 1 Reporting record M 1 Reporting record W 1 Trailer record Z 1 Data records M and W are ignored by Access Online if delivered by the customer Header record The header record is the first record of the logical file. It contains information regarding the commissioning client; the identification information. This record may only occur once in a logical file. Header record Q Status Mandatory T00 Fld Name Type in. Repeat 1 Stat Condition / Remark VR Q1 Record Length N4 M Record length of the header record. Must be 4 numeric positions. Must be >0. Q2 Record Type A1 M Fixed value Q T03 T01 T02 96

97 Header record Q Status Mandatory T00 Fld Name Type in. Repeat 1 Q3 Bank Code N8 O Ignored in Access Online. Stat Condition / Remark VR Q4 Client Number N10 O Reference passed on by the commissioning party/debtor. The reference is used as the set name in Access Online. If empty, the value from the Access Online upload profile is taken over as the set name. Q5 Name and address X35 O Ignored in Access Online. data * 4 Q6 Create Date N6 O Ignored in Access Online. Q7 File sequence N2 O Ignored in Access Online. number Q8 Execution Date N6 M Desired Execution Date. T04 Possible value: - Date in the format yymmdd - Spaces or zeroes; is interpreted as the current date during processing. Q9 Central Bank X1 O If Y, message L1 is displayed. Reporting Y/N Other values are ignored. Q10 Federal state Number N2 O Ignored in Access Online. Q11 Company Number / N8 O Ignored in Access Online. Bank Code Q12 Filler X68 O Reserved L Data record T Data record T Status Optional Fld Name Type in. Repeat Max 9,999 T1 Record Length N4 M Record length data record T. Stat Condition / Remark VR Must be 4 numeric positions. Must >0 are. T2 Record Type X1 M Fixed value T T03 T3 Bank Code N8 O Code of the bank (Bankleitzahl) that holds the customer account. T01 T02 The value is implicitly in Access Online. T4a Debit account A3 O ISO currency type for the customer account T05 Currency type T4b Debit account N10 M Customer account number. The order is charged to this account number. Value 10-digit number > 0. T06 T07 T5 Execution Date N6 O If filled, desired Execution Date for the payment order. T04 97

98 Data record T Status Optional Fld Name Type in. Repeat Max 9,999 Stat Condition / Remark VR Possible value: - Date in the format yymmdd - 6 zeroes; is interpreted as the current date during processing. T6 Costs Account Bank Code If T5 is not filled, the Execution Date is taken over from Q8. N8 O Ignored in Access Online T7a Costs Account A3 O Ignored in Access Online Currency Type T7b Costs Account N10 O Ignored in Access Online T8 BIC for the Creditor Bank X11 O BIC of the creditor s bank. If the Creditor s Bank is a German bank, the Bank Code (Bankleitzahl) can also be specified. T9a Creditor Bank A3 O ISO country code for the creditor s bank Country Code T9b Creditor Bank Address X35 * 4 O Name, Address and City data creditor s bank. Lines 1 and 2: Creditor bank name Line 3: Creditor bank street Line 4: Creditor bank City and Country. T10a Creditor Country A3 O ISO country code for the creditor Code T10b Creditor X35 * 4 O Name, Address and City data for the creditor/recipient of the cheque. Lines 1 and 2: Creditor name Line 3: Creditor Street Line 4: Creditor City and Country. T11 Order Mark X35 O Ignored in Access Online * 2 T12 Creditor account number X35 O/M Creditor IBAN or account number Mandatory for non-cheque payments. Ignored for cheque payments. T13 Currency type Order A3 M ISO currency type for the order amount T08 amount T14a Order amount N14 O Order amount before the decimal point (right justified) Must be 14 numeric positions T14b Order amount N3 M Order amount after the decimal point (left justified) Must be 3 numeric positions T15 Description line X35 O Information for the creditor, lines 1 through *4 T16 bank instruction 1 N2 O Instruction for the Creditor s Bank. The following values are supported: T09 T10 98

99 Data record T Status Optional Fld Name Type in. Repeat Max 9,999 Stat Condition / Remark VR 04 : HOLD 09 : PHONBEN 10 : TELB 11 : CORPTRAD 12 : INTC T17 bank instruction 2 N2 O See T16. Other values are ignored. T18 bank instruction 3 N2 O See T16. T17 is only read if T16 does not contain any values. If T17 is filled, ignore T18 and T19. T19 bank instruction 4 N2 O See T16. T18 is only read if T16 and T17 do not contain any values. If T18 is filled, ignore T19. T19 is only read if T16, T17 and T18 do not contain any values. T20 bank instruction X25 O Ignored in Access Online Details T21 Cost code N2 M The following values are supported: 00 : SHA 01 : OUR 02 : BEN Other values are ignored. T22 Payment Type N2 M Must be 2 numeric positions T11 The following values are supported: 00, 13 : Standard payment 10, 11 : Urgent payment 20, 21, 22, 23 : Bank Cheque (sent to the creditor) 30, 31, : Bank Cheque (sent to the customer) Other values result in rejection T23 Reference for the customer X27 O First 16 characters serve as the customer reference. Other characters are ignored. T24 Contact person X35 O Ignored in Access Online customer T25 CBR Reporting Code N1 O Ignored in Access Online T26 Filler X51 O Reserved T27 Extension ID N2 O Ignored in Access Online T12 99

100 14.6 Trailer record The trailer record is the last record in the logical file; it contains information for file control. This record may only occur once in a logical file. Trailer record Z Status Mandatory T00 Fld Name Type in. Repeat 1 Stat Condition / Remark VR Z1 Record Length N4 M Record length of the header record. Must be 4 numeric positions. Must be >0. Z2 Record Type X1 M Fixed value Z T03 Z3 Total Order Amount N15 M Sum of order amounts in this file (field T14a) T13 Z4 Number of T records N15 M Number of payment orders in this file (number of records with record code T) Z5 Filler X221 O Reserved T01 T02 T Validation rules Technical Validation In the event of a technical error in a validation rule for this file format, the entire file is rejected. Consequently, only the generic message is described. Status VR Rejection Message Field Rejected T00 File An error has been encountered while processing your file. A mandatory record <Record name> is missing. Please make the requisite Header Trailer modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T01 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%Length of record> is 4N, but the value received in the file is <%actualvalue%>. Q1 T1 Z1 Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T02 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%Length of record> should not be blank, but the value received in the file is Q1 T1 Z1 <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T03 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%Type of record> is '#', but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Q2 T2 Z2 Note: # can contain the value Q, T or Z Rejected T04 File An error has been encountered in record number <%recordnumber%> while processing your file. The field <%execution date of file%> contains an invalid date. The expected date format is YYMMDD, but the format received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error Q8 T5 100

101 Status VR Rejection Message Field under ID: <%fileid%>. Rejected T05 File An error has been encountered in record number <%recordnumber%> while processing your file. The value of the field <%ISO currency code> associated with the Debit account number is not found to be available in the database. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T06 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%account number to be debited%> is 10N, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T07 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%account number to be debited%> should not be blank, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T08 File An error has been encountered in record number <%recordnumber%> while processing your file. The field <%ISO code or currency payable%> contains an invalid ISO currency code. The value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T09 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%amount%> is 14N, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T10 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%amount%> is 3N, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T11 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%Code for type of payment%> is 2N, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T12 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%Code for type of payment%> is '00,13,10,11,20, 21, 22, 23,30, 31, 32, 33', but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T13 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%total of amounts%> is the total of all amounts mentioned in the file, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error T4a T4b T4b T13 T14a T14b T22 T22 Z3 101

102 Status VR Rejection Message Field under ID: <%fileid%>. Rejected T14 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%number of T data records%> is the total number of T data records in the file, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Z Logical Validation Status VR Message Field Entered Messages serve as notification. Orders are executable Incomplete L1 ABN AMRO Access Online does not have the capability to report data on payment made to non-residents (Z1 form) to the Bundesbank on your behalf. Please make sure to deliver that information via a different channel. Notices require further action. Orders can only be executed after correction. Q9 Rejected Messages serve as notification. Orders are not executable. 102

103 CFONB France 103

104 15. CONFB 15.1 Introduction The CFONB format is the French file format for national payments. The format was developed by CFONB, the Committee Français d Organisation et de Normalisation Bancaires, in External Documentation & Information Author Title / Source Date CFONB Remises Informatisées d Ordres de Virements au format 160c April 2004 ( %20Remises%20informatis%C3%A9es%20d%20ordres%20de%20paiement%20160c_2004.pdf) CFONB Remises Informatisées d Ordres de Prélèvement au format 160c ( _clientele_160c_version%20finale_octobre_2006.pdf) October 2006 Remark The documentation specified above only relates to the ABN AMRO Access Online application in which these formats are supported Assumptions & Principles Standard upload profile In Access Online, the upload profile for the CFONB format further can further specify how the upload file must be processed. The description of the CONFB in this chapter is based on an upload profile with standard settings. If other settings are used in the upload profile, this can affect the validation/control and the messages described in this chapter. The standard upload profile contains a mandatory batch reference specifically for CFONB transfers; this reference is only used if the submitted file does not contain any batch reference(s) Number of Orders For the delivery and processing via Access Online, the maximum Number of Orders per file is set at 9, Batch Orders The files submitted contain one or more batches. The format contains a specific indicator with which a batch can be designated. Access Online deals with the files submitted as batch orders. After the file is read, within Access Online it is possible to specify whether or not the batch file must be split into individual orders. Batch Payments The Account number of the commissioning /paying party debit account, field D4 in the header record, is used as the debit account number for all orders in the batch. A payment can be a normal payment (Virement Ordinaire) or a treasury payment (Virement de Trésorerie). Batch Direct debits The Account number of the commissioning/collecting party credit account, field D4 in the header record, is used as the credit account number for all orders in the batch. A Direct debit can be a standard direct debit 104

105 (Prélèvement Ordinaire) or an accelerated direct debit (Prélèvement Accéléré) File Structure Technical File CFONB has a fixed line length of 160 positions. Each line concludes with a return; a carriage return and line feed character (hexadecimal x0d x0a), referred to in this description as CRLF Character set See chapter 19 Character Sets for an overview of the characters that can be used in the CFONB file format Logical File A CFONB file contains 1-n batches. A batch consists of a Header record, followed by a maximum of 9,999 payment orders, which are then followed by a Totals record. A payment order consists of one Payment record1, and possibly an optional Payment record2. Payment record2 only appears if the description contains more than 31 positions. Level Record Type Repeat Batch 1-n Customer Header record 03 1 Payment order 1 9,999 Transaction record Transaction record Totals record

106 16. CFONB Transfer 16.1 Introduction This section describes the French CFONB format used to offer payment orders (Ordres de Virements) Header record This is the first record of a batch. It contains information regarding the commissioning (paying) party. This record type may only appear once in a batch. Header record First record of a batch Status Repeat Mandatory 1 x per Batch Field Name Type Stat Condition / Remark VR A Record code N2 M Fixed value 03 T01 B1 Transaction code N2 M Standard value = ordinary transfer 76 = treasury payment B2 Filler X8 O Spaces B3 Submitter identification X6 O C1-1 Filler X1 O Space C1-2 Filler X6 O Spaces C1-3 Desired processing N5 O Desired Execution Date of payment order. date Possible value: - Date with the layout ddmmy - dd = day - mm = month - y = last position year - 5 zeroes; is interpreted as the current date during processing. C2 Customer name X24 M Must be filled. T01 T02 T03 Access Online retrieves data from its own administration. D1-1 Batch reference X7 O Reference is passed on by the commissioning party/debtor. Can be used for reconciliation. If empty, the value is taken over from the Access Online upload profile, plus a 4-position sequence number. D1-2 Filler X17 O Spaces D2-1 Filler X2 O Spaces D2-2 Currency type A1 M Standard value E E = Euro D2-3 Filler X5 M Spaces D3 Bank Sector code N5 M Contains the code of the office (Code Guichet) that holds the customer account. May contain zeroes. D4 Customer Account X11 M Account number must be held in EUR. Number Customer account number, without check digit (clé RIB). Payment orders are charged to this account number. E Customer identification X16 O Code that identifies the customer. Not mandatory. T01 T04 T05 106

107 Header record First record of a batch Status Mandatory Repeat 1 x per Batch Field Name Type Stat Condition / Remark VR F Filler X31 O Spaces G1 Bank code N5 M Contains the code (Code Banque) of the bank that T06 maintains the customer s account. May not contain any zeroes G2 Filler X6 O Spaces 16.3 Transaction record1 Transaction record1 is the first record of a payment and contains information regarding the creditor. Transaction record 1 of 2 First record of the transaction. Status Repeat Mandatory 1x per Transaction Field Name Type Stat Condition / Remark VR A Record code N2 M Fixed value 06 T01 B1 Transaction code N2 M Value must be identical to B1 in Header record T01 B2 Filler X8 O Spaces B3 Submitter identification X6 O Value must be identical to B3 in Header record T01 C1 Transaction reference X12 O Reference number assigned by the Customer. Can be used for reconciliation. If empty, NONREF is used. C2 Creditor name X24 M Must be filled. T03 D1 Creditor Bank Name X24 C Creditor name bank. D2 Central Bank reporting, see 16.6 If Central bank reporting is mandatory, the entry is: - SIREN code of the resident customer, 9 positions - Name of the creditor bank (15 positions) X8 C If Central bank reporting is mandatory, the entry is: - Declaration type 1 position: value = 1-3-position economic activity code, see appendix 21 Economic activity code (CFONB) for the possible values - 3-position ISO Country Code D3 Bank Sector code N5 M Contains the code of the bank office (Code Guichet) that D4 Creditor account number maintains the creditor account. May contain zeroes. X11 M The account number must be linked to the FR country code via the Bank code. Creditor account number, without check digit (clé RIB) Payment orders are charged to this account number. E Amount N16 M Amount in Euro cents, without decimal point, right justified with leading zeroes. Value > 0. F Description X31 O Contains space for the first 31 positions of the description G1 Bank code N5 M Contains the code of the bank (Code Banque) that holds G2 Filler X6 O Spaces the creditor s account. May not contain zeroes T04 T05 T07 T06 107

108 16.4 Transaction record2 Transaction record2 only appears if the description contains more than 31 positions. Transaction record 1 of 2 Second record of the transaction. Status Repeat Optional 1x per Transaction Field Name Type Stat Condition / Remark VR A Record code N2 M Fixed value 07 T01 B1 Transaction code N2 M Value must be identical to B1 in Header record T08 B2 Filler X8 O Spaces B3 Submitter identification X6 O Value must be identical to B3 in Header record T08 C1 Transaction reference X12 O Value must be identical to C1 in Transaction record1 T08 C2 Creditor name X24 M Value must be identical to C2 in Transaction record1 T08 D1 Creditor Bank Name X24 C Value must be identical to D1 in Transaction record1 T08 D2 Filler X8 O Spaces D3 Bank Sector code N5 M Value must be identical to D3 in Transaction record1 T08 D4 Creditor account number X11 M Value must be identical to D4 in Transaction record1 T08 E Amount N16 M Must contain the value 0 T09 F Description X31 M If the description contains more than 31 positions, this contains the second part of the description. Must be filled. G1 Bank code N5 M Value must be identical to G1 in Transaction record1 T08 G2 Filler X6 O Spaces T01 108

109 16.5 Total record Total record Last record of a batch Status Mandatory Repeat 1x per Batch Field Name Type Stat Condition / Remark VR A Record code N2 M Fixed value 08 T01 B1 Transaction code N2 M Value must be identical to B1 in Header record T10 B2 Filler X8 O B3 Submitter identification X6 O Value must be identical to B3 in Header record T10 C1 Filler X12 O Spaces C2 Filler X24 O Spaces D1 Filler X24 O Spaces D2 Filler X8 O Spaces D3 Filler X5 O Spaces D4 Filler X11 O Spaces E Total batch amount N16 M Amount in Euro cents, without a decimal point, right T11 justified with leading zeroes. Value > 0. F Filler X31 O Spaces G1 Filler X5 O Spaces G2 Filler X6 O Spaces 16.6 Central Bank Reporting In France, residents must report payments of EUR 50, or more to the French Central Bank under the following conditions: From French Euro account to French account Creditor is a resident of the SEPA zone Creditor is a non-resident of the SEPA The debtor is a resident of France 1. - CBR is mandatory for customer The debtor is a non-resident of France. - - zone 1 Including the French overseas territories GF, MQ, GP, RE or MC 109

110 17. CFONB Direct debit 17.1 Introduction This section describes the French CFONB format used to offer direct debit orders (Ordres de Prélèvements) Header record This is the first record of a batch. It contains information regarding the commissioning (creditor) party. This record type may only appear once in a batch. Header record First record of a batch Status Repeat Mandatory 1 x per Batch Field Name Type Stat Condition / Remark VR A Record code N2 M Fixed value 03 T01 B1 Transaction code N2 M Standard value = standard direct debit 85 = accelerated direct debit B2 Filler X8 O Spaces B3 Creditor identification X6 M Numéro National d'emetteur (NNE) Assigned by the bank; this identifies the creditor in France. C1-1 Filler X7 O Space C1-2 Desired processing N5 M Desired Execution Date of the direct debit mandate. date Possible value: - Date with the layout ddmmy - dd = day - mm = month - y = last position year C2 Customer name X24 M Must be filled. T01 T01 T02 T03 Access Online retrieves data from its own administration. D1-1 Batch reference X7 O Reference is passed on by the commissioning party/debtor. Can be used for reconciliation. If empty, the value is taken over from the Access Online upload profile, plus a 4-position sequence number. D1-2 Filler X17 O Spaces D2-1 Filler X2 O Spaces D2 Filler X8 M Spaces D3 Bank Sector code N5 M Contains the code of the bank office (Code Guichet) that holds the customer s account. May contain zeroes. D4 Customer Account X11 M Account must be a EURO account. Number Customer account number, without check digit (clé RIB). Payment orders are charged to this account number. E Filler X16 O Spaces F Filler X31 O Spaces G1 Bank code N5 M Contains the code of the bank (Code Banque) that maintains the customer account. T04 T05 T06 110

111 Header record First record of a batch Status Mandatory Repeat 1 x per Batch Field Name Type Stat Condition / Remark VR May not contain zeroes. G2 Filler X6 O Spaces 17.3 Transaction record1 The transaction record1 is the first record of a direct debit and contains information regarding the paying party. Transaction record 1 of 2 First record of the transaction. Status Mandatory Repeat 1x per Transaction Field Name Type Stat Condition / Remark VR A Record code N2 M Fixed value 06 T01 B1 Transaction code N2 M Value must be identical to B1 in Header record T01 B2 Filler X8 O Spaces B3 Submitter identification X6 O Value must be identical to B3 in Header record T01 C1 Transaction reference X12 O Reference number assigned by the customer. Can be used for reconciliation. If empty, NONREF is used. C2 Debtor name X24 M Must be filled. T03 D1 Name bank debtor X24 O Name of the paying bank. D2 Filler X8 O Spaces D3 Bank Sector code N5 M Contains the code of the bank office (Code Guichet) that T04 holds the debtor s account. May contain zeroes. D4 Debtor account number X11 M Account number must be linked to the FR country code via T05 the Bank code. Debtor account number, without check digit (clé RIB). Payment orders are charged to this account number. E Amount N16 M Amount in Euro cents, without decimal point, right justified T07 with leading zeroes. Value > 0. F Description X31 O Contains space for the first 31 positions of the description. G1 Bank code N5 M Contains the code of the bank (Code Banque) that holds T06 the debtor s account. May not contain zeroes. G2 Filler X6 O Spaces 17.4 Transaction record2 Transactions record 2 only appears if the description contains more than 31 positions. Transaction record 2 of 2 Second record of the transaction. Status Repeat Optional 1x per Transaction Field Name Type Stat Condition / Remark VR 111

112 A Record code N2 M Fixed value 07 T01 B1 Transaction code N2 M Value must be identical to B1 in Header record T08 B2 Filler X8 O Spaces B3 Submitter identification X6 O Value must be identical to B3 in Header record T08 C1 Transaction reference X12 O Value must be identical to C1 in Transaction record1 T08 C2 Creditor name X24 M Value must be identical to C2 in Transaction record1 T08 D1 Creditor Bank Name X24 C Value must be identical to D1 in Transaction record1 T08 D2 Filler X8 O Spaces D3 Bank Sector code N5 M Value must be identical to D3 in Transaction record1 T08 D4 Creditor account X11 M Value must be identical to D4 in Transaction record1 T08 number E Amount N16 M Must contain the value 0 T09 F Description X31 M If the description contains more than 31 positions, this T01 record contains the second part of the description. Must be filled. G1 Bank code N5 M Value must be identical to G1 in Transaction record1 T08 G2 Filler X6 O Spaces 17.5 Total record Total record Last record of a batch Status Mandatory Repeat 1x per Batch Field Name Type Stat Condition / Remark VR A Record code N2 M Fixed value 08 T01 B1 Transaction code N2 M Value must be identical to B1 in Header record T10 B2 Filler X8 O B3 Submitter identification X6 O Value must be identical to B3 in Header record T10 C1 Filler X12 O Spaces C2 Filler X24 O Spaces D1 Filler X24 O Spaces D2 Filler X8 O Spaces D3 Filler X5 O Spaces D4 Filler X11 O Spaces E Total batch amount N16 M Amount in Euro cents, without a decimal point, right T11 justified with leading zeroes. Value > 0. F Filler X31 O Spaces G1 Filler X5 O Spaces G2 Filler X6 O Spaces 112

113 18. CFONB Validation rules applies In the event of a technical error in a validation rule for the CFONB file formats, the entire file is rejected. Status VR Rejection Message Field Rejected T01 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%Field No.%> in a <%Record Type%> is <%Expected Values%>, but the value received A, B1, B3, D2-2,F in the file is <%actual Value%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T02 File An error has been encountered in record number <%recordnumber%> while processing your file. The field <%FieldNr%> in <%RecordType%> C1-2, C1-3 contains an invalid date. The expected date format is numeric DDMMY but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T03 File An error has been encountered in record number <%recordnumber%> C2 while processing your file. The field <%FieldNr%> in <%RecordType%> must not be empty. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T04 File An error has been encountered in record number <%recordnumber%> D3 while processing your file. The expected value of the field <D3:%originator bank branch code%> in a batch header record is a full 5-digit number, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T05 File An error has been encountered in record number <%recordnumber%> D4 while processing your file. The expected value of the field <D4:%debit account number%> in a batch header record is a full 11-character field, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T06 File An error has been encountered in record number <%recordnumber%> G1 while processing your file. The expected value of the field <G1:%originator bank code%> in a batch header record is a full 5-digit number greater than 0, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T07 File An error has been encountered in record number <%recordnumber%> E while processing your file. The expected value of the field <E:%amount%> in a transaction is greater than 0, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T08 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <%FieldNr%> in the second record must be the same as that provided in the first record of the transaction <%recordnumber%>, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. B1, B3, C1, C2, D1, D3, D4, G1 113

114 Status VR Rejection Message Field Rejected T09 File An error has been encountered in record number <%recordnumber%> E while processing your file. The expected value of the field <E:%amount%> in the second record of the transaction is zero, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T10 File An error has been encountered in record number <%recordnumber%> B1, B3 while processing your file. The expected value of the field <%FieldNr%> in a batch trailer record must be the same as that provided in the corresponding batch header record <%recordnumber%>, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. Rejected T11 File An error has been encountered in record number <%recordnumber%> while processing your file. The expected value of the field <E:%total amount%> in a batch trailer record is the total of all transaction amounts included in the batch, but the value received in the file is <%actualvalue%>. Please make the requisite modification(s) and upload the file again. We have registered this error under ID: <%fileid%>. E 114

115 Appendices 115

116 19. Character Sets Character Chara cter ASCII value ClieOp03 BTL91 AOL CIRI AOL DTAus AOL New line LF 10 Return CR 13 CFONB AOL Space 32 Exclamation point! 33 Double quotes 34 Hash sign # 35 Dollar sign $ 36 Percent sign % 37 Ampersand & 38 Apostrophe 39 Open parentheses ( 40 Close parentheses ) 41 Asterisk * 42 Plus sign + 43 Comma, 44 Minus sign - 45 Point. 46 Forward slash / 47 Figures Colon : 58 Semi-colon ; 59 Less than < 60 Equal sign = 61 Greater than > 62 Question mark? 63 At 64 Alphabetic capital letters A Z Backslash \ 92 Circumflex ^ 94 Alphabetic small letters a z Curly brace open { 123 Vertical line 124 Curly brace close } 125 Tilde ~ 126 SEPA AOL Remark Access Online translates characters in submitted files that do not occur in the character set for the format in question into an equivalent character or a space. The user receives a notice that this has occurred. 116

117 20. ISO Codes In various file formats, the ISO standard is used for the codes for countries and currencies. As support and as a reference to the other parts of this document, this section lists the most frequently used country and currency codes. For the integral and most current overviews, please go to the appropriate ISO url: Country code: Currency code: ISO Country Code (truncated list) Code Country SEPA AD Andorra AT Austria AU BA Australia Bosnia & Herzegovina BE Belgium BG Bulgaria CA Canada CH Switzerland CY Cyprus CZ The Czech Republic DE Germany DK Denmark EE Estonia ES Spain 3 FI Finland FR France 1 GB Great Britain 4 GI Gibraltar GR Greece HK HR Hong Kong Croatia HU Hungary IE Ireland IN India IS Iceland IT Italy Code Country SEPA LI Liechtenstein LT Lithuania LU Luxemburg LV Latvia ME MK Montenegro Macedonia MT Malta MC Monaco NL The Netherlands NO Norway NZ New Zealand PL Poland PT Portugal 2 RO Romania RS RU Serbia Russian Federation SE Sweden SI Slovenia SK Slovakia SM TN TR US ZA San Marino Tunisia Turkey United States South Africa 1. including Guadeloupe, Martinique, French Guyana and Réunion 2. including the Azores and Madeira 3. including the Canary Islands, Ceuta and Melilla 4. including Gibraltar and NorthIerland 117

118 20.2 ISO Currency Code (Truncated list) AED VAE-Dirham HKD Hong Kong dollar OMR Omanian rial ANG Antillean guilders HRK Croatian kuna PEN New Peruvian sol AOA Angolese kwanza HUF Hungarian forint PHP Philippine peso ARS Argentine peso IDR Indonesian rupee PKR Pakistani rupee AUD Australian dollar ILS New Israeli shekel PLN Polish zloty AWG Aruban guilders INR Indian rupee QAR Qatar rial BDT Bengalese taka IQD Iraqi dinar RON Rumanian leu BGN New Bulgarian lev IRR Iranian rial RUB Russian rouble BHD Bahraini dinar ISK Icelandic crown SAR Saudi-Arabian riyal BND Brunesian dollar JMD Jamaican dollar SDG Sudanese pound BRL Brazilian real JOD Jordanian dinar SEK Swedish crown BSD Bahamanain dollar JPY Japanese yen SGD Singapore dollar BWP Botswanan pula KES Kenyan shilling SRD Surinam dollar CAD Canadian dollar KRW South Korean won SZL Swaziland lilangeni CHF Swiss frank KWD Kuwaiti dinar THB Thai baht CLP Chilean peso KZT Kazakh tenge TND Tunisian dinar CNY Chinese yuan LBP Lebanese pound TOP Tongan pa'anga COP Colombian peso LKR Sri Lankan rupee TRY New Turkish lira CSD Serbian dinar LTL Lithuanian litas TTD Trinidad and Tobago dollar CVE Cape Verdian escudo LVL Latvian lats TWD New Taiwanese dollar CZK Czech crown LYD Libyan dinar TZS Tanzanian shilling DKK Danish crown MAD Moroccan dirham UAH Ukrainian grivna DZD Algerian dinar MGA Malagan ariary UGX Ugandan shilling EEK Estonian crown MTL Maltese lira USD American dollar EGP Egyptian pond MUR Mauritanian rupee UYU Uruguayan peso ETB Ethiopian birr MWK Malawian kwacha VEF Venezuelan Bolivar EUR Euro MXN Mexican peso VND Vietnamese dong FJD Fiji dollar MYR Malaysian ringgit WST Samoan tala GBP British pound sterling NAD Namibian dollar ZAR South African rand GEL Georgian lari NGN Nigerian naira ZMK Zambian kwacha GHS Ghanesian cedi NOK Norwegian crown ZWD Zimbabwe dollar GIP Gibraltar pound NZD New-Zealand dollar 118

119 21. Economic activity code (CFONB) Code Description (French) Description (English) E01 Biens (marchandises générales, avitaillement, travail à Goods (merchandises, supplies, tailoring and trade) façon et négoce) E02 Services de transport (maritimes, aériens et autres) Transport services E03 Services informatiques et de communication ICT services E04 Services de construction Construction services E05 Redevances et droits de licence, acquisition / cession et Royalties, licenses and ownership rights utilisation de droits d exploiter des ressources, de droits de franchise et d autres droits de propriété E06 Services liés au tourisme Tourist services E07 Autres services (y compris services aux entreprises et aux professionnels) Miscellaneous services (including services to companies and professionals) E08 Revenus d investissement (y compris dividendes et intérêts) Investments revenues (dividends and interest) E09 Transferts courants (y compris l envoi de fonds, salaires et rémunérations, pensions) Transfers (Including remittances, salaries, remunerations, pensions) E10 Investissements intra-groupes (participations, prêts, dépôts et règlements intervenant dans le cadre de procédures de Intra-company investments (shareholdings, loans, deposits, netting) netting) E11 Désinvestissements intra-groupes (participations, prêts, dépôts et règlements intervenant dans le cadre de Intra-company disinvestments (participations, loans, deposits, netting) procédures de netting) E12 Opérations sur actifs immobiliers Real estate operations E13 Titres de dettes et actions (Valeurs mobilières de placement Securities et titres immobilisés) à l exclusion des participations E14 Produits financiers dérivés Derivatives E15 Prêts et emprunts hors-groupe Loans (excluding intra-company loans) 119