OfficeNet Direct data import and export formats - ABN … · OfficeNet Direct data import and...

OfficeNet Direct data import and export formats

CLIEOP 03

ABN AMRO BTL91

SWIFT MT940/MT942

Version 1.11

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________OfficeNet Direct Format Book

2

� ABN AMRO Bank N.V. 2005 All rights reserved. With the exception of the conditions specified in or based on the 1912 Copyright Act, no part of this publication may be reproduced and/or made public by print, photocopy, microfilm, or any other means whatsoever, nor may the document be stored in a data storage system without the express written permission of ABN AMRO Bank N.V.

___________________________________________________________________ABN AMRO Bank N.V.


3

Getting started with OfficeNet Direct formats This document was written for people who define specifications for importing or exporting data to the ABN AMRO OfficeNet Direct electronic banking product. Although OfficeNet Direct can be used as a stand-alone product, it can also be used as a communication module for other ABN AMRO electronic banking products. OfficeNet Direct is supplied as a module with OfficeNet Extra (for Windows), for instance. It can also be used as a communication module with a financial package, allowing you to send Payments to ABN AMRO Bank and retrieve reporting information from ABN AMRO Bank. Should you have questions and/or remarks regarding this document, please contact the Electronic Banking Service Desk. You can also address questions to the following department: ABN AMRO Bank N.V. Afdeling MCBS S&TP T.a.v. Beheer formaten Postbus 283 1000 EA Amsterdam PAC AA2444 e-mail: [email protected] Although the information in this document has been compiled with the utmost care, we can accept no liability for any errors or inaccuracies. We reserve the right to modify the (technical) data of the products mentioned in this document at any time without prior notification. We accept no liability from any third parties who may use the information presented in this document. ABN AMRO Bank N.V.

___________________________________________________________________ABN AMRO Bank N.V.


4

Contents 1. A BRIEF REVIEW........................................................................................................................5

2. HOW PAYMENTS ARE PROCESSED IN OFFICENET DIRECT........................................6

3. CLIEOP03......................................................................................................................................7 3.1 GENERAL .................................................................................................................................7 3.2 ORDER TYPES...........................................................................................................................7 3.3 OBLIGATORY FIELDS IN OFFICENET DIRECT............................................................................9 3.4 CHECKS/VALIDATIONS...........................................................................................................10 3.5 DEVIATIONS IN ADMINISTRATIVE PROCESSING ......................................................................11 3.6 CLIEOP03 FILE SECURITY ......................................................................................................12

4. ABN AMRO BTL91 ....................................................................................................................13 4.1 GENERAL ...............................................................................................................................13 4.2 ORDER TYPES.........................................................................................................................13 4.3 OBLIGATORY FIELDS IN OFFICENET DIRECT..........................................................................14 4.4 DEVIATIONS IN ADMINISTRATIVE PROCESSING ......................................................................14 4.5 CRITERIA EU PAYMENT (IBAN/BIC) .....................................................................................14 4.6 BTL91 FILE SECURITY ...........................................................................................................16

5. SWIFT MT940.............................................................................................................................17 5.1 GENERAL ...............................................................................................................................17 5.2 OFFICENET DIRECT MT940 EXPORT FILE..............................................................................18 5.3 FORMAT DESCRIPTION ...........................................................................................................19 5.4 SUPPORTED CHARACTERS ......................................................................................................22

6. SWIFT MT942.............................................................................................................................23 6.1 GENERAL ...............................................................................................................................23 6.2 OFFICENET DIRECT MT942 EXPORT FILE..............................................................................24 6.3 FORMAT DESCRIPTION ...........................................................................................................24 6.4 SUPPORTED CHARACTERS ......................................................................................................27

APPENDIX A OVERVIEW OF FIGURES AND TABLES ......................................................28

APPENDIX B EXPLANATION OF TAG USAGE IN MT940 ..................................................29

APPENDIX C EXPLANATION OF TAG USAGE IN MT942 .................................................32

___________________________________________________________________ABN AMRO Bank N.V.


5

1. A brief review

OfficeNet Direct supports the ClieOp03, ABN AMRO BTL91, SWIFT MT940 and SWIFT MT942 formats. The format descriptions in this document make it possible to define specifications for the import of data from OfficeNet Direct and the export of data to OfficeNet Direct. This document contains the data characteristics that must be considered in these data. The deviations from official format descriptions issued by the suppliers of data in the various formats are also handled in this document. By importing, we mean integrating a file with Payments created using another program in OfficeNet Direct. By exporting, we mean saving the balance and transaction data in a file in such a way that other programs can process it. OfficeNet Direct supports four formats: - ClieOp03 - ABN AMRO BTL91 - SWIFT MT940 - SWIFT MT942 The formats were developed to facilitate electronic data processing (payments or account statements). ClieOp03 is an Interpay format for submitting domestic payment orders and direct debits euros. The BTL91 format is an ABN AMRO format that supports the electronic delivery of foreign payment orders. The SWIFT (Society for Worldwide Interbank Financial Telecommunication) formats make it possible to export account data. The formats in OfficeNet Direct differ from the official format descriptions while in some cases other validations apply. This is necessary to support administrative processing in the ABN AMRO systems. This document describes the specific characteristics for correct data delivery via OfficeNet Direct using ClieOp03 and ABN AMRO BTL91. The file layout for the SWIFT MT940 and MT 942 formats as used for the presentation of account information is also explained.

___________________________________________________________________ABN AMRO Bank N.V.


6

2. How payments are processed in OfficeNet Direct

This section contains a brief explanation of how payments that comply with the ClieOp03 and ABN AMRO BTL91 are processed in OfficeNet Direct. For a detailed description, please see the help texts supplied with the OfficeNet Direct package. To view help texts, press function key F1. Payments in ClieOp03 and ABN AMRO BTL91 format can be created in a financial package or one of the OfficeNet Extra modules. Once created, the payments must be stored in a file. OfficeNet Direct can automatically process this file if: - the file complies with the format descriptions - the file is placed in the directory specified in the OfficeNet Direct settings. The locations of the directories are specified in the OfficeNet Direct settings, which can be opened via 'Settings\Conversions\OfficeNet Direct '. Once the order files have been placed in these directories, these files will be processed in OfficeNet Direct. The payments they contain can be signed and sent to the bank. The process is shown in the figure below. Figure 1. Creating and processing payments using OfficeNet Direct Note The extension given to the file is of no importance. As long as the files comply with the format descriptions, they can be automatically processed by OfficeNet Direct. During processing, the payments in the file are checked to determine whether they can be processed by ABN AMRO Bank. OfficeNet Direct may discover that payments cannot be signed and sent to the bank because they do not comply with certain requirements. This is indicated via the file status in the screen 'Orders\Imported' in OfficeNet Direct. Payments that cannot be imported are displayed in the screen 'Orders\Rejected by import'. Additional information on the status of payments and rejected order files can be found in the help texts for this screen. The information on the ClieOp03 and ABN AMRO BTL91 formats in this document is based on the standard installation of OfficeNet Direct. This assumption plays a role in determining the settings for the directories in which the order files are placed.

Create payments in financial package or module

Save file in specified directory

Start OfficeNet Direct and select Payments, Imported

Sign the payments and send them to ABN AMRO Bank

___________________________________________________________________ABN AMRO Bank N.V.


7

3. ClieOp03

The peculiarities described in this chapter regarding use of the ClieOp03 format with OfficeNet Direct are based on the official ClieOp03 format description issued by Interpay . The ClieOp03-format description can be downloaded from www.interpay.nl 3.1 General

Batch payments: pure/impure Postbank payments A Postbank order (transfer to or direct debit from a Postbank account) is pure if the customer has verified that the Postbank account holder’s name and address correspond to the account data as registered with the Postbank. If so, these files can be imported without name and address data. The Postbank performs no further name/number check on ‘pure’ payments. To enable the import of pure payments in OfficeNet Direct, you must specify in the transaction type field of the ClieOp03 file that the order must be processed as pure. 3.2 Order types

The checks performed by OfficeNet Direct and the manner in which the payments must be delivered for processing are determined by: ��the directory in which the payments are placed; ��the individual order and batch settings in OfficeNet Direct; ��any specifications included in the order file. These items are explained below. Urgent payments and non-urgent payments The way in which payments are processed depends on the directory in which the payments are placed for processing by OfficeNet Direct: - Directory 'installation directory'\ClieOp\: processing of all domestic payments delivered in ClieOp03 format, except urgent payments. The applicable order types are non-urgent (bankgiro), acceptgiro collection form and batch. - Directory 'installation directory'\ClieOp\Spoed: processing of all urgent domestic payments. Individual or batch When importing into OfficeNet Direct, you can specify whether the payments in the import file must be processed collectively (batch processing) or individually. To do this, select ‘Settings’, followed by ‘General’. To process imported payments as a batch, activate the ‘Treat orders as batch’ checkbox.

___________________________________________________________________ABN AMRO Bank N.V.


8

The total amount of payments processed as a batch is reported on the account statement. To process the imported payments individually, do not activate the checkbox. Note! - This setting only applies when OfficeNet Direct is used with a financial package. If

the Domestic Payments module of OfficeNet Extra is used to create payments, the type of processing (batch, urgent, non-urgent or acceptgiro collection form) determines how the payments are processed in OfficeNet Direct.

- Direct debits are always processed in batches. Specifications included in the order file The settings described above can be used to make a distinction between urgent payments and non-urgent payments and between individual and batch payments. The distinction between normal (bankgiro) and acceptgiro collection form payments is indicated by specifying the payment reference and the form code of the acceptgiro collection form in the ClieOp03 file. This approach makes it possible to retain the reference of the acceptgiro collection form in the payment process. To have OfficeNet Direct process an order as an acceptgiro collection form, place the two-digit form code at the end of the filler of info code 100, in the first position following the account number. The form code is specified in the white bar in the lower right-hand corner of the acceptgiro collection form . If applicable, the payment reference for an acceptgiro collection form can be placed in info code 0150. Direct debit payments can be identified by transaction type. These payments must always be delivered in a separate batch. Neither of the codes described here deviate from the official ClieOp03 format description.

___________________________________________________________________ABN AMRO Bank N.V.


9

3.3 Obligatory fields in OfficeNet Direct

The following table indicates what fields require an obligatory entry in the ClieOp03 file. The fields in bold show the deviations from the Interpay format description. If the field is included in a multi-field data layout, we also specify the data layout to which the field belongs. Table 1. ClieOp03 and the obligatory fields in OfficeNet Direct ClieOp03 field OfficeNet Direct Delivery currency (Batch header info) Obligatory File creation date (Batch header info) Obligatory Number of items (Batch trailer info) Obligatory Batch sequence number (Batch header info) Obligatory* Amount (Transaction info) Obligatory File identification (File header info) Obligatory Duplicate code (File header info) Optional Sender identification (File header info) Optional Info code (All info) Obligatory Beneficiary’s name Obligatory ** Customer name (Customer info) Obligatory Name and address code (Customer info) Obligatory (value 1) Beneficiary’s acct. no. (Transaction info) Obligatory Principal’s acct. no. (Transaction info) Obligatory Customer acct. no. (Batch header info) Obligatory Test code (Customer info) Obligatory (value P) Total amount (Batch trailer info) Obligatory Total Acct. nos. (Batch trailer info) Obligatory Transaction group (Batch header info) Obligatory Transaction type (Transaction info) Obligatory Variant code (All info) Obligatory Beneficiary’s town Obligatory***

* When importing one batch in a file, zeroes will suffice. ** With the exception of batch processing. *** With the exception of batch processing and urgent payments.

___________________________________________________________________ABN AMRO Bank N.V.


10

3.4 Checks/validations

Although OfficeNet Direct does not support certain fields when processing a ClieOp03 file, it does check these fields upon import of a ClieOp03 file. The following table gives an overview of these fields and states any peculiarities. If the field is included in a multi-field data layout, we also specify the data layout to which the field belongs. Table 2. ClieOp03 fields not supported by OfficeNet Direct ClieOp03 field Peculiarities in OfficeNet Direct Duplicate code (File header info)

This code indicates whether the file is a duplicate of a file previously delivered for processing. You cannot use this field when importing a ClieOp03 file into OfficeNet Direct. Enter the value 1 (only copy).

Name and address (Customer info)

When processing a ClieOp03 file via OfficeNet Direct, it is not possible to receive the name and address data for impure Postbankaccount numbers as registered with the Interpay using the ‘Name and address code’ (Customer info) field. Enter the value 1 (Name and address not required).

Test code (Customer info)

This field is not applicable when processing a ClieOp03 file via OfficeNet Direct. If you enter the value ‘T’ (test) here, this item is ignored in the bank systems during processing and payments in the file delivered are processed normally. For ‘Test code’, enter the value P (production).

Supported characters When importing a ClieOp03 file, OfficeNet Direct checks whether the characters in the file being delivered can be processed by the ABN AMRO systems. The following characters are supported: - capital letters; - digits; - the punctuation marks space ( ), period (.), asterisk (*), slash (/), at (@), minus

sign/hyphen (-), percentage (%), ampersand (&) and equal sign (=). OfficeNet Direct replaces all other characters with spaces. We therefore recommend that you use supported characters only. Fillers: only spaces If the ‘fillers’ contain characters other than spaces when a ClieOp03 file is imported into OfficeNet Direct, the file cannot be imported. This does not apply to: − the payment reference and the form code of the acceptgiro collection form (see

section 3.2) − use of a Des Hash code to check the file (see section 3.6) − alphanumeric characters can be placed in the first line of the ClieOp03 file.

___________________________________________________________________ABN AMRO Bank N.V.


11

3.5 Deviations in administrative processing

In ClieOp03, a limited number of positions is available for each field. In OfficeNet Direct too, the number of available positions per field is subject to a maximum. The number of available positions in OfficeNet Direct can deviate from the number specified in the ClieOp03 format description. This is due to the file handling method in the ABN AMRO systems. OfficeNet Direct checks the number of positions in the fields when it imports the ClieOp03 file. Any changes that may be made in these fields are indicated in the status assigned to the imported file. OfficeNet Direct also indicates what changes are made. The following table gives the number of positions permitted for each field, split out into order type where applicable. If the field is included in a multi-field data layout, we also specify the data layout to which the field belongs. Table 3. Number of available positions in OfficeNet Direct ClieOp03 field OfficeNet Direct Beneficiary’s name (35 positions) 24 positions (name) Principal’s name (35 positions) 24 positions (name) Beneficiary’s town (35 positions) 20 positions (town)

18 positions (town) for urgent payments Principal’s town (35 positions) 20 positions (town) Payment reference (16 positions) Fixed description (4 * 32 positions) Description (4 * 32 positions)

3 * 32 positions (description, see explanation below)

When the ClieOp03 file is imported in OfficeNet Direct, the fields ‘Payment reference’, ‘Fixed description’ and ‘Description’ are entered in the ‘Description’ field insofar as the number of positions permits. This field contains 3 lines of 32 positions each, with the fields ‘Payment reference’, ‘Fixed description’ and ‘Description’ being entered in that order. A space is inserted between the fields within the available number of positions in OfficeNet Direct. Any characters in excess of the maximum number of positions are dropped.

___________________________________________________________________ABN AMRO Bank N.V.


12

3.6 ClieOp03 file security

A Des Hash code is added to files containing completed payments created in the Domestic Payments or Direct Debits module of OfficeNet Extra. A Des Hash code is a number used for verification purposes and is the result of a calculation that includes a number of variables from the file. The Des Hash code is calculated in compliance with the standards of the Netherlands Bankers’ Association’s Des Hash formula, version 7.1. The Des Hash code is added in the filler of the ‘File trailer info’ in ClieOp03 files. Adding the Des Hash code increases file security because the Des Hash code generated by the OfficeNet Extra modules can be compared with the Des Hash code calculated by OfficeNet Direct for the imported file. The Des Hash code is added to the order file and specified in an overview when it is placed by the modules in a directory for delivery to the bank. The overview also specifies which payments are ready to send. The information in the overview can be printed. After the file has been imported in OfficeNet Direct, the Des Hash code calculated for the file can be viewed by selecting 'Orders\Imported' and then placing the mouse cursor over the lock shown in the overview. The information in this overview can also be printed in OfficeNet Direct by selecting 'Reports\Import reports'. Double-click the desired order line to display a detailed import report that can be printed.

___________________________________________________________________ABN AMRO Bank N.V.


13

4. ABN AMRO BTL91

The details described in this chapter regarding the use of the ABN AMRO BTL91 format in combination with OfficeNet Direct are based on the official Foreign Payments ABN AMRO BTL91 format description (abbreviated as BTL91). This format was developed by the ABN AMRO International Funds Transfers department (May 1998 version). 4.1 General

Place foreign payments for import in OfficeNet Direct in the directory 'installatiedirectory'\BTL91, regardless of the order type. 4.2 Order types

The following foreign order 'types' can be imported in OfficeNet Direct in BTL91 format:

♦ ABN AMRO Foreign payment Normal ♦ ABN AMRO Foreign payment Urgent ♦ ABN AMRO Cheque ♦ ABN AMRO EU-payment(IBAN/BIC)

The codes required to define Foreign payments or Cheque payments are available in the BTL91 format description. There is no code available for an EU-payment(IBAN/BIC). For composing an EU-payment(IBAN/BIC) see paragraph 4.5.

___________________________________________________________________ABN AMRO Bank N.V.


14

4.3 Obligatory fields in OfficeNet Direct

The following table shows the fields that deviate from the ABN AMRO BTL91 format description. This depends in part on the order type. Table 4. BTL91 and obligatory fields in OfficeNet Direct Obligatory (Yes/No) Field Description BTL91 Normal Urgent Cheque 22- 3 Beneficiary’s account no. No No No No 22- 6 Beneficiary’s town Yes Yes Yes Yes 22- 8 Beneficiary’s country No Yes Yes Yes 23- 4 Name of beneficiary’s bank No No No No 23- 6 Town of beneficiary’s bank No Yes Yes Yes

For the specifications of an EU-payment see paragraph 4.5. 4.4 Deviations in administrative processing

The BTL91 format was developed for direct electronic delivery of foreign payment orders to ABN AMRO Bank. At a later stage, the format was also included in OfficeNet Direct. The required modifications are described in this section. In BTL91, a limited number of positions is available for each record. In OfficeNet Direct too, the number of available positions per field is subject to a maximum. The number of available positions in OfficeNet Direct can deviate from the number specified in the BTL91 format description. Any changes that may be made in these fields are indicated in the status assigned to the imported file. OfficeNet Direct also indicates what changes are made. The following table gives the number of positions permitted for each field. Table 5. Number of available positions in OfficeNet Direct ABN AMRO BTL91 record OfficeNet Direct 21-19 Payment reference 1 (40 positions) 21-20 Payment reference 2 (40 positions)

70 positions (payment type) see explanation below

The field ‘Payment type’ in OfficeNet Direct contains a total of 70 positions. If both record 21-19 and record 21-20 are filled, a space is placed between the two fields within the available number of positions in OfficeNet Direct. Any characters in the file in excess of the maximum number of positions are dropped. Beneficiary’s account number In record 22-3, Beneficiary’s account number, a BTL91 file for import in OfficeNet Direct may not contain any separators, hyphens, etc. This can lead to incorrect import of the account numbers, which will impede correct order processing. Supported characters When importing a BTL91 file, OfficeNet checks whether the characters in the file being delivered can be processed by the ABN AMRO systems. The following characters are supported: - capital letters; - digits;

___________________________________________________________________ABN AMRO Bank N.V.


15

- the punctuation marks space ( ), period (.), asterisk (*), slash (/), at (@), minus sign/hyphen (-), percentage (%), ampersand (&) and equal sign (=).

OfficeNet Direct replaces all other characters with spaces. We therefore recommend that you use supported characters only.

4.5 Criteria EU-payment (IBAN/BIC)

With BTL91 you can import an EU-payment (IBAN/BIC) in OfficeNet. An EU-payment (IBAN/BIC) has to comply with the following conditions to be processed against domestic charges: • The currency of the amount is in euro's; • The amount of EU-payment is maximum 50.000 euro; • The charges for processing the payment will be shared between principal and

beneficiary;�• The correct and complete accountnumber of the beneficiary in IBAN-format; • The correct and complete BIC(SWIFT- address) of the bank of the beneficiary; • The country of the beneficiary bank is one of the EU-countries; • No supplementary instructions �

For the BTL91-payments record layout, which does not change this leads to the corresponding heading description: Tabel 6 Specifice Payment records EU-Payment(IBAN/BIC) Heading Name Startposition Alfa/

numeric Contents

21-5 ISO CURRENCY CODE OF THE PAYMENT

20 3a EUR

21-6 AMOUNT OF THE PAYMENT 23 15n 3d <=000000050000000 21-8 CODE-COSTS-DOMESTIC BANK 46 1n 1 21-9 CODE-COSTS-CORRESPONDENT 47 1n 3 22-3 BENEFICIARY-ACCOUNTNUMBR 7 34a ‘International Bank

Account Number (IBAN)’

23-3 BANK-BENEFICIARY-SWIFTADRES 7 11a

‘complete and correct BIC’

23-7 BANK BENEFICIARY-LANDCODE-ISO 146 2a ‘EU-country code’

Supported characters When importing a BTL91 file, OfficeNet checks whether the characters in the file being delivered can be processed by the ABN AMRO systems. The following characters are supported: - capital letters; - digits; - the punctuation marks space ( ), period (.), asterisk (*), slash (/), at (@), minus

sign/hyphen (-), percentage (%), ampersand (&) and equal sign (=). OfficeNet Direct replaces all other characters with spaces. We therefore recommend that you use supported characters only.

___________________________________________________________________ABN AMRO Bank N.V.


16

4.6 BTL91 file security

A Des Hash code is added to files containing completed payments created in the Foreign Payments module of OfficeNet Extra. A Des Hash code is a number used for verification purposes and is the result of a calculation that includes a number of variables from the file. The Des Hash code is calculated in compliance with the standards of the Netherlands Bankers’ Association’s Des Hash formula, version 7.1. The Des Hash code is added in tag 41-4 (trailer record) of BTL91 files. If a financial package that does not calculate the Des Hash code is used to create the BTL91 file, special software designed for this purpose can be used to add a Des Hash code to the file. Adding the Des Hash code increases file security because the Des Hash code generated by the financial package or the Foreign Payments module of OfficeNet Extra can be compared with the Des Hash code generated by OfficeNet Direct for the imported file. Addition of a Des Hash code to the file is optional. To import BTL91 files without a Des Hash code in OfficeNet Direct, activate the option ‘Accept foreign payments without hash’ under ‘Settings/Advanced’. Only the main user is authorised to activate this option. If the payments are created using the Foreign Payments module of OfficeNet Extra, the Des Hash code added to the order file is specified in the overview of payments ready to send. The information in the overview can be printed. After the file has been imported in OfficeNet Direct, the Des Hash code calculated for the file can be viewed by selecting 'Payments\Imported' and then placing the mouse cursor over the lock shown in the overview. The information in this overview can also be printed in OfficeNet Direct by selecting 'Reports\Import reports'. Double-click the desired order line to display a detailed import report that can be printed.

___________________________________________________________________ABN AMRO Bank N.V.


17

5. SWIFT MT940

OfficeNet Direct uses the SWIFT MT940 format (abbreviated as MT940) to export account information to other packages. In the previous chapters (ClieOp03 and ABN AMRO BTL91), we limited ourselves to the differences compared with the official format descriptions. This chapter offers a total overview of the SWIFT MT940 format as used by OfficeNet Direct to report account data. 5.1 General

The structure of the information in MT940 files is based on the SWIFT format. SWIFT (Society for Worldwide Interbank Financial Telecommunication) is an international, electronic communication network used by banks throughout the world for data exchange. The SWIFT format is the universal standardised format that has been developed for this purpose.

An MT940 Customer Statement Message, which can be compared to a statement of account, has the following structure: Message header Transaction identification Account number Sequence number Opening balance Transactions Transaction data (0 - n) Transaction description Closing balance

(if available)

Message description Message trailer The file consists of one or more messages. Each message consists of a Message Header, followed by a Customer Statement Message (MT940), which in turn is followed by a Message Trailer. The format description uses specific abbreviations. The definitions for these abbreviations are shown in the following table. Table 7. Definition of abbreviations used in MT940 Abbreviation Definition V Compulsory O Optional, tag level [ ] Optional, field level X Alphanumerical N Numerical A Alphabetical 15 NUM Amount consisting of no more than 15 characters,

including a decimal point Figure maximum number of positions; variable length Underlined figure fixed number of positions; fixed length

___________________________________________________________________ABN AMRO Bank N.V.


18

Each record is identified by a ‘tag’ and consists of a ’tag’, a message and a carriage return/line feed. The records can vary in length. The layout of records of the same tag may vary. A record can be sub-divided into fields. A field may never begin with CRLF or ':'. A line in the file may never begin with '-'. Account statement numbering The account statement numbering in OfficeNet Direct differs from the numbering on printed account statements. Appendix B describes the numbering system used in MT940. Transaction codes We recommend that you use the transaction code field included in tag 61 (‘Type of transaction’ sub-field 6, see table 10) as a check in your financial software. When exporting with MT940, a three-digit transaction code is included in tag 61. This transaction code is used internally by ABN AMRO Bank. In older export formats, this was a three-letter combination. Some accounting packages used the letter combination to check for messages regarding sent payment payments. This is not possible in MT940. We recommend not using the three-digit transaction codes as a reference because they can change. 5.2 OfficeNet Direct MT940 export file

The directory in which OfficeNet Direct Export places the account statements is specified under ‘Settings/Conversions’. The default directory is ‘…\Exports\MT940’ under the OfficeNet Extra installation directory. The standard name for the file is also specified here, i.e. ‘MT940.STA’. When creating MT940 files, you can indicate whether the new files should be appended or the existing files be overwritten. The default setting is ‘Append’. This setting appends the information obtained during communication with the bank computer to the existing files, thus increasing their size. If ‘Overwrite’ is activated, the files are replaced with newly obtained information after each communication session. The old file is overwritten, making it unavailable for future use. It is very important that the new information is integrated after each communication session in this case. NOTE: If a date is entered in the ‘Resend date’ field under ‘Manual communication’, information from this date forward can be retrieved again from the bank. Information is available up to 45 days into the past, allowing retrieval of lost information for integration in the package. NOTE: • The files always contain all account numbers for which reports are received in

OfficeNet Direct under the conditions of the electronic banking contract. • If the financial package can only integrate one day of reports, the ‘Overwrite’

option must be activated. A communication session must be established with OfficeNet Direct each day to retrieve reports (otherwise, a file containing multi-day reports might be created).

• OfficeNet Direct cannot be used to create an export file specifically for a given period or account.

___________________________________________________________________ABN AMRO Bank N.V.


19

5.3 Format description

The format description for MT940 Customer Statement Message is given below. Table 8 shows the layout of the MT940 message, which starts with a SWIFT Message Header and ends with a SWIFT Message Trailer. The specifications are given in table 9. Table 10 gives a specification of the Customer Statement Message Text per ‘tag’. An explanation of tag use is given in Appendix B. Table 8. Layout of MT940 Customer Statement Message V/O Tag Field Name Picture Once per message: V :20: Transaction Reference Number (TRN) 16X O :21: Reference to related message/transaction 16X V :25: Account identification 35X V :28: or

:28C: Statement number/sequence number 5N[/2N]

5N/(/3N) V :60m: Opening balance (:60F: or :60M:) A6N3A 15 NUM Transaction group, can be repeated as long as max. length of the message allows: O :61: Statement Line 6N1A 15 NUM 4X6X O :86: Description of transaction 6 * 65X Once per message: V :62m: Closing balance (:62F: or :62M:) A6N3A 15 NUM O :64: Closing available balance 1A6N3A 15 NUM Balance group, can be repeated as long as max. length of the message allows: O :65: Forward available balance 1A6N3A 15 NUM Once per message: O :86: Description of message 6 * 65X

NOTE: If there is too much information to store (send) in a single SWIFT message, one or more additional sub-messages are created and an interim balance is used for consolidation (:60M: and :62M:). ABN AMRO Bank uses the SWIFT format for reporting data only. When exporting account data from OfficeNet Direct, a SWIFT message header and a SWIFT Message trailer are added.

___________________________________________________________________ABN AMRO Bank N.V.


20

The values of these items are: • SWIFT Message Headers

ABNANL2A 940 ABNANL2A

• SWIFT Message Trailer -

The SWIFT addresses in the header can come from another bank. We recommend not using the information in the Message Header as a reference/identification for reconciliation purposes. Table 9. Layout of MT940 Message Header/Trailer V/O Description Picture Value V Header part 1 (Swift address of

sender) 12X ABNANL2A or other

CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' V Header part 2 Message type 3N 940 CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' V Header part 3 (Swift address of

receiver) 12X ABNANL2A

CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' MT940 Customer statement Message

V Trailer 1X - CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' Table 10. Layout of MT940 Customer Statement Message per Tag V/O Tag Description Picture Value V 20 Tag 20 4X :20: V 1 Transaction Reference Number (TRN) 16X CS2 (end of line) 2X CRLF = X'0D25' or ‘0D0A' O 21 Tag 21 4X :21: V 1 Ref to related mess/trans 16X CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' V 25 Tag 25 4X :25: V 1 Account number 35X CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' V 28 or

28C Tag 28 or Tag 28C

4X or 5X

:28: or :28C:

V 1 Statement Number 5N O 2 Sequence number (Page number) [/2N] With Tag 28 O 2 Sequence number (Page number) [/3N] With Tag 28C CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' V 60m Tag 60m Opening balance 5X :60m : m = F or M V 1 Debit-credit indication 1A C or D V 2 Date (last entry data) 6N Format YYMMDD V 3 Currrency code (ISO currency code) 3A V 4 Opening balance or interim balance 15 NUM CS2 (end of line) 2X CRLF = X'0D25' or '0D0A'

___________________________________________________________________ABN AMRO Bank N.V.


21

Continuation of Table 10. Layout of MT940 Customer Statement Message per Tag V/O Tag Description Picture Value NO 61 Tag 61 Statement line 4X :61: transaction line V 1 Value date 6N Format YYMMDD O 2 Entry date (book date) [4N] Format MMDD V 3 Debit-credit indication 2A 'C' ,'D', 'C ', 'D , 'RC' or

'RD' O 4 Funds code 1A 3rd pos. currency code V 5 Transaction amount 15 NUM V 6 Type of transaction 4X O 7 Reference for 'account owner' 16X O 8 Account Servicing bank ref [//16X] CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' O 9 Further reference/info [34X] CS2 (end of line) [2X] CRLF = X'0D25' or '0D0A' NO 86 Tag 86 4X :86: O Description at transaction level 6 * 65X Max. 6 lines, each

followed by CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' V 62m Tag 62m (booked funds) 5X :62m: m = F or M V 1 Debit-credit indication 1A C or D V 2 Closing balance entry date 6N format YYMMDD V 3 ISO currency code 3A V 4 Closing balance / interim balance 15 NUM CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' O 64 Tag 64 (Available funds) 4X :64: V 1 Debit-credit indication 1A C or D V 2 Closing balance date 6N Same as date in 62m V 3 ISO currency code 3A V 4 Available closing balance 15 NUM CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' NO 65 Tag 65 Forward Available Balance 4X :65: V 1 Debit-credit indication 1A C or D V 2 Date 6N V 3 ISO currency code 3A V 4 Available forward balance 15 NUM CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' O 86 Tag 86 4X :86: O Description at message level 6*65X Max. 6 lines each

followed by CS2 (end of line) 2X CRLF = X'0D25' or '0D0A'

___________________________________________________________________ABN AMRO Bank N.V.


22

5.4 Supported characters

The following characters are supported: - capital letters; - digits; - the characters: space ( ), period (.),open parenthesis ( and close parenthesis ), hyphen (-), slash (/), less than (<), plus (+), ampersand (&), dollar sign ($), asterisk (*), semi-colon (;), percent sign (%), at sign (@), equal sign (=), double quote (“), and back-slash (\).

___________________________________________________________________ABN AMRO Bank N.V.


23

6. SWIFT MT942

OfficeNet Direct uses the SWIFT MT942 format (abbreviated as MT942) to export intraday information to other packages. The sections on ClieOp03 and ABN AMRO BTL91 focused on deviations from the official format descriptions. Here, as in the previous section, however, a complete overview is given of how the SWIFT MT942 format is used by OfficeNet Direct for intraday message reporting. 6.1 General

The structure of the information in MT942 files is based on the SWIFT format. SWIFT (Society for Worldwide Interbank Financial Telecommunication) is an international, electronic communication network used by banks throughout the world for data exchange. The SWIFT format is the universal standardised format that has been developed for this purpose.

An MT942 Interim Transaction Report, which can be compared to a statement of account, has the following structure:

Message header Transaction identification Account number Sequence number Floor limit indicator debit/credit Transactions Transaction data (0 – n) Transaction description Number and sum of debit/credit

transactions

Message description Message trailer

The file consists of one or more messages. Each message consists of a Message Header, followed by an Interim Transaction Report (MT942), which in turn is followed by a message trailer.

The format description uses specific abbreviations. The definitions for these abbreviations are shown in the following table. Table 11. Definition of abbreviations used in MT942 Abbreviation Definition V Compulsory O Optional, tag level [ ] Optional, field level X Alphanumerical N Numerical A Alphabetical 15 NUM Amount consisting of no more than 15 characters,

including a decimal point Figure maximum number of positions; variable length Underlined figure fixed number of positions; fixed length

___________________________________________________________________ABN AMRO Bank N.V.


24

Each record is identified by a ‘tag’ and consists of a ’tag’, a message and a carriage return/line feed. The records can vary in length. The layout of records of the same tag may vary. A record can be sub-divided into fields. A field may never begin with CRLF or ':'. A line in the file may never begin with '-'. 6.2 OfficeNet Direct MT942 export file

The directory in which OfficeNet Direct Export places intraday reports is specified under ‘Settings/Conversions’. The default directory is ‘…\Exports\MT942’ under the OfficeNet Extra installation directory. The standard name for the file is also specified here, i.e. ‘MT942.STA’. When creating MT942 files, you can indicate whether the new files should be appended or the existing files be overwritten. The default setting is ‘Append’. This setting appends the information obtained during communication with the bank computer to the existing files, thus increasing their size. If ‘Overwrite’ is activated, the files are replaced with newly obtained information after each communication session. The old file is overwritten, making it unavailable for future use. It is very important that the new information is integrated after each communication session in this case. NOTE: OfficeNet Direct cannot be used to create an export file specifically for a given period or account.

6.3 Format description

The format description for MT942 Interim Transaction Report is given below. Table 14 shows the layout of the MT942 message, which starts with a SWIFT Message Header and ends with a SWIFT Message Trailer. The specifications are given in table 15. Table 16 gives a specification of the Customer Statement Message per Tag. An explanation of tag use is given Appendix C.

___________________________________________________________________ABN AMRO Bank N.V.


25

Table 12. Layout of MT942 Interim Transaction Report V/O Tag Field Name Picture Once per message: V :20: Transaction Reference Number (TRN) 16X O :21: Reference to related message/transaction 16X V :25: Account identification 35X V :28C: Statement Number/Sequence Number 5N[/3N] V :34F: Floor limit indicator debit/credit 3A [1A] 15 NUM O :34F: Floor limit indicator credit 3A 1A 15 NUM V :13: Date/time indicator 10N Transaction group, can be repeated as long as max. length of the message allows: O :61: Statement line 6N1A 15 NUM 4X6X O :86: Description of transaction 6 * 65X Once per message: O :90D: Numbers and sum of debit entries 5N3A 15 NUM O :90C: Numbers and sum of credit entries 5N3A 15 NUM O :86: Description of message 6 * 65X ABN AMRO Bank uses the SWIFT format for reporting data only. When exporting account data from OfficeNet Direct, a SWIFT message header and a SWIFT Message trailer are added. The values of these items are:

• SWIFT Message Headers ABNANL2A 942 ABNANL2A

• SWIFT Message Trailer -

The SWIFT addresses in the header can come from another bank. We recommend not using the information in the Message Header as a reference/identification for reconciliation purposes. Table 13. Layout of MT942 Message Header/Trailer V/O Description Picture Value V Header part 1 (Swift address of

sender) 12X ABNANL2A or other

CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' V Header part 2 Message type 3N 942 CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' V Header part 3 (Swift address of

receiver) 12X ABNANL2A

CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' MT942 Interim Transaction Report

V Trailer 1X - CS2 (end of line) 2X CRLF = X'0D25' or '0D0A'

___________________________________________________________________ABN AMRO Bank N.V.


26

Table 14. Layout of MT942 Interim Transaction Report per Tag V/O Tag Description Picture Value V 20 Tag 20 4X :20: V 1 Transaction Reference Number (TRN) 16X CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' O 21 Tag 21 4X :21: V 1 Related Reference 16X CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' V 25 Tag 25 4X :25: V 1 Account Identification 35X (CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' V 28C Tag 28C 5X :28C: V 1 Statement Number 5N O 2 Sequence Number [/3N] (CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' V 34F Tag 34F 5X :34F: Floor limit indicator (first occurrence) V 1 Currency code 3A O 2 Debit-credit indicator [1A] D V 3 Amount 15 NUM (CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' O 34F Tag 34F 5X :34F: Floor limit indicator (sec occurrence) V 1 Currency code 3A V 2 Debit-credit indicator 1A C V 3 Amount 15 NUM (CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' V 13 Tag 13 4X :13: V 1 Date/Time indicator 10N Format YYMMDDHHMM (CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' NO 61 Tag 61 Statement line 4X :61: V 1 Value date 6N Format YYMMDD O 2 Entry date 4N Format MMDD V 3 Debit-credit indicator 2A C , D , RC of RD O 4 Funds code 1A 3rd char. of Currency code V 5 Amount 15 NUM V 6 Transaction Type 4X O 7 Reference for ‘account owner’ 16X O 8 Account Servicing bank ref [//16X] (CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' O 9 Further reference/info [34X] (CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' NO 86 Tag 86 4X :86: 1 Description of transaction 6 * 65X Max. 6 lines, each foll. by: (CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' O 90D Tag 90D 5X :90D: V 1 Number of debit entries 5N V 2 Currency code 3A V 3 Total amount of debit entries 15 NUM (CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' O 90C Tag 90C 5X :90C: V 1 Number of credit entries 5N V 2 Currency code 3A V 3 Total amount of credit entries 15 NUM (CS2 (end of line) 2X CRLF = X'0D25' or '0D0A' O 86 Tag 86 4X :86: O Description of message 6 * 65X Max. 6 lines, each foll. by: (CS2 (end of line) 2X CRLF = X'0D25' or '0D0A'

___________________________________________________________________ABN AMRO Bank N.V.


27

6.4 Supported characters

The following characters are supported: - capital letters; - digits; - the characters: space ( ), period (.),open parenthesis ( and close parenthesis ), hyphen (-), slash (/), less than (<), plus (+), ampersand (&), dollar sign ($), asterisk (*), semi-colon (;), percent sign (%), at sign (@), equal sign (=), double quote (“), and back-slash (\).

___________________________________________________________________ABN AMRO Bank N.V.


28

Appendix A Overview of figures and tables

Table 14. List of figures Figure Description Page

1 Creating and processing payments using OfficeNet Direct 6 Table 15. List of tables Table Description Page

1 ClieOp03 and the obligatory fields in OfficeNet Direct 9 2 Unsupported ClieOp03 fields 10 3 Number of available positions in OfficeNet Direct 11 4 BTL91 and the obligatory fields in OfficeNet Direct 14 5 Number of available positions in OfficeNet Direct 14 6 Specific Payment records EU-Payment(IBAN/BIC) 15 7 Explanation of abbreviations in MT940 17 8 Layout of MT940 Customer Statement Message 19 9 Layout of MT940 Message Header/Trailer 20 10 Layout of MT940 Customer Statement Message per Tag 20 11 Explanation of abbreviations in MT942 23 12 Layout of MT942 Interim Transaction Report 25 13 Layout of MT942 Message Header/Trailer 26 14 Layout of MT942 Interim Transaction Report per Tag 26 15 List of figures and tables 28

___________________________________________________________________ABN AMRO Bank N.V.


29

Appendix B Explanation of tag usage in MT940

TAG 20 Bank identification for a message, which must be identical in the subsequent message. This tag is intended for use to retrieve the transaction later (reference to origin). In the MT940 message created in OfficeNet Direct, this field is filled with the logical file sequence number, which includes a sequence number (7 positions) that increases with each statement, separated by a slash and followed by 1 space: 9999999/9999999[ ].

TAG 21 Contains the TRN of another message, if applicable. This tag is included

in SWIFT files. The field is optional because there are no relationships with other messages at this point. The field may therefore be empty. Later, however, this field may be filled for incoming SWIFT messages (currently unavailable).

TAG 25 Contains the account number to which the account statement applies.

For Dutch accounts, this tag consists of 10 positions, except if the first position is '0', in which case it consists of 9 positions, e.g. 412345578. If the SWIFT message is received from SWIFT, all 35 positions are used.

TAG 28 Contains the statement number/sequence number of the account

statement. The tag is used as specified in the SWIFT delivery. When created by ABN AMRO systems, the layout of the tag is as follows:

maximum of 5 digits before the slash and 2 digits after the slash. The digits before the slash consist of the day code (1 through 366) and the run number. The run number is currently always 01, but this number will increase automatically in the future to reflect multiple runs on a single day (e.g. 02). The digits after the slash represent the sub-message number. Tag 28 can have a maximum of 99 sub-messages. In cases involving sub-message numbers less than 10, preceding zeros are not used. Tag 28 can have any value between 101/1 and 36601/99.

TAG 28C The format of the positions before the slash in this tag is the same as the

format for the positions before the slash in Tag 28. This tag is used in cases involving 100 or more sub-messages. Tag 28C can have any value between 101/1 and 36601/999. Tag 28 and Tag 28C can both appear in the same message. If required, a check can be performed on the PC for sequence, connection and double delivery based on Tag 28 and Tag 28C. Connection checks based on the account balance can also be performed on the PC. This method is recommended. For checking purposes, ABN AMRO Bank also creates account statements for accounts with no transaction activity, even if the account balance is zero. The sequence number (page number) indicates the sequence of subsequent messages for the same account number within a single transmission file.

TAG 60m Content of the previous MT940 message for this account: 60F = First (previous delivery), 60M = Intermediate (subsequent message) � D/C - NOTE = C for balance = zero

___________________________________________________________________ABN AMRO Bank N.V.


30

� Date This is the date of the last account statement on which transactions

occurred. For a new account, this date will be 0 until the first account statement is printed. If an account statement is not issued daily, this date remains unchanged until the next printed account statement is issued. For subsequent messages, 60M must contain all of the data from 62M of the previous MT940. This means that the date becomes the current book date. NOTE: If reports are generated more than once a day, the date of the last account statement is no longer given. Instead, the book date for the last transaction reported is given.

� Balance Number of decimals of the opening balance derived from the ISO currency code (generally 2). For example: 60F:C921231EUR100, then the opening balance is 100.00. The decimal point is always included in our deliveries. For example: 60F:C921231USD100.

TAG 61 Content of the transaction:

� Value date If the value date is zero, the book date is always given as the value

date. � Entry date (book date)

If the book date is zero, the ABN AMRO book date (from the header record) is used.

� D/C Debit/Credit. If the amount is zero, we report this as C. � Funds code

OfficeNet Direct ignores this; this is possible because all transactions within a single SWIFT message have the same currency code; see tags 60m and 62m.

� Amount The amount received from SWIFT is used. If the amount is created by a bank application, the number of decimal places is changed if necessary (currently unnecessary). Two decimal places are always used for reports and messages from the bank systems, whatever the ISO currency code (e.g. 100.00). The decimal calculation performed on the PC automatically retrieves the appropriate currency code based on the account number and uses it to determine the appropriate number of decimal places.

� Type The format is Nxxx, where xxx is the transaction code.

NOTE: This transaction code is primarily intended for internal use by ABN AMRO Bank. We do not recommend use of this code for reconciliation purposes.

� Reference for account owner When reporting in OfficeNet Direct, this record is filled with NONREF. � Account servicing bank Not filled in. � Further reference/info

To be used for the original transaction amount (see section 5.5).

TAG 86 This tag contains a maximum of 9 x 32 = 288 positions at transaction level. The value of the tag is used as received, i.e. not condensed.

___________________________________________________________________ABN AMRO Bank N.V.


31

Each line of 32 positions is converted into a single SWIFT line of 65 positions if the number of description lines within the transactions processed by ABN AMRO Bank is not greater than 6.

If the number of description lines exceeds six, two description lines are placed one below the other in a single SWIFT line:

Line 1 Pos. 1-32 1st ‘ABN AMRO’ description line Pos. 33-64 2nd ‘ABN AMRO’ description line Line 2 Pos. 1-32 3rd ‘ABN AMRO’ description line Pos. 33-64 4th ‘ABN AMRO’ description line Line 3 Pos. 1-32 5th ‘ABN AMRO’ description line Pos. 33-64 6th ‘ABN AMRO’ description line Line 4 Pos. 1-32 7th ‘ABN AMRO’ description line Pos. 33-64 8th ‘ABN AMRO’ description line Line 5 Pos. 1-32 9th ‘ABN AMRO’ description line

Contra-account number When submitting transactions, tag 86 indicates, where applicable, the contra-account number for a transaction. Bank account numbers are specified using full stops, e.g. “43.01.63.622” of “111.11.11.111”, and are always preceded by a space. Postbank account numbers use the word “GIRO”, e.g. “:86:GIRO 4090309”, without a preceding space. The total number of positions for Postbank account numbers is always 9. If the account number consists of less than 9 positions, spaces follow the word GIRO.

Compression The text as compressed: line 1 pos. 1-32 'CUMULATION OF ZZZZZZ9 BOOKINGS' The text as compressed according to output contract: line 1 pos. 1-32 'ZZZZZZ9 BOOKINGS ACCORDING TO SUPPLEMENTS'

No description If there is no description, then positions 5-6 in the bank identification = ‘NL’ and the text in tag 86 is set to ‘VARIOUS’ and otherwise ‘MISC’.

TAG 62m Analogous to tag 60m (62F - final and 62M – subsequent message). For

a subsequent message, the total of the transactions is the interim balance. In OfficeNet Direct, the date is the book date.

TAG 64m Is not provided in OfficeNet Direct. TAG 65m Is not provided in OfficeNet Direct. TAG 86 This tag at message level gives the EUR conversion rate of the currency

of the account to which the report applies. This tag applies to the EMU currencies and a (limited) number of non-EMU currencies.

___________________________________________________________________ABN AMRO Bank N.V.


32

Appendix C Explanation of tag usage in MT942

TAG 20 Bank identification for a message, which must be identical in the subsequent message. This tag is intended for use to retrieve the transaction later (reference to origin). In the MT940 message created in OfficeNet Direct, this field is filled with the logical file sequence number, which includes a sequence number (7 positions) that increases with each statement, separated by a slash and followed by 1 space: 9999999/9999999[ ].

TAG 21 Contains the TRN of another message, if applicable. This tag is included

in SWIFT files. The field is optional because there are no relationships with other messages at this point. The field may therefore be empty. Later, however, this field may be filled for incoming SWIFT messages (currently unavailable).

TAG 25 Contains the account number to which the account statement applies.

For Dutch accounts, this tag consists of 10 positions, except if the first position is '0'; in which case it consists of 9 positions, e.g. 412345578. If the SWIFT message is received from SWIFT, all 35 positions are used.

TAG 28C Contains the statement number/sequence number of the account

statement. The tag is used as specified in the SWIFT delivery. If the tag is filled by ABN AMRO systems, the statement number is filled with the day code for the day on which the intraday transaction was created.

TAG 34F First occurrence: Floor Limit indicator specifies the minimum value an

order must have to be individually delivered. In cases involving messages received from SWIFT, the information is used as it is received from SWIFT. The limit is zero for messages from the ABN AMRO systems. The currency code for an account may be unknown for certain reports and messages generated by ABN AMRO systems. In such cases, EUR is used as the default or TAG 34F is not included in the file at all. In principle, the account number from TAG 25 is used to retrieve the currency code from the local table.

TAG 34F Second occurrence: Same as above, but specifically for credit messages.

This tag is only used if the limit for credit transactions differs from the limit for debit transactions. The field is not used in messages generated by ABN AMRO systems.

TAG 13 Date/time indicator

Date and time at which a message arrives or is created at the bank (yymmddhhmm). In cases involving SWIFT deliveries, this tag is used as it is delivered by SWIFT. In cases involving the ABN AMRO systems, the actual date and time at which the message is created is used.

___________________________________________________________________ABN AMRO Bank N.V.


33

TAG 61 Content of the transaction: � Value date as received in the SWIFT delivery.

Sub-messages: filled with the value from CRC (yymmdd). Messages: filled with zeros because the definitive value date is unknown at the moment the message is created (may change in the future).

� Entry date (book date) as received in the SWIFT delivery. Sub-messages: filled with the value from CRC (yymmdd). Messages: filled with zeros because the definitive book date is unknown at the moment the message is created (may change in the future).

� D/C Debit/Credit. If the amount is zero, we report this as C. � Funds code

OfficeNet Direct ignores this; this is possible because all transactions within a single SWIFT message have the same currency code; see tags 60m and 62m.

� Amount The amount received from SWIFT is used. If the amount is created by a bank application, the number of decimal places is changed if necessary (currently unnecessary). Two decimal places are always used for reports and messages from the bank systems, whatever the ISO currency code (e.g. 100.00). The decimal calculation performed on the PC automatically retrieves the appropriate currency code based on the account number and uses it to determine the appropriate number of decimal places.

� Type The format is Nxxx, where xxx is the transaction code.

NOTE: This transaction code is primarily intended for internal ABN AMRO Bank use. We do not recommend use of this code for reconciliation purposes.

� Reference for account owner When reporting in OfficeNet Direct, this record is filled with NONREF. � Account servicing bank Not filled in. � Further reference/info To be used for the original transaction amount (see section 6.5).

TAG 86 This tag is used as received in the SWIFT delivery. In cases involving the ABN AMRO systems, the tag is checked to determine whether it begins on a line with ":" or ""; in which case these characters are replaced by spaces. Lines containing (X65) spaces are skipped. In cases involving interim messages from Telegiro, only 3*30 positions are currently filled. In cases involving interim messages from Bankgiro, only 3*32 positions are currently filled. In cases involving interim messages Batchgiro, 3*32 positions are currently filled.. In cases involving interim messages Foreigngiro, 4 lines of 32 positions are currently filled:

Line 1 Name of principal. Line 2 Reason for payment. Line 3 'TEXT SEE NOTAREF: xxxxxxxxxxxxxxxx'(SBI ref no.). Line 4 Corrected report text if applicable

___________________________________________________________________ABN AMRO Bank N.V.


34

The manner in which the SWIFT line is filled for sub-messages differs. Each line of 32 positions is converted into a single SWIFT line of 65 positions if the number of description lines within the transactions processed by ABN AMRO Bank is not greater than 6.

If the number of description lines exceeds six, two description lines are placed one below the other in a single SWIFT line:

Line 1 Pos. 1-32 1st ‘ABN AMRO’ description line Pos. 33-64 2nd ‘ABN AMRO’ description line Line 2 Pos. 1-32 3rd ‘ABN AMRO’ description line Pos. 33-64 4th ‘ABN AMRO’ description line Line 3 Pos. 1-32 5th ‘ABN AMRO’ description line Pos. 33-64 6th ‘ABN AMRO’ description line Line 4 Pos. 1-32 7th ‘ABN AMRO’ description line Pos. 33-64 8th ‘ABN AMRO’ description line Line 5 Pos. 1-32 9th ‘ABN AMRO’ description line

TAG 90D Number of debit transactions in message.

In cases involving SWIFT deliveries, this tag is used as it is received from SWIFT. In cases involving ABN AMRO systems, two situations apply: � If the MT942 message contains only one TAG 61, it is left unfilled.

This situation resembles the old situation and occurs in urgent messages and foreign messages.

� If the MT942 message contains more than one TAG 61, it is filled if possible (optional). This situation did not occur in the past, but occurs now because messages are now also sent to the principal in cases involving bankgiro and batches.

NOTE: In cases involving messages with different currencies, separate MT942 messages are created for each ISO currency code. In cases involving just 1 credit message, TAG 90C is not used (even if there are debit messages).

TAG 90C Number of credit messages in the message. See TAG 90D.

In cases involving just 1 debit message, TAG 90C is not used (even if there are credit messages).

TAG 86 Is used in cases involving SWIFT deliveries. There is no reason to fill this

tag in cases involving ABN AMRO systems because there is no variable information at message level.

OfficeNet Direct data import and export formats - ABN … · OfficeNet Direct data import and...

Documents

Transcript of OfficeNet Direct data import and export formats - ABN … · OfficeNet Direct data import and...