Oracle® Banking Treasury

Management
Messaging User Guide

Release 14.7.2.0.0
F89104-01
November 2023
Oracle Banking Treasury Management Messaging User Guide, Release 14.7.2.0.0

F89104-01

Copyright © 2020, 2023, Oracle and/or its affiliates.

This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.

If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related
documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S.
Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,
any programs embedded, installed, or activated on delivered hardware, and modifications of such programs)
and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end
users are "commercial computer software," "commercial computer software documentation," or "limited rights
data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental
regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation
of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated
software, any programs embedded, installed, or activated on delivered hardware, and modifications of such
programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and
limitations specified in the license contained in the applicable contract. The terms governing the U.S.
Government's use of Oracle cloud services are defined by the applicable contract for such services. No other
rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.

Oracle®, Java, MySQL and NetSuite are registered trademarks of Oracle and/or its affiliates. Other names
may be trademarks of their respective owners.

Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc,
and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise
set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be
responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,
products, or services, except as set forth in an applicable agreement between you and Oracle.
Contents
Preface
Audience vi
Acronyms and Abbreviations vi
Conventions vii
List of Topics vii
Related Resources viii
Symbols and Icons viii

1 An Overview of the Message System

2 Messaging Branch Preferences Maintenance

2.1 Maintain Messaging Branch Parameters 2-1
2.2 Maintain Message Types 2-5
2.3 Maintain SWIFT Tag 2-7
2.4 Process PDE Messages 2-8

3 Maintain Addresses for Customer

3.1 Maintain Address at Customer (CIF) Level 3-1
Change Log 3-9
3.2 View Customer Address 3-10

4 Maintain Advice Formats

4.1 Maintain Advice Format Details 4-2
4.2 Start the Background Process 4-4

5 Process Outgoing Messages

5.1 Generate Messages from Outgoing Browser 5-2

iii
6 Retrieve an Archived Message
6.1 Process Message History Retrieval Summary 6-1
6.2 Process Message 6-2

7 Process Incoming Messages

7.1 Incoming Messages 7-1
7.1.1 View Incoming Message Browser Summary 7-2
7.1.2 View Details of Incoming Message 7-9
7.1.3 Edit Incoming Message 7-10

8 Define Free Format Messages

8.1 Maintain Free Format Message 8-1
Maintain Free Format Message - Message Tab 8-3
Maintain Free Format Message - SWIFT Message Details Tab 8-4
Maintain Free Format Message - Free Format Text Tab 8-6

9 Process Query
9.1 Launch Advanced Search Screen 9-1
9.2 Make Query based on more than one Criterion 9-3
9.3 Select Same Criterion to Apply One or More Conditions 9-3
9.4 Order Details of Query 9-4
9.5 Using Wildcards to make Query 9-6

10 Process SWIFT Messages

10.1 Treasury Markets - Foreign Exchange, Money Markets and Derivatives 10-2
10.1.1 MT 300 Foreign Exchange Confirmation 10-3
10.1.2 MT 304 Advice/Instruction of a Third Party Deal 10-5
10.1.3 MT 305 Foreign Currency Option Confirmations 10-8
10.1.4 MT 306 Foreign Currency Option Confirmation 10-9
10.1.5 MT 320 Fixed Loan/Deposit Confirmation 10-17
10.1.6 MT 330 Call/Notice Loan/Deposit Confirmation 10-20
10.1.7 MT 340 Forward Rate Agreement Confirmation 10-23
10.1.8 MT 341 Forward Rate Agreement Settlement Confirmation 10-26
10.1.9 MT 350 Advice of Loan/Deposit Interest Payment 10-27
10.1.10 MT 360 Single Currency Interest Rate Derivative Confirmation 10-29
10.1.11 MT 361 Cross Currency Interest Rate Swap Confirmation 10-35
10.1.12 MT 362 Interest Rate Reset/Advice of Payment 10-36

iv
 10.1.13 MT 364 Single Currency Interest Rate Derivative Termination/ Recouponing
Confirmation 10-39
10.1.14 MT 365 Cross Currency Interest Rate Swap Termination/Recouponing
Confirmation 10-41
10.2 CoSecurities Markets 10-44
10.2.1 MT 517 Trade Confirmation Affirmation 10-44
10.2.2 MT 518 Market-Side Securities Trade Confirmation 10-45
10.2.3 MT 540 Receive Free 10-50
10.2.4 MT 541 Receive Against Payment 10-52
10.2.5 MT 542 Deliver Free 10-55
10.2.6 MT 543 Deliver Against Payment 10-58
10.2.7 MT 592 Request for Cancellation 10-61
10.2.8 MT 598 Proprietary Message 10-62
10.3 Treasury Markets - Metals 10-62
10.3.1 MT 643 Notice of Drawdown/Renewal 10-62
10.3.2 MT 644 Advice of Rate and Amount Fixing 10-64
10.3.3 MT 645 Notice of Fee Due 10-64
10.3.4 MT 646 Payment of Principal and/or of Interest 10-65

11 Processing of MX Messages as per ISO 20022

11.1 Generation of MX Type Messages 11-2
11.1.1 Maintenance Required in OBTR for MX Type camt.054 Generation 11-3
11.2 MX Message Notification to OBTR from OBPM 11-3
11.2.1 Maintenance Required in OBPM 11-3

Index

v
 Preface

Preface
This manual is designed to help you to quickly get acquainted with the Messaging
module of Oracle Banking Treasury Management.
• Audience
• Acronyms and Abbreviations
• Conventions
• List of Topics
• Related Resources
• Symbols and Icons

Audience
This guide is intended for Back Office Data Entry Clerk, Back Office Managers/
Officers, Product Managers, End of Day Operators, and Financial Controller users.

Acronyms and Abbreviations

The acronyms and abbreviations are listed in this below table:

Table 1 Acronyms and Abbreviations

Abbreviations or Definition
Acronyms
AEOD Automated End of Day
AIF Alternative Investment Fund
CLS Continuous Linked Settlement
CIF Customer Information Files
DV Derivatives
Dr Debit
EOFI End of Financial Input
EOD End of Day
FX Foreign Exchange
GL General Ledger
IRS Internal Revenue Service
ICCB Interest Commission Charge and Fee
LCY Local Currency

vi
 Preface

Table 1 (Cont.) Acronyms and Abbreviations

Abbreviations or Definition
Acronyms
LIBOR London Interbank Offered Rate
MM Money Market
OBTR Oracle Banking Treasury Management
OT Over the Counter Options
RFR Risk Free Rates

Conventions
The following text conventions are used in this document:

Table 2 Conventions and Meaning

Convention Meaning
boldface Boldface type indicates graphical user interface elements associated
with an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables for
which you supply particular values.
monospace Monospace type indicates commands within a paragraph, URLs, code
in examples, text that appears on the screen, or text that you enter.

List of Topics
This guide is organized as follows:

Topics Description
Overview of Messaging Explains the overview of the Messaging system.
System
Maintain Messaging Branch Explains the maintenance of the messaging branch preferences.
Preferences
Maintain Address for Explains the Maintenance of customer address details.
Customer
Maintain Advices Format Explains the advices format maintenance.
Process Outgoing Messages Explains the processing of outgoing message.
Retrieve an Incoming Explains the retrieving process of an incoming message.
Message
Define Free Format Explains how to define free format messages.
Messages
Make Query Explains how to make query.
Process SWIFT Messages Explains how to process SWIFT messages.

vii
 Preface

Related Resources
For more information, see these Oracle Banking Treasury Management resources:
• The Procedures User Manual
• The Products User Manual

Symbols and Icons

Table 3 Symbols

Icons Function
Exit

Add row

Delete row

Option List

viii
1
An Overview of the Message System
Introduction
The Messaging System module of Oracle Banking Treasury Management is designed to
handle outgoing and incoming messages. The module supports various types of media.
Besides standard media modes like Mail, Telex and SWIFT, other media types also can be
used which are supported by the Media Control System (MCS) installed at the node at which
the database of the branch is installed. Oracle Banking Treasury Management gives native
support for media like Mail, Telex, and SWIFT using EMS as the MCS.
While defining a product, specify the messages to be generated for the events occurs during
the lifecycle of contracts. During such events, the message will be automatically generated
and sent to the customer’s address through the specified media and in the format and
language that is maintained for the customer–message combination.
While entering the details of a contract, choose to generate or suppress the message. There
is an option to prioritize the urgency with which a SWIFT message should be generated.

Features Provided for Processing Outgoing Messages

In the case of outgoing messages, the module provides for the generation of messages using
formats that can be defined. Maintaining message formats ensure consistency across the
branches of the bank. The module provides a host of features to enter or authorize test words
and to interface with media control systems to generate the message.
Several customers addresses for a given media: With multi-branch setup, the customers
of the bank can operate their accounts from several locations. Based on the convenience of
the customers, send messages to locations of their choice. Oracle Banking Treasury
Management provides for the setting up of several addresses for a given customer-media
combination. In addition, associate a language with an address. All messages sent to the
address will be expressed in the language that is defined.
Free format messages: In the course of daily banking operations, it might required to
generate messages that are not automatically generated by the system or to communicate a
message that is very specific to a customer. It is possible to personalize a message by
defining a free format message and linking it to a customer-address combination. Whenever
the message is to be generated it will bear the personalized format that is defined.
MCS maintenance: The messages that are sent from and delivered to the bank are
transmitted and received from external sources to Oracle Banking Treasury Management.
These external sources are called Media Control Systems (MCS). In a distributed
environment, the database of a branch is located in a node or server. The MCS of the
messages is also installed in a node. Thus, while defining an MCS, specify the node in which
it is installed.

Features Provided for Processing of Incoming Messages

In case of incoming messages, set up various message queues and direct incoming
messages to them and also grant selective access to the queues to personnel at the bank
who are authorized to handle incoming messages.

1-1
 Chapter 1

Archival and Retrieval of Information

Archival is the process of storing old messages for future retrieval. While defining
messaging preferences for the branch, specify the number of days for which an
outgoing message should be kept in the Outgoing Message Browser. Messages will
be automatically archived after the number of days specified for the branch. Retrieve
the messages that have been archived at any time and process them just as any other
messages.

Set- up Messaging Preferences

Specify messaging preferences that will govern the workflow aspects of the messaging
system module at the branch. Specify the following preferences:
• The number of days for which outgoing messages should be kept in the Browser
for every branch
• Whether a testword is required for Telex messages
• The activities on a message that requires authorization
• The PDE (Possible Duplication Emission) Archival period
• The text for duplication check
• The Hold Mail text to be displayed
• The Swift Key arrangement values
• Whether Authorization is required for the actions like Cancel, Hold, Change Node,
Test Word. etc. on a generated message.

Message Notification Process

The messages that are sent from and delivered to your bank are transmitted and
received from sources that are external to Oracle Banking Treasury Management and
these external sources are called Media Control Systems (MCS).
In a distributed environment, the database of a branch is located in a node or server.
The MCS of the messages are also installed in a node. Thus, while defining an MCS
you need to also indicate the node in which it is installed.

Outgoing EMS Process

The Outgoing EMS Process is in two layers. The EMS process as part of jobs in FCJ
scheduler, polls the outgoing message table for generated and un-send messages.
The job then sends minimal data about the message to be handed off, to an internal
JMS queue. The EMS process as part of an MDB that listens on internal JMS queue
builds final message and sends to their intended destinations.
The ‘EMS out’ job is available as factory shipped.
The Outgoing EMS Process as part of jobs scheduler is as follows:
• Once the job is triggered, it polls outgoing messages table for generated and
unsent messages.
• Each message is then sent to an internal JMS queue.
• The job is then rescheduled to fire next time.
The Outgoing EMS Process in MDB is as follows:

1-2
 Chapter 1

• An MDB listens on the internal EMS outgoing queue and it builds the final message sent
to intended destinations.
• In case of any exception while processing, message is sent to a deferred queue.
The following diagram illustrates outgoing EMS process in scheduler.

Figure 1-1 Outgoing EMS process in scheduler

1-3
 Chapter 1

Figure 1-2 Outgoing EMS process in MDB

Incoming EMS Process

The Incoming EMS Process is in two layers. The EMS process as part of jobs in FCJ
scheduler, polls the pre configured folder for messages and sends the messages read,
to EMS internal queue. The EMS process as part of an MDB listening on internal JMS

1-4
 Chapter 1

queue, identifies the message from queue and calls the incoming messages service package
to process the message. The ‘EMS in’ job is available as factory shipped.
The Incoming EMS Process as part of jobs scheduler is as follows:
• Once the job is triggered, it polls for messages in a folder (Configured for incoming
messages).
• Each message is then sent to an internal JMS queue.
• The job is then rescheduled to fire next time.
The Incoming EMS Process in MDB is as follows: 
• An MDB that listens on the internal EMS incoming queue receives the message.
• The media details are identified and incoming message processing package is called to
process the message.
• In case of any exception while processing, message is sent to a deferred queue.
• In case of messages directly arriving to JMS queue instead of a folder; the same MDB is
configured to listen on specific queue.

1-5
 Chapter 1

Figure 1-3 Incoming EMS process in Job Scheduler

1-6
 Chapter 1

Figure 1-4 Incoming EMS process in MDB

1-7
2
Messaging Branch Preferences Maintenance
This topic provides an overview of maintaining messaging branch preferences.
The messaging preferences governs the workflow aspects of the Messaging System module.
Specify messaging preferences for the branch in the Messaging Branch Parameters
Maintenance screen. On this screen, specify following points:
• The number of days for which outgoing messages should be kept in the browser
• Whether a test word is required for telex messages
• The activities on a message that requires authorization
• The PDE Functional Validation/archive period
• The Text for hold mail and duplicate check

Note:
Specify preferences only for the branch from which the Oracle Banking Treasury
Management logged onto.

• Maintain Messaging Branch Parameters

This topic provides systematic instructions to maintain messaging branch parameters.
• Maintain Message Types
This topic provides systematic instructions to maintain message types.
• Maintain SWIFT Tag
This topic provides systematic instructions to maintain tag descriptions for SWIFT
messages.
• Process PDE Messages
This topic provides an overview of the PDE validations on SWIFT messages.

2.1 Maintain Messaging Branch Parameters

This topic provides systematic instructions to maintain messaging branch parameters.
Specify User ID and Password and login to Homescreen.
1. On Homescreen screen, type MSDTRPREF in the text box, and click next.
Treasury Messaging Branch Parameters Maintenance screen displays.

2-1
 Chapter 2
Maintain Messaging Branch Parameters

Figure 2-1 Treasury Messaging Branch Parameters Maintenance

2. To maintain preferences for a new branch, click the New button on the application
toolbar.
3. On Treasury Messaging Branch Parameters Maintenance screen, specify the
details.

Table 2-1 Treasury Messaging Branch Parameters Maintenance - Field

Description

Field Description
Branch Specify the branch for which the preferences are to be
maintained.
Message Archive Period Archival is the process of storing old messages for future
retrieval. Specify the number of days for which an outgoing
message should be kept in the Outgoing Message Browser. A
message will be automatically archived after the number of
days that are specified. The details of outgoing message that
has been archived can be un-archive through the Message
History Retrieval Summary screen. Then these un-archive
messages can be processed as any other outgoing message.

Note:
It is recommended to enter a value of 1 in this field.
In this case, only those messages that have been
triggered for the generation today will be displayed
in the Outgoing Message Browser.

2-2
 Chapter 2
Maintain Messaging Branch Parameters

Table 2-1 (Cont.) Treasury Messaging Branch Parameters Maintenance -

Field Description

Field Description
PDE Archive Period Specify the number of days for which messages should be
kept in the queue for PDE Possible Duplicate Emission)
identification. The system does not consider messages for
PDE identification post the PDE archive period maintained
here.

Note:
The PDE archive period should be less than or
equal to message archival days.

Text for Duplicate Every message is maintained in the Outgoing Browser as an

un-generated copy of the original. When the copy is
generated, it will contain along with the contents of the original
message, any additional text that is maintained in the Text for
Duplicate field.
Hold Mail Text All the mail advices generated for a customer for whom Add
Hold Mail Text is checked at the Customer Address
Maintenance would have the hold mail text maintained in this
field. This text will be displayed on top of the message.
Test Word check Specify whether a testword needs to be entered before a telex
message is generated from and received at the branch from
the following options.
• Yes
• No
PDE Functional Check this box to indicate that system should identify an
Validation outgoing message as PDE (Possible Duplicate Emission)
using the functional key or not. The PDE validation is done
either using the hash value of the SWIFT message or using
the tag/field value of the message. If this option is checked,
Oracle FLEXCUBE Universal Banking identifies duplicate
messages by performing PDE functional validations also. Hash
value-based validation shall be done irrespective of this option
being checked.

2-3
 Chapter 2
Maintain Messaging Branch Parameters

Table 2-1 (Cont.) Treasury Messaging Branch Parameters Maintenance -

Field Description

Field Description
SK Arrangement Select the action to be performed on the message based on
the Swift Key arrangement with the receiver from the following
options:
• Validate: On selecting this option, the system validates if
an SK arrangement exists between the bank and the
receiver. If yes, then the original SWIFT message is
generated otherwise, the message will go to repair
• Generate: On selecting this option, the system validates if
an SK arrangement exists between the bank and the
receiver. If yes, then the original SWIFT message is
generated otherwise, MT 999 (Free Format Messages)
will be generated instead of the SWIFT message.
• FFT No Validation: On selecting this option, the system
does not Validate but send the original SWIFT message
always.
Processing SWIFT Messages if an SK arrangement is
Validate in the static messaging table:
• This system checks for the value in the branch’s SK
Arrangement field.
• If the field value is No Validate, the system will generate
messages the normal way.
• If the SWIFT keys have been exchanged then the swift
message will be generated.
• If SWIFT keys have not been exchanged with the receiver
and the value of SK Arrangement for the branch is
Validate then the following messages will go to repair:
MT420, MT754 and MT756. For all other messages, the
original SWIFT message gets generated whether swift key
exists or not.
• If SWIFT keys have not been exchanged with the receiver
and the value of SK Arrangement for the branch is
Generate FFT then the message MT999 would be
generated instead of original SWIFT message.
Duplicate Advice Check this box to track the duplicate advices. When an advice
Tracking is duplicated or regenerated, the word Reprint appears over
the advice. Generation of MT999:
• The message header is changed from the original header
to MT999.
• That portion of the message after tag 21 will be prefixed
with tag 79 followed by the original SWIFT message.
• The message will be populated with the same contents as
the original SWIFT message with the respective SWIFT
tags.

2-4
 Chapter 2
Maintain Message Types

Table 2-1 (Cont.) Treasury Messaging Branch Parameters Maintenance -

Field Description

Field Description
Authorization Several activities can be performed on a message that is to be
generated from the branch. For example, From the outgoing or
incoming browser, The address to which a message should be
sent can be changed. In the Messaging Branch Parameters
Maintenance screen, specify the activities which are to be
performed on an incoming or outgoing message and would
require a subsequent manual authorization for the message. A
message on which activity to be performed would require
subsequent manual authorization for the activity to take effect.
A message on which an activity not selected on this screen is
performed, would be automatically authorized with the activity
taking effect. Activities:
• Cancel
• Hold
• Change NodeTest Word
• Auth Repair Incoming
• Carry Forward
• Change Media
• Regenerate
• Change Address
• Reinstate
• Release
• Branch Move
• Test Word Check
• Change Priority

4. After entering the mandatory entries, save the record.

This record should be authorized before the End of Day process (EOD) is run.
5. Click the Exit button to end the transaction.

2.2 Maintain Message Types

This topic provides systematic instructions to maintain message types.
1. On Homevpage, specify MSDTRMTM in the text box, and click Next.
Treasury Message Type Maintenance screen displays.

2-5
 Chapter 2
Maintain Message Types

Figure 2-2 Treasury Message Type Maintenance

2. On Treasury Message Type Maintenance screen, specify the details.

Table 2-2 Message Type Maintenance - Field Description

Field Description
Module Specify the module from the adjoining option list.
Message Type Specify the message type for which SWIFT codes can be
maintained.
Description Specify a brief description of the message type.
Priority Specify the priority in which a message is to be sent. Change
the priority, if required. To change the priority specified for a
message, click the button marked Change Priority.
Thereafter, select an option from the option list that is available
for this field.
• Normal
• Medium
• High
Maximum Message Specify the maximum message count.
Count
Purge Message Select whether to purge message from the drop-down list.
• Yes
• No
Acknowledgment Nak Select option from the drop-down list.
Processing • Yes
• No
SWIFT Message Type This field indicates the SWIFT message type in the free format
message. For example: The Message Type as
CUST_TRANSFER in IS module, the user needs to indicate
the message type as MT103.
Consolidated Message Select consolidated message type from the adjoining option
Type list.

2-6
 Chapter 2
Maintain SWIFT Tag

Table 2-2 (Cont.) Message Type Maintenance - Field Description

Field Description
Generate at input Check this box to indicate that this message is to be generated
at the time of input of the contract, and not after authorization.
Show In Product Check this box to indicate that this message will be available in
the product to be maintained against a particular event.

3. Click the Exit button to end the transaction.

2.3 Maintain SWIFT Tag

This topic provides systematic instructions to maintain tag descriptions for SWIFT messages.
1. On Home page, specify MSDTRSWT in the text box, and click Next.
Treasury Swift Tag Maintenance screen displays.

Figure 2-3 Treasury Swift Tag Maintenance

2. On Treasury Swift Tag Maintenance screen, specify the details.

Table 2-3 Treasury Swift Tag Maintenance - Field Description

Field Description
SWIFT Message/Sub Specify the swift message/sub message type from the adjoining list.
Message Type
Description The system displays the message description.
Envelope Message Type The system displays envelope message type based on the
message/sub-message type selected.
Tag Name The system displays the tag name.
Description The system displays the description.
Tag Option The system displays whether the tag is optional (O) or mandatory
(M).
Lines The system displays the number of lines required for the tag.
Sequence The system displays the tag sequence number.
Repeatable Check this box to indicate whether the tag is repeatable.

2-7
 Chapter 2
Process PDE Messages

Table 2-3 (Cont.) Treasury Swift Tag Maintenance - Field Description

Field Description
All Options The system displays all options.
Sequence Name Specify the sequence number
LBL_TAGCHARSET Specify the LBL_TAGCHARSET.

Note:
Swift message tag descriptions are factory shipped.

3. Click the Exit button to end the transaction.

2.4 Process PDE Messages

This topic provides an overview of the PDE validations on SWIFT messages.
The system detects the messages (Incoming/Outgoing) as PDE messages by
performing the validations. The Incoming and Outgoing PDE messages are processed
by the system in the following manners:

Incoming PDE Messages

In the case of incoming messages, EMS picks up the incoming messages and inserts
them into a data store. If the incoming message has a PDE trailer (message contains
the text PDE) then the system will mark the process status as Stopped due to PDE.
After due validations, release the message from the incoming PDE message queue.
Once these messages are accepted they will continue to get uploaded as a normal
messages. If the PDE trailer is not present in the incoming message, then the
message upload will continue as normal.
In the case of incoming messages with a PDE trailer, the PDE Flag check box in the
Incoming Message Browser screen will be checked.
For more details on the PDE indication of an incoming message in the Incoming
Message Browser, refer to topic Processing income message section.

Outgoing PDE Messages

In the case of outgoing messages, follow any of the following if the system detects a
message as a duplicate based on the PDE validations:
• Auto release the message with the PDE trailer
• Release the message without the PDE trailer
• Reject the message
The system displays an override when it finds a message to be a duplicate one. In this
case, the message is parked in the PDE queue and either does release the message
without the PDE trailer or with the PDE trailer. If the message is released with the PDE
trailer then the message is appended with PDE, else the message is released without
PDE. The messages can be rejected. In this case, the message status will be changed
to E(Exception) and this will not be picked up by EMS (Electronic Messaging
System).

2-8
 Chapter 2
Process PDE Messages

Due to message size restrictions, sometimes a single message is physically split into multiple
parts and each one is stored in a distinct record in the outgoing message data store. A
message is marked as PDE, if all the split messages are found to be duplicates.

Note:
All the messages in the PDE queue (Incoming and Outgoing) are completely
processed by EMS before initiating EOD operations.

2-9
3
Maintain Addresses for Customer
The messages and advices that are sent to the customers of the bank can be transmitted to
various addresses through the media types that are maintained on the Media Maintenance
screen. In the Account Address Maintenance screen, some of the details that can be
maintained are:
• The media through which messages to a customer should be transmitted
• The address(es) of a customer for each media type
• The answer-back code for a telex advice
• A Test Word for the customer
• The messages that should be sent to an address
• The language in which messages must be sent to a customer address
• Specifying the Delivery By as FILEFACT while maintaining the Customer Address
Information for MT102 Type of messages.
A customer of the bank can have several addresses for a given media. To distinguish
between one address and another for the same media, the user can capture an address for
every location.

Note:
The addresses that are maintained for a customer on the Account Address
Maintenance screen are in addition to the ones maintained in the Customer
Information File (CIF) of the Core module.

This topic contains the following sub-topics:

• Maintain Address at Customer (CIF) Level
This topic provides systematic instructions to maintain address at the customer level.
• View Customer Address
This topic provides systematic instructions to view the address details.

3.1 Maintain Address at Customer (CIF) Level

This topic provides systematic instructions to maintain address at the customer level.
1. On Homescreen, specify MSDTRCAD in the text box, and click Next.
Treasury Customer Address Maintenance screen displays.

3-1
 Chapter 3
Maintain Address at Customer (CIF) Level

Figure 3-1 Treasury Customer Address Maintenance

2. To maintain a new address for a customer, select New from the Actions menu, or
click the New icon on the toolbar.

Note:

• Oracle Banking Treasury Management generates a notification

message when a new customer address is created and authorized.
This notification message can be sent to any external system if
required.
• In the Group Code Restriction screen, the customer details whose
accounts are permitted for the query/modification can be modified.

Basic fields such as information such as Customer No, Location, Media, and
Address (line 1 to 4), and Any Message Type will be auto-populated from the
Customer Address Maintenance (MSDCUSAD) screen using the
TR_CUST_DATA_REPLICATE job
Customer replication process supports auto population of modified Customer
address maintenance details from FCUBS to OBTR.
The below list of fields can be modified in the Customer Address Maintenance
(MSDCUSAD) screen from FCUBS:
• Country
• Language
• Name

3-2
 Chapter 3
Maintain Address at Customer (CIF) Level

• Address Code
• Address 1
• Address 2
• Address 3
• Address 4
• 50F party Details
3. On Customer Address Maintenance screen, specify the details.

Table 3-1 Customer Address Maintenance - Field Description

Field Description
Customer Number Specify the customer (CIF) number, assigned to a customer in the
Customer Maintenance screen, before capturing the different
addresses of the customer. The name of the customer whose
address is automatically displayed on providing the customer’s
identifier.
Location A customer of the bank can have several addresses for the same
media. To differentiate between one address of a customer and
another for a given media, it is mandatory to specify a unique
location for each address. The location that is specified for an
address is used as a unique identifier for the customer address. A
single customer can have any number of accounts. Link a specific
location with an Account Number. Maintaining multiple locations for
the customer facilitates the sending of interest and account
statements to more than one address of the customer. If an address
is maintained at the Customer Account Definition level, all
statements pertaining to the particular account will be sent only to
the address specified at the account level, irrespective of the
message and location maintenance for the customer. Choose from
the available list and indicate the Account Number, which should be
linked with the respective address.

Note:
A customer address is allowed to link with an account
only for a specific branch which means that the branch
should be a valid branch code in the system.All option
indicates that the customer address and account linkage
is valid in all the branches of the bank, but this option can
not be exercised. This supports account statement
generation in ISO 20022 format for cash management.

Country Select the relevant country code where the customer resides. All
countries maintained through the Country Code Maintenance
screen is made available here.
Answerback Specify the answerback code for the customer. This field is
applicable only if a message is transmitted through Telex. It cannot
be more than 20 characters in length. It is a free format text.

3-3
 Chapter 3
Maintain Address at Customer (CIF) Level

Table 3-1 (Cont.) Customer Address Maintenance - Field Description

Field Description
Add Hold Mail Text If this option is checked, then all the mail advice generated for this
customer and location would have the hold mail text displayed on
top of the message. As a consequence, these mail advices would
not be dispatched to the customer unless required. Check this box
to display the hold mail text on top of the message indicating the
branch.
Media The types of media for which wants to capture addresses include
Mail, E-Mail, Telex, SWIFT, FINPLUS, FAX and FILEACT interface
to TIPA network. The Media details maintained in the Media
Maintenance screen will appear in the list of values.

Note:
If media is maintained as FINPLUS, and the message
type DEBIT_ADVICE and CREDIT_ADVICE are mapped,
system supports generation of MX message Camt.054
debit/credit notification as per ISO 20022 standard which
is the equivalent for SWIFT MT900 (Confirmation of
Debit), and SWIFT MT910 (Confirmation of Credit).

Language Specify the language code in which the messages sent to the
address should be expressed. The language code specified here is
taken as the default language in which all messages will be sent to
the addresses.

Note:
To send a message to a customer in a particular
language, maintain a message format for the chosen
language through the Advice Format Maintenance
screen.

Test Keyword Enter the test word allotted to a customer. This field is applicable
only if the message is transmitted through the media Telex.
Delivery By Select how statements sent to the customer by mail should be
delivered from the adjoining option list. All the values maintained
through the Message Location Maintenance screen will be
displayed in the option list.
Send by Email If the customer has an e-mail address, capture it by clicking on the
box adjacent to the Send by Email option. Enter the E-mail address
for the customer, media and location combination in the first
Address field. Capture addresses such as fax, mail, etc., for the
combination in the remaining address fields, if required.
Sanction Check Status The system displays the status of the sanction check request.
• Not Required
• Pending
• Approved
• Rejected
Name Specify the name of the customer.

3-4
 Chapter 3
Maintain Address at Customer (CIF) Level

Table 3-1 (Cont.) Customer Address Maintenance - Field Description

Field Description
Address Code Select the address code from the adjoining address code option list.
Address 1, Address 2, Enter the detailed address to which generated messages and
Address 3 and Address 4 advices to be sent, for a particular customer account under the
selected media and location combination. The format of the address
depends on the media through which the message is transmitted. If
the address is for the media type Mail, enter the customer's address
in the four rows under this field. Each line can contain a maximum
of 35 characters. If the media of transmission is Telex, the address
should be expressed numerically. For a SWIFT address, the
address should be of eight or eleven characters alphanumeric.

Note:
The valid address (Mail or Telex or SWIFT) must be
entered in the first line of the Address field only.

3-5
 Chapter 3
Maintain Address at Customer (CIF) Level

Table 3-1 (Cont.) Customer Address Maintenance - Field Description

Field Description
50F Party Details Specify the party details related to the ordering customer as a 5-line
input here. Line 1 indicates the party identifier, and Line 2 to Line 5
indicates the name and address details of the party. Use either of
the following line formats with option F:
• Line 1 (Party Identifier) /34x (Account)
• Line 2 to Line 5 (Name & Address) 1!n/33x (Number)(Details)
Or
• Line 1 (Party Identifier) 4!a/2!a/27x4!a/30x (Code)(Country
Code)( Identifier)
• Line 2 to Line 5 (Name & Address) 1!n/33x (Number)(Details)
The details specified here are used for a stricter validation of the
details related to the ordering customer. The validations are carried
out according to the rules indicated below:
a. Validations for Line 1, party identifier (applicable for the second
format listed above)
• Line 1 has to comply with (Code)(Country Code)(Identifier)
format where the country code should be a valid ISO
country code.
• The first 4 characters specified should be a valid party
identifier code supported by SWIFT.
b. Validations for Line 2 to Line 5, Name and Address details of
the party:
• The first line must start with number 1.
• Line numbers must appear in numerical order.
• Line number 2 cannot be used without line number 3 and
vice versa.
• Line number 4 cannot be used without line number 5 and
vice versa.
• Line number 4 should have the format YYYYMMDD and
this date must not be greater than the date on which the
message was sent to SWIFT.
• Line numbers 3, 5, 6, and 7 should be followed by a valid
ISO country code.
• Line numbers 3, 4, 5, 6, 7, and 8 should not repeat. Line
numbers 1 and 2 can repeat.
• Line 8 is used as additional information. When the account
identifier format is used, then in the case of Line 8 being
used, either Line 6 or Line 7 should be used. When the
party code identifier format is used, then Line 8 can be the
continuation of Line 1, Line 6, or Line 7. Line 6 or 7 need
not be mandatorily be used.
During contract input, the ordering customer record is searched in
the customer addresses maintained, and if found the corresponding
50F details are defaulted to the contract. If not found, the address
details default from customer maintenance. These validations are
carried out for the following outgoing message types and
appropriate error messages are displayed incase of any
mismatches.
• MT101
• MT102
• MT102+
• MT103
• MT103+

3-6
 Chapter 3
Maintain Address at Customer (CIF) Level

Table 3-1 (Cont.) Customer Address Maintenance - Field Description

Field Description
• MT210
• MT910

Specifying Message Address: For a customer address - message type combination,

specify the branch from which the message can be sent to the address. With Oracle
FLEXCUBE Universal Banking , the customers have the facility to effect a transaction
from any of the branches of the bank.

Note:
The All option indicates that the message can be sent to the address in the
defined format from all the branches of the bank.

Table 3-2 Message Address - Field Description

Field Description
Message Type Specify the message type from the adjoining option list. A message
type is always associated with a module.

Note:
The option All indicates that all messages for the
customer should be sent to the address being defined.

Module Specify the module from the adjoining option list.

Branch Specify the branch code from the adjoining option list.
Number of Copies Specify the number of copies of the message that must be sent to
the location each time it is generated. The number specified here is
taken as the default number of copies of the message that will be
generated each time a message is sent to this location through the
media. To send more than one copy to a location, the first message
will be the original and the others will be marked as Copy.

Note:
For payment messages, Oracle Banking Treasury
Management defaults to 1 which indicates that only one
payment message to be generated and there is no option
to change it.

3-7
 Chapter 3
Maintain Address at Customer (CIF) Level

Table 3-2 (Cont.) Message Address - Field Description

Field Description
Format Specify the format in which a message should be sent to a
customer’s address. The default format for a message type needs
to be defined through the Advice Format Maintenance screen.
Use the default format defined for the message type or define
another format for the message. If this field is left blank, the default
format specified for a message type in the Advice Format
Maintenance screen will be used. However, to personalize a
message to make it specific to a customer, specify the code of the
format that should be used for the advice - customer combination.

Note:
The special format should first be defined in the advice
format screen before it can be associated the customer
address.

Account Number Specify the account number from the adjoining option list.
Primary Address When defining addresses for a message type,check this box to
define the primary address.
Confirmation Matching Check this box to automatically match the MM and FX confirmation
messages. The confirmation messages are matched based on the
confirmation rule maintained. Auto matching of confirmation
messages is enabled only if the Confirmation Matching is checked
for the combination of customer, branch, message type, module,
location, and media.

Note:
If addresses at both the customer account level and the
customer (CIF) level are maintained, then the system
picks up the maintenance done at the customer account
level to generate messages and advices. However, if the
addresses at an account level are not maintained, then
the system picks up the maintenance done at the
customer (CIF) level to generate messages and advices.

Note:
The notification message is generated when a new customer address is
created and authorized. This notification message can be sent to any
external system if required.

3-8
 Chapter 3
Maintain Address at Customer (CIF) Level

Change Log
This subtopic provides detailed information on customer addresses.
The View screen displays the customer’s previous addresses, the number of changes made
to the address till the date, who has made the changes, when the changes are made, and
whether the change has been authorized or not.
1. On Treasruy Customer Address Maintenance screen, click the Change Log button.
View screen displays.

Figure 3-2 View

This screen displays the following details:

• Modification Number
• Modification Status
• First Authorization Status
• Authorization Status
• Maker ID
• Maker Date Stamp
• First Checker Id
• First Checker Date

3-9
 Chapter 3
View Customer Address

• Checker ID
• Checker Date Stamp
• View Changes
• Maker Remarks
• Maker Override Remarks
• First Checker Remarks
• Checker Remarks
• Warning Code
• Warning Description
• Field Name
• Old Value
• New Value
2. To view the changes made on a particular date, double-click the View Changes
button corresponding to the required date under the Maker Date Stamp.
A detailed screen appears containing changes made on the given date.
3. Click the Exit button to end the transaction.

3.2 View Customer Address

This topic provides systematic instructions to view the address details.
1. On Home page, specify MSSTRCAD in the text box, and click Next.
Treasury Customer Address Summary screen displays.

Figure 3-3 Treasury Customer Address Summary

2. On Treasury Customer Address Summary screen, specify the details.

3-10
 Chapter 3
View Customer Address

Table 3-3 Customer Address Summary - Field Description

Field Description
Customer Number Specify the customer number from the adjoining option list.
Authorization Status Select the authorization status from the drop-down list.
• Authorized
• Unauthorized
• Rejected
Location Specify the location from the adjoining option list.
Record Status Select the record status from the drop-down list.
• Open
• Closed
Media Specify the media from the adjoining option list.

Note:
In the Group Code Restriction screen, modify the customer details whose
accounts are permitted for the query/modification.

3. Select any or all of the above parameters for a query and click the Search button.
The records meeting the selected criteria are displayed. The system displays the
following details:
• Customer Number
• Authorization Status
• Location
• Record Status
• Media
4. Click the Exit button to end the transaction.

3-11
4
Maintain Advice Formats
This topic provides an overview of the Advices and its formats.
The advices that are generated from the bank will have a definite format. In the Advice
Format Maintenance screen, the user can specify formats and indicate the messages and
advices that should use the formats that are defined.
By maintaining message formats, the user can ensure consistency across the branches of
the bank. The user can maintain advice formats either by:
• Using the format editor on the screen to enter the format, or
• Importing the format from an ASCII file which can be located either on the Server or
Client

Note:
Message formats are maintained at the bank level and will apply to all the branches
of the bank.

Automatic Printing of Advices Generated during EOD Processing

In addition to the generation of advices, Oracle FLEXCUBE Universal Banking automatically
prints the advices that are scheduled to be generated during End Of Day (EOD) processing.
Account Statements, Loan statements are examples of advices that is scheduled to be
generated during EOD processing. This section contains the following topics:
1. Start the Background Process
2. Printing of Advices
In Oracle FLEXCUBE Universal Banking , the advices are generated during batch
processing. On starting the background process, the system will search for the messages
that are not generated. The advices may be of two kinds:
• The Advices that are not generated during contract authorization (If the message
generation at the time of contract authorization is not opted.)
• The Advices that are scheduled to be generated during End of Day operations.
• As soon as the message is generated, the system will check whether the advice was
scheduled to get generated during EOD. If so, the advice will be sent for spooling
and printing.
If the advice is not scheduled to be generated during EOD, the system will move on to
generate the next advice without printing the advice.
• Maintain Advice Format Details
This topic provides systematic instructions to maintain Advice format details.
• Start the Background Process
This topic provides systematic instructions to start the background process for generating
and printing advices.

4-1
 Chapter 4
Maintain Advice Format Details

4.1 Maintain Advice Format Details

This topic provides systematic instructions to maintain Advice format details.
1. On Home page, specify MSDTRAFM in the text box, and click Next.
Treasury Advice Format Maintenance screen displays.

Figure 4-1 Treasury Advice Format Maintenance

2. On Treasury Advice Format Maintenance screen, specify the details.

Table 4-1 Treasury Advice Format Maintenance - Field Description

Field Description
Format Specify the format code. Each format is identified by a fifteen-
character code called a Format code. The code that is
assigned to a format should be unique as it is used to identify
the format. Compare simple conditions while defining message
formats. The details of the format will automatically become
applicable to the message, after the code is assigned to a
format. This code indicates the following details:
• The number of lines that should be contained on a page
when the advice is printed.
• The number of columns that should be contained on a
page when the advice is printed.
• The language of the message.
• The form type is attached to the format.

4-2
 Chapter 4
Maintain Advice Format Details

Table 4-1 (Cont.) Treasury Advice Format Maintenance - Field Description

Field Description
Language A message can be sent to a customer in different languages.
To make this possible, maintain a format in different
languages. While maintaining addresses for a customer in the
Customer Address Maintenance screen, specify the format
and language in which a message to be sent.

Note:

Format Type Specify the form type that applies to the message from the
adjoining option-list.
Lines This field displays the number of lines that should be
contained on a page when the message is printed.
Columns This field displays the number of columns that should be
contained on a page when the message is printed.
Import File Specify the full path to the file on the server which contains the
format to be imported.
Import Click Import button to import the ASCII file format. The file
containing the format of the message will be displayed on the
screen.
Format Text Specify the text in the text box.
Module Specify the module from the adjoining option list.
Message Type Specify the message type from the adjoining option list.
Media Specify the media from the adjoining option list.
Branch Specify the branch code from the adjoining option list.
Currency Select the currency code from the adjoining option list.
Product Specify the product code from the adjoining option list.

Entering an advice format using the format editor: To enter a format using the format
editor, click the free format text icon positioned next to the text of the message. In the
notepad, the user can tailor an advice to suit the requirements. Keywords to format the
advice (similar to the Advice Format Maintenance screen) can be used here too to get
the desired format. The following table contains a comprehensive list of the keywords that
can be used in the format editor.

Table 4-2 Keywords

Keyword Significance
#RH Indicates the start of the report header section
#PH Indicates the beginning of the header for a page
#EH Indicates both the end of the header section of the report or the end
header of a page
#RF Indicates the start of the report footer section
#PF Indicates the start of the footer of a page
#EF Indicates both the end of the footer of a report or page
#B Indicates the start of the body of the message

4-3
 Chapter 4
Start the Background Process

Table 4-2 (Cont.) Keywords

Keyword Significance
#EB Indicates the end of the body of the message
#CL Indicates that you can collapse a line
#EC Indicates the end of a line that you have collapsed
#LOOP Indicates the beginning of a loop
#ENDLOOP Indicates the end of a loop
#IF Indicates a conditional section
#ANDIF Indicates a conditional section
#ORIF Indicates a conditional section
#ENDIF Indicates the end of a conditional

After defining a format and assigning it a code, specify the list of messages that
should use the format. The format that is defined for a message in this screen is
taken to be the default format that will be used whenever the message is
generated from the bank.

Note:
For all the five combinations, use option ALL which indicates that the
format is applicable for records in that category.

3. After specifying the mandatory entries, save the record.

An advice format maintenance record that is defined should be authorized by a
user bearing a different login Id, before the End of Day (EOD) process begins.
4. Click the Exit button to end the transaction.

4.2 Start the Background Process

This topic provides systematic instructions to start the background process for
generating and printing advices.
The user needs to run the background process to generate and print advices. In
addition to the generation of the advices, the system prints the advices that are
scheduled to be generated during EOD processing. The user can start or stop a
process in the Jobs Details screen.
1. On Homescreen, specify SMSJBBRW in the text box, and click Next.
Jobs Details screen displays.

4-4
 Chapter 4
Start the Background Process

Figure 4-2 Jobs Details

2. On Job Details screen, specify the details.

Table 4-3 Jobs Details - Field Description

Field Description
Job Module Select the job module from the drop-down list.
Status Select the status from the drop-down list.
• Stopped
• Running
• Halted
Process Specify the process.

3. Select any or all of the above parameters for a query and click Search button.
The records meeting the selected criteria are displayed as follows:
• Job Module
• Process
• Process Sequence Number
• Status
4. Check the required process in the search results table and click Start button to start the
process.
5. Click Stop button to stop the process, at any point.
6. Click the Exit button to end the transaction.

4-5
5
Process Outgoing Messages
This topic provides an overview of the process of generating an outgoing message.
In each module, while defining products indicate the messages that should be associated
with an event in the life cycle of a contract involving the product. A contract goes through
several events during its life cycle. A message for an event is triggered for a generation when
the event is authorized. For example, While defining a product to cater to short-term loans,
the following messages should be generated when events take place:

Table 5-1 Messages for Short-term Loans Product

Event Message
INITIATION Initiation Advice
LIQUIDATION Liquidation Advice

To initiate a short-term loan involving the product an Initiation Advice will be triggered for a
generation. Similarly, To make a repayment on the loan, the liquidation advice defined for the
event will be triggered for a generation.

Note:
In this context advices and messages are commonly referred to as messages.

Depending on the product - message - customer details, the address and the media through
which the message should be transmitted. If a message is to be transmitted through Mail, it
has to be printed. If the message is to be transmitted through Telex, enter the testword (if it is
required for the message). The messages that are to be transmitted through media like Telex
and SWIFT will be sent by the Media Control System (MCS) which is connected to the node
in which the database of branch is installed. A message that is triggered for generation can
be sent in the background or can be generated on-line. An outgoing message will be
processed based on the preference that are set.

Note:
The messages that are triggered by an automatic event will be put in the Outgoing
Browser by the automatic function itself. This is because events triggered by an
automatic function do not require authorization.

This topic contains the following sub-topics:

• Generate Messages from Outgoing Browser
This topic provides systematic instructions for generating messages from an outgoing
browser.

5-1
 Chapter 5
Generate Messages from Outgoing Browser

5.1 Generate Messages from Outgoing Browser

This topic provides systematic instructions for generating messages from an outgoing
browser.
If the background message process is not running, in that case, all the messages
triggered for the generation are displayed in the Outgoing Message Browser, where
the message can be generated at any time in the day.
1. On Homescreen, specify MSSTROBR in the text box, and click Next.
Treasury Outgoing Message Browser Summary screen displays.

Figure 5-1 Treasury Outgoing Message Browser Summary

2. On Treasury Outgoing Message Browser Summary screen, specify the details.

Table 5-2 Outgoing Message Browser Summary - Field Description

Field Description
Branch Specify the branch code.
Module Specify the module code.
Media Specify the media.
Hold/Release Status Select the appropriate status from the drop-down list.
• Hold
• Released
• Carry Forward
Delivered Status Select the appropriate status from the drop-down list.
• Delivered
• Non Delivered

5-2
 Chapter 5
Generate Messages from Outgoing Browser

Table 5-2 (Cont.) Outgoing Message Browser Summary - Field Description

Field Description
Bulk Status Specify the bulk status from the following options:
• INPROGRESS: This option indicates that the bulking is
identified for the DCN.
• BULK_SUCC: This option indicates that the bulking
operation is successfully completed.
• BULK_FAIL: This option indicates that the bulking
operation is failed.
• FILESENT_SUCC: This option indicates that the bulked
file is sent to the destination.
• FILESENT_FAIL: This option indicates that the bulked file
was not sent as sending failed.
User Reference Number Specify user reference number.
Document Number Specify document number.
Message Type Specify Message type.
SWIFT Message Type Specify SWIFT Message type.
Acknowledgment Select the acknowledgment status from the drop-down list.
Status • Pending
• Accepted
• Rejected
• Not Required
Bulk Reference Number Specify bulk reference number.
Destination Type Specify destination type.
Value Date Select value date from the Calendar icon.
Reference Number Specify reference number.
Receiver Specify receiver.
Message Status Select message type from the drop-down list.
• Cancelled
• Reinstated
• Repair
• Sent Ungenerated
• Generated
• Handoff
• Processed
• Confirmation Pending
• External - Ungenerated Bulk
Authorization Status Select authorization status from the drop-down list.
• Authorized
• Unauthorized
Bulk Preference Name Specify bulk preference name.
SWIFT LAU Specify the SWIFT LAU details.

3. Click the Search button.

The system identifies all outgoing messages satisfying the specified criteria and displays
the following details for each outgoing message:
• Branch
• Document Number
• Reference Number

5-3
 Chapter 5
Generate Messages from Outgoing Browser

• Module
• Message Type
• Sub Message Type
• Receiver
• Currency
• Amount
• Media
• SWIFT Message Type
• SWIFT Sub Message Type
• Node
• Priority
• Name
• Address
• Address 2
• Address 3
• Address 4
• Location
• Message Status
• Testword
• Exception
• Running Number
• Hold/Release Status
• Test Amount
• Test Date
• Test Currency
• Test Word Narrative
• Acknowledgement Status
• Hold Mail
• External Reference
• Delivery By
• RTGS Network
• Entry By
• Maker Date Stamp
• Authorized By
• Checker Date Stamp
• Authorization Status
• Once Authorized

5-4
 Chapter 5
Generate Messages from Outgoing Browser

• Modification Number
• DCN List
• Bulk
• Selected
• Testing Status
• Any or Original
• Original DCN
• Delivered Status
• From Date
• To Date
• Bulk Reference Number
• Bulk Preference Name
• Bulk Status
• File Type
• SWIFT Net Connectivity
• Folder Name
• Queue Name
• Destination Type
• SWIFT LAU
• User Reference Number
• Value Date
RTGS Network defaults the following message types:
• CUST_TSFR_RTGS
• BANK_TSFR_RTGS
• DIRDR_RTGS

Table 5-3 RTGS Message Type and Description

Message Description SWIFT Message

CUST_TSFR_RTGS Used when a Pay message MT 103
generation is for a corporate and
sent through the RTGS Network.
BANK_TSFR_RTGS Used when a message belongs MT 202
to an interbank deal and sent
through the RTGS Network.
DIRDR_RTGS Used when a direct debit MT 204
message is sent through the
RTGS Network.

5-5
 Chapter 5
Generate Messages from Outgoing Browser

Note:

• If none of the criteria is selected, then the system displays all the
messages in the outgoing browser.
• Funding Status will be updated during the processing of incoming
MT102 and MT109.

4. Check the box against the message(s) for which needs to perform an operation
and then click the corresponding operation.
The operations that can be performed on an outgoing message are determined by
the rights that are assigned with at Security Management System (SMS) level. If a
function in the Outgoing Browser is disabled, then the function is not allowed for
the record. The action performed will require authorization, if maintained at the
Messaging Branch Preferences level. The system allows only Print, View and
Detail actions for messages generated by External Payment system. The
following operations can be performed on the outgoing messages:

Table 5-4 Operations

Operation Description
Generate Click this button to generate an outgoing message.
Ungenerated and repaired messages can be
generated. On clicking the Generate button, the
system checks the contract status for which the
message is generated and will not generate a
message in the following condition:
• If the contract is reversed
• If the message is on hold
• If the message maintenance is not authorized
and the message is moved to repair queue
Hold Click this button to temporarily stop generating an
outgoing message. Authorizing Supervisor can
view details and then release the messages or
change their status to Carry Forward which in turn
can be released on further authorization.

Note:
Messages with Hold status must either
be carried forward or released before
executing the EOD processes at the
branch; else the system displays an
error message. However, if the
message is canceled, then the system
will not display an error message,
though the status is Hold.

Cancel Click this button to cancel an outgoing message.

The messages with Ungenerated and Hold status
can be canceled.

5-6
 Chapter 5
Generate Messages from Outgoing Browser

Table 5-4 (Cont.) Operations

Operation Description
TW Input Click this button to input testword for Telex
messages which were moved to Repair status.
Change Node Click this button to change the node from which an
outgoing message is generated. In a distributed
environment, the database of one or more
branches of the bank is located at a node or a
server. Hence a Media Control System is installed
and defined specifying the node at which it is
installed. On clicking the Node, the system
displays the details of the individual message
providing an option to change the Node. Select the
node to be changed from the adjoining option list.

Note:
MCS status at the node in which the
database of the bank is installed should
be passive.

Change Address Click this button to change the address to which an

outgoing message has to be sent. Enter the new
address to which the message should be sent and
click OK to save.

Note:
Change of address can be done only
before a message is generated.

Print/Spool Click this button to print an outgoing message. On

clicking the Print button, the option will be
provided to select spool or print online. Messages
that are transmitted through the mail and those
canceled should be printed. The details of
messages transmitted through other media types
can also be printed. The system provides an
option to spool the advice in PDF format. On
clicking the Print/ Spool button, the selected
advice in PDF file is displayed along with SWIFT
tag description.
Undo Click this button to reverse the last action
performed on an outgoing message at the
Outgoing Message Browser Summary level.

5-7
 Chapter 5
Generate Messages from Outgoing Browser

Table 5-4 (Cont.) Operations

Operation Description
Change Priority Click this button to change the priority for sending
a payment message which is yet to be generated.

Note:
In the Background, messages
generated on a priority basis.

Resend Click this button to regenerate and resend a

message which was generated and sent.
Release Click this button to release a message which is on
hold.
Reinstate Click this button to reinstate canceled outgoing
messages.
TW Auth Click this button to authorize testword entered for a
Telex message if the rights to authorize are
provided. While authorizing, reenter the testword.
Change Media Click this button to change the media through
which a message is transmitted before it is
generated. Media of transmission of a message is
changed if there is a failure of the medium at the
recipient’s end.

Note:
The selected media through which a
message is transmitted should be
available to the recipient.

Change Branch Click this button to send an outgoing message

from another branch. Select the branch to which
the message needs to be moved from the
adjoining option list. Change the branch of a
message for the following reasons:
• If there is a failure of a medium at the bank’s
or the counterparty’s end.
• If the branch is located closer to the location
of the customer’s address.
View Click this option to view the contents of a
generated outgoing message. Viewing multiple
messages is not supported.
Authorize Click this option to authorize if there are
authorization rights for an operation at the
Messaging Branch Preferences level. Messages
should be authorized before sending.
Handoff Click this button to hand off a generated message
to MCS to save the date in an ASCII format.

5-8
 Chapter 5
Generate Messages from Outgoing Browser

Table 5-4 (Cont.) Operations

Operation Description
Details Click this option to view the details of a generated
outgoing message. Viewing details of multiple
messages is not supported.
On-Line Auth Click this option to authorize online, if there are
online authorization rights for an operation at the
Messaging Branch Preferences level. Messages
should be authorized before sending.
Copy Click this button to send a copy of an outgoing
message to another customer involved in a
contract. Specify the following details:
a. Any: Select this option to implement the
following changes:
• Media
• Name of the recipient
• Location of the recipient
• Address of the recipient
b. Original: Select this option to copy the
message in the original form.

Carry Forward Click this button to carry forward an outgoing

message which is on Hold for subsequent days.

Note:
Messages which have been Carried
Forward can be put back on Hold.

5. Click the Exit button to end the transaction.

5-9
6
Retrieve an Archived Message
This topic provides an overview of the process to retrieve an archived message.
Archival is the process of storing old messages for future retrieval. To recall, while defining
messaging preferences for the branch, the user must specify the number of days for which an
outgoing message should be kept in the Outgoing Message Browser. A message will be
automatically archived after the number of days that are specified in the Messaging Branch
Parameters Maintenance screen. The user can choose to retrieve the outgoing messages
that have been archived by invoking the Message History Retrieval Summary screen.
This sections contains the following topics:
• Process Message History Retrieval Summary
This topic provides systematic instructions to process Treasury Message History
Retrieval summary.
• Process Message
This topic provides systematic instructions to process and view Message screen.

6.1 Process Message History Retrieval Summary

This topic provides systematic instructions to process Treasury Message History Retrieval
summary.
1. On Home page, specify MSSTRUAR in the text box, and click Next.
Treasury Message History Retrieval Summary screen displays.

Figure 6-1 Treasury Message History Retrieval Summary

2. On Treasury Message History Retrieval Summary screen, specify the details.

6-1
 Chapter 6
Process Message

Table 6-1 Message History Retrieval Summary - Field Description

Field Description
Module Specify module number from the option list.
Message Type Specify the type of the message from the option list.
Receiver Specify receiver.
Reference Number Specify reference number from the option list..
Media Specify media from the option list.
Date Select date by clicking the Calendar icon.

3. Select any or all of the above parameters for a query and click the Search button.
The records meeting the selected criteria are displayed:
• Document Number
• Module
• Reference Number
• Message Type
• Media
• Receiver
• Date
4. Click the Exit button to end the transaction.

6.2 Process Message

This topic provides systematic instructions to process and view Message screen.
1. On Homescreen, specify MSDTRVMS in the text box, and click Next.
Treasury Message screen displays.

Figure 6-2 Treasury Message

6-2
 Chapter 6
Process Message

2. On Treasury Message screen, specify the details.

For more information on fields, refer to the below field description table.

Table 6-2 Treasury Message - Field Description

Field Description
Reference Number The system displays the reference number.
DCN Specify the DCN.
Event Sequence Number The system displays the event sequence number.
or Version Number
Receiver or Sender The system displays the receiver or sender identification details.
Message Type The system displays the Message type.
SWIFT Message Type The system displays the SWIFT Message type.
Sub Message Type The system displays the Sub Message type.
SWIFT Sub Message Type The system displays the SWIFT Sub Message type.
SWIFT MX Type The system displays the MX equivalent of SWIFT MT message.

The system displays the following details:

• Message
• Remarks
• Reject Reason
• Message Trailers
3. Click the Exit button to end the transaction.

6-3
7
Process Incoming Messages
This topic provides an overview of the process of generating an incoming message.
The Message Media Control Maintenance screen displays the Media Control Systems that
are connected to the node in which the database of the branch is installed, the media that the
Media Control Systems should handle, and the hand-off directory into which all incoming
messages transmitted through a specific media should be stored. The final destination of an
incoming message is the end user queue. These queues represent departments responsible
for acting on the received messages.
This topic contains the following sub-topics:
• Incoming Messages
This topic provides an overview of the Incoming messages.

7.1 Incoming Messages

This topic provides an overview of the Incoming messages.

Background Processing of Incoming Messages

All incoming messages that are intended for the bank will be handled based on the MCS
specifications that are maintained for the branch. An incoming messages can be received in
the ASCII format from an MCS, and manually direct them to the appropriate queues, or
indicate that the background process should automatically pickup incoming messages from
an MCS and transfer them to the appropriate queues.
To process incoming messages for the branch in the background, the messages will be
routed to the relevant queues as and when they come in without manual intervention.
Configure the background process to begin when the Beginning of Day process is run or
process it at any time in the day. This screen (Job Browser/Job Monitor screen) can also be
used to check whether the background process is running for outgoing and incoming
messages.
Messages that are transmitted by mail will have to be handled manually. Messages
transmitted through media like Telex and SWIFT will be automatically routed to the relevant
queues. A unique reference number (DCN) is assigned to each incoming message. Incoming
messages, which have an error, will be moved to the error queue.

Manual Processing of Incoming Messages

Process incoming messages manually if the background message process is not running to
route messages that cannot be routed to a user queue automatically.
If the background process is not running, the messages that have come in to the bank will be
stored in the incoming directory located on the node at which the database of the branch is
installed. This directory is specified in the Message Media Control Maintenance screen. On
processing the Incoming Message Browser, upload all the messages from the directory on
the node. All the incoming messages will be displayed in the incoming browser.

7-1
 Chapter 7
Incoming Messages

Maintain Incoming Message Browser Screen

Refer to the topic View Incoming Message Browser Summary for the detailed
information.
• View Incoming Message Browser Summary
This topic provides systematic instructions to view incoming message browser
summary.
• View Details of Incoming Message
This topic provides systematic instruction to view details of incoming message.
• Edit Incoming Message
This topic provides systematic instructions to edit an incoming message.

7.1.1 View Incoming Message Browser Summary

This topic provides systematic instructions to view incoming message browser
summary.
The Treasury Incoming Message Browser Summary screen receives the messages
that have come in through the MCS connected to the node in which the database of
the branch is installed.
1. On Homescreen, specify MSSTRIBR in the text box, and click Next.
Treasury Incoming Message Browser Summary screen displays.

Figure 7-1 Treasury Incoming Message Browser Summary

2. On Treasury Incoming Message Browser Summary screen, specify the details.

Table 7-1 Treasury Incoming Message Browser Summary - Field

Description

Field Description
Branch Specify the branch code.
Reference Number Specify the reference number.

7-2
 Chapter 7
Incoming Messages

Table 7-1 (Cont.) Treasury Incoming Message Browser Summary - Field

Description

Field Description
Media Specify the media through which the message was
transmitted.
SWIFT Sub Message Specify the SWIFT sub message type.
Type
Authorized Select the authorization status from the drop-down list.
• Authorized
• Unauthorized
Suppress Message Select the message suppression option from the drop-down
list.
• Suppress Msg Generation
• No Suppress
• Suppress Full
Queue Specify the queue.
Document Number The Document Number (DCN) is the delivery control number
used to identify the message. It is a 10-digit number prefixed
with a letter of the English alphabet. The DCN is constructed
as follows:
• 1-2 Characters: Last two digits of the current year
• 3-5 Characters: Day of the year (Julian Date)
• 6-10 Characters: Sequential number starting from 00001
each day
Sender Specify the name, address and location of the sender of the
message.
SWIFT Message Type Specify the SWIFT message type.
Testword For a message that was transmitted through Telex, specify the
testword. Telex messages that come into the bank needs to be
checked for validity if it is specified in the Messaging Branch
Parameters Maintenance screen. This is done by entering a
testword which depends on the testword arrangement with the
counterparty, the important aspects of the message like
customer, date and currency. If the testword entered does not
match the Telex testword the message is registered as a
defective message and put into the repair status.

7-3
 Chapter 7
Incoming Messages

Table 7-1 (Cont.) Treasury Incoming Message Browser Summary - Field

Description

Field Description
Status Select the record status from the drop-down list.
• Unprocessed
• Processed
• Repair
• Suppressed
• Funding Exception
• Pending Cover Match
• Failed Verification
• Pending Authorization
• Pending Liquidation
If the Bill Liquidation failed for the trade-related MT202
message, the status will be updated as L (Pending
Liquidation). List all the trade-related MT202 which are failed
during Bill Liquidation by filtering by Status as L (Pending
Liquidation). On successful processing of Trade Related
MT202, the generated Reference Number is displayed with the
Bill Contract Reference Number in the Incoming Message
Browser Summary screen.
Process Status Select the process status from the drop-down list.
• Unprocessed
• Processed
• Repair
• Exception
• Pending Auth Receipt

Through the Incoming Message Browser Summary screen, the following

functions can be performed:
• Upload incoming messages from the incoming directory on the node
• Check Testwords for Telex messages
• Authorize the Testword check for messages
• Link an incoming message to a contract
• Route the incoming messages to appropriate queues
3. Click the Search button to view the details.
The system identifies all incoming messages satisfying the specified criteria and
displays the following details for each incoming message:
• Branch
• Document Number
• Reference Number
• Sender
• Media
• SWIFT Message Type
• SWIFT Sub Message Type
• Name

7-4
 Chapter 7
Incoming Messages

• Address 1
• Address 2
• Address 3
• Address 4
• Location
• Testword
• Entry By
• Release Time
• Running Number
• Authorized
• Checker Date Stamp
• Checker ID
• Status
• Suppress Message
• External Reference
• Process Status
• Modification Number
• Media Control System
• Message Status
• Once Auth
• Value Date
• Amount
• PDE Flag
• Queue
• Message Sequence Number
• Customer Reference Number
• SWIFT LAU
• LAU Validation
• RTGS Network
• Generated Reference
4. Check the box against the message(s) for which needs to perform an operation and then
click the corresponding operation.

Table 7-2 Operations

Operation Description
View To view the message, highlight the message and click the View
button on the browser. The contents of the message will be
displayed in a separate screen.

7-5
 Chapter 7
Incoming Messages

Table 7-2 (Cont.) Operations

Operation Description
Change Branch Select the message for which Branch has to be changed and click
on Change Branch button. The details of the message will be
displayed with only the Branch field enabled. Select the new branch
from the list of values provided and save the message.
TW Auth A telex message for which a testword is entered should be
authorized before it can be routed to a user queue (if it is specified
in the Messaging Branch Parameters Maintenance screen). To
authorize a test word that was entered for a telex message, click the
TW Auth button from the browser on this screen. During the
authorization of a testword the authorizer will be required to re-enter
the testword.
Link Contract In the browser, select the message with which a contract to be
associated and click the Link Contract button. The Reference
Number option list is enabled for the selected message. Select the
appropriate contract from the list. The message will be
subsequently associated with the contract selected here.
Edit Click the Edit button to make changes to the SWIFT message,
especially the messages marked for repair. The message is
displayed in edit mode (Edit Message screen) and only a user with
requisite rights for editing can edit an incoming message. If editing
is possible for the user, the message is available for amendment.
The list of fields which can be modified are maintained through
back-end database tables appropriately during implementation of
Oracle FLEXCUBE Universal Banking . Mostly fields like Amount,
Currency are maintained as non-modifiable whereas fields such as
Value Date is maintained as modifiable. Based on the maintenance
in these tables, the appropriate fields are enabled for amendment.
On saving the amendment of the message, a new version is created
and must be authorized. Two versions of an incoming message are
displayed on the screen. If the verifier needs to reject the change for
any reason the same can be mentioned in the Reject Reason field.

Note:
In the case of incoming messages with a PDE trailer, the
PDE Flag check box in the Incoming Message Browser
Summary screen will be checked. In the Edit Message
screen, check Remove Trailer option to remove the PDE
trailer (message contains the text PDE) and save the
message.

Force Use Force button to forcibly release all Payment Message

Transactions with Funding Exception status and insufficient funds.
In other words, the system will post the required accounting entries
for such transactions regardless of insufficient funds in the
accounts. However, an override will be displayed. The system will
also maintain a detailed audit trail for such transactions. A user with
appropriate rights can perform this function.
Print To print the details of an incoming message, highlight the message
and click the Print button on the browser. The screen prompts the
option to spool or directly print the message. The SWIFT tag
description can also be viewed.

7-6
 Chapter 7
Incoming Messages

Table 7-2 (Cont.) Operations

Operation Description
Change Address To change the address, highlight the message and click the
Change Address button on the browser.
Move To Queue After the necessary checks for the media through which a message
is transmitted, route the message to a user queue. To change the
queue in which an incoming message should be stored, select the
message, click the Move To Queue button and select a queue from
the adjoining option list. The message will be automatically moved
to the queue that is specified. The final destination of an incoming
message is the end-user queue. These queues represent
departments or printers responsible for acting on the received
messages. Once a message is lodged into an end-user queue, it
can be viewed on-screen or printed by the users who have access
to the queue. It is possible to move messages from one end user
queue to another as well. For a message that was transmitted
through Telex, enter the testword and have it authorized before
routing it to the relevant end-user queue.
Upload If the background process for incoming messages is not running,
upload the messages that have come into the bank from the
incoming directory on the node to which the branch is connected.
To upload messages from the incoming directory (specified in the
Message Media Control Maintenance screen) click the Upload
button. All messages that were stored in the incoming directory will
be uploaded to Oracle FLEXCUBE Universal Banking and displayed
in the Incoming Message Browser.
Authorize Use the Authorize button to authorize the message. All the
amendments made to a SWIFT payment message have to be
authorized by a user with appropriate authorization rights. At the
time of authorization, Oracle FLEXCUBE Universal Banking will
display the earlier version of the SWIFT payment message along
with the amended version, in the same window. A list of all the
errors due to which the message was marked for repair is also
displayed. The authorizer can view all the errors and also verify the
changes that were made to correct them. After verification, if all the
details are found to be appropriate, the message is authorized.
Oracle FLEXCUBE Universal Banking maintains a detailed audit log
of all amended SWIFT Payment Messages. The following details
are captured for each authorized message:
• User ID of the person who authorized the amendments
• Date and time of authorization
At any point during the verification and authorization process, the
authorizer can choose to cancel the entire operation without
changing the status of the message.

7-7
 Chapter 7
Incoming Messages

Table 7-2 (Cont.) Operations

Operation Description
Suppress To suppress a message, click the Suppress button in the incoming
browser and process the Suppress Message screen. The following
options are available to suppress a Payment Message:
• Suppress Message Generation: On selecting this option,
Oracle FLEXCUBE Universal Banking stops the generation of
the Payment Message. However, the system post the
necessary accounting entries for the messages being
suppressed.
• Suppress Full: On selecting this option, the system does not
post the related accounting entries. Advice generation stops
and the system does not pick up the Payment Message for any
further processing.
• No Suppress: A message marked with the No Suppress
option is processed like any other normal incoming SWIFT
payment message.
Specify the reason for suppressing a Payment Message in the
Remarks field.

7-8
 Chapter 7
Incoming Messages

Table 7-2 (Cont.) Operations

Operation Description
Details To view details of the incoming message, select the message and
click the Details button. The following details regarding the
incoming message are displayed on the Details screen:
• Document Number
• Reference Number
• Swift Message Type
• Queue
• Operation
• Status
• Currency
• Amount
• Value Date
• External Reference Number
• Multi Credit Reference Number
• Branch
• Media Control System
• Node
• Test Word
• Repair Reason
• Name
• Address
• Location
• Process
• PDE Flag
• Suppress Options
• Remarks
• Auth By
• Entry By
• Sender
• Media
• Mod Number
• Checker Date Stamp
• Maker Date Stamp
• Suppress Status
• Funding Exception Status
• Cover Match Status
• Authorization Status

5. Click the Exit button to end the transaction.

7.1.2 View Details of Incoming Message

This topic provides systematic instruction to view details of incoming message.
1. On Treasury Incoming Message Summary screen, select the message and click
'Details' button.
2. On 'Message' screen, specify the details as required.
• DCN
• Reference Number

7-9
 Chapter 7
Incoming Messages

• Sender
• Media
• Swift Message Type
• Queue
• Operation
• Status
• Currency
• Amount
• Value Date
• External Reference Number
• Multi Credit Reference Number
• Branch
• Media Control System
• Node
• Test Word
• Repair Reason
• Name
• Address
• Location
• Process
• PDE Flag
• Suppress Options
• Remarks
• Auth By
• Entry By
• Mod No
• Checker Date Stamp
• Maker Date Stamp
• Suppress Status
• Funding Exception Status
• Cover Match Status
• Authorization Status

7.1.3 Edit Incoming Message

This topic provides systematic instructions to edit an incoming message.

• On Treasury Incoming Message Summary screen, click Edit button.

7-10
 Chapter 7
Incoming Messages

The message is displayed in edit mode. Only a user with requisite rights for editing can
edit an incoming message.
The Treasury Edit SWIFT Message screen is displayed:

Figure 7-2 Treasury Edit SWIFT Message

If editing is possible for the user, the message is displayed and is available for
amendment. The list of fields, which can be modified are maintained through back-end
database tables appropriately during implementation of Oracle Banking Treasury
Management. Most typically, fields like amount, currency would be maintained as non-
modifiable whereas fields such as value date could be maintained as modifiable. Based
on the maintenance in these tables, the appropriate fields are enabled for amendment.
On saving the amendment of the message, a new version is created and must be
authorized. The screen shown above displays two versions of an incoming message. If
the verifier needs to reject the change for any reason the same can be mentioned in the
‘Reject Reason’ field.

Note:
In the case of incoming messages with a PDE trailer, the ‘PDE Flag’ check box
in the ‘Incoming Message Browser’ screen will be checked. In the ‘Edit
Message’ screen, check ‘Remove Trailer’ option to remove the PDE trailer
(message contains the text {‘PDE:’}) and save the message.

7-11
8
Define Free Format Messages
In the course of daily banking operations, the user may want to generate messages that are
not automatically generated by the system to communicate a message that is very specific to
a customer. The user can enter the details of such messages in the form of a free format
message.
The details of a free format message can be entered in the Free Format Message
Maintenance screen. This screen displays the some of the following details:
• The format of the message
• The recipient of the message
• The media through which the message should be transmitted
• The address and location to which the Free Format Message should be sent
This topic contain the following sub-topics:
• Maintain Free Format Message
This topic provides systematic instructions to maintain a free format message.

8.1 Maintain Free Format Message

This topic provides systematic instructions to maintain a free format message.
1. On Homescreen, specify MSDTRFFT in the text box, and click Next.
Treasury Free Format Message Maintenance screen displays.

8-1
 Chapter 8
Maintain Free Format Message

Figure 8-1 Treasury Free Format Message Maintenance

2. On Treasury Free Format Message Maintenance screen, specify the details.

Table 8-1 Treasury Free Format Message Maintenance - Field Description

Field Description
Document Number The system generates the document number on save.
Module Select the module from the drop-down list.
Customer Select the customer code to whom the message is addressed.
If the recipient is not a customer of the bank, then specify the
name of the recipient in this field.
Media Specify the media through which the Free Format Message
should be transmitted. The media through which a Free
Format Message is transmitted is depends on the media types
that is maintained for the branch in the Media Maintenance
screen.
Location Specify the location of the address. To recall, the location that
is specified for an address is a unique identifier between the
other addresses of the customer for a given media. The
address of the customer will be automatically displayed based
on the Customer-Location-Media combination, if it is already
maintained in the system.
Node Specify the node from where this Free Format Message has to
be generated.
Date Select the date from the Calendar icon.
External Reference The system displays external reference number on save.
Number

8-2
 Chapter 8
Maintain Free Format Message

Table 8-1 (Cont.) Treasury Free Format Message Maintenance - Field

Description

Field Description
Name In the case of a walk-in customer, enter the name of the
customer to whom the message is to be addressed. If the
recipient of the message is a customer of the bank, the
customer’s name will be automatically displayed on entering
the customer’s CIF number in the Customer field.
Address If the recipient of the message is a customer of the bank, the
customer’s address will be automatically displayed based on
the Customer-Location-Media combination that is specified.
In the case of a Walk-in customer, enter the address. The
format of the address depends on the media through which the
Free Format Message is transmitted. If the address is for the
media type Mail, enter the customer's address in the four rows
under this field. Each line can contain a maximum of 35
characters. If the media of transmission is Telex, the address
should be expressed numerically. For defining a SWIFT
address, the address should be of eight or eleven
alphanumeric characters.
Form If the message to be sent is in the form of a template, select
the template from the option list.
Copies Enter the number of copies of the Free Format Message must
be sent to the customer at the time it is generated. To send
more than one copy to a location, the first message is the
original one and the others are marked as Copy
Hold On-hold Messages are temporarily stopped from the
generation. If its specified to generate messages in the
background, the Free Format Messages are immediately sent
on saving the record. To not send the messages immediately,
place it on hold. In this case, the messages appears in the
Outgoing Message Browser, but will be in the hold status. The
user must release the message before generating it from the
Outgoing Browser.
Test Word Required Indicate whether a test word needs to be inserted into the telex
message manually before it is generated from your branch.
Contract Reference Specify the code assigned to the customer, the recipient of the
message. This code is assigned to the customer in the
Customer Information File (CIF).
Server The server indicates the machine on which the database of the
bank is installed. To import a format from an ASCII file on the
server, select the radio button against Server.
Import File Specify the full path to the file on the server which contains the
format to be imported.
Import Click Import button to import the ASCII file format. The file
containing the format of the message will be displayed on the
screen.

Maintain Free Format Message - Message Tab

This topic provides systematic instructions to specify free format messages.
1. On Treasury Free Format Message Maintenance screen, click the Message tab.
Message tab displays.

8-3
 Chapter 8
Maintain Free Format Message

Figure 8-2 Treasury Free Format Message Maintenance - Message

2. On Message tab, specify the details.

Table 8-2 Message Tab - Field Description

Field Description
Message Enter the details of a Free Format Message
either by using the format editor on the
screen or by importing the format from an
ASCII file. This can be located either on the
server or the client.

Maintain Free Format Message - SWIFT Message Details Tab

This topic provides systematic instructions to view SWIFT message details.
1. On Treasury Free Format Message Maintenance screen, click the SWIFT
Message Details tab.
SWIFT Message Details tab displays.

8-4
 Chapter 8
Maintain Free Format Message

Figure 8-3 Treasury Free Format Message Maintenance - SWIFT Message Details

2. On SWIFT Message Details tab, specify the details.

8-5
 Chapter 8
Maintain Free Format Message

Table 8-3 SWIFT Message Details Tab - Field Description

Field Description
SWIFT Message Type Select the type of SWIFT message.
• 199
• 299
• 399
• 499
• 599
• 699
• 799
• 899
• 999
• 649
Enter the SWIFT messages by clicking the
Text icon.

Maintain Free Format Message - Free Format Text Tab

This topic provides systematic instructions to maintain free format text.
1. On Treasury Free Format Message Maintenance screen, click the Free Format
Text tab.
Free Format Text tab displays.

8-6
 Chapter 8
Maintain Free Format Message

Figure 8-4 Treasury Free Format Message Maintenance - Free Format Text

2. On Free Format Text tab, specify the details.

8-7
 Chapter 8
Maintain Free Format Message

To enter a format using the format editor, click the free format text icon positioned
next to the text of the message. In the notepad, the user can tailor an advice to
suit the requirements. Keywords to format the advice (similar to the Advice
Format Maintenance screen) can be used here too to get the desired format. The
following table contains a comprehensive list of the keywords that can be used in
the format editor.

Table 8-4 Keywords

Keyword Significance
#NL Indicates the number of lines that should be
contained in a page when the message is
printed
#NC Indicates the number of columns that should
be contained in a page when the message
is printed
#RH Indicates the start of the Report Header
section
#PH Indicates the beginning of the Header for a
page
#EH Indicates both the end of the Header section
of the report or the end of Header section of
a page
#RF Indicates the start of the Report Footer
section
#PF Indicates the start of the Footer of a page
#EF Indicates both the end of the Footer of a
report or page
#B Indicates the start of the body of the
message
#EB Indicates the end of the body of the
message
#CL Indicates that you can collapse a line
#EC Indicates the end of a line that you have
collapsed
#LOOP Indicates the beginning of a loop
#ENDLOOP Indicates the end of a loop
#IF Indicates a Conditional section
#ANDIF Indicates a Conditional section
#ORIF Indicates a Conditional section
#ENDIF Indicates the end of a Conditional section

A Free Format Message will be sent depending on the specifications in the Jobs
Browser screen.
• If the background process is running, a free format text that is defined will be
immediately sent on saving the record.
• If the background process is not running, the Free Format Message that is
defined will be displayed in the Outgoing Message browser from where can be
processed.
3. After specifying the mandatory entries, save the record.

8-8
 Chapter 8
Maintain Free Format Message

A free format record that is defined should be authorized by a user bearing a different
login Id, before the End of Day (EOD) process is run.
4. Click the Exit button to end the transaction.

8-9
9
Process Query
In the Outgoing or Incoming Message Browser, all the messages that were transmitted from
and received at the branch are displayed. This may amount to hundreds of messages. To
avoid wading through this mass of data, perform a query to obtain information that is relevant
at a particular time. For example, The Advanced Search function makes possible to obtain
information on the messages that were sent to just two customers on a specific date or to see
all outgoing messages across modules sent during a specific period etc.
• Launch Advanced Search Screen
This topic provides the systematic instructions to load advanced search screen.
• Make Query based on more than one Criterion
This topic provides the systematic instructions to make query based on more than one
criterion.
• Select Same Criterion to Apply One or More Conditions
This topic provides the systematic instructions to select same criterion to apply one or
more conditions.
• Order Details of Query
This topic provides the systematic instructions to order details of query.
• Using Wildcards to make Query

9.1 Launch Advanced Search Screen

This topic provides the systematic instructions to load advanced search screen.
1. Click Advanced Search either from the Outgoing or Incoming Browser.
The Advanced Search screen is displayed:

9-1
 Chapter 9
Launch Advanced Search Screen

Figure 9-1 Advanced Search

9-2
 Chapter 9
Make Query based on more than one Criterion

The Query screen will display all the fields that appear in the messaging module. These
fields form the criteria based on which you can make a query.
2. On the Advanced Summary screen, click Clear Query’button, not wish to carry the
query and you can proceed to make a new query.

9.2 Make Query based on more than one Criterion

This topic provides the systematic instructions to make query based on more than one
criterion.
Suppose you want to obtain information based on more than one criterion. For example, you
may want to view the details of all the guarantees generated for the Letters of Credit module
from your branch located at London.
The procedure to make such a query involves the following steps:

Table 9-1 Actions

Action Button
Accept The Accept button
And The And button

1. Select Module under Fields, and then from the Operator drop-down list choose Equal To
and LC under Value. Then click the Accept button.
2. Click the And button. Repeat step one with the criteria value, as Message type, select
Guarantee under value clicking accept and add buttons in the sequence described for the
first criterion.
3. Click the And button. Repeat step one with the criteria value, as Branch select London
under Value clicking accept and add buttons in the sequence described for the first
criterion.
4. The query that you have made will be displayed in the Query screen. Check it for
correctness and click ‘Ok’ button.
The Outgoing Message Browser will display details of all the Guarantees generated for the
LC module from your branch at London.

9.3 Select Same Criterion to Apply One or More Conditions

This topic provides the systematic instructions to select same criterion to apply one or more
conditions.
Now, you may want to make a query to see the debit advices (in the Letters of Credit module)
that were generated from the London branch involving three different customers (Wendy
Klien, Silas Reed and Keturah Smith).
This involves specifying a customer code one by one all of which come under the same
criterion module -- LC (listed out under Fields) and indicating a message type for which you
want details. This is where the ‘Or’ button on the query screen comes into play. You can
choose to use the keyboard to key in the query or you can follow the following procedure to
make a query.
1. Select Module under Fields, and then from the Operator drop-down list choose Equal To
and LC under Value. Then click the ‘Accept’ button.

9-3
 Chapter 9
Order Details of Query

2. Click the And button. Repeat step one with criteria Field as “Branch”, Operator
being “Equal To” and “London” under Value. Click the ‘Accept’ and ‘Add’ buttons
in the sequence described in Step 1.
3. Click the And button. Repeat step one for Field with the criteria value, as Message
Type. Then select Debit Message under Value clicking the ‘Accept’ and ‘Add’
buttons in the sequence described for the first criterion.
4. To cull out details of the debit advices involving these three customers, click the
And button. Repeat Step 1 with the ‘Field’ as ‘Name’. Select say Ms. Keturah
Smith under Value. Then click the accept button.
To select another customer, click the Or button and then click Name in the Fields
list, specify the Operator as Equal To and pick out the customer name Mr. Silas
Reed from the Value option list then click the Accept button.
Repeat the process for the third customer, Ms. Wendy Klien.
5. The query that you have made is displayed on the Query screen.
MODULE = LC AND BRANCH = LONDON AND MSG_TYPE = DR_ADV AND
NAME = SILAS REED OR NAME = KETURAH SMITH OR NAME = WENDY
KLIEN
Check it for correctness and click ‘Ok’ button to see the query through. The
Outgoing Message Browser will display details of all the debit advices generated
for the LC module from your branch at London to the three customers that you
specified.

9.4 Order Details of Query

This topic provides the systematic instructions to order details of query.
Oracle Banking Trade Finance also provides you the option to order the information
that you have made a query on.
1. On 'Advanced Search' screen, specify the ordered information.
It should be arranged in ascending or descending order.

9-4
 Chapter 9
Order Details of Query

Figure 9-2 Advanced Search

9-5
 Chapter 9
Using Wildcards to make Query

Suppose you have made a query to obtain details of the debit messages that were
generated by the Data Entry module of Oracle Banking Trade Finance, and you
wish to order the information in the ascending order of the customer to whom the
message was sent.
Make the query following the procedure detailed under the head making a Query
after you have specified the entire criterion for the query, select the required
ordering option from the Order By drop-down list. The list contains the following
options:
• Ascending
• Descending
2. Click the option of your choice, say, Descending.
3. Click the ‘Accept’ button and click ‘Ok’.
The details of the query that you have made will be displayed on the Outgoing
Browser ordered on the basis of the customer to whom the message was sent.
The details will further be sorted in the alphabetic order.
4. Click 'Clear Query’ button.
If you decide to cancel the ordering you have specified. The screen clears and you
can specify a new order.

9.5 Using Wildcards to make Query

You need not always specify the criteria for a query. You can use wild cards such as:

Table 9-2 Wildcards

Wild Card Description Implication

- Underscore To match a single
character
% Percent To match any string of
multiple characters

Using %
For instance, if you have to check the messages relating to one particular Loans
product LD01, you can query for records with Reference Number like ‘%LD01%’ since
all the contract reference numbers with that product will invariably contain that string.

Once you click the Accept button and make a query, the Outgoing Message
Browser screen displays all the Free Format Texts.

Using And
When you are searching for strings of specific length which vary in only one character
– for instance, all branches like 001, 002, 003 – can be represented as 00_. Searching
for 00_ will fetch all the messages for all these three branches.

9-6
10
Process SWIFT Messages
This topic provides an overview of the SWIFT messages.
SWIFT is the Society for Worldwide Interbank Financial Telecommunication, a member-
owned cooperative through which the financial world conducts its business operations with
speed, certainty, and confidence. SWIFT enables customers to automate and standardize
financial transactions, thereby lowering costs, reducing operational risk, and eliminating
inefficiencies from their operations.
SWIFT is solely a carrier of messages. It does not hold funds nor does it manage accounts
on behalf of customers, nor does it store financial information on an on-going basis. As a data
carrier, SWIFT transports messages between two financial institutions. This activity involves
the secure exchange of proprietary data while ensuring its confidentiality and integrity.
There are four key areas that SWIFT services fall under within the financial marketplace.
They are Securities, Treasury and Derivatives, Trade Services, and Payments and Cash
Management.
SWIFT messages consist of five blocks of data including three headers, message content,
and a trailer. They are identified in a consistent manner. They all start with the literal MT
which denotes Message Type. This is followed by a 3-digit number that denotes the message
type, category, and group. The following are the categories of a message:

Table 10-1 Message Category

Category Description
Category 1 Customer Payments and Cheques
Category 2 Financial Institution Transfers
Category 3 Treasury Markets - Foreign Exchange, Money
Markets and Derivatives
Category 4 Collections and Cash Letters
Category 5 Securities Markets
Category 6 Treasury Markets - Metals
Category 7 Documentary Credits and Guarantees
Category 8 Travellers Cheques
Category 9 Cash Management and Customer Status
Category n Common Group Messages

Oracle FLEXCUBE Universal Banking interfaces with an external payment system for the
generation of Category 1 and Category 2.
The following SWIFT message types are generated for the various transfers that are initiated
through the Oracle FLEXCUBE Universal Banking.
• Treasury Markets - Foreign Exchange, Money Markets and Derivatives
This topic describes the Swift messages for Foreign Exchange, Money Market, and
Derivatives modules.

10-1
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

• CoSecurities Markets
• Treasury Markets - Metals

10.1 Treasury Markets - Foreign Exchange, Money Markets

and Derivatives
This topic describes the Swift messages for Foreign Exchange, Money Market, and
Derivatives modules.
This topic has the following sub-topics:
• <Insert a cross-reference to the first child topic.>
• <Insert a cross-reference to the second child topic.>
• MT 300 Foreign Exchange Confirmation
This topic describes the MT 300 Foreign Exchange Confirmation messages.
• MT 304 Advice/Instruction of a Third Party Deal
This topic describes the MT 304 Advice/Instruction of a Third Party Deal.
• MT 305 Foreign Currency Option Confirmations
This topic describes the MT 305 Foreign Currency Option Confirmations.
• MT 306 Foreign Currency Option Confirmation
This topic describes the MT 306 Foreign Currency Option Confirmation.
• MT 320 Fixed Loan/Deposit Confirmation
This topic describes the MT 320 Fixed Loan/Deposit Confirmation messages.
• MT 330 Call/Notice Loan/Deposit Confirmation
This topic describes the MT 330 Call/Notice Loan/Deposit Confirmation.
• MT 340 Forward Rate Agreement Confirmation
This topic describes the MT 340 Forward Rate Agreement Confirmation.
• MT 341 Forward Rate Agreement Settlement Confirmation
This topic describes the MT 341 Forward Rate Agreement Settlement
Confirmation.
• MT 350 Advice of Loan/Deposit Interest Payment
This topic describes the MT 350 Advice of Loan/Deposit Interest Payment
• MT 360 Single Currency Interest Rate Derivative Confirmation
This topic describes the MT 360 Single Currency Interest Rate Derivative
Confirmation.
• MT 361 Cross Currency Interest Rate Swap Confirmation
This topic describes the MT 361 Cross Currency Interest Rate Swap Confirmation.
• MT 362 Interest Rate Reset/Advice of Payment
This topic describes the MT 362 Interest Rate Reset/ Advice of payment.
• MT 364 Single Currency Interest Rate Derivative Termination/ Recouponing
Confirmation
This topic describes the MT 364 single currency interest rate derivative
termination/recouponing confirmation.

10-2
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

• MT 365 Cross Currency Interest Rate Swap Termination/Recouponing Confirmation

This topic describes the MT 365 Cross Currency Interest Rate Swap Termination/
Recouponing Confirmation.

10.1.1 MT 300 Foreign Exchange Confirmation

This topic describes the MT 300 Foreign Exchange Confirmation messages.
This message is exchanged by or on behalf of the institutions or corporate, party A and party
B, which have agreed to a foreign exchange contract. This message may also be sent by a
money broker to the two parties (party A and party B) for which the broker arranged the deal.
This message is also used when one of the trading parties is a fund manager as the fund
manager has to specify the fund for which he is dealing.
The MT 300 is used to:
• confirm the details of a new contract between the parties
• confirm an exercised foreign currency option
• confirm the details of an amendment to a previously sent confirmation
• cancel a previously sent confirmation.
Maximum Length: 10000

Table 10-2 Format Specifications: Mandatory Sequence A General Information

Field Tag Field Name Format Mandatory/Optional

Field Tag Field Name Format Mandatory/Optional
15A New Sequence Empty field M
20 Sender's Reference 16x M
21 Related Reference 16x O
22A Type of Operation 4!c M
94A Scope of Operation 4!c O
22C Common Reference 4!a2!c4!n4!a2!c M
17T Block Trade Indicator 1!a O
17U Split Settlement 1!a O
Indicator
82a Party A A or J M
87a Party B A or J M
83a Fund or Beneficiary A or J O
Customer
77D Terms and Conditions 6*35x O

The system does not support the use of NDF codes (/VALD/, /SETC/, /FIX/)in the field 77D of
MT 300 in Sequence A.

Table 10-3 Mandatory Sequence B Transaction Details

Field Tag Field Name Format Mandatory/Optional

15B New Sequence Empty field M
30T Trade Date 8!n M

10-3
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-3 (Cont.) Mandatory Sequence B Transaction Details

Field Tag Field Name Format Mandatory/Optional

30V Value Date 8!n M
36 Exchange Rate 12d M

Table 10-4 Mandatory Subsequence B1 Amount Bought

Field Tag Field Name Format Mandatory/Optional

32B Currency, Amount 3!a15d M
53a Delivery Agent A or J O
56a Intermediary A or J O
57a Receiving Agent A or J M

Table 10-5 Mandatory Sub-sequence B2 Amount Sold

Field Tag Field Name Format Mandatory/Optional

33B Currency, Amount 3!a15d M
53a Delivery Agent A or J O
56a Intermediary A or J O
57a Receiving Agent A or J M
58a Beneficiary Institution A or J O

Table 10-6 Optional Sequence C Optional General Information

Field Tag Field Name Format Mandatory/Optional

15C New Sequence Empty field M
29A Contact Information 4*35x O
24D Dealing Method 4!c[/35x] O
84a Dealing Branch Party A, B, D, or J O
A
85a Dealing Branch Party A, B, D, or J O
B
88a Broker Identification A, D, or J O
71F Broker's Commission 3!a15d O
26H Counterparty's 16x O
Reference
21G Broker's Reference 16x O
72 Sender to Receiver 6*35x O
Information

Table 10-7 Optional Sequence D Split Settlement Details

Field Tag Field Name Format Mandatory/Optional

15D New Sequence Empty field M

10-4
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-7 (Cont.) Optional Sequence D Split Settlement Details

Field Tag Field Name Format Mandatory/Optional

17A Buy (Sell) Indicator 1!a M
32B Currency, Amount 3!a15d M
53a Delivery Agent A, D, or J O
56a Intermediary A, D, or J O
57a Receiving Agent A, D, or J M
58a Beneficiary Institution A, D, or J O
16A Number of 5n M
Settlements

Note:
In option J, Party Identification must be specified as a list of pairs (Code)(Value).
The codes must be placed between slashes ('/').

10.1.2 MT 304 Advice/Instruction of a Third Party Deal

This topic describes the MT 304 Advice/Instruction of a Third Party Deal.
This message is sent by a fund manager to a custodian bank as an advice of/instruction to
settle a third party foreign exchange deal. The definition of third party must be agreed up front
between the fund manager and the custodian relative to deals executed by the custodians'
treasury area on behalf of the fund manager. It is used to:
• provide details about a new deal
• provide a settlement notification
• amend a previously sent message
• cancel a previously sent message
This message may also be sent to the member of a centralised settlement system or directly
to the centralised settlement system.

Table 10-8 Format Specifications: Mandatory Sequence A General Information

Field Tag Field Name Format Mandatory/Optional

15A New Sequence Empty field M
20 Sender's Reference 16x M
21 Related Reference 16x O
22A Type of Operation 4!c M
94A Scope of Operation 4!c M
17O Open Indicator 1!a O
17F Final Close Indicator 1!a O
17N Net Settlement Indicator 1!a O
83a Fund A or J M

10-5
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-8 (Cont.) Format Specifications: Mandatory Sequence A General Information

Field Tag Field Name Format Mandatory/Optional

82a Fund Manager A or J M
87a Executing Broker A or J M
81a Central Counterparty A, D, or J O
Clearing House (CCP)
89a Clearing Broker A, D, or J O
17l Payment versus 1!a O
Payment Settlement
Indicator
77H Type, Date, Version of 6a[/8!n][//4!n] O
the Agreement
14C Year of Definitions 4!n O
32E Settlement Currency 3!a O
30U Valuation Date 8!n O
14S Settlement Rate Source 3!a2n[/4!n/4!c] O
21A Reference to Opening 16x O
Instruction
14E Clearing or Settlement 35x O
Session

Table 10-9 Mandatory Sequence B Forex Transaction Details

Field Tag Field Name Format Mandatory/Optional

15B New Sequence Empty field M
30T Trade Date 8!n M
30V Value Date 8!n M
36 Exchange Rate 12d M
39M Payment Clearing 2!a O
Centre

Table 10-10 Mandatory Sub-sequence B1 Amount Bought

Field Tag Field Name Format Mandatory/Optional

32B Currency, Amount 3!a15d M
Bought
53a Delivery Agent A or J M
56a Intermediary A or J O
57a Receiving Agent A or J O

Table 10-11 Mandatory Subsequence B2 Amount Sold

Field Tag Field Name Format Mandatory/Optional

Field Tag Field Name Format Mandatory/Optional
33B Currency, Amount 3!a15d M
Sold

10-6
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-11 (Cont.) Mandatory Subsequence B2 Amount Sold

Field Tag Field Name Format Mandatory/Optional

53a Delivery Agent A or J O
56a Intermediary A or J O
57a Receiving Agent A or J M
58a Beneficiary Institution A or J O

Table 10-12 Optional Sequence C Optional General Information

Field Tag Field Name Format Mandatory/Optional

15C New Sequence Empty field M
21A Reference to the 16x O
Associated Trade
21G Executing Broker's 16x O
Reference
22U Underlying Product 6a O
Identifier
35B Identification of [ISIN1!e12!c] O
Financial Instrument 4*35x
22V Execution Venue 35x O
98D Execution Timestamp 8!n6!n[,3n][/[N]2!n[2!n]] O
98G Confirmation 8!n6!n[,3n][/[N]2!n[2!n]] O
Timestamp
98H Clearing Timestamp 6!n[,3n][/[N]2!n[2!n]] O
29A Contact Information 4*35x O
34C Commission and Fees 4!c/[N]3!a15d O
72 Sender to Receiver 6*35x O
Information

Table 10-13 Optional Repetitive Subsequence C1 Unique Transaction Identifier

Field Tag Field Name Format Mandatory/Optional

22L Reporting Jurisdiction 35x M
22M UTI Namespace/Issuer 30x M
Code
22N Transaction Identifier 32x M

Table 10-14 Optional Repetitive Sub-sequence C1a Prior Unique Transaction

Identifier

Field Tag Field Name Format Mandatory/Optional

22P PUTI Namespace/ 30x M
Issuer Code
22R Prior Transaction 32x M
Identifier

10-7
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-15 Optional Sequence D Accounting Information

Field Tag Field Name Format Mandatory/Optional

15D New Sequence Empty field M
21P Reference to Previous 16x O
Deals
17G Gain (Loss) Indicator 1!a O
32G Currency, Amount 3!a15d O
34B Commission and Fees 3!a15d O
- Currency and
Amount
30F Commission and Fees 8!n O
- Settlement Date

Table 10-16 Optional Sequence E Net Amount to be Settled

Field Tag Field Name Format Mandatory/Optional

15E New Sequence Empty field M
17G Gain (Loss) Indicator 1!a M
32G Currency, Amount 3!a15d M
53a Delivery Agent A, D, or J O
56a Intermediary A, D, or J O
57a Receiving Agent A, D, or J O
58a Beneficiary Institution A, D, or J O

Note:
In option J, Party Identification must be specified as a list of pairs (Code)
(Value). The codes must be placed between slashes ('/').

10.1.3 MT 305 Foreign Currency Option Confirmations

This topic describes the MT 305 Foreign Currency Option Confirmations.
This message type is exchanged between the financial institutions which have agreed
to a foreign currency option contract. It is used to confirm the details of:
• a new contract between the parties
• an amendment to a previously agreed contract
• the cancellation of a confirmation
• the surrender of an option by the buyer (holder) to the seller (grantor) for
compensation.
Maximum Length: 2000

10-8
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-17 Format Specifications

Field Tag Field Name Format Mandatory/Optional

15A New Sequence M
20 Transaction Reference 16x M
Number
21 Related Reference 16x M
22 Code/Common 8a/4!a2!c4!n4!a2!c M
Reference
23 Further Identification 16x M
94A Scope of Operation 4!c O
82a Party A A, , or J M
87a Party B A, , or J M
83a Fund or Beneficiary A,, or J O
Customer
30 Date Contract Agreed/ 6!n M
Amended
31C Earliest Exercise Date 6!n O
31G Expiry Details 6!n/4!n/12a M
31E Final Settlement Date 6!n M
26F Settlement Type 9a M
32B Underlying Currency 3!a15d M
and Amount
36 Strike Price 12d M
33B Counter Currency and 3!a15d M
Amount
37K Premium Price 3!a12d M
34a Premium Payment P or R M
53a Sender's Correspondent A, B, or D O
56a Intermediary A or D O
57a Account With Institution A or D M
77D Terms and Conditions 6*35x O
72 Sender to Receiver 6*35x O
Information

10.1.4 MT 306 Foreign Currency Option Confirmation

This topic describes the MT 306 Foreign Currency Option Confirmation.
This message is exchanged to confirm a foreign currency option contract, by or on behalf of
the institutions or corporate, party A and party B, which have agreed to it. A money broker
may also send this message to the two parties (party A and party B) for which he arranged
the deal. If there are two money brokers involved in arranging a deal between party A and
party B, this message can also be exchanged between these money brokers. The message
is used to confirm/notify the details of:
• a new contract between the parties
• an amendment to a previously agreed contract

10-9
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

• the cancellation of a confirmation a trigger event: knock-in/knock-out of an option,

hitting of a trigger level
• the close out of an option
Maximum Length: 10000

Table 10-18 Format Specifications: Mandatory Sequence A General Information

Field Tag Field Name Format Mandatory/Optional

12G Option Type 4!c O
15A New Sequence Empty field M
20 Sender's Reference 16x M
21 Related Reference 16x O
22A Type of Operation 4!c M
94A Scope of Operation 4!c O
22C Common Reference 4!a2!c4!n4!a2!c M
21N Contract Number 16x M
Party A
21B Contract Number 16x O
Party B
12F Option Style 4!c M
12E Expiration Style 4!c M
17A Barrier Indicator 1!a M
17F Non-Deliverable 1!a M
Indicator
22K Type of Event 4!c[/35x] M
30U Date of Trigger Hit 8!n O
29H Location of Trigger Hit 4!c O
82a Party A A, , or J M
87a Party B A, or J M
83a Fund or Beneficiary A, , or J O
Customer
77H Type, Date, Version of 6a[/8!n][//4!n] M
the Agreement
77D Additional Conditions 6*35x O
14C Year of Definitions 4!n O

Table 10-19 Mandatory Sequence B Transaction Details

Field Tag Field Name Format Mandatory/Optional

15B New Sequence Empty field M
17V Buy (Sell) Indicator 1!a M
30T Trade Date 8!n M
30X Expiration Date 8!n M
29E Expiration Location 4!c/4!n M
and Time
30a Final Settlement Date F or J M

10-10
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-20 Optional Sub-sequence B1 Premium Details

Field Tag Field Name Format Mandatory/Optional

37K Premium Price 3!a12d O
30V Premium Payment Date 8!n M
34B Premium Currency and 3!a15d M
Amount

Table 10-21 Optional Sub-sequence B2 Calculation Agent

Field Tag Field Name Format Mandatory/Optional

84a Calculation Agent A, B, D, or J O

Table 10-22 Optional Sequence C Settlement Instructions for Payment of Premium

Field Tag Field Name Format Mandatory/Optional

15C New Sequence Empty field M
53a Delivery Agent A, , or J O
86a Intermediary 2 A, , or J O
56a Intermediary A, , or J O
57a Receiving Agent A, , or J M
58a Beneficiary Institution A, , or J O

Table 10-23 Optional Sequence D Vanilla Block

Field Tag Field Name Format Mandatory/Optional

15D New Sequence Empty field M
30P Earliest Exercise Date 8!n O
30Q Intermediate Exercise 8!n O
Date
26F Settlement Type 9a M
32B Put Currency and 3!a15d M
Amount
36 Strike Price 12d M
33B Call Currency and 3!a15d M
Amount

Table 10-24 Optional Sequence E Payout Amount

Field Tag Field Name Format Mandatory/Optional

15E New Sequence Empty field M
33E Currency, Amount 3!a15d M
30H Touch Payment Date 8!n O
53a Delivery Agent A, or J O
86a Intermediary 2 A, or J O

10-11
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-24 (Cont.) Optional Sequence E Payout Amount

Field Tag Field Name Format Mandatory/Optional

56a Intermediary A, or J O
57a Receiving Agent A, or J M
58a Beneficiary Institution A, or J O

Table 10-25 Optional Sequence F Barrier Block

Field Tag Field Name Format Mandatory/Optional

15F New Sequence Empty field M
22G Type of Barrier 4!c M
37J Barrier Level 12d M
37L Lower Barrier Level 12d O
14M Barrier Time Type 4!c M

Table 10-26 Optional Sub-sequence F1 Barrier Window Block

Field Tag Field Name Format Mandatory/Optional

30G Barrier Window Start 8!n/8!n M
Date and End Date
29J Location and Time for 4!c[/4!n] M
Start Date
29K Location and Time for 4!c/4!n M
End Date

Table 10-27 Optional Sequence G Trigger Block

Field Tag Field Name Format Mandatory/Optional

15G New Sequence Empty field M
22J Type of Trigger 4!c M
37U Trigger Level 12d M
37P Lower Trigger Level 12d O
32Q Currency Pair 3!a/3!a M

Table 10-28 Optional Sequence H Non Deliverable Option Block

Field Tag Field Name Format Mandatory/Optional

15H New Sequence Empty field M
14S Settlement Rate 3!a2!n M
Source, Settlement
Rate Location,
Settlement Rate Time
(HHMM)
32E Settlement Currency 3!a M

10-12
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-29 Optional Sequence I Additional Information

Field Tag Field Name Format Mandatory/Optional

15I New Sequence Empty field M
29A Contact Information 4*35x O
24D Dealing Method 4!c[/35x] O
88a Broker Identification A or D O
71F Broker's Commission 3!a15d O
21G Broker's Reference 16x O
72 Sender to Receiver 6*35x O
Information

Table 10-30 Optional Sequence L Additional Amounts

Field Tag Field Name Format Mandatory/Optional

15J New Sequence Empty field M
18A Number of Repetitions 5n M
30F Payment Date 8!n M
32H Currency, Payment [N]3!a15d M
Amount
53a Delivery Agent A, or J O
86a Intermediary 2 A, or J O
56a Intermediary A, or J O
57a Receiving Agent A, or J M

SWIFT 2023 Message Standards

Table 10-31 Format Specifications: Mandatory Sequence A General Information

Field Tag Field Name Format Mandatory/Optional

15A New Sequence Empty field M
20 Sender's Reference 16x M
21 Related Reference 16x O
22A Type of Operation 4!c M
94A Scope of Operation 4!c O
22C Common Reference 4!a2!c4!n4!a2!c M
21N Contract Number Party 16x M
A
21B Contract Number Party 16x O
B
12F Option Style 4!c M
12E Expiration Style 4!c O
12D Option Type 4!C O
17A Barrier Indicator 1!a O
17F Non-Deliverable 1!a M
Indicator

10-13
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-31 (Cont.) Format Specifications: Mandatory Sequence A General

Information

Field Tag Field Name Format Mandatory/Optional

22K Type of Event 4!c[/35x] M
30U Date of Barrier Event 8!n O
29H Location of Barrier 4!c O
Event
82a Party A A, or J M
87a Party B A, or J M
83a Fund or Beneficiary A, , or J O
Customer
77H Type, Date, Version of 6a[/8!n][//4!n] M
the Agreement
77D Additional Conditions 6*35x O
14C Year of Definitions 4!n O

Table 10-32 Mandatory Sequence B Transaction Details

Field Tag Field Name Format Mandatory/Optional

15B New Sequence Empty field M
17V Buy (Sell) Indicator 1!a M
30T Trade Date 8!n M
30X Expiration or Valuation 8!n M
Date
29E Expiration or Valuation 4!c/4!n M
Location and Time
30a Final Settlement Date F or J M
14S Settlement Rate 3!a2n[/4!n/4!c] O
Source
39M Payment Clearing 2!a O
Centre

Table 10-33 Optional Sub-sequence B1 Premium Details

Field Tag Field Name Format Mandatory/Optional

37K Premium Price 3!a12d O
30V Premium Payment 8!n M
Date
34B Premium Currency 3!a15d M
and Amount

Table 10-34 Optional Sub-sequence B2 Calculation Agent

Field Tag Field Name Format Mandatory/Optional

84a Calculation Agent A, B, D, or J M

10-14
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-35 Optional Sequence C Settlement Instructions for Payment of Premium

Field Tag Field Name Format Mandatory/Optional

15C New Sequence Empty field M
53a Delivery Agent A or J O
86a Intermediary 2 A or J O
56a Intermediary A or J O
57a Receiving Agent A or J M
58a Beneficiary Institution A or Jl O

Table 10-36 Optional Sequence D Vanilla Block

Field Tag Field Name Format Mandatory/Optional

15D New Sequence Empty field M
30P Earliest Exercise Date 8!n O
30Q Intermediate Exercise 8!n O
Date
26F Settlement Type 9a M
32B Put Currency and 3!a15d M
Amount
36 Strike Price 12d M
33B Call Currency and 3!a15d M
Amount

Table 10-37 Optional Sequence E Binary Payout Amount

Field Tag Field Name Format Mandatory/Optional

15E New Sequence Empty field M
33E Currency, Amount 3!a15d M
53a Delivery Agent A or J O
86a Intermediary 2 A or J O
56a Intermediary A or J O
57a Receiving Agent A or J M
58a Beneficiary Institution A or J O

Table 10-38 Optional Sequence F Barrier Block

Field Tag Field Name Format Mandatory/Optional

15F New Sequence Empty field M
22G Type of Barrier 4!c M
17C Barrier Event Equal 1!a O
Modifier
37J Barrier Level 12d M
37L Lower Barrier Level 12d O
14S Barrier Settlement Rate 3!a2n[/4!n/4!c] O
Source

10-15
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-38 (Cont.) Optional Sequence F Barrier Block

Field Tag Field Name Format Mandatory/Optional

29I Barrier Determination 4!c O
Business Days
14H All Barrier Dates 4!c O
Business Day
Convention
14K Interim Barrier Dates 4!c O
Business Day
Convention
14L Barrier Event End Date 4!c O
Business Day
Convention
14M Barrier Time Type 4!c M
29O Continuous Time Period 4!c/4!n4!n O
14N Spot Market 4!c O
29J Barrier Event 4!c/4!n O
Determination Time
14O Barrier Event 4!c O
Determination Time
Source
33Z Rebate Amount 15d O
30a Rebate Amount F or J O
Payment Date
84a Barrier Determination A, B, D, or J O
Agent

Table 10-39 Optional Sub-sequence F1 Barrier Window Block

Field Tag Field Name Format Mandatory/Optional

30I Barrier Monitoring 8!n[/8!n] M
Period

Table 10-40 Optional Sequence G Binary Block

Field Tag Field Name Format Mandatory/Optional

15G New Sequence Empty field M
32Q Currency Pair 3!a/3!a M

Table 10-41 Optional Sequence H Non Deliverable Option Block

Field Tag Field Name Format Mandatory/Optional

15H New Sequence Empty field M
32E Settlement Currency 3!a M
26K Calculation Agent 4!c O
35C Digital Token Identifier 9x[/30x] O

10-16
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-42 Optional Sequence I Early Termination

Field Tag Field Name Format Mandatory/Optional

15I New Sequence Empty field M
12G Early Termination Style 4!c M
30T Early Termination Date 8!n O
22Y Frequency of Early 4!c O
Termination
85a Exercising Party A, D, or J O
88a Non-Exercising Party A, D, or J O
84a Calculation Agent A, B, D, or J M
30Y Commencement Date 8!n O
29L Expiry Details 8!n/4!c/4!n O
29E Earliest Exercise Time 4!c/4!n O
29M Latest Exercise Time 4!c/4!n O
17I Cash Settlement 1!a O
29N Cash Settlement 8!n/4!c/4!n O
Valuation Details
30Z Cash Settlement 8!n O
Payment Date
14S Settlement Rate Source 3!a2n[/4!n/4!c] O

Table 10-43 Optional Sequence L Additional Amounts

Field Tag Field Name Format Mandatory/Optional

15J New Sequence Empty field M
18A Number of Repetitions 5n M
30F Payment Date 8!n M
32H Currency, Payment [N]3!a15d M
Amount
53a Delivery Agent A or J O
86a Intermediary 2 A or J O
56a Intermediary A or J O
57a Receiving Agent A or J M

10.1.5 MT 320 Fixed Loan/Deposit Confirmation

This topic describes the MT 320 Fixed Loan/Deposit Confirmation messages.
This message is exchanged to confirm a fixed term loan/deposit contract, in order to confirm/
notify the details of:
• a new contract between the parties
• an amendment to a previously agreed contract
• the cancellation of a confirmation
• a rolled over/renewed contract between the parties the maturity of a contract

10-17
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

This message is exchanged by or on behalf of the institutions or corporate, party A

and party B, who have agreed to a fixed term loan/deposit contract. A money broker
may also send this message to the two parties (party A and party B) for which he
arranged the deal. Maximum Length: 10000

Table 10-44 Format Specifications: Mandatory Sequence A General Information

Field Tag Field Name Format Mandatory/Optional

15A New Sequence Empty field M
20 Sender's Reference 16x M
21 Related Reference 16x O
22A Type of Operation 4!c M
94A Scope of Operation 4!c O
22B Type of Event 4!c M
22C Common Reference 4!a2!c4!n4!a2!c M
21N Contract Number 16x O
Party A
82a Party A A, D, or J M
87a Party B A, D, or J M
83a Fund or Instructing A, D, or J O
Party
77D Terms and Conditions 6*35x O

Table 10-45 Mandatory Sequence B Transaction Details

Field Tag Field Name Format Mandatory/Optional

15B New Sequence Empty field M
17R Party A's Role 1!a M
30T Trade Date 8!n M
30V Value Date 8!n M
30P Maturity Date 8!n M
32B Currency and 3!a15d M
Principal Amount
32H Amount to be Settled [N]3!a15d O
30X Next Interest Due 8!n O
Date
34E Currency and Interest [N]3!a15d M
Amount
37G Interest Rate [N]12d M
14D Day Count Fraction 7x M
30F Last Day of the First 8!n O
Interest Period
38J Number of Days 1!a3!n O

10-18
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-46 Mandatory Sequence C Settlement Instructions for Amounts Payable by

Party A

Field Tag Field Name Format Mandatory/Optional

15C New Sequence Empty field M
53a Delivery Agent A, D, or J O
86a Intermediary 2 A, D, or J O
56a Intermediary A, D, or J O
57a Receiving Agent A, D, or J M
58a Beneficiary Institution A, D, or J O

Table 10-47 Mandatory Sequence D Settlement Instructions for Amounts Payable by

Party B

Field Tag Field Name Format Mandatory/Optional

15D New Sequence Empty field M
53a Delivery Agent A, D, or J O
86a Intermediary 2 A, D, or J O
56a Intermediary A, D, or J O
57a Receiving Agent A, D, or J M
58a Beneficiary Institution A, D, or J O

Table 10-48 Optional Sequence F Settlement Instructions for Interests Payable by

Party B

Field Tag Field Name Format Mandatory/Optional

15F New Sequence Empty field M
53a Delivery Agent A, D, or J O
86a Intermediary 2 A, D, or J O
56a Intermediary A, D, or J O
57a Receiving Agent A, D, or J M
58a Beneficiary Institution A, D, or J O

Table 10-49 Optional Sequence G Tax Information

Field Tag Field Name Format Mandatory/Optional

15G New Sequence Empty field M
37L Tax Rate 12d M
33B Transaction Currency 3!a15d M
and Net Interest
Amount
36 Exchange Rate 12d O
33E Reporting Currency and 3!a15d O
Tax Amount

10-19
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-50 Optional Sequence H Additional Information

Field Tag Field Name Format Mandatory/Optional

15H New Sequence Empty field M
29A Contact Information 4*35x O
24D Dealing Method 4!c[/35x] O
84a Dealing Branch Party A, B, D, or J O
A
85a Dealing Branch Party A, B, D, or J O
B
88a Broker Identification A, D, or J O
71F Broker's Commission 3!a15d O
26H Counterparty's 16x O
Reference
21G Broker's Reference 16x O
72 Sender to Receiver 6*35x O
Information

Table 10-51 Optional Sequence I Additional Amounts

Field Tag Field Name Format Mandatory/Optional

15I New Sequence Empty field M
18A Number of Repetitions 5n M
30F Payment Date 8!n M
32H Currency, Payment [N]3!a15d M
Amount
53a Delivery Agent A, D, or J O
86a Intermediary 2 A, D, or J O
56a Intermediary A, D, or J O
57a Receiving Agent A, D, or J M

10.1.6 MT 330 Call/Notice Loan/Deposit Confirmation

This topic describes the MT 330 Call/Notice Loan/Deposit Confirmation.
This message is exchanged to confirm a call/notice loan/deposit contract. The
message is used to confirm/notify the details of:
• a new contract between the parties
• an amendment to a previously agreed contract
• the cancellation of a confirmation
• an increase or decrease in the balance of the account, in an already agreed
contract
• a change in the interest rate
• a change in the period of notice the closing of a contract, i.e. final redemption of
the loan/deposit balance to zero and all interest paid

10-20
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

This message is sent by or on behalf of the institution or corporate, party A and party B, who
have agreed to a call/notice loan/deposit contract. Maximum Length: 10000

Table 10-52 Format Specifications: Mandatory Sequence A General Information

Field Tag Field Name Format Mandatory/Optional

15A New Sequence Empty field M
20 Sender's Reference 16x M
21 Related Reference 16x O
22A Type of Operation 4!c M
94A Scope of Operation 4!c O
22B Type of Event 4!c M
22C Common Reference 4!a2!c4!n4!a2!c M
21N Contract Number Party 16x O
A
82a Party A A, D, or J M
87a Party B A, D, or J M
83a Fund or Instructing A, D, or J O
Party
77D Terms and Conditions 6*35x O

Table 10-53 Mandatory Sequence B Transaction Details

Field Tag Field Name Format Mandatory/Optional

15B New Sequence Empty field M
17R Party A's Role 1!a M
30T Trade Date 8!n M
30V Value Date 8!n M
38A Period of Notice 3n M
32B Currency and Balance 3!a15d O
32H Principal Amount to be [N]3!a15d O
Settled
30X Interest Due Date 8!n O
34E Currency and Interest [N]3!a15d O
Amount
37G Interest Rate [N]12d M
14D Day Count Fraction 7x M
30F Last Day of the Next 8!n O
Interest Period
38J Number of Days 1!a3!n O

Table 10-54 Mandatory Sequence C Settlement Instructions for Amounts Payable by

Party A

Field Tag Field Name Format Mandatory/Optional

15C New Sequence Empty field M
53a Delivery Agent A, D, or J O

10-21
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-54 (Cont.) Mandatory Sequence C Settlement Instructions for Amounts

Payable by Party A

Field Tag Field Name Format Mandatory/Optional

86a Intermediary 2 A, D, or J O
56a Intermediary A, D, or J O
57a Receiving Agent A, D, or J M
58a Beneficiary Institution A, D, or J O

Table 10-55 Mandatory Sequence D Settlement Instructions for Amounts

Payable by Party B

Field Tag Field Name Format Mandatory/Optional

15D New Sequence Empty field M
53a Delivery Agent A, D, or J O
86a Intermediary 2 A, D, or J O
56a Intermediary A, D, or J O
57a Receiving Agent A, D, or J M
58a Beneficiary Institution A, D, or J O

Table 10-56 Optional Sequence E Settlement Instructions for Interests Payable

by Party A

Field Tag Field Name Format Mandatory/Optional

15E New Sequence Empty field M
53a Delivery Agent A, D, or J O
86a Intermediary 2 A, D, or J O
56a Intermediary A, D, or J O
57a Receiving Agent A, D, or J M
58a Beneficiary Institution A, D, or J O

Table 10-57 Optional Sequence E Settlement Instructions for Interests Payable

by Party A

Field Tag Field Name Format Mandatory/Optional

15F New Sequence Empty field M
53a Delivery Agent A, D, or J O
86a Intermediary 2 A, D, or J O
56a Intermediary A, D, or J O
57a Receiving Agent A, D, or J M
58a Beneficiary Institution A, D, or J O

10-22
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-58 Optional Sequence G Tax Information

Field Tag Field Name Format Mandatory/Optional

15G New Sequence Empty field M
37L Tax Rate 12d M
33B Transaction Currency 3!a15d M
and Net Interest
Amount
36 Exchange Rate 12d O
33E Reporting Currency and 3!a15d O
Tax Amount

Table 10-59 Optional Sequence H Additional Information

Field Tag Field Name Format Mandatory/Optional

15H New Sequence Empty field M
29A Contact Information 4*35x O
24D Dealing Method 4!c[/35x] O
84a Dealing Branch Party A A, B, D, or J O
85a Dealing Branch Party B A, B, D, or J O
26H Counterparty's 16x O
Reference
72 Sender to Receiver 6*35x O
Information

10.1.7 MT 340 Forward Rate Agreement Confirmation

This topic describes the MT 340 Forward Rate Agreement Confirmation.
This message is exchanged by or on behalf of the institutions or corporates, party A and
party B, who have agreed to a forward rate agreement (FRA).
The confirmed transaction is covered by an ISDA (International Swaps and Derivatives
Association), Deutscher Rahmenvertrag für Finanztermingeschäfte, FRABBA (British
Bankers' Association) or AFB (Association Française de Banques) Master Agreement. These
agreements are either signed or under negotiation.
A money broker may also send this message to the two parties (party A and party B) for
which he arranged the deal. If there are two money brokers involved in arranging a deal
between party A and party B, this message is also exchanged between these money brokers.
The message is used to confirm/notify the details of:
• a new contract between the parties
• an amendment to a previously agreed contract
• the cancellation of a confirmation
Maximum Length: 10000

10-23
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-60 Format Specifications: Mandatory Sequence A General Information

Field Tag Field Name Format Mandatory/Optional

15A New Sequence Empty field M
20 Sender's Reference 16x M
21 Related Reference 16x O
22A Type of Operation 4!c M
94A Scope of Operation 4!c O
22C Common Reference 4!a2!c4!n4!a2!c M
23D Type of FRA 10a M
21N Contract Number 16x O
Party A
21B Contract Number 16x O
Party B
82a Party A A or D M
87a Party B A or D M
77H Type, Date, Version of 6a[/8!n][//4!n] M
the Agreement
14C Year of Definitions 4!n O

Table 10-61 Mandatory Sequence B Transaction Details

Field Tag Field Name Format Mandatory/Optional

15B New Sequence Empty field M
30T Trade Date 8!n M
32B Currency, Notional 3!a15d M
Amount
30F Effective Date 8!n M
30P Termination Date 8!n M
37M Fixed Rate [N]12d M
14F Floating Rate Option 24x M

Table 10-62 Optional Subsequence B1 AFB and FRABBA Details

Field Tag Field Name Format Mandatory/Optional

30V Fixing Date 8!n M
38D Contract Period 4n M

Table 10-63 Mandatory Subsequence B2 Other Details

Field Tag Field Name Format Mandatory/Optional

38G Designated Maturity 2n1!a/2n1!a M
14D Floating Rate Day 7x M
Count Fraction
17F FRA Discounting 1!a M
18A Number of Repetitions 5n M

10-24
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-63 (Cont.) Mandatory Subsequence B2 Other Details

Field Tag Field Name Format Mandatory/Optional

22B Financial Centre 4!c M

Table 10-64 Mandatory Sequence C Settlement Instructions for Settlement Amount

Payable by Party B

Field Tag Field Name Format Mandatory/Optional

15C New Sequence Empty field M
53a Delivery Agent A, D, or J O
86a Intermediary 2 A, D, or J O
56a Intermediary A, D, or J O
57a Receiving Agent A, D, or J M
58a Beneficiary Institution A, D, or J O

Table 10-65 Mandatory Sequence D Settlement Instructions for Settlement Amount

Payable by Party A

Field Tag Field Name Format Mandatory/Optional

15D New Sequence Empty field M
53a Delivery Agent A, D, or J O
86a Intermediary 2 A, D, or J O
56a Intermediary A, D, or J O
57a Receiving Agent A, D, or J M
58a Beneficiary Institution A, D, or J O

Table 10-66 Optional Sequence E Additional Information

Field Tag Field Name Format Mandatory/Optional

15E New Sequence Empty field M
29A Contact Information 4*35x O
24D Dealing Method 4!c[/35x] O
88a Broker Identification A or D O
71F Broker's Commission 3!a15d O
21G Broker's Reference 16x O
72 Sender to Receiver 6*35x O
Information

Table 10-67 Optional Sequence F Additional Amounts

Field Tag Field Name Format Mandatory/Optional

15F New Sequence Empty field M
18A Number of Repetitions 5n M
30F Payment Date 8!n M

10-25
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-67 (Cont.) Optional Sequence F Additional Amounts

Field Tag Field Name Format Mandatory/Optional

32H Currency, Payment [N]3!a15d M
Amount
53a Delivery Agent A, D, or J O
86a Intermediary 2 A, D, or J O
56a Intermediary A, D, or J O
57a Receiving Agent A, D, or J M

10.1.8 MT 341 Forward Rate Agreement Settlement Confirmation

This topic describes the MT 341 Forward Rate Agreement Settlement Confirmation.
This message is exchanged by or on behalf of the institutions or corporates, party A
and party B, who have agreed to a forward rate agreement (FRA). It is used to confirm
the settlement details of the forward rate agreement when the settlement rate has
been fixed on the fixing date. The message is also used for:
• an amendment to a previously agreed settlement message
• the cancellation of a settlement message
Maximum Length: 10000

Table 10-68 Format Specifications: Mandatory Sequence A General Information

Field Tag Field Name Format Mandatory/Optional

15A New Sequence Empty field M
20 Sender's Reference 16x M
21 Related Reference 16x O
22A Type of Operation 4!c M
94A Scope of Operation 4!c O
22C Common Reference 4!a2!c4!n4!a2!c M
23D Type of FRA 10a M
21N Contract Number 16x O
Party A
21B Contract Number 16x O
Party B
82a Party A A or D M
87a Party B A or D M
29A Contact Information 4*35x O
72 Sender to Receiver 6*35x O
Information

Table 10-69 Mandatory Sequence B Transaction Details

Field Tag Field Name Format Mandatory/Optional

15B New Sequence Empty field M

10-26
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-69 (Cont.) Mandatory Sequence B Transaction Details

Field Tag Field Name Format Mandatory/Optional

30T Trade Date 8!n M
32B Currency, Notional 3!a15d M
Amount
30F Effective Date 8!n M
30P Termination Date 8!n M
37M Fixed Rate [N]12d M

Table 10-70 Optional Subsequence B1 AFB and FRABBA Details

Field Tag Field Name Format Mandatory/Optional

30V Fixing Date 8!n O
38D Contract Period 4n O

Table 10-71 Mandatory Sequence C Settlement Instructions for the Settlement

Amount

Field Tag Field Name Format Mandatory/Optional

15C New Sequence Empty field M
37R Settlement Rate [N]12d M
34E Settlement Currency [N]3!a15d M
and Amount
53a Delivery Agent A, D, or J O
86a Intermediary 2 A, D, or J O
56a Intermediary A, D, or J O
57a Receiving Agent A, D, or J M
58a Beneficiary Institution A, D, or J O

10.1.9 MT 350 Advice of Loan/Deposit Interest Payment

This topic describes the MT 350 Advice of Loan/Deposit Interest Payment
It is used to inform that an interest amount has been paid to the account of the beneficiary
with the receiving agent mentioned in the message. The message may also be used to notify
the details of:
• an amendment to a previously sent advice
• the cancellation of an advice
This message is sent by or on behalf of the institution or corporate, party A who has
borrowed cash from the institution or corporate, party B.
Maximum Length: 10000

10-27
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-72 Format Specifications

Field Tag Field Name Format Mandatory/Optional

15A New Sequence Empty field M
20 Sender's Reference 16x M
21 Related Reference 16x O
22A Type of Operation 4!c M
94A Scope of Operation 4!c O
22C Common Reference 4!a2!c4!n4!a2!c M
21N Contract Number 16x O
Party A
82a Party A A, D, or J M
87a Party B A, D, or J M
83a Fund or Instructing A, D, or J O
Party
72 Sender to Receiver 6*35x O
Information

Table 10-73 Mandatory Sequence B Interest Information

Field Tag Field Name Format Mandatory/Optional

15B New Sequence Empty field M
30G Interest Period 8!n/8!n M
32B Currency and 3!a15d M
Principal Amount
30V Value Date of Interest 8!n M
Payment
34B Currency and Interest 3!a15d M
Amount
37J Interest Rate 12d M
14D Day Count Fraction 7x M
30F Next Interest Payment 8!n O
Date

Table 10-74 Mandatory Sequence C Settlement Instructions

Field Tag Field Name Format Mandatory/Optional

15C New Sequence Empty field M
53a Delivery Agent A, D, or J O
86a Intermediary 2 A, D, or J O
56a Intermediary A, D, or J O
57a Receiving Agent A, D, or J M
58a Beneficiary Institution A, D, or J O

10-28
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-75 Optional Sequence D Tax Information and Broker's Commission

Field Tag Field Name Format Mandatory/Optional

15D New Sequence Empty field M
34B Transaction Currency 3!a15d M
and Interest Amount
33B Transaction Currency 3!a15d M
and Net Interest
Amount
36 Exchange Rate 12d O

Table 10-76 Optional Subsequence D1 Tax Details

Field Tag Field Name Format Mandatory/Optional

37L Tax Rate 12d M
33E Reporting Currency and 3!a15d M
Tax Amount

Table 10-77 Optional Subsequence D2 Broker's Commission Information

Field Tag Field Name Format Mandatory/Optional

71F Broker's Commission 3!a15d M
37L Tax Rate on Broker's 12d O
Commission
33E Reporting Currency and 3!a15d O
Tax Amount on Broker's
Commission

10.1.10 MT 360 Single Currency Interest Rate Derivative Confirmation

This topic describes the MT 360 Single Currency Interest Rate Derivative Confirmation.
This message is exchanged by or on behalf of the institutions or corporates, party A and
party B, which have agreed to a single currency interest rate swap, a cap, a collar or a floor.
The confirmed transaction is covered by a BBAIRS (British Bankers' Association Interest
Rate Swap), ISDA (International Swaps and Derivatives Association), Deutscher
Rahmenvertrag für Finanztermingeschäfte or AFB (Association Française de Banques)
Master Agreement.
The message also covers deals which are not part of an ISDA, AFB, Deutscher
Rahmenvertrag für Finanztermingeschäfte or BBAIRS Master. In this case, party A and party
B must have another bilateral agreement in place. This message may also be sent by a
money broker to the two parties (party A and party B) for which the broker arranged the deal.
If there are two money brokers involved in arranging a deal between party A and party B, this
message is also exchanged between these money brokers. The MT 360 may be used to:
• confirm the details of a new transaction between the parties
• correct a previously sent confirmation
• cancel a previously sent confirmation

10-29
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Maximum Length: 10000

Table 10-78 Format Specifications

Field Tag Field Name Format Mandatory/Optional

15A New Sequence Empty field M
20 Sender's Reference 16x M
21 Related Reference 16x O
22A Type of Operation 4!c M
94A Scope of Operation 4!c O
22C Common Reference 4!a2!c4!n4!a2!c M
23A Identification of the 10a/5a M
Swap
21N Contract Number 16x M
Party A
21B Contract Number 16x O
Party B
30T Trade Date 8!n M
30V Effective Date 8!n M
30P Termination Date 8!n M
14A Business Day 9a O
Convention
32B Currency, Notional 3!a15d M
Amount
82a Party A A or D M
87a Party B A or D M
83a Fund or Beneficiary A, D, or J O
Customer
17A Collateral Agreement 1!a O
Indicator
77H Type, Date, Version of 6a[/8!n][//4!n] M
the Agreement
77D Additional Conditions 6*35x O
14C Year of Definitions 4!n M
72 Sender to Receiver 6*35x O
Information

Table 10-79 Optional Sequence B Fixed Interest Payable by Party B

Field Tag Field Name Format Mandatory/Optional

15B New Sequence Empty field M
37U Fixed Rate 12d O
37N Details of Interest 6*35x O
Rate

10-30
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-80 Optional Subsequence B1 Interest Details

Field Tag Field Name Format Mandatory/Optional

18A Number of Repetitions 5n M
30F Payment Date 8!n M
32M Currency, Payment 3!a15d O
Amount
17F Period End Date 1!a O
Adjustment Indicator
14D Day Count Fraction 7x O
14A Business Day 9a M
Convention
18A Number of Repetitions 5n M
22B Financial Centre 4!c M

Table 10-81 Optional Sequence C Floating Interest Payable by Party B

Field Tag Field Name Format Mandatory/Optional

15C New Sequence Empty field M
14F Floating Rate Option 24x M
37J Cap Rate 12d O
37L Floor Rate 12d O
37N Details of Interest Rate 6*35x O

Table 10-82 Optional Subsequence C1 Interest Details

Field Tag Field Name Format Mandatory/Optional

14J Reset Date 5a M
Specification
14G Averaging Frequency 1!a/8!a O
and Method
38E Designated Maturity 2n1!a M
18A Number of Repetitions 5n M
30F Payment Date 8!n M
17F Period End Date 1!a M
Adjustment Indicator
14D Day Count Fraction 7x M
14A Business Day 9a M
Convention
18A Number of Repetitions 5n M
22B Financial Centre 4!c M
37R Spread [N]12d O

10-31
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-83 Optional Subsequence C2 Compounding Details

Field Tag Field Name Format Mandatory/Optional

22D Compounding Type 4!c M
18A Number of Repetitions 5n M
30X Compounding Date 8!n M

Table 10-84 Optional Subsequence C3 Interpolation for Stub Periods

Field Tag Field Name Format Mandatory/Optional

38G First Stub Period, 2n1!a/2n1!a O
Interpolation Period
38H Last Stub Period, 2n1!a/2n1!a O
Interpolation Period

Table 10-85 Mandatory Sequence D Payment Instructions for Interest Payable

by Party B

Field Tag Field Name Format Mandatory/Optional

15D New Sequence Empty field M
53a Delivery Agent A or D O
56a Intermediary A or D O
86a Second Intermediary A or D O
57a Receiving Agent A or D M

Table 10-86 Optional Sequence E Fixed Interest Payable by Party A

Field Tag Field Name Format Mandatory/Optional

15E New Sequence Empty field M
37U Fixed Rate 12d O
37N Details of Interest 6*35x O
Rate

Table 10-87 Optional Subsequence E1 Interest Details

Field Tag Field Name Format Mandatory/Optional

18A Number of Repetitions 5n M
30F Payment Date 8!n M
32M Currency, Payment 3!a15d O
Amount
17F Period End Date 1!a O
Adjustment Indicator
14D Day Count Fraction 7x O
14A Business Day 9a M
Convention
18A Number of Repetitions 5n M

10-32
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-87 (Cont.) Optional Subsequence E1 Interest Details

Field Tag Field Name Format Mandatory/Optional

22B Financial Centre 4!c M

Table 10-88 Optional Sequence F Floating Interest Payable by Party A

Field Tag Field Name Format Mandatory/Optional

15F New Sequence Empty field M
14F Floating Rate Option 24x M
37J Cap Rate 12d O
37L Floor Rate 12d O
37N Details of Interest Rate 6*35x O

Table 10-89 Optional Subsequence F1 Interest Details

Field Tag Field Name Format Mandatory/Optional

14J Reset Date 5a M
Specification
14G Averaging Frequency 1!a/8!a O
and Method
38E Designated Maturity 2n1!a M
18A Number of Repetitions 5n M
30F Payment Date 8!n M
17F Period End Date 1!a M
Adjustment Indicator
14D Day Count Fraction 7x M
14A Business Day 9a M
Convention
18A Number of Repetitions 5n M
22B Financial Centre 4!c M
37R Spread [N]12d O
Field Tag Field Name Format Mandatory/Optional
22D Compounding Type 4!c M
18A Number of Repetitions 5n M
30X Compounding Date 8!n M

Table 10-90 Optional Subsequence F3 Interpolation for Stub Periods

Field Tag Field Name Format Mandatory/Optional

38G First Stub Period, 2n1!a/2n1!a O
Interpolation Period
38H Last Stub Period, 2n1!a/2n1!a O
Interpolation Period

10-33
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-91 Mandatory Sequence G Payment Instructions for Interest Payable

by Party A

Field Tag Field Name Format Mandatory/Optional

15G New Sequence Empty field M
53a Delivery Agent A or D O
56a Intermediary A or D O
86a Second Intermediary A or D O
57a Receiving Agent A or D M

Table 10-92 Optional Sequence H Amortising Schedule

Field Tag Field Name Format Mandatory/Optional

15H New Sequence Empty field M
18A Number of Repetitions 5n M
30G Variable Notional Start 8!n/8!n M
and End Date
32U Outstanding Notional 3!a15d M
Currency and Amount
14A Business Day 9a M
Convention
18A Number of Repetitions 5n M
22B Financial Centre 4!c M

Table 10-93 Optional Sequence L Additional Amounts Payable by Party B

Field Tag Field Name Format Mandatory/Optional

15L New Sequence Empty field M
18A Number of Repetitions 5n M
22E Type of Payment 4!c M
30F Payment Date 8!n M
32M Currency, Payment 3!a15d M
Amount
14A Business Day 9a M
Convention
18A Number of Repetitions 5n M
22B Financial Centre 4!c M
53a Delivery Agent A or D O
56a Intermediary A or D O
86a Second Intermediary A or D O
57a Receiving Agent A or D O

Table 10-94 Optional Sequence M Additional Amounts Payable by Party A

Field Tag Field Name Format Mandatory/Optional

15M New Sequence Empty field M

10-34
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-94 (Cont.) Optional Sequence M Additional Amounts Payable by Party

A

Field Tag Field Name Format Mandatory/Optional

18A Number of Repetitions 5n M
22E Type of Payment 4!c M
30F Payment Date 8!n M
32M Currency, Payment 3!a15d M
Amount
14A Business Day 9a M
Convention
18A Number of Repetitions 5n M
22B Financial Centre 4!c M
53a Delivery Agent A or D O
56a Intermediary A or D O
86a Second Intermediary A or D O
57a Receiving Agent A or D O

Table 10-95 Optional Sequence N Optional General Information

Field Tag Field Name Format Mandatory/Optional

15N New Sequence Empty field M
29A Contact Information 4*35x O
24D Dealing Method 4!c[/35x] O
88a Broker Identification A or D O
71F Broker's Commission 3!a15d O
21G Broker's Reference 16x O

10.1.11 MT 361 Cross Currency Interest Rate Swap Confirmation

This topic describes the MT 361 Cross Currency Interest Rate Swap Confirmation.
This message is exchanged by or on behalf of the institutions or corporates, party A and
party B, which have agreed to a cross currency interest rate swap covered by a BBAIRS
(British Bankers' Association Interest Rate Swap), Deutscher Rahmenvertrag für
Finanztermingeschäfte or an ISDA (International Swaps and Derivatives Association) Master
Agreement. The message also covers deals which are not part of an ISDA, Deutscher
Rahmenvertrag für Finanztermingeschäfte or BBAIRS Master. In this case, party A and party
B must have another bilateral agreement in place, except under AFB (Association Française
de Banques) Master (until the AFB does define the interbank confirmation for cross currency
swaps, the MT 361 cannot be used to confirm such transactions).
This message may also be sent by a money broker to the two parties (party A and party B)
for which the broker arranged the deal. If there are two money brokers involved in arranging a
deal between party A and party B, this message is also exchanged between these money
brokers. The message may be used to:
• confirm the details of a new transaction between the parties
• correct a previously sent confirmation

10-35
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

• cancel a previously sent confirmation

Maximum Length: 10000

10.1.12 MT 362 Interest Rate Reset/Advice of Payment

This topic describes the MT 362 Interest Rate Reset/ Advice of payment.
This message is exchanged by or on behalf of the financial institutions, Party A and
Party B, who have agreed to a single or cross currency interest rate derivative
transaction, including caps, collars and floors.
This message may be used to:
• advise the details of the determination of the floating interest rate(s)
• advise the details of the payment of interest at the end of an interest period
• cancel a previously sent reset/advice
• correct errors in a previously sent reset/advice
Maximum Length: 2000

Table 10-96 Format Specifications

Field Tag Field Name Format Mandatory/Optional

15A New Sequence Empty field M
20 Sender's Reference 16x M
21 Related Reference 16x O
22A Type of Operation 4!c M
94A Scope of Operation 4!c O
22C Common Reference 4!a2!c4!n4!a2!c M
23A Identification of the 10a/5a M
Swap
21N Contract Number 16x M
Party A
21B Contract Number 16x O
Party B
30V Effective Date 8!n M
30P Termination Date 8!n M
82a Party A A or D M
87a Party B A or D M
83a Fund or Beneficiary A, D, or J O
Customer
29A Contact Information 4*35x O
72 Sender to Receiver 6*35x O
Information

Table 10-97 Optional Sequence B Interest Rate/Principal Payable by Party B

Field Tag Field Name Format Mandatory/Optional

15B New Sequence Empty field M

10-36
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-97 (Cont.) Optional Sequence B Interest Rate/Principal Payable by

Party B

Field Tag Field Name Format Mandatory/Optional

33F Calculation Notional 3!a15d M
Currency and Amount
30X Period Start Date 8!n M
30Q Period End Date 8!n O
37G Reset Rate [N]12d M
37J Cap Rate 12d O
37L Floor Rate 12d O
37R Spread [N]12d M
37M Total Rate [N]12d M
30F Payment Date 8!n M
32H Currency, Interest [N]3!a15d O
Amount
33E Currency, Principal 3!a15d O
Exchange Amount
37N Details of Interest 6*35x O
Rate

Table 10-98 Optional Sequence C (Net) Amount(s) Payable by Party B

Field Tag Field Name Format Mandatory/Optional

15C New Sequence Empty field M
18A Number of Repetitions 5n M
30F Payment Date 8!n M
32M Currency, Payment 3!a15d M
Amount
53a Delivery Agent A or D O
56a Intermediary A or D O
86a Second Intermediary A or D O
57a Receiving Agent A or D M

Table 10-99 Optional Sequence D Interest Rate/Principal Payable by Party A

Field Tag Field Name Format Mandatory/Optional

15D New Sequence Empty field M
33F Calculation Notional 3!a15d M
Currency and Amount
30X Period Start Date 8!n M
30Q Period End Date 8!n O
37G Reset Rate [N]12d M
37J Cap Rate 12d O
37L Floor Rate 12d O
37R Spread [N]12d M

10-37
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-99 (Cont.) Optional Sequence D Interest Rate/Principal Payable by Party A

Field Tag Field Name Format Mandatory/Optional

37M Total Rate [N]12d M
30F Payment Date 8!n M
32H Currency, Interest [N]3!a15d O
Amount
33E Currency, Principal 3!a15d O
Exchange Amount
37N Details of Interest Rate 6*35x O

Table 10-100 Optional Sequence E (Net) Amount(s) Payable by Party A

Field Tag Field Name Format Mandatory/Optional

15E New Sequence Empty field M
18A Number of Repetitions 5n M
30F Payment Date 8!n M
32M Currency, Payment 3!a15d M
Amount
53a Delivery Agent A or D O
56a Intermediary A or D O
86a Second Intermediary A or D O
57a Receiving Agent A or D M

Processing Incoming MT362

During STP, the system picks up an incoming MT362 message and extracts the
following details from Sequence D for auto confirmation:
• The currency and interest amount to be paid (Field 32H)
• The currency and principal to be exchanged (Field 33E)
• The payment due date (Field 30F)
After the above details are extracted, the corresponding interest and principal
schedule on that date is compared with the details extracted as mentioned above. The
following details are considered for matching:
• The schedule due date
• The amount of the schedule
• The currency of the schedule
• The pay and receive flag of the schedule
If the details match, the schedule will be marked as ‘Confirmed’. The same approach
is followed for party B whose details are extracted from sequence B of the message.
After the message is processed, the message is marked as ‘Processed’. You can view
the message status in the incoming browser. After the corresponding schedules are
marked as confirmed, they can be viewed in the contract confirmation screen. After
confirmation, ‘Media’ will be updated as ‘SWIFT’ and ‘Authorization Status’ as ‘Auto’ in
this screen.

10-38
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

RCON is triggered post confirmation and can be viewed under ‘Contract Online’ screen.

10.1.13 MT 364 Single Currency Interest Rate Derivative Termination/

Recouponing Confirmation
This topic describes the MT 364 single currency interest rate derivative termination/
recouponing confirmation.
This message is exchanged by or on behalf of the institutions or corporates, party A and
party B, which have agreed to the termination, partial termination or recouponing of a single
currency interest rate swap, a cap, a collar or a floor. The terminated/recouponed transaction
is covered by a BBAIRS, ISDA or AFB or another bilateral agreement.
This message may be used to:
• confirm the details of the partial or full termination of an existing transaction between the
parties
• confirm the details of the recouponing of an existing transaction
• correct a previously sent termination/recouponing
• cancel a previously sent termination/recouponing
Maximum Length: 10000

Table 10-101 Format Specifications: Mandatory Sequence A General Information

Field Tag Field Name Format Mandatory/Optional

15A New Sequence Empty field M
20 Sender's Reference 16x M
21 Related Reference 16x O
22A Type of Operation 4!c M
94A Scope of Operation 4!c O
22B Type of Event 4!c M
22C Common Reference 4!a2!c4!n4!a2!c M
23A Identification of the 10a/5a M
Swap
21N Contract Number Party 16x M
A
21B Contract Number Party 16x O
B
30T Termination/ 8!n M
Recouponing Trade
Date
30Q Termination/ 8!n M
Recouponing Effective
Date
30P Original Termination 8!n M
Date
30V Original Effective Date 8!n M
32B Current Currency, 3!a15d M
Notional Amount
82a Party A A or D M

10-39
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-101 (Cont.) Format Specifications: Mandatory Sequence A General

Information

Field Tag Field Name Format Mandatory/Optional

87a Party B A or D M
83a Fund or Beneficiary A, D, or J O
Customer
22D Accrual of Interest 4!c O
Specification
32G New Currency, Notional 3!a15d O
Amount
37N Details of Interest Rate 6*35x O
29A Contact Information 4*35x O
72 Sender to Receiver 6*35x O
Information

Table 10-102 Optional Sequence B Fixed Interest Payable by Party B

Field Tag Field Name Format Mandatory/Optional

15B New Sequence Empty field M
37U Current Fixed Rate 12d M
37P New Fixed Rate 12d O

Table 10-103 Optional Sequence E Fixed Interest Payable by Party A

Field Tag Field Name Format Mandatory/Optional

15E New Sequence Empty field M
37U Current Fixed Rate 12d M
37P New Fixed Rate 12d O

Table 10-104 Optional Sequence L Fee Payable by Party B

Field Tag Field Name Format Mandatory/Optional

15L New Sequence Empty field M
30F Payment Date 8!n M
32M Currency, Payment 3!a15d M
Amount
53a Delivery Agent A or D O
56a Intermediary A or D O
86a Second Intermediary A or D O
57a Receiving Agent A or D M

Table 10-105 Optional Sequence M Fee Payable by Party A

Field Tag Field Name Format Mandatory/Optional

15M New Sequence Empty field M

10-40
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-105 (Cont.) Optional Sequence M Fee Payable by Party A

Field Tag Field Name Format Mandatory/Optional

30F Payment Date 8!n M
32M Currency, Payment 3!a15d M
Amount
53a Delivery Agent A or D O
56a Intermediary A or D O
86a Second Intermediary A or D O
57a Receiving Agent A or D M

10.1.14 MT 365 Cross Currency Interest Rate Swap Termination/

Recouponing Confirmation
This topic describes the MT 365 Cross Currency Interest Rate Swap Termination/
Recouponing Confirmation.
This message is exchanged by or on behalf of the institutions or corporates, party A and
party B, which have agreed to the termination, partial termination or recouponing of a cross
currency interest rate swap. The terminated/recouponed transaction is covered by a BBAIRS,
ISDA or another bilateral agreement.
This message may be used to:
• confirm the details of the partial or full termination of an existing transaction between the
parties
• confirm the details of the recouponing of an existing transaction
• correct a previously sent termination/recouponing
• cancel a previously sent termination/recouponing
Maximum Length: 10000

Table 10-106 Format Specifications: Mandatory Sequence A General Information

Field Tag Field Name Format Mandatory/Optional

15A New Sequence Empty field M
20 Sender's Reference 16x M
21 Related Reference 16x O
22A Type of Operation 4!c M
94A Scope of Operation 4!c O
22B Type of Event 4!c M
22C Common Reference 4!a2!c4!n4!a2!c M
23A Identification of the 10a/5a M
Swap
21N Contract Number Party 16x M
A
21B Contract Number Party 16x O
B

10-41
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-106 (Cont.) Format Specifications: Mandatory Sequence A General

Information

Field Tag Field Name Format Mandatory/Optional

30T Termination/ 8!n M
Recouponing Trade
Date
30Q Termination/ 8!n M
Recouponing Effective
Date
30P Original Termination 8!n M
Date
30V Original Effective Date 8!n M
32B Party B Current 3!a15d M
Currency, Notional
Amount
33B Party A Current 3!a15d M
Currency, Notional
Amount
82a Party A A or D M
87a Party B A or D M
83a Fund or Beneficiary A, D, or J O
Customer
22D Accrual of Interest 4!c O
Specification
32G Party B New Currency, 3!a15d O
Notional Amount
33E Party A New Currency, 3!a15d O
Notional Amount
37N Details of Interest Rate 6*35x O
29A Contact Information 4*35x O
72 Sender to Receiver 6*35x O
Information

Table 10-107 Optional Sequence B Fixed Interest Payable by Party B

Field Tag Field Name Format Mandatory/Optional

15B New Sequence Empty field M
37U Current Fixed Rate 12d M
37P New Fixed Rate 12d O

Table 10-108 Optional Sequence E Fixed Interest Payable by Party A

Field Tag Field Name Format Mandatory/Optional

15E New Sequence Empty field M
37U Current Fixed Rate 12d M
37P New Fixed Rate 12d O

10-42
 Chapter 10
Treasury Markets - Foreign Exchange, Money Markets and Derivatives

Table 10-109 Optional Sequence J Re-exchange of Principal Payable by Party B

Field Tag Field Name Format Mandatory/Optional

15J New Sequence Empty field M
30F Payment Date 8!n M
32M Currency, Payment 3!a15d M
Amount
53a Delivery Agent A or D O
56a Intermediary A or D O
86a Second Intermediary A or D O
57a Receiving Agent A or D M

Table 10-110 Optional Sequence K Re-exchange of Principal Payable by Party A

Field Tag Field Name Format Mandatory/Optional

15K New Sequence Empty field M
30F Payment Date 8!n M
32M Currency, Payment 3!a15d M
Amount
53a Delivery Agent A or D O
56a Intermediary A or D O
86a Second Intermediary A or D O
57a Receiving Agent A or D M

Table 10-111 Optional Sequence L Fee Payable by Party B

Field Tag Field Name Format Mandatory/Optional

15L New Sequence Empty field M
30F Payment Date 8!n M
32M Currency, Payment 3!a15d M
Amount
53a Delivery Agent A or D O
56a Intermediary A or D O
86a Second Intermediary A or D O
57a Receiving Agent A or D M

Table 10-112 Optional Sequence M Fee Payable by Party A

Field Tag Field Name Format Mandatory/Optional

15M New Sequence Empty field M
30F Payment Date 8!n M
32M Currency, Payment 3!a15d M
Amount
53a Delivery Agent A or D O
56a Intermediary A or D O

10-43
 Chapter 10
CoSecurities Markets

Table 10-112 (Cont.) Optional Sequence M Fee Payable by Party A

Field Tag Field Name Format Mandatory/Optional

86a Second Intermediary A or D O
57a Receiving Agent A or D M

10.2 CoSecurities Markets

This topic contains the following sub-topics:
• MT 517 Trade Confirmation Affirmation
This topic describes the MT 517 trade confirmation affirmation.
• MT 518 Market-Side Securities Trade Confirmation
This topic describes the MT 518 Market-Side Securities Trade Confirmation
message.
• MT 540 Receive Free
This topic describes the MT 540 Receive Free message formats
• MT 541 Receive Against Payment
This topic describes the MT541 Receive Against Payment message.
• MT 542 Deliver Free
This topic describes the MT 542 deliver free message.
• MT 543 Deliver Against Payment
This topic describes the MT 543 deliver against payment message format
specifications.
• MT 592 Request for Cancellation
This topic describes the MT 592 request for cancellantion message and format
specifications.
• MT 598 Proprietary Message
This topic describes the MT 598 proprietary message format specifications.

10.2.1 MT 517 Trade Confirmation Affirmation

This topic describes the MT 517 trade confirmation affirmation.
This message is sent by an instructing party, e.g. client, or its authorized
representative, to a financial institution which had previously sent a trade confirmation/
contract note.
This message is used to positively affirm the details of a previously received
confirmation/ contract note. This message binds the Sender and the Receiver of the
message to the trade details contained in the confirmation being affirmed.
This message may be sent directly between the parties to the trade or via an ETC
service provider.
Maximum Length: 10000

10-44
 Chapter 10
CoSecurities Markets

Table 10-113 Format Specifications: Mandatory Sequence A General Information

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block GENL M
20C Reference Sender's Message :4!c//16x M
Reference
23G Function of the 4!c[/4!c] M
Message
98a Date/Time Preparation Date/ A, C, or E O
Time
95a Party (see qualifier P, Q, or R M
description)
25D Status Code Affirmation Status :4!c/[8c]/4!c O

Table 10-114 Mandatory Repetitive Subsequence A1 Linkages

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block LINK M
13a Number Linked Message A or B O
Identification
20C Reference (see qualifier :4!c//16x M
description)
16S NA End of Block LINK M

Table 10-115 End of Subsequence A1 Linkages

Field Tag Field Name Field Description Format Mandatory/

Optional
16S End of Block GENL M

10.2.2 MT 518 Market-Side Securities Trade Confirmation

This topic describes the MT 518 Market-Side Securities Trade Confirmation message.
This message is sent by an executing party to its trade counterparty. It is used to confirm the
details of a trade. It may also be used to:
• request the cancellation of a previously sent confirmation
• re-send a confirmation previously sent
• provide a third party with a copy of the message (be it the confirmation or request for
cancellation) being sent
This message may include, where necessary, the settlement details of the trade.
The market confirmation may be:
• exchanged directly or via an ETC service provider between two trade counterparties for
mutual comparison of the trade details

10-45
 Chapter 10
CoSecurities Markets

• sent by one trade party to allege the trade against its counterparty, either directly
or via an ETC service provider
Maximum Length: 10000
Format Specifications

Table 10-116 Mandatory Sequence A General Information

Field Tag Field Name Field Format Mandat

Description ory/
Option
al
16R Start of Block GENL M
20C Reference Sender's :4!c//16x M
Message
Reference
23G Function of the 4!c[/4!c] M
Message
98a Date/Time Preparation Date/ A, C, or E O
Time
22F Indicator Trade Transaction :4!c/[8c]/4!c M
Type

Table 10-117 Optional Repetitive Subsequence A1 Linkages

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block LINK M
13a Number Linked Message A or B O
Identification
20C Reference (see qualifier :4!c//16x M
description)
16S End of Block LINK M
16S End of Block GENL M

Table 10-118 Mandatory Sequence B Confirmation Details

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block CONFDET M
98a Date/Time (see qualifier A, B, C, or E M
description)
90a Price Deal Price A or B M
92A Rate (see qualifier :4!c//[N]15d O
description)
99A Number Count (see qualifier :4!c//[N]3!n O
description)
94a Place (see qualifier B, C, or F O
description)

10-46
 Chapter 10
CoSecurities Markets

Table 10-118 (Cont.) Mandatory Sequence B Confirmation Details

Field Tag Field Name Field Format Mandatory/

Description Optional
19A Amount Settlement :4!c//[N]3!a15d O
Amount
22a Indicator (see qualifier F or H M
description)
11A Currency (see qualifier :4!c//3!a O
description)

Table 10-119 Mandatory Repetitive Subsequence B1 Confirmation Parties

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block CONFPRTY M NA
95a Party (see qualifier P, Q, R, or S M
description)
97a Account (see qualifier A or B O
description)
98a Date/Time Processing Date/ A or C O
Time
20C Reference Processing :4!c//16x O
Reference
70a Narrative (see qualifier C or E O
description)
22F Indicator (see qualifier :4!c/[8c]/4!c O
description)
s16S NA End of Block CONFPRTY M

Table 10-120 Optional Subsequence B2 Financial Instrument Attributes

Field Tag Field Name Field Description Format Mandatory/

Optional
36B Quantity of Quantity of :4!c//4!c/15d M
Financial Financial
Instrument Instrument
Confirmed
35B NA Identification of the [ISIN1!e12!c]
Financial
Instrument
[4*35x] M NA NA NA

Table 10-121 Optional Sequence C Settlement Details

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block SETDET M

10-47
 Chapter 10
CoSecurities Markets

Table 10-121 (Cont.) Optional Sequence C Settlement Details

Field Tag Field Name Field Description Format Mandatory/

Optional
22F Indicator (see qualifier :4!c/[8c]/4!c M
description)
11A Currency (see qualifier :4!c//3!a O
description)

Table 10-122 Optional Repetitive Subsequence C1 Settlement Parties

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block SETPRTY M
95a Party (see qualifier C, P, Q, R, or S M
description)
97a Account Safekeeping A or B O
Account
98a Date/Time Processing Date/ A or C O
Time
20C Reference Processing :4!c//16x O
Reference
70a Narrative (see qualifier C or D O
description)
16S NA End of Block SETPRTY M

Table 10-123 Optional Repetitive Subsequence C2 Cash Parties

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block CSHPRTY M
95a Party (see qualifier P, Q, R, or S M
description)
97A Account (see qualifier :4!c//35x O
description)
98a Date/Time Processing Date/ A or C O
Time
20C Reference Processing :4!c//16x O
Reference
70C Narrative Party Narrative :4!c//4*35x O
16S End of Block CSHPRTY M

Table 10-124 Optional Repetitive Subsequence C3 Amounts

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block AMT M

10-48
 Chapter 10
CoSecurities Markets

Table 10-124 (Cont.) Optional Repetitive Subsequence C3 Amounts

Field Tag Field Name Field Format Mandatory/

Description Optional
17B Flag (see qualifier :4!c//1!a O
description)
19A Amount (see qualifier :4!c//[N]3!a15d M
description)
98a Date/Time Value Date/Time A or C O
92B Rate Exchange Rate :4!c//3!a/3!a/15d O
16S End of Block AMT M

Table 10-125 Optional Repetitive Sequence D Other Parties

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block REPO M
98a Date/Time (see qualifier A, B, or C O
description)
22F Indicator (see qualifier :4!c/[8c]/4!c O
description)
20C Reference (see qualifier :4!c//16x O
description)
92a Rate (see qualifier A, C, or F O
description)
99B Number Count (see qualifier :4!c//3!n O
description)
19A Amount (see qualifier :4!c//[N]3!a15d O
description)
70C Narrative Second Leg :4!c//4*35x O
Narrative
16S End of Block REPO M

Table 10-126 Optional Sequence E Two Leg Transaction Details

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block REPO M
98a Date/Time (see qualifier A, B, or C O
description)
22F Indicator (see qualifier :4!c/[8c]/4!c O
description)
20C Reference (see qualifier :4!c//16x O
description)
92a Rate (see qualifier A, C, or F O
description)
99B Number Count (see qualifier :4!c//3!n O
description)

10-49
 Chapter 10
CoSecurities Markets

Table 10-126 (Cont.) Optional Sequence E Two Leg Transaction Details

Field Tag Field Name Field Description Format Mandatory/

Optional
19A Amount (see qualifier :4!c//[N]3!a15d O
description)
70C Narrative Second Leg :4!c//4*35x O
Narrative
16S End of Block REPO M

10.2.3 MT 540 Receive Free

This topic describes the MT 540 Receive Free message formats
This message is sent by an account owner to an account servicer (account servicing
institution). The account owner may be a global custodian which has an account with
its local agent (sub custodian) or an investment management institution or a broker/
dealer which has an account with their custodian.
This message is used to instruct a receipt of financial instruments free of payment. It
may also be used to request a cancellation or pre-advise an instruction.
Maximum Length: 10000

Table 10-127 Mandatory Sequence A General Information

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block GENL M
20C Reference Sender's :4!c//16x M
Message
Reference
23G Function of the 4!c[/4!c] M
Message
98a Date/Time Preparation Date/ A,C or E O
Time

Table 10-128 Optional Repetitive Subsequence A1

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block LINK M
20C Reference (see qualifier :4!c//16x M
description)
36B Quantity of Quantity of :4!c//4!c/15d O
Financial Financial
Instrument Instrument to be
Paired-off
16S End of Block LINK M

10-50
 Chapter 10
CoSecurities Markets

Table 10-129 Mandatory Sequence B Trade Details

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block TRADDET M
94B Place Place of Trade :4!c/[8c]/4!c[/30x] O
98a Date/Time (see qualifier A, B, C, or E M
description)
90a Deal Deal Price A or B O
99A Number Count Number of Days :4!c//[N]3!n O
Accrued
35B Identification of the [ISIN1!e12!c] M
Financial
Instrument
70E Narrative (see qualifier :4!c//10*35x O
description)
16S End of Block TRADDET M

Table 10-130 Mandatory Repetitive Sequence C Financial Instrument/Account

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block FIAC M
36B Quantity of Quantity of :4!c//4!c/15d M
Financial Financial
Instrument Instrument to be
settled
95a Party Account Owner P or R O
97a Account (see qualifier A or B M
description)
16S End of Block FIAC M

Table 10-131 Optional Sequence D Two Leg Transaction Details

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block REPO M
98a Date/Time (see qualifier A, B, or C O
description)
22F Indicator (see qualifier :4!c/[8c]/4!c O
description)
20C Reference (see qualifier :4!c//16x O
description)
92a Rate (see qualifier A, C, or F O
description)
19A Amount (see qualifier :4!c//[N]3!a15d O
description)
70C Narrative Second Leg :4!c//4*35x O
Narrative

10-51
 Chapter 10
CoSecurities Markets

Table 10-131 (Cont.) Optional Sequence D Two Leg Transaction Details

Field Tag Field Name Field Description Format Mandatory/

Optional
16S End of Block REPO M

Table 10-132 Mandatory Sequence E Settlement Details

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block SETDET M
22F Indicator (see qualifier :4!c/[8c]/4!c M
description)

Table 10-133 Mandatory Repetitive Subsequence E1 Settlement Parties

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block SETPRTY M
95a Party (see qualifier C, P, Q, R, or S M
description)
97a Account Safekeeping A or B O
Account
16S End of Block SETPRTY M

Table 10-134 Optional Repetitive Subsequence E3 Amount

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block AMT M
19A Amount (see qualifier :4!c//[N]3!a15d M
description)
16S End of Block AMT M
16S End of Block SETDET M

10.2.4 MT 541 Receive Against Payment

This topic describes the MT541 Receive Against Payment message.
This message is sent by an account owner to an account servicer (account servicing
institution). The account owner may be a global custodian which has an account with
its local agent (sub custodian) or an investment management institution or a broker/
dealer which has an account with their custodian. This message is used to instruct a
receipt of financial instruments against payment. It may also be used to request a
cancellation or pre-advise an instruction.
Maximum Length: 10000
Format Specifications

10-52
 Chapter 10
CoSecurities Markets

Table 10-135 Mandatory Sequence A General Information

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block GENL M
20C Reference Sender's Message :4!c//16x M
Reference
23G Function of the 4!c[/4!c] M
Message
98a Date/Time Preparation Date/ A,C or E O
Time

Table 10-136 Optional Repetitive Subsequence A1

Field Tag Field Name Field Description Format Mandatory/

Optional
16R NA Start of Block GENL M
20C Reference Sender's Message :4!c//16x M
Reference
23G NA Function of the 4!c[/4!c] M
Message
98a Date/Time Preparation Date/ A,C or E O
Time

Table 10-137 Mandatory Sequence B Trade Details

Field Tag Field Name Field Description Format Mandatory/

Optional
16R NA Start of Block TRADDET M
94B Place Place of Trade :4!c/[8c]/4!c[/30x] O
98a Date/Time (see qualifier A, B, C, or E M
description)
90a Deal Deal Price A or B O
99A Number Count Number of Days :4!c//[N]3!n O
Accrued
35B NA Identification of the [ISIN1!e12!c] M
Financial
Instrument
70E Narrative (see qualifier :4!c//10*35x O
description)
16S NA End of Block TRADDET M

Table 10-138 Mandatory Repetitive Sequence C Financial Instrument/Account

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block FIAC M

10-53
 Chapter 10
CoSecurities Markets

Table 10-138 (Cont.) Mandatory Repetitive Sequence C Financial Instrument/Account

Field Tag Field Name Field Description Format Mandatory/

Optional
36B Quantity of Quantity of :4!c//4!c/15d M
Financial Financial
Instrument Instrument to be
settled
95a Party Account Owner P or R O
97a Account (see qualifier A or B M
description)
16S End of Block FIAC M

Table 10-139 Optional Sequence D Two Leg Transaction Details

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block REPO M
98a Date/Time (see qualifier A, B, or C O
description)
22F Indicator (see qualifier :4!c/[8c]/4!c O
description)
20C Reference (see qualifier :4!c//16x O
description)
92a Rate (see qualifier A, C, or F O
description)
19A Amount (see qualifier :4!c//[N]3!a15d O
description)
70C Narrative Second Leg :4!c//4*35x O
Narrative
16S NA End of Block REPO M

Table 10-140 Mandatory Sequence E Settlement Details

Field Tag Field Name Field Format Mandatory/

Description Optional
16R NA Start of Block SETDET M
22F Indicator (see qualifier :4!c/[8c]/4!c M
description)

Table 10-141 Mandatory Repetitive Subsequence E1 Settlement Parties

Field Tag Field Name Field Format Mandatory/

Description Optional
16R NA Start of Block SETPRTY M
95a Party (see qualifier C, P, Q, R, or S M
description)
97a Account Safekeeping A or B O
Account

10-54
 Chapter 10
CoSecurities Markets

Table 10-141 (Cont.) Mandatory Repetitive Subsequence E1 Settlement Parties

Field Tag Field Name Field Format Mandatory/

Description Optional
16S NA End of Block SETPRTY M

Table 10-142 Optional Repetitive Subsequence E3 Amount

Field Tag Field Name Field Description Format Mandatory/

Optional
16R NA Start of Block AMT M
19A Amount (see qualifier :4!c//[N]3!a15d M
description)
16S NA End of Block AMT M
16S NA End of Block SETDET M

Table 10-143 Repetitive Optional Sequence F Other Parties

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block OTHRPRTY M NA
95a Party (see qualifier C, P, R, Q or S M
description)
97A Account (see qualifier :4c//35x O
description)
70a Narrative (see qualifier E,D or C O
description)
20C Reference Reference :4c//16x O
16S End of Block OTHRPRTY M NA

10.2.5 MT 542 Deliver Free

This topic describes the MT 542 deliver free message.
This message is sent by an account owner to an account servicer (account servicing
institution). The account owner may be a global custodian which has an account with its local
agent (sub custodian) or an investment management institution or a broker/dealer which has
an account with their custodian. This message is used to instruct a delivery of financial
instruments free of payment. It may also be used to request a cancellation or pre-advise an
instruction.
Maximum Length: 10000

Table 10-144 Mandatory Sequence A General Information

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block GENL M

10-55
 Chapter 10
CoSecurities Markets

Table 10-144 (Cont.) Mandatory Sequence A General Information

Field Tag Field Name Field Description Format Mandatory/

Optional
20C Reference Sender's Message :4!c//16x M
Reference
23G Function of the 4!c[/4!c] M
Message
98a Date/Time Preparation Date/ A, C or E O
Time
99B Number Count (see qualifier :4!c//3!n O
description)

Table 10-145 Optional Repetitive Subsequence A1

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block LINK M
20C Reference (see qualifier :4!c//16x M
description)
16S End of Block LINK M
16S End of Block GENL M

Table 10-146 Mandatory Sequence B Trade Details

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block TRADDET M
94B Place Place of Trade :4!c/[8c]/4!c[/30x] O
98a Date/Time (see qualifier A, B, C, or E M
description)
90a Price Deal Price A or B O
35B Identification of [ISIN1!e12!c] M
the Financial
Instrument
16S End of Block TRADDET M

Table 10-147 Mandatory Repetitive Sequence C Financial Instrument/Account

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block FIAC M
36B Quantity of Quantity of :4!c//4!c/15d M
Financial Financial
Instrument Instrument to be
Settled
95a Party Account Owner P or R O

10-56
 Chapter 10
CoSecurities Markets

Table 10-147 (Cont.) Mandatory Repetitive Sequence C Financial Instrument/

Account

Field Tag Field Name Field Format Mandatory/

Description Optional
97a Account (see qualifier A or B M
description)
94a Place Place of B, C, or F O
Safekeeping
16S End of Block FIAC M

Table 10-148 Optional Sequence D Two Leg Transaction Details

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block REPO M
98a Date/Time Closing Date/Time A, B, or C O
22F Indicator (see qualifier :4!c/[8c]/4!c O
description)
20C Reference (see qualifier :4!c//16x O
description)
92a Rate (see qualifier A, C, or F O
description)
99B Number Count (see qualifier :4!c//3!n O
description)
19A Amount (see qualifier :4!c//[N]3!a15d O
description)
70C Narrative Second Leg :4!c//4*35x O
Narrative
16S End of Block REPO M

Table 10-149 Mandatory Sequence E Settlement Details

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block SETDET M
22F Indicator (see qualifier :4!c/[8c]/4!c M
description)

Table 10-150 Mandatory Repetitive Subsequence E1 Settlement Parties

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block SETPRTY M
95a Party (see qualifier C, P, Q, R, or S M
description)
16S End of Block SETPRTY M

10-57
 Chapter 10
CoSecurities Markets

Table 10-151 Repetitive Optional Subsequence E2 Cash Parties

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block CSHPRTY M NA
95a Party (see qualifier P, R, Q or S M
description)
97A Account (see qualifier :4c//35x O
description)
70a Narrative (see qualifier E,D or C O
description)
16S End of Block CSHPRTY M NA

Table 10-152 Optional Repetitive Subsequence E3 Amount

Field Tag Field Name Field Format Mandatory/

Description Optional
16R NA Start of Block AMT M
19A Amount (see qualifier :4!c//[N]3!a15d M
description)
16S NA End of Block AMT M
16S NA End of Block SETDET M

Table 10-153 Repetitive Optional Sequence F Other Parties

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block OTHRPRTY M NA
95a Party (see qualifier C, P, R, Q or S M
description)
97A Account (see qualifier :4c//35x O
description)
70a Narrative (see qualifier E,D or C O
description)
20C Reference Reference :4c//16x O
16S End of Block OTHRPRTY M NA

10.2.6 MT 543 Deliver Against Payment

This topic describes the MT 543 deliver against payment message format
specifications.
This message is sent by an account owner to an account servicer (account servicing
institution). The account owner may be a global custodian which has an account with
its local agent (sub custodian) or an investment management institution or a broker/
dealer which has an account with their custodian. This message is used to instruct a
delivery of financial instruments against payment. It may also be used to request a
cancellation or pre-advise an instruction.
Maximum Length: 10000

10-58
 Chapter 10
CoSecurities Markets

Table 10-154 Mandatory Sequence A General Information

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block GENL M
20C Reference Sender's Message :4!c//16x M
Reference
23G Function of the 4!c[/4!c] M
Message
98a Date/Time Preparation Date/ A, C or E O
Time
99B Number Count (see qualifier :4!c//3!n O
description)

Table 10-155 Optional Repetitive Subsequence A1

Field Tag Field Name Field Description Format Mandatory/

Optional
16R NA Start of Block LINK M
16S NA End of Block LINK M
16S End of Block GENL M NA

Table 10-156 Mandatory Sequence B Trade Details

Field Tag Field Name Field Description Format Mandatory/

Optional
16R NA Start of Block TRADDET M
94B Place Place of Trade :4!c/[8c]/4!c[/30x] O
98a Date/Time (see qualifier A, B, C, or E M
description)
90a Price Deal Price A or B O
35B NA Identification of the [ISIN1!e12!c] M
Financial
Instrument
16S NA End of Block TRADDET M

Table 10-157 Mandatory Repetitive Sequence C Financial Instrument/Account

Field Tag Field Name Field Description Format Mandatory/

Optional
16R NA Start of Block FIAC M
36B Quantity of Quantity of :4!c//4!c/15d M
Financial Financial
Instrument Instrument to be
Settled
95a Party Account Owner P or R O
97a Account (see qualifier A or B M
description)

10-59
 Chapter 10
CoSecurities Markets

Table 10-157 (Cont.) Mandatory Repetitive Sequence C Financial Instrument/Account

Field Tag Field Name Field Description Format Mandatory/

Optional
16S NA End of Block FIAC M

Table 10-158 Optional Sequence D Two Leg Transaction Details

Field Tag Field Name Field Format Mandatory/

Description Optional
16R NA Start of Block REPO M
98a Date/Time (see qualifier A, B, or C O
description)
22F Indicator (see qualifier :4!c/[8c]/4!c O
description)
20C Reference (see qualifier :4!c//16x O
description)
92a Rate (see qualifier A, C, or F O
description)
99B Number Count (see qualifier :4!c//3!n O
description)
19A Amount (see qualifier :4!c//[N]3!a15d O
description)
70C Narrative Second Leg :4!c//4*35x O
Narrative
16S NA End of Block REPO M

Table 10-159 Mandatory Sequence E Settlement Details

Field Tag Field Name Field Format Mandatory/

Description Optional
16R NA Start of Block SETDET M
22F Indicator (see qualifier :4!c/[8c]/4!c M
description)
95a Party (see qualifier C, P, Q, R, or S M
description)

Table 10-160 Repetitive Optional Subsequence E2 Cash Parties

Field Tag Field Name Field Format Mandatory/

Description Optional
16R Start of Block CSHPRTY M NA
95a Party (see qualifier P, R, Q or S M
description)
97A Account (see qualifier :4c//35x O
description)
70a Narrative (see qualifier E,D or C O
description)

10-60
 Chapter 10
CoSecurities Markets

Table 10-160 (Cont.) Repetitive Optional Subsequence E2 Cash Parties

Field Tag Field Name Field Format Mandatory/

Description Optional
16S End of Block CSHPRTY M NA

Table 10-161 Mandatory Repetitive Subsequence E3 Amount

Field Tag Field Name Field Description Format Mandatory/

Optional
16R NA Start of Block AMT M
19A Amount (see qualifier :4!c//[N]3!a15d M
description)
16S NA End of Block AMT M
16S NA End of Block SETDET M

Table 10-162 Repetitive Optional Sequence F Other Parties

Field Tag Field Name Field Description Format Mandatory/

Optional
16R Start of Block OTHRPRTY M NA
95a Party (see qualifier C, P, R, Q or S M
description)
97A Account (see qualifier :4c//35x O
description)
70a Narrative (see qualifier E,D or C O
description)
20C Reference Reference :4c//16x O
16S End of Block OTHRPRTY M NA

10.2.7 MT 592 Request for Cancellation

This topic describes the MT 592 request for cancellantion message and format specifications.
This message type is sent by a financial institution to request a second financial institution to
consider cancellation of the SWIFT message identified in the request. If the Receiver of the
request for cancellation has already acted on the message for which cancellation is
requested, the MT n92 asks for a retransfer, ie, reversal, with the beneficiary's consent.
Maximum Length: 2000

Table 10-163 Format Specifications

Field Tag Field Name Format Mandatory/Optional

20 Transaction Reference 16x M
Number
21 Related Reference 16x M
11S MT and Date of the 3!n NA
Original Message

10-61
 Chapter 10
Treasury Markets - Metals

Table 10-163 (Cont.) Format Specifications

Field Tag Field Name Format Mandatory/Optional

6!n NA NA NA
[4!n6!n] M NA NA
79 Narrative Description of 35*50x O
the Original Message
NA Copy of at least the Copy of fields O
Mandatory Fields of the
Original Message

10.2.8 MT 598 Proprietary Message

This topic describes the MT 598 proprietary message format specifications.
This message type is used by financial institutions, with their own offices, and/or with
other financial institutions with which they have established bilateral agreements. It is
used as an envelope for a specified message included in it.
It allows for the definition of a unique format for which another message type is not
available or applicable. It also allows financial institutions to use message types which
are awaiting live implementation on the SWIFT system.
Maximum Length: 10000

Table 10-164 Format Specifications

Field Tag Field Name Format Mandatory/Optional

20 Transaction Reference 16x M
Number
12 Sub-Message Type 3!n M
77E Proprietary Message 120*78x M

10.3 Treasury Markets - Metals

This topic contains the following sub-topics:
• MT 643 Notice of Drawdown/Renewal
• MT 644 Advice of Rate and Amount Fixing
This topic describes the MT 644 Advice of Rate and Amount fixing message
formats and its specifications.
• MT 645 Notice of Fee Due
This topic describes the MT 645 Notice of Fee Due message formats.
• MT 646 Payment of Principal and/or of Interest
This topic describes the MT 646 payment of principal and/or of interest message
formats.

10.3.1 MT 643 Notice of Drawdown/Renewal

10-62
 Chapter 10
Treasury Markets - Metals

This message type is sent by the agent of the facility to the providers of funds. It gives notice
of the borrower(s) request for drawdown(s)/renewal(s) on a given date. This request may
require the provision of new funds or the re-borrowing of previously disbursed funds. The MT
643 allows for the handling of drawdown(s)/renewal(s) with differing characteristics. It
specifies the currency (ies), amount(s), period(s) and interest rate origin(s).
Maximum Length: 2000

Table 10-165 Mandatory Sequence A Identification of the Facility

Field Tag Field Name Format Mandatory/Optional

20 Transaction Reference 16x M
Number
21 Related Reference 16x O
23 Further Identification 16x M
27 Sequence of Total 1!n/1!n O
29A From 4*35x O
29B To the Attention of 4*35x O
88D Borrower(s) [/1!a][/34x]4*35x NA
32A Original Facility Amount 6!n3!a15d M

Table 10-166 Optional Repetitive Sequence B Existing Drawings

Field Tag Field Name Format Mandatory/Optional

26P Drawing Identification 3!a/4x M
31F Drawdown Period 6!n[/6!n][//35x] O
32P Repayment of Principal 6!n3!a15d O
33a Interest Amount P or R M
71C Details of Adjustments 6*35x O
34a Net Interest Amount P or R O
57a Account With Institution A, B, or D O
72 Sender to Receiver 6*35x O
Information

Table 10-167 Mandatory Repetitive Sequence C New Drawing(s)

Field Tag Field Name Format Mandatory/Optional

26N Drawing Identification 3!a/4x M
(New)
32E Selected Currency 3!a O
31F Drawdown Period 6!n[/6!n][//35x] M
31R Rate Fixing Date 6!n[/6!n] O
32B Amount of Drawdown 3!a15d M
33B Receiver's Participation 3!a15d M
57a Account With Institution A, B, or D O
72 Sender to Receiver 6*35x O
Information

10-63
 Chapter 10
Treasury Markets - Metals

10.3.2 MT 644 Advice of Rate and Amount Fixing

This topic describes the MT 644 Advice of Rate and Amount fixing message formats
and its specifications.
This message type is sent by the agent of the facility to the providers of funds. It
specifies the interest rate applicable for a drawdown/renewal for a specified interest
period, whether the end date of that period is set or not. When applicable, this
message type will also set the exchange rate.
Maximum Length: 2000

Table 10-168 Mandatory Sequence A Identification of the Facility

Field Tag Field Name Format Mandatory/Optional

20 Transaction Reference 16x M
Number
21 Related Reference 16x O
27 Sequence of Total 1!n/1!n O
29A From 4*35x O
29B To the Attention of 4*35x O
88D Borrower(s) [/1!a][/34x] M
32A Original Facility 6!n3!a15d M
Amount

Table 10-169 Mandatory Repetitive Sequence B Specification of the Drawing

and Related Data

Field Tag Field Name Format Mandatory/Optional

26a Drawing Identification N or P M
31F Interest Period 6!n[/6!n][//35x] M
33B Receiver's 3!a15d O
Participation
36 Exchange Rate 12d O
37G Basis Rate [N]12d M
37M Interest Margin [N]12d O
37R Reserve Interest [N]12d O
37a Total Interest Rate A, B, C, D, E, or F O
34a Differential Amount P or R O
57a Account With A, B, or D O
Institution
72 Sender to Receiver 6*35x O
Information

10.3.3 MT 645 Notice of Fee Due

This topic describes the MT 645 Notice of Fee Due message formats.

10-64
 Chapter 10
Treasury Markets - Metals

This message type is sent by the agent of the facility to the signatories thereto or to the
parties to the offer. It specifies flat and variable fees, payable on the same date, which are
due to the Receiver.
Maximum Length: 2000
Format Specifications

Table 10-170 Mandatory Sequence A Identification of the Facility and Flat Fees

Field Tag Field Name Format Mandatory/Optional

20 Transaction Reference 16x M
Number
21 Related Reference 16x O
29A From 4*35x O
29B To the Attention of 4*35x O
88D Borrower(s) [/1!a][/34x]4*35x M
32A Original Facility Amount 6!n3!a15d M
71B Flat Fees 6*35x O

Table 10-171 Optional Repetitive Sequence B Variable Fees

Field Tag Field Name Format Mandatory/Optional

23 Type of Fee 16x M
31F Fee Period 6!n[/6!n][//35x] M
33B Computation Base 3!a15d O
Amount
34B Fee Amount 3!a15d M
37a Fee Rate A, B, C, D, E, or F O
72 Sender to Receiver 6*35x O
Information

Table 10-172 Mandatory Sequence C Summation of Fees

Field Tag Field Name Format Mandatory/Optional

71C Summary of Variable 6*35x O
Fees
33A Total Fees 6!n3!a15d M
34A Amount to be 6!n3!a15d O
Transferred
57a Account With Institution A, B, or D O
72 Sender to Receiver 6*35x O
Information

10.3.4 MT 646 Payment of Principal and/or of Interest

This topic describes the MT 646 payment of principal and/or of interest message formats.
This message type is sent by the agent of a facility to the providers of funds. It provides
advice of payments and/or prepayments of principal and/or payment of interest on the same

10-65
 Chapter 10
Treasury Markets - Metals

value date, which are not related to any subsequent drawing or renewal. It specifies (to
the Receiver) the amount with respect to principal and/or interest.
Maximum Length: 2000

Table 10-173 Mandatory Sequence A Identification of the Facility

Field Tag Field Name Format Mandatory/Optional

20 Transaction Reference 16x M
Number
21 Related Reference 16x O
23 Further Identification 16x M
29A From 4*35x O
29B To the Attention of 4*35x O
88D Borrower(s) [/1!a][/34x]4*35x M
32A Original Facility 6!n3!a15d M
Amount
26P Drawing Identification 3!a/4x O

Table 10-174 Mandatory Repetitive Sequence B Interest Calculation

Field Tag Field Name Format Mandatory/Optional

31F Interest Period 6!n[/6!n][//35x] O
33B Computation Base 3!a15d O
Amount
34N Interest Amount [N]6!n3!a15d O
37a Interest Rate A, B, C, D, E, or F O
72 Sender to Receiver 6*35x O
Information

Table 10-175 Mandatory Sequence C Principal Payment/Sum of Interest Due

Field Tag Field Name Format Mandatory/Optional

32A Total Principal Amount 6!n3!a15d M
Repaid/Prepaid
32N Principal Amount Due [N]6!n3!a15d O
to Receiver
33N Gross Interest [N]6!n3!a15d O
Amount Due to
Receiver
34N Net Interest Amount [N]6!n3!a15d O
Due to Receiver
34a Total Amount P or R O
Transferred
57a Account With A, B, or D O
Institution
71C Details of Adjustments 6*35x O
72 Sender to Receiver 6*35x O
Information

10-66
11
Processing of MX Messages as per ISO
20022
This topic describes the overview of the ISO 20022.
ISO 20022 is a multi part International Standard prepared by ISO Technical Committee TC68
Financial Services.
It is a messaging standard for exchanging electronic messages. It uses XML syntax and
offers structured rich data. This format is already used by many real-time, low-value, and
high-value clearing systems around the world. Offers richer references and improved
remittance information.
Under ISO 20022, financial institutions will be changing the messages they send and receive
via SWIFT from the legacy MT (message type) format to the new MX (message type XML)
format, which is more transparent, holds more data and is expected to boost interoperability
between banks.
For banks, the most important difference between SWIFT MT messages and the new MX
message format used for ISO 20022 is that MX messages are far richer in data. Banks have
the opportunity to leverage this data to enhance everything from sanctions and compliance
processes to customer analytics.
The primary difference between ISO 20022 and SWIFT messages is their respective formats.
Both styles of message are text-based, but SWIFT messages use a notation that is peculiar
to SWIFT whereas ISO 20022 uses a standardized XML-based syntax for messages.
ISO 20022 organizes financial definitions in business areas. These business areas are
uniquely identified by four-character codes called business area codes. The ISO 20022
catalog includes over 800 messages covering the following business areas:
• acmt: Account Management
• auth: Authorities Communications
• caaa: Acceptor to Acquirer Card Transactions
• cain: Acquirer to Issuer Card Transactions
• catm: Card Terminal Management
• catp: ATM Card Transactions
• caam: ATM Management
• pacs: Payments Clearing and Settlement
• pain: Payments Initiation
• camt: Cash Management
• remt: Payments Remittance Advice
• fxtr: Foreign Exchange Trade
• colr: Collateral Management

11-1
 Chapter 11
Generation of MX Type Messages

• setr: Securities Trade

• secl: Securities Clearing
• sese: Securities Settlement
• semt: Securities Management
• seev: Securities Events
• tsin: Trade Services Initiation
• tsmt: Trade Services Management
• reda: Reference Data

• Generation of MX Type Messages

This topic describes the generation of MX type messages supported in OBTR for
cash management which is camt.054 BankToCustomerDebitCreditNotification.
• MX Message Notification to OBTR from OBPM
This topic describes the MX message generation from Oracle Banking Payments
and sending notification to the Oracle Banking Treasury Management.

11.1 Generation of MX Type Messages

This topic describes the generation of MX type messages supported in OBTR for cash
management which is camt.054 BankToCustomerDebitCreditNotification.

Table 11-1 Cash Management and Customer Status

MT Number MT Name MX ID MX Name

MT 900 Confirmation of Debit camt.054 BankToCustomerDebit
CreditNotification
MT 910 Confirmation of Credit camt.054 BankToCustomerDebit
CreditNotification

The BankToCustomerDebitCreditNotification message is sent by the account servicer

to an account owner or to a party authorised by the account owner to receive the
message. It can be used to inform the account owner, or authorised party, of single or
multiple debit and/or credit entries reported to the account.
This new ISO 20022 message replaces both the FIN MT900 confirmation of debit and
the MT910 confirmation of credit messages. It is worth noting that the use of the
camt.054 message is optional – meaning that, even though it is part of the CBPR+
message portfolio, banks are not obliged to send it and it is bilaterally agreed.
The camt.054 BankToCustomerDebitCreditNotification is composed of:
• Group Header: This building block is mandatory and present once. It contains
elements such as MessageIdentification and CreationDateTime
• Notification: This building block is mandatory and repetitive. It should be repeated
for each account on which a notification is provided. The Notification contains
information on the booked debit entries.
• Entry: Entry is part of the Notification and can be repetitive. It contains information
related to the entry in the account, such as Amount, Booking or ValueDate and
BankTransactionCode. EntryDetails

11-2
 Chapter 11
MX Message Notification to OBTR from OBPM

• Entry detail: This is part of the Entry and there can only be one EntryDetails in each
Entry. This part contains detailed information related to the entry, such as References,
Amount Details, Related Parties and RemittanceInformation.
• Maintenance Required in OBTR for MX Type camt.054 Generation
The topic describes the maintenance required in OBTR to support the generation of MX
type camt.054.

11.1.1 Maintenance Required in OBTR for MX Type camt.054 Generation

The topic describes the maintenance required in OBTR to support the generation of MX type
camt.054.
The maintenance required in OBTR are given below:
• In the Media Maintenance (MSDMEDMT) screen, a new Media Code FINPLUS for the
generation of ISO20022 MX Messages must be maintained. The media FINPLUS must
be maintained as a higher priority than SWIFT for MX message generation
• For a given record of Media: FINPLUS; Location: CIF mapped to a customer at Treasury
Customer Address Maintenance (MSDTRCAD) screen, system should support
generation of camt.054 message. Existing Message types of DEBIT_ADVICE &
CREDIT_ADVICE both should be maintained in MSDTRCAD for generating Camt.054
MX message
• Newly introduced field SWIFT MX Type displays camt.054 for equivalent message type
DEBIT_ADVICE & CREDIT_ADVICE

11.2 MX Message Notification to OBTR from OBPM

This topic describes the MX message generation from Oracle Banking Payments and
sending notification to the Oracle Banking Treasury Management.
OBTR interfaces with external payment system OBPM for generation of MX message type for
the payment messages. The MX message gets generated in OBPM and a notification is
received in OBTR. The user can view the generated MX message in OBTR.

Table 11-2 Payment messages in MX format

MT Number MT Name MX ID MX Name

MT 103 Single Customer Credit pacs.008 FIToFICustomerCreditTr
Transfer ansfer
MT 202 General Financial pacs.009 FinancialInstitutionCredi
Institution Transfer tTransfer

• Maintenance Required in OBPM

This topic describes the MX message type maintenance required in OBPM.

11.2.1 Maintenance Required in OBPM

This topic describes the MX message type maintenance required in OBPM.
The maintenance required in OBPM are given below:
• In the Source Maintained Details (PMDSORCE) screen, the Source code must be
maintained for the MX message type maintenance.

11-3
 Chapter 11
MX Message Notification to OBTR from OBPM

• In the External Notification Queue Detailed (PMDEXTNT) screen, the

Notification System Class must be maintained as OBTR.
• In the Network Code Maintenance (PMDNWCOD) screen, the Network Code
must be maintained as SWIFTISO.
• In the Source Network Preferences Detailed (PMDSORNW ), the Network
Code must be maintained as SWIFTISO which is mapped to source code, and the
Transaction Type as Outgoing.
• In the Network Rule Detailed (PMDNWRLE) screen, the Channel Type must be
maintained as SWIFTMX and network code must be SWIFTISO for the respective
network rule.
For more information on the OBPM maintenance, refer to the Maintenance Required in
OBPM section in the Oracle Banking Payments Interface Guide.

11-4
Index
M MSSTRCAD- Treasury Customer Address
Summary, 3-10
MSDPREF- Messaging Branch Parameters MSSTRIBR- Treasury Incoming Message
Maintenance, 2-1 Browser Summary, 7-2
MSDTRAFM- Treasury Advice Format MSSTROBR- Treasury Outgoing Message
Maintenance, 4-2 Browser Summary, 5-2
MSDTRCAD- Treasruy Customer Address MSSTRUAR- Treasury Message History
Maintenance, 3-1 Retrieval Summary, 6-1
MSDTRFFT- Treasury Free Format Message
Maintenance, 8-1
MSDTRSWT- Treasury SWIFT Tag Maintenance,
S
2-7 SMSJBBRW- Job Details, 4-4
MSDTRVMS- Treasury Message, 6-2

Index-1