Message Reference Guide: Category 9 - Cash Management and Customer Status
Message Reference Guide: Category 9 - Cash Management and Customer Status
Message Reference Guide: Category 9 - Cash Management and Customer Status
This reference guide contains the category 9 message text standards, including a detailed description of the scope, the
format specifications, the rules, the guidelines, and the field specifications of each message type.
18 December 2020
Category 9 - Cash Management and Customer Status for Standards MT November 2021
Table of Contents
Introduction................................................................................................................................................. 3
Summary of Changes............................................................................................................................. 3
Category 9 Message Types........................................................................................................................ 4
Euro - Impact on Category Message Standards ........................................................................................7
MT 900 Confirmation of Debit .................................................................................................................... 8
MT 910 Confirmation of Credit ................................................................................................................... 9
MT 910 Scope ........................................................................................................................................ 9
MT 910 Format Specifications................................................................................................................ 9
MT 910 Network Validated Rules ........................................................................................................... 9
MT 910 Usage Rules.............................................................................................................................. 9
MT 910 Field Specifications ................................................................................................................. 10
MT 920 Request Message ....................................................................................................................... 20
MT 935 Rate Change Advice ................................................................................................................... 21
MT 940 Customer Statement Message....................................................................................................22
MT 941 Balance Report ........................................................................................................................... 23
MT 942 Interim Transaction Report..........................................................................................................24
MT 950 Statement Message .................................................................................................................... 25
MT 970 Netting Statement ....................................................................................................................... 26
MT 971 Netting Balance Report ............................................................................................................... 27
MT 972 Netting Interim Statement ........................................................................................................... 28
MT 973 Netting Request Message ........................................................................................................... 29
MT 985 Status Enquiry ............................................................................................................................. 30
MT 986 Status Report .............................................................................................................................. 31
MT 990 Advice of Charges, Interest and Other Adjustments ...................................................................32
MT 991 Request for Payment of Charges, Interest and Other Expenses ................................................33
MT 992 Request for Cancellation ............................................................................................................. 34
MT 995 Queries........................................................................................................................................ 35
MT 996 Answers ...................................................................................................................................... 36
MT 998 Proprietary Message ................................................................................................................... 37
MT 999 Free Format Message ................................................................................................................. 38
Glossary of Terms..................................................................................................................................... 39
Legal Notices............................................................................................................................................ 41
Introduction
Summary of Changes
Added Message Types
None
18 December 2020 3
Category 9 - Cash Management and Customer Status for Standards MT November 2021
For each message type, there is a short description, an indicator whether the message type is
signed (Y or N), the maximum message length on input (2,000 or 10,000 characters), whether the
use of the message requires registration with SWIFT for use in a message user group (Y or N), and
whether value date ordering (VDO) can be requested for the message (Y/N). Value date ordering
criteria are described in the Standards MT General Information.
(1) A Relationship Management Application (RMA) authorisation is required in order to sign a message.
18 December 2020 5
Category 9 - Cash Management and Customer Status for Standards MT November 2021
Note: A Message User Group (MUG), for the purposes of this book, is a group of users who have
voluntarily agreed to support the specified message type and have registered with SWIFT to send or
receive the specified message type. These messages are indicated in the preceding table in the
column MUG.
Registration is free of charge. To register to use one or more message types, submit a registration
request (Order Message User Group) through the forms available on www.swift.com > Ordering
& Support > Ordering > Order Products and Services > Message User Group (MUG).
To withdraw from a MUG, use the Terminate your MUG subscription request. These forms are
available at www.swift.com > Ordering & Support > Ordering > Terminate and deactivate >
Message User Group (MUG).
To get the list of other members of a particular MUG, please contact Support.
18 December 2020 7
Category 9 - Cash Management and Customer Status for Standards MT November 2021
Details of this message are still available in the current version of the Standards MT documentation
on www.swift.com > Ordering & Support > Knowledge Centre (User Handbook).
MT 910 Scope
This message is:
• sent by an account servicing institution to a party authorised by the account owner to receive
the information.
It is used to notify the account owner of an entry which has been credited to its account. The entry
will be further confirmed by statement.
For use of messages in the corporate to bank environment, see the MT message implementation
guide for corporate customers available on www.swift.com.
O 56a Intermediary A or D 8
18 December 2020 9
Category 9 - Cash Management and Customer Status for Standards MT November 2021
• This message type does not normally result in any bookings. It is a confirmation to the Receiver
(account owner) of a credit to its account.
• Where a correspondent bank has received a cover payment and sends a confirmation of credit
(MT 910) to the Beneficiary Bank, the reference from field 21 of the inward payment message
must be passed on unchanged in field 21 of the MT 910 message.
16x
PRESENCE
Mandatory
DEFINITION
This field specifies the reference assigned by the Sender to unambiguously identify the message.
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//'
(Error code(s): T26).
16x
PRESENCE
Mandatory
DEFINITION
This field contains the reference for the account owner (Receiver), for example, field 21, from the
SWIFT message which resulted in this credit.
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//'
(Error code(s): T26).
USAGE RULES
This reference must be copied unchanged from the inward message that caused the credit on the
account, for example, field 20 of a received MT 103, or field 21 of the MT 202 (or MT 205) or MT
202 COV (or MT 205 COV) must be copied unchanged to this field.
PRESENCE
Mandatory
DEFINITION
This field identifies the account which has been credited and optionally the identifier code of the
account owner.
USAGE RULES
Option P must only be used if the Receiver of the message is not the account owner.
PRESENCE
Optional
DEFINITION
This field indicates the date, time and time zone when the entry is posted to the account, in the
books of the account servicing institution.
CODES
One of the following codes must be used in Sign (Error code(s): T15):
18 December 2020 11
Category 9 - Cash Management and Customer Status for Standards MT November 2021
Time offset is expressed as 'HHMM', where the hour component, that is, 'HH', must be in the range
of 00 through 13, and the minute component, that is, 'MM' must be in the range of 00 through 59.
Any 'HH' or 'MM' component outside of these range checks will be disallowed (Error code(s): T16).
USAGE RULES
The time zone in which Time is expressed is to be identified by means of the offset against the
UTC (Coordinated Universal Time - ISO 8601).
PRESENCE
Mandatory
DEFINITION
This field specifies the value date, currency code and amount of the credit.
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and
is included in the maximum length. The number of digits following the comma must not exceed the
maximum number allowed for that specific currency as specified in ISO 4217 (Error code(s):
C03,T40,T43).
In option F, the following line formats must be used (Error code(s): T54):
Or
PRESENCE
DEFINITION
This field identifies the customer or financial institution (from a Category 1 Payment), which
originated the transaction resulting in this credit.
CODES
In option F, when Party Identifier is used with the (Code)(Country Code)(Identifier) format, one of
the following codes must be used in Code (Error code(s): T55):
ARNU Alien Registration The code followed by a slash, '/' must be followed by the ISO country
Number code, a slash, '/' and the Alien Registration Number.
CCPT Passport Number The code followed by a slash, '/' must be followed by the ISO country
code, a slash, '/' and the Passport Number.
CUST Customer The code followed by a slash, '/' must be followed by the ISO country
Identification code of the issuer of the number, a slash, '/', the issuer of the number,
Number a slash, '/' and the Customer Identification Number.
DRLC Driver's Licence The code followed by a slash, '/' must be followed by the ISO country
Number code of the issuing authority, a slash, '/', the issuing authority, a slash,
'/' and the Driver's Licence Number.
EMPL Employer Number The code followed by a slash, '/' must be followed by the ISO country
code of the registration authority, a slash, '/', the registration authority,
a slash, '/' and the Employer Number.
NIDN National Identity The code followed by a slash, '/' must be followed by the ISO country
Number code, a slash, '/' and the National Identity Number.
SOSE Social Security The code followed by a slash, '/' must be followed by the ISO country
Number code, a slash, '/' and the Social Security Number.
TXID Tax Identification The code followed by a slash, '/' must be followed by the ISO country
Number code, a slash, '/' and the Tax Identification Number.
CODES
In option F, Number must contain one of the following values (Error code(s): T56):
18 December 2020 13
Category 9 - Cash Management and Customer Status for Standards MT November 2021
1 Name of Ordering The number followed by a slash, '/' must be followed by the name of
Customer the ordering customer.
2 Address Line The number followed by a slash, '/' must be followed by an address
line (Address Line can be used to provide, for example, street name
and number, or building name).
3 Country and Town The first occurrence of number 3 must be followed by a slash, '/', the
ISO country code and, optionally, additional details that are preceded
by a slash '/'.
Other occurrences of number 3 must be followed by a slash '/' and the
continuation of additional details.
Additional details can contain town, which can be complemented by
postal code (for example zip) and country subdivision (for example
state, province, or county). The country code and town should,
preferably, indicate the country and town of residence.
4 Date of Birth The number followed by a slash, '/' must be followed by the date of
birth in the YYYYMMDD format.
5 Place of Birth The number followed by a slash, '/' must be followed by the ISO
country code, a slash '/' and the place of birth.
6 Customer The number followed by a slash, '/' must be followed by the ISO
Identification country code of the issuer of the number, a slash, '/', the issuer of the
Number number, a slash, '/' and the customer identification number.
7 National Identity The number followed by a slash, '/' must be followed by the ISO
Number country code, a slash, '/' and the national identity number.
8 Additional
Information The number followed by a slash, '/' is followed by information that
completes one of the following:
In option F, subfield 1 (Party Identifier) used with the (Code)(Country Code)(Identifier) format:
Country Code must be a valid ISO country code (Error code(s): T73).
• The first line must start with number 1 (Error code(s): T56).
• The first occurrence of number 3 must be followed by a valid ISO country code (Error code(s):
T73).
• Numbers 1, 2, and 3 may be repeated. The same number must not occur more than 2 times
(Error code(s): T56).
• Number 4 must not be used without number 5 and vice versa (Error code(s): T56).
• Number 4 must be followed by a valid date in the format YYYYMMDD and this date, local to the
sender, must not be later than the date on which the message is successfully sent to SWIFT
(Error code(s): T50).
• Numbers 5, 6 and 7 must be followed by a valid ISO country code (Error code(s): T73), a slash
'/' and additional Details (Error code(s): T56).
• The use of number 8 is only allowed in the following instances (Error code(s): T56):
◦ to continue information on the Identifier of the ordering customer provided in subfield 1
(Party Identifier) used with the (Code)(Country Code)(Identifier) format.
◦ to continue information on the National Identity Number provided in subfield 2 (Name and
Address) following number 7.
USAGE RULES
When option A is used, this field can only contain a financial institution BIC if the message that
caused the credit is a Category 1 message and a financial institution BIC was present in 50A
Ordering Customer.
In option F, subfield 2 (Name and Address): if number 2 is present, the first occurrence of number 3
must include the town in additional details.
In option F, subfield 1 (Party Identifier) used with the (Code)(Country Code)(Identifier) format: if
additional space is required for providing the Identifier of the ordering customer, one of the
following options must be used:
1. First option (preferred): Identify the ordering customer with a different identifier where the length
is not an issue.
2. Second option: Continue the information in subfield 2 (Name and Address) using number 8.
In option F, subfield 2 (Name and Address): if additional space is required for providing the
Customer Identification Number (number 6) or the National Identity Number (number 7) of the
ordering customer, one of the following options must be used:
1. First option (preferred): Identify the ordering customer with a different identifier where the length
is not an issue.
2. Second option: Continue the information in subfield 2 (Name and Address) using number 8.
18 December 2020 15
Category 9 - Cash Management and Customer Status for Standards MT November 2021
When Chinese characters are necessary and when use is bilaterally agreed, the Chinese
Commercial Code e-table and guidelines must be followed as published in www.swift.com >
Standards > Document centre > Market Practice > Chinese Commercial Code eTable Information.
PRESENCE
DEFINITION
This field identifies the financial institution which originated the transaction resulting in this credit. If
field 50a is present, then this field identifies the financial institution of the ordering customer present
in the original transaction that resulted in this credit.
CODES
In option A, Party Identifier may be used to indicate a national clearing system code.
CODES
In option D, Party Identifier may be used to indicate a national clearing system code.
Identifier Code must be a registered financial institution BIC (Error code(s): T27,T28,T29,T45).
Identifier Code must be a financial institution BIC. This error code applies to all types of BICs
referenced in a FIN message including connected BICs, non-connected BICs, Masters, Synonyms,
Live destinations and Test & Training destinations (Error code(s): C05).
USAGE RULES
The coded information contained in field 52a must be meaningful to the Receiver of the message.
Option D should only be used when the ordering financial institution has no BIC.
18 December 2020 17
Category 9 - Cash Management and Customer Status for Standards MT November 2021
PRESENCE
Optional
DEFINITION
This field identifies the financial institution from which the Sender received the funds, when other
than the ordering institution.
Identifier Code must be a registered financial institution BIC (Error code(s): T27,T28,T29,T45).
Identifier Code must be a financial institution BIC. This error code applies to all types of BICs
referenced in a FIN message including connected BICs, non-connected BICs, Masters, Synonyms,
Live destinations and Test & Training destinations (Error code(s): C05).
6*35x (Narrative)
In addition to narrative text, structured text with the following line formats may be used:
PRESENCE
Optional
DEFINITION
USAGE RULES
This field may contain information only, that is, no instructions may be included.
Additional explanatory information, which may be continued on the next lines, is preceded by a
double slash '//'.
This field may contain ERI to transport dual currencies, as explained in the chapter "Euro-Related
Information (ERI)" in the Standards MT General Information.
In order to comply with the EC-directive on cross border credit transfers, the optional code word
EXCH may be used to transport an exchange rate. In line with ERI, the code word EXCH is placed
between slashes, followed by the exchange rate, format 12d, and terminated with another slash.
18 December 2020 19
Category 9 - Cash Management and Customer Status for Standards MT November 2021
Details of this message are still available in the current version of the Standards MT documentation
on www.swift.com > Ordering & Support > Knowledge Centre (User Handbook).
Details of this message are still available in the current version of the Standards MT documentation
on www.swift.com > Ordering & Support > Knowledge Centre (User Handbook).
18 December 2020 21
Category 9 - Cash Management and Customer Status for Standards MT November 2021
Details of this message are still available in the current version of the Standards MT documentation
on www.swift.com > Ordering & Support > Knowledge Centre (User Handbook).
Details of this message are still available in the current version of the Standards MT documentation
on www.swift.com > Ordering & Support > Knowledge Centre (User Handbook).
18 December 2020 23
Category 9 - Cash Management and Customer Status for Standards MT November 2021
Details of this message are still available in the current version of the Standards MT documentation
on www.swift.com > Ordering & Support > Knowledge Centre (User Handbook).
Details of this message are still available in the current version of the Standards MT documentation
on www.swift.com > Ordering & Support > Knowledge Centre (User Handbook).
18 December 2020 25
Category 9 - Cash Management and Customer Status for Standards MT November 2021
Details of this message are still available in the current version of the Standards MT documentation
on www.swift.com > Ordering & Support > Knowledge Centre (User Handbook).
Details of this message are still available in the current version of the Standards MT documentation
on www.swift.com > Ordering & Support > Knowledge Centre (User Handbook).
18 December 2020 27
Category 9 - Cash Management and Customer Status for Standards MT November 2021
Details of this message are still available in the current version of the Standards MT documentation
on www.swift.com > Ordering & Support > Knowledge Centre (User Handbook).
Details of this message are still available in the current version of the Standards MT documentation
on www.swift.com > Ordering & Support > Knowledge Centre (User Handbook).
18 December 2020 29
Category 9 - Cash Management and Customer Status for Standards MT November 2021
Details of this message are still available in the current version of the Standards MT documentation
on www.swift.com > Ordering & Support > Knowledge Centre (User Handbook).
Details of this message are still available in the current version of the Standards MT documentation
on www.swift.com > Ordering & Support > Knowledge Centre (User Handbook).
18 December 2020 31
Category 9 - Cash Management and Customer Status for Standards MT November 2021
18 December 2020 33
Category 9 - Cash Management and Customer Status for Standards MT November 2021
MT 995 Queries
See Category n - Common Group Messages, Chapter n95 Queries for details concerning this
message type.
18 December 2020 35
Category 9 - Cash Management and Customer Status for Standards MT November 2021
MT 996 Answers
See Category n - Common Group Messages, Chapter n96 Answers for details concerning this
message type.
18 December 2020 37
Category 9 - Cash Management and Customer Status for Standards MT November 2021
Glossary of Terms
In addition to the definitions which appear in the Standards MT General Information, Glossary of
Terms, the following terms apply to Category 9 message types:
Account Servicing Institution's A reference assigned by the account servicing institution to identify the
Reference transaction. (This is the reference to which the account owner refers in
cases of inquiry to that financial institution.)
Available Balance The balance at the disposal of the account owner on the date specified.
The specific formula for the calculation of the balance is dependent upon
national, local, legal or bilateral agreement/conventions/requirements.
Closing Available Balance Amount at the disposal of the account owner at the close of the statement
period.
Closing Balance Balance of entries posted to the account at the close of the statement
period.
Concentrating Institution A financial institution authorised by the account owner to receive, collate
and report status and movement information on behalf of the account
owner.
Credit Advice An advice by the account servicing institution of a credit to the account of
the Receiver (Account Owner). This advice must not be used to transmit
payment instructions.
Debit Advice An advice by the account servicing institution of a debit to the account of
the Receiver (Account Owner).
ECU Netting System A multi-lateral payment netting service operated by SWIFT/SSP on behalf
of the ECU Banking Association, with settlement through the Bank for
International Settlement.
Entry Date Date on which entries are made in the records of an account.
Forward Available Balance The balance of the booked items that will be available to the account
owner on a specified future date.
Immediate Funds Same day funds in which the settlement is simultaneous with execution of
the transaction.
18 December 2020 39
Category 9 - Cash Management and Customer Status for Standards MT November 2021
Intermediate Closing Balance Balance of entries posted to the account as reflected in the statement
'page' (message) of a statement consisting of multiple 'page' (messages).
Intermediate Opening Balance Intermediate closing balance as reflected in the previous statement 'page'
(message) of a statement consisting of multiple 'pages' (messages).
Netting Balance The balance of entries posted to a netting position by a netting system.
Nostro Account A record kept by an account owner of an account serviced on its behalf by
an Account Servicing Institution. It is also known as a Due From account.
Reference for the account The reference which identifies the transaction to the Account Owner.
owner
Reference for the Beneficiary See 'Reference for the Account Owner'.
Reporting Bank The bank transmitting the information about accounts serviced by them.
Statement Number A number for the sequential identification of statements. It may have a
subfield indicating the 'page' number.
Legal Notices
Copyright
Disclaimer
This publication constitutes advance information only and is not to be considered the final and complete standards
documentation for the subject matter published herein.
The information in this publication may change from time to time. You must always refer to the latest available version.
SWIFT Standards Intellectual Property Rights (IPR) Policy - End-User License Agreement
SWIFT Standards are licensed subject to the terms and conditions of the SWIFT Standards IPR Policy - End-User License
Agreement available at www.swift.com > About Us > Legal > IPR Policies > SWIFT Standards IPR Policy.
Translations
The English version of SWIFT documentation is the only official and binding version.
Trademarks
SWIFT is the trade name of S.W.I.F.T. SC. The following are registered trademarks of SWIFT: 3SKey, Innotribe,
MyStandards, Sibos, SWIFT, SWIFTNet, SWIFT Institute, the Standards Forum logo, the SWIFT logo, and UETR. Other
product, service, or company names in this publication are trade names, trademarks, or registered trademarks of their
respective owners.
18 December 2020 41