TEMENOS T24

Delivery - Messages Creation

User Guide

No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV.

Copyright 2005 TEMENOS Holdings NV. All rights reserved.

Delivery - Messages Creation

Table of Contents
Overview.................................................................................................................................................. 4
MT101 Processing................................................................................................................................... 5
Outward MT101 Processing - [Link] ......................................................................... 5
Inward MT101 processing ................................................................................................................... 9
Case 1: Agreement details not available for Sender & Ordering Customer .................................. 11
Case 2: Agreement details not available for Ordering Customer .................................................. 12
[Link].111 ................................................................................................................................ 16
[Link] – MT111 ...................................................................................................................... 17
[Link] for MT111 production .................................................................................................. 18
Free Format Messages ......................................................................................................................... 19
Free Format Outward Messaging (MTn99's) ..................................................................................... 19
Free Format Inward Messaging (MTn99's) ........................................................................................ 20
Interbank Statement Requests/Production ........................................................................................... 25
Outward generation of MT920 ........................................................................................................... 25
Inward processing of MT920 & Generation of outward statements. ................................................. 27
Interim / Customer Statement processing ......................................................................................... 32
MT940-Customer Statement /MT950-Statement Message ............................................................... 32
MT941-Balance Report ...................................................................................................................... 32
MT942-Interim Transaction report ..................................................................................................... 32
Setup required for MT920-STP process ............................................................................................ 33
MT942 production.................................................................................................................................. 33
Manual MT942 production - [Link] .......................................................................... 33
Automatic MT942 production - [Link] ...................................................................... 34
Interim transaction reports (MT942) – Phantom ................................................................................ 35
[Link] ..................................................................................................................... 36
Set-up................................................................................................................................................. 37
Soft Delivery records.......................................................................................................................... 38
[Link]................................................................................................................................ 39
[Link]................................................................................................................................ 40
[Link] .................................................................................................................. 40
[Link] application .................................................................................................. 43
Sample Workflow ............................................................................................................................... 44
[Link] Enquiries.................................................................................................. 53
EBQA.I.SWIFT92 ........................................................................................................................... 53
[Link] ................................................................................................. 53

TEMENOS T24 User Guide

Page 2 of 53
Delivery - Messages Creation

EBQA.I.SWIFT95 ........................................................................................................................... 53
[Link] ................................................................................................. 53
EBQA.I.SWIFT96 ........................................................................................................................... 53
[Link] ................................................................................................. 53

TEMENOS T24 User Guide

Page 3 of 53
Delivery - Messages Creation

Overview
The Delivery system itself can create Messages, which are not explicitly linked to any other T24
application. In order to keep the setup of the delivery system separate from its own applications which
create messages we have segregated the User Guide into the two parts; ‘Delivery - Base’ & ‘Delivery
– Messages Creation’.
The applications that create messages for the delivery system (as opposed to those made by core or
optional applications) are:

[Link]
[Link].111
[Link]
[Link]
[Link]

TEMENOS T24 User Guide

Page 4 of 53
Delivery - Messages Creation

MT101 Processing
Outward MT101 Processing - [Link]
Swift message MT101 (Request for Transfer) is sent by a financial institution on behalf of a non-
financial institution account owner, i.e., the ordering customer/instructing party, and is subsequently
received by the receiving financial institution and processed by the receiving financial institution or the
account servicing financial institution.

The MT 101 can be used to order the movement of funds:

Between ordering customer accounts, or
In favour of a third party, either domestically or internationally.

The MT 101 consists of two sequences:

Sequence A - General Information is a single occurrence mandatory sequence and contains
information to be applied to all individual transactions detailed in sequence B.

Sequence B - Transaction Details is a repetitive sequence; each occurrence provides details

of one individual transaction. Fields which appear in both sequences are mutually exclusive

To generate outward MT101s, application [Link] can be used and a receiver of an

MT101 can be specified here either with a valid BIC code prefixed with “SW-“ or a customer number
who has a Swift address.

In the [Link] application, fields from RECEIVER.101 to AUTHORISATION forms

single occurrence mandatory sequence A and fields [Link] to [Link] forms sequence B
transaction details which can be multi-valued for repetitive sequence. During input, if [Link]
details are not given, then system defaults the Id of the application and it is mapped to the outgoing
MT101.

After giving the sequence A and B details, CREATE.MT101 has to be set to “YES” in the
[Link] application, which will generate swift message- MT101. Outward delivery
reference number and the date of creation is updated in [Link] and [Link].101
fields for our reference. Once the MT101 Outward message is generated from the application, the
record is moved to History.

TEMENOS T24 User Guide

Page 5 of 53
Delivery - Messages Creation

[Link] –Single Sequence Example

Outward MT101 Message-Single Sequence Output

TEMENOS T24 User Guide

Page 6 of 53
Delivery - Messages Creation

To generate an MT101 with repetitive sequence as per the below example, fields can be multi-valued
and an MT101 with more than one sequence can be generated. There is no restriction on the number
of sequences, however if the total characters in MT101 message including the header and trailer
exceeds the Swift allowed maximum characters then the message, during formatting, will be moved to
Repair disposition with appropriate error message.

[Link]-Repetitive Sequence Example

TEMENOS T24 User Guide

Page 7 of 53
Delivery - Messages Creation

Outward MT101Message Multi-Sequence Output

TEMENOS T24 User Guide

Page 8 of 53
Delivery - Messages Creation

Inward MT101 processing

An MT101 message type requires Message User Group (MUG) registration and its use governed by
bilateral agreements:

• Between the Account Servicing financial institution and the ordering customer
• Between the sending financial institution and the ordering customer

Hence before processing an incoming MT101 message, agreement details have to be checked for the
sender of the message and the ordering Customer.

To trigger the checking of an agreement before processing an MT101 message, in [Link] the
field [Link] has to be set as “Y” and in [Link], field [Link] has
to be set as “Y” for the record id 101. When the above fields are not set in [Link] and
[Link], then the Incoming MT101 will be processed without checking the agreement details.

[Link]-101 record with [Link] as “YES”

Agreement details related to an MT101 can be added in [Link] with the customer
number of the sender of MT101 message as ID and the ordering Customer BIC details in
[Link] with [Link] as FT.

For example, to process an Inward MT101 received from ABSA Bank and ordered by customer,
whose BIC is “TESTGBT1” – following set-up has to be done in [Link]
Application:

TEMENOS T24 User Guide

Page 9 of 53
Delivery - Messages Creation

[Link] –Set up example

When an Incoming MT101 has ordering customer as Name and Address (Tag 50H), then checking
against the [Link] is skipped and the message is processed normally.
For each repetitive sequence in an MT101 message, a separate Funds Transfer contract is created for
each sequence. If the Ordering customer (tag 50g) is given in sequence A then that account is used to
debit all Sequence B transactions, otherwise Ordering Customer given in the respective sequence is
used as a Debit account. Based on the Txn Code given in [Link], either “AC” (both
debit and credit account –Customer account) or “IT” (debit to an Nostro / Vostro account) or “OT”
(Credit to Nostro account) type of transaction is created.

TEMENOS T24 User Guide

Page 10 of 53
Delivery - Messages Creation

The flow for checking the agreement details for inward MT101 message is explained below:

Sample Inward MT101 message used for Checking Agreement

Case 1: Agreement details not available for Sender & Ordering Customer
The above MT101 message is processed through inward delivery processing there is no
[Link] for the Customer BIC code XBSAZAJJ). In such cases an error Message
is raised indicating agreement details do not exist for the sender of the MT101 and the message is
placed in “Repair” disposition.

TEMENOS T24 User Guide

Page 11 of 53
Delivery - Messages Creation

[Link]- Error - No Netting Agreement available for Sender

Case 2: Agreement details not available for Ordering Customer

The Sender of the MT101 does have a record in [Link], but the ordering
Customer BIC (50g) is not given in [Link]. In this case the message is placed in “Repair”
Disposition with an error indicating agreement is available with the sender but not with the Ordering
Customer.

TEMENOS T24 User Guide

Page 12 of 53
Delivery - Messages Creation

[Link]-Repair-No agreement for Ordering Customer

TEMENOS T24 User Guide

Page 13 of 53
Delivery - Messages Creation

Once the Sender of an MT101 and ordering Customer details are available in
[Link], then an inward MT101 is processed and a [Link]
contract is created by debiting the Ordering Customer and crediting the Beneficiary Account or by
crediting the Nostro account of Account With Bank Customer. Incoming MT101 Request Execution
date (Tag 30) contains the date on which the request has to be executed. In case the request
execution date is less than the system date, then contracts will be processed with Debit and credit
value date as the request execution date, and processing date as Today otherwise the request
execution date will be used as Debit value date / Credit value date and processing date in the
FUNDS. TRANSFER contract.

[Link]- Processed when Agreement is available

TEMENOS T24 User Guide

Page 14 of 53
Delivery - Messages Creation

When successful the resulting FT would look similar to the one below:

Successful FT created by incoming MT101

TEMENOS T24 User Guide

Page 15 of 53
Delivery - Messages Creation

[Link].111
T24 can produce the additional outgoing SWIFT messages from the application, [Link].111.
The MT111 – Request for stop payment of a cheque will be produced via the Soft Delivery Mechanism.

[Link].111 Input Record

TEMENOS T24 User Guide

Page 16 of 53
Delivery - Messages Creation

[Link] – MT111
The following [Link] record is released for use with the [Link].111 application.
Populate the [Link] field on these records according to your business needs.

EB Activity Input Record

TEMENOS T24 User Guide

Page 17 of 53
Delivery - Messages Creation

[Link] for MT111 production

The following [Link] is released for use with the [Link].111 application.

[Link] Input Record

TEMENOS T24 User Guide

Page 18 of 53
Delivery - Messages Creation

Free Format Messages

Free Format Outward Messaging (MTn99's)
Free Format messages are stored in the application [Link]. This applies to outward
and inward messages. To send a message, prepare a record on [Link] with the
receiver's customer number, the activity, and the message text. You can choose to see a preview of
the message(s), which will be sent.
When an outgoing record on [Link] is authorised, then the activity identified in
[Link] is invoked and each message specified in the corresponding [Link] record
is handed off to the T24 delivery application. Consult the ‘Delivery – Base’ User Guide on the use of
[Link] and [Link].

Free Format Message Input Record

Messages MT499 & MT799 have the option to use a repeating set of text so instead of using the field
TEXT for the message use the field NARRATIVE.

TEMENOS T24 User Guide

Page 19 of 53
Delivery - Messages Creation

Free Format Inward Messaging (MTn99's)

MTn99's when received by T24 are stored on the [Link] Soft Delivery file. Below are
details of the procedures that must be followed to enable the processing of inward MTn99s.
We have standard inward templates that can be customised by users to meet the specific demands of
their business relating to that type of incoming message. This can involve customisation down to how
the individual tag of a specific SWIFT message is handled.
When dealing with the n99 series of messages the actual data received is little more than a few
references and some free-format text, so there is not that much that can be done with the incoming
message.
We have allowed for a generic message to be recorded and a link that allows the user to view the
incoming message details so this is perhaps the best way to handle the n99 messages.
It should be noted that if you have a unique usage for these messages you can tailor the routines
accordingly, perhaps to create or update a locally developed application.
To use the generic message support is a matter of checking you have (or adding) a few records to the
system.

For example to handle an inward MT299:

[Link] you need record EB-0299

[Link] must be present before [Link] **
[Link] a basic mapping record in this case [Link].1
[Link] a basic one, such as ADVICE will probably exist already
[Link] you need record EB-0299

VERSION To set [Link] and [Link] settings

[Link] Basic OFS details – must have GLOBUS in [Link]

** Note
The [Link] record will need updating with the other record details created before the inward
message can be processed.

TEMENOS T24 User Guide

Page 20 of 53
Delivery - Messages Creation

[Link] Record

[Link] record

Simple VERSION record

TEMENOS T24 User Guide

Page 21 of 53
Delivery - Messages Creation

[Link] record

TEMENOS T24 User Guide

Page 22 of 53
Delivery - Messages Creation

[Link] record

An [Link] record must also be set up, this uses the ‘GLOBUS’ [Link] which in
effect is creation of a T24 record or contract by a program

OFS Source Record

The [Link] record is the link that brings all these records together and which tells the
incoming T24 services which processing/contracts are to be created.

TEMENOS T24 User Guide

Page 23 of 53
Delivery - Messages Creation

[Link] record

Since this is using a provided template it can be used to process any incoming message where the main
requirement is to record and view the SWIFT record.
If, however, the requirement is also there to update more fields such as local references or even a
different application then the templates can be copied and amended to suit as required.

TEMENOS T24 User Guide

Page 24 of 53
Delivery - Messages Creation

Interbank Statement Requests/Production

The set of SWIFT messages used by banks to request or send statement information is handled by
the [Link] application.
Banks send a request message to their correspondent to get information related to their Accounts (or
Accounts maintained for their Customers where a prior agreement is in place).
In this regard an MT920-Request message is sent to the Account servicing institution to transmit one
or more MT940 Customer Statement(s), MT941-Balance Report(s), MT942-Interim Transaction
Report(s), or MT950 Statement Message(s) containing the latest information available for the Account
as identified in the Message.
This Message has a multiple sequence consists of Account(s) for which the information is requested
along with the required Message type(s). MT920 message requires implementation of special
procedures and its use is governed by bilateral agreements between correspondents.
T24 supports the generation of Outward MT920 as well as inward processing, whether automatically
processed (straight through) or requiring some manual intervention.

Outward generation of MT920

An MT920 (Request message) can be sent to a correspondent that requests information to be sent
back in one or more of the standard messages. According to the message type(s) additional
information, such as debit/credit floor limits may be needed.
Message that can be requested are the MT940, MT941, MT942 and MT950.
In the example below an MT942 is being requested, the user requests debit entries of $5million and
credit entries of $1million or over to be shown.

TEMENOS T24 User Guide

Page 25 of 53
Delivery - Messages Creation

Example MT920 outward request

TEMENOS T24 User Guide

Page 26 of 53
Delivery - Messages Creation

Inward processing of MT920 & Generation of outward statements.

Inward MT920s can be received from Correspondents with a request to send out specific statement
types for an Account.
Where the requesting institution is not the account owner the existence of Bilateral Agreement
between the correspondent sender and receiver is necessary. Hence when a MT920 is received from
the Correspondent for an Account, the existence of bilateral agreement may be checked for the
combination of Account owner, Correspondent and the message type.
In T24 the bilateral agreement details are specified in the [Link] application
for a Customer (Account Owner) along with the counter party and the message type(s), either MT940,
MT941, MT942, MT950 that can be transmitted. To add an agreement for an Account owned by the
Correspondent, the Customer and the counterparty can be input as the same.

[Link] record

When an Incoming MT920 is received, the existence of the agreement for the combination of
correspondent, Account Owner and the Message type is checked. If an agreement is not available for
the above combination in [Link], then a record is created in IHLD Status in
[Link].

TEMENOS T24 User Guide

Page 27 of 53
Delivery - Messages Creation

To process request for Interim statements - MT941 & MT942 along with the bilateral agreement check,
the requested Account should have the “STP” flag set for the Message type in
[Link]. If the flag is not set then an Error is raised and request is put on Hold.

[Link] setting STP support

A record is created in [Link] for each sequence, where an Incoming MT920

has multiple sequences.

TEMENOS T24 User Guide

Page 28 of 53
Delivery - Messages Creation

Incoming MT920 trigger

MT920 requesting MT942 statement

TEMENOS T24 User Guide

Page 29 of 53
Delivery - Messages Creation

The generated outward MT942 has the Opening balance, closing balance and forward available
balance along with the sum of Debit / Credit movement for the Account.

MT942 generated in response to MT920 request

TEMENOS T24 User Guide

Page 30 of 53
Delivery - Messages Creation

When a MT920 is received and there is an error such as:

• No bilateral agreement
• No agreement for combination of sender/counterparty
• Incoming Account number is not a valid Account in Globus.
• Statement type requested is not on the agreement

Then the [Link] is created in “IHLD” Status with a validation error and when
the record is viewed or amended the relevant error message is shown. In such cases either the record
can be amended after setting the agreement or the request can be discarded.

Incoming MT920 has a problem

TEMENOS T24 User Guide

Page 31 of 53
Delivery - Messages Creation

Interim / Customer Statement processing

Interim statements (i.e. MT941 & MT942) are generated online and end of day statement Messages
(ie. MT940 & MT950) are generated during end of day statement processing with the required
information.
When a request for a message type is received through an incoming MT920, the transaction in the
statement information should not be duplicated and should be sent as per Swift standards as
applicable for the Message type. The information such as Opening Date/balance, Closing
Date/Balance, statement details etc given in response to a request message is explained below:

MT940-Customer Statement /MT950-Statement Message

As per Swift standards, the MT940-Customer Statement Message or MT950- Statement Message
which is transmitted should have the opening date / balance same as the closing date/ balance as
reported in the previous Customer Statement or Statement Message.
Thus, when a MT920 is received with a request for MT940 or MT950, along with creating the
[Link] with the Incoming details [Link] application is
updated with the Message type and statement request ID for EOD processing. During end of day
statement processing, the required statement is generated like an ad-hoc statement using the Closing
Balance / Date, Statement No as available for Frequency 1 in [Link] for the
requested Account. When more than one request for an Account is received in a day, it is marked as
duplicate and only one statement is sent during the EOD processing.

MT941-Balance Report
MT941 statement should have the opening date/ Balance same as the Closing Date/Balance as
reported in the previous Statement (940/950) or Balance report (941) and sum of all transactions done
after the opening date has to be reported.
Hence when a MT920 is received which requests an MT941, the last statement sent date as available
in Frequency1 & the Last MT941 sent date as available in the [Link] application
for the requested Account is compared and the latest among the above is taken for processing. The
sum of debit & credit entries processed after the latest statement date is reported in the outward
MT941. The transactions that are reported in MT941 message are stored in
[Link] to avoid duplicating the entries.

MT942-Interim Transaction report

Swift states that MT942 should contain the detailed and summary information about the entries
debited or credited to the Account since: -
• The last statement (940/950) or balance report (941) or
• The last interim transaction (942) report (sent in the period since the last statement or balance
report)

TEMENOS T24 User Guide

Page 32 of 53
Delivery - Messages Creation

Hence when a request for MT942 is received, all the transactions which are already reported in the
Previous Statement (950) or Balance report (941) or Interim transaction report (942) is ignored and
remaining transactions are reported subject to the debit / credit floor limit.

Setup required for MT920-STP process

In [Link] application, for record-ID 920, set [Link] as DE.I.MT920, along with
required [Link] VERSION and [Link] id, which has the
[Link] as GLOBUS.

[Link] record settings

MT942 production
There is also a newer application for the processing of both incoming/outgoing request statement
message types called [Link] which has more flexibility and which may be
preferred for the production of MT942 messages.

Manual MT942 production - [Link]

This application allows SWIFT MT942 interim statements to be produced on an ad-hoc basis for
specified accounts. It requires the 'V' function to initiate the production.

TEMENOS T24 User Guide

Page 33 of 53
Delivery - Messages Creation

DE MT942 Request Verify Record

This application can only produce an MT942 message where the ACCOUNT in question has been
configured for their production, by use of the SEND.942 field in [Link]. It also
requires that the correct delivery route for the message is defined in a [Link] record and an
alternate delivery address in [Link].

Refer to the User Guide - Account, Interest and Charges for further information on Account statements.

Automatic MT942 production - [Link]

Where MT 942 messages are required to be sent automatically, at specified times during the day, an
[Link] record must be created in order to run the [Link] routine
which is entered into the [Link] field. Use the 'V' function to run the process. To stop the
phantom use the 'I' function, and enter the codeword STOP in the field [Link].

Phantom Control Verify Record

TEMENOS T24 User Guide

Page 34 of 53
Delivery - Messages Creation

The phantom process can only work effectively provided the [Link],
[Link] and [Link] records have been configured. Refer to the User Guide -
Account, Interest and Charges for further information.

Interim transaction reports (MT942) – Phantom

Interim transaction reports are produced optionally, either on request, or at specified times during the
day.
Requests are submitted via the file [Link]. Timed reports are controlled via
[Link]. Consult Accounts, Interest and Charges for further details of the
records involved.
The process [Link] runs as a phantom to produce the timed reports. To start
the phantom, Verify an [Link] record for the process.

TEMENOS T24 User Guide

Page 35 of 53
Delivery - Messages Creation

[Link]
This application in T24 caters for some of the general SWIFT messages both inward and outward that
are required to cancel messages sent, make queries on messages received or send and
provide/receive answers to the queries.
Among the Common message group, SWIFT provides for 3 message types covering the whole 9
categories of message types. These are the n92, n95 and n96 messages. So for example, you would
use a 192 to cancel an MT100; a 195 to send a query and a 196 to respond to a query. Since the
message formats are the same across the categories, T24 allows all of the n92, n95 and n96, even
though it may not produce messages in that series. This is to allow a common query/answer interface
for the bank.
The processing of these message types involves the use of the Open Financial Server product, which
must be installed, configured and working. This takes qualifying messages from the incoming SWIFT
queue and creates OFS data records, which then input records to the [Link] file.
These will be cancellation requests (n92), new or existing queries (n95) and replies to your queries
(n96).

In short, the types of processing will involve:

• Sending cancellations of various messages you have sent,

• Receiving confirmation of the cancellation, rejection or query related to it.

• Receiving requests for cancellation,

• You confirm, reject or query the cancellation.

• Sending your queries to a SWIFT bank,

• Receiving responses to them.

• Receiving queries from a SWIFT bank,

• Assigning them to a staff member for resolution,
• Sending your responses back.

• Enquiries on the outstanding items.

In order to work smoothly, it is appropriate that VERSION and ENQUIRY records are configured to
use the workflow methodology. Some example type records are released as a starting point for the
bank to use.

TEMENOS T24 User Guide

Page 36 of 53
Delivery - Messages Creation

Set-up
[Link] is a core application, so it will be installed when upgrading.

To ensure that OFS can create records you should:

• Add the [Link] program to the COMPANY record in the [Link] field.
• Create and authorise an [Link] record like the one below:

Auto ID Start Input Record

• Create an [Link] record, the id of which is then added to each n92, n95 and n96
[Link] record.
• The ENQUIRY USER-LIST is used to assign items to staff members. If not present or working it will
need to be created/modified.
• [Link] records should be added to send n92, n95 and n96 messages via SWIFT
• Part of the upgrade process will have added records to [Link] and
[Link], which are crucial for the correct operation of [Link].
• [Link] uses T24 soft delivery so records are also supplied for [Link] and
[Link], these must be authorised and in place.

TEMENOS T24 User Guide

Page 37 of 53
Delivery - Messages Creation

Soft Delivery records

Records are supplied ready for use.

[Link] records such as:

[Link] Input Record

[Link] record such as:

[Link] Input Record

You probably will not need to change these.

TEMENOS T24 User Guide

Page 38 of 53
Delivery - Messages Creation

[Link]
Used by the inward delivery services.

OFS Source Input Record

TEMENOS T24 User Guide

Page 39 of 53
Delivery - Messages Creation

[Link]

There are special fields near the end of the [Link] record, which instruct the system on what
is needed for OFS type inward processing.

DE Message Input Record

Note. The OFS id is entered here. The mapping routines and VERSION to use are supplied already,
but since some users do not have OFS installed, the [Link] id must be entered manually.

[Link]
The actual SWIFT messages are quite simple and allow for standard situations to be identified by
using 2-digit numeric codes that have set meanings. Some of these require further data such as dates,
statement numbers etc, which are usually appended to the code in the relevant field.
To assist in the use of these codes, we have added them to the [Link] application
and used new detail fields to assist in their explanation. The text and codes are derived from SWIFT
to avoid any errors.

TEMENOS T24 User Guide

Page 40 of 53
Delivery - Messages Creation

Swift Code Words Input Record

There is a small description field for internal use, the message types that use the code, the number of
supplemental information items and the SWIFT text for the code.
In use this file is viewed by running a context based ENQUIRY, which displays only the codes
pertinent to the query item you are entering. So for example, when responding to a query you would
be entering an n96 reply and the table below would appear, you can then use the drag and drop
feature of T24 browser to select the code you want whilst being able to see the context in which it is
used.

TEMENOS T24 User Guide

Page 41 of 53
Delivery - Messages Creation

List of Query Codes for Swift MTn96

TEMENOS T24 User Guide

Page 42 of 53
Delivery - Messages Creation

[Link] application
The application itself looks as below but needs some explanation of its use. Shown is a sample
(populated) record from the application, followed by a few examples of how it is intended to be used.
First select a pre-designed VERSION for straight contract input from a menu:

EB Queries Answer Application

Sending a cancellation:

EB Cancellation Queries Answers Record

TEMENOS T24 User Guide

Page 43 of 53
Delivery - Messages Creation

The details required are not too complicated but the process of retrieving the information and entering
it can be automated to some extent.

Sample Workflow
Below is an example of sending a 192 Cancellation request. The correspondent sends a query on it,
which is replied to, and then confirmation is received that the payment was cancelled.

Our cancellation request:

Run an Enquiry to find the reference of the message sent selecting the Enquiry from the menu.

Use an ENQUIRY to find the details

This brings the selection criteria panel, which is important, as the sent messages file is quite large.

Enquiry selection criteria panel

TEMENOS T24 User Guide

Page 44 of 53
Delivery - Messages Creation

Run the enquiry to narrow down the search, for example defining the following results.

Enquiry of sending a 192 Cancellation Request

In this instance there is only one match. We can click on the ‘Send Cancel Message’ or the ‘Query
Sent Message’ using the pre-defined links.

TEMENOS T24 User Guide

Page 45 of 53
Delivery - Messages Creation

This retrieves the data from the Enquiry and ‘pushes’ it into a specified VERSION, avoiding having to
type the details of the message.

Retrieve data from Enquiry

Only a few fields are required for completion to finish the transaction. Assuming that this cancellation
has been sent and received by the correspondent, there may be a small query on it.

TEMENOS T24 User Guide

Page 46 of 53
Delivery - Messages Creation

Incoming Query
It is not pertinent to explain how inward delivery works in this document. Rather the events, which
transpire in getting the message in and converting it to an OFS message (which then creates our new
[Link] transaction), will be shown as bullet points below:

• Inward SWIFT message comes into T24 via hardware or software link to SWIFT.
• Delivery services are running so the message is processed by T24 and if they are in a valid format
end up in the inward delivery files.
• The [Link] record is checked to see if this message should be processed as an incoming
OFS type message. If so, the OFS routine will read the message and translate from into a format for
the OFS processing thereby creating a T24 transaction; in this case an [Link]
one. .

We should now
have the query from our correspondent on the unauthorised
[Link] file.

We can check for incoming n95 queries by selecting the menu option. This will trigger an ENQUIRY,
which filters the unauthorised file for n95 inward queries. You may wish to first assign the query to an
investigator, or send a n96 reply immediately. You can make the decision from the ENQUIRY by
right clicking on the message and selecting the view, generate answer or assign options.

Select n95 queries from the Menu option

Now enter any pertinent selection criteria:

TEMENOS T24 User Guide

Page 47 of 53
Delivery - Messages Creation

Criteria Selection Panel

Then a list of the matches will be displayed:

Enquiry displays list of matches

Options here are to view the record, generate an MTn96 response or to assign the query to an
investigator.

The view details is self evident but if the other actions are selected a context sensitive action is
triggered.

TEMENOS T24 User Guide

Page 48 of 53
Delivery - Messages Creation

The assign to investigator will open the message for input:

“Assign to Investigator” to open the message for input

TEMENOS T24 User Guide

Page 49 of 53
Delivery - Messages Creation

The Generate MTn96 will create a new [Link] record for you to complete:

Generate MTn96 will create a new [Link] record

Note: The two fields likely to be entered are the ANSWER and NARRATIVE ones. Whilst the
NARRATIVE is for free format text and needs no further explanation, the ANSWER field can contain
short codes to represent the standard answers.

T24 has an option that populates the T24 browser ENQUIRY menu with those that are appropriate
for the task at hand. This is set-up in [Link], and we have enabled the
[Link] relevant for the message type to be available for these actions.

TEMENOS T24 User Guide

Page 50 of 53
Delivery - Messages Creation

Selecting the ENQUIRY from the menu invokes a display of the codes. This is done using the ‘More
Actions …’ feature in Browser where the options to list files, print, copy etc are located.

Select Enquiry from the menu to invoke a display of the codes

TEMENOS T24 User Guide

Page 51 of 53
Delivery - Messages Creation

The full display of the codes appears as:

Full Display of Codes

Conclusion
The three message types are:
N92- Send Cancellation
N95- Sent or received Query
N96 – Sent or received Answer
Whilst we have not covered the use of each message being sent/received the concept is quite easy
and the above examples should be sufficient to familiarise yourself with what the application can do.

TEMENOS T24 User Guide

Page 52 of 53
Delivery - Messages Creation

[Link] Enquiries
EBQA.I.SWIFT92
This Enquiry has the following functionality:
• View all incoming SWIFT MTn92 messages awaiting replies.
• View a specific message, using different selection criteria, i.e. STATUS, [Link] or
[Link] e.g. all ‘195’, ‘INWORK’ or all ‘195’ with user ‘TONY’.
• Generate a MTn96 Answer for the incoming MTn92.
• Update status of the messages accordingly. All incoming MTn92 have the Status ‘NEW’ when
written to the [Link] unauthorised file.
• When the above Enquiry is run, and a reply is generated, the status changes to ‘INWORK’ for
both the incoming (MTn92) and outgoing (MTn96) messages.
• When the reply is authorised the status then changes to ‘PROCESSED’ for both messages.

[Link]
Shows the SWIFT MTn92 record in a formatted layout.

EBQA.I.SWIFT95
Similar to EBQA.I.SWIFT92, but this Enquiry processes incoming SWIFT MTn95.

[Link]
Shows the SWIFT MTn95 record in a formatted layout.

EBQA.I.SWIFT96
This Enquiry has the following functionality:
• View all incoming SWIFT MTn96 messages awaiting authorisation.
• View a specific message using different selection criteria, i.e. STATUS, [Link] or
[Link] e.g. all ‘196’, ‘INWORK’ or all ‘196’ with user ‘TONY’.
• Update status of the incoming SW.I.F.T MTn96 message to ‘PROCESSED’ when authorised.

SWIFT MTn96 Answer does not require a reply.

[Link]
Shows the MTn96 record in a formatted layout

TEMENOS T24 User Guide

Page 53 of 53