Standard Document Template - Portrait

TEMENOS
Changes for SWIFT 2019 MT Standards Release
Version 1.0
Information in this document is subject to change without notice.
No part of this document may be reproduced or transmitted in any form or by any means,
for any purpose, without the express written permission of TEMENOS HEADQUARTERS SA.
© 2012 Temenos Headquarters SA - all rights reserved.

SWIFT – Standards MT November 2019
Table of Contents
Table of Contents .................................................................................................................................... 1

Changes for SWIFT 2019 MT Standards Release ................................................................................. 1
TEMENOS............................................................................................................................................... 1
Version 1.0 .............................................................................................................................................. 1
1 Introduction ...................................................................................................................................... 5
1.1 Executive Summary .............................................................................................................. 6
1.2 Timetable for Changes .......................................................................................................... 7
1.3 References ............................................................................................................................ 8
2 SWIFT Message Changes ............................................................................................................... 9
2.1 Compliance with SWIFT MT Standards ................................................................................ 9
2.2 Compliance with new Rule Book .......................................................................................... 9
2.3 Temenos Changes for SWIFT 2019 ..................................................................................... 9
2.3.1 Temenos timetable for SWIFT 2019 ................................................................................. 9
2.3.2 Temenos charging policy ................................................................................................ 10
2.3.3 Dependency on Previous Temenos SWIFT release changes ........................................ 10
3 SWIFT MT 2019 Amendments – Detailed Requirements ............................................................. 11
3.1 Payment Message Group 1 ................................................................................................ 11
3.1.1 Overview .......................................................................................................................... 11
Added Message Types .................................................................................................................. 11
Removed Message Types ............................................................................................................. 11
Modified Message Types ............................................................................................................... 11
3.1.2 Group 1 Messages requiring changes to the system ...................................................... 11
3.1.3 Group 1 Message changes that do not affect the system ............................................... 12
3.2 Payment Message Group 2 ................................................................................................ 13
3.2.1 Overview .......................................................................................................................... 13
3.3 Treasury Message Group 3 ................................................................................................ 16
3.3.1 Overview .......................................................................................................................... 16
2
3.4 Corporate Collections and Guarantees Group 4 ................................................................ 23

3.4.1 Overview .......................................................................................................................... 23
3.4.3 Group 4 Message Changes that do not affect the system .............................................. 23
3.5 Securities Group 5 .............................................................................................................. 24
3.5.1 Overview .......................................................................................................................... 24
3.6 Corporate and Treasury Group 6 ........................................................................................ 44
3.6.1 Overview .......................................................................................................................... 44
3.7 Trade Finance Group 7 ....................................................................................................... 45
3.7.1 Overview .......................................................................................................................... 45
3.8 Utility Group 9 ..................................................................................................................... 45
3.8.1 Overview .......................................................................................................................... 45
3.9 Common Group Category n ................................................................................................ 46
3.9.1 Overview .......................................................................................................................... 46
3.9.2 Group n Messages requiring changes to the system ...................................................... 47
3.9.3 Group n Message changes that do not affect the system ............................................... 48
3
4 Exclusions ...................................................................................................................................... 49
5 Further Information ........................................................................................................................ 49
5.1 Contact Details .................................................................................................................... 49
Document History
Author Version Date
Temenos 1.0 May 2019
Comments:
4
1 Introduction
This document describes the changes required to Temenos software in order to comply with the
SWIFT Standards changes, which come into effect on 17th November 2019.
The changes described will allow Temenos software to continue to send and receive correctly
formatted SWIFT MT messages.
5
1.1 Executive Summary

Below is a summary by product of the messages that will require changes to Temenos software.
•MT 190, MT 191, MT 192, MT 195, MT 196, MT 199: field 121

Payment Group Series 1
•MT 103, MT 103REMIT, MT 110: field 72
• MT 292, MT 295, MT 296, MT 299: field 121

Payment Group Series 2 • MT 200, MT 201, MT 202, MT 202COV, MT 203, MT 205, MT
205COV: field 72
Retail Series 3 Messages • No changes
Treasury Series 3 Messages • MT 300 Various
Corporate Collections and

• No changes
Guarantees Series 4 Messages
Securities Series 5 Messages • MT 565 Tag 36a, MT 567 Tag 24B
Treasury Metals Series 6 Messages • No changes
Trade Finance Series 7 Messages • No changes
Traveller Cheques Series 8

• Currently not supported
Messages
Utility Series 9 Messages • MT 992, MT 995, MT 996, MT 999: Tag 121
Common Group Category n • MT n92: Tag 79
Figure 1 - Overview of SWIFT MT Message Changes for 2019, which impact the system
6
1.2 Timetable for Changes

The following is the SWIFT standards published timetable.
Date Details
20 July 2018 High-Level Information on Standards MT Release 2019

Summary of change requests received for SR 2019 – change requests
are not yet approved and some may be declined
For resource and budget allocation purposes only –not to be used for
implementation
Updated High-Level Information on Standards MT Release 2019
16 November 2018
Summary of approved change requests received for SR 2019
For resource and budget allocation purposes only –not to be used for
implementation
21 December 2018 Standards MT Release Guide 2019 (public)
Message Format Validation Rules 2019 (login required)
Describes the changes to Standards messages effective as of 17
November 2019
Find advance information for Standards MT Release 2019 in
MyStandards.
Update to Standards MT Release Guide 2019 (public)
22 February 2019
Update to Message Format Validation Rules 2019 (login required)
Describes the changes to Standards messages effective as of 17
November 2019
Find advance information for Standards MT Release 2019 in
MyStandards.
4 May 2019 Vendor Test System
Standards User Handbook
19 July 2019
Standards user handbook for Standards MT Release 2019 published
online.
If necessary, updates to Message Format Validation Rules 2019 also
published.
21 July 2019 Test & Training System
17 November 2019 Standards Release 2019 Live
Figure 2 - Overview of Message Changes for 2019
7
1.3 References
http://www.swift.com
SWIFT maintenance documents dated 21st December 2018.
SWIFT Description
Book
us1m Category 1 – Customer Payments and Cheques
us2m Category 2 – Financial Institution Transfers
us3ma Category 3 - Treasury Markets – Foreign Volume 1 – MT 300 – MT 341
us3mb Exchange Money Market and Derivatives Volume 2 – MT 350 – MT 399
us4m Category 4 – Collections and Cash Letters
us5ma Volume 1 – MT 500 – MT 518
us5mb Volume 2 - MT 519 – MT 543
Category 5 - Securities Markets
us5mc Volume 3 – MT 544 – MT 567
us5md Volume 4 – MT 568 – MT 599
us6mpm Category 6 – Treasury Markets – Commodities
us6ms Category 6 – Treasury Markets – Syndications
us7m Category 7 - Documentary Credits and
Guarantees
us8m Category 8 - Travellers Cheques Currently not supported
us9m Category 9 - Cash Managements and Customer
Status
uscm Category n - Common Group Messages
Figure 3 – References
Additional references can be found on the following link:

https://www.swift.com/standards/standards-releases/release-highlights?tl=en#topic-tabs-
menu
8
2 SWIFT Message Changes

2.1 Compliance with SWIFT MT Standards
Temenos software provides the ability to generate SWIFT messages for the financial
applications the product supports. SWIFT annually revises its rulebook and a new version is
implemented in November each year. Changes may be made to the format and rules for the
formatting of the different messages.
Contractually Temenos provides the necessary updates to the software to ensure that the
application remains compliant with the new SWIFT standard.
2.2 Compliance with new Rule Book

Temenos will ensure that the system will be updated so that after 17 th November 2019 the
system will continue to generate valid SWIFT MT format messages.
Support for new mandatory fields and new or amended conditional field rules will be provided
for previously supported message types.
SWIFT may introduce new optional fields or new options within an existing field for previously
supported message types. In this case, Temenos may provide support for the new option where
appropriate, but we reserve the right not to do so.
Temenos will provide support for new messages where a previous message type is replaced,
and will provide support for all mandatory or conditionally mandatory fields and options in the
new message type.
2.3 Temenos Changes for SWIFT 2019

2.3.1 Temenos timetable for SWIFT 2019
Date Details
Publish impact of standards MT 2019 on Temenos software to
May 2019
clients
End May 2019 Temenos clients to have requested through their account
managers updates for specific releases.
Delivery dates for specific releases will be individually confirmed
only once a formal request has been received from an account
manager
August 2019 Release updates for Temenos software for the following releases
 R19
 201908
August/September
Updates available for client specific releases prior to R19
2019
From September
Clients Test System
2019
17th November 2019 Standards Release 2019 Live
Figure 4 – Temenos timetable
9
2.3.2 Temenos charging policy

Temenos policy is to charge for changes to the system to maintain compliance with SWIFT
standards.
Temenos will make the required documentation and software changes available for 1st August
2019, automatically in the following releases with no additional charge:
 R19
 201908
Please contact your account manager should you require the SWIFT
changes on any release not listed above regarding the cost and
availability, provisional delivery date.
2.3.3 Dependency on Previous Temenos SWIFT release changes

The changes required to the Category 1, 2, and 9 Series
messages that are required to be made to Temenos software
for the SWIFT 2019 changes are dependent on the changes for
SWIFT 2018 being installed in the system.
The SWIFT 2018 Rule Book is a prerequisite for SWIFT 2019.
10
3 SWIFT MT 2019 Amendments – Detailed Requirements

3.1 Payment Message Group 1
3.1.1 Overview
Added Message Types
None
Removed Message Types

None
Modified Message Types

The following messages are identified as having changes by SWIFT:
MT 103, MT 103REMIT, MT 110, MT 190, MT 191, MT 192, MT 195, MT 196, MT 199
3.1.2 Group 1 Messages requiring changes to the system
MT 190 – Advice of Charges, Interest and Other Adjustments

MT 191 – Request for Payment of Charges, Interest and Other Expenses
MT 192 – Request for Cancellation
MT 195 – Queries
MT 196 – Answers
MT 199 – Free Format Message
Field 121 - Unique end-to-end transaction reference (UETR)
MT n91 Usage Rules
When the transaction, to which the charge(s), interest, or other adjustment(s) in MT 191 apply,
contained a Unique End-to-end Transaction Reference (UETR), this UETR may be copied in
field 121 in the user header block of the message.
MT n92 Usage Rules
When the original message contained a Unique End-to-end Transaction Reference (UETR),
this UETR may be copied in field 121 in the user header block of the MT 192, MT 292, or MT
992 request for cancellation message.
MT n95 Usage Rules
995 query message.
MT n96 Usage Rules
996 answer message.
Make field 121 (unique end-to-end transaction reference (UETR)) optional in header block 3 of
enquiry and cancellation messages in categories 1, 2, and 9.
Required software changes
11
For the below outgoing messages the system will be enhanced to support field 121 in Header
Block 3. When the original/related message contained a Unique End-to-end Transaction
Reference (UETR), this UETR will be copied unchanged into field 121 of the following outgoing
messages:
o MT 190 – Advice of Charges, Interest and Other Adjustments
o MT 191 – Request for Payment of Charges, Interest and Other Expenses
o MT 192 – Request for Cancellation
o MT 195 – Queries
o MT 196 – Answers
o MT 199 – Free Format Message
The system will be enhanced to support the incoming MT 191 message. This enhancement
will be restricted to Temenos payments solution only, the Funds Transfer module will not be
enhanced.
Note: From inward processing point of view, no changes are required in the system to process
the following inward messages (MT 192, MT 195, MT 196 and MT 199) as the system can
already receive field 121 for all the category 1 messages that are supported (existing
functionality from MT Standards Release 2018)
The following inward message is currently not supported;

MT190 – Advice of Charges, Interest and Other Adjustments
MT 103 – Single Customer Credit Transfer

MT 103 REMIT – Single Customer Credit Transfer
MT 110 – Advice of Cheque
Field 72 Sender to Receiver Information
PRESENCE
Optional
CODES
REC Receiver Instructions following are for the Receiver of the message.
Remarks
The code word REC is removed in field 72 to increase STP.
Required software Changes

Changes will be made to SWIFT.CODE.WORDS, the code word REC will be removed from
this application. If the use of this code word is bilaterally agreed by the bank then it can be setup
in SWIFT.CODE.WORDS locally.
3.1.3 Group 1 Message changes that do not affect the system

MT 191 – Request for Payment of Charges, Interest and Other Expenses
MT 195 – Queries
12
MT 196 – Answers
For the following inward messages no changes are required as the field 121(UETR) is already
supported from SWIFT 2018 changes, there is the requirement that SWIFT 2018 changes need
to be installed.
MT 195 – Queries
MT 196 – Answers
No changes are required for the following messages, as they are currently not supported.
MT 199 gCCT (gpi Customer Credit Transfer) – Free Format Message

Field 121 - Unique end-to-end transaction reference (UETR) & Field 79 (Narrative)
Make use of payment credit confirmation (with field 121 unique end-to-end transaction
reference (UETR) in header block 3 and structure in field 79 as defined within the SWIFT gpi
service) optional for any SWIFT user.
MT 199 Market Practice Rules
FIN users that are not members of the SWIFT gpi service can optionally use the MT 199
gCCT confirmation message (MT 199 with structured content). This message will allow non-
gpi members to also send a structured payment processing status message. Only if non-gpi
members send the message in scope of the SWIFT gpi service (meaning the receiver is the
SWIFT gpi Tracker, TRCKCHZZ, and user header block field 121 is present) validation
against the mandatory structure as defined in the SWIFT gpi service will be triggered on the
network and the SWIFT gpi Tracker status will be updated.
No changes required
SWIFT GPI functionality is currently not supported. This functionality will only be supported in
Temenos SWIFT GPI solution which will be available only through our Temenos Payments
Hub. For further information on Temenos GPI solution please contact
Sujatha Venkatraman vsujatha@temenos.com
Shrey Rastogi srastogi@temenos.com
3.2 Payment Message Group 2

3.2.1 Overview
Added Message Types
None
13

None

MT 200, MT 201, MT 202; MT 202COV, MT 203, MT 204, MT 205, MT 205COV, MT 292, MT
295, MT 296, MT 299

MT 295 – Queries
MT 296 – Answers
Message Usage Rules
MT n92 Usage Rules
MT n95 Usage Rules
995 query message.
MT n96 Usage Rules
996 answer message.

Reference (UETR), this UETR will be copied unchanged into field 121 of the following outgoing
messages:
 MT 292 – Request for Cancellation
 MT 295 – Queries
 MT 296 – Answers
 MT 299 – Free Format Message
the inward messages MT 292, MT 295, MT 296 and MT 299, as the system can already receive
field 121 for all the category 2 messages that are currently supported (existing functionality from
MT Standards Release 2018)
MT 200 – Financial Institution Transfer for its Own Account
14
MT 201 – Multiple Financial Institution Transfer for its Own Account

MT 202 – General Financial Institution Transfer
MT 202 COV – General Financial Institution Transfer,
MT 203 – Multiple General Financial Institution Transfer
MT 204 – Financial Markets Direct Debit Message
MT 205 – Financial Institution Transfer Execution,
MT 205 COV – Financial Institution Transfer Execution
Tag 72 Sender to Receiver Information
PRESENCE
Optional
CODE
REC Receiver Instructions following are for the Receiver of the message.
The code word REC in field 72 is being removed.

Changes will be made to the SWIFT.CODE.WORDS application. The code word REC will be
removed from this application. If the use of this code word is bilaterally agreed by the bank then
it can be setup in SWIFT.CODE.WORDS locally.

MT 292 – Request for cancellation
MT 295 – Queries
MT 296 – Answers
For the following inward messages, no changes are required as field 121 is already supported
from SWIFT 2018 changes, there is the requirement that SWIFT 2018 changes need to be
installed.
 MT 292 – Request for cancellation
 MT 295 – Queries
 MT 296 – Answers
 MT 299 – Free Format Message
15
3.3 Treasury Message Group 3

3.3.1 Overview
Added Message Types
None

None

SWIFT identifies the following messages as having changes:
MT 300, MT 304, MT 305, MT 306, MT 340, MT 341, MT 360, MT 361, MT 380, MT 381

MT 300 Foreign Exchange Confirmation
Status Tag Field Name Content/Options No.
Mandatory Sequence A General Information
M 82a Party A AA,D, or J 10
M 87a Party B AA,D, or J 11
O 83a Fund or Beneficiary Customer AA,D, or J 12
Mandatory Subsequence B1 Amount Bought
O 53a Delivery Agent AA,D, or J 29
O 56a Intermediary AA,D, or J 30
O 57a Receiving AA,D, or J 31
Mandatory Subsequence B2 Amount Sold
O 53A Delivery Agent AA,D, or J 33
O 56a Intermediary AA,D, or J 34
M 57a Receiving Agent AA,D, or J 35
O 58a Beneficiary Institution AA,D, or J 36
Tighten settlement party fields and trade party fields: In order to promote more structured usage
of the messages, in fields 82, 87, 83, 53, 56, 57, 58 when occurring in sequence A, B1, and B2
the following changes are included:
 Remove option D, which is free format text
 Partially restructure option J codes, to provide more clarity
16
 Mandate that a BIC cannot be the only information in option J. For those cases,
option A must be used.
For more details on these changes please consult the SWIFT Book “us3ma Category 3 -
Treasury Markets – Foreign Exchange Money Market and Derivatives”
Required Software Changes
Currently, the system supports the usage of Option A and D in Tags 82, 87, 53, 56, 57 and 58.
Option J is not supported. Changes will be made to support Option J in MT 300.
Kindly note that wherever the supports usage of option D (Field 56a and 57a in
subsequence B1 and Field 53a, 56a and 57a in subsequence B2) shall now support
option J instead.
Changes will be made to the system to remove the usage of option D in MT 300.

MT 300 Foreign Exchange Confirmation
Field 22L: Reporting Jurisdiction
FORMAT
Option L 35x (Reporting Jurisdiction)
PRESENCE
Mandatory in optional subsequence E1
DEFINITION
This field specifies the supervisory party to which the trade needs to be reported.
CODES
BankOfRussia Central Bank of Russian Federation (RU)
FFMS Federal Financial Markets Service (RU)
Remarks:
Replacing the Reporting Jurisdiction for Russia because the Federal Financial Market Service
in Russia no longer exists. The code "FFMS" was indicated in the Message Reference
Guides as optional code in several category 3 MT’s in field 22L Reporting Jurisdiction, but the
code is now replaced by "BankOfRussia" as they will be taking over the activities of the
Federal Financial Market Service.
No system changes required as the Regulator codes can be parametrized and mapped to
Tag 22L.
An Optional Sequence F has been added to the Message.
Status Tag Field Name Content/Options No.
Optional Sequence F Post-Trade Events
M 15F New Sequence Empty field 88
M 21H Event Type and Reference 4!c/16x 89
O 21F Underlying Liability Reference 16x 90
17
O 30F Profit and Loss Settlement Date 8!n 91
O 32H Profit and Loss Settlement Amount [N]3!a15d 92
O 33E Outstanding Settlement Amount 3!a15d 93
Remarks:
An optional sequence in MT 300 has been added to address a requirement for some regions
whereby trade life cycle events are offered on a FX Forward contract. These are known as
"Post Trade Event" (PTE). That includes early delivery or take up; termination, close out or
Net Present Value (NPV) or extension or rollover of the FX Forward contract.
The system does not support Post-Trade events on Customer Forward contracts that are
prevalent in the Asian markets.
Note: This functionality and the subsequent support for SWIFT confirmation messages may
be developed in the future.
Field 77H: Type, Date, Version

USAGE RULES
If the "Offshore CNY Centre" is not Hong Kong, it can be specified in field 39M as a two letter
country code, for example :39M:TW.
Optional in mandatory sequence B
Remarks:
Correct a misleading message usage rule that refers to field 39M Payment Clearing Centre in
field 77H because field 39M is used to designate the clearing centre for offshore currency
trades, also HK for CNY.
The system does not support Tag 39M, which is an optional field. Hence, the message usage
rule is not applicable.
MT 304 Advice/Instruction of a Third Party Deal

Not supported in the system.
MT 305 Foreign Currency Option Confirmation

FORMAT
PRESENCE
Mandatory in optional subsequence B1
DEFINITION
CODES
Remarks
18
Federal Financial Market Service
The system does not support optional subsequence B1. As a result, the proposed change is
not applicable.

USAGE RULES
Remarks
The system does not support TAG 39M, which is an optional field, this message usage rule is
not applicable.
MT 306 Foreign Currency Option Confirmation

FORMAT
PRESENCE
Mandatory in optional subsequence M1
DEFINITION
CODES
Remarks
in Russia no longer exists. The code "FFMS" was indicated in the Message Reference Guides
as optional code in several category 3 MT’s in field 22L Reporting Jurisdiction, but the code is
now replaced by "BankOfRussia" as they will be taking over the activities of the Federal
Financial Market Service.
The system does not support Tag 39M, which is an optional field. As a result, the message
usage rule is not applicable.

USAGE RULES
Remarks
The system does not support TAG 39M, which is an optional field, this message usage rule is
not applicable.
MT 340 Forward Rate Agreement Confirmation
19

FORMAT
Option L 35x
PRESENCE
Mandatory in optional subsequence G1
DEFINITION
CODES
One of the following codes may be used:
ASIC Australian Securities and Investments Commission (AU)
Remarks:
Guides as optional code in several category 3 MTs in field 22L Reporting Jurisdiction, but the
No system changes required as the system does not support the reporting sequence and
hence the usage of Tag 22L.
Field 77H: Type, Date, Version of the Agreement

USAGE RULES
Remarks:
Correcting a misleading message usage rule that refers to field 39M Payment Clearing Centre
in field 77H because field 39M is used to designate the clearing centre for offshore currency
No change are required as the system does not support Tag 39M, which is an optional tag.
Hence, the message usage rule is not applicable.
MT 341 Forward Rate Agreement Settlement Confirmation

FORMAT
PRESENCE
Mandatory in optional subsequence D1
DEFINITION
CODES
20

Remarks:
No system changes are required, as the system does not support the reporting sequence in
MT 341.
MT 360 Single Currency Interest Rate Derivative Confirmation

FORMAT
PRESENCE
Mandatory in optional subsequence O1
DEFINITION
CODES
Remarks:
MT 360.

USAGE RULES
Remarks:
Correcting a misleading message usage rule that refers to field 39M Payment Clearing Centre
in field 77H because field 39M is used to designate the clearing centre for offshore currency
No system changes are required, the system does not support Tag 39M, which is an optional
tag. Hence, the message usage rule is not applicable.
MT 361 Cross Currency Interest Rate Swap Confirmation

Field 77H: Type, Date, Version of the agreement
21
FORMAT
Option H 6a[/8!n][//4!n] (Type)(Date)(Version)
PRESENCE
Mandatory in mandatory sequence A
DEFINITION
This field specifies the type of the Agreement covering the transaction, followed by the date
on which the Agreement was signed and the version of the Agreement.
CODES
Remarks:
MT 361.

USAGE RULES
Remarks:
A correction to a misleading message usage rule that refers to field 39M Payment Clearing
Centre in field 77H because field 39M is used to designate the clearing centre for offshore
currency trades, also HK for CNY.
No system changes are required as the system does not support Tag 39M, which is an
optional tag. Hence, the message usage rule is not applicable.
MT 380 Foreign Exchange Order

MT 380 is not supported in the system.
MT 381 Foreign Exchange Order Confirmation

MT 381 is not supported in the system.
22
3.4 Corporate Collections and Guarantees Group 4

3.4.1 Overview
Added Message Types
None

None

None

Not applicable
3.4.3 Group 4 Message Changes that do not affect the system

Not applicable
23
3.5 Securities Group 5

3.5.1 Overview
Added Message Types
None

MT 599

MT 502, MT 506, MT 509, MT 513, MT 514, MT 515, MT 517, MT 518,
MT 530, MT 535, MT 536, MT 537, MT 540, MT 541, MT 542, MT 543,
MT 544, MT 545, MT 546, MT 547, MT 548, MT 549, MT 564, MT 565, MT 566, MT 567
MT 575, MT 578, MT 586

The following are minor changes to MT 565 and MT 567
MT 565 Corporate Action Instruction
Field 36a: Quantity of Financial Instrument

PRESENCE
Conditional (see rule C5) in mandatory sequence D
QUALIFIER
(Error code(s): T89)
Order M/O Qualifier R/N CR Options Qualifier Description

1 O QINS R C4, B or C Quantity of Securities Instructed
C7C4
2 O COND N B Conditional Quantity
3 O RDUQ N B Additional Round Up Quantity
DEFINITION
This qualified generic field specifies:
COND Conditional Minimum quantity of securities to be accepted (used in the

Quantity framework of conditional privilege on election). In case of proration,
if this minimum quantity is not reached then the instruction is void
QINS Quantity of Quantity of securities to which this instruction applies
Securities
Instructed
24
RDUQ Additional Round Quantity of additional shares requested due to the difference of
Up Quantity "round-up against payment" practice between the account servicer
and the account holder (for instance for French dividend option).
USAGE RULES
QINS could refer to one account in case of one account per instruction. It would refer
to the aggregated quantity of the different accounts if the instruction message refers to
more than one account, that is multiple B2 subsequence.
Remarks:
Add qualifier RDUQ in field 36a in sequence D of MT 565.
To enable CSD participants to indicate the additional quantity of new shares which must be
added to the number of shares calculated by the CSD based on the exercised rights provided
by its participants on the Securities option with Buy Up disposition of fraction. This applies as
well for exercise of warrants and conversion of bonds.
This code will be added to SC.CA.REASON.CODE in release 201908. For any releases prior
to this, it can be added manually locally to SC.CA.REASON.CODE.
MT 567 Corporate Action Status and Processing Advice

Field 24B: Reason Code
PRESENCE
Mandatory in optional subsequence A2a
CODES
If Qualifier is REJT and Data Source Scheme is not present, Reason Code must contain one
of the following codes (Error code(s): K24):
IRDQ Invalid Use Round Instruction is rejected due to invalid use of additional round up
Up Quantity quantity (RDUQ)
Remarks:
Code IRDQ is added to qualifier REJT in field 24B in subsequence A2a in MT 567.
To enable CSD participants to indicate the additional quantity of new shares which must be
added to the number of shares calculated by the CSD based on the exercised rights provided
by its participants on the Securities option with Buy Up disposition of fraction. This applies as
well for exercise of warrants and conversion of bonds.
This code will be added to SC.CA.REASON.CODE in release 201908. For any releases prior
to this, it can be added manually locally to SC.CA.REASON.CODE.
MT 559 Paying Agents Claim

The removal of this message does not impact the system as it is not supported.
MT 506 Collateral and Exposure Statement

Field 20a:20C: Reference
FORMAT
25
Option C :4!c//16x (Qualifier)(Reference)

Option U :4!c//52x (Qualifier)(UTI Reference)
PRESENCE
Optional in optional sequence C
QUALIFIER
1 O TRRF R C or U Deal Reference
2 O CPTR R C Counterparty's Deal Reference
Remarks:
The above changes are summarised as:
 A new format option is added to qualifier TRRF in field 20C of subsequence Linkages
to allow 52 characters.
 Transport the Unique Transaction Identifier (UTI) in Trade Initiation and Confirmation
(TIC) and Settlement and Reconciliation (S&R) messages
The proposed change is not applicable, as the message MT 506 is not supported.
MT 515 Client confirmation of Purchase or Sale

MT 517 Trade Confirmation Affirmation
FORMAT
PRESENCE
Mandatory in Mandatory subsequence A1
QUALIFIER
Remarks:
26
The proposed change is not applicable for message MT 515, as the system supports only
RELA in 20C of subsequence Linkages. Hence the change in tag 20C Qualifier TRRF does
not have an impact for the messages listed above.
The message MT 517 is not supported.
MT 509 Trade Status Message

MT 513 Client Advice Of Execution
MT 514 Trade Allocation Instruction
MT 518 Market-Side Securities Trade Confirmation
FORMAT
PRESENCE
Mandatory in optional subsequence A1
QUALIFIER
Remarks:
The proposed change is not applicable, as the system supports only RELA in 20C of
subsequence Linkages. Hence the change in tag 20C Qualifier TRRF does not have an
impact for the messages listed above.
MT 530 Transaction Processing Command

FORMAT
PRESENCE
27
Mandatory in Mandatory sequence B

QUALIFIER
Remarks:
The proposed change is not applicable, as message MT 530 is not supported.
MT 502 Order to Buy or Sell

Field 22F: Indicator
PRESENCE
Mandatory in optional sequence C
CODES
If Qualifier is SETR and Data Source Scheme is not present, Indicator must contain one of
the following codes (Error code(s): K22):
BSBK Buy Sell Back Relates to a buy sell back
transaction
BYIY Buy In The transaction related to a
buy-in by the market following
a delivery transaction failure
Add a code for Buy-in indicator when qualifier SETR is used in field 22F of subsequence
Settlement Details.
CSDR proposes to adopt a Buy-in mechanism in case of fail delivery of fail instrument. The
new trade must carry a reference to the original trade and be specified to this new Buy-in.
Remarks:
The change will be analysed, and considered for inclusion, with a development that is
currently in progress to handle institutional client custody/account servicing functionality, this
functionality will only be available in a future release.
MT 513 Client Advice of Execution

MT 514 Trade Allocation Instrument
Field 17B: Flag
PRESENCE
28
Optional in optional subsequence C

QUALIFIER

1 O ACRU N B Accrued Interest Flag
2 O STAM N B Stamp Duty Flag
3 O EXEC N B Brokerage Amount Flag
4 O RSCH N B Research Fee Flag
DEFINITION
ACRU Accrued Interest Flag Indicates whether the net proceeds include interest
accrued on the financial instrument.
EXEC Brokerage Amount Flag Indicates whether the net proceeds include brokerage
fees for the transaction.
RSCH Research Fee Flag Indicates whether the net proceeds include research
STAM Stamp Duty Flag Indicates whether the net proceeds include stamp duty
for the transaction.
Remarks:
The above change is summarised as
 Add a research fee qualifier RSCH in field 17B of subsequence Amounts.
The proposed change is not applicable in the system as it currently supports only the qualifier
ACRU under 17B of subsequence Amounts and processes confirmation.
MT 515 Client Confirmation of Purchase or Sale

Field 17B: Flag
PRESENCE
Optional in optional subsequence D3
QUALIFIER

29
DEFINITION
Remarks:
MT 518 Market-Side Securities Trade Confirmation

Field 17B: Flag
PRESENCE
Optional in optional subsequence C3
QUALIFIER

DEFINITION
30
Remarks:
MT 535 Statement of Holdings

Format Specifications
Status Tag Qualifier Generic Field Detailed Field Name Content/Options No.
Name
Optional Repetitive Sequence C Additional Information
M 16R Start of Block ADDINFO 75
O 95a 4!c Party (see qualifier description) P, Q, or R 76
O 19A 4!c Amount (see qualifier description) :4!c//[N]3!a15d 77
O 70H ADTX Narrative Additional Text :4!c//2500z 78
M 16S End of Block ADDINFO 79

78
End of Sequence C Additional Information
Field 70H: Narrative: Additional Text

FORMAT
Option H :4!c//2500z (Qualifier)(Narrative)
PRESENCE
QUALIFIER

1 O ADTX N H Additional Text
DEFINITION
31
ADTX Additional Text Provides additional information or specifies in more detail the content of
a message. This field may only be used when the information to be transmitted cannot be
coded.
USAGE RULES
Unless bilaterally agreed between the Sender and the Receiver, narrative field 70a must not
contain information that can be provided in a structured field.
Field 17B: Flag
PRESENCE
QUALIFIER

1 M ACTI N B Activity Flag
2 O AUDT N B Audited Statement
3 M CONS N B Sub-safekeeping Statement
4 O LOTS N B Tax Lots
5 O SLRS N B Security Interest, Lien or Right of Set-Off
DEFINITION
SLRS Security Interest, Indicates whether the holdings on the account are subject to
Lien or Right of Set- security interest, lien or right of set-off.
Of

PRESENCE
CODES
If Qualifier is SFRE and Data Source Scheme is not present, Indicator must contain one of the
following codes (Error code(s): K22):
QUTR Quarterly Statement is sent quarterly (four times per year).
Remarks:
The above changes are summarised as
 A new field has been added for Holdings Narrative in sequence C.
 A new qualifier has been added for Security Interest, Lien or Right of Set-Off in field 17B
of sequence A.
 A new code has been added for Quarterly Statements indicator when qualifier SFRE is
used without Data Source Scheme in field 22F for sequence A.
32
The proposed changes are not applicable to the system as

 Optional tags in Sequence C are currently not supported
 The addition of optional flag SLRS under 17B in sequence A does not impact the system
 SFRE under tag 22F is not currently supported, as a result the addition of the new code
QUTR under SFRE does not impact the system
MT 537 – Statement of pending Transactions

The addition of a Penalty/Penalty Redistribution sequence in the MT 537 (Statement of
Pending Transactions).
For the details of this change to the MT 537, please refer to the “Message Reference Guide:
Volume 2 (MT 519 - MT 543)”.
Remarks:
Currently the system does not support the message MT 537. Therefore, the proposed change
will not be applicable.
MT 535 Statement of Holdings

MT 537 Statement of Pending Transactions
MT 540 Receive Free
MT 541 Receive Against Payment
MT 542 Deliver Free
MT 543 Deliver Against Payment
MT 544 Receive Free Confirmation
MT 545 Receive Against Payment Confirmation
MT 546 Deliver Free Confirmation
MT 547 Deliver Against Payment Confirmation
MT 548 Settlement Status and Processing Advice
MT 549 Request For Statement/Status Advice
FORMAT
PRESENCE
Mandatory in optional subsequence A1
QUALIFIER
1 M POOL N C Pool Reference
or PREA N C Preadvice Message Reference
or PREV N C8 C Previous Message Reference
33
or RELA N C Related Message Reference
or TRRF N C or U Deal Reference
Remarks:
A new format option is added to qualifier TRRF in field 20C of subsequence Linkages to allow
52 characters.
The proposed change is not applicable in the messages listed above, as the system supports
only RELA in 20C of subsequence Linkages. Hence, the change in tag 20C Qualifier TRRF
does not have an impact.
MT 537 is not supported.
MT 536 Statement of Transactions

FORMAT
PRESENCE
Mandatory in mandatory subsequence B1a1
QUALIFIER
1 M POOL N C Pool Reference
or PREA N C Preadvice Message Reference
or PREV N C8 C Previous Message Reference
or RELA N C Related Message Reference
or TRRF N C or U Deal Reference
Remarks:
A new format option is added to qualifier TRRF in field 20C of subsequence Linkages to allow
52 characters.
The proposed change is not applicable in this message, as the system supports only RELA in
20C of subsequence Linkages. Hence, the change in tag 20C Qualifier TRRF does not have
an impact.
MT 540 Receive Free

MT 542 Deliver Free
34

PRESENCE
CODES
If Qualifier is RPOR and Data Source Scheme is not present, Indicator must contain one of
the following codes (Error code(s): K22):
BYIY Buy In The transaction relates to a buy-in by the market following a delivery
transaction failure.
Remarks:
A new code is added for Buy-in indicator when qualifier RPOR is used in field 22F of
subsequence Settlement Details.
CSDR proposes to adopt a Buy-in mechanism in case of fail delivery of fail instrument. The
new trade must carry a reference to the original trade and be specified to this new Buy-in.
No changes are required, as the system does not currently support the functionality.

Field 23G: Function of the Message
CODES
Function must contain one of the following codes (Error code(s): T86):
CAST Cancellation Message reporting on a cancellation request status.

Request Status
INST Transaction Status Message reporting on an instruction status.
PENA Penalties Message contains settlement penalties
Remarks:
A new Optional Penalty/Penalty Redistribution sequence C has been added. Please refer to
the Message Reference Guide: Volume 3 (MT 544 - MT 567) for specific details on this
change.
CSDs will implement a penalty mechanism for settlement fails, which will serve as an effective
deterrent for participants that cause settlement fails. The penalties information needs to be
transported.
The above changes are not applicable as the functionality to automatically charge a penalty in
case of settlement fails is currently not supported in the system.
MT 540 Receive Free

MT 542 Deliver Free
35

Field 17B: Flag
PRESENCE
QUALIFIER
DEFINITION
ACRU Accrued Interest Indicates whether the net proceeds include interest accrued on
Flag the financial instrument.
EXEC Brokerage amount Indicates whether the net proceeds include brokerage fees for
Flag the transaction.
RSCH Research Fee Flag Indicates whether the net proceeds include research fees for
the transaction.
STAM Stamp Duty Flag Indicates whether the net proceeds include stamp duty for the
transaction.
Remarks:
The proposed change is not applicable as the system supports only qualifier ACRU under
17B of subsequence Amounts.
The system processes settlement based on overall amounts in the confirmation received.
MT 564 Corporate Action Notification

Field 95a: Party
FORMAT
Option L :4!c//18!c2!n (Qualifier)(Legal Entity Identifier)
PRESENCE
Optional in optional sequence F
QUALIFIER
3 O ISAG R L,P,Q,or Issuer Agent
R
12 O ISSU N L, P, Q, Issuer
or R
13 O OFFO R L, P, Q, Offeror
or R
36
14 O TAGT N L, P, Q, Transfer Agent

or R
DEFINITION
ISSU Issuer Issuer of the financial instrument.
OFFO Offeror Party making the offer and which is different from the issuing company
TAGT Transfer agent A trust company, bank, or similar financial institution appointed by a
Fund Management Company to maintain records of investors and
account balances. The transfer agent records transactions, including
subscriptions, redemptions, switches, transfers, and re-registrations.
Remarks:
The qualifiers ISSU (Issuer), OFFO (Offeror), and TAGT (Transfer Agent) are added in field
95a Party in sequence F in MT 564 with format options L, P, Q, R.
The above change is not applicable, as system currently does not support field 95a Party in
Sequence F in MT 564. Therefore the addition of qualifier ISSU, OFFO and TAGT in this
sequence does not impact the system.

Field 95a: Party
FORMAT
Option L :4!c//18!c2!n (Qualifier)(Legal Entity Identifier)
PRESENCE
Mandatory in optional sequence C
QUALIFIER
1 M OWND RN C6 L,P,R or Beneficial Owner’s Identification

V
Remarks:
Add new format option L to field 95a Party on qualifier OWND and make it repeatable in
sequence C of MT 565 and add new network validated rule on OWND in MT 565.
The above change is not applicable, as system currently does not support sequence C of MT
565. Hence addition of a qualifier OWND in tag 95A does not impact the system.
MT 566 Corporate Action Confirmation

Field 17B: Flag
PRESENCE
QUALIFIER
37
Order M/0 Qualifier R/N CR Options Qualifier Description

1 O CERT N B Certification/Breakdown Flag
DEFINITION
CERT Certification/ Indicates whether certification/breakdown is required.
Breakdown Flag
The qualifier CERT in field 17B in sequence C of MT 566 has been deleted.
Remarks:
The above change is not applicable, as system currently does not support field 17B in
sequence C. Hence deletion of the qualifier in this sequence does not impact the system.

Field 19B: Amount: Instructed Amount
PRESENCE
Conditional (see rule C5) in mandatory sequence D
QUALIFIER
1 O QCAS N C5 B Instructed Amount
Remarks:
The underlying functionality of sending the instructed amount is currently not available in the
System

Field 20D: Reference: Shareholder Number
FORMAT
Option D :4!c//25x (Qualifier)(Reference)
PRESENCE
Optional in mandatory sequence D
QUALIFIER
1 O SHAR N D Shareholder Number
DEFINITION
38
SHAR Shareholder Reference number assigned to identify an investor or a shareholder with

Number the issuer or the registration provider (for instance allocation code)
NETWORK VALIDATED RULES

Reference must not start or end with a slash '/' and must not contain two consecutive slashes
'//' (Error code(s): T26).
Remarks
Add optional and repeatable field 20D Reference with qualifier SHAR to sequence D of MT 565.
The above change is not applicable, as the underlying functionality is currently not supported by the
system.

Field 24B: Indicator
PRESENCE
Mandatory in option subsequence A2A
CODES
SHAR Shareholder Shareholder number or reference is missing
Number Missing
Remarks
A new rejection reason code SHAR is added to qualifier REJT in field 24B in subsequence A2a in MT
567.
System.

Field 19B: Amount
PRESENCE
Conditional (see rule C2) in optional subsequence E2
QUALIFIER

47 O DEDI N B Deemed Dividend Amount
48 O DEFP N B Deemed Fund Amount
49 O DEIT N B Deemed Interest Amount
50 O DERY N B Deemed Royalties Amount
DEFINITION
DEDI Deemed Dividend Deemed amount resulting from the difference between the rate of
Amount dividend proceeds attributed to the security holder for the taxable
39
year and the rate of dividend proceeds previously notified to the

security holder in relation to cash distributions for the year
DEFP Deemed Fund Deemed amount resulting from the difference between the rate of
Amount the proceeds components comprising a fund payment attributed to
the security holder for the taxable year and the rate of the fund
proceeds previously notified to the security holder in relation to
cash distributions for the year
DEIT Deemed Interest Deemed amount resulting from the difference between the rate of
Amount interest proceeds attributed to the security holder for the taxable
year and the rate of interest proceeds previously notified to the
security holder in relation to cash distributions for the year.
DERY Deemed Royalties Deemed amount resulting from the difference between the rate of
Amount royalty proceeds attributed to the security holder for the taxable
year and the rate of royalty proceeds previously notified to the
Remarks:
The qualifiers DEDI, DEFP, DEIT, and DERY are added in field 19B in subsequence E2 of
MT 564.
To enable the account servicer to communicate the cash amounts components corresponding
to the four deemed rate type codes defined for the Deemed Rate that may be used for Tax
On Non-Distributed Proceeds event as specified in the AU tax law amendment for attribution
managed investment trust (AMIT).
The recording of income components as per AU Tax law is currently not supported

Field 19B: Amount
FORMAT
Option B :4!c//3!a15d (Qualifier)(Currency Code)(Amount)
PRESENCE
QUALIFIER

52 O DEDI N B Deemed Dividend Amount
53 O DEFP N B Deemed Fund Amount
54 O DEIT N B Deemed Interest Amount
55 O DERY N B Deemed Royalties Amount
DEFINITION
40
DEDI Deemed Dividend Deemed amount resulting from the difference between the rate of
Amount dividend proceeds attributed to the security holder for the taxable
year and the rate of dividend proceeds previously notified to the
security holder in relation to cash distributions for the year
DEFP Deemed Fund Deemed amount resulting from the difference between the rate of
Amount the proceeds components comprising a fund payment attributed to
the security holder for the taxable year and the rate of the fund
proceeds previously notified to the security holder in relation to
cash distributions for the year
DEIT Deemed Interest Deemed amount resulting from the difference between the rate of
Amount interest proceeds attributed to the security holder for the taxable
year and the rate of interest proceeds previously notified to the
DERY Deemed Royalties Deemed amount resulting from the difference between the rate of
Amount royalty proceeds attributed to the security holder for the taxable
year and the rate of royalty proceeds previously notified to the
Remarks:
The qualifiers DEDI, DEFP, DEIT, and DERY are added in field 19B in subsequence D2 of
MT 566.
To enable the account servicer to communicate the cash amounts components corresponding
to the four deemed rate type codes defined for the Deemed Rate that may be used for Tax
On Non-Distributed Proceeds event as specified in the AU tax law amendment for attribution
managed investment trust (AMIT).
The recording of income components as per AU Tax law is currently not supported.

Field 24B: Reason Code
PRESENCE
Mandatory in optional subsequence A2a
CODES
If Qualifier is REJT and Data Source Scheme is not present, Reason Code must contain one
of the following codes (Error code(s): K24):
DQBI Invalid Bid Bid price/basis points/percentage increments rejected due to
Increment invalid bid increment for the event (generally used in Dutch
Auctions or Bid Tenders)
DQBV Invalid Bid Value Bid price/basis points/percentage falls outside of bid range for the
event (generally used in Dutch Auctions or Bid Tenders).
Remarks:
The codes DQBI and DQBV are added to qualifier REJT in field 24B in subsequence A2a in
MT 567.
To be able to report specific rejection reasons for invalid bid price or bid increment present in
instructions on events with bidding ranges such as Dutch auction events.
The above change is not applicable, as the underlying functionality is not supported.
41

PRESENCE
Mandatory in optional sequence E
SHAR Shareholder Number Indicates usage of a reference number to identify an

investor or a shareholder with the issuer or the
registration provider (for instance allocation code).
Remarks
The code SHAR (Shareholder Number) is added to qualifier OPTF in field 22F in sequence E in MT 564.
System.

Field 19B: Amount
PRESENCE
QUALIFIER
56 O ADJS N B Adjusted Subscription Amount
57 O REFU N B Refunded Subscription Amount
Remarks:
The qualifiers ADJS and REFU are added in the field 19B in subsequence D2
To enable the agent to communicate an adjustment to a subscription amount after the final
rate of the rights offer has been fixed and to report also the part of the original subscription
amount that must be refunded in case of pro-ration of the oversubscription
The above change is not applicable, as system does not support the underlying functionality.
The system currently supports only the qualifier PSTA in fields 19B in subsequence D2.

Field 22a: Indicator
PRESENCE
Mandatory in mandatory sequence D
QUALIFIER
5 O OPTF N F Option Features Indicator
42
DEFINITION
OPTF Option Features Specifies the features that may apply to a corporate action option.
Indicator
CODES
In option F, if Qualifier is OPTF and Data Source Scheme is not present, Indicator must
contain the following code (Error code(s): K22):
OPLF Odd Lot Preference Tender or Exchange with the Odd Lot Preference
Remarks:
A new qualifier is added OPTF with code value OPLF in field 22a in sequence D of MT 565.
To enable the securities holders to notify the depository that particular instructions should be
treated as an odd-lot (for example that instructions should not be pro-rated if pro-ration were
to occur).
The above change is not applicable as the functionality to treat an instruction as an odd-lot is
currently not supported within the system.

Field 22a: Indicator: Corporate Action Option Code Indicator
PRESENCE
Conditional (see rule C2) in optional sequence B
QUALIFIER
1 O CAOP N C2 F or H Corporate Action Option Code Indicator
2 O OPTF N F Option Features Indicator
DEFINITION
CAOP Corporate Action Specifies the corporate action options available to the account
Option Code Indicator owner
OPTF Option Features Specifies the features that may apply to a corporate action
Indicator option.
CODES
In option F, if Qualifier is OPTF and Data Source Scheme is not present, Indicator must contain
the following code (Error code(s): K22):
OPLF Odd Lot Preference Tender or Exchange with the Odd Lot Preference
Remarks:
A new qualifier is added OPTF with code value OPLF in field 22a in sequence B of MT 567.
43
To enable the securities holders to notify the depository that particular instructions should be
treated as an odd-lot (for example that instructions should not be pro-rated if pro-ration were
to occur).
The above change is not applicable as the functionality to treat an instruction as an odd-lot is
currently not supported within the system.
3.6 Corporate and Treasury Group 6

3.6.1 Overview
Added Message Types
None

None

MT 600, MT 601

None

MT 600 Commodity Trade Confirmation
PRESENCE
CODES
One of the following codes may be used.
The Federal Financial Market Service in Russia no longer exists. The code "FFMS" was
indicated in the Message Reference Guides as optional code in field 22L Reporting Jurisdiction,
but the code will be replaced by "BankOfRussia" as they will be taking over the activities of the
No system changes required, as the system does not support the reporting sequence in MT600
MT 601 Commodity Option Confirmation
44

PRESENCE
Mandatory in optional subsequence B1
CODES
One of the following codes may be used:
Remarks
The system does not support optional subsequence B1. Proposed Change is not applicable
3.7 Trade Finance Group 7

3.7.1 Overview
Added Message Types
None

None

None
3.8 Utility Group 9

3.8.1 Overview
Added Message Types
None

None

MT 992, MT 995, MT 996, MT 999

MT 995 – Queries
MT 996 – Answers
45
MESSAGE USAGE RULES

MT n92 Usage Rules
MT n95 Usage Rules
995 query message.
MT n96 Usage Rules
996 answer message.

Reference (UETR), this UETR will be copied in field 121 of the following outgoing messages:
o MT 992 – Request for Cancellation
o MT 995 – Queries
o MT 996 – Answers
o MT 999 – Free Format Message
all these inward messages (MT 992, MT 995, MT 996 and MT 999) as the system can already
receive field 121 in all these inward messages.

None
3.9 Common Group Category n

3.9.1 Overview
Added Message Types
None

None

n92
46
3.9.2 Group n Messages requiring changes to the system
n92 – Request for Cancellation

Field 79: Narrative Description of the Original Message
Add optional code words to field 79 to indicate cancellation reason
FORMAT
35*50x (Narrative)
In addition to narrative text, the following line formats may be used:
Line 1 /4!c//4!a/ [additional information] (Cancellation Reason)(Narrative)
Lines 2-35 [//continuation of additional information] (Narrative)
PRESENCE
Conditional (see rule C1)
DEFINITION
This field contains a narrative description of the original message, or single transaction
within a multiple message, which will enable the Receiver to positively identify the
message or transaction to be cancelled.
CODES
Cancellation Reason may contain one of the following codes:
AGNT Incorrect Agent Agent in the payment workflow is incorrect
AM09 Wrong Amount Amount is not the amount agreed or expected.
COVR Cover Cancelled or Cover payment has either been returned or cancelled.
Returned
CURR Incorrect Currency Currency of the payment is incorrect.
CUST Requested by Customer Cancellation requested by the ordering customer.
CUTA Cancel upon Unable to Cancellation requested because an investigation

Apply request has been received and no remediation is
possible.
DUPL Duplicate Payment Payment is a duplicate of another payment.
FRAD Fraudulent Origin Cancellation requested following a transaction that

was originated fraudulently. The use of the Fraudulent
Origin code should be governed by jurisdictions.
TECH Technical Problem Cancellation requested following technical problems

resulting in an erroneous transaction.
UPAY Undue Payment Payment is not justified.
Add optional code words to field 79 to indicate cancellation reason
47
Changes will be made to the SWIFT.CODE.WORDS application and the above 2 new optional
code words (AM09 and COVR) will be added for field 79 to indicate the cancellation reason.
3.9.3 Group n Message changes that do not affect the system
n92 – Request for Cancellation

Field 79: Narrative Description of the Original Message
Add a usage rule to indicate willingness to indemnify in field 79.
USAGE RULES
When the sender of the cancellation request is willing to consider an indemnity, the code INDM
may be used as narrative after the cancellation reason in this field.
Changes to T24 are not required.
48
4 Exclusions
Temenos software currently does not support SWIFT GPI; population of tag 111 in outgoing
messages for GPI participating banks has been excluded.
5 Further Information
5.1 Contact Details
Area Product Manager Contact Address
General SWIFT questions, Lisa Hall lhall@temenos.com

payments and utility
Phil White pwhite@temenos.com
messages
Sujatha Venkatraman vsujatha@temenos.com
Treasury Adam Gable agable@temenos.com
Corporate Steve Scott sscott@temenos.com
Retail Andy Hall ahall@temenos.com
Wealth Balasubramanian Viswanath bsviswa@temenos.com

Paul Taylor ptaylor@temenos.com
49

Standard Document Template - Portrait

Uploaded by

Copyright:

Available Formats

You might also like

Standard Document Template - Portrait

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

Standard Document Template - Portrait

Uploaded by

Copyright:

Available Formats

TEMENOS

Changes for SWIFT 2019 MT Standards Release

Information in this document is subject to change without notice.

© 2012 Temenos Headquarters SA - all rights reserved.

Table of Contents .................................................................................................................................... 1

3.4 Corporate Collections and Guarantees Group 4 ................................................................ 23

Author Version Date

Temenos 1.0 May 2019

1.1 Executive Summary

•MT 190, MT 191, MT 192, MT 195, MT 196, MT 199: field 121

• MT 292, MT 295, MT 296, MT 299: field 121

Retail Series 3 Messages • No changes

Treasury Series 3 Messages • MT 300 Various

Corporate Collections and

Securities Series 5 Messages • MT 565 Tag 36a, MT 567 Tag 24B

Treasury Metals Series 6 Messages • No changes

Trade Finance Series 7 Messages • No changes

Traveller Cheques Series 8

Utility Series 9 Messages • MT 992, MT 995, MT 996, MT 999: Tag 121

Common Group Category n • MT n92: Tag 79

1.2 Timetable for Changes

20 July 2018 High-Level Information on Standards MT Release 2019

17 November 2019 Standards Release 2019 Live

Figure 2 - Overview of Message Changes for 2019

Additional references can be found on the following link:

2 SWIFT Message Changes

2.2 Compliance with new Rule Book

2.3 Temenos Changes for SWIFT 2019

17th November 2019 Standards Release 2019 Live

Figure 4 – Temenos timetable

2.3.2 Temenos charging policy

2.3.3 Dependency on Previous Temenos SWIFT release changes

The SWIFT 2018 Rule Book is a prerequisite for SWIFT 2019.

3 SWIFT MT 2019 Amendments – Detailed Requirements

Removed Message Types

Modified Message Types

3.1.2 Group 1 Messages requiring changes to the system

MT 190 – Advice of Charges, Interest and Other Adjustments

Required software changes

The following inward message is currently not supported;

MT 103 – Single Customer Credit Transfer

Required software Changes

3.1.3 Group 1 Message changes that do not affect the system

MT 190 – Advice of Charges, Interest and Other Adjustments

MT 199 gCCT (gpi Customer Credit Transfer) – Free Format Message

3.2 Payment Message Group 2

Removed Message Types

Modified Message Types

3.2.2 Group 2 Messages requiring changes to the system

Required software changes

MT 200 – Financial Institution Transfer for its Own Account

MT 201 – Multiple Financial Institution Transfer for its Own Account

The code word REC in field 72 is being removed.

3.2.3 Group 2 Message changes that do not affect the system

3.3 Treasury Message Group 3

Removed Message Types

Modified Message Types

3.3.2 Group 3 Messages requiring changes to the system

Status Tag Field Name Content/Options No.