Account Statement Service MT 940

File Description

Version 1.1
Index

1 Account Statement Service MT 940 .............................................................................3

2 The structure of a message ..........................................................................................3
2.1 Block 1 – Basic Header Block ..................................................................................... 4
2.2 Block 2 – Application Header Block ............................................................................ 4
2.3 Block 4 – Text Block ................................................................................................... 4
3 Account Statement .......................................................................................................5
3.1 Format specification for the Account Statement.......................................................... 7
3.2 Field definitions........................................................................................................... 8
Balances – formatting rules for field 60F, 62a, 64 and 65 ....................................................... 8
Field 28C – Statement Number/Sequence Number ................................................................ 8
Field 60a – Opening Balance (Booked Funds) ........................................................................ 8
Field 61, Subfield 6 – Transaction Type Identification Code.................................................... 8
Field 61, Subfield 7 – Reference for the Account Owner......................................................... 9
Field 61, Subfield 9 – Supplementary Details .......................................................................... 9
Field 86 – Information to Account Owner................................................................................. 9
Field 62a – Closing Balance (Booked Funds).......................................................................... 9
Field 65 – Forward Available Balance ..................................................................................... 9
Nordea’s Sweeping Services ................................................................................................. 10

Version log

Version no Date Description of change

1.0 2006-01-18 Original version

1.1 2006-02-27 Block 3 added

MT940_File_Description_v1.1.doc 2
1 Account Statement Service MT 940
Via Corporate Netbank, Nordea’s web electronic banking portal for corporate customers, it is possible for the
customer to download files with account statements from Nordea and other banks in a format based on SWIFT
standards. The files can be retrieved directly into the customer’s own system, which give the possibility to replace
time-consuming manual booking and reconciliation by automated processes.

An account statement is produced by a Nordea bank or sent via SWIFT from the account holding bank to a
Nordea bank. The bank that transmits account statements is responsible for their content. Nordea relays
information from the foreign bank to the customer in the received form. Account statements normally contain each
transaction of the given account day with opening and closing balances.

The arrival time of account information to Nordea depends on the time zone and the transmitting bank’s service
hours. In most cases, account statements are available by 9 a.m. CET on the next banking day. Account
information that has arrived at Nordea can be retrieved from Corporate Netbank’s File Transfer service 7-22 CET,
five days per week. Account statements remain available to the customer in Nordea Bank’s data systems for two
months after its arrival.

Account Statements are coded in the SWIFT message format MT 940. Since the length of a SWIFT message is
restricted to the maximum input message length, several messages may be required to accommodate all the
information for one account statement. A file may include several messages, depending on the user’s choice in the
bank’s download interface. No extra information besides the SWIFT messages is provided in the file.

Messages in a file
Message Example of Content
Message no. 1 Account statement no. 1, part 1 from Bank X
Message no. 2 Account statement no. 1, part 2 from Bank X
Message no. 3 Account statement no. 2 from Bank X
Message no. 4 Account statement no. 1 from Bank Y
Message no. 2 Account statement no. 1, part 1 from Bank Z
Message no. 2 Account statement no. 1, part 2 from Bank Z

The message format presented in this description fully complies with the international definitions for content and
use of an SWIFT MT 940 Customer Statement Message. Attached to the general definitions you will find Technical
Specifications containing detailed information about the field content in statements from Nordea Denmark,
Finland, Norway and Sweden. In other cases, please contact the account servicing bank to obtain information
about the content of a message.

The following terminology is used through out this text to identify the banks involved in the process of delivering
account statements to the customer:
Sender The account servicing bank producing/sending the message
Receiver The Nordea bank presenting the message to the customer.

2 The structure of a message

Each message is divided into three blocks. Each block contains data of a particular type and is used for a
particular purpose. Each block begins and ends with a curly bracket, or brace, character '{' and '}' respectively. All
blocks are numbered, and the block number followed by a colon ‘:’ is always the first character within any block.

Blocks 1, 2 and 3 relate to header information, and Block 4 contains the text of the message. Each block is
subdivided into a number of fields and each field contains particular information, for example, date, time, LT
address, Session Number, ISN, or a tag number followed by the appropriate variable content.

All fields within blocks 1 and 2 are of fixed length and are continuous. Block 3 is optional and may be used for
user-to-user messages. No field separators are used. The content of Block 4 differs depending on bank in terms of
which optional fields are used.

MT940_File_Description_v1.1.doc 3
Block structure
Block Name Example of Content
1. BASIC HEADER BLOCK {1:F01NDEASESSAXXX0833510237}
2. APPLICATION HEADER BLOCK {2:O9400325050701NDEANOKKBXXX12706189060507010325N}
3: USER HEADER BLOCK {3:108:34}
4. TEXT BLOCK {4:<CrLf>
:20:VR06314330391601<CrLf>
:25:60030631433<CrLf>
:28C:123/1<CrLf>
:60F:D050629NOK25,65<CrLf>
:62F:D050630NOK25,65<CrLf>
:64:D050630NOK25,65<CrLf>
-}
Note: <CrLf> is only used within Block 4, not between blocks. For the purposes of clarity in this publication,
the block structure is shown in the table above with each block beginning a new line.

2.1 Block 1 – Basic Header Block

The Basic Header given in Block 1 provides the fundamental reference for any particular message:
{1:F01NDEASESSAXXX0833510237}

Components
Name Description Type Content
Block Identifier The identifier for a Basic Header Block 2x Always '1:'
Application Identifier The application within which the message is being sent/received 1x Always 'F'
Service Identifier The type of data that is being sent/received 2n Always '01'
LT Identifier The FIN address of the receiver of the message: 1-8=SWIFT 12x E.g.
address, 9=LT Code, 10-12=Branch Code (default 'XXX' ) 'NDEASESSAXXX'
Session Number Identifies the session in which the message was transmitted 4x E.g. ‘0833’
Sequence Number The OSN of the receiver's current output session 6x E.g. ‘510237’

2.2 Block 2 – Application Header Block

The Application Header provides information about the message itself. It defines the type of message, who sent it
and when, and when it was delivered: {2:O9400325050701NDEANOKKBXXX12706189060507010325N}

Components
Name Description Type Content
Block Identifier The identifier for an Application Header Block 2x Always '2:'
Input/Output ‘I’ for input message, ‘O’ for output message 1x Always 'O'
Identifier
Message Type Defines the MT number of the output message 3n Always '940'
Input Time Expressed in the sender's local time (HHMM) 4n E.g. ‘0325’
MIR Every message is assigned a unique MIR, which consists of 28x E.g. ‘050701NDEANOKK
the input date, local to the sender, and the sender's full BXXX1270618906’
SWIFT address, Session Number and ISN
Output Date The date (YYMMDD), local to the receiver, on which the 6n E.g. ‘050701’
message is delivered to the receiver
Output Time The time (HHMM), local to the receiver, at which the 4n E.g. ‘0325’
message is actually delivered to the receiver
Message Priority The priority with which a message is delivered 1x Always ‘N’

2.3 Block 3 – User Header Block

The User Header is an optional header available within FIN for user-to-user messages only. It appears in Block 3
of a FIN message, and allows users to provide their own reference within the headers for a particular message.

MT940_File_Description_v1.1.doc 4
Components
Name Description Type Content
Block Identifier The identifier for an Application Header Block 2x Always '3:'
Banking Priority Tag 113 defines an optional 4-character banking priority. The
contents of tag 113 are agreed between two or more users.
Message User Tag 108 defines a free-format field in which users may
Reference specify their own reference of up to 16 characters of the
permitted character set.

2.4 Block 4 – Text Block

The Text Block contains the text of the message. Each field within the text begins with a tag number between
colons, followed by the appropriate variable content. <CrLf> is a mandatory field delimiter within the text. Which
optional fields are included, depends on the bank.

Block 4 begins with Carriage Return and Line Feed <CrLf> and ends with <CrLf> followed by a hyphen ‘-‘. Each
field within the text begins with a tag number between colons, followed by the appropriate variable content. A field
consists of at least one meaningful character. Whenever field content contains mandatory and optional subfields,
at least all of the mandatory subfields appear when that field is used.

The general definition of a field format is using the following symbols:

x any character of the permitted character set
n numeric digits (0 through 9) only
a alphabetic letters (A through Z), upper case only
c alphabetic letters (upper case) and digits only
d decimals
! fixed length, for ex. 3!a = always 3 letters
4*35x up to 4 lines of up to 35 characters each
[...] subfield is optional
-----> start repetitive sequence
-----| end repetitive sequence

The permitted character set is as follows:

abcdefghijklmnopqrstuvwxyz
ABCDEFGHIJKLMNOPQRSTUVWXYZ
0123456789
/-?:().,’+{}
Cr Lf Space

Although part of the character set, the curly brackets are used as delimiters and will not be used within the text of
message. In some cases, the field specifications indicate that a slash '/' is included in the text of the field.

3 Account Statement
Account Statements are coded in the SWIFT message format MT 940.

Example of Block 4 including an Account Statement

Field Name Content of Block 4
{4:<CrLf>
Transaction Reference Number :20:395931447812662B<CrLf>
Related Reference :21:AXEL PERSSONS LI<CrLf>
Account Identification :25:31441812552USD<CrLf>
Statement Number/ Sequence Number :28C:76/1<CrLf>
Opening Balance :60F:C050831USD4613989,59<CrLf>
Statement Line :61:0509010901C12726,92NINTINTERN TILLGODOR//090103780980005<CrLf>
Statement Line :61:0509020901C6150000,00NTRFUTLANDSINSATTNIN//090103954532596<CrLf>
Closing Balance :62F:C050901USD10776716,51<CrLf>
Closing Available Balance :64:C050901USD5004626716,51<CrLf>
-}

MT940_File_Description_v1.1.doc 5
 3.1 Format specification for the Account Statement
Tag Field Name Type/Option Content
M 20 Transaction Reference 16x Reference assigned by the Sender to unambiguously identify
Number the message
O 21 Related Reference 16x
M 25 Account Identification 35x Account for which the statement is sent
:
M 28C Statement Number/ 5n[/5n] See attached spreadsheet for details
Sequence Number
M 60a Opening Balance 1!a6!n3!a15d 60F=First opening balance
See Balances 60M=Intermediate opening balance
See attached spreadsheet for details
-----> Transaction Details
O 61 Statement Line 6!n[4!n]2a[1!a Details of each transaction
]15d1!a3!c16
Subfields: x[//16x][34x]
1. Value Date 6!n (YYMMDD)
2. Entry Date [4!n] Booking date (MMDD)
3. Debit/Credit Mark 2a ‘D’=Debit, ‘C’=Credit, ‘RC’=Reversal of credit (debit entry),
‘RD’=Reversal of debit (credit entry)
4. Funds Code [1!a] 3rd character of currency code.
5. Amount 15d The integer part must contain at least one digit. The decimal
comma ‘,’ is mandatory and is included in the maximum length
6. Transaction Type 1!a3!c
Identification Code
7. Reference for the 16x
Account Owner
8. Account Servicing In- [//16x] May be omitted for a transaction initiated by the account
stitution's Reference servicing institution
9. Supplementary [34x] See attached spreadsheet for details
Details
O 86 Information to Account 6*65x See attached spreadsheet for details
Owner
-----|
M 62a Closing Balance 1!a6!n3!a15d 62F=Final closing balance
(Booked Funds) See Balances 62M=Intermediate closing balance
See attached spreadsheet for details
O 64 Closing Available Balan- 1!a6!n3!a15d Funds available to the account owner (if credit balance) or the
ce (Available Funds) See Balances balance subject to interest charges (if debit balance)
See attached spreadsheet for details
-----> Forward Balances
O 65 Forward Available 1!a6!n3!a15d Funds available to the account owner for the specified forward
Balance See Balances value date. See attached spreadsheet for details
-----|
M=Mandatory, O=Optional
Attached to the general definitions you will find Technical Specifications containing detailed information about the
field content in statements from Nordea Denmark, Finland, Norway and Sweden.

MT940_File_Description_v1.1.doc 7
 3.2 Field definitions

Balances – formatting rules for field 60F, 62a, 64 and 65

Information about balances is formatted: 1!a6!n3!a15d. The included subfields are formatted as follows:
Type Subfield Name Content
1!a Debit/Credit Mark ‘D’=debit balance, ‘C’=credit balance
6!n Date YYMMDD
3!a Currency A valid ISO 4217 currency code
15d Amount The integer part must contain at least one digit. The decimal
comma ‘,’ is mandatory and is included in the maximum length

Field 28C – Statement Number/Sequence Number

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 should be reset to 1 on
1 January of each year. If used, the sequence number always starts with 1. When several messages are sent to
convey information about a single statement, the first message must contain ‘/1’ in Sequence Number. The
sequence number must be incremented by one for each additional message. The statement number and
sequence number enable the Receiver to put the messages into sequence and thus form the complete statement.
Example
The first message of a statement is: 28C:235/1
The second message is: 28C:235/2 and so on.

Field 60a – Opening Balance (Booked Funds)

The first or intermediate opening balance. 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).

Field 61, Subfield 6 – Transaction Type Identification Code

The field may be completed in one of three ways:
1. For entries related to SWIFT transfer instructions and subsequent charge messages:
Format: S3!n (3!n=a number in the range 100-999)
The last three characters will indicate the message type of the SWIFT message causing the entry (for
debit entries) or the type of the 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!c=one of the SWIFT or Nordea specific codes below)
3. For entries being first advised by the statement (items originated by the account servicing institution):
Format: F3!c (3!c=one of the SWIFT codes below)

Transaction types according to SWIFT user handbook for format N3!c and F3!c
Code Explanation Code Explanation
BOE Bill of exchange DIV Dividends-Warrants
BRF Brokerage fee EQA Equivalent amount
CHG Charges and other expenses ECK Eurocheques
CHK Cheques FEX Foreign exchange
CLR Cash letters/Cheques remittance INT Interest
CMI Cash management item - No detail LBX Lock box
CMN Cash management item - Notional pooling LDP Loan deposit
CMS Cash management item - Sweeping MSC Miscellaneous
CMT Cash management item -Topping RTI Returned item
CMZ Cash management item - Zero balancing SEC Securities (principal amount)
COL Collections (principal amount) STO Standing order
COM Commission TCK Travellers cheques
DCR Documentary credit (principal amount) TRF Transfer
DDT Direct Debit Item VDA Value date adjustment

MT940_File_Description_v1.1.doc 8
 Nordea specific transaction types for format N3!c
Code Explanation
CMZ Zero Balancing
CMS Sweeping
CMT Topping
● See Nordea’s Sweeping Services for usage rules
Please refer to the attached Technical Specifications for information about usage in Nordea, Denmark,
Finland, Norway and Sweden.

Field 61, Subfield 7 – Reference for the Account Owner

The field may be completed in one of three ways:
· For debit entries, the purpose of this subfield is to identify, to the account owner, the instruction that
caused the debit.
· Credit entries may be the result of one of the following situations:
1. The account servicing institution is identifying, to the account owner the receipt of funds for its
account as a result of a related transaction.
2. The account servicing institution has issued a payment instruction to the account owner and the
credit identified in this subfield is for that payment.

If no reference is available, the code NONREF is used.

Field 61, Subfield 9 – Supplementary Details

If subfield 7=’NONREF’, the account servicing institution should provide the best available alternative information
in this subfield. May also be used when an advice has not been sent for a transaction, or to provide additional
information to facilitate reconciliation.

Field 86 – Information to Account Owner

Additional information on the transaction to be passed on to the account owner. Information are separated by
S.W.I.F.T. codes:
Format: /Code/Information (Code=one of the codes below)

SWIFT codes
Code Explanation
CHGS Currency code and “OUR” charges
OCMT Original currency and amount
EXCH Exchange rate
ORDP Ordering party
BENM Beneficiary party
TRMT Amount to Beneficiary
RATE Exchange rate
REMI Remittance information

Field 62a – Closing Balance (Booked Funds)

Intermediate or final closing balance. 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.

Field 64 – Closing Available Balance (Available Balance)

Funds which are available to the account owner (if credit balance) or the balance which is subject to interest
charges (if debit balance).

Field 65 – Forward Available Balance

Funds that are available to the account owner (if a credit or debit balance) for the specified forward value date.
When there is more than one value date for the items booked to the account (in this or previous statement
periods), this field will indicate the balance which will be available to the account owner on the date(s) indicated.

MT940_File_Description_v1.1.doc 9
Nordea’s Sweeping Services
· Field 61, subfield 6 contains one of the codes NCMZ, NCMS, NCMT.
· Field 61, subfield 7 contains the customer individual reference for the cash management transaction.
· Field 61, subfield 9 can contain the name of the payer or the beneficiary.
· Field 86, the first line consists of: (transaction code – CMZ, CMS or CMT) (account number of beneficiary
or payer) (customer individual reference number, if wanted) (name of beneficiary or payer).
Example
:61:0509070908D494031,34NCMZTOP/SWEEPSVERIGE
GBPAX DANMARK A/S
:86:CMZ/20496116759120/TOP/SWEEPSVERIGE/GBPAX DANMARK A/S

This document contains extracts from the SWIFTStandards Handbook (March 2005 edition) and they are included
into this document with prior permission from S.W.I.F.T. SCRL. To the said extracts shall apply the legal notices
regarding copyright, confidentiality, disclaimer, translations, warnings to all users and trademark and patents as
stated in the SWIFTStandards, Category 9, Cash Management & Customer Status (March 2005 edition).

MT940_File_Description_v1.1.doc 10