Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Implementation guide
Table of contents
1 INTRODUCTION ...................................................................................................................................... 3
1.1 1.2 Definitions ........................................................................................................................................................3 History ..............................................................................................................................................................3
2.3
2.2.1.1 Example bookings on the account statement ................................................................................6 2.2.1.2 Example MT940 compared to Extended MT940..............................................................................6 2.2.1.3 File example MT940 ..........................................................................................................................7 2.2.1.4 File example MT940XS......................................................................................................................7 Restrictions to the service ................................................................................................................................8
CONDITIONS.....................................................................................................................................................................8 GENERAL LIMITATIONS...................................................................................................................................................8 INFORMATION NOT REPORTED IN THE SERVICE.......................................................................................................8 COUNTRY SPECIFIC SWEDEN .......................................................................................................................................8 COUNTRY SPECIFIC NORWAY.......................................................................................................................................9 COUNTRY SPECIFIC GERMANY.....................................................................................................................................9 COUNTRY SPECIFIC GREAT BRITAIN ...........................................................................................................................9 COUNTRY SPECIFIC THE NETHERLANDS ....................................................................................................................9
2.4
2.4.1 2.4.2 2.4.3 2.4.4
Agreement........................................................................................................................................................9
EXTENDED INFORMATION..............................................................................................................................................9 ACCOUNT NUMBER .........................................................................................................................................................9 COMMUNICATION METHODS .........................................................................................................................................9 LOCAL AGREEMENTS NEEDED FOR THE SERVICE:...................................................................................................9
2.5
Implementation guide
1 Introduction
This document contains information about the service Extended Account statement in MT940 format. Extended Account statement manages balances and detailed payment information for incoming and outgoing commercial payments for Norway, Sweden, Denmark, Finland, Germany, Great Britain and The Netherlands. The format are based on SWIFT MT940 which is a standard defined by the SWIFT organisation. The difference from an ordinary (Nordic) SWIFT MT940 is that transactions included in batch bookings/lump sums are reported as separate items in the extended account statement and are presented as individual transactions with detailed payment information. The information can be delivered to the company on file or via the SWIFT network, for further processing in the companys business system.
1.1
Term BBAN
Definitions
Description BBAN stands for Basic Bank Account Number and identifies a unique national bank account number. A BBAN can comprise up to 30 characters and can be alphanumeric. An international IBAN is created based on a BBAN. IBAN stands for International Bank Account Number and consists of a country code, a control digit, a bank identifier and a national account number. A Swedish IBAN is made up of 24 characters in total and a foreign IBAN can be up to 34 characters. SWIFT is the abbreviation of Society for Worldwide Interbank Financial Telecommunication and is a communications network used by most of the banks in the world for sending each other payment instructions and messages. Bank Identifier Code, 8 or 11 characters. A unique address linked to SWIFT.
IBAN
SWIFT
BIC
1.2
0.1.2 0.1.1
History
Date 2008-12-12 2008-10-28 May 2007 Description Finland: New code in field 61/6 for local Sweeping, CMS Extended Account statement SWIFT MT940XS-format Extended Account statement SWIFT MT940E and MT940X-format
Version
Implementation guide
2.1
Availability
Account statements are sent on a daily basis, Monday to Friday, on banking days in the country where the account is operated. The frequency of delivery cannot be changed. In the event of technical problems causing a delay, the file is sent to the customer as soon as the error has been corrected. In the event of technical problems causing an incorrect account statement, the ambition is always to send a new correct account statement for the affected account to the customer as soon as the error has been corrected.
2.2
The information can be delivered in various ways, directly via the SWIFT network or by file transfer. Handelsbanken can accommodate most of the communication methods used in the market. Companies can download their files using our online service, or automatically via TCP/IP FTP. The delivery time by file transfer is between 06.45 CET and 08.15 CET.
If nothing else is agreed, all account statements (i.e. from all countries) are sent in the same file.
Implementation guide
2.2.1
EXAMPLE
All bookings on the account are combined and matched with different sources of payment information as for example incoming Bankgiro payments, incoming payments via SWIFT MT103 and the companys file with outgoing payments to be executed. Transactions included in lump sums booked on the account are separated in the extended account statement and presented as individual items with detailed payment information. This is described in the examples below.
Implementation guide
2.2.1.1
Example bookings on the account statement Value date 080103 080103 080103 080103 080103 Text Opening balance 56789876 BGINB 292822779876 ABOL Fil bet Fil-E Closing balance 36198,70 70884,00 -7100,00 199982,70 Amount (SEK) Balance (SEK) 100000,00
Example of standard MT940 and the extended MT940, account with Handelsbanken SE. The two versions show the same transactions, the standard MT940 with lump sums and no detailed payment information. The extended MT940 with each transaction specified with detailed payment information.
Field 20 25 28C 60F 61 86 61 86 61 86 61 86
0801030103D7100,NMSCFil Bet//6000 FIL-E 0801030103C70884,NTRF292822779876//60001ABOL 987654321 2/1 C080103SEK100000, 0801030103C36198,7NTRF00000056789876//6091 BGINB
Standard MT940
556677889960008
61 86 61 86 62F 64
C080103SEK199982, C080103SEK199982,
C080103SEK199982,7 C080103SEK199982,7
Lump sums are shown for bankgiro payments for example. Extended information/detailed information is not shown for the transactions.
4: :20:556677889960008 :25:987654321 :28C:2/1 :60F:C080103SEK100000, :61:0801030103C36198,7NTRF00000056789876//6091 BGINB :61:0801030103C70884,NTRF292822779876//60001ABOL :61:0801030103D7100,NMSCFil Bet//6000 FIL-E :62F:C080103SEK199982, :64:C080103SEK199982, - 2.2.1.4 File example MT940XS
Lump sums, for example for bankgiro payments and other local payments, are shown as separate items and presented in the account statement as individual transactions with detailed payment information. Other transactions (for example cross border payments) are presented with extended/detailed payment information.
4: :20:556677889960008 :25:987654321 :28C:2/1 :60F:C080103SEK100000,00 :61:0801030103C3500,NLOC015543005551//6091 BGINB :86:/REMI/807656677 +3500,00 :61:0801030103C1115,NLOC065531002226//6091 BGINB :86:/REMI/8001536529 +1115,00 /ORDP/COMPANY AB TEST STOCKHOLM :61:0801030103C31583,7NLOC495540105541//6091 BGINB :86:/REMI/8000172780 +31583,70 /ORDP/BOLAGET NORR AB UME :61:0801030103C70884,NCRO20482176//64501ABOL :86:/REMI/Faktura 800678633428 Kundenr. 56990368 /ORDP/Testing Communication A/S /BENM/BOLAGET AB /CHG1/SEK20, /OCMT/SEK70904,/ /ORDB/JYBADKKK :61:0801030103D7000,NLOC100045620077//6000 FIL-E BG22227777 :86:/REMI/160555 /BENM/BILBOLAGET BODEN AB :61:0801030103D100,NLOC100045620078//6000 FIL-E BG22227777 :86:/REMI/4567899944 /BENM/GTEBORGS BOLAGET AB :62F:C080103SEK199982, :64:C080103SEK199982, -
Implementation guide
2.3
2.3.1
In order to report extended information for outgoing payments, all outgoing payments must be sent to Handelsbanken by file transfer. Manual payments initiated on the Internet or a branch cannot be reported with extended/detailed payment information. Manual payments on the Internet are coded with standard SWIFT transaction type codes in field 61/6. The bank recommends the customer to provide a unique reference for each payment in the file. The unique reference is returned in field 61, sub-field 7 in the extended account statement. If the reference contains more than 16 characters the reference is stated in field 61, sub-field 9 instead, in these cases NONREF is stated in sub-field 7.
GENERAL LIMITATIONS
2.3.2
Batch bookings (several payments booked as one transaction) are separated and each individual payment is shown as one item in the statement. In those cases where one or more transactions on the account cannot be matched, these are reported as a lump sum with the original reference and code. This applies to both debit and credit information. Payment and account information are matched as far as possible by unique references. If there is no unique reference, a match can be made using the amount. If several transactions have the same amount and no unique reference, there is a risk that matching is not possible. Batch bookings cannot be matched and specified if the sum of the individual payments is larger than the booked amount. In this case, the original amount and transaction reference is presented. All transactions booked to the account, in addition to supplier and customer payments, are reported in the same way in the extended account statement as in the regular account statement. Examples of this type of transaction are salary payments, individual withdrawals, and cash deposits. Extended information about these transactions is not reported.
INFORMATION NOT REPORTED IN THE SERVICE
2.3.3
Salary payments in Sweden and Finland are reported as normal transactions/lump sums without any detailed payment information. It is not possible to obtain detailed information about interest data. Interest transactions will be reported as ordinary transactions on the statement, in most cases with the code INT in field 61, subfield 6. Incoming financial and intra-group payments cannot always be reported with detailed extended payment information. If the payment information, for some reason, cannot be matched with a transaction on the account statement the transaction are reported as a normal booking/lump sum without extra/detailed information. Payments manually initiated on the internet or a branch cannot be reported with detailed payment information in the extended account statement.
COUNTRY SPECIFIC SWEDEN
2.3.4
Extended Debit/Credit information for Swedish Plusgiro transactions cannot be reported. Paper statements, concerning paper-based incoming payments, cannot be sent to the customer. The information can be found on the Internet instead. OCR numbers can be reported several times in the same payment. If the payer pays several invoices in one payment, this may lead to the same OCR number being reported several times. This is because the BGC reports all information, i.e. all references/OCR numbers stated by the payer in the payment and that the BGC also reports separately the OCR numbers that are correct following a check against the OCR agreement. If the payer pays one invoice per payment the reference is only shown once.
Page 8 (53) Publishing date 12 December 2008
Implementation guide
Extended information for Swedish Direct debit transactions (Autogiro AG) cannot be reported. The lump sum with direct debits are shown on the account. To include outgoing cross-border payments sent in UTLI file format in the account statement, the company must select individual payments.
COUNTRY SPECIFIC NORWAY
2.3.5
Extended information for Norwegian Direct debit transactions (Autogiro AU) cannot be reported. The lump sum with direct debits are shown on the account.
COUNTRY SPECIFIC GERMANY
2.3.6
To include details about outgoing local payments in Germany a separate agreement must be made with the respective country for individual payments to be booked on the account.
COUNTRY SPECIFIC GREAT BRITAIN
2.3.7
Extended debit information such as the companys own reference per payment cannot be reported.
COUNTRY SPECIFIC THE NETHERLANDS
2.3.8
To include details about incoming payments in the Netherlands a separate agreement must be made with the branch for individual payments to be booked on the account. To include details about outgoing local payments in the Netherlands a separate agreement must be made with the respective country for individual payments to be booked on the account.
2.4
2.4.1
Agreement
EXTENDED INFORMATION
It is possible to include extended information/details about incoming payments, outgoing payments or both in the account statement. Note that all transactions, i.e. both credits and debits, always are presented in the statement irrespective of what is agreed about the details.
2.4.2 ACCOUNT NUMBER
The account number in field 25 can be presented either as BBAN or as IBAN, this is agreed upon in the agreement.
2.4.3 COMMUNICATION METHODS
There are different communication methods to be used for file transfers from the bank, for example the file can be delivered to an online inbox on the Internet or to a home directory (i.e. the company downloads the file automatically via TCP/IP FTPS). Your local branch can provide more information about the communication methods supported by Handelsbanken.
2.4.4 LOCAL AGREEMENTS NEEDED FOR THE SERVICE:
SWIFT MT940 must be sent via SWIFT from the local branch to Handelsbanken Sweden (HANDSESS). This is agreed upon with the local branch in the respective country.
To include details about incoming payments in Sweden a file with Incoming Bankgiro payments (Bg Inbetalningar) in BgMax file format must be sent to Handelsbanken Sweden. This is agreed with the local branch in Sweden. To include outgoing cross-border payments sent in UTLI file format in the account statement, the company must select individual payments in the agreement.
Norway:
To include details about incoming payments in Norway an EDIFACT CREMUL file must be sent to Handelsbanken Sweden. This is agreed with the local branch in Norway.
The Netherlands:
To include details about incoming payments in the Netherlands a separate agreement must be made with the branch for individual payments to be booked on the account. To include details about outgoing local payments in the Netherlands a separate agreement must be made with the local branch for individual payments to be booked on the account.
Germany
To include details about outgoing local payments in Germany a separate agreement must be made with the local branch for individual payments to be booked on the account.
2.5
Technical requirements Requirements to the ERP system when implementing Extended MT940: The ERP-system must support the Standard MT940 as per the SWIFT standard with the following exceptions/additions: - The following special characters can appear in the MT940XS file format (not allowed in the SWIFT system): , , , , , , , , , , , , , &, *, %,: - There are not any hard limitations on the maximum amount of lines and characters that field 86 can consist of. This means that this field can consist of nearly an unlimited amount of lines and characters. A zero payment might occur. Start and ending of each account in the file: Every account in the file is separated as shown below. {4: is translated to 4: in the file. -} is translated to in the file. I.e. the receiving system must be able to handle the file with start 4: and ending -. Example:
4: :20:5566778899100112 :25:123456789 :28C:188/1 :60F:C070928SEK0, :62F:C070930SEK0, :64:C070930SEK0, - 4: :20:5566778899100169 :25:337788999 :28C:188/1 :60F:C070928SEK0, :62F:C070930SEK0, :64:C070930SEK0, - Extended Account statement MT940XS Version 0.1.2 Page 10 (53) Publishing date 12 December 2008
Implementation guide
3 Implementation guidelines
3.1
M Not used M M M O O M O
Status
M = Mandatory O = Optional
Explanations: = alphabetic letters a c = alphabetic letters and digits = amount, must contain one digit and comma (,), ex 15d = maximum 15 digits includings the d decimal comma = character x n = digits, ex. 2n = up to 2 digits ! = always, ex 1!a =always 1 alphabetic letter / = slash [] = subfield
Implementation guide
3.2
3.2.1
Format
16x
Presence
Mandatory
Definition
This field specifies the reference assigned by the Sender to unambiguously identify the message.
3.2.2 FIELD 21: RELATED REFERENCE
Format
16x
Presence
Format
35x
Presence
(Account)
Mandatory
Definition
This field identifies the account for which the statement is sent. The account can be presented either with BBAN or with IBAN. This is decided when setting up the agreement.
3.2.4 FIELD 28C: STATEMENT NUMBER/SEQUENCE NUMBER
Format
5n[/5n]
Presence
Mandatory
Definition
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 one statement. The statement number will be reset to 1 on 1 January of each year. Both the statement number and the sequence number enable the Receiver to put the different messages into sequence and thus form the complete statement.
Implementation guide
Example: The first message of a statement is :28C:235/1 The second message is :28C:235/2 and so on.
3.2.5 FIELD 60A: OPENING BALANCE (BOOKED FUNDS)
Format
Option F Option M
Presence
1!a6!n3!a15d 1!a6!n3!a15d
(D/C Mark) (Date) (Currency) (Amount) (D/C Mark) (Date) (Currency) (Amount)
Mandatory
Definition
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.
Codes
Usage rules
This field must always be the same as field 62a (closing balance) of the previous customer statement message for this account. The first customer statement message for a specified period must contain field 60F (first opening balance); additional statement messages for the same statement period must contain field 60M (intermediate opening balance). The date is expressed as YYMMDD. The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the maximum length.
3.2.6 FIELD 61: STATEMENT LINE
Format
Implementation guide Subfield 5 6 7 8 9 Presence Format 15d 1!a3!c 16x [//16x] [34x] Name Amount Transaction Type Identification Code Reference for the Account Owner (e.g. reference from incoming MT101 tag 21) Account Servicing Institution's Reference Supplementary Details
Optional
Definition
Subfield 3, Debit/Credit Mark, must contain one of the following codes (Error code(s): T51):
D C RC RD Codes Debit Credit Reversal of credit (debit entry) Reversal of debit (credit entry)
Subfield 6, Transaction Type Identification Code, may be completed in one of three ways (Error code(s): T53): 1. For entries related to SWIFT transfer instructions and subsequent charge messages: Format: S3!n The last three characters will indicate the message type of the SWIFT message causing the entry (for debit entries) or the message type of the SWIFT message used to advise the account owner (for credit entries) 2. For entries related to payment and transfer instructions, including related charges messages, not sent through SWIFT or where an alpha description is preferred: Format: N3!c 3. For entries being first advised by the statement (items originated by the account servicing institution): Format: F3!c
Implementation guide Codes used in DK, FI, DE, GB, NL, NO, SE
The list consists of both SWIFT standard codes and Handelsbanken codes When formats (2) or (3) are used, the last three characters, i.e., 3!c, may contain one of the following codes:
Code BOE BRF CHG CHK CHQ CLR CMI CMN CMS CMT CMZ Explanation Bill of exchange Courtage Charges and other expenses Cheques Cheques Cash letters/Cheques remittance Cash management item - No detail Cash management item - Notional pooling Cash management item - Sweeping Cash management item -Topping Cash management item - Zero balancing Used in country Not used SE DK, FI, DE, GB, NL, NO, SE DK*, FI GB SE Not used NL DK, NL, FI NL, Local zero balancing: DK, DE, GB (debit transaction only), NL, SE Comment local zero balancing transactions: GB credit transaction coded FTRF NO - coded TRF SE FI, SE SE NL SE - debits and lump sums with credits FI, SE Not used SE, NO DK, FI, DE, GB, NL, NO, SE Not used NL, SE DK, FI, DE, NL, SE NL, SE
Collections (used when entering a principal amount) Commission Documentary credit (used when entering a principal amount) Direct Debit Dividends-Warrants Equivalent amount Foreign exchange Interest Lock box Loan deposit Miscellaneous Returned item
Implementation guide
Explanation Securities (used when entering a principal amount) Standing order Transfer, payment Value date adjustment (used with an entry made to withdraw an incorrectly dated entry it will be followed by the correct entry with the relevant code) Transaction initiated via SWIFT MT103 Transaction initiated via SWIFT MT700 Issue of a documentary credit (documentary credits & guarantees) Cross-border (outgoing and incoming payments)
Used in country FI, SE FI, NL, SE DK, FI, DE, GB, NL, NO, SE SE
DK DK
NCRO
Outgoing payments (made by file): DK, FI, DE, NL, NO, SE Comment outgoing c-b payments: GB coded FTRF Incoming payments: DK, FI, NO, SE Comment incoming c-b payments: DE coded FTRF NL coded FMSC GB coded FTRF
Cross-border urgent payment (outgoing) Cross-border intra group payment (outgoing) Financial cross-border payment (outgoing) Local intra group payment (outgoing) Financial local payment (outgoing) Local payment (outgoing and incoming)
Outgoing payments (made by file): DK, FI, DE, NL, NO, SE Outgoing payments (made by file): DK, FI, DE, NL, NO, SE Outgoing payments (made by file): DK, FI, DE, NL, NO, SE Outgoing payments (made by file): DK, FI, DE, GB, NL, NO, SE Outgoing payments (made by file): DK, FI, DE, GB, NL, NO, SE Outgoing payments (made by file): DK, FI, DE, GB, NL, NO, SE Incoming payments: FI, NO, SE Comment local incoming payments: DE coded FTRF NL coded FMSC GB coded FTRF DK see below
NLOU NOCR
Outgoing payments (made by file): DK, FI, DE, GB, NL, NO, SE FI Reference giro payment NO KID payment Page 16 (53) Publishing date 12 December 2008
Implementation guide Code NK71 NK73 NK75 NGIR Explanation Joint payment forms 71 (incoming local payment) Joint payment forms 73 (incoming local payment) Joint payment forms 75 (incoming local payment) GIRO (incoming local payment) Used in country DK Payment form FI, code 71 DK Payment form FI, code 73 DK Payment form FI, code 75 DK Payment form Giro, codes 04, 15, 41 NO Giro payment Incoming payments: DK Bank transfer, incoming local payment NO Other local incoming payments Outgoing local payments (made on the Internet) DK, SE, FI, NO FTRF Transfer DE Incoming cross-border payment DE Incoming local payment DE Outgoing local payment (made on the Internet) GB Incoming cross-border payment GB Incoming local payment GB Outgoing cross-border payment GB Outgoing local payment (made on the Internet) FMSC Miscellaneous NL Incoming cross-border payment NL Incoming local payment NL Outgoing local payment FI
NTRF
NTAX
* Incoming cheques in Denmark can be coded either CHK or TRF. Please note: Transactions and payments made on the Internet are always coded with SWIFT standard codes.
Implementation guide
3.2.7
Format
Unlimited. There are not any hard limitations on the maximum amount of lines and characters in this field. This means that Handelsbanken shows all details/all reference information that exists for the transaction, i.e. all information that is forwarded from the payment systems is stated in this field.
Presence
Optional
Definition
This field contains additional information on the transaction detailed in the preceding statement line and which is to be passed on to the account owner.
Usage rules
Handelsbanken presents one code word in each line, except for charges where several code words can appear on the same line. The information after the code word OCMT will be followed by a slash (/).
Example:
:86:/REMI/INVOICE NO. 177566 DATE 04.09.2008 /ORDP/EXPORT INDUSTRIES /BENM/COMPANY SWEDEN AB /CHG2/SEK25,/CHG4/EUR10, /OCMT/SEK15717,5/ /ORDB/CNRBINBB
These Handelsbanken codes below are used in field 86. The codes are presented in priority order.
Code REMI ORDP Explanation Remittance information Ordering Part Direction Outgoing/Incoming payment Outgoing/Incoming payment For incoming payments, debit account is displayed when present. BENM Beneficiary Outgoing/Incoming payment Beneficiary is displayed if different from account owner. For outgoing payments, credit account is displayed when present. CHGS Charges Outgoing/Incoming payment For outgoing cross-border payments, the allocation of charges is displayed CHG1 Charges - commission Outgoing/incoming payment
Implementation guide
Code CHG2
Explanation Charges commission periodic debit (debited separately for example on a monthly basis) Charges correspondent bank Charges during processing (sending bank) Charges intermediary bank Original amount Exchange rate Ordering bank BIC Code Beneficiary bank BIC Code or Party Identifier (BLZ, FW) Correspondent bank BIC Code
Outgoing payment Incoming payment Outgoing/Incoming payment Outgoing/Incoming payment Outgoing/Incoming payment Incoming payment Outgoing payment Outgoing payment
Format
Option F Option M
Presence
1!a6!n3!a15d 1!a6!n3!a15d
(D/C Mark) (Date) (Currency) (Amount) (D/C Mark) (Date) (Currency) (Amount)
Mandatory
Definition
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.
Codes
Usage rules:
The content of this field will be repeated in field 60a of the subsequent customer statement message for this account. If there is only one customer statement message transmitted for the period, this field must use tag option F, i.e., 62F (final closing balance). When several messages are transmitted for the same statement period, all messages except the last message must contain field 62M (intermediate closing balance); the last message of the statement must contain field 62F. The date is expressed as YYMMDD. The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the maximum length.
Implementation guide
3.2.9 FIELD 64: CLOSING AVAILABLE BALANCE (AVAILABLE FUNDS)
Format
1!a6!n3!a15d
Presence
Optional
Definition
This field indicates the funds available to the account owner (if credit balance) or the balance, which is subject to interest charges (if debit balance).
Codes
Usage rules:
The date is expressed as YYMMDD. The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the maximum length.
Implementation guide
4.1
Denmark
62F 64
File example Incoming cross-border payment 4: :20:5566778899042235 :25:08901234567 :28C:123/1 :60F:C080326DKK123234,96 :61:0803260325C29970,NCRO0880103M72615621//0326132225123477 :86:/REMI/29970, 0880103M72615621 INVOICES 300544,300545 /ORDP/GERMANY GMBH STRASSE 500 DE-FRANKFURT /BENM/TESTCOMPANY DENMARK A/S :62F:C080326DKK153204,96 :64:C080326DKK153204,96 - Extended Account statement MT940XS Version 0.1.2 Page 21 (53) Publishing date 12 December 2008
Implementation guide
File example Incoming local payment, payment form FI code 71 4: :20:5566778899042235 :25:08901234567 :28C:123/1 :60F:C080326DKK123234,96 :61:0803260326C12000,56NK71INDBETAL.KORT//0326140456983457 :86:/REMI/0000000000403002193 +12000,56 :62F:C080326DKK135235,52 :64:C080326DKK135235,52 -
Implementation guide
Statement Number/Sequence Number 123/1 Opening Balance Value Date (YYMMDD) Entry Date (MMDD) Debit/Credit Mark Funds Code Amount Transaction Type Identification Code Reference for the Account Owner Account Servicing Institutions Reference Supplementary Details Information to Account Owner /REMI/+8000,65 DANSKE BOLAG A/S Faktura 2697932,2697933,2698044 Faktura 2698123,2698124,2698156 Faktura 2698201,2699522,269965 Kreditnota 9025180,902593 /ORDP/DANSKE BOLAG A/S TESTVEJ 1234 KBENHAVN C080326DKK131235,61 C080326DKK131235,61 8000,65 NTRF DANSKE BOLAG A/S //0326142546321587 C080326DKK123234,96 080326 0326 C
62F 64
File example Incoming payment, bank transfer 4: :20:5566778899042235 :25:08901234567 :28C:123/1 :60F:C080326DKK123234,96 :61:0803260326C8000,65NTRFDANSKE BOLAG A/S//0326142546321587 :86:/REMI/+8000,65 DANSKE BOLAG A/S Faktura 2697932,2697933,2698044 Faktura 2698123,2698124,2698156 Faktura 2698201,2699522,269965 Kreditnota 9025180,902593 /ORDP/DANSKE BOLAG A/S TESTVEJ 1234 KBENHAVN :62F:C080326DKK131235,61 :64:C080326DKK131235,61 -
Implementation guide
Statement Number/Sequence Number 123/1 Opening Balance Value Date (YYMMDD) Entry Date (MMDD) Debit/Credit Mark Funds Code Amount Transaction Type Identification Code Reference for the Account Owner Account Servicing Institutions Reference Supplementary Details Information to Account Owner /REMI/INVOICE NO 123890543 /BENM/SVERIGE AB SE4030000000016601238827 /CHGS/SHA /OCMT/SEK15000,/ /EXCH/80,29 /BENB/NDEASESS C080326DKK111191,46 C080326DKK111191,46 12043,5 NCRO REMITTER REF 001 //0326132225123456 C080326DKK123234,96 080326 0326 D
62F 64
File example Outgoing cross-border payments 4: :20:5566778899042235 :25:08901234567 :28C:123/1 :60F:C080326DKK123234,96 :61:0803260326D12043,5NCROREMITTER REF 001//0326132225123456 :86:/REMI/INVOICE NO 123890543 /BENM/SVERIGE AB SE4030000000016601238827 /CHGS/SHA /EXCH/80,29 /BENB/NDEASESS :62F:C080326DKK111191,46 :64:C080326DKK111191,46 -
Implementation guide
62F 64
File example Outgoing local payment 4: :20:5566778899042235 :25:08901234567 :28C:123/1 :60F:C080326DKK123234,96 :61:0803260326D5000,NLOCREMITTER REF 002//0326132545124985 :86:/REMI/Invoice 4568877 /BENM/COMPANY A/S 31008812666 /ORDP/Testcompany Denmark A/S :62F:C080326DKK118234,96 :64:C080326DKK118234,96 -
Implementation guide
4.2
Finland
File example Incoming local payment, OCR payment (Reference giro) 4: :20:5566778899042235 :25:31313001122334 :28C:123/1 :60F:C080326EUR4524492, :61:0803260326C110,54NOCR0000044000950055//03105 LM 245887 :86:/REMI/44000950055 /ORDP/PETRI FINSK :62F:C080326EUR4524602,54 :64:C080326EUR4524602,54 -
Implementation guide
62F 64
File example Incoming cross-border payments 4: :20:5566778899042235 :25:31313001122334 :28C:123/1 :60F:C080326EUR4524492, :61:0803260326C437,25NLOCNONREF//09025E0265485699 :86:/REMI/TEST COMPANY FINLAND OY LASKU 12456 437,25 /ORDP/HELSINKI COMPANY OY :62F:C080326EUR4524929,2 :64:C080326EUR4524929,2 -
Implementation guide
Account Servicing Institutions Reference //0212313190U45774 Supplementary Details Information to Account Owner /REMI/313190U45774 PANO/INSATTN EUR 2551,50 MAKSU/UPPDR. EUR 2551,50 ULK.AROPV/UTL.VALUT.DAG 25.03.2008 45688+45698+45706 /ORDP/DEUTSCHE GMBH C020129EUR4527043,5 C020129EUR4527043,5
62F 64
File example Incoming cross-border payment 4: :20:5566778899042235 :25:31313001122334 :28C:123/1 :60F:C080326EUR4524492, :61:0803260326C2551,5NCRONONREF//0212313190U45774 :86:/REMI/313190U45774 PANO/INSATTN EUR 2551,50 MAKSU/UPPDR. EUR 2551,50 ULK.AROPV/UTL.VALUT.DAG 25.03.2008 45688+45698+45706 /ORDP/DEUTSCHE GMBH :62F:C080326EUR4527043,5 :64:C080326EUR4527043,5 -
Implementation guide
File example Outgoing local payment 4: :20:5566778899042235 :25:31313001122334 :28C:123/1 :60F:C080326EUR4524492, :61:0803260326D160,NLOCREMITTER REF 201//02013131LM912345 :86:/REMI/2233344 +100,00 20233358 +60,00 /BENM/COMPANY FINSKA OY 12885000245880 :62F:C080326EUR4524332, :64:C080326EUR4524332, -
Implementation guide
62F 64
File example Outgoing cross border payment 4: :20:5566778899042235 :25:31313001122334 :28C:123/1 :60F:C080326EUR4524492, :61:0803260326D980,NCROREMITTER REF 301//02013131190U29085 :86:/REMI/458578 +980,00 /BENM/FACTORY GMBH AT072400055942234880 /CHGS/SHA /OCMT/EUR980,/ /BENB/BKAUATWWXXX :62F:C080326EUR45235512, :64:C080326EUR45235512, -
Implementation guide
4.3
Germany
62F 64
File example Incoming local payment 4: :20:5566778899042235 :25:0010612345 :28C:123/1 :60F:C080326EUR350000, :61:0803260326C854,4FTRFDTA/29628/01025//G010321 DTA/29628/01025 :86:FRANKFURTER FABRIKEN KUNDENNUMMER 1234 INVOICE 6543 :62F:C080326EUR350854,4 :64:C080326EUR350854,4 -
Implementation guide
62F 64
File example Outgoing local payment 4: :20:5566778899042235 :25:0010612345 :28C:123/1 :60F:C080326EUR350000, :61:0803260326C8651,83FTRF20070118/0927/2//G003214 20070118/0927/2 :86:TESTCOMPANY LTD PO BOX 300 MANCHESTER BA 14 1XX ENGLAND INVOICE A89999 :62F:C080326EUR358651,83 :64:C080326EUR358651,83 -
Implementation guide
File example Outgoing local payment 4: :20:5566778899042235 :25:0010612345 :28C:123/1 :60F:C080326EUR350000, :61:0803260326D972,34NLOCREMITTER REF 123//G076141 IZ/MCI-G/7588079999 :86:/REMI/00022344 00022345 00022346 /BENM/VON TEST CUSTOMER GMBH 943543000 :62F:C080326EUR349027,66 :64:C080326EUR349027,66 -
Implementation guide
62F 64
File example Outgoing local payment 4: :20:5566778899042235 :25:0010612345 :28C:123/1 :60F:C080326EUR350000, :61:0803260326D42490,31NCROREMITTER REF 129//G045042 BUTI980000069212 :86:/REMI/INVOICE NO A-456789 CUSTOMER 556699-AB /BENM/STOCKHOLM BOATING AB /ORDP/TESTCOMPANY GERMANY GMBH /CHGS/SHA /OCMT/EUR42490,31/ /BENB/ESSESESS :62F:C080326EUR392490,31 :64:C080326EUR392490,31 -
Implementation guide
4.4
Great Britain
File example Outgoing local payment 4: :20:5566778899042235 :25:12345678 :28C:123/1 :60F:C080326GBP600000, :61:0803260326C78,5FTRFB/O LONDON BRIDG E LTD :62F:C080326GBP600078,5 :64:C080326GBP600078,5 -
Implementation guide
File example Outgoing local payment 4: :20:5566778899042235 :25:12345678 :28C:123/1 :60F:C080326GBP600000, :61:0803260326C11845,35FTRFB/O BRUSSELS SA BELGIUM :86:DOC.NO11001222 DOC.NO 11001223 :62F:C080326GBP611845,35 :64:C080326GBP611845,35 -
Implementation guide
File example Outgoing local payment 4: :20:5566778899042235 :25:12345678 :28C:123/1 :60F:C080326GBP600000, :61:0803260326D606,88NLOCREMITTER REF 523//0628414311845100 :86:/REMI/16211 16210 /BENM/TESTCOMPANY 1 UK LTD 11464930 :62F:C080326GBP599399,12 :64:C080326GBP599399,12 -
Implementation guide
Please note:
Outgoing cross border payments in the UK can not be matched towards the file with payments, i.e. the own reference (remitter ref) from the transaction in the payment file can not be reported in the account statement. Incoming cross border payments in the UK will be coded FTRF in field 61/6.
File example Outgoing cross-border payment 4: :20:5566778899042235 :25:12345678 :28C:123/1 :60F:C080326GBP600000, :61:0803260326D303,74FTRFTESTCOMPANY OY :86:EUR 457,78 0,6635 :62F:C080326GBP599696,26 :64:C080326GBP599696,26 -
Implementation guide
4.5
Norway
File example Incoming local payment, GIRO payment 4: :20:5566778899042235 :25:90462312323 :28C:123/1 :60F:C080326NOK8513000, :61:0803260326C10000,NGIRNONREF//9999999994 :86:/REMI/INV4509 /ORDP/COMPANY A AS OSLO 3201000000 :62F:C080326NOK8523000, :64:C080326NOK8523000, -
Implementation guide
62F 64
File example Incoming local payment, electronic payment 4: :20:5566778899042235 :25:90462312323 :28C:123/1 :60F:C080326NOK8513000, :61:0803260326C20000,NLOCNONREF//797999998 52247360000 :86:/REMI/31208588 +7000,00 31208596 +8000,00 31208632 +3000,00 31208621 +2000,00 /ORDP/COMPANY B AS OSLO 18500500000 :62F:C080326NOK8533000, :64:C080326NOK8533000, -
Implementation guide
File example Incoming OCR payment (KID) 4: :20:5566778899042235 :25:90462312323 :28C:123/1 :60F:C080326NOK8513000, :61:0803260326C1000,NOCRNONREF//090000000 01220106633 :86:/REMI/05215332 +1000,00 :62F:C080326NOK8514000, :64:C080326NOK8514000, -
Implementation guide
File example Incoming cross-border payment 4: :20:5566778899042235 :25:90462312323 :28C:123/1 :60F:C080326NOK8513000, :61:0803260326C300000,NCRONONREF//999999995 09050100453 :86:/REMI/INVOICE NO 1478-99 /ORDP/R & SONS NEW YORK 84460331047 :62F:C080326NOK8813000, :64:C080326NOK8813000, -
Implementation guide
File example Outgoing local payment 4: :20:5566778899042235 :25:90462312323 :28C:123/1 :60F:C080326NOK8513000, :61:0803260326D100000,NLOCREMITTER REF 101//999999991 87917890000 :86:/REMI/4563 +1000000,00 /BENM/COMPANY Z AS 23123123000 :62F:C080326NOK8613000, :64:C080326NOK8613000, -
Implementation guide
62F 64
File example Outgoing cross-border payment 4: :20:5566778899042235 :25:90462312323 :28C:123/1 :60F:C080326NOK8513000, :61:0803260326D8241,16NCROREMITTER REF 104//088010399993 07050813000 :86:/REMI/985474 +9200,00 /BENM/COMPANY TEST SWEDEN AB SE6650000000052275033340 /CHGS/SHANOK40,00 /OCMT/SEK9200,/ /EXCH/89,143 /BENB/ESSESESS :62F:C080326NOK8504758,84 :64:C080326NOK8504758,84 -
Implementation guide
4.6
Sweden
62F 64
File example Incoming local payment, bankgiro payment with invoice information 4: :20:5566778899042235 :25:123123123 :28C:123/1 :60F:C080326SEK500000, :61:0803260326C5587,5NLOC584108870001//6091 BGINB :86:/REMI/161326 +587,50 161306 +1500,00 161326 +1100,00 161284 +750,50 161244 +749,50 161401 +900,00 /ORDP/MEKANISKA VERKSTADEN STOCKHOLM :62F:C080326SEK505587,5 :64:C080326SEK505587,5 - Extended Account statement MT940XS Version 0.1.2 Page 45 (53) Publishing date 12 December 2008
Implementation guide
File example Incoming local payment, bankgiro payment with OCR number 4: :20:5566778899042235 :25:123123123 :28C:123/1 :60F:C080326SEK500000, :61:0803260326C10000,NLOC584108870002//6091 BGINB :86:/REMI/100586875 /ORDP/FORETAGET AB STOCKHOLM :62F:C080326SEK510000, :64:C080326SEK510000, -
Implementation guide
62F 64
File example Incoming cross-border payment 4: :20:5566778899042235 :25:123123123 :28C:123/1 :60F:C080326SEK500000, :61:0803260326C19940,NCRO12345678//60687ABOL :86:/REMI/1122334 /ORDP/COMPANY UK LTD /BENM/TESTCOMPANY SWEDEN AB /CHGS/SEK60 /OCMT/GBP2000/ /EXCH/10, /ORDB/HANDGB22 :62F:C080326SEK519940, :64:C080326SEK519940, -
Implementation guide
File example Outgoing local payment 4: :20:5566778899042235 :25:123123123 :28C:123/1 :60F:C080326SEK500000, :61:0803260326D10000,NLOCREMITTER REF 211//6001 FIL-E :86:/REMI/3314155 3314156 3314177 3314182 /BENM/TESTCOMPANY SWEDEN AB 12345678 :62F:C080326SEK490000, :64:C080326SEK490000, -
Implementation guide
62F 64
File example Outgoing cross-border payment 4: :20:5566778899042235 :25:123123123 :28C:123/1 :60F:C080326SEK500000, :61:0803260326D19900,NCROREMITTER REF 401//60010UTLB :86:/REMI/1234567 /BENM/FACTORY A/S NORGE NO61976002112345 /ORDP/TESTCOMPANY SWEDEN AB /CHGS/SHASEK100 /OCMT/SEK19800,/ /BENB/DABANO22 :62F:C080326SEK480100, :64:C080326SEK480100, -
Implementation guide
4.7
The Netherlands
62F 64
File example Incoming local payment 4: :20:5566778899042235 :25: 0718776777 :28C:123/1 :60F:C080326EUR400000, :61:0803260326C112,5FMSC005009//G007090 :86:DTA/04803/00013 TESTCOMPANY N V P.O BOX 30400 1008 KA ROTTERDAM 11002800 11002877 :62F:C080326SEK400112,5 :64:C080326SEK400112,5 -
62F 64
File example Incoming cross-border payment 4: :20:5566778899042235 :25: 0718776777 :28C:123/1 :60F:C080326EUR400000, :61:0803270326C3847,67FMSC009005//G007003 :86:TESTCOMPANY ABC LTD P O BOX 123 LONDON IM9 5EE Orig. amount USD 4993,5 DAUGHTER COMP INV. 44433 15.03.08 6544455000 :62F:C080326SEK403847,67 :64:C080326SEK400000, -
Implementation guide
File example Outgoing local payment 4: :20:5566778899042235 :25: 0718776777 :28C:123/1 :60F:C080326EUR400000, :61:0803270326D30476,82NLOCREMITTER REF 547//G007077 IZ/MCI-G/0153079999 :86:/REMI/410655555 /BENM/TESTCUSTOMER ROTTERDAM BV 353062222 :62F:C080326SEK369523,18 :64:C080326SEK369523,18 -
Implementation guide
62F 64
File example Outgoing cross-border payment 4: :20:5566778899042235 :25: 0718776777 :28C:123/1 :60F:C080326EUR400000, :61:0803270326D9480,24NCROREMITTER REF 566//G007080 BUTI110000008307 :86:/REMI/410655560 /BENM/TESTCUSTOMER GMBH HAMBURG DE6502000000001693333333 /CHGS/SHA /OCMT/EUR9480,24/ /BENB/DEUTDEHH :62F:C080326SEK390519,76 :64:C080326SEK390519,76 -