Travellers Cheques

Category 8 - Travellers Cheques
For Standards MT November 2024
Message Reference Guide
This reference guide contains the category 8 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/cat8

For Standards MT November 2024 Table of Contents
Table of Contents
Introduction..............................................................................................................................................4
Overview..................................................................................................................................................4
Changes.................................................................................................................................................. 4
Volume Formatting Explanation...............................................................................................................4
Category 8 Message Types.....................................................................................................................8
Euro - Impact on Category Message Standards.................................................................................10
T/C Purchase Agreement Guidelines...................................................................................................11

Guidelines.............................................................................................................................................. 11
Handling of the Purchase Agreement....................................................................................................12
MT 801 T/C Multiple Sales Advice........................................................................................................13

MT 801 Scope....................................................................................................................................... 13
MT 801 Format Specifications............................................................................................................... 13
MT 801 Network Validated Rules.......................................................................................................... 14
MT 801 Usage Rules.............................................................................................................................14
MT 801 Field Specifications...................................................................................................................14
MT 801 Examples..................................................................................................................................19
MT 802 T/C Settlement Advice............................................................................................................. 20

MT 802 Scope....................................................................................................................................... 20
MT 802 Format Specifications............................................................................................................... 20
MT 802 Network Validated Rules.......................................................................................................... 20
MT 802 Usage Rules.............................................................................................................................20
MT 802 Field Specifications...................................................................................................................21
MT 802 Examples..................................................................................................................................24
MT 890 Advice of Charges, Interest and Other Adjustments............................................................ 34
MT 891 Request for Payment of Charges, Interest and Other Expenses.........................................35
MT 892 Request for Cancellation......................................................................................................... 36
MT 895 Queries...................................................................................................................................... 37
MT 896 Answers.................................................................................................................................... 38
19 July 2024 2
For Standards MT November 2024 Table of Contents
MT 898 Proprietary Message................................................................................................................ 39
MT 899 Free Format Message.............................................................................................................. 40
Glossary of Terms................................................................................................................................. 41
Legal Notices......................................................................................................................................... 42
19 July 2024 3
For Standards MT November 2024 Introduction
Introduction
Overview
Category 8 supports messages which are exchanged between issuers and remitting agents, selling
agents, and refund agents in the handling of travellers cheques. Included in this category are messages
which relate to travellers cheques sales and settlement, refunds, and inventory administration.
Exchange of these messages is subject to bilateral agreements between issuers and their Swift member/
submember selling agents, remitting agents, and refund agents (that is, these messages may only be
sent and received after prior arrangements between an issuer and its member/submember agent(s)).
Changes
Category 8 - Travellers Cheques 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)
19 July 2024 4
M 25 Account Identification 35x 3
M 32a Value Date, Currency Code, Amount C or D 4
-----> 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.
19 July 2024 5
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.
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.
19 July 2024 6
• 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 7
For Standards MT November 2024 Category 8 Message Types
Category 8 Message Types

The following table lists all message types defined in category 8.
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
801 T/C Multiple Sales Provides the details (excluding the Y 2,000 N
Advice settlement details) of the sales of
travellers cheques in cases where
the data is lengthy or includes data
from several selling agents.
802 T/C Settlement Advice Provides the settlement details of Y 2,000 N

multiple sales of travellers cheques.
890 Advice of Charges, Advises an account owner of Y 2,000 N

Interest and Other charges, interest, or other
Adjustments adjustments to its account.
891 Request for Payment Requests payment of charges, Y 2,000 N

of Charges, Interest interest, or other expenses.
and Other Expenses
892 Request for Requests the receiver to consider Y 2,000 N

Cancellation cancellation of the message
identified in the request.
895 Queries Requests information relating to a Y 2,000 N

previous message or amendment to
a previous message.
896 Answers Responds to an MT 895 Queries Y 2,000 N

message or MT 892 Request for
Cancellation or other messages
where no specific message type has
been provided for the response.
898 Proprietary Message Contains formats defined and agreed Y 10,000 N

to between users and for those
messages not yet live.
899 Free Format Message Contains information for which no Y 2,000 N

other message type has been
defined.
(1) A Relationship Management Application (RMA) authorisation is required in order to sign a message.
19 July 2024 8
For Standards MT November 2024 Category 8 Message Types
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 9
For Standards MT November 2024 Euro - Impact on Category Message Standards
Euro - Impact on Category Message Standards

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 10
For Standards MT November 2024 T/C Purchase Agreement Guidelines
T/C Purchase Agreement Guidelines

Travellers cheque issuers which are participants in and, therefore, users of Swift have agreed, subject to
bilateral agreement, that they will accept, from selling agents, T/C Purchase Agreements conforming to
this guideline.
This guideline sets forth the standard English text and data content to be used in the purchase
agreement, but it does not standardise the format nor size of the document. The standard text must
appear in English and may also appear in other languages.
This guideline also mandates minimum rules regarding the handling of purchase agreements.
Guidelines
English Text Field Content/Notes
Purchase agreement This must appear as the title of the document.
Issuer The name of the T/C issuer, as agreed between the issuer and the
selling agent, must be included.
Selling agent The name and location of the selling agent, in sufficient detail to
provide identification of the inventory holder. In addition, the selling
agent code, as assigned by the issuer, must be included.
Purchaser The full name of the purchaser and either his address or sufficient
identification to establish his address.
Currency The ISO (alpha) currency code of the T/Cs.
Serial numbers: For each serial identification range, the following items must be
provided:
From Entire first cheque serial identification in the range.
To At least the final four digits of the last cheque in the range.
Quantity The number of cheques in the range.
Denomination The face value of one cheque in the range.
Amount The total face value of the cheques in the range.
Total sale amount The total amount of the sale.
Sale date The date when the purchase occurred.
PA Identification The selling agent's identification of the purchase agreement.
Signature The purchaser's signature.
Text The following text must also appear:

'The purchaser (or his agent) confirms receipt of, and agrees to, the
terms and conditions of the above mentioned issuer and confirms
receipt of these travellers cheques.'
19 July 2024 11
For Standards MT November 2024 T/C Purchase Agreement Guidelines
Other information, such as commission details, may be included by the selling agent.
Handling of the Purchase Agreement

The selling agent must provide to the purchaser:
• cheque signature instructions
• the issuer's terms and conditions, including refund instructions
At least two copies of the purchase agreement must be available, as described below:
• the original, with the purchaser's signature, is to be held by the selling agent at the disposal of the
Issuer, for a retention period specified by a bilateral agreement
• a copy, which is to be given to the purchaser
19 July 2024 12
For Standards MT November 2024 MT 801 T/C Multiple Sales Advice
MT 801 T/C Multiple Sales Advice
MT 801 Scope
This message type is sent by, or on behalf of, a single remitting agent to the issuer of travellers cheques.
It is used to provide the sale details of a multiple sale of travellers cheques by either:
• a single selling agent (where the details would exceed the maximum input message length of an MT
800 T/C Sales and Settlement Advice [Single]), or
• several selling agents
This message will be followed by an MT 802 T/C Settlement Advice.
MT 801 Format Specifications

MT 801 T/C Multiple Sales Advice
M 28 Settlement No./Page No. 5n[/2n] 2
----->
M 51a Selling Agent A or C 3
----->
M 23 Purchase Agreement ID 16x 4
O 30 Sales Date 6!n 5
----->
M 26A Serial Numbers 16x[/4!x] 6
-----|
M 33B Face Amount 3!a15d 7
O 73 Additional Amounts 6*35x 8
-----|
M 34B Selling Agent Amount 3!a15d 9
M 16A Selling Agent's No. of PAs 5n 10
-----|
M = Mandatory, O = Optional - Network Validated Rules may apply
19 July 2024 13
MT 801 Network Validated Rules

C1 The currency code in all occurrences of fields 33B and 34B must be the same (Error code(s): C02).
MT 801 Usage Rules

• This message may only be sent and received after prior arrangements between an issuer and its
member/submember Agent(s).
• When an MT 801 is being used, it may not be possible to fit all the sales advice information for a
particular selling agent into one MT 801. When this is the case, the information must be divided so that
each message contains a series of complete purchase agreements for that selling agent, as well as a
selling agent amount, which shall be the total for the selling agent in that message.
• A series of one or more MTs 801 must be followed by a single MT 802.
MT 801 Field Specifications
MT 801 - 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).
MT 801 - 2. Field 28: Settlement No./Page No.

Format
5n[/2n] (Settlement Number)(Page Number)
Presence
Mandatory
Definition
This field specifies the number of the sales advice and, optionally, the page number within a series of
messages sent.
19 July 2024 14
Usage Rules
In a sequence of MT 801s which are followed by an MT 802, the Settlement Number must always be the
same.
It is strongly recommended that Settlement Number be unique per day and per currency, and/or subject
to prior arrangement, to allow the Receiver to match up the related MT 801(s) with the appropriate MT
802.
Page Number must start at 1 in the first message, and be incremented by 1 for each succeeding
message in the sequence, thus enabling the sequence of messages to be determined. The final message
(page) must always be an MT 802.
MT 801 - 3. Field 51a: Selling Agent

Format
Option A [/1!a][/34x] (Party Identifier)
4!a2!a2!c[3!c] (Identifier Code)
Option C /34x (Account)
Presence
Mandatory
Definition
This field identifies the selling agent to which the sales details in this sequence apply.

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 selling agent, which may also be the remitting agent and Sender, will be identified in this field by a
code that is intelligible to the issuer and uniquely identifies the selling agent (that is, the ISO Business
Identifier Code [option A] or selling agent code as assigned by the issuer [option C]).
Whenever possible, all sales advice relating to a particular selling agent must be contained in the same
message. When there is too much data, that is, the information would exceed the maximum input
message length, a sequence of MT 801s must be sent. In a message which continues the sales
information for a particular selling agent, the first field 51a must be the same as the last field 51a in the
previous message.
MT 801 - 4. Field 23: Purchase Agreement ID

Format
16x
19 July 2024 15
Presence
Mandatory
Definition
This field contains the selling agent's identification of the purchase agreement to which the message is
related.
Usage Rules
The information in this field will be used by the issuer when contacting the selling agent with a query
about the referenced purchase agreement.
The detailed form and content of the purchase agreement ID are at the discretion of the selling agent.
Inclusion of identification numbers in this field enables the possibility for agreement between selling
agents and issuers not to send purchase agreement forms in paper to the issuers. However, as long as
no such agreement exists, the paper forms will be sent to the issuer in addition to the SWIFT messages.
MT 801 - 5. Field 30: Sales Date

Format
6!n (Date)
Presence
Optional
Definition
This field specifies the date, when available, on which the travellers cheques were delivered to the
purchaser.

Date must be a valid date expressed as YYMMDD (Error code(s): T50).
MT 801 - 6. Field 26A: Serial Numbers

Format
Option A 16x[/4!x] (Number 1)(Number 2)
Presence
Mandatory
Definition
This field specifies the serial number sequences of the T/Cs sold relative to the referenced purchase
agreement (field 23).
Usage Rules
If only Number 1 is present, it refers to either a single cheque or, after agreement between the parties, it
may specify the first number in a pack of cheques or the pre-assigned identification number of the pack.
19 July 2024 16
If Number 2 is present, the Sender has specified a range of serial numbers. In this case, Number 1 is the
first serial number in the range and Number 2 consists of the last four characters of the serial number of
the last cheque in the consecutive sequence.
Where a range of serial numbers is provided and the last number differs from the first in more than the
last four positions, this field should be repeated to give ranges in each of which only the last four positions
change.
MT 801 - 7. Field 33B: Face Amount

Format
Option B 3!a15d (Currency)(Amount)
Presence
Mandatory
Definition
This field specifies the currency code and total face value of all the T/Cs identified in the referenced
purchase agreement.

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 801 - 8. Field 73: Additional Amounts

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 any amounts which have been added to or deducted from the face value of the
purchase agreement.
19 July 2024 17
Codes
One or more of the following codes may be used in Code:
DISC Selling agent's discount deducted from the face value of the sale
TCOMM Commission due to the issuer
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 801 - 9. Field 34B: Selling Agent Amount

Format
Option B 3!a15d (Currency)(Amount)
Presence
Mandatory
Definition
This field specifies the currency code and amount being remitted in this message on behalf of the selling
agent in this selling agent sequence.

Currency must be a valid ISO 4217 currency code (Error code(s): T52).
Usage Rules
Normally, this field is the total of all face amounts (field 33B) plus any commission and/or minus any
discounts (field 73).
MT 801 - 10. Field 16A: Selling Agent's No. of PAs

Format
Option A 5n (Number)
Presence
Mandatory
Definition
This field specifies the total number of purchase agreements included in this selling agent sequence (that
is, the total number of times the purchase agreement sequence is repeated for this selling agent).
19 July 2024 18
MT 801 Examples
Examples of this message type may be found in the Examples section of the MT 802 T/C Settlement
Advice.
19 July 2024 19
For Standards MT November 2024 MT 802 T/C Settlement Advice
MT 802 T/C Settlement Advice
MT 802 Scope
This message type is sent by, or on behalf of, a single remitting agent to the issuer of travellers cheques.
The T/C Settlement Advice is used to provide the settlement details of the total sales amount included in
one or several MT 801 T/C Multiple Sales Advice.
A single MT 802 must always be preceded by one or several MTs 801.
MT 802 Format Specifications

MT 802 T/C Settlement Advice
M 28 Settlement No./Page No. 5n[/2n] 2
M 32A Settlement Amount 6!n3!a15d 3
O 52a Remitting Agent A or D 4
O 53a Sender's Correspondent A, B, or D 5
O 54a Receiver's Correspondent A, B, or D 6
O 72 Sender to Receiver Information 6*35x 7
M = Mandatory, O = Optional - Network Validated Rules may apply
MT 802 Network Validated Rules

There are no network validated rules for this message type.
MT 802 Usage Rules

• This message may only be sent and received after prior arrangements between an issuer and its
member/submember Agent(s).
• An MT 802 must be preceded by a sequence of one or more MTs 801.
19 July 2024 20
MT 802 Field Specifications
MT 802 - 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.

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error
code(s): T26).
MT 802 - 2. Field 28: Settlement No./Page No.

Format
5n[/2n] (Settlement Number)(Page Number)
Presence
Mandatory
Definition
This field specifies the number of the sales advice to which this settlement advice applies and, optionally,
the page number within the series of messages sent.
Usage Rules
In a sequence of MTs 801 which are followed by an MT 802, Settlement Number, must always be the
same.
It is strongly recommended that Settlement Number be unique per day and per currency, and/or subject
to prior arrangement, to allow the Receiver to match up the related MT(s) 801 with the appropriate MT
802.
Page Number must start at 1 in the first message, and be incremented by 1 for each succeeding
message in the sequence, thus enabling the sequence of messages to be determined. The MT 802 must
always be the final message (page) in the series.
MT 802 - 3. Field 32A: Settlement Amount

Format
Option A 6!n3!a15d (Date)(Currency)(Amount)
19 July 2024 21
Presence
Mandatory
Definition
This field specifies the value date, currency code and total settlement amount to be remitted by the
Sender to the Receiver (issuer).

Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Currency must be a valid ISO currency code (Error code(s): T52).
Usage Rules
Amount must be the total of all fields 34B in the preceding MT 801 message(s) which have been sent in
conjunction with the MT 802.
Currency in field 32A must be the same as the currency in field 34B in the preceding MT 801 message(s)
which have been sent in conjunction with the MT 802.
MT 802 - 4. Field 52a: Remitting Agent

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

4*35x (Name and Address)
Presence
Optional
Definition
This field specifies the remitting agent.

Usage Rules
This field is used when the remitting agent is other than the Sender (for example, the remitting agent is
not connected to SWIFT).
19 July 2024 22
MT 802 - 5. Field 53a: Sender's Correspondent

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

[35x] (Location)

Presence
Optional
Definition
This field identifies the financial institution, branch or account, when different from the Sender, through
which reimbursement of the settlement amount will take place.

Usage Rules
If the Sender and Receiver (issuer) have a single direct account relationship, in the currency of the T/Cs,
and this account is to be used in reimbursement, fields 53a and/or 54a must not appear in the message.
In all other cases, the relevant reimbursement details must be specified in fields 53a and/or 54a. Normally
the Sender undertakes responsibility for crediting the Receiver via the specified parties, unless alternative
arrangements have been established with the issuer. For further details concerning the use of this field,
see the Standards MT General Information.
MT 802 - 6. Field 54a: Receiver's Correspondent

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

[35x] (Location)

Presence
Optional
19 July 2024 23
Definition
This field specifies the financial institution, or branch, when different from the Receiver, servicing the
account at which the settlement amount will be made available to the Receiver.
Usage Rules
If the Sender and Receiver (issuer) have a single direct account relationship, in the currency of the T/Cs,
and this account is to be used in reimbursement, fields 53a and/or 54a must not appear in the message.
In all other cases, the relevant reimbursement details must be specified in fields 53a and/or 54a. Normally
the Sender undertakes responsibility for crediting the Receiver via the specified parties, unless alternative
arrangements have been established with the issuer. For further details concerning the use of this field,
see the Standards MT General Information.
MT 802 - 7. 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 with 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 802 Examples
Examples of the MT 801 T/C Multiple Sales Advice are included in this Examples section.
19 July 2024 24
Message A T/C Multiple Sales Advice

On 17 August 2002, Christiania Bank og Kreditkasse, Oslo, notifies Citicorp Travellers Cheques about the
following purchases of travellers cheques:
Selling Agent: Christiania Bank og Kreditkasse, Oslo
1. Purchase Agreement Number 31146853611; Date: 12 August 2002
68364118512/8516 5 * 10.00 USD 50.00
68364119321/9330 10 * 10.00 100.00
68489165771/5775 5 * 20.00 100.00
68489166203/6212 10 * 20.00 200.00
68371148100/8104 5 * 100.00 500.00
TOTAL TRAVELLERS CHEQUES 950.00
+ 1.5% Commission 14.25
TOTAL USD 964.25
68911348300 1 * 500.00 USD 500.00
68208743201/3205 5 * 100.00 500.00
68894113746/3755 10 * 50.00 500.00
68721234990/4994 5 * 20.00 100.00
TOTAL TRAVELLERS CHEQUES 1,600.00
TOTAL USD 1,624.00
TOTAL SETTLEMENT FOR OSLO USD 2,550.00
(less 1.5% commission retained by Selling Agent)
Selling Agent: Christiania Bank og Kreditkasse, Bergen (XIANNOBB)

68568558789/8798 10 * 10.00 USD 100.00
68398458213/8217 5 * 20.00 100.00
68589554123/4132 10 * 50.00 500.00
19 July 2024 25
68774623485/3487 3 * 100.00 300.00
68115589478 1 * 500.00 500.00
TOTAL USD 1,522.50
68258987684/7693 10 * 20.00 USD 200.00
68586974321/4330 10 * 50.00 500.00
68258674333/4337 5 * 100.00 500.00
68885774123/4127 5 * 500.00 2,500.00
TOTAL USD 3,755.50
TOTAL SETTLEMENT FOR BERGEN USD 5,200.00
Selling Agent: Christiania Bank og Kreditkasse, Lillestroem (XIANNOKKLTM)

68125885456/5460 5 * 50.00 USD 250.00
68699558781/8785 5 * 100.00 500.00
68586669211/9213 3 * 500.00 1,500.00
TOTAL USD 2,283.75
TOTAL SETTLEMENT FOR LILLESTROEM USD 2,250.00
Selling Agent: Christiania Bank og Kreditkasse, Aalesund (XIANNO24)
19 July 2024 26
68225558123/8152 30 * 20.00 USD 600.00
68558447259/7283 25 * 50.00 1,250.00
68226998796/8800 5 * 100.00 500.00
68587469135/9138 4 * 500.00 2,000.00
TOTAL USD 4,415.25
TOTAL SETTLEMENT FOR AALESUND USD 4,350.00
Selling Agent: Christiania Bank og Kreditkasse, Trondheim (XIANNOKKTRD)

68258698457/8474 18 * 10.00 USD 180.00
68589669132/9141 10 * 20.00 200.00
68889669546/9548 3 * 100.00 300.00
TOTAL USD 690.20
68558669325/9329 5 * 20.00 USD 100.00
68889669756/9760 5 * 50.00 250.00
TOTAL USD 355.35
68225669585/9604 20 * 10.00 USD 200.00
68896667454/7478 25 * 20.00 500.00
19 July 2024 27
68897362111/2120 10 * 50.00 500.00
6889314755/4757 3 * 500.00 1,500.00
TOTAL USD 2,740.50
TOTAL SETTLEMENT FOR TRONDHEIM USD 3,730.00
TOTAL SETTLEMENT AMOUNT USD 18,080.00
Christiania Bank og Kreditkasse informs Citicorp Travellers Cheques (reference T9208173611/3619) that
reimbursement will be through Citibank, New York.
Information Flow
Selling Agent Christiana Bank og Kreditkasse
Oslo Bergen Lillestrœm Aalesund Trondheim
51a 51a 51a 51a 51a
Sender Christiana Bank og Kreditkasse

(Remitting Agent) Oslo
(MT 202)
MT
Sender's Citibank
Correspondent 53a MT 801/802 New York
(MT 910/950)
Receiver Citicorp Travellers Cheques

(Issuer) New York
D0080005
Explanation Format
Sender XIANNOKK
19 July 2024 28
Explanation Format
Message Type 801
Receiver CITIUS33
Message Text
Transaction Reference Number :20:T0208173611/3619
Settlement Number/Page Number (1) :28:181/1
Selling Agent (2) :51A:XIANNOKK
Purchase Agreement ID (3) :23:31146853611
Sales Date :30:020812
Serial Numbers :26A:68364118512/8516

:26A:68364119321/9330
:26A:68489165771/5775
:26A:68489166203/6212
:26A:68371148100/8104
Face Amount :33B:USD950,
Serial Numbers :26A:68911348300

:26A:68208743201/3205
:26A:68894113746/3755
:26A:68721234990/4994
Selling Agent Amount :34B:USD2550,
Selling Agent's Number of PAs :16A:2
Selling Agent (5) :51A:XIANNOBB
Serial Numbers :26A:68568558789/8798

:26A:68398458213/8217
:26A:68589554123/4132
:26A:68774623485/3487
:26A:68115589478
19 July 2024 29
Explanation Format
Serial Numbers :26A:68258987684/7693

:26A:68586974321/4330
:26A:68258674333/4337
:26A:68885774123/4127
Selling Agent Number of PAs :16A:2
Selling Agent (8) :51A:XIANNOKKLTM
Purchase Agreement ID :23:31146852215
Serial Numbers :26A:68125885456/5460

:26A:68699558781/8785
:26A:68586669211/9213
Selling Agent (9) :51A:XIANNO24
Purchase Agreement ID :23:31146852216
Serial Numbers :26A:68225558123/8152

:26A:68558447259/7283
:26A:68226998796/8800
:26A:68587469135/9138
End of Message Text/Trailer
(1) This is the first message of settlement number 181.

(2) Total sales information for Oslo (51A), with 2 purchase agreements (16A), totalling USD 2,550 (34B).
(3) First purchase agreement for Oslo.
(4) Second purchase agreement for Oslo.
(5) Total sales information for Bergen (51A), with 2 purchase agreements (16A), totalling USD 5,200 (34B).
(6) First purchase agreement for Bergen.
(7) Second purchase agreement for Bergen.
(8) Total sales information for Lillestroem (51A, with 1 purchase agreement (16A), totalling USD 2,250 (34B).
(9) Total sales information for Aalesund (51A), with 1 purchase agreement (16A), totalling USD 4,350 (34B).
19 July 2024 30
Explanation Format
Sender XIANNOKK
Message Type 801
Receiver CITIUS33
Message Text
Selling Agent (2) :51A:XIANNOKKTRD
Serial Numbers :26A:68258698457/8574

:26A:68589669132/9141
:26A:68889669546/9548
Serial Numbers :26A:68558669325/9329

:26A:68889669756/9760
Serial Numbers :26A:68225669585/9604

:26A:68896667454/7478
:26A:68897362111/2120
:26A:68869314755/4757
(1) This is the second message of settlement number 181.

(2) Total sales information for Trondheim (51A), with 3 purchase agreements (16A), totalling USD 3,730 (34B).
(3) First purchase agreement for Trondheim.
(4) Second purchase agreement for Trondheim.
(5) Third purchase agreement for Trondheim.
19 July 2024 31
Explanation Format
Sender XIANNOKK
Message Type 802
Receiver CITIUS33
Message Text
Settlement Amount (2) :32A:020817USD18080,
Sender's Correspondent (3) :53A:CITIUS33
(1) This is the third (and last) page of settlement number 181.
(2) The total amount of sales in the preceding MT 801s is USD 18,080. This is the amount to be settled with the issuer.
(3) Reimbursement of the settlement amount will be through Citibank, New York, in favour of Citicorp Travellers Cheques.
Message B General Financial Institution Transfer

On 17 August 1992, Christiania Bank og Kreditkasse (remitting agent), sends a payment order to
Citibank, New York, for payment of the settlement amount of USD 18,080 to Citicorp Travellers Cheques,
New York.
Information Flow
Sender Christiana Bank og Kreditkasse

(Remitting Agent) Oslo
MT
MT 202
Receiver Citibank
New York
Beneficiary Institution Citicorp Travellers Cheques

58a New York
D0080006
19 July 2024 32
Explanation Format
Sender XIANNOKK
Message Type 202
Receiver CITIUS33
Message Text
Transaction Reference Number :20:86356873097
Related Reference :21:T0208173611/3619
Value Date/Currency/Amount :32A:020817USD18080,
Beneficiary Institution :58A:CITIUS33TCH
Message C Statement Message

Citibank, New York, credits Citicorp Travellers Cheques.
The transaction will appear as follows on the statement of account (MT 950):
:61:020817C18080,S950T0208173611/3619//468276202
19 July 2024 33
For Standards MT November 2024 MT 890 Advice of Charges, Interest and Other Adjustments
MT 890 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 34
For Standards MT November 2024 MT 891 Request for Payment of Charges, Interest and Other Expenses
MT 891 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 35
For Standards MT November 2024 MT 892 Request for Cancellation
MT 892 Request for Cancellation

See Category n - Common Group Messages, Chapter n92 Request for Cancellation for details
concerning this message type.
19 July 2024 36
For Standards MT November 2024 MT 895 Queries
MT 895 Queries
See Category n - Common Group Messages, Chapter n95 Queries for details concerning this message
type.
19 July 2024 37
For Standards MT November 2024 MT 896 Answers
MT 896 Answers
See Category n - Common Group Messages, Chapter n96 Answers for details concerning this message
type.
19 July 2024 38
For Standards MT November 2024 MT 898 Proprietary Message
MT 898 Proprietary Message

See Category n - Common Group Messages, Chapter n98 Proprietary Message for details concerning
this message type.
19 July 2024 39
For Standards MT November 2024 MT 899 Free Format Message
MT 899 Free Format Message

See Category n - Common Group Messages, Chapter n99 Free Format Message for details concerning
this message type.
19 July 2024 40
For Standards MT November 2024 Glossary of Terms
Glossary of Terms
In addition to the definitions which appear in the Standards MT General Information, Glossary of Terms,
the following terms apply to Category 8 message types:
Acceptor A bank, other institution, merchant or individual giving value to a Purchaser, in

exchange for travellers cheques being countersigned in the Acceptor's presence.
Claimant A purchaser requesting a refund from an Issuer for lost or stolen travellers
cheques.
Issuer An organisation, or the agent for an organisation, which issues travellers cheques
and is an obliger with ultimate responsibility to give value for the checks which it
issues, irrespective of wherever they may be payable.
Purchaser An individual buying travellers cheques from a Selling Agent. The purchaser signs
and countersigns the travellers cheque.
Refund Agent An institution acting on behalf of an Issuer to refund travellers cheques and/or cash
to the Claimant.
Remitting Agent An institution responsible for ordering the transfer of funds to an Issuer for the sale
of travellers cheques. A Remitting Agent may be a selling agent and/or a
concentrating point for several Selling Agents.
Selling Agent An institution under agreement with an Issuer to stock and sell the Issuer's
travellers cheques.
T/C Purchase An agreement between a selling agent and purchaser of Travellers Cheques for
Agreement the sale and purchase of those cheques.
19 July 2024 41
For Standards MT November 2024 Legal Notices
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 42

Travellers Cheques

Uploaded by

Copyright:

Available Formats

Travellers Cheques

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Travellers Cheques

Uploaded by

Copyright:

Available Formats

Category 8 - Travellers Cheques

For Standards MT November 2024

Message Reference Guide

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

Category 8 Message Types.....................................................................................................................8

Euro - Impact on Category Message Standards.................................................................................10

T/C Purchase Agreement Guidelines...................................................................................................11

MT 801 T/C Multiple Sales Advice........................................................................................................13

MT 802 T/C Settlement Advice............................................................................................................. 20

MT 890 Advice of Charges, Interest and Other Adjustments............................................................ 34

MT 891 Request for Payment of Charges, Interest and Other Expenses.........................................35

MT 892 Request for Cancellation......................................................................................................... 36

MT 898 Proprietary Message................................................................................................................ 39

MT 899 Free Format Message.............................................................................................................. 40

Volume Formatting Explanation

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)

Status Tag Field Name Content/Options No.

M 25 Account Identification 35x 3

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

-----> 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 Network Validated Rules

Category 8 Message Types

MT MT Name Purpose Signed(1 Max. MUG

802 T/C Settlement Advice Provides the settlement details of Y 2,000 N

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

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

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

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

896 Answers Responds to an MT 895 Queries Y 2,000 N

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

899 Free Format Message Contains information for which no Y 2,000 N

Euro - Impact on Category Message Standards

T/C Purchase Agreement Guidelines

Purchase agreement This must appear as the title of the document.

Currency The ISO (alpha) currency code of the T/Cs.

From Entire first cheque serial identification in the range.

Quantity The number of cheques in the range.

Denomination The face value of one cheque in the range.

Amount The total face value of the cheques in the range.

Total sale amount The total amount of the sale.

Sale date The date when the purchase occurred.

PA Identification The selling agent's identification of the purchase agreement.

Signature The purchaser's signature.

Text The following text must also appear:

Handling of the Purchase Agreement

MT 801 T/C Multiple Sales Advice

MT 801 Format Specifications

Status Tag Field Name Content/Options No.

M 20 Transaction Reference Number 16x 1

M 28 Settlement No./Page No. 5n[/2n] 2

M 51a Selling Agent A or C 3

M 23 Purchase Agreement ID 16x 4

O 30 Sales Date 6!n 5