Format Differences SWIFT FIN MT940 MT942

Transcription

1 SWIFT FIN MT940 MT942 ABN AMRO versus Fortis [version 1.0] 24 January 2011

2 Should you have questions and/or remarks regarding this document, please contact the department: ABN AMRO Bank N.V. COO / C&MB / echannels P.O. Box EA Amsterdam PAC AA Globalchannels@nl.abnamro.com ABN AMRO Bank N.V 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. 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.

3 Contents 0 Introduction Audience Differences Systems Document Structure Document History Documentation & Information Layout Convention Legend Tables... 3 Swift Formats MT940 & MT Swift Introduction External Documentation & Information MT940 vs MT Assumptions Standard Swift MT940 Account Statement Introduction Message Structure MT Sub-message Specification Tags and Fields MT Swift MT940 SEC & Tandem vs FRS Introduction Scope MT940 Account Statement Zero messages Assumptions Amount B Zero amounts Differences per tag Tag 20 Transaction Reference Number Tag 21 Related Reference Tag 25 Account Number Tag 28C Statement Number/Sequence Number Tag 60 Opening Balance Tag 61 Statement Line Tag 86 Transaction Information Tag 62 Closing Balance Tag 64 Closing Available Balance Tag 65 Forward Available Balance Tag 86 Information to Account Owner I

4 4 Standard Swift MT942 Intraday Transaction Report Introduction Message Structure MT Specification Tags and Fields MT Swift MT942 SEC vs FRS Introduction Processing Intraday Transactions Processing SEC Processing FRS Final Settlement SEC en FRS Scope MT942 Intraday Rapport Zero messages Assumptions Amount B Floor Limit Differences per tag Tag 20 Transaction Reference Number Tag 21 Related Reference Tag 25 Account Number Tag 28C Statement Number/Sequence Number Tag 34F Floor Limit (1) Tag 34F Floor Limit (2) Tag 13D Date/Time Indication Tag 61 Statement Line Tag 86 Transaction Information Tag 90D Number and Sum Debit of Entries Tag 90C Number and Sum Credit of Entries Tag 86 Information to Account Owner Annex Character Sets ISO Codes ISO Country code ISO Currency Code Bank Codes FBN Transaction Code FBN Service Type AAB Transaction Code Swift Transaction Type Identification Code Examples Introduction Transactions II

5 0 Introduction Clients of former Fortis Bank Nederland can receive MT940 and/or MT942 messages via a Swift connection, with address FTSBNL2R. In the near future these clients will receive these messages from replacing ABN AMRO systems, via the Swift address ABNANL2A. Therefore a migration of account numbers is necessary which is planned for the beginning of This document describes the differences between the Swift MT940 and MT942 file format generated by various internal bank systems. These differences are caused by the various systems and computer programs used by ABN AMRO and former Fortis Bank Nederland. 0.1 Audience This information is intended for IT departments of companies that use electronic files, or by their software suppliers. The differences can affect the way these files are processed in the administration. 0.2 Differences The format differences do not apply to the technical structure of the MT940 and MT942 messages. This remains in line with the format description specified by Swift. The differences affect to the logical content of the MT940 and MT942: frequency of reporting; formatting of account numbers; statement number / sequence number; zero messages; available balance; structure and ordering statements; condensed statements. 0.3 Systems Former Fortis Bank Netherlands uses two systems which eventually will be phased out: Tandem for Swift MT940; SEC for Swift MT940 and MT942. ABN AMRO uses two systems for the servicing of client accounts: FRS for Dutch accounts: Swift MT940 and MT942; T24 for accounts outside The Netherlands: Swift MT940 en MT942. The countries where the accounts are hold can influence the content of the Swift MT940 and MT942 messages. Besides the layout of the account number the Swift MT940 messages from FRS and T24 must be equal. 1

6 0.4 Document Structure This document describes the formats which are relevant for the migration. For each format the generic standard is described followed by the internal differences Document History Version Date Author Role s Rob Scheper Channel Manager Initial version Documentation & Information Title Version / Date Author / Source Swift Formats MT940-MT942 formats for exporting data from OfficeNet Direct January 2008 ABN AMRO Swift Formats MT940-MT Layout Convention Font type Courier is used in examples to show the content of the MT940 and MT942 messages. These icons are used to mark specific information. Tip Useful tip to work more efficient Paragraph with this icon contains extra information about the subject concerned Additional Information Paragraph with this icon contains reference to other parts of this document which contains additional information about the subject concerned. Attention Paragraph with this icon contains information that asks for special attention. 2

7 0.4.4 Legend Tables Column Value Description s Status Type Length V Mandatory Item must be used O Optional Item may be used C Conditional Item may and/or must be used depending on the existence or value of other items N Numeric Digits, 0-9 B Amount This type is used for amounts. There should be at least 1 digit before the comma. The decimal comma ', ' is mandatory and is included in total length. A Alphabetic Letters, A-Z (capitals) X Alphanumeric Combination of digits, capitals (upper-case) and signs from a specific set. See Annex 6 Character Sets x Alphanumeric Combination of digits, capitals (upper-case), lower-case and signs from a specific set. See Annex 6 Character Sets Count Fixed count Fixed count x characters of item (underlined) Count Variable count Maximum x count of characters of item. When used with a mandatory item at least 1 digit must be used. Repeat Count Count how many times a item, record, tag or field may be used 3

8 Swift Formats MT940 & MT942

9 1 Swift 1.1 Introduction Swift (Society for Worldwide Interbank Financial Telecommunication) is the international organization that handles exchange of messages between banks. For this Swift has defined the MT, or Message type, standard. In the MT standard in particular, the following two message types used for reporting account information towards clients: MT940 is used to report electronic statement information; MT942 is used to rapport intra-day transaction information. The layout and content of the messages is base don the FIN standard of Swift, Category 9, Cash Management and Customer Status. In this document a brief description of Swift MT940 and MT942 is added for support and as reference for the additional part of the document. For the complete and most recent description of the MT940 and MT942 see the Swift documentation. De Swift MT format standard uses strict conditions and validation rules. When deviated of this a remark is made in this document External Documentation & Information Title Version / Date Author / Source User Handbook SWIFT Standards MT November 2010 Swift Standards MT November 2010 (authorisation required) 1.2 MT940 vs. MT942 The MT940 and MT942 are related to each other. The MT942 intra-day report contains transactions that may occur in the following MT940 statement. The transactions are 'already' booked yet but not finalized. Such operations are called pre-advice". It remains a pre-advise until the end of the day when the final entries are booked and the MT940 statement is created. Pre-advice The transactions in the MT942 are called pre-advice because of the possibility the transaction ultimately isn t processed and not definitely settled. This may occur when it turns out that the transaction contains errors and/or is recalled. For this reason it s not possible to derive rights from a pre-advise. 5

10 1.3 Assumptions Character Set The Swift format uses a variable row length. Every row ends with a carriage return and line feed character (hexadecimal x0d x0a). In this document indicated as CRLF. See Annex 6 Character Sets for an overview of the characters that can be used by Swift in the MT messages. Amount B15 The integer part of amount must contain at least one digit. The decimal comma ',' is mandatory and included in the maximum length. An amount has no leading zeros. However, if an amount is less than the currency unit a zero is placed before the decimal comma, for example: 0,89 The number of digits after the comma may not exceed the maximum count that is defined for the concerning ISO-Currency code. Example: EUR (Euro) 2 decimals, JPY (Japanese Yen) 0 decimals. In case of a round sum or in case of amounts whereby the last decimals may be zeros: the last zeros may be absent, for example: USD 100, EUR 99,5 ISO-Currency code A3 The currency code must occur in the list maintained by ISO according to the standard (see Annex 7.2 ISO Currency Code) 6

11 2 Standard Swift MT940 Account Statement 2.1 Introduction MT940 is used to report electronic account statement information. 2.2 Message Structure MT940 The table below shows the structure of the Swift MT940 standard. The Status column indicates if a tag is mandatory or optional. Status Tag Name Repeat V Message Header Record 1 Section Statement 1 V 20 Transaction Reference Number O 21 Related Reference V 25 Account Number & Currency Code V 28C Statement Number/Sequence Number V 60x Opening Balance ---> Section Transactions 0-n O 61 Statement Line O 86 Statement Information --- V 62x Closing Balance O 64 Closing Available Balance ---> O 65 Forward Available Balance 0-n --- O 86 Information to Account Owner V Message Trailer Record The message header and trailer record are not described in detail. Apart from the Swift address in the header record these will not change Sub-message Swift allows a MT940 to contain characters as a maximum. When a complete MT940 will contain more than characters it has to be split up in several sub-messages with each of characters as a maximum. In sub-messages the Option M (intermediate) in tag 60 and 62 is used and Sequence Number in tag 28C determines the right logical sort order. When a Swift MT940 message contains less than characters the Option F (first) in tag 60 and 62 is used. 7

12 2.3 Specification Tags and Fields MT940 Tag Name Typ. Len. Stat. Rep C 60a Transaction Reference Number (TRN) Tag V 1 :20: Transaction Reference Number X 16 V 1 V 1 This tag contains a unique number to identify the MT940 message. Related Reference 16 O 1 If the MT 940 is sent in response to an MT 920 Request Message, this field must contain the field 20 Transaction Reference Number of the request message. Tag V 1 :21: Reference X 16 V 1 Account Number V 1 Code assigned by the bank to uniquely identify an account. Tag V 1 :25: Account Number X 35 V 1 Statement Number/Sequence Number Tag V 1 :28C: Statement Number N 5 V 1 Sequence Number N 5 O 1 V 1 This tag contains the number of the account statement, optional followed by a sequence number of the message in the statement. Opening Balance V 1 This field specifies, for the (intermediate) opening balance, whether it is a debit or credit balance, the date, the currency and the amount of the balance. Option F V 1 :60F: Debit/Credit indicator A 1 V 1 D = Debit, C = Credit Start Booked date N 6 V 1 Format: YYMMDD ISO-Currency code A 3 V 1 Amount B 15 V 1 Option M V 1 :60M: Debit/Credit indicator A 1 V 1 D = Debit, C = Credit Start Booked date N 6 V 1 Format: YYMMDD ISO-Currency code A 3 V 1 Amount B 15 V 1 Statement Line O 1 This tag contains the details of a transaction Tag V 1 :61: 1 Value date N 6 V 1 Format: YYMMDD 2 Booked date N 4 O 1 Format: MMDD 3 Debit/Credit indicator A 2 V 1 D = Debit, C = Credit, RD = Reverse Debit, RC = Reverse Credit 4 Funds Code A 1 O 1 5 Amount B 15 V 1 6 Transaction Type Code X 4 V 1 7 Reference Account Owner X 16 V 1 8 Reference Bank X 16 O 1 9 Transaction Information x 34 O 1 On a new line Transaction Information O 1 Additional information to the account owner about the transaction Tag V 1 :86: Description x 65 V 1-6 Rows ends with CRLF 8

13 Tag Name Typ. Len. Stat. Her. 62a Closing Balance V 1 This field specifies, for the (intermediate) closing balance, whether it is a debit or credit balance, the date, the currency and the amount of the balance. Option F Tag V 1 :62F: Debit/Credit Indicator A 1 V 1 D = Debit, C = Credit End Booked Date N 6 V 1 Format: YYMMDD ISO-Currency code A 3 V 1 Amount B 15 V 1 Option M Tag V 1 :62M: Debit/Credit Indicator A 1 V 1 End Booked Date N 6 V 1 Format: YYMMDD ISO-Currency code A 3 V 1 Amount B 15 V 1 Closing Available Balance O 1 This field indicates the funds which are available to the account owner (if credit balance) or the balance which is subject to interest charges (if debit balance). Tag V 1 :64: Debit/Credit Indicator A 1 V 1 D = Debit, C = Credit Value Date N 6 V 1 Format: YYMMDD Currency code A 3 V 1 ISO-Currency code Amount B 15 V 1 Forward Available Balance O x This field indicates the funds which are available to the account owner (if a credit or debit balance) for the specified forward value date. Tag V 1 :65: Debit/Credit Indicator A 1 V 1 D = Debit, C = Credit Value Date N 6 V 1 Format: YYMMDD Currency code A 3 V 1 ISO-Currency code Amount B 15 V 1 Information to Account Owner O 1 This field contains additional information about the statement as a whole. It is to be passed on to the account owner. Tag V 1 :86: Information x 65 V 1-6 Rows ends with CRLF 9

14 3 Swift MT940 SEC & Tandem vs FRS 3.1 Introduction This chapter describes the differences between the Swift MT940 from SEC and FRS. ABN AMRO uses 2 systems to service accounts of her clients: a system for Dutch accounts and a system for accounts outside The Netherlands. Both systems can generate and send MT940 messages. The country where the account is held can influence the content of the Swift MT940. MT940 messages received through Swift, for example in a multibank-scenario, are outside the scope of this document. Namely, the MT940 messages received from third banks are passed unchanged so the functional content can differ. 3.2 Scope The differences are related to the Swift MT940, created by ABN AMRO and former Fortis Bank Netherlands, sent via respectively Swift address ABNANL2A and FTSBNL2R. The differences between these two 'standard' formats are described in this chapter: MT940 from SEC and Tandem; MT940 from FRS. At the request of the client in FRS a distinction can be made in the following settings: Layout account number in tag 25: - optional provided with a leading zero - optionally followed with the ISO Currency code Usage of the Swift TTIC code or the AAB Transaction code in tag 61, sub-field 6. A comparison between these client settings in relation to the standard is not made. 3.3 MT940 Account Statement The differences between MT940 from SEC/Tandem and FRS apply to the logical content. Functionality SEC Tandem FRS Zero messages Yes Yes Yes Frequency of reporting Daily Daily Daily Available balance (Forward, tag 65) Yes No Yes Arrangement transactions Fixed Fixed Fixed Order transaction Fixed Fixed Fixed Account counterparty in transaction information Fixed Fixed Fixed Transaction Type Identification Code (Swift TTIC) Fixed Fixed Fixed FBN Transaction Code No No No AAB Transaction Code No No Yes FBN Service Type No No No Variable arrangement files No No No Naming export files n/a n/a n/a 10

15 3.3.1 Zero messages A zero message is a MT940 account statement without statement lines and contains only an opening- and a closing balance supplemented with possible available balances. Source SEC Tandem FRS Sending zero messages Yes. Condition: the balance in tag 62F doesn t equal to 0 and/or there are available balances (64 or 65) unequal to 0 present. Yes. MT940 is always created regardless of account balance and/or absence of transactions. Yes. MT940 is always created regardless of account balance and/or absence of transactions. 3.4 Assumptions Amount B15 Using the data type Amount conforms to the Swift standard amount. The requirement for the maximum number of decimal places to use the ISO Currency Code is respected. However, the usage of Amount varies per source system and per tag. The most common number of decimal places in the ISO Currency Codes is 2. The table below shows the possible Amount layout variations and to which Swift tag they apply. The amount layout code is used in the detailed tag description. Amount Value Layout SEC Tandem FRS Layout code Round sum Amount with 1 decimal 0, Without decimals 60 0,00 Right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code 0,1 With 1 decimal 61 0,10 Right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code A0 AM B1 BM SEC and FRS reports amounts exactly with the number of decimals as defined for the concerning ISO Currency code. Tandem reports amount always with 2 decimals. However, when the Currency code is JPY then the decimals are lacking Zero amounts In tag 60, 62, 64 and 65 the amount can be zero. The debit en credit indicator is differently used: SEC and FRS both use standard C Tandem uses standard D 11

16 3.5 Differences per tag The differences do not apply to the technical structure. This remains in line with the format description specified by Swift, unless stated explicitly. 3.6 Tag 20 Transaction Reference Number :20: Transaction Reference Number (TRN) V 1 This tag contains a unique number to identify the MT940 message. Field Form SEC/Tandem FRS Transaction Reference Number X16 Form: N9A3N4 N9: First 9 digits of the 10-digit Account number A3: ISO Currency code N4: Processing day number: format YDDD The number of the processing day applies to the day number and year on which the MT940 has been created. Form: N7/N8 N7: Bank reference number N8: Fixed number: Bank identification of the message. Must be equal in case of a consecutive message. Intended for later retrieval (reference to origin). The Bank reference number doesn t apply to the logical content of the message. Example :20: EUR0350 :20: / Tag 21 Related Reference :21: Related Reference O 1 If the MT 940 is sent in response to an MT 920 Request Message, this field must contain the field 20 Transaction Reference Number of the request message. Field Form SEC/Tandem FRS Reference X16 Not used Form: X11 X11: Swift-BIC sender Example n/a :21:ABNANL2AXXX Default value ABNANL2AXXX unless other value available. Can be used when received through Swift third banks in a multibank-scenario. 3.8 Tag 25 Account Number :25: Account Number V 1 Code assigned by the bank to uniquely identify an account. Field Form SEC/Tandem FRS Account Number X35 Form: N10A3 Form: N9 N10 N10: Account Number with leading zero A3: ISO Currency code (see Annex 7.2 ISO Currency Code) N9: Account Number without leading zero N10: Account Number with leading zero One Account Number can be hold in several different currencies (ISO Currency code) Depending on the country where the account is hold the form can varies. Usage of leading zero is a client preference. Example :25: EUR :25: One Account Number can be hold in one currency (ISO Currency code) 12

17 3.9 Tag 28C Statement Number/Sequence Number :28C: Statement Number / Sequence Number V 1 This tag contains the number of the account statement, optional followed by a sequence number of the message in the statement. Field Form SEC/Tandem FRS Statement Number / Sequence Number N5 [/N5] Form: N5/N5 N5: Statement Number /N5: Sequence Number Form: N3/N5 N3: Statement Number /N5: Sequence Number Statement Number is consecutive and has leading zeros. Every calendar year Statement Number starts again with 1. Example SEC: Statement Number is increased by 1 when there are transactions. When there are no transactions but the Book Balance in tag 62F is unequal 0, a zero message is created; the Statement Number remains the same as in the last statement with transactions. Date in 62F contains the previous bank business day. If the Book Balance is zero and there are no transactions then: a MT940 isn t created. Tandem: always a MT940 is created regardless of Account Balance and/or absence of transactions. Statement Number is incremented by 1. Statement Number contains the day number in the year. (1 to 366). The day number refers to the End Book Date in tag 62F. Sequence Number starts with the value 1 and is incremented by 1 for each submessage. This is because the MT940 Bank Statement is divided into submessages each up to 10,000 characters. The Statement Number of an account opened during the year begins with the concerning day number. The numbering of the electronic Account Statement is consecutive, but may differ from the number on the paper account statement. :28C:00168/00001 :28C:00213/00001 :28C:355/00001 :28C:3/

18 3.10 Tag 60 Opening Balance :60x: Opening Balance V 1 This field specifies, for the (intermediate) opening balance, whether it is a debit or credit balance, the date, the currency and the amount of the balance. Field Form SEC/Tandem FRS 1 Debit / Credit indicator A1 D (debit) or C (credit) D (debit) or C (credit) 2 Start Booked Date, YYMMDD N6 3 ISO Currency code A3 Option F: The Start Booked Date matches with the date in tag 62F Closing Balance of the previous Account Statement. When the amount equals zero and/or the previous days there were no MT940 created than the date is the previous bank business day. Option M: The Start Booked Date match with the date in tag 62F Closing Balance of the concerning Account Statement. 4 Amount B15 Option F: The Opening Balance match with the Closing Balance in tag 62F of the previous Account Statement. Option M: The Opening Balance match with the Closing Balance in tag 62M of the previous sub-message. SEC: Layout code A0/BM. Round sum is reported without decimals. Amount with decimals are right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. Tandem: Layout code AM/BM. The decimal part of the amount is right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. Option F: The Start Booked Date matches with the date in tag 62F Closing Balance of the previous Account Statement. Option M: The Start Booked Date match with the date in tag 62F Closing Balance of the concerning Account Statement. In case of a new Account this date has the value 0 until the first Account Statement is printed. Option F: The Opening Balance match with the Closing Balance in tag 62F of the previous Account Statement. Option M: The Opening Balance match with the Closing Balance in tag 62M of the previous sub-message. Layout code A0/BM. Round sum is reported without decimals. Amount with decimals are right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. Example :60F:C101217EUR0, :60F:C101217USD25920, :60F:D101215USD ,73 :60F:D090825GBP135222,16 14

19 3.11 Tag 61 Statement Line :61: Statement Line O 1 This tag contains the details of a transaction Field Form SEC/Tandem FRS 1 Value Date YYMDD N6 2 Booked Date, MMDD [N4] In use In use 3 Debit / Credit indicator A2 Form: A2: D (debit), C (credit), RD (Reverse Debit) of RC (Reverse Credit) 4 Funds Code [X1] n/a n/a 5 Amount B15 SEC: Layout code A0/BM. Round sum is reported without decimals. Amount with decimals are right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. 6 Transaction Type Code 7 Reference Account Owner A1X3 X16 Tandem: Layout code AM/BM. The decimal part of the amount is right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. Form: A1A3 N plus TTIC Code (see 9 Swift Transaction Type Identification Code) MSC default with multibank accounts Form: A1N3 S plus Swift message number (see Swift documentation) Default value NONREF unless other value available Form: A2: D (debit), C (credit), RD (Reverse Debit) of RC (Reverse Credit) A zero amount is reported as C. Layout code: A0/B1. Round sum is reported without decimals. Amount with decimals is reported without trailing zeros. FormA: A1A3 N plus TTIC Code (see 9 Swift Transaction Type Identification Code) FormB: A1N3 8 Reference Bank [//X16] FormC: [//N3] 9 Transaction Information [X34] SEC: Additional information Tandem: Depending on the type of transaction a 10 digit number, possibly with leading zeros, is placed being the counter party account number. In case of a Postbank account number: P with a 9 digit number, right aligned and with leading zeroes. This is the approach regardless the country of origin or the use of an IBAN in the transaction. In the case of a payment in the Netherlands the account number is complete. In other cases this approach may result in an incomplete account number. The account number may further be supplemented with the ascription of the account of the counterparty till the maximum length of 34 characters is reached. The account number and ascription of the account of the counterparty are also part of the transaction information in tag 86. Also possible text: [TOTAAL INCASSO VOOR COMPRIMEREN] [TOTAAL BETALINGEN VOOR] + in 86 + [COMPRIMEREN] N plus AAB Transaction Code (see 8.3 AAB Transaction Code) Default value NONREF unless other value available // plus AAB Transaction Code (see 8.3 AAB Transaction Code) Can be used for: - additional transaction classification - original transaction amount 15

20 Example SEC Example FRS :61: RC1122,88NCOL The information shown (form A, B or C) in field 6 and 8 depends on the client preference. Using the AAB Transaction Code is not recommended for reconciliation purposes. :61: C16970,73NSEC //C ST. US99999X1054 A :61: C150,NTRFNONREF B :61: D1359,93N192NONREF C :61: C218,05NTRFNONREF//792 /EC-COMPLIANT/ C :61: D1099,93NTRFNONREF//192 16

21 3.12 Tag 86 Transaction Information :86: Transaction Information O 6 Additional information to the account owner about the transaction. Field Form SEC/Tandem FRS Description X65 Maximum 6 x 65 = 390 positions Maximum 9 x 32 = 288 positions are available. SEC/Tandem: Possible text in the first line: [BETALINGSKENM. BETREFT ACCEPTGIRO] [ACCEPTGIRO] [ONZE REF.: ] [UW REF.:] SEC: There is no formal formatting. Tandem: The transaction information is stripped of double spaces (condensed), placed on the available rules and cut off when the maximum line length is reached. The text contains uppercase and lowercase letters. There is no formal formatting. Counter party account number and ascription of the account of the counterparty is possibly also placed in tag 61 field 9. If the number of rows of description doesn t exceed 6 then each line of 32 positions is put in a separate description row. When more than 6 rows description of 32 positions then every 2 rows description are put together with a space between in 1 row of 65 characters. Counterparty account number When submitting transactions, tag 86 indicates, where applicable, the counterparty account number for a transaction. Bank account numbers are specified using full stops, e.g of , and are always preceded by a space. Postbank account numbers use the word GIRO, e.g. :86:GIRO , 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 thus: :86:GIRO , without leading spaces. The number of spaces between GIRO and the Postbank account number (max. 7 digits) is variable and depends on the number of digits in the Postbank account number. This number is right aligned with the last digit op position 17 or position 19. Compression The text as compressed: TOTAAL INCASSO VOOR COMPRIMEREN 10 POSTEN LAATSTE 5 POS SOM REKNRS or TOTAAL BETALINGEN VOOR COMPRIMEREN 63 POSTEN LAATSTE 5 POS SOM REKNRS

22 3.13 Tag 62 Closing Balance :62x: Closing Balance V 1 This field specifies, for the (intermediate) closing balance, whether it is a debit or credit balance, the date, the currency and the amount of the balance. Field Form SEC/Tandem FRS 1 Debit / Credit indicator A1 D (debit) or C (credit) D (debit) or C (credit). 2 End Booked Date, YYMMDD N6 3 ISO Currency code A3 SEC: A zero Amount is reported as C Tandem: A zero Amount is reported as D Option F: The End Booked Date Option M: The End Booked Date 4 Amount B15 Option F: The Closing Balance is the amount calculated from tag 60F plus or minus the transaction amounts of the concerning account statement. Example Option M: The Closing Balance is the amount calculated from tag 60 plus or minus the transaction amounts of the concerning sub-message. SEC: Layout code A0/BM. Round sum is reported without decimals. Amount with decimals are right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. Tandem: Layout code AM/BM. The decimal part of the amount is right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. SEC C101220EUR0, D101220EUR , D101220EUR ,40 Tandem D101215JPY0, D101220EUR0,00 D101220EUR486888,30 D101220EUR ,00 A zero Amount is reported as C Option F: The End Booked Date Option M: The End Booked Date Option F: The Closing Balance is the amount calculated from tag 60F plus or minus the transaction amounts of the concerning account statement. Option M: The Closing Balance is the amount calculated from tag 60 plus or minus the transaction amounts of the concerning sub-message. Layout code A0/BM. Round sum is reported without decimals. Amount with decimals are right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. C101231EUR0, C101221EUR1,20 C101221EUR574,80 C101231EUR ,34 18

23 3.14 Tag 64 Closing Available Balance :64: Closing Available Balance O 1 This field indicates the funds which are available to the account owner (if credit balance) or the balance which is subject to interest charges (if debit balance). Field Form SEC/Tandem FRS 1 Debit / Credit indicator A1 D (debit) or C (credit) D (debit) or C (credit). 2 Value Date, YYMMDD N6 3 ISO Currency code A3 4 Amount B15 SEC: Layout code A0/BM. Round sum is reported without decimals. Amount with decimals are right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. Example Tandem: Layout code AM/BM. The decimal part of the amount is right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. SEC C101220EUR0, C101220EUR10000, D101220EUR ,20 Tandem D101220EUR0,00 C101220EUR10000,00 D101220EUR ,20 Layout code: A0/B1. Round sum is reported without decimals. Amount with decimals is reported without trailing zeros. C101221EUR0, C101221EUR1,2 C101221EUR574,8 C101231EUR , Tag 65 Forward Available Balance :65: Forward Available Balance O x This field indicates the funds which are available to the account owner (if a credit or debit balance) for the specified forward value date. Field Form SEC/Tandem FRS 1 Debit / Credit indicator A1 D (debit) of C (credit) D (debit) of C (credit). 2 Value Date, YYMMDD N6 3 ISO Currency code A3 4 Amount B15 Layout code A0/BM. Round sum is reported without decimals. Amount with decimals are right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. Example SEC: Tag maximum 11 occurrences Tandem: Tag not used :65:C101220SEK85461, :65:C101216JPY , :65:D101220HUF ,30 Layout code: A0/B1. Round sum is reported without decimals. Amount with decimals is reported without trailing zeros. The number of lines tag 65 depends on the number of days in future which for a transaction is known. :65:C101230EUR361364,3 :65:C101222USD ,59 :65:C101223USD ,69 19

24 3.16 Tag 86 Information to Account Owner :86: O 1 This field contains additional information about the statement as a whole. It is to be passed on to the account owner. Field Form SEC/Tandem FRS Description X65 Not used Form: Default value /ACSI/ABNANL2AXXX unless other value available. Example n/a :86:/ACSI/ABNANL2AXXX 20

25 4 Standard Swift MT942 Intraday Transaction Report 4.1 Introduction A MT942 Intraday Report (Swift calls it: Interim Transaction Report) is a standard message for electronic transaction reporting. Message type MT942 is used to report brief and/or detailed information concerning debit or credit transactions since: The appearance of the last account statement or; The last intraday transaction report (sent in the period since the last account statement) 4.2 Message Structure MT942 The table below shows the structure of the Swift MT942 standard. The Status column indicates if a tag is mandatory or optional. Status Tag Name Repeat V Message Header Record 1 Section Statement 1 V 20 Transaction Reference Number O 21 Related Reference V 25 Account Number & Currency Code V 28C Statement Number/Sequence Number V 34F Floor Limit O 34F Floor Limit V 13D Date/Time Indication ---> O 61 Statement Line Section Transactions 0-n O 86 Statement Information --- O 90D Number and Sum of Entries O 90C Number and Sum of Entries O 86 Information to Account Owner V Message Trailer Record The message header and trailer record are not described in detail. Apart from the Swift address in the header record these will not change. 21

26 4.3 Specification Tags and Fields MT942 Tag Name Typ. Len. Stat. Her C 34F 34F Transaction Reference Number (TRN) Tag V 1 :20: Transaction Reference Number X 16 V 1 V 1 This tag contains a unique number to identify the MT942 message. Related Reference 16 O 1 If the MT 942 is sent in response to an MT 920 Request Message, this field must contain the field 20 Transaction Reference Number of the request message. Tag V 1 :21: Reference X 16 V 1 Account Number V 1 Code assigned by the bank to uniquely identify an account. Tag V 1 :25: Account Number X 35 V 1 Statement Number/Sequence Number Tag V 1 :28C: Statement Number N 5 V 1 Sequence Number N 5 O 1 V 1 This field contains the sequential number of the statement, optionally followed by the sequence number of the message within that statement when more than one message is sent for the statement. Floor Limit V 1 This field specifies the minimum value (transaction amount) reported in the message. Tag V 1 :34F: ISO Currency code A 3 V 1 Debit/Credit indicator A 1 O 1 When available: D = Debit Amount B 15 V 1 Floor Limit O 1 This field specifies the minimum credit value (transaction amount) reported in the message. Tag V 1 :34F: ISO Currency code A 3 V 1 Debit/Credit indicator A 1 O 1 C = Credit Amount B 15 V 1 13D Date/Time Indication V 1 This field indicates the date, time and time zone at which the report was created. Tag V 1 :13D: Date N 6 V 1 Format: YYMMDD Time N 4 V 1 Format: HHMM Time zone indicator X 1 V 1 Sign + of - Time zone offset N 4 V 1 Hour(s) differing from UTC 22

27 Tag Name Typ. Len. Stat. Her D 90C 86 Statement Line O 1 This tag contains the details of a transaction Tag V 1 :61: 1 Value date N 6 V 1 Format: YYMMDD 2 Booked date N 4 O 1 Format: MMDD 3 Debit/Credit indicator A 2 V 1 D = Debit, C = Credit, RD = Reverse Debit, RC = Reverse Credit 4 Funds Code A 1 O 1 5 Amount B 15 V 1 6 Transaction Type Code X 4 V 1 7 Reference Account Owner X 16 V 1 8 Reference Bank X 16 O 1 9 Transaction Information x 34 O 1 On a new line Transaction Information O 1 Additional information to the account owner about the transaction Tag V 1 :86: Description x 65 V 1-6 Rows ends with CRLF Number and Sum of Entries O 1 This field indicates the total number and amount of debit entries. Tag V 1 :90D: Number N 5 V 1 ISO Currency code A 3 V 1 Amount B 15 V 1 Number and Sum of Entries O 1 This field indicates the total number and amount of credit entries. Tag V 1 :90C: Number N 5 V 1 ISO Currency code A 3 V 1 Amount B 15 V 1 Information to Account Owner O 1 This field contains additional information about the statement as a whole. It is to be passed on to the account owner. Tag V 1 :86: Information x 65 V 1-6 Rows ends with CRLF 23

28 5 Swift MT942 SEC vs FRS 5.1 Introduction This chapter describes the differences between the intraday reporting from SEC and FRS. ABN AMRO uses 2 systems to service accounts of her clients. A system for Dutch accounts and a system for accounts outside The Netherlands. Both systems can generate and send MT942 messages. The country where the account is hold can influence the content of the Swift MT942. MT940 messages received through Swift, for example in a multibank-scenario, are outside the scope of this document. Namely, the MT940 messages received from third banks are passed unchanged so the functional content can differ. 5.2 Processing Intraday Transactions Not all transactions are advised, for example: certain costs/fee transactions, balancing transactions, ideal receivables and so on Processing SEC During a bank working day there are transactions initiated as well as received through the bank system. These transactions are provisional and made available through SEC. However, these transactions aren t yet provided with the right transaction codes. These new transactions are gathered and send in a Swift MT942 message. Normally spoken, this happens 9 times a day, 10 minutes before the hour, between 08:50 en 16: Processing FRS During a bank working day there are transactions initiated as well as received through the bank system. Periodic, approximately every 15 minutes, the new gathered transactions are send in a MT942 message. These transactions are provided with a generic code. Normally, the sending take place during the bank working day, but this can, depending on the availability of the systems, also happen outside this time frame Final Settlement SEC en FRS During the final settlement and during the creation of the account statement the transactions are processed : they are provided with the right transaction code. 24

29 5.3 Scope The differences are related to the Swift MT942, created by ABN AMRO and former Fortis Bank Netherlands, sent via respectively Swift address ABNANL2A and FTSBNL2R. The differences between these two 'standard' formats are described in this chapter: MT942 from SEC; MT940 from FRS. At the request of the client in FRS a distinction can be made in the following settings: Layout account number in tag 25: - optional provided with a leading zero - optionally followed with the ISO Currency code Usage of the Swift TTIC code or the AAB Transaction Code in tag 61, sub-field 6. A comparison between these client settings in relation to the standard is not made. Then Tandem system of former Fortis Bank Nederland isn t able to create MT942 messages and is not in scope of this chapter. 5.4 MT942 Intraday Rapport The differences between MT940 from SEC and FRS apply to the logical content. Functionality SEC FRS Zero messages No No Frequency of reporting During the day During the day Available balance (Forward, tag 65) n/a n/a Arrangement transactions Fixed Fixed Order transaction Fixed Fixed Account counterparty in transaction information Fixed Fixed Transaction Type Identification Code (Swift TTIC) n/a n/a FBN Transaction Code n/a n/a AAB Transaction Code n/a n/a FBN Service Type n/a n/a Variable arrangement files n/a n/a Naming export files n/a n/a Zero messages In the standard Swift MT942 description is the Section Transactions defined as optional. When there are no transactions this will result in a zero message. This situation won t occur in SEC as well in FRS. Both systems send a Swift MT942 only when there are transactions available. 25

30 5.5 Assumptions Amount B15 Using the data type Amount conforms to the Swift standard amount. The requirement for the maximum number of decimal places to use the ISO Currency Code is respected. However, the usage of Amount varies per source system and per tag. The most common number of decimal places in the ISO Currency Codes is 2. The table below shows the possible Amount layout variations and to which Swift tag they apply. The amount layout code is used in the detailed tag description. Amount Value Layout SEC FRS Layout code Round sum Amount with 1 decimal 0, Without decimals 61 0,00 Right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code 90D 90C 61 90D 90C 0,1 With 1 decimal B1 0,10 Right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code 61 90D 90C 61 90D 90C A0 AM BM Floor Limit The mechanism of Floor Limits is not used by the concerning channels. 5.6 Differences per tag The differences do not apply to the technical structure. This remains in line with the format description specified by Swift, unless stated explicitly. 26

31 5.7 Tag 20 Transaction Reference Number :20: Transaction Reference Number (TRN) V 1 This tag contains a unique number to identify the MT942 message. Field Form SEC FRS Transaction Reference Number Example X16 Form: A3-N6-N5 A3: ISO Currency code N6: Date creation message: YYMMDD (see also tag 13D) N5: Message sequence number (see also tag 28C) Sequence starts per creation date at 1 and is incremented by 1 per message. :20:EUR :20:EUR Form: N7/N7 N7: Bank reference number N7: Fixed number: 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). The Bank reference number doesn t apply to the logical content of the message. :20: / :20: / Tag 21 Related Reference :21: Related Reference O 1 If the MT 942 is sent in response to an MT 920 Request Message, this field must contain the field 20 Transaction Reference Number of the request message. Field Form SEC FRS Reference X16 Not used Form: X11 Contains default value ABNANL2AXXX unless other value available. Example n/a :21:ABNANL2AXXX 5.9 Tag 25 Account Number :25: Account Number V 1 Code assigned by the bank to uniquely identify an account. Field Form SEC FRS Account Number X35 Form: N10A3 Form: N9 N10 N10: Account Number with leading zero A3: ISO Currency code (see Annex 7.2 ISO Currency Code) N9: Account Number without leading zero N10: Account Number with leading zero One Account Number can be hold in several different currencies (ISO Currency code) Depending on the country where the account is hold the form can varies. Usage of leading zero is a client preference. Example :25: EUR :25: One Account Number can be hold in one currency (ISO Currency code) 27

32 5.10 Tag 28C Statement Number/Sequence Number :28C: Statement Number / Sequence Number V 1 This field contains the sequential number of the statement, optionally followed by the sequence number of the message within that statement when more than one message is sent for the statement. Field Form SEC FRS Statement Number / Sequence Number N5 [/N5] Form: N5/N5 N5: Statement Number /N5: Sequence Number (see also tag 20) Form: N5 N5: Statement number Example Sequence starts per creation date at 1 and is incremented by 1 per message. :28C:00251/00001 :28C:00251/00002 Sequence number is not used. :28C: Tag 34F Floor Limit (1) :34F: Floor Limit (first occurrence) V 1 This field specifies the minimum value (transaction amount) reported in the message. Field Form SEC FRS 1 ISO Currency code A3 2 Debit / Credit indicator [A1] Form: A1 Default value: D 3 Amount B15 Default value: 0, Default value: 0,00 Floor Limit (1) isn t used, however tag is reported. Example :34F:EURD0, :34F:EUR0,00 n/a Floor Limit (1) isn t used, however tag is reported. 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 5.12 Tag 34F Floor Limit (2) :34F: Floor Limit (second occurrence) O 1 This field specifies the minimum credit value (transaction amount) reported in the message. Field Form SEC FRS 1 ISO Currency code A3 2 Debit / Credit indicator A1 Form: A1 Tag Floor Limit (2) isn t used. Default value: C 3 Amount B15 Default value: 0, Floor Limit (2) isn t used, however tag is reported. Example :34F:EURC0, 28

33 5.13 Tag 13D Date/Time Indication :13D: Date/Time Indication V 1 This field indicates the date, time and time zone at which the report was created. Field Form SEC FRS 1 Date, YYMMDD N6 2 Time, HHMM N4 3 Time zone indicator X1 4 Time zone offset N4 Example :13D: :13D: Tag 61 Statement Line :61: Statement Line O 1 This tag contains the details of a transaction. Field Form SEC FRS 1 Value Date, YYMMDD N6 2 Booked Date, MMDD [N4] Form: N4 Date can change during final settlement, 3 Debit / Credit indicator A2 Form: A2: D (debit), C (credit), RD (Reverse Debit) of RC (Reverse Credit) 4 Funds Code [X1] n/a n/a 5 Amount B15 Layout code A0/BM. Round sum is reported without decimals. Amount with decimals are right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. 6 Transaction Type Code 7 Reference Account Owner A1X3 X16 Form: A1A3 F plus TTIC Code (see 9 Swift Transaction Type Identification Code) Default value: FTRF Default value NONREF unless other value available 8 Reference Bank [//X16] n/a n/a 9 Transaction Information n/a [X34] n/a n/a Form: A2: D (debit), C (credit), RD (Reverse Debit) of RC (Reverse Credit) Layout code AM/BM. The decimal part of the amount is right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. Form: A1A3 F plus TTIC Code (see 9 Swift Transaction Type Identification Code) Default value: FTRF Default value NONREF unless other value available SEC FRS Example :61: C ,FTRFNONREF :61: C97,50FTRFNONREF :61: D96651,97FTRFNONREF :61:101221C9792,00FTRFNONREF :61:101221C999,60FTRFNONREF :61:101221C3088,29FTRFNONREF 29

34 5.15 Tag 86 Transaction Information :86: Transaction Information O 6 Additional information to the account owner about the transaction. Field Form SEC FRS Description X65 Maximum 6 x 65 = 390 positions There is no formal formatting. Maximum 9 x 32 = 288 positions are available. Possible text in the first line: [BETALINGSKENM.] [BUIT.BET.REF.] [SEPA BETALING] [SPOEDBETALING] [TOTAAL TERUGBOEKINGEN RUN VOOR COMPRIMEREN: POSTEN] Counterparty account number Where applicable tag 86 indicates the counterparty account number for a transaction. Bank account numbers are reported with 10 digits, leading zero included. Postbank account numbers begins with letter P followed by 9 digits. This number is right aligned with the last digit on position 14. Counterparty account number When submitting transactions, tag 86 indicates, where applicable, the counterparty account number for a transaction. Bank account numbers are specified using full stops, e.g of , and are always preceded by a space. Postbank account numbers use the word GIRO, e.g. :86:GIRO , 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 thus: :86:GIRO , without leading spaces. Example 1 e row of tag 86 Transaction Information SEC :86: P.D.I. DE GROOT PERCEEL 4899RB99 :86:P HR S PETERS BETALINGSKENM :86:BUIT.BET.REF IFN FINANCE BV FRS :86: VAN AALTEN :86:GIRO ABNAMRO.NL :86:FR LA FRANCE 30

35 5.16 Tag 90D Number and Sum Debit of Entries :90D: Number and Sum Debit of Entries O 1 This field indicates the total number and amount of debit entries. Field Form SEC FRS 1 Number N5 Form: N5 Form: N5 2 ISO Currency code A3 3 Amount B15 Layout code A0/BM. Round sum is reported without decimals. Amount with decimals are right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. Layout code AM/BM. The decimal part of the amount is right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. Tag is always reported Tag is only reported when there debit transactions Example :90D:00000EUR0, :90D:00001EUR , :90D:00002EUR2286,10 :90D:00003EUR2287,09 Not available 5.17 Tag 90C Number and Sum Credit of Entries :90C: Number and Sum Credit of Entries O 1 This field indicates the total number and amount of credit entries. Field Form SEC FRS 1 Number N5 Form: N5 Form: N5 2 ISO Currency code A3 3 Amount B15 Layout code A0/BM. Round sum is reported without decimals. Amount with decimals are right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. Layout code AM/BM. The decimal part of the amount is right aligned and filled with zeros till the maximum count of decimals defined for the concerning ISO Currency code. Tag is always reported Tag is only reported when there credit transactions Example :90C:00000EUR0, :90C:00001EUR , :90C:00003EUR187931,60 :90C:00005EUR102756,73 :90C:4EUR1355,10 :90C:2EUR3021, Tag 86 Information to Account Owner :86: O 1 This field contains additional information about the statement as a whole. It is to be passed on to the account owner. Field Form SEC FRS Description X65 Not used Default value /ACSI/ABNANL2AXXX Example n/a :86:/ACSI/ABNANL2AXXX 31