Professional Documents
Culture Documents
This document describes a usage guideline restricting the base message MT940 (SR 2017)
.You can also consult this information online.
14 August 2018
Table of Content 2
Message Functionality 3
Usage Guideline 6
Appendix 16
Legal Notices 33
Collection Description
Account, Balance and Transaction Reporting (MT) (link)
The structure of an MT940 message is based on SWIFT code words and code words from
other relevant sources (/xxxx/) and subfields within a code word (/xxxx/subfield 1/subfield 2/).
This format can be easily processed and reconciled by an automated function. The present
layout is based on SWIFT Standards FIN, Category 9, Cash Management and Customer
Status.
Message Separator
In case of multiple statements delivered in one file, the messages are separated by the sign
"$". This is applicable to the following Channels: InsideBusiness Connect, SwiftNet FileAct
and EBICS.
Country coverage
This CAMT.053 applies to all ING countries incl. Multibank. For Multibank the CAMT.053 is
based on a incoming SWIFT MT940. Therefore the CAMT.053 will contain limited information.
Outline
The ING Format Description MT.940 Customer Statement Message message is composed of
10 building blocks
Legend
Header Description
LvL Element nesting in tree hierarchy
Name Element name
Mult Element multiplicity
Type / Code Element formatting
Rest Restriction type
Additional details Other restriction specifics
Multibank:
= Transaction Amount (Tag 61 Sub 5) of incoming MT940
3 Transaction Type [1..1] 1!a
4 First advice F X
4 Non-SWIFT transfer N
4 SWIFT transfer S X
Multibank:
= Reference (Tag 61 Sub 7) of incoming MT940
4 Reference of the Account Servicing [0..1] 16x Comment:
Institution Starts with "//" filled with 14 positions of unique ING reference
Multibank:
= Reference of the Account Servicing Institution (Tag 61 Sub 8) of
incoming MT940
4 Supplementary Details [0..1] 34x Comment:
/TRCD/<ING transaction codification>
/OCMT/<ISO CCY+original amount of transaction>/
(only reported if original amount deviates from reported amount in
Tag 61.5)
Multibank:
=Supplementary Details (Tag 61 Sub 9) of incoming MT940
2 86 Information to Account Owner [0..1] 6*65x
Multibank:
= Information to Account Owner (Tag 86 Copy) of incoming MT940
4 Narrative [1..1]
5 Line [1..6] 65x T/C Type Changed:
[ 6n[ 4x]][ 6n[ 3 5x]][ 6n[ 3 5x]][ 6n[ 3 5x]][ 6n[ 4x]][ 6n[ 3 5x]][ 6n[ 3
5x]][ 6n[ 3 5x][ 1 1x][ 5 0x][ 3 5x]][ 6n[ 6 5x][ 6 5x][ 6 5x]][ 6n[ 4x]][
6n[ 7 0x][ 3 5x]][ 6n[ 7 0x][ 3 5x]][ 6n[ 1 2x]][ 6n[ 1 5x]]
6 Return_Reason [0..1] 6n[4x]
7 RTRN [1..1] 6n
7 ReasonCode [0..1] 4x
6 Client_Reference [0..1] 6n[35x]
7 CREF [1..1] 6n
7 ClientReference [0..1] 35x
6 End_to_End_Reference [0..1] 6n[35x]
7 EREF [1..1] 6n
7 End_to_End_Reference [0..1] 35x
6 Payment_Information_ID [0..1] 6n[35x]
7 PREF [1..1] 6n
7 Batch_ID [0..1] 35x
It complements the ING Format Description Structured MT940 & MT942 (Version 4) Strategic
and the ING Format Description Camt.052.001.02, Camt.053.001.02 and Camt.054.001.02
Strategic.
© ING Bank N.V., 2018. This document is a publication of ING Wholesale Banking
The ING Transaction Codification list contains the current list of possible codes. A number of codes are country specific or for future reference.
Code Description NL IE BG FR AT CH DE ES GB IT PT CZ HU SK RO PL TR RU UA LU
[1] Only in combination with Camt Format and Global Entry Enrichment
[2] Either Single SEPA SCT Salary or In Batch; In Batch only in combination with Camt Format and Global Entry Enrichment;
[3] Used to report an All-in-country transfer within the branch
[4] As of mid 2018 the Codes 05002, 05003, 05004, 05005, 05007, 5010 and 05011 will all be reported as 05001
[5] depending on commercial availability of the product
Code Description
A group will only contain transactions if the transaction type occurs in the specific country for the specific account.
The ISO return reason codes in the table below are applicable to:
• SEPA Credit Transfer (SCT) and/or
• SEPA Direct Debit (SDD)
* Ensure the above listed ISO Return Reason codes can be handled by your IT system.
For the most recent list of reason codes see www.ISO20022.org
The ISO return reason codes in the table below are generic codes that can occur in payment processing, including SEPA transactions.
* Ensure the above listed ISO Return Reason codes can be handled by your IT system.
For the most recent list of reason codes see www.ISO20022.org
Copyright
SWIFT SCRL © 2018. All rights reserved.
This material is a component of MyStandards, the SWIFT collaborative Web application used
to manage standards definitions and industry usage. It can only be used and distributed in
accordance with MyStandards Terms of Use.
Unless otherwise agreed in writing with SWIFT SCRL, you have no right to:
- authorise external end users to use this component for other purposes than their internal
use.
- remove, alter, cover, obfuscate or cancel from view any copyright or other proprietary rights
notices appearing in this physical medium.
- re-sell or authorise another party e.g. software and service providers, to re-sell this
component.
Confidentiality
This publication may contain SWIFT or third-party confidential information. Only disclose it
outside your organisation in accordance with MyStandards Terms of Use and your related
license rights.
This component is provided 'AS IS'. SWIFT does not give and excludes any express or
implied warranties with respect to this component such as but not limited to any guarantee as
to its quality, supply or availability.
Any and all rights, including title, ownership rights, copyright, trademark, patents, and any
other intellectual property rights of whatever nature in this component will remain the
exclusive property of SWIFT or its licensors.