TECHNICAL DESCRIPTION OF THE MT940
STATEMENT FORMAT FOR BUSINESS 24
Table of contents
Description of MultiCash MT940 statement format ........................................................................................................ 2
1.1. Terms and abbreviations............................................................................................................... 2
1.2. File header ...................................................................................................................................... 2
1.3. Record structure ............................................................................................................................ 2
1.4. Structure of Field 86....................................................................................................................... 5
DESCRIPTION OF MULTICASH MT940 STATEMENT FORMAT
BUSINESS 24 Internetbanking application allows getting of data statements also in MT940 format, which is
the same as data statements from MultiCash service. Description of the format follows.
1.1. Terms and abbreviations
Description Files contain account statements and other texts
Record Multi-line
Line separator <CRLF>
Field separator <CRLF>
Message format SWIFT MT940 format – supports SWIFT1 and SWIFT2
Statement file name *.STA
File header (yes/no) No
Limits (size, no. of records/lines) Maximum message length is 2000 characters
Code page CP 852 (Latin2)
Compulsory field c
Optional field o
Alphanumerical field a
Numerical field n
Fixed field length f
Variable field length v
File can consist of several statements (i.e. statements from
File content
different accounts or statements from several dates)
1.2. File header
Field content Compulsory (C) / Length and
Optional (O) format
1st line c
GIBACZPX 0800
SWIFT address and bank code
<CR><LF>
2nd line c
940 N2
Message type
<CR><LF>
3rd line o
Client number
Client number or blank line
1.3. Record structure
Field content Compulsory / Length and
Optional format
<CR><LF>:20: c 4af
Transaction reference number c 16 a v
Displayed:
Account number in PPPPPPBBBBBBBBBB format where
PPPPPP is a prefix and BBBBBBBBBB is the account number.
<CR><LF>:25: c 4af
0800/PPPPPPBBBBBBBBBB c 35 a v
Account number
0800 = bank code (4 characters, fixed length)
/ = forward slash separator
PPPPPP = prefix (6 characters, variable length)
BBBBBBBBBB = account number (10 characters, fixed
length filled in by zeros from the left)
Example:
0800/190012345671
0800/9944040012345671
<CR><LF>:28: c 4af
xxxxx/yyyyy c 11 a v
Account statement number
3 (x/y) to 11 characters (xxxxx/yyyyy)
xxxxx = account statement number
/ = forward slash separator
yyyyy = statement page number
Example:
00024/00001
<CR><LF>:60 c 3af
Opening balance
Balance type: c 1af
F = Opening balance
M = Intermediate balance
: c 1af
Debit /credit item: c 1af
C = Credit
D = Debit
Accounting day: c 6nf
YYMMDD = Accounting day
Currency
ISO currency code c 3af
Amount
Amount with “,” (comma) as the decimal separator c 16 n v
<CR><LF>:61: c 4af
Transaction line
Maturity/value date (in YYMMDD format) c 6nf
Posting date (in MMDD format) o 4af
Debit/credit transaction:
C = Credit transaction
D = Debit transaction c 2av
RC = Credit transaction cancellation
RD = Debit transaction cancellation
Currency code (3rd character from ISO currency code)
Amount o 1af
Amount with “,” (comma) as the decimal separator
c 16 n v
Text key (exactly 4 alphanumeric characters, 1st character = N)
c 4af
Reference
Client reference; if not available, use "NONREF"
c 16 a v
// separator
o 2af
Bank reference
<CR><LF> o 16 a v
Only for further payment information
E.g. payment reference, bank reference, original payment amount, o 34 a v
etc.
<CR><LF>:86: o 6*65 a v
Blank field (see the description in “Structure of Filed 86” bellow)
<CR><LF>:62 c 3af
Closing balance
Balance type: c 1af
F = Opening balance
M = Subtotal
: c 1af
Debit /credit item: c 1af
C = Credit
D = Debit
Accounting day: c 6nf
Accounting day in YYMMDD format
Currency c 3af
ISO currency code
Amount c 15 n v
Amount with “,” (comma) as the decimal separator
<CR><LF> -} c 1af
End of record
<CR><LF>
1.4. Structure of Field 86
Key rules:
¾ Subfields are optional
¾ Subfields are separated by ‘?‘ (question mark)
¾ Fields which are not used/ left blank will be filled in by ‘.‘ (dot)
¾ Banking transactions are sorted out into three main categories – their list is available in the first
record of Field 86 (020 – domestic payments, 030 – foreign payments, 020 – other payments).
The main sorting criterion is displayed in Subfield 10.
Subfield Length and Name
format
3nf Business code (payment type)
Domestic transactions
‘020’
Foreign transactions
‘030’
Other transactions
‘020’
00 27 a v Transaction number
Transaction number
Transaction number
10 10 a v Banking transaction type
Banking transaction type
Banking transaction type
20 27 a v Constant symbol
Always with KS:
Example „KS:8“ ; „KS:308“ ; „KS:5308“
Banking transaction description
Constant symbol
Always with KS:
21 27 a v Variable Symbol
Always with VS:
Example VS:23568 ; VS:456781
Exchange rate
Always with KURS: 5.8 numeric format where zeros in the beginning
and at the end are ignored.
Variable symbol
Always with VS:
22 27 a v Specific symbol
Always with SS:
Example SS:4523 ; SS:1234564
Outgoing/incoming payment – payment details – Line 1
Internal transfer – additional information – Line 1
Specific symbol
Always with SS:
23 27 a v Counterparty’s account
Counterparty’s bank code/account
Outgoing/incoming payment – payment details – Line 2
Internal transfer – additional information – Line 2
Other transactions
Payments between two ČS accounts
Deposits to /withdrawals from accounts
24 29 a v Counterparty’s VS and SS
Always VS2: /SS2: or e.g. VS2: XXXXXXXXXX/SS2: YYYYYYYYYY -
filled in only if received with a payment.
Outgoing/incoming payment – payment details – Line 3
Internal transfer – additional information – Line 3
Counterparty’s VS and SS
Always VS2: /SS2: or VS2: XXXXXXXXXX/SS2: YYYYYYYYYY (filled
in only if received with a payment) or a dot.
25 35 a v Payment purpose
Outgoing payment – beneficiary’s account
Incoming payment – payer’s account
Internal transfer – counterparty’s account
Payment purpose
26 27 a v Payment purpose
Outgoing payment – beneficiary’s name – Line 1
Incoming payment – payer’s details - Line 1
Internal transfer – name of the counterparty
Payment purpose
27 27 a v Payment purpose
Outgoing payment – beneficiary’s name – Line 2
Incoming payment – payer’s details - Line 2
Internal transfer – ‘.‘ (dot)
Payment purpose
28 27 a v Payment purpose
Outgoing payment – beneficiary’s name – Line 3
Incoming payment – payer’s details - Line 3
Payment purpose
29 27 a v Payment purpose
SEPA payment – sender’s reference 1st part
In other instances filled in with ‘.‘ (dot)
Payment purpose
30 12 a v Counterparty’s bank code
SEPA payment - sender’s reference 2nd part
In other instances filled in with ‘.‘ (dot)
Bank code
31 24 n v Counterparty’s account number
Not used, will be filled in with ‘.‘ (dot)
Account number
32 27 a v Counterparty’s name
SEPA payment – sender’s identification (first 27 characters)
In other instances filled in with ‘.‘ (dot)
Transfer between two accounts within ČS
Deposits to and withdrawals from the account
33 27 a v Counterparty’s name
SEPA payment – beneficiary’s identification (first 27 characters)
In other instances filled in with ‘.‘ (dot)
Transfer between two accounts within ČS
Deposits to and withdrawals from the account
60 6nv Date when transaction debited from the payer’s account
(Optional
field) Not used, will be marked with ‘.‘ (dot)
Not used, will be marked with ‘.‘ (dot)
