Category 4 - Collections and Cash Letters

For Standards MT November 2024

Message Reference Guide

This reference guide contains the category 4 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.

19 July 2024

Link to this document: https://www2.swift.com/go/book/cat4

Category 4 - Collections and Cash Letters
For Standards MT November 2024 Table of Contents
Message Reference Guide

Table of Contents

Introduction..............................................................................................................................................6
Changes.................................................................................................................................................. 6
Volume Formatting Explanation...............................................................................................................6
MT Scope...................................................................................................................................... 6
MT Format Specifications..............................................................................................................6
MT Network Validated Rules......................................................................................................... 7
MT Usage Rules............................................................................................................................7
MT Guidelines............................................................................................................................... 7
MT Field Specifications................................................................................................................. 8
MT Mapping...................................................................................................................................8
MT Examples.................................................................................................................................8
Euro - Impact on Category Message Standards......................................................................................9
Deletion of the National Currency Denomination Currency Codes............................................... 9

Part 1 - Collections................................................................................................................................ 10
Collections Message Types................................................................................................................... 11
MT 400 Advice of Payment....................................................................................................................12
MT 400 Scope............................................................................................................................. 12
MT 400 Format Specifications.....................................................................................................12
MT 400 Network Validated Rules................................................................................................ 13
MT 400 Field Specifications........................................................................................................ 13
MT 400 Examples........................................................................................................................21
MT 410 Acknowledgement.................................................................................................................... 27
MT 410 Scope............................................................................................................................. 27
MT 410 Format Specifications.....................................................................................................27
MT 410 Network Validated Rules................................................................................................ 27
MT 410 Usage Rules...................................................................................................................27
MT 410 Field Specifications........................................................................................................ 28
MT 410 Examples........................................................................................................................31
MT 412 Advice of Acceptance...............................................................................................................33
MT 412 Scope............................................................................................................................. 33
MT 412 Format Specifications.....................................................................................................33
MT 412 Network Validated Rules................................................................................................ 33

19 July 2024 2
Category 4 - Collections and Cash Letters
For Standards MT November 2024 Table of Contents
Message Reference Guide

MT 412 Usage Rules...................................................................................................................33

MT 412 Field Specifications........................................................................................................ 34
MT 412 Examples........................................................................................................................36
MT 416 Advice of Non-Payment/Non-Acceptance................................................................................ 38
MT 416 Scope............................................................................................................................. 38
MT 416 Format Specifications.....................................................................................................38
MT 416 Network Validated Rules................................................................................................ 39
MT 416 Guidelines...................................................................................................................... 40
MT 416 Field Specifications........................................................................................................ 40
MT 416 Examples........................................................................................................................47
MT 420 Tracer....................................................................................................................................... 50
MT 420 Scope............................................................................................................................. 50
MT 420 Format Specifications.....................................................................................................50
MT 420 Network Validated Rules................................................................................................ 50
MT 420 Usage Rules...................................................................................................................50
MT 420 Field Specifications........................................................................................................ 51
MT 420 Examples........................................................................................................................55
MT 422 Advice of Fate and Request for Instructions.............................................................................57
MT 422 Scope............................................................................................................................. 57
MT 422 Format Specifications.....................................................................................................57
MT 422 Network Validated Rules................................................................................................ 57
MT 422 Usage Rules...................................................................................................................58
MT 422 Field Specifications........................................................................................................ 58
MT 422 Examples........................................................................................................................64
MT 430 Amendment of Instructions.......................................................................................................66
MT 430 Scope............................................................................................................................. 66
MT 430 Format Specifications.....................................................................................................66
MT 430 Network Validated Rules................................................................................................ 66
MT 430 Usage Rules...................................................................................................................67
MT 430 Field Specifications........................................................................................................ 67
MT 430 Examples........................................................................................................................73

Part 2 - Cash Letters..............................................................................................................................75

Cash Letters Message Types................................................................................................................ 76
MT 450 Cash Letter Credit Advice.........................................................................................................77
MT 450 Scope............................................................................................................................. 77
MT 450 Format Specifications.....................................................................................................77

19 July 2024 3
Category 4 - Collections and Cash Letters
For Standards MT November 2024 Table of Contents
Message Reference Guide

MT 450 Network Validated Rules................................................................................................ 77

MT 450 Usage Rules...................................................................................................................77
MT 450 Guidelines...................................................................................................................... 78
MT 450 Field Specifications........................................................................................................ 78
MT 450 Examples........................................................................................................................81
MT 455 Cash Letter Credit Adjustment Advice......................................................................................83
MT 455 Scope............................................................................................................................. 83
MT 455 Format Specifications.....................................................................................................83
MT 455 Network Validated Rules................................................................................................ 83
MT 455 Usage Rules...................................................................................................................83
MT 455 Guidelines...................................................................................................................... 83
MT 455 Field Specifications........................................................................................................ 84
MT 455 Examples........................................................................................................................87
MT 456 Advice of Dishonour................................................................................................................. 89
MT 456 Scope............................................................................................................................. 89
MT 456 Format Specifications.....................................................................................................89
MT 456 Network Validated Rules................................................................................................ 89
MT 456 Usage Rules...................................................................................................................90
MT 456 Guidelines...................................................................................................................... 90
MT 456 Field Specifications........................................................................................................ 90
MT 456 Examples........................................................................................................................96

Part 3 - Common Group........................................................................................................................ 98

Common Group Message Types........................................................................................................... 99
MT 490 Advice of Charges, Interest and Other Adjustments.............................................................. 100
MT 491 Request for Payment of Charges, Interest and Other Expenses........................................... 101
MT 492 Request for Cancellation........................................................................................................ 102
MT 495 Queries...................................................................................................................................103
MT 496 Answers..................................................................................................................................104
MT 498 Proprietary Message.............................................................................................................. 105
MT 499 Free Format Message............................................................................................................ 106
MT 499 Scope........................................................................................................................... 106
MT 499 Format Specifications...................................................................................................106
MT 499 Network Validated Rules.............................................................................................. 106
MT 499 Field Specifications...................................................................................................... 106
MT 499 Examples......................................................................................................................107

Glossary of Terms............................................................................................................................... 108

19 July 2024 4
Category 4 - Collections and Cash Letters
For Standards MT November 2024 Table of Contents
Message Reference Guide

Legal Notices....................................................................................................................................... 109

19 July 2024 5
Category 4 - Collections and Cash Letters
For Standards MT November 2024 Introduction
Message Reference Guide

Introduction
Category 4 consists of messages that are exchanged between banks in the handling of documentary and
clean collections, for example, cheque collections, as well as cash letters.
The following guideline applies when sending/receiving messages within this category:
• no provision is made to handle multi-currency collections in any of the message types in this category,
except for the MT 430.

Changes
Category 4 - Collections and Cash Letters is not impacted by the November 2024 Standards release.
Swift continually applies editorial enhancements to its documentation to improve quality and ensure
consistency. These changes are not published but are controlled in order to ensure that they have no
impact on FIN validation.

Important This volume contains information effective as of the November 2024 Standards release.
Therefore the 20 July 2023 edition of the Standards MT User Handbook volumes remains
effective until November 2024.

Volume Formatting Explanation

This volume of the Standards User Handbook set contains general information about the category and a
detailed description of each message type which is currently available for use. For each message type,
the following information is provided:

MT Scope
The scope specifies the Sender and Receiver of the message and provides an explanation on how the
message is used. In some messages, an example of the message flow is also provided.

MT Format Specifications
The format specifications are the rules for the layout of the message type. This information is provided in
table form with the following information:
MT nnn (Message Type Name)

Status Tag Field Name Content/Options No.

M 20 Transaction Reference Number 16x 1

M 21 Related Reference 16x 2

Mandatory Sequence A (Sequence Name)

M 25 Account Identification 35x 3

M 32a Value Date, Currency Code, Amount C or D 4

19 July 2024 6
Category 4 - Collections and Cash Letters
For Standards MT November 2024 Introduction
Message Reference Guide

Status Tag Field Name Content/Options No.

-----> Optional Repetitive Sequence B (Sequence Name)

O 52a Ordering Institution A or D 5

M 71B Details of Charges 6*35x 6

O 72 Sender to Receiver Information 6*35x 7

-----|

M = Mandatory O = Optional - Network Validated Rules may apply

• MT nnn (Message Type Name) provides the message type number and name
• Status indicates if the field is
- M = Mandatory
- O = Optional - Network Validated Rules may apply
The status M for fields in optional (sub)sequences means that the field must be present if the
(sub)sequence is present and is otherwise not allowed.
• Tag is the field identification.
• Field Name is the detailed name of the field tag, for this message type.
• Content/Options provides permitted field length and characteristics. For information concerning field
structure, notation and character restrictions, see the Standards MT General Information.
• No. identifies the number of the field in the Field Specifications for the message type.
Some messages are separated into sequences of fields, as shown above. An arrow indicates that a
sequence of fields may be repeated.

MT Network Validated Rules

Network validated rules are validated on the network, that is, rules for which an error code is defined.
Rules specified in this section affect more than one field in the message, placing a condition on one of
the fields specified. They are identified as Cn, or conditional rules.

MT Usage Rules
Usage rules are not validated on the network, that is, rules for which no error code is defined, but are
nevertheless mandatory for the correct usage of the message. Rules specified in this section affect more
than one field in the message, or more than one Swift message.

MT Guidelines
Guidelines are not validated on the network and are not mandatory for the correct usage of the message.
They concern good practices. Guidelines specified in this section affect more than one field in the
message, or more than one Swift message.

19 July 2024 7
Category 4 - Collections and Cash Letters
For Standards MT November 2024 Introduction
Message Reference Guide

MT Field Specifications
The rules for the use of each field in the message are specified in this section. Each field is identified by
its index number (as shown in the No. column of the MT Format Specifications), field tag and detailed
field name, followed by a description of the field, which may contain some or all of the following:
• FORMAT specifies the field formats which are allowed for the field.
• PRESENCE indicates if the field is mandatory, optional or conditional in its sequence.
• DEFINITION specifies the definition of the field in the message type.
• CODES lists all codes available for use in the field. If there is more than one subfield for which codes
are defined, each separate code list will be identified with a CODES heading. When a list of codes is
validated by the network, the error code will be specified.
• NETWORK VALIDATED RULES specifies rules that are validated on the network, that is, rules for
which an error code is defined. Generally, rules specified in this section affect only the field in which
they appear. In some cases, rules which are validated at the message level, that is, rules which affect
more than one field, are repeated in this section. This is the case when the rule does not affect the
presence of the field, but information within several fields, for example, a currency which must be the
same for more than one field in the message.
• USAGE RULES specifies rules that are not validated on the network, that is, rules for which no error
code is defined, but are nevertheless mandatory for the correct usage of the field. Rules specified in
this section affect only the field in which they appear.
• MARKET PRACTICE RULES specifies rules published by the Payments Market Practice Group
(PMPG). It informs the reader of the existence of a global market practice document on the business
process in which the concerned field is used. The absence of a market practice rule notation does not
mean that no market practices exist for the concerned field. The presence of a market practice rule is
merely an indicator of a known market practice. Furthermore, readers should be aware that in addition
to global market practices there may also be country specific requirements that should be considered
when using the field. For more details on PMPG market practice documentation, refer to
www.pmpg.info.
• EXAMPLES provides one or more examples of the field as it will be formatted/used.

MT Mapping
MT mapping provides an explanation of how to map the fields of the message into another Swift
message, either of the same or a different message type.

MT Examples
Examples are provided to illustrate the correct use of a message. Examples always include the following
information:
• Narrative provides a brief description of a transaction
• Information Flow illustrates the relationships between the parties involved in the message. An
explanation of the flow diagram can be found in the Standards MT General Information.
• Swift Message provides the message using the defined Swift format, and providing an explanation,
where necessary, of the fields which have been used.

19 July 2024 8
Category 4 - Collections and Cash Letters
For Standards MT November 2024 Introduction
Message Reference Guide

Euro - Impact on Category Message Standards

Deletion of the National Currency Denomination Currency Codes

See the Standards MT General Information for full details of the Euro-Related Information (ERI) and the
impact on Standards MT message types.

19 July 2024 9
Category 4 - Collections and Cash Letters
For Standards MT November 2024 Part 1 - Collections
Message Reference Guide

Part 1 - Collections

19 July 2024 10
Category 4 - Collections and Cash Letters
For Standards MT November 2024 Collections Message Types
Message Reference Guide

Collections Message Types

The following table lists all Collections message types defined in Category 4.
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) and whether the use of the
message requires registration with Swift for use in a message user group (Y or N).

MT MT Name Purpose Signed(1) Max. MUG

Length

400 Advice of Payment Advises of a payment under a Y 2,000 N

collection or part thereof. It also
handles the settlement of proceeds.

410 Acknowledgement Acknowledges receipt of a collection. Y 2,000 N

It also specifies if the collecting bank
does not intend to act in accordance
with the collection instruction.

412 Advice of Acceptance Informs the remitting bank of the Y 2,000 N

acceptance of one or more drafts
under one collection instruction.

416 Advice of Non- Advises of the non-payment or non- Y 10,000 Y

Payment/Non- acceptance under a previously
Acceptance received collection.

420 Tracer Enquires about documents sent for Y 2,000 N

collection.

422 Advice of Fate and Advises the remitting bank of the fate Y 2,000 N
Request for of one or more collection documents;
Instructions usually accompanied by one or more
questions or requests.

430 Amendment of Amends collection instructions. Y 2,000 N

Instructions

(1) A Relationship Management Application (RMA) authorisation is required in order to sign a message.

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 MySwift > Order, change or
terminate products > Order Products and Services > Message User Group (MUG).
To withdraw from a MUG, use the Terminate your MUG subscription request. The form is
available through MySwift > Order, change or terminate products > Terminate and
deactivate > Message User Group (MUG).
To get the list of other members of a particular MUG, please contact Support.

19 July 2024 11
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 400 Advice of Payment
Message Reference Guide

MT 400 Advice of Payment

MT 400 Scope
This message type is sent by the collecting bank to the remitting bank.
It may also be sent:
• on behalf of the collecting bank by its branch/affiliate bank to the remitting bank or branch/affiliate of
that bank
• by a collecting bank to another collecting bank
It is used to advise a payment under a collection or a part thereof and may also be used for the
settlement of proceeds. The account relationship between the Sender and the Receiver is used, unless
expressly stated otherwise in the message.
This message must never be sent to a bank acting solely as a reimbursement bank. In this case, the
appropriate message type is an MT 202 Financial Institution Transfer.

MT 400 Format Specifications

MT 400 Advice of Payment

Status Tag Field Name Content/Options No.

M 20 Sending Bank's TRN 16x 1

M 21 Related Reference 16x 2

M 32a Amount Collected A, B, or K 3

M 33A Proceeds Remitted 6!n3!a15d 4

O 52a Ordering Bank A or D 5

O 53a Sender's Correspondent A, B, or D 6

O 54a Receiver's Correspondent A, B, or D 7

O 57a Account With Bank A or D 8

O 58a Beneficiary Bank A, B, or D 9

O 71B Details of Charges 6*35x 10

O 72 Sender to Receiver Information 6*35x 11

O 73 Details of Amounts Added 6*35x 12

M = Mandatory, O = Optional - Network Validated Rules may apply

19 July 2024 12
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 400 Advice of Payment
Message Reference Guide

MT 400 Network Validated Rules

C1 Field 57a may only be present if fields 53a and 54a are both present (Error code(s): C11).

C2 The currency code in the amount fields 32a and 33A must be the same (Error code(s): C02).

MT 400 Field Specifications

MT 400 - 1. Field 20: Sending Bank's TRN

Format
16x

Presence
Mandatory

Definition
This field specifies the collection number which has been assigned by the Sender of the message.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

MT 400 - 2. Field 21: Related Reference

Format
16x

Presence
Mandatory

Definition
This field specifies the collection number of the Receiver of the message.
Codes
If the reference cannot be contained in this field, the code 'SEE72' may be used and the reference placed
in field 72.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

19 July 2024 13
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 400 Advice of Payment
Message Reference Guide

MT 400 - 3. Field 32a: Amount Collected

Format
Option A 6!n3!a15d (Date)(Currency)(Amount)

Option B 3!a15d (Currency)(Amount)

Option K 1!a3!n2!a3!a15d (Day/Month)(Number of Days/Months)

(Code)(Currency)(Amount)

Presence
Mandatory (referenced in rule C2)

Definition
This field contains the maturity date as indicated in the collection instruction, followed by the currency
code and the amount of principal paid or to be paid by the drawee.

Codes
In option K, Day/Month must contain one of the following codes (Error code(s): T61):

D Days Period is expressed as a number of days.

M Months Period is expressed as a number of months.

Codes
In option K, Code must contain one of the following codes specifying additional information about the
maturity period (Error code(s): T20):

BE After the date of the bill of exchange.

CC After customs clearance of goods.

FD After goods pass food and drug administration.

FP First presentation.

GA After arrival of goods.

ID After invoice date.

ST After sight.

TD After date of transport documents.

XX See field 72 for specification.

Network Validated Rules

In option A, date must be a valid date expressed as YYMMDD (Error code(s): T50).
Currency must be a valid ISO 4217 currency code (Error code(s): T52).

19 July 2024 14
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 400 Advice of Payment
Message Reference Guide

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).

Usage Rules
Option A must be used when the maturity is at a fixed date.
Option B must be used when the maturity date is not known.
Option K must be used when the maturity date is expressed as a period of time, with additional
information needed to calculate the maturity date.
Traditional collection terms, for example, primo, ultimo, etc., must be expressed in the ISO date format,
using option A.
Example
:32A:081216EUR100000,
(EUR 100000, on 16 Dec 2008)
:32B:EUR100000,
(EUR 100000, no maturity date)
:32K:D060STEUR100000,
(EUR 100000, 60 days after sight)
:32K:D000STEUR100000,
(EUR 100000, at sight)
:32K:M001IDEUR100000,
(EUR 100000, 1 month after invoice date)

MT 400 - 4. Field 33A: Proceeds Remitted

Format
Option A 6!n3!a15d (Date)(Currency)(Amount)

Presence
Mandatory (referenced in rule C2)

Definition
This field specifies the value date, currency code and the amount remitted.

Network Validated Rules

Date must be a valid date expressed as YYMMDD (Error code(s): T50).
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 the specified currency (Error code(s): C03, T40, T43).

19 July 2024 15
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 400 Advice of Payment
Message Reference Guide

Usage Rules
Amount will normally be equal to the amount specified in field 32a plus any amount(s) specified in field
73, less any amount(s) specified in field 71B.

MT 400 - 5. Field 52a: Ordering Bank

Format
Option A [/1!a][/34x] (Party Identifier)
4!a2!a2!c[3!c] (Identifier Code)

Option D [/1!a][/34x] (Party Identifier)

4*35x (Name and Address)

Presence
Optional

Definition
This field identifies the collecting branch or affiliate bank on behalf of which the message was sent. It
must specify a branch or an affiliate of the Sender.

Network Validated Rules

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).

MT 400 - 6. Field 53a: Sender's Correspondent

Format
Option A [/1!a][/34x] (Party Identifier)
4!a2!a2!c[3!c] (Identifier Code)

Option B [/1!a][/34x] (Party Identifier)

[35x] (Location)

Option D [/1!a][/34x] (Party Identifier)

4*35x (Name and Address)

Presence
Optional (referenced in rule C1)

Definition
Where required, this field identifies the account or branch of the Sender, or another bank, through which
the Sender will provide the proceeds of the collection to the Receiver.

Network Validated Rules

Identifier Code must be a registered financial institution BIC (Error code(s): T27, T28, T29, T45).

19 July 2024 16
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 400 Advice of Payment
Message Reference Guide

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 absence of field 53a and/or field 54a means that the single direct account relationship between the
Sender and the Receiver, in the currency of the credit, will be used to remit the collection proceeds.

MT 400 - 7. Field 54a: Receiver's Correspondent

Format
Option A [/1!a][/34x] (Party Identifier)
4!a2!a2!c[3!c] (Identifier Code)

Option B [/1!a][/34x] (Party Identifier)

[35x] (Location)

Option D [/1!a][/34x] (Party Identifier)

4*35x (Name and Address)

Presence
Conditional (see rule C1)

Definition
Where required, this field specifies the branch of the Receiver, or another bank, at which the proceeds of
the collection will be made available to the Receiver.

Network Validated Rules

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 absence of field 53a and/or field 54a means that the single direct account relationship between the
Sender and the Receiver, in the currency of the credit, will be used to remit the collection proceeds.

MT 400 - 8. Field 57a: Account With Bank

Format
Option A [/1!a][/34x] (Party Identifier)
4!a2!a2!c[3!c] (Identifier Code)

Option D [/1!a][/34x] (Party Identifier)

4*35x (Name and Address)

Presence
Conditional (see rule C1)

19 July 2024 17
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 400 Advice of Payment
Message Reference Guide

Definition
This field identifies the account with bank.
Network Validated Rules
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
This field may only be used in those cases where the funds will be made available to the Receiver
through a bank other than that indicated in field 54a, that is, the bank in field 54a will remit the funds to
the bank in this field for further credit to the Receiver.
When this field is used, the content of field 57a in the subsequent MT 202/203 Financial Institution
Transfer message sent by the Sender of the MT 400 will be the same.

MT 400 - 9. Field 58a: Beneficiary Bank

Format
Option A [/1!a][/34x] (Party Identifier)
4!a2!a2!c[3!c] (Identifier Code)

Option B [/1!a][/34x] (Party Identifier)

[35x] (Location)

Option D [/1!a][/34x] (Party Identifier)

4*35x (Name and Address)

Presence
Optional

Definition
This field identifies the Receiver's branch or affiliate that initiated the collection. It is the party which is to
be credited with the proceeds of the collection.

Network Validated Rules

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).

MT 400 - 10. Field 71B: Details of Charges

Format
Option B 6*35x (Narrative)

In addition to narrative text, the following line formats may be used:

19 July 2024 18
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 400 Advice of Payment
Message Reference Guide

Line 1 /8a/[3!a13d][additional (Code)(Currency)(Amount)

information] (Narrative)

Lines 2-6 [//continuation of additional (Narrative)

information] or
or (Code)(Currency)(Amount)
[/8a/[3!a13d][additional (Narrative)
information]]

Presence
Optional

Definition
This field specifies the deductions made from the total amount collected (field 32a).

Codes
One of the following codes may be used in Code, followed by the currency code and amount:

AGENT Agent's Commission

COMM Our Commission

CORCOM Our Correspondent's Commission

DISC Commercial Discount

INSUR Insurance Premium

POST Our Postage

STAMP Stamp Duty

TELECHAR Teletransmission Charges

WAREHOUS Wharfing and Warehouse

Usage Rules
This field will only be used for deductions in the same currency as that in which the collection has been
paid and remitted. For charges in other currencies, field 72 must be used.
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.

Example
:71B:/AGENT/USD50,

MT 400 - 11. Field 72: Sender to Receiver Information

Format
6*35x (Narrative)

19 July 2024 19
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 400 Advice of Payment
Message Reference Guide

In addition to narrative text, structured text with the following line formats may be used:

Line 1 /8c/[additional information] (Code)(Narrative)

Lines 2-6 [//continuation of additional (Narrative)

information] or
or (Code)(Narrative)
[/8c/[additional information]]

Presence
Optional

Definition
This field specifies additional information for the Receiver.

Codes
One or more of the following codes may be used in Code:

ALCHAREF All charges have

been refused by
drawee(s).

BNF Beneficiary Information following is for the beneficiary.

OUCHAREF Our charges Our charges have been refused by drawee(s).

refused

PHONBEN Telephone Please advise/contact the beneficiary by phone.

beneficiary

REC Receiver Instructions following are for the Receiver of the message.

TELEBEN Telecommunication Please advise the beneficiary by the most efficient means of
telecommunication.

TSU Trade Services The code placed between slashes ('/') must be followed by the
Utility transaction TSU transaction identifier, a slash ('/'), the invoice number, a
slash ('/') and the amount paid.

UCHAREF Your charges Your charges have been refused by drawee(s).

refused

Usage Rules
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.
This field may include ERI, as specified in the chapter entitled "Euro-Related Information (ERI)" in the
Standards MT General Information.

19 July 2024 20
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 400 Advice of Payment
Message Reference Guide

MT 400 - 12. Field 73: Details of Amounts Added

Format
6*35x (Narrative)

In addition to narrative text, the following line formats may be used:

Line 1 /8a/[3!a13d][additional (Code)(Currency)(Amount)

information] (Narrative)

Lines 2-6 [//continuation of additional (Narrative)

information] or
or (Code)(Currency)(Amount)
[/8a/[3!a13d][additional (Narrative)
information]]

Presence
Optional

Definition
This field specifies the details of amounts added to the amount of principal.

Codes
For amounts frequently added, the codes shown below may be used in Code, followed by the amount
which has been added:

INTEREST Interest collected

RETCOMM Return commission Return commission given by the collecting bank.

YOURCHAR Your charges Remitting bank's charges collected.

collected

Usage Rules
This field will only be used for amounts added in the same currency as that in which the collection has
been paid and remitted. Amounts added in other currencies must be explained in field 72.
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.

MT 400 Examples

Advice of Payment
Narrative
Kredietbank, Brussels, sends an advice of payment to Banca Nazionale del Lavoro, Rome, with the
following information:

19 July 2024 21
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 400 Advice of Payment
Message Reference Guide

Kredietbank's Reference: COL456

Banca Nazionale del Lavoro's Reference: REM432

Amount Collected: EUR 1,000,000

Terms: Payable at sight

Charges: EUR 200 Amendment Fee

EUR 260 Stamp Duty

Proceeds Remitted: EUR 999,540

Value Date: 5 August 2012

(To review the MT 410, 412, 420, 422 and 430 messages concerning this collection, see the respective
Example sections).

Information Flow

Sender Kredietbank
(Collecting Bank) Brussels

MT

MT 400

Receiver Banca Nazionale del Lavoro

(Remitting Bank) Rome
D0040001

SWIFT Message
Explanation Format

Sender KREDBEBB

Message Type 400

Receiver BNLIITRR

Message Text

Sending Bank's TRN :20:COL456

Related Reference :21:REM432

Amount Collected :32K:D000STEUR1000000,

19 July 2024 22
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 400 Advice of Payment
Message Reference Guide

Explanation Format

Proceeds Remitted :33A:080805EUR999540,

Details of Charges :71B:/STAMP/EUR260,

AMENDMENT FEE EUR200,

End of Message Text/Trailer

Message A Advice of Payment

Narrative
Goods with a value of US dollars 6,000 were exported from Germany to England. Deutsche Bank,
Hamburg, sent the documents to Royal Bank of Scotland, Manchester, for collection.
Royal Bank of Scotland sends the advice of payment to Deutsche Bank, Hamburg, with the following
information:

Royal Bank of Scotland's Reference: C67211

Deutsche Bank's Reference: 421337HBG

Amount Collected: USD 6,000

Terms: Payable at sight

Charges: USD 15 Commission

Proceeds Remitted: USD 5,985

Value Date: 30 July 2012

Payable through: Royal Bank of Scotland, London, to Deutsche Bank,

Frankfurt, at Bank of New York, New York

19 July 2024 23
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 400 Advice of Payment
Message Reference Guide

Information Flow

Sender Royal Bank of Scotland

(Collecting Bank) Manchester

Sender's Royal Bank of Scotland

Correspondent London
(MT 202)
53a

MT

Receiver's Bank of New York

Correspondent MT 400 New York
54a

Account With Deutsche Bank

Institution Frankfurt
57a
Receiver Deutsche Bank
(Remitting Bank) Hamburg

D0040002
SWIFT Message
Explanation Format

Sender RBOSGB2M

Message Type 400

Receiver DEUTDEHH

Message Text

Sending Bank's TRN :20:C67211

Related Reference :21:421337HBG

Amount Collected :32K:D000STUSD6000,

Proceeds Remitted :33A:120730USD5985,

Sender's Correspondent (1) :53A:RBOSGB2L

Receiver's Correspondent (2) :54A:BONYUS33

Account With Bank (3) :57A:DEUTDEFF

Details of Charges :71B:/COMM/USD15,

19 July 2024 24
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 400 Advice of Payment
Message Reference Guide

Explanation Format

End of Message Text/Trailer

(1) Royal Bank of Scotland, London, which will provide reimbursement of the proceeds of the collection on behalf of the Sender.
(2) Bank of New York, NY, which will receive the proceeds of the collection for credit to Deutsche Bank, Frankfurt.
(3) Deutsche Bank, Frankfurt, which will be credited with the proceeds of the collection in favour of the Receiver of the message.

Message B General Financial Institution Transfer

Narrative
The cover payment is sent by Royal Bank of Scotland, Manchester directly to Bank of New York, New
York.

Information Flow

Sender Royal Bank of Scotland

(Collecting Bank) Manchester

MT

Sender's Royal Bank of Scotland

Correspondent MT 202 London
53a

Receiver Bank of New York

New York

Account With Deutsche Bank

Institution 57a Frankfurt

Beneficiary Institution Deutsche Bank

(Remitting Bank) 58a Hamburg
D0040003

SWIFT Message
Explanation Format

Sender RBOSGB2M

Message Type 202

Receiver BONYUS33

19 July 2024 25
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 400 Advice of Payment
Message Reference Guide

Explanation Format

Unique End-to-end Transaction Reference 121:4732689d-efab-4fbe-9f09-fb75eb563bb9

Message Text

Transaction Reference Number :20:C67211

Related Reference :21:421337HBG

Value Date/Currency Code/Amount :32A:120730USD5985,

Sender's Correspondent (1) :53A:RBOSGB2L

Account With Institution :57A:DEUTDEFF

Beneficiary Institution :58A:DEUTDEHH

End of Message Text/Trailer

(1) Royal Bank of Scotland, London, on behalf of its Manchester branch, will provide the funds to Bank of New York, NY.

19 July 2024 26
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 410 Acknowledgement
Message Reference Guide

MT 410 Acknowledgement

MT 410 Scope
This message type is sent by a collecting bank to a remitting bank to acknowledge the receipt of a
collection.
It may also be sent by a collecting bank to another collecting bank.
Unless otherwise expressly stated, this message type states that the collecting bank intends to act in
accordance with the collection instruction.

MT 410 Format Specifications

MT 410 Acknowledgement

Status Tag Field Name Content/Options No.

----->

M 20 Sending Bank's TRN 16x 1

M 21 Related Reference 16x 2

M 32a Amount Acknowledged A, B, or K 3

-----|

O 72 Sender to Receiver Information 6*35x 4

M = Mandatory, O = Optional - Network Validated Rules may apply

MT 410 Network Validated Rules

C1 Fields 20, 21, and 32a may not appear more than ten times (Error code(s): T10).

C2 The currency code in the amount field 32a must be the same for all occurrences of this field in the
message (Error code(s): C02).

MT 410 Usage Rules

• If the collecting bank does not apply the ICC Uniform Rules for collections, this should be stated in the
message.
• The MT 410 may be a single or a multiple message. When it is a multiple message, it must refer to
one collection (for at least one of the banks).
• When one of the banks views a collection with more than one item as more than one collection, fields
20 and 21 are to be used as follows:
The remitting bank sends what it considers to be two separate collections (references '1' and '2') to the
collecting bank.

19 July 2024 27
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 410 Acknowledgement
Message Reference Guide

The collecting bank, when sending an acknowledgement, considers this to be one item (reference 'A').
Fields 20 and 21, will appear as:

1st repetitive sequence: :20:A

:21:1

2nd repetitive sequence: :20:A

:21:2

The remitting bank sends what it considers to be one collection (reference '1') to the collecting bank.
The collecting bank, when sending an acknowledgement, considers this to be two items (reference 'A'
and 'B').
Fields 20 and 21 will appear as:

1st repetitive sequence: :20:A

:21:1

2nd repetitive sequence: :20:B

:21:1

• A collection instruction involving two or more currencies must be acknowledged by two or more
separate MT 410s.

MT 410 Field Specifications

MT 410 - 1. Field 20: Sending Bank's TRN

Format
16x

Presence
Mandatory (referenced in rule C1)

Definition
This field contains the collection number which has been assigned by the Sender of the message.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

MT 410 - 2. Field 21: Related Reference

Format
16x

19 July 2024 28
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 410 Acknowledgement
Message Reference Guide

Presence
Mandatory (referenced in rule C1)
Definition
This field contains the collection number of the Receiver of the message.

Codes
If the reference cannot be contained in this field, the code 'SEE72' may be used and the reference placed
in field 72.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

MT 410 - 3. Field 32a: Amount Acknowledged

Format
Option A 6!n3!a15d (Date)(Currency)(Amount)

Option B 3!a15d (Currency)(Amount)

Option K 1!a3!n2!a3!a15d (Day/Month)(Number of Days/Months)

(Code)(Currency)(Amount)

Presence
Mandatory (referenced in rules C1 and C2)

Definition
This field contains the maturity date as indicated in the collection instruction, followed by the currency
code and the amount of the collection acknowledged.

Codes
In option K, Day/Month must contain one of the following codes (Error code(s): T61):

D Days Period is expressed as a number of days.

M Months Period is expressed as a number of months.

Codes
In option K, Code must contain one of the following codes specifying additional information about the
maturity period (Error code(s): T20):

BE After the date of the bill of exchange.

CC After customs clearance of goods.

FD After goods pass food and drug administration.

FP First presentation.

19 July 2024 29
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 410 Acknowledgement
Message Reference Guide

GA After arrival of goods.

ID After invoice date.

ST After sight.

TD After date of transport documents.

XX See field 72 for specification.

Network Validated Rules

In option A, Date must be a valid date expressed as YYMMDD (Error code(s): T50).
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 the
maximum length includes it. 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).

Usage Rules
Option A must be used when the maturity is at a fixed date.
Option B must be used when the maturity date is not known.
Option K must be used when the maturity date is expressed as a period of time, with additional
information needed to calculate the maturity date.
Traditional collection terms, for example, primo, ultimo, etc. must be expressed in the ISO date format,
using option A.

Example
:32A:081216EUR100000,
(EUR100000, on 12 Dec 2008)
:32B:EUR100000,
(EUR 100000, no maturity date)
:32K:D060STEUR100000,
(EUR 100000, 60 days after sight)
:32K:D000STEUR100000,
(EUR 100000, at sight)
:32K:M001IDEUR100000,
(EUR 100000, 1 month after invoice date)

MT 410 - 4. Field 72: Sender to Receiver Information

Format
6*35x (Narrative)

In addition to narrative text, structured text with the following line formats may be used:

19 July 2024 30
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 410 Acknowledgement
Message Reference Guide

Line 1 /8c/[additional information] (Code)(Narrative)

Lines 2-6 [//continuation of additional (Narrative)

information] or
or (Code)(Narrative)
[/8c/[additional information]]

Presence
Optional

Definition
This field specifies additional information about the collection.
Codes
One or more of the following codes may be used in Code:

DRAWEE Drawee not known Insufficient information to identify/contact drawees. Please

give us further instructions.

FORWARD Forwarding the We are forwarding the collection(s) to our branch ... Please
collection address any further communication to them.

REC Receiver Instructions following are for the Receiver of the message.

Usage Rules
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.

MT 410 Examples
Narrative
William Lesis, whose bank is Kredietbank, Brussels, imports shoes at a cost of Euro 2,300,000 from
Martino Gagli, whose bank is Banca Nazionale del Lavoro in Rome.
Banca Nazionale del Lavoro sends the documents for collection (against payment), together with a sight
draft, to Kredietbank.
(To review the MT 400, 412, 420, 422 and 430 messages related to this collection, see the respective
Example sections.)

19 July 2024 31
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 410 Acknowledgement
Message Reference Guide

Information Flow

Sender Kredietbank
Brussels

MT
(MT 400)
MT 410

Receiver Banca Nazionale del Lavoro

Rome

D0040006
SWIFT Message
Explanation Format

Sender KREDBEBB

Message Type 410

Receiver BNLIITRR

Message Text

Sending Bank's TRN (1) :20:COL456

Related Reference (2) :21:REM432

Amount Acknowledged (3) :32K:D000STEUR2300000,

End of Message Text/Trailer

(1) The reference assigned by Kredietbank.

(2) The reference assigned by Banca Nazionale del Lavoro.
(3) The maturity period (payable at sight), currency code and amount of the collection.

19 July 2024 32
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 412 Advice of Acceptance
Message Reference Guide

MT 412 Advice of Acceptance

MT 412 Scope
This message type is sent by the collecting bank to the remitting bank.
It may also be sent by a collecting bank to another collecting bank.
It is used to inform the Receiver of the acceptance of one or more drafts under one collection instruction.

MT 412 Format Specifications

MT 412 Advice of Acceptance

Status Tag Field Name Content/Options No.

----->

M 20 Sending Bank's TRN 16x 1

M 21 Related Reference 16x 2

M 32A Maturity Date, Currency Code, Amount Accepted 6!n3!a15d 3

-----|

O 72 Sender to Receiver Information 6*35x 4

M = Mandatory, O = Optional - Network Validated Rules may apply

MT 412 Network Validated Rules

C1 Fields 20, 21 and 32A may not appear more than ten times (Error code(s): T10).

C2 The currency code in the amount field 32A must be the same for all occurrences of this field in the
message (Error code(s): C02).

MT 412 Usage Rules

• The MT 412 may be a single or a multiple message. When it is a multiple message, it must refer to
one collection (for at least one of the banks) or one collection message.
• When one of the banks views a collection with more than one item as more than one collection, fields
20 and 21 are to be used as follows:
The remitting bank sends what it considers to be two separate collections (references '1' and '2') to the
collecting bank.
The collecting bank, when sending an acknowledgement, considers this to be one item (reference 'A').
Fields 20 and 21, will appear as:

19 July 2024 33
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 412 Advice of Acceptance
Message Reference Guide

1st repetitive sequence: :20:A

:21:1

2nd repetitive sequence: :20:A

:21:2

The remitting bank sends what it considers to be one collection (reference '1') to the collecting bank.
The collecting bank, when sending an acknowledgement, considers this to be two items (reference 'A'
and 'B').
Fields 20 and 21 will appear as:

1st repetitive sequence: :20:A

:21:1

2nd repetitive sequence: :20:B

:21:1

MT 412 Field Specifications

MT 412 - 1. Field 20: Sending Bank's TRN

Format
16x

Presence
Mandatory (referenced in rule C1)

Definition
This field contains the collection number which has been assigned by the Sender of the message.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

MT 412 - 2. Field 21: Related Reference

Format
16x

Presence
Mandatory (referenced in rule C1)

19 July 2024 34
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 412 Advice of Acceptance
Message Reference Guide

Definition
This field contains the collection number of the remitting bank.
Codes
If the reference cannot be contained in this field, the code 'SEE72' may be used and the reference placed
in field 72.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

MT 412 - 3. Field 32A: Maturity Date, Currency Code, Amount Accepted

Format
Option A 6!n3!a15d (Date)(Currency)(Amount)

Presence
Mandatory (referenced in rules C1 and C2)
Definition
This field specifies the maturity date, currency code and the amount of the collection which has been
accepted.

Network Validated Rules

Date must be a valid date expressed as YYMMDD (Error code(s): T50).
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 the specified currency (Error code(s): C03, T40, T43).

MT 412 - 4. Field 72: Sender to Receiver Information

Format
6*35x (Narrative)

In addition to narrative text, structured text with the following line formats may be used:

Line 1 /8c/[additional information] (Code)(Narrative)

Lines 2-6 [//continuation of additional (Narrative)

information] or
or (Code)(Narrative)
[/8c/[additional information]]

Presence
Optional

19 July 2024 35
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 412 Advice of Acceptance
Message Reference Guide

Definition
This field specifies additional information for the Receiver.
Codes
One or more of the following codes may be used in Code:

ALCHAREF All charges refused All charges have been refused by drawee(s).

DOMICIL Domiciled at The collection has been domiciled at ...

HOLD Hold The accepted draft(s) is/are being held with us in safe custody
and at your disposal for presentation for payment at maturity.

OUCHAREF Our charges Our charges have been refused by drawee(s).

refused

REC Receiver Instructions following are for the Receiver of the message.

RETURN Return The accepted draft(s) is/are being returned to you by airmail.

UCHAREF Your charges Your charges have been refused by drawee(s).

refused

Usage Rules
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.

MT 412 Examples
Narrative
William Lesis, whose bank is Kredietbank, Brussels, imports shoes at a cost of Euro 2,300,000 from
Martino Gagli, whose bank is Banca Nazionale del Lavoro in Rome.
Banca Nazionale del Lavoro sends the documents for collection (against payment), together with a sight
draft, to Kredietbank.
(To review the MT 400, 410, 420, 422 and 430 messages relating to this collection, see the respective
Example sections.)
The terms of the collection state that Mr. Lesis will pay Euro 1,000,000 on arrival of the goods and will
accept a 90 days draft for the remaining Euro 1,300,000.
Kredietbank, Brussels, informs Mr. Lesis that his conditions have been met. Mr. Lesis accepts the draft
and pays EUR 1,000,000. Kredietbank sends an advice of acceptance for the deferred payment of EUR
1,300,000 with a maturity date of 2 November 2012.

19 July 2024 36
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 412 Advice of Acceptance
Message Reference Guide

Information Flow

Sender Kredietbank
Brussels

MT

MT 412

Receiver Banca Nazionale del Lavoro

Rome

D0040007
SWIFT Message
Explanation Format

Sender KREDBEBB

Message Type 412

Receiver BNLIITRR

Message Text

Sending Bank's TRN :20:COL456

Related Reference :21:REM432

Maturity Date/Currency Code/Amount :32A:121102EUR1300000,

Sender to Receiver Information (1) :72:/HOLDING/

End of Message Text/Trailer

(1) /HOLDING/ meaning that the accepted draft is being held in safe custody for presentation for payment at maturity.

19 July 2024 37
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 416 Advice of Non-Payment/Non-Acceptance
Message Reference Guide

MT 416 Advice of Non-Payment/Non-Acceptance

Note The use of this message type requires Message User Group (MUG) registration.

MT 416 Scope
This message type is sent by the collecting bank to the remitting bank.
It may also be sent:
• to the remitting bank via another financial institution
• by a presenting bank to a collecting bank
It is used to advise of non-payment or non-acceptance under a previously received collection or part
thereof.

MT 416 Format Specifications

The MT 416 consists of two sequences:
• Sequence A General Information is a single occurrence mandatory sequence and contains information
to be applied to all individual transactions detailed in sequence B.
• Sequence B Non-Payment/Non-Acceptance Details, is a repetitive mandatory sequence; each
occurrence provides details of one individual document which was non-paid/non-accepted.
MT 416 Advice of Non-Payment/Non-Acceptance

Status Tag Field Name Content/Options No.

Mandatory Sequence A General Information

M 20 Sender's Reference 16x 1

M 21 Related Reference 16x 2

O 23E Advice Type 4!c[/30x] 3

O 51A Sending Institution [/1!a][/34x]<crlf>4!a2!a2!c[3!c] 4

O 53a Sender's Correspondent A or B 5

O 71F Sender's Charges 3!a15d 6

O 77A Reason for Non-Payment/Non-Acceptance 20*35x 7

End of Sequence A General Information

-----> Mandatory Repetitive Sequence B Non-Payment/Non-Acceptance Details

M 21A Related Sequence Reference 16x 8

O 23E Advice Type 4!c[/30x] 9

O 21C Principal's Reference 35x 10

19 July 2024 38
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 416 Advice of Non-Payment/Non-Acceptance
Message Reference Guide

Status Tag Field Name Content/Options No.

M 32a Face Amount of Document(s) A, B, or K 11

O 50D Principal [/1!a][/34x]<crlf>4*35x 12

O 59 Drawee [/34x]<crlf>4*35x 13

O 71F Sender's Charges 3!a15d 14

O 77A Reason for Non-Payment/Non-Acceptance 20*35x 15

-----| End of Sequence B Non-Payment/Non-Acceptance Details

M = Mandatory, O = Optional - Network Validated Rules may apply

MT 416 Network Validated Rules

C1 Field 23E must be present either in sequence A or in each occurrence of sequence B but not in both
(Error code(s): D78).

Sequence A Sequence B
if field 23E is ... then field 23E is ...

Present Not allowed

Not present Mandatory

C2 When present in sequence A, fields 71F and 77A must, independently of each other, not be present
in any occurrence of sequence B. Conversely, when not present in sequence A, fields 71F and 77A
are, independently of each other, optional in any occurrence of sequence B (Error code(s): D83).

Sequence A Sequence B (each occurrence)

if field 71F is ... then field 71F is ...

Present Not allowed

Not present Optional

In sequence A Sequence B (each occurrence)

if field 77A is ... then field 77A is ...

Present Not allowed

Not present Optional

19 July 2024 39
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 416 Advice of Non-Payment/Non-Acceptance
Message Reference Guide

C3 The MT 416 is a 'single currency' message. This means that the currency code in all amount fields,
that is, field 71F in sequence A and fields 32a and 71F in sequence B must be the same for all
occurrences of these fields in the message (Error code(s): C02).

MT 416 Guidelines
When sending the message via FileAct, institutions should bilaterally agree on the maximum size of the
message.

MT 416 Field Specifications

MT 416 - 1. Field 20: Sender's Reference

Format
16x

Presence
Mandatory in mandatory sequence A

Definition
This field specifies the reference to the entire message.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

Usage Rules
The sender's reference must be unique for each message and is part of the message identification and
transaction identification which is used in case of queries, cancellations, etc. This reference must be
quoted in any related confirmation or statement, to the sending financial institution.

MT 416 - 2. Field 21: Related Reference

Format
16x

Presence
Mandatory in mandatory sequence A

Definition
This field specifies the reference to the original collection.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

19 July 2024 40
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 416 Advice of Non-Payment/Non-Acceptance
Message Reference Guide

MT 416 - 3. Field 23E: Advice Type

Format
Option E 4!c[/30x] (Type)(Narrative)

Presence
Conditional (see rule C1) in mandatory sequence A
Definition
This field identifies the type of advice for all transactions contained in this message.

Codes
Type must contain one of the following codes (Error code(s): T47):

NACC Non-acceptance This message contains an advice of non-acceptance.

NPAY No payment This message contains an advice of non-payment.

OTHR Other Used for bilaterally agreed codes and/or information when no other
code exists for the advice type to be specified. The actual bilateral
code and/or information must be specified in Narrative.

Network Validated Rules

Narrative may only be used in combination with 'OTHR' (Error code(s): D81).

MT 416 - 4. Field 51A: Sending Institution

Format
Option A [/1!a][/34x] (Party Identifier)
4!a2!a2!c[3!c] (Identifier Code)

Presence
Optional in mandatory sequence A

Definition
This field identifies the Sender of the message.
Network Validated Rules
This field may only be used in FileAct, and not in FIN (Error code(s): D63).

Usage Rules
In FileAct the sender's reference together with the content of this field provides the message identification
which is to be used in the case of queries, cancellations, etc.
At least the first eight characters of the financial institution BIC in this field must be identical to the
originator of this FileAct message.

19 July 2024 41
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 416 Advice of Non-Payment/Non-Acceptance
Message Reference Guide

MT 416 - 5. Field 53a: Sender's Correspondent

Format
Option A [/1!a][/34x] (Party Identifier)
4!a2!a2!c[3!c] (Identifier Code)

Option B [/1!a][/34x] (Party Identifier)

[35x] (Location)

Presence
Optional in mandatory sequence A

Definition
This field specifies, where required, the account or branch of the Sender through which the Sender wants
non-payment or non-acceptance charges to be reimbursed by the Receiver.

Network Validated Rules

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).

MT 416 - 6. Field 71F: Sender's Charges

Format
Option F 3!a15d (Currency)(Amount)

Presence
Conditional (see rules C2 and C3) in mandatory sequence A

Definition
This field specifies the currency and amount of the total charges due to the Sender for the individual
transaction contained in this message.

Network Validated Rules

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 the specified currency (Error code(s): C03, T40, T43).

MT 416 - 7. Field 77A: Reason for Non-Payment/Non-Acceptance

Format
Option A 20*35x (Narrative)

In addition to narrative text, structured text with the following line formats may be used:

19 July 2024 42
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 416 Advice of Non-Payment/Non-Acceptance
Message Reference Guide

Line 1 /8a/[additional information] (Code)(Narrative)

Lines 2-20 [//continuation of additional (Narrative)

information] or
or (Code)(Narrative)
[/8a/[additional information]]

Presence
Conditional (see rule C2) in mandatory sequence A

Definition
This field contains the reason for non-payment/non-acceptance for all transactions contained in this
message.
Codes
One of the following codes may be used in Code:

HOLD Documents held at your disposal

RETURN Documents being returned to you

Usage Rules
The structured format may also be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.

MT 416 - 8. Field 21A: Related Sequence Reference

Format
Option A 16x

Presence
Mandatory in mandatory sequence B

Definition
This field specifies the reference to the related individual transaction in the original collection.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

MT 416 - 9. Field 23E: Advice Type

Format
Option E 4!c[/30x] (Type)(Narrative)

19 July 2024 43
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 416 Advice of Non-Payment/Non-Acceptance
Message Reference Guide

Presence
Conditional (see rule C1) in mandatory sequence B
Definition
This field identifies the type of advice for the individual transaction in this occurrence of sequence B.

Codes
Type must contain one of the following codes (Error code(s): T47):

NACC Non-acceptance This transaction contains an advice of non-acceptance.

NPAY No payment This transaction contains an advice of non-payment.

OTHR Other Used for bilaterally agreed codes and/or information when no other
code exists for the advice type to be specified. The actual bilateral
code and/or information must be specified in Narrative.

Network Validated Rules

Narrative may only be used in combination with 'OTHR' (Error code(s): D81).

MT 416 - 10. Field 21C: Principal's Reference

Format
Option C 35x

Presence
Optional in mandatory sequence B

Definition
This field specifies the reference allocated by the principal in the original collection.

MT 416 - 11. Field 32a: Face Amount of Document(s)

Format
Option A 6!n3!a15d (Date)(Currency)(Amount)

Option B 3!a15d (Currency)(Amount)

Option K 1!a3!n2!a3!a15d (Day/Month)(Number of Days/Months)

(Code)(Currency)(Amount)

Presence
Mandatory (see rule C3) in mandatory sequence B

Definition
This field specifies the maturity date of the individual document(s) which failed to be collected from the
drawee. This field should therefore not include any charges.

19 July 2024 44
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 416 Advice of Non-Payment/Non-Acceptance
Message Reference Guide

Codes
In option K, Day/Month must contain one of the following codes, followed by the actual number of days or
months (Error code(s): T61):

D Days Period is expressed as a number of days.

M Months Period is expressed as a number of months.

Codes
In option K, Code must contain one of the following codes, to calculate the maturity date specifying
additional information about the maturity period (Error code(s): T20):

BE After the date of the bill of exchange.

ST After sight.

Network Validated Rules

In option A, Date must be a valid date expressed as YYMMDD (Error code(s): T50).
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).

Usage Rules
Option A must be used when the maturity is at a fixed date.
Option B must be used when the maturity date is not known.
Option K must be used when the maturity date is expressed as a period of time, with additional
information needed to calculate the maturity date.
For financial documents payable 'at sight', option K must be used with the number of days or months
being zero, that is, D000ST.
In option K, the codes 'BE' and 'ST' should be used according to the following table:

Financial Document Codes allowed

Bill of Exchange BE, ST

Promissory Note BE, ST

Receipt ST

Example
:32A:061103USD1000,
:32B:USD1000,
:32K:D060STUSD1000,

19 July 2024 45
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 416 Advice of Non-Payment/Non-Acceptance
Message Reference Guide

MT 416 - 12. Field 50D: Principal

Format
Option D [/1!a][/34x] (Party Identifier)
4*35x (Name and Address)

Presence
Optional in mandatory sequence B

Definition
This field identifies the principal which requested the collection of the transaction in this occurrence of
sequence B.

Usage Rules
At a minimum, the principal's name must be present.

MT 416 - 13. Field 59: Drawee

Format
[/34x] (Account)
4*35x (Name and Address)

Presence
Optional in mandatory sequence B

Definition
This field identifies the drawee of the individual transaction in this occurrence of sequence B.

Usage Rules
When this field is used, the drawee's name and address must be present. The account is optional.

MT 416 - 14. Field 71F: Sender's Charges

Format
Option F 3!a15d (Currency)(Amount)

Presence
Optional (referenced in rules C2 and C3) in mandatory sequence B

Definition
This field specifies the currency and amount of the charges due to the Sender for the individual
transaction in this occurrence of sequence B.

Network Validated Rules

Currency must be a valid ISO 4217 currency code (Error code(s): T52).

19 July 2024 46
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 416 Advice of Non-Payment/Non-Acceptance
Message Reference Guide

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 the specified currency (Error code(s): C03, T40, T43).

MT 416 - 15. Field 77A: Reason for Non-Payment/Non-Acceptance

Format
Option A 20*35x (Narrative)

In addition to narrative text, structured text with the following line formats may be used:

Line 1 /8a/[additional information] (Code)(Narrative)

Lines 2-20 [//continuation of additional (Narrative)

information] or
or (Code)(Narrative)
[/8a/[additional information]]

Presence
Optional (referenced in rule C2) in mandatory sequence B

Definition
This field contains the reason for non-payment/non-acceptance for the individual transaction in this
occurrence of sequence B.

Codes
One of the following codes may be used in Code:

HOLD Documents held at your disposal

RETURN Documents being returned to you

Usage Rules
The structured format may also be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.

MT 416 Examples
Narrative
Upon non-payment of the EUR 40,000 draft by the German importer, Verein, Deutsche Bank in Münich,
Germany will send the following MT 416 Advice of Non-Payment/Non-Acceptance to Cariverona Banca in
Verona, Italy, on 1 May 2012.
Deutsche Bank Münich, Germany wants non-payment charges for an amount of EUR 200 to be
reimbursed by Cariverona Banca, Verona, Italy at its Frankfurt branch.

19 July 2024 47
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 416 Advice of Non-Payment/Non-Acceptance
Message Reference Guide

Information Flow

Drawee Verein
(Importer) Munich

Presenting Bank Münchener Bank

Munich

Sender Deutsche Bank

(Collecting Bank) Munich

MT

MT 416

Receiver Cariverona Banca

(Remitting Bank) Verona

Principal Impressa
(Exporter) Verona
D0040008

SWIFT Message
Explanation Format

Sender DEUTDEMM

Message Type 416

Receiver CRVRIT2V

Message Text

Sender's Reference :20:AUSL98765

Related Reference :21:CRVR/1234567

Advice Type :23E:NPAY

Sender's Correspondent :53A:DEUTDEFF

19 July 2024 48
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 416 Advice of Non-Payment/Non-Acceptance
Message Reference Guide

Explanation Format

Sender's Charges :71F:EUR200,

Reason for Non-Payment/Non-Acceptance :77A:REFER TO DRAWEE

Related Sequence Reference :21A:COLL202712346

Face Amount of Document(s) :32B:EUR40000,

End of Message Text/Trailer

19 July 2024 49
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 420 Tracer
Message Reference Guide

MT 420 Tracer

MT 420 Scope
This message type is sent by the remitting bank to the collecting bank.
It may also be sent by a collecting bank to another collecting bank.
It is used to enquire about the fate of documents sent for collection.

MT 420 Format Specifications

MT 420 Tracer

Status Tag Field Name Content/Options No.

----->

M 20 Sending Bank's TRN 16x 1

M 21 Related Reference 16x 2

M 32a Amount Traced A, B, or K 3

-----|

O 30 Date of Collection Instruction 6!n 4

O 59 Drawee [/34x]<crlf>4*35x 5

O 72 Sender to Receiver Information 6*35x 6

M = Mandatory, O = Optional - Network Validated Rules may apply

MT 420 Network Validated Rules

C1 Fields 20, 21 and 32a may not appear more than ten times (Error code(s): T10).

C2 The currency code in the amount field 32a must be the same for all occurrences of this field in the
message (Error code(s): C02).

MT 420 Usage Rules

• As the MT 420 is a special function, the MT 495 Queries message should not be used.
• The MT 420 may be a single or a multiple message. When it is a multiple message, it must refer to
one collection (for at least one of the banks) or one collection message.
• When one of the banks views a collection with more than one item as more than one collection, fields
20 and 21 are to be used as follows:

19 July 2024 50
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 420 Tracer
Message Reference Guide

The remitting bank sends what it considers to be two separate collections (references '1' and '2') to the
collecting bank.
The collecting bank, when sending an acknowledgement, considers this to be one item (reference 'A').
Fields 20 and 21, will appear as:

1st repetitive sequence: :20:A

:21:1

2nd repetitive sequence: :20:A

:21:2

The remitting bank sends what it considers to be one collection (reference '1') to the collecting bank.
The collecting bank, when sending an acknowledgement, considers this to be two items (reference 'A'
and 'B').
Fields 20 and 21 will appear as:

1st repetitive sequence: :20:A

:21:1

2nd repetitive sequence: :20:B

:21:1

• Several references can be indicated in the message when, for at least one of the banks, the amount
traced has several references.
• The answer to an MT 420 is to be made using an MT 422 Advice of Fate and Request for Instructions,
where appropriate.

MT 420 Field Specifications

MT 420 - 1. Field 20: Sending Bank's TRN

Format
16x

Presence
Mandatory (referenced in rule C1)

Definition
This field contains the collection number which has been assigned by the Sender of the message.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

19 July 2024 51
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 420 Tracer
Message Reference Guide

MT 420 - 2. Field 21: Related Reference

Format
16x

Presence
Mandatory (referenced in rule C1)
Definition
This field contains the collection number of the collecting bank, for example, the content of field 20 of the
MT 410 Acknowledgement.

Codes
In cases where the initial message is not sent via SWIFT and the reference cannot be contained in field
21, the code SEE72 may be used and the reference placed in field 72.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

Usage Rules
If the reference of the collecting bank is not known, that is, no acknowledgement has been received, the
code NONREF must appear in this field. When this is the case, field 59 Drawee must be present.

MT 420 - 3. Field 32a: Amount Traced

Format
Option A 6!n3!a15d (Date)(Currency)(Amount)

Option B 3!a15d (Currency)(Amount)

Option K 1!a3!n2!a3!a15d (Day/Month)(Number of Days/Months)

(Code)(Currency)(Amount)

Presence
Mandatory (referenced in rules C1 and C2)

Definition
This field contains the maturity date as indicated in the collection instruction, followed by the currency
code and the aggregate amount of the collection instruction or the amount of the individual collection
traced.

Codes
In option K, Day/Month must contain one of the following codes (Error code(s): T61):

D Days Period is expressed as a number of days.

M Months Period is expressed as a number of months.

19 July 2024 52
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 420 Tracer
Message Reference Guide

Codes
In option K, Code must contain one of the following codes specifying additional information about the
maturity period (Error code(s): T20):

BE After the date of the bill of exchange.

CC After customs clearance of goods.

FD After goods pass food and drug administration.

FP First presentation.

GA After arrival of goods.

ID After invoice date.

ST After sight.

TD After date of transport documents.

XX See field 72 for specification.

Network Validated Rules

In option A, Date must be a valid date expressed in YYMMDD format (Error code(s): T50).
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).

Usage Rules
Option A must be used when the maturity is at a fixed date.
Option B must be used when the maturity date is not known.
Option K must be used when the maturity date is expressed as a period of time, with additional
information needed to calculate the maturity date.
Traditional collection terms, for example, primo, ultimo, etc., must be expressed in the ISO date format,
using option A.

Example
:32A:081216EUR100000,
(EUR100000, on 12 Dec 2008)
:32B:EUR100000,
(EUR 100000, no maturity date)
:32K:D060STEUR100000,
(EUR 100000, 60 days after sight)
:32K:D000STEUR100000,
(EUR 100000, at sight)
:32K:M001IDEUR100000,

19 July 2024 53
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 420 Tracer
Message Reference Guide

(EUR 100000, 1 month after invoice date)

MT 420 - 4. Field 30: Date of Collection Instruction

Format
6!n (Date)

Presence
Optional
Definition
This field specifies the date of the collection instruction.

Network Validated Rules

Date must be a valid date expressed in YYMMDD format (Error code(s): T50).

Usage Rules
If the collection instruction has been amended, this is the date of the original collection instruction.

MT 420 - 5. Field 59: Drawee

Format
[/34x] (Account)
4*35x (Name and Address)

Presence
Conditional (see rule C2)

Definition
This field identifies the drawee.

Usage Rules
When the reference of the collecting bank is not known, that is, NONREF appears in field 21, this field
must be present to enable the collecting bank to identify the collection.
Optional Account must not be used.

MT 420 - 6. Field 72: Sender to Receiver Information

Format
6*35x (Narrative)

In addition to narrative text, structured text with the following line formats may be used:

Line 1 /8c/[additional information] (Code)(Narrative)

19 July 2024 54
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 420 Tracer
Message Reference Guide

Lines 2-6 [//continuation of additional (Narrative)

information] or
or (Code)(Narrative)
[/8c/[additional information]]

Presence
Optional

Definition
This field specifies additional information for the Receiver.

Usage Rules
The structured format may be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.

MT 420 Examples
Narrative
On 8 July 2012, Banca Nazionale del Lavoro, Rome, sends a tracer to Kredietbank, Brussels, to ask the
position regarding a collection of Euro 2,300,000.
(To review the MT 400, 410, 412, 422 and 430 messages related to this collection, see the respective
Example sections.)

Information Flow

Sender Banca Nazionale del Lavoro

(Remitting Bank) Rome

MT

MT 420

Receiver Kredietbank
(Collecting Bank) Brussels
D0040009

SWIFT Message
Explanation Format

Sender BNLIITRR

19 July 2024 55
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 420 Tracer
Message Reference Guide

Explanation Format

Message Type 420

Receiver KREDBEBB

Message Text

Sending Bank's TRN :20:REM432

Related Reference :21:COL456

Amount Traced :32K:D000STEUR2300000,

End of Message Text/Trailer

19 July 2024 56
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 422 Advice of Fate and Request for Instructions
Message Reference Guide

MT 422 Advice of Fate and Request for Instructions

MT 422 Scope
This message type is sent by the collecting bank to the remitting bank.
It may also be sent by a collecting bank to another collecting bank.
It is used to advise the Receiver of the status of collection documents received by the collecting bank.
Since an advice of fate generally includes one or more questions or requests, the two functions are
included in this one message type.

MT 422 Format Specifications

MT 422 Advice of Fate and Request for Instructions

Status Tag Field Name Content/Options No.

----->

M 20 Sending Bank's TRN 16x 1

M 21 Related Reference 16x 2

O 32a Amount of Collection A, B, or K 3

-----|

O 72 Sender to Receiver Information 6*35x 4

O 75 Queries 6*35x 5

O 76 Answers 6*35x 6

M = Mandatory, O = Optional - Network Validated Rules may apply

MT 422 Network Validated Rules

C1 Fields 20, 21 and 32a may not appear more than ten times (Error code(s): T10).

C2 At least one of the fields in the non-repetitive sequence (Field 72, 75 or 76) must be present (Error
code(s): C10).

C3 The currency code in the amount field 32a must be the same for all occurrences of this field in the
message (Error code(s): C02).

19 July 2024 57
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 422 Advice of Fate and Request for Instructions
Message Reference Guide

MT 422 Usage Rules

• The MT 422 is sent in response to a tracer.
• The MT 422 may be a single or a multiple message. When it is a multiple message, it must refer to
one collection (for at least one of the banks) or one collection message.
• When one of the banks views a collection with more than one item as more than one collection, fields
20 and 21 are to be used as follows:
The remitting bank sends what it considers to be two separate collections (references '1' and '2') to the
collecting bank.
The collecting bank, when sending an acknowledgement, considers this to be one item (reference 'A')
Fields 20 and 21, will appear as:

1st repetitive sequence: :20:A

:21:1

2nd repetitive sequence: :20:A

:21:2

The remitting bank sends what it considers to be one collection (reference '1') to the collecting bank.
The collecting bank, when sending an acknowledgement, considers this to be two items (reference 'A'
and 'B').
Fields 20 and 21 will appear as:

1st repetitive sequence: :20:A

:21:1

2nd repetitive sequence: :20:B

:21:1

• One MT 422 may be sent for several amounts of a collection when they refer to the same queries or
answers.

MT 422 Field Specifications

MT 422 - 1. Field 20: Sending Bank's TRN

Format
16x

Presence
Mandatory (referenced in rule C1)

19 July 2024 58
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 422 Advice of Fate and Request for Instructions
Message Reference Guide

Definition
This field contains the collection number which has been assigned by the Sender of the message.
Network Validated Rules
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//'.

MT 422 - 2. Field 21: Related Reference

Format
16x

Presence
Mandatory (referenced in rule C1)

Definition
This field contains the collection number of the Receiver of the message.

Codes
In cases where the initial message was not sent via SWIFT, and the reference cannot be contained in
field 21, the code SEE72 may be used and the reference placed in field 72.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//'.

MT 422 - 3. Field 32a: Amount of Collection

Format
Option A 6!n3!a15d (Date)(Currency)(Amount)

Option B 3!a15d (Currency)(Amount)

Option K 1!a3!n2!a3!a15d (Day/Month)(Number of Days/Months)

(Code)(Currency)(Amount)

Presence
Optional (referenced in rules C1 and C3)
Definition
This field contains the maturity date as indicated in the collection instruction, followed by the currency
code and the amount of the particular collection to which the query or answer refers.

Codes
In option K, Day/Month must contain one of the following codes (Error code(s): T61):

D Days Period is expressed as a number of days.

M Months Period is expressed as a number of months.

19 July 2024 59
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 422 Advice of Fate and Request for Instructions
Message Reference Guide

Codes
In option K, Code must contain one of the following codes specifying additional information about the
maturity period (Error code(s): T20):

BE After the date of the bill of exchange.

CC After customs clearance of goods.

FD After goods pass food and drug administration.

FP First presentation.

GA After arrival of goods.

ID After invoice date.

ST After sight.

TD After date of transport documents.

XX See field 72 for specification.

Network Validated Rules

In option A, Date must be a valid date expressed in YYMMDD format (Error code(s): T50).
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).

Usage Rules
Option A must be used when the maturity is at a fixed date.
Option B must be used when the maturity date is not known.
Option K must be used when the maturity date is expressed as a period of time, with additional
information needed to calculate the maturity date.
Traditional collection terms, for example, primo, ultimo, etc., must be expressed in the ISO date format,
using option A.

Example
:32A:081216EUR100000,
(EUR100000, on 12 Dec 2008)
:32B:EUR100000,
(EUR 100000, no maturity date)
:32K:D060STEUR100000,
(EUR 100000, 60 days after sight)
:32K:D000STEUR100000,
(EUR 100000, at sight)
:32K:M001IDEUR100000,

19 July 2024 60
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 422 Advice of Fate and Request for Instructions
Message Reference Guide

(EUR 100000, 1 month after invoice date)

MT 422 - 4. Field 72: Sender to Receiver Information

Format
6*35x (Narrative)

In addition to narrative text, structured text with the following line formats may be used:

Line 1 /8c/[additional information] (Code)(Narrative)

Lines 2-6 [//continuation of additional (Narrative)

information] or
or (Code)(Narrative)
[/8c/[additional information]]

Presence
Conditional (see rule C2)

Definition
This field specifies additional information for the Receiver.

Usage Rules
The structured format may be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.

MT 422 - 5. Field 75: Queries

Format
6*35x (Narrative)

In addition to narrative text, the following line formats may be used:

Line 1 /2n/[supplement 1][supplement (Query Number)

2] (Narrative1)(Narrative2)

Lines 2-6 [//continuation of (Narrative)

supplementary information] or
or (Query Number)
[/2n/[supplement 1] (Narrative1)(Narrative2)
[supplement 2]]

Presence
Conditional (see rule C2)

Definition
This field specifies any queries related to the collection referred to in the message.

19 July 2024 61
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 422 Advice of Fate and Request for Instructions
Message Reference Guide

Codes
For frequently used query texts, the following predefined Query Numbers may be used:

1 We appear not to have been debited so far.

14 We cannot trace this transaction. Please send details.

15 May we release the documents to the drawee free of payment?

16 We have not received your confirmation to date.

Usage Rules
When a message contains more than one query, each query must appear on a separate line.
Queries must appear in ascending order.
When supplement 2 is used, that is, two different pieces of supplementary information are provided, it
must be preceded by a slash "/".
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.

MT 422 - 6. Field 76: Answers

Format
6*35x (Narrative)

In addition to narrative text, the following line formats may be used:

Line 1 /2n/[supplement 1][supplement (Answer Number)

2] (Narrative1)(Narrative2)

Lines 2-6 [//continuation of (Narrative)

supplementary information] or
or (Answer Number)
[/2n/[supplement 1] (Narrative1)(Narrative2)
[supplement 2]]

Or

Line 1 /8c/[additional information] (Code)(Narrative)

Lines 2-6 [//continuation of additional (Narrative)

information] or
or (Code)(Narrative)
[/8c/[additional information]]

Presence
Conditional (see rule C2)

Definition
This field specifies any answers related to the collection referred to in the message.

19 July 2024 62
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 422 Advice of Fate and Request for Instructions
Message Reference Guide

Codes
For frequently used answer texts, the following predefined Answer Numbers may be used:

1 We hereby confirm in response to Query 1 or 16

that we carried out
your instruction on
(1) ... (YYMMDD).

2 We hereby confirm in response to Query 16

that the transaction
has been effected
and advised on
(1) ... (YYMMDD).

10 We authorise you
to debit our
account.

Codes
The following codes are also defined for Code:

ARRIVCEP Arrival acceptance Acceptance promised upon arrival of goods.

ARRIVPAY Arrival pay Payment promised upon arrival of goods.

DIRECPAY Pay direct Drawee states payment has been effected direct to principal.
Please authorise us to release documents free of payment.

DRAWEE Drawee not known Insufficient information to identify/contact drawees. Please

give us further instructions.

EXCONPER Exchange control Please note that the payment has not been made as it
permission requires exchange control permission. We shall address this
matter as soon as possible.

INFNOCEP Informed non- Drawee states he has informed the drawer of the reason for
acceptance non-acceptance.

INFNOPAY Informed non- Drawee states he has informed the principal of the reason for
payment non-payment.

LOCAL Local currency Payment has been made in local currency pending release of
payment foreign exchange transfer authorisation.

NOANSWER No answer No response yet received from drawee.

PROMICEP Acceptance The acceptance is promised soon.

promised

PROMIPAY Payment promised The payment is promised soon.

Usage Rules
When a message contains more than one answer, each answer must appear on a separate line.
Answers must appear in ascending order.

19 July 2024 63
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 422 Advice of Fate and Request for Instructions
Message Reference Guide

Numbers in brackets, for example, (1), mean that supplementary information is required. This
supplementary information must be the first information following the code number.
When supplement 2 is used, that is, two different pieces of supplementary information are provided, it
must be preceded by a slash "/".
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.
When structured line format (2) is used, any code must be between slashes and must appear at the
beginning of a line.

MT 422 Examples
Narrative
In replying to an MT 420 Tracer sent by Banca Nazionale del Lavoro, Rome, Kredietbank, Brussels,
replies by an Advice of Fate, indicating that Mr. Lesis is disputing the terms of the collection.
(To review the MT 400, 410, 412, 420, and 430 messages related to this collection see the respective
Example sections.)

Information Flow

Sender Kredietbank
(Collecting Bank) Brussels

MT

Collection
MT 422

Receiver Banca Nazionale del Lavoro

(Remitting Bank) Rome
D0040010

SWIFT Message
Explanation Format

Sender KREDBEBB

Message Type 422

Receiver BNLIITRR

Message Text

Sending Bank's TRN :20:COL456

Related Reference :21:REM432

19 July 2024 64
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 422 Advice of Fate and Request for Instructions
Message Reference Guide

Explanation Format

Amount of Collection :32K:D000STEUR2300000,

Sender to Receiver Information :72:GOODS WAREHOUSED AND INSURED

Answers :76:DRAWEE DISAGREES WITH CONDITIONS

PLEASE VERIFY WITH DRAWER.

End of Message Text/Trailer

19 July 2024 65
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 430 Amendment of Instructions
Message Reference Guide

MT 430 Amendment of Instructions

MT 430 Scope
This message type is sent by the remitting bank to the collecting bank.
It may also be sent by a collecting bank to another collecting bank.
This message is used to amend instructions contained in the collection.

MT 430 Format Specifications

This format contains two sequences:
• Sequence A provides general information about the amended collection and describes amendment(s)
to the existing maturity date, currency code and amount made to the initial collection instruction.
• Sequence B describes the amendment(s) concerning the drawee and any other amendments of
instructions.
MT 430 Amendment of Instructions

Status Tag Field Name Content/Options No.

-----> Mandatory Repetitive Sequence A

M 20 Sending Bank's TRN 16x 1

M 21 Related Reference 16x 2

O 32a Existing Maturity Date, Currency Code, Amount A or K 3

O 33a Amended Maturity Date, Currency Code, Amount A or K 4

-----| End of Sequence A

Optional Sequence B

O 59 Drawee [/34x]<crlf>4*35x 5

O 72 Sender to Receiver Information 6*35x 6

O 74 Amendments 6*35x 7

End of Sequence B

M = Mandatory, O = Optional - Network Validated Rules may apply

MT 430 Network Validated Rules

C1 If field 33a is present in a sequence A, field 32a must be present in the same sequence (Error
code(s): C09).

19 July 2024 66
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 430 Amendment of Instructions
Message Reference Guide

C2 At least one optional field 32a in sequence A or field 74 in sequence B must be present (Error
code(s): C26).

MT 430 Usage Rules

• This is the only collection message type with which more than one currency can be accommodated in
defined amount fields. This will be the case when the amendment is a change to the currency code
quoted in previous collection messages.
• The MT 430 may be a single or a multiple message. When it is a multiple message, it must refer to
one collection (for at least one of the banks) or one collection message.
• When one of the banks views a collection with more than one item as more than one collection, fields
20 and 21 are to be used as follows:
The remitting bank sends what it considers to be two separate collections (references '1' and '2') to the
collecting bank.
The collecting bank, when sending an acknowledgement, considers this to be one item (reference 'A').
Fields 20 and 21, will appear as:

1st repetitive sequence: :20:A

:21:1

2nd repetitive sequence: :20:A

:21:2

The remitting bank sends what it considers to be one collection (reference '1') to the collecting bank.
The collecting bank, when sending an acknowledgement, considers this to be two items (reference 'A'
and 'B').
Fields 20 and 21 will appear as:

1st repetitive sequence: :20:A

:21:1

2nd repetitive sequence: :20:B

:21:1

• One MT 430 can be sent for several amounts of a collection to be amended.

MT 430 Field Specifications

MT 430 - 1. Field 20: Sending Bank's TRN

Format
16x

19 July 2024 67
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 430 Amendment of Instructions
Message Reference Guide

Presence
Mandatory (referenced in rule C1) in mandatory sequence A
Definition
This field contains the reference number of the collection, as shown on the collection instruction.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

MT 430 - 2. Field 21: Related Reference

Format
16x

Presence
Mandatory (referenced in rule C1) in mandatory sequence A
Definition
This field contains the collection number assigned by the Receiver of the message, as it appears in field
20 of the MT 410 Acknowledgement.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

Usage Rules
In cases where the initial message was not sent via SWIFT, and the reference cannot be contained in
field 21, the code SEE72 may be used and the reference placed in field 72.
If the reference of the collecting bank is not known, the code NONREF must appear in this field. When
this is the case, field 59 Drawee must be present.

MT 430 - 3. Field 32a: Existing Maturity Date, Currency Code, Amount

Format
Option A 6!n3!a15d (Date)(Currency)(Amount)

Option K 1!a3!n2!a3!a15d (Day/Month)(Number of Days/Months)

(Code)(Currency)(Amount)

Presence
Optional (referenced in rules C1 and C2) in mandatory sequence A

Definition
This field contains the existing maturity date, currency code and amount of the collection.

Codes
In option K, Day/Month must contain one of the following codes (Error code(s): T61):

19 July 2024 68
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 430 Amendment of Instructions
Message Reference Guide

D Days Maturity period is expressed as a number of days.

M Months Period is expressed as a number of months.

Codes
In option K, Code must contain one of the following codes specifying additional information about the
maturity period (Error code(s): T20):

BE After the date of the bill of exchange.

CC After customs clearance of goods.

FD After goods pass food and drug administration.

FP First presentation.

GA After arrival of goods.

ID After invoice date.

ST After sight.

TD After date of transport documents.

XX See field 72 for specification.

Network Validated Rules

In option A, Date must be a valid date expressed in YYMMDD format (Error code(s): T50).
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).

Usage Rules
Option A must be used when the maturity is at a fixed date.
Option K must be used when the maturity date is expressed as a period of time, with additional
information needed to calculate the maturity date.
Traditional collection terms, for example, primo, ultimo, etc., must be expressed in the ISO date format,
using option A.

Example
:32A:081216EUR100000,
(EUR100000, on 12 Dec 2008)
:32K:D060STEUR100000,
(EUR 100000, 60 days after sight)
:32K:D000STEUR100000,

19 July 2024 69
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 430 Amendment of Instructions
Message Reference Guide

(EUR 100000, at sight)

:32K:M001IDEUR100000,
(EUR 100000, 1 month after invoice date)

MT 430 - 4. Field 33a: Amended Maturity Date, Currency Code, Amount

Format
Option A 6!n3!a15d (Date)(Currency)(Amount)

Option K 1!a3!n2!a3!a15d (Day/Month)(Number of Days/Months)

(Code)(Currency)(Amount)

Presence
Conditional (see rule C1) in mandatory sequence A

Definition
This field contains the amended maturity date, currency code and amount of the collection.

Codes
In option K, Day/Month must contain one of the following codes (Error code(s): T61):

D Days Maturity period is expressed as a number of days.

M Months Period is expressed as a number of months.

Codes
In option K, Code must contain one of the following codes specifying additional information about the
maturity period (Error code(s): T20):

BE After the date of the bill of exchange.

CC After customs clearance of goods.

FD After goods pass food and drug administration.

FP First presentation.

GA After arrival of goods.

ID After invoice date.

ST After sight.

TD After date of transport documents.

XX See field 72 for specification.

Network Validated Rules

In option A, Date must be a valid date expressed in YYMMDD format (Error code(s): T50).

19 July 2024 70
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 430 Amendment of Instructions
Message Reference Guide

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).

Usage Rules
Option A must be used when the maturity is at a fixed date.
Option K must be used when the maturity date is expressed as a period of time, with additional
information needed to calculate the maturity date.

Example
:32A:081216EUR100000,
(EUR 100000, on 12 Dec 2008)
:32K:D060STEUR100000,
(EUR 100000, 60 days after sight)
:32K:D000STEUR100000,
(EUR 100000, at sight)
:32K:M001IDEUR100000,
(EUR 100000, 1 month after invoice date)

MT 430 - 5. Field 59: Drawee

Format
[/34x] (Account)
4*35x (Name and Address)

Presence
Optional in optional sequence B

Definition
This field identifies the drawee.

Usage Rules
Drawee must be present when:
• The reference of the collecting bank is not known, that is, NONREF in field 21, to enable the collecting
bank to identify the collection.
• There is a new drawee in field 74, to identify the initial drawee.
Account must not be used.

MT 430 - 6. Field 72: Sender to Receiver Information

Format
6*35x (Narrative)

19 July 2024 71
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 430 Amendment of Instructions
Message Reference Guide

In addition to narrative text, structured text with the following line formats may be used:

Line 1 /8c/[additional information] (Code)(Narrative)

Lines 2-6 [//continuation of additional (Narrative)

information] or
or (Code)(Narrative)
[/8c/[additional information]]

Presence
Optional in optional sequence B

Definition
This field specifies additional information for the Receiver.

Codes
The following code may be used in Code:

TSU Trade Services The code placed between slashes ('/') must be followed by the TSU
Utility Transaction transaction identifier, a slash ('/'), the invoice number, a slash ('/') and
the amount paid.

Usage Rules
The structured format may be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.

MT 430 - 7. Field 74: Amendments

Format
6*35x (Narrative)

In addition to narrative text, the following line formats may be used:

Line 1 /8a/[additional information] (Code)(Narrative)

Lines 2-6 [//continuation of additional (Narrative)

information] or
or (Code)(Narrative)
[/8a/[additional information]]

Presence
Conditional (see rule C2) in optional sequence B

Definition
This field specifies any amendments to instructions other than those specified in field 33a.

19 July 2024 72
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 430 Amendment of Instructions
Message Reference Guide

Codes
For frequently used amendments, one or more of the following codes may be used in Code:

CLOSE Close your file Return the documents to us and close your file.

FREE Free of payment Deliver documents free of payment to the drawee. When the
documents are to be delivered to a party other than the
drawee, the code FREE must be followed by that information.

HOLDCEP Hold after After acceptance, please retain the draft(s), and collect the
acceptance proceeds at maturity.

SENDCEP Send after After acceptance please airmail the draft(s) to us.
acceptance

Usage Rules
If there is a new drawee in this field, field 59 must be present.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.

MT 430 Examples
Narrative
Mr. Lesis, the drawee in collection number COL456 with Kredietbank, Brussels, refuses to pay Euro
2,300,000 at sight, claiming the conditions of the contract have not been met by Mr. Gagli of Banca
Nazionale del Lavoro. Mr. Lesis claimed to have agreed to pay Euro 1,000,000 on arrival of the goods
and to accept a 90 day draft for the remainder. He contacted Mr. Gagli directly in this matter.
(To review the MT 400, 410, 412, 420 and 422 messages related to this collection, see the respective
Example sections.)
Mr. Gagli agrees to these conditions and instructs Banca Nazionale del Lavoro to send an amendment of
instructions accordingly.

19 July 2024 73
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 430 Amendment of Instructions
Message Reference Guide

Information Flow

Sender Banca Nazionale del Lavoro

(Remitting Bank) Rome

MT

Collection
MT 430

Receiver Kredietbank
(Collecting Bank) Brussels

D0040011
SWIFT Message
Explanation Format

Sender BNLIITRR

Message Type 430

Receiver KREDBEBB

Message Text

Sending Bank's TRN :20:REM432

Related Reference :21:COL456

Existing Amount of Collection :32K:D000STEUR2300000,

New Amount :33K:D000STEUR1000000,

Sending Bank's TRN :20:REM432

Related Reference :21:COL456

Existing Amount of Collection :32K:D000STEUR2300000,

New Amount (1) :33K:D090STEUR1300000,

End of Message Text/Trailer

(1) The amended maturity date, currency code and amount of the collection as agreed between the drawer and the drawee. Because the
terms for settlement of the collection involve two different maturity dates/amounts, the terms for each are reported in the repetitive
sequence.

19 July 2024 74
Category 4 - Collections and Cash Letters
For Standards MT November 2024 Part 2 - Cash Letters
Message Reference Guide

Part 2 - Cash Letters

19 July 2024 75
Category 4 - Collections and Cash Letters
For Standards MT November 2024 Cash Letters Message Types
Message Reference Guide

Cash Letters Message Types

The following table lists all Cash Letter message types defined in Category 4.
For each message type, there is a short description, an indicator whether the message type requires
authentication (Y or N), the maximum message length on input (2,000 or 10,000 characters) and whether
the use of the message requires registration with Swift for use in a message user group (Y or N).

MT MT Name Purpose Signed(1) Max. MUG

Length

450 Cash Letter Credit Confirms that the face amount of Y 2,000 N
Advice cash letter(s) received has been
credited under usual reserve (subject
to final payment).

455 Cash Letter Credit Advises the account owner of Y 2,000 N

Adjustment Advice adjustments made to its account
(related to a previous credit for a
cash letter).

456 Advice of Dishonour Advises the account owner that Y 2,000 N

financial document(s) included in the
cash letter have been dishonoured
for reasons specified in the advice.

(1) Relationship Management Application (RMA) authorisation is required in order to sign a message.

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 MySwift > Order, change or
terminate products > Order Products and Services > Message User Group (MUG).
To withdraw from a MUG, use the Terminate your MUG subscription request. The form is
available through MySwift > Order, change or terminate products > Terminate and
deactivate > Message User Group (MUG).
To get the list of other members of a particular MUG, please contact Support.

19 July 2024 76
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 450 Cash Letter Credit Advice
Message Reference Guide

MT 450 Cash Letter Credit Advice

MT 450 Scope
This message type is sent by the account servicing institution to the account owner.
It is used to confirm that the face amount of cash letter(s) received has been credited under usual reserve
(subject to final payment).

MT 450 Format Specifications

MT 450 Cash Letter Credit Advice

Status Tag Field Name Content/Options No.

O 25 Account Identification 35x 1

O 72 Sender to Receiver Information 6*35x 2

----->

M 20 Transaction Reference Number 16x 3

M 21 Related Reference 16x 4

M 30 Date of Cash Letter 6!n 5

M 32A Value Date, Currency Code, Amount 6!n3!a15d 6

O 52a Sender of Cash Letter A, B, or D 7

-----|

M = Mandatory, O = Optional - Network Validated Rules may apply

MT 450 Network Validated Rules

C1 The repetitive sequence must not appear more than ten times (Error code(s): T10).

C2 The currency code in the amount field 32A must be the same for all occurrences of this field in the
message (Error code(s): C02).

MT 450 Usage Rules

The repetitive sequence may be repeated up to a maximum of 10 times. Each repetitive sequence must
pertain to a separate cash letter.

19 July 2024 77
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 450 Cash Letter Credit Advice
Message Reference Guide

MT 450 Guidelines
The cash letter can have been sent by the account owner or one of its branches or affiliates.

MT 450 Field Specifications

MT 450 - 1. Field 25: Account Identification

Format
35x

Presence
Optional

Definition
This field identifies the account which has been credited with the face amount of the cash letter(s).
Usage Rules
The absence of this field implies that the account that has been credited by the Sender (account servicing
institution) is the Receiver's (account owner's) general or only account with the Sender.

MT 450 - 2. Field 72: Sender to Receiver Information

Format
6*35x (Narrative)

In addition to narrative text, structured text with the following line formats may be used:

Line 1 /8c/[additional information] (Code)(Narrative)

Lines 2-6 [//continuation of additional (Narrative)

information] or
or (Code)(Narrative)
[/8c/[additional information]]

Presence
Optional

Definition
This field specifies additional information for the Receiver.

Usage Rules
The structured format may be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.

19 July 2024 78
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 450 Cash Letter Credit Advice
Message Reference Guide

This field may include ERI, as specified in the chapter entitled "Euro-Related Information (ERI)" in the
Standards MT General Information.

MT 450 - 3. Field 20: Transaction Reference Number

Format
16x

Presence
Mandatory

Definition
This field contains the reference assigned by the Sender to unambiguously identify the message.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

MT 450 - 4. Field 21: Related Reference

Format
16x

Presence
Mandatory

Definition
This field contains the exact reference of the original cash letter.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

MT 450 - 5. Field 30: Date of Cash Letter

Format
6!n (Date)

Presence
Mandatory

Definition
This field specifies the actual date on which the cash letter was prepared by the account owner (or its
branch or affiliate bank) and not the date it was sent (they may, however, be the same day). It is included
to facilitate recognition by the Receiver of the cash letter credit.

19 July 2024 79
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 450 Cash Letter Credit Advice
Message Reference Guide

Network Validated Rules

Date must be a valid date expressed in YYMMDD format (Error code(s): T50).

MT 450 - 6. Field 32A: Value Date, Currency Code, Amount

Format
Option A 6!n3!a15d (Date)(Currency)(Amount)

Presence
Mandatory (referenced in rule C2)

Definition
This field specifies the value date on which the account was credited, the currency code and amount
credited, that is, the face value of the cash letter.

Network Validated Rules

Date must be a valid date expressed in YYMMDD format (Error code(s): T50).
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 the specific currency (Error code(s): C03, T40, T43).

Usage Rules
Currency must be the currency of the account maintained by the Sender for the Receiver.

MT 450 - 7. Field 52a: Sender of Cash Letter

Format
Option A [/1!a][/34x] (Party Identifier)
4!a2!a2!c[3!c] (Identifier Code)

Option B [/1!a][/34x] (Party Identifier)

[35x] (Location)

Option D [/1!a][/34x] (Party Identifier)

4*35x (Name and Address)

Presence
Optional

Definition
This field is used to identify the branch or affiliate bank of the Receiver which sent the cash letter, if other
than the Receiver (account owner).

Network Validated Rules

Identifier Code must be a registered financial institution BIC (Error code(s): T27, T28, T29, T45).

19 July 2024 80
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 450 Cash Letter Credit Advice
Message Reference Guide

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).

MT 450 Examples
Narrative
On 9 September 2013, Banco de Madrid, Madrid, sends a cash letter to Banco de Portugal, Lisbon, under
its reference CL99364.
The cash letter was prepared on 8 September 2013 and covers 7 documents totalling Euro 1,263,015.
On 10 September 2013, Banco de Portugal sends an MT 450 Cash Letter Credit Advice (reference
973293), advising Banco de Madrid that its account, number 33-70247-1, has been credited for the total
amount of the cash letter.

Information Flow

Sender Banco de Portugal

Lisbon

MT

Cash Letter
MT 450

Receiver Banco de Madrid

Madrid
D0040012

SWIFT Message
Explanation Format

Sender BGALPTPL

Message Type 450

Receiver MADBESMM

Message Text

Account Identification :25:33-70247-1

Transaction Reference Number :20:973293

Related Reference :21:CL99364

Date of Cash Letter :30:130908

19 July 2024 81
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 450 Cash Letter Credit Advice
Message Reference Guide

Explanation Format

Value Date, Currency Code, Amount :32A:130910EUR1263015,

End of Message Text/Trailer

19 July 2024 82
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 455 Cash Letter Credit Adjustment Advice
Message Reference Guide

MT 455 Cash Letter Credit Adjustment Advice

MT 455 Scope
This message type is sent by an account servicing institution to the account owner.
It is used to advise the account owner of one or several adjustments that have been made to its account
that are related to a previous credit for a cash letter.

MT 455 Format Specifications

MT 455 Cash Letter Credit Adjustment Advice

Status Tag Field Name Content/Options No.

M 20 Transaction Reference Number 16x 1

M 21 Related Reference 16x 2

O 25 Account Identification 35x 3

M 30 Date of Cash Letter 6!n 4

M 32A Value Date and Original Amount 6!n3!a15d 5

M 33a Value Date and Adjustment Amount C or D 6

O 52a Sender of Cash Letter A, B, or D 7

M 77A Reason for Adjustment 20*35x 8

M = Mandatory, O = Optional - Network Validated Rules may apply

MT 455 Network Validated Rules

C1 The currency code in the amount fields 32A and 33a must be the same for all occurrences of these
fields in the message (Error code(s): C02).

MT 455 Usage Rules

The adjustment may be either a credit or a debit as specified by the letters C or D in the tag of field 33a.

MT 455 Guidelines
• The cash letter may have been sent by the account owner or one of its branches or affiliates.
• Adjustments may be caused by a miscalculation, missing item, etc., but not by a dishonoured item.

19 July 2024 83
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 455 Cash Letter Credit Adjustment Advice
Message Reference Guide

MT 455 Field Specifications

MT 455 - 1. Field 20: Transaction Reference Number

Format
16x

Presence
Mandatory

Definition
This field contains the reference assigned by the Sender to unambiguously identify the message.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

MT 455 - 2. Field 21: Related Reference

Format
16x

Presence
Mandatory

Definition
This field contains the exact reference of the original cash letter.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

MT 455 - 3. Field 25: Account Identification

Format
35x

Presence
Optional

Definition
This field identifies the account to which the adjustment has been debited or credited.

19 July 2024 84
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 455 Cash Letter Credit Adjustment Advice
Message Reference Guide

Usage Rules
The absence of this field implies that the account to which the adjustment was posted by the Sender
(account servicing institution) is the Receiver's (account owner's) general or only account with the Sender.

MT 455 - 4. Field 30: Date of Cash Letter

Format
6!n (Date)

Presence
Mandatory

Definition
This field specifies the actual date on which the cash letter was prepared by the account owner (or its
branch or affiliate bank) and not the date it was sent (they may, however, be the same day). It is included
to facilitate recognition of the cash letter to which the adjustment is related, by the Receiver of the
message.

Network Validated Rules

Date must be a valid date expressed in YYMMDD format (Error code(s): T50).

MT 455 - 5. Field 32A: Value Date and Original Amount

Format
Option A 6!n3!a15d (Date)(Currency)(Amount)

Presence
Mandatory (referenced in rule C1)

Definition
This field specifies the value date on which the account was originally credited, the currency code and
amount credited, that is, the face value of the cash letter.

Network Validated Rules

Date must be a valid date expressed in YYMMDD format (Error code(s): T50).
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 the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).

Usage Rules
Currency must be the currency of the account maintained by the Sender for the Receiver.

19 July 2024 85
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 455 Cash Letter Credit Adjustment Advice
Message Reference Guide

MT 455 - 6. Field 33a: Value Date and Adjustment Amount

Format
Option C 6!n3!a15d (Date)(Currency)(Amount)

Option D 6!n3!a15d (Date)(Currency)(Amount)

Presence
Mandatory (referenced in rule C1)

Definition
This field specifies the value date of the adjustment, the currency code and amount debited (option D) or
credited (option C).

Network Validated Rules

Date must be a valid date expressed in YYMMDD format (Error code(s): T50).
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 the specified currency (Error code(s): C03, T40, T43).

MT 455 - 7. Field 52a: Sender of Cash Letter

Format
Option A [/1!a][/34x] (Party Identifier)
4!a2!a2!c[3!c] (Identifier Code)

Option B [/1!a][/34x] (Party Identifier)

[35x] (Location)

Option D [/1!a][/34x] (Party Identifier)

4*35x (Name and Address)

Presence
Optional

Definition
This field is used to identify the branch or affiliate bank that sent the cash letter, if other than the Receiver
(account owner).

Network Validated Rules

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).

19 July 2024 86
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 455 Cash Letter Credit Adjustment Advice
Message Reference Guide

MT 455 - 8. Field 77A: Reason for Adjustment

Format
Option A 20*35x (Narrative)

In addition to narrative text. The following line formats may be used:

Line 1 /8a/[additional information] (Code)(Narrative)

Lines 2-20 [//continuation of additional (Narrative)

information] or
or (Code)(Narrative)
[/8a/[additional information]]

Presence
Mandatory

Definition
This field contains identification of each adjustment stating the amount of and reason for the adjustment.

Usage Rules
The structured format may be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.
This field may include ERI, as specified in the chapter entitled "Euro-Related Information (ERI)" in the
Standards MT General Information.

MT 455 Examples
Narrative
On 9 September 2013, Banco de Madrid, Madrid, sends a cash letter to Banco de Portugal, Lisbon, under
its reference CL99364.
(To review the MT 450 related to this transaction, see the Example section of the MT 450.)
On 11 September 2013, Banco de Portugal sends an MT 455 (reference 9AD31793), advising Banco de
Madrid that its account, number 33-70247-1, has been credited for an additional 20,000 Euro resulting
from an amount error on cheque number 376 dated 5 September 2013, issued by Jose Garcia.

19 July 2024 87
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 455 Cash Letter Credit Adjustment Advice
Message Reference Guide

Information Flow

Sender Banco de Portugal

Lisbon

MT

Cash Letter (MT 450)

MT 455

Receiver Banco de Madrid

Madrid

D0040013
SWIFT Message
Explanation Format

Sender BGALPTPL

Message Type 455

Receiver MADBESMM

Message Text

Transaction Reference Number :20:9AD31793

Related Reference :21:CL99364

Account Identification :25:33-70247-1

Date of Cash Letter :30:130908

Value Date and Original Amount :32A:130910EUR1263015,

Value Date and Adjustment Amount :33C:130910EUR20000,

Reason for Adjustment :77A:AMOUNT ERROR ON CHEQUE 376 130905

End of Message Text/Trailer

19 July 2024 88
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 456 Advice of Dishonour
Message Reference Guide

MT 456 Advice of Dishonour

MT 456 Scope
This message type is sent by the account servicing institution to the account owner.
It is used to advise the account owner that a financial document(s) included in the referenced cash letter
has/have been dishonoured for the reasons given. The account owner's account is debited accordingly.
The advice will specify whether the financial document(s) is/are being returned unpaid to the originator of
the cash letter or if it is/they are being re-presented to the drawee(s) for payment.

MT 456 Format Specifications

MT 456 Advice of Dishonour

Status Tag Field Name Content/Options No.

O 25 Account Identification 35x 1

O 52a Sender of Cash Letter A, B, or D 2

O 72 Sender to Receiver Information 6*35x 3

----->

M 20 Transaction Reference Number 16x 4

M 21 Related Reference 16x 5

M 32a Date and Face Amount of Financial Document A or B 6

M 33D Total Amount Debited 6!n3!a15d 7

O 71B Fee 6*35x 8

M 77A Reason for Dishonour 20*35x 9

M 77D Details of Dishonoured Item 6*35x 10

O 72 Sender to Receiver Information 6*35x 11

-----|

M = Mandatory, O = Optional - Network Validated Rules may apply

MT 456 Network Validated Rules

C1 The repetitive sequence must not appear more than ten times (Error code(s): T10).

C2 If field 71B is present, the amounts expressed in field 32a and 33D must be different (Error code(s):
C49).

19 July 2024 89
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 456 Advice of Dishonour
Message Reference Guide

C3 The currency code in the amount fields 32a and 33D must be the same for all occurrences of these
fields in the message (Error code(s): C02).

MT 456 Usage Rules

In order to expedite processing, this message must not contain more than ten pieces of advice, that is,
the repetitive sequence may not appear more than ten times.

MT 456 Guidelines
The cash letter can have been sent by the account owner or one of its branches or affiliates.

MT 456 Field Specifications

MT 456 - 1. Field 25: Account Identification

Format
35x

Presence
Optional

Definition
This field identifies the account to which the dishonoured item(s) has been debited.

Usage Rules
The absence of this field implies that the account to which the item was posted by the Sender (account
servicing institution) is the Receiver's (account owner's) general or only account with the Sender.

MT 456 - 2. Field 52a: Sender of Cash Letter

Format
Option A [/1!a][/34x] (Party Identifier)
4!a2!a2!c[3!c] (Identifier Code)

Option B [/1!a][/34x] (Party Identifier)

[35x] (Location)

Option D [/1!a][/34x] (Party Identifier)

4*35x (Name and Address)

Presence
Optional

19 July 2024 90
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 456 Advice of Dishonour
Message Reference Guide

Definition
This field is used to identify the branch or affiliate bank of the Receiver that sent the cash letter, if other
than the Receiver (account owner).
Network Validated Rules
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).

MT 456 - 3. Field 72: Sender to Receiver Information

Format
6*35x (Narrative)

In addition to narrative text, structured text with the following line formats may be used:

Line 1 /8c/[additional information] (Code)(Narrative)

Lines 2-6 [//continuation of additional (Narrative)

information] or
or (Code)(Narrative)
[/8c/[additional information]]

Presence
Optional

Definition
This field specifies additional information for the Receiver.

Codes
One of the following codes may be used in Code:

REPR Re-presented to The cheques are being re-presented to the drawee.

RETURN Return The cheques are being returned to you.

Usage Rules
The structured format may also be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.
This field may include ERI, as specified in the chapter entitled "Euro-Related Information (ERI)" in the
Standards MT General Information.

19 July 2024 91
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 456 Advice of Dishonour
Message Reference Guide

MT 456 - 4. Field 20: Transaction Reference Number

Format
16x

Presence
Mandatory
Definition
This field contains the reference assigned by the Sender to unambiguously identify the message.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

MT 456 - 5. Field 21: Related Reference

Format
16x

Presence
Mandatory

Definition
This field contains the reference assigned to the original cash letter or financial document by the
Receiver.

Codes
If the related reference is not known, the code NONREF must be used.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

MT 456 - 6. Field 32a: Date and Face Amount of Financial Document

Format
Option A 6!n3!a15d (Date)(Currency)(Amount)

Option B 3!a15d (Currency)(Amount)

Presence
Mandatory (referenced in rules C2 and C3)

Definition
This field specifies the currency code and amount of the item being dishonoured.

19 July 2024 92
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 456 Advice of Dishonour
Message Reference Guide

If the date of the financial document is known, it should be indicated in this field, using option A.

Network Validated Rules

In option A, Date must be a valid date expressed in YYMMDD format (Error code(s): T50).
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 the specified currency (Error code(s): C03, T40, T43).

MT 456 - 7. Field 33D: Total Amount Debited

Format
Option D 6!n3!a15d (Date)(Currency)(Amount)

Presence
Mandatory (referenced in rules C2 and C3)
Definition
This field specifies the value date, currency code and total amount debited. It is the sum of the contents of
field 32a and, if present, field 71B.

Network Validated Rules

Date must be a valid date expressed in YYMMDD format (Error code(s): T50).
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 the specified currency (Error code(s): C03, T40, T43).

MT 456 - 8. Field 71B: Fee

Format
Option B 6*35x (Narrative)

In addition to narrative text, the following line formats may be used:

Line 1 /8a/[3!a13d][additional (Code)(Currency)(Amount)

information] (Narrative)

Lines 2-6 [//continuation of additional (Narrative)

information] or
or (Code)(Currency)(Amount)
[/8a/[3!a13d][additional (Narrative)
information]]

Presence
Optional (referenced in rule C2)

19 July 2024 93
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 456 Advice of Dishonour
Message Reference Guide

Definition
This field contains an explanation of any fees which have been charged for the dishonoured item(s).
Codes
One or more of the following codes may be used in Code, followed by the currency code and amount:

AGENT Agent's Commission

COMM Our Commission

CORCOM Our Correspondent's Commission

DISC Commercial Discount

INSUR Insurance Premium

POST Our Postage

STAMP Stamp Duty

TELECHAR Teletransmission Charges

WAREHOUS Wharfing and Warehouse

Usage Rules
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.

MT 456 - 9. Field 77A: Reason for Dishonour

Format
Option A 20*35x (Narrative)

In addition to narrative text, the following line formats may be used:

Line 1 /8a/[additional information] (Code)(Narrative)

Lines 2-20 [//continuation of additional (Narrative)

information] or
or (Code)(Narrative)
[/8a/[additional information]]

Presence
Mandatory

Definition
This field contains identification of each item dishonoured, stating the amount and reason for dishonour.

19 July 2024 94
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 456 Advice of Dishonour
Message Reference Guide

Usage Rules
The structured format may be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.

MT 456 - 10. Field 77D: Details of Dishonoured Item

Format
Option D 6*35x (Narrative)

Presence
Mandatory

Definition
This field contains any additional information to assist the Receiver in identifying the financial document
being dishonoured. This includes the drawer, drawee, maker, payee, the financial document number, etc.

Usage Rules
Codes are not permitted in this field.

MT 456 - 11. Field 72: Sender to Receiver Information

Format
6*35x (Narrative)

In addition to narrative text, structured text with the following line formats may be used:

Line 1 /8c/[additional information] (Code)(Narrative)

Lines 2-6 [//continuation of additional (Narrative)

information] or
or (Code)(Narrative)
[/8c/[additional information]]

Presence
Optional

Definition
This field specifies additional information for the Receiver.

Codes
One of the following codes may be used in Code:

REPR Re-presented to The cheque is being re-presented to the drawee.

19 July 2024 95
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 456 Advice of Dishonour
Message Reference Guide

RETURN Return The cheque is being returned to you.

Usage Rules
The structured format may also be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last
information in the field.
This field may include ERI, as specified in the chapter entitled "Euro-Related Information (ERI)" in the
Standards MT General Information.

MT 456 Examples
Narrative
On 9 September 2013, Banco de Madrid, Madrid, sends a cash letter to Banco de Portugal, Lisbon, under
its reference CL99364.
(To review the MT 450 and MT 455 related to this transaction, see the respective Example sections.)
On 13 September 2013, Banco de Portugal sends an MT 456 Advice of Dishonour (reference
9CLD00793), advising Banco de Madrid that its account, number 33-70247-1, has been debited for
50,750 Euro (50,000 plus processing fee of 750) resulting from the return of cheque number 1303 dated 4
September 2013, issued by Juan Cortez, for insufficient funds.

Information Flow

Sender Banco de Portugal

Lisbon

MT

Cash Letter (MT 450)

MT 456

Receiver Banco de Madrid

Madrid
D0040014

SWIFT Message
Explanation Format

Sender BGALPTPL

Message Type 456

Receiver MADBESMM

19 July 2024 96
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 456 Advice of Dishonour
Message Reference Guide

Explanation Format

Message Text

Account Identification :25:33-70247-1

Transaction Reference Number :20:9CLD00793

Related Reference :21:CL99364

Date and Face Amount of Doc. :32A:030904EUR50000,

Total Amount Debited :33D:130913EUR50750,

Fee :71B:PROCESSING FEE EUR750,

Reason for Dishonour :77A:INSUFFICIENT FUNDS

Details of Item :77D:CHEQUE 1303 ISSUED BY JUAN

CORTEZ RETURNED

End of Message Text/Trailer

19 July 2024 97
Category 4 - Collections and Cash Letters
For Standards MT November 2024 Part 3 - Common Group
Message Reference Guide

Part 3 - Common Group

19 July 2024 98
Category 4 - Collections and Cash Letters
For Standards MT November 2024 Common Group Message Types
Message Reference Guide

Common Group Message Types

The following table lists all Common Group message types defined in Category 4.
For each message type, there is a short description, an indicator whether the message type requires
authentication (Y or N), the maximum message length on input (2,000 or 10,000 characters) and whether
the use of the message requires registration with Swift for use in a message user group (Y or N).

MT MT Name Purpose Signed(1 Max. MUG

) Length

490 Advice of Charges, Advises an account owner of Y 2,000 N

Interest and Other charges, interest, or other
Adjustments adjustments to its account.

491 Request for Payment Requests payment of charges, Y 2,000 N

of Charges, Interest interest, or other expenses.
and Other Expenses

492 Request for Requests the receiver to consider Y 2,000 N

Cancellation cancellation of the message
identified in the request.

495 Queries Requests information relating to a Y 2,000 N

previous message or amendment to
a previous message.

496 Answers Responds to an MT 495 Queries Y 2,000 N

message or MT 492 Request for
Cancellation or other messages
where no specific message type has
been provided for the response.

498 Proprietary Message Contains formats defined and agreed Y 10,000 N

to between users and for those
messages not yet live.

499 Free Format Message Contains information for which no Y 10,000 N

other message type has been
defined.

(1) A Relationship Management Application (RMA) authorisation is required in order to sign a message.

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 MySwift > Order, change or
terminate products > Order Products and Services > Message User Group (MUG).
To withdraw from a MUG, use the Terminate your MUG subscription request. The form is
available through MySwift > Order, change or terminate products > Terminate and
deactivate > Message User Group (MUG).
To get the list of other members of a particular MUG, please contact Support.

19 July 2024 99
Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 490 Advice of Charges, Interest and Other Adjustments
Message Reference Guide

MT 490 Advice of Charges, Interest and Other Adjustments

See Category n - Common Group Messages, Chapter n90 Advice of Charges, Interest and Other
Adjustments for details concerning this message type.

19 July 2024 100

Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 491 Request for Payment of Charges, Interest and Other Expenses
Message Reference Guide

MT 491 Request for Payment of Charges, Interest and

Other Expenses
See Category n - Common Group Messages, Chapter n91 Request for Payment of Charges, Interest and
Other Expenses for details concerning this message type.

19 July 2024 101

Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 492 Request for Cancellation
Message Reference Guide

MT 492 Request for Cancellation

See Category n - Common Group Messages, Chapter n92 Request for Cancellation for details
concerning this message type.

19 July 2024 102

Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 495 Queries
Message Reference Guide

MT 495 Queries
See Category n - Common Group Messages, Chapter n95 Queries for details concerning this message
type.

19 July 2024 103

Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 496 Answers
Message Reference Guide

MT 496 Answers
See Category n - Common Group Messages, Chapter n96 Answers for details concerning this message
type.

19 July 2024 104

Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 498 Proprietary Message
Message Reference Guide

MT 498 Proprietary Message

See Category n - Common Group Messages, Chapter n98 Proprietary Message for details concerning
this message type.

19 July 2024 105

Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 499 Free Format Message
Message Reference Guide

MT 499 Free Format Message

MT 499 Scope
This message type is used by financial institutions to send or receive information for which another
message type is not applicable.

MT 499 Format Specifications

MT 499 Free Format Message

Status Tag Field Name Content/Options No.

M 20 Transaction Reference Number 16x 1

O 21 Related Reference 16x 2

----->

M 79 Narrative 35*50x 3

-----|

M = Mandatory, O = Optional - Network Validated Rules may apply

MT 499 Network Validated Rules

There are no network validated rules for this message type.

MT 499 Field Specifications

MT 499 - 1. Field 20: Transaction Reference Number

Format
16x

Presence
Mandatory

Definition
This field specifies the reference assigned by the Sender to unambiguously identify the message.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

19 July 2024 106

Category 4 - Collections and Cash Letters
For Standards MT November 2024 MT 499 Free Format Message
Message Reference Guide

MT 499 - 2. Field 21: Related Reference

Format
16x

Presence
Optional
Definition
This field contains a reference to the related message.

Network Validated Rules

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).

MT 499 - 3. Field 79: Narrative

Format
35*50x (Narrative)

Presence
Mandatory

Definition
This field contains the free format message. This field may be repeated.

MT 499 Examples
As any free format information may be provided in this message type, no message examples will be
provided.

19 July 2024 107

Category 4 - Collections and Cash Letters
For Standards MT November 2024 Glossary of Terms
Message Reference Guide

Glossary of Terms
In addition to the definitions which appear in Standards General Information, Glossary of Terms, the
following terms apply to Category 4 message types.
For any additional definitions or details, see the Uniform Rules for Collections, International Chamber of
Commerce, Paris, France.

Cash Letter For the purpose of this category, any covering letter, however named or
described, whereby a bank (the Remitting Bank) requests credit for one or
more financial documents under usual reserve (subject to final payment).

Clean Payment A payment not accompanied by any documents.

Collection Instruction Instructions accompanying documents sent by a Remitting Bank to a

Collecting Bank.

Draft Terms The specification of the terms by which a collection instruction or draft will be
honoured.

Maturity Date and The maturity date of the collection and the amount paid by the Drawee.
Amount Collected

Protest The legal action taken in confirming the refusal of a party to accept its
obligation to a transaction or instruction.

Settlement Instructions The manner by which a financial transaction between two parties is to be
settled.

Value Date and The value date and amount remitted by the Sender to the Receiver for a
Proceeds Remitted collection or part thereof.

19 July 2024 108

Category 4 - Collections and Cash Letters
For Standards MT November 2024 Legal Notices
Message Reference Guide

Legal Notices
Copyright
Swift © 2024. All rights reserved.

Disclaimer
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,
Swift GPI with logo, the Swift GPI logo, and UETR. Other product, service, or company names in this
publication are trade names, trademarks, or registered trademarks of their respective owners.

19 July 2024 109