TEMENOS T24
Confirmation Matching
User Guide
Information in this document is subject to change without notice.
No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV.
Copyright 2005 TEMENOS Holdings NV. All rights reserved.
Confirmation Matching
Table of Contents
Overview.................................................................................................................................................. 3
Deal/Transaction Processing .................................................................................................................. 3
General Process of Automatic Matching ............................................................................................. 3
Starting/Stopping Processors ........................................................................................................... 6
Automatic Matching Process ............................................................................................................ 6
[Link] ............................................................................................................... 7
[Link] ........................................................................................................... 8
Full Match ..................................................................................................................................... 8
Part Match .................................................................................................................................... 9
Setup ..................................................................................................................................................... 11
[Link] .............................................................................................................................. 11
Manual Matching................................................................................................................................ 11
[Link] ........................................................................................................................ 12
MATCHING TAGS ......................................................................................................................... 12
OPTIONAL TAGS .......................................................................................................................... 12
[Link] .................................................................................................................... 12
[Link] ...................................................................................................................... 16
[Link]................................................................................................................................... 17
[Link] .............................................................................................................................. 20
[Link] .................................................................................................................... 20
[Link] ........................................................................................................... 20
Enquiries................................................................................................................................................ 20
Running the Enquiries........................................................................................................................ 20
ENQ [Link] ..................................................................................................... 21
ENQ [Link] ....................................................................................................................... 22
ENQ [Link] ..................................................................................................................... 23
MANUAL MATCHING USING ENQUIRIES ...................................................................................... 24
Viewing Records ............................................................................................................................ 24
Matching Records .......................................................................................................................... 26
View [Link] .......................................................................................................... 28
TEMENOS T24 User Guide
Page 2 of 28
Confirmation Matching
Overview
Messages sent or received by the Electronic Delivery System are copied to the confirmation matching
application module. Message types specified within the CM application parameter files are selected for
matching. The incoming messages are matched with the outgoing messages and the messages are
matched where both have identical match keys.
The messages requiring matching need not only be the confirmation messages they can be any other
message types. Although, the intentions are that this application is used for confirmation matching i.e.
S.W.I.F.T. message types MT300, MT320, MT324, MT330 and MT350.
Deal/Transaction Processing
General Process of Automatic Matching
A copy of generated S.W.I.F.T. messages (sent out or received) is placed onto the confirmation
matching holding queue file, [Link]. Each message on this queue is individually
taken and processed; its entry effectively removed. If the required message type is of the type
specified in the confirmation matching application file, [Link], it is passed for
matching, otherwise it is discarded.
General process of Automatic Matching
TEMENOS T24 User Guide
Page 3 of 28
Confirmation Matching
A match key is generated for the message using the S.W.I.F.T. tag contents and the matching tags.
For each message type that needs matching the matching tags are defined in [Link].
If the match key has a value then the message is selected for matching. The selected message is
stored on [Link] and the [Link] is written to [Link], both with the same
record key.
Two additional work files are used for the matching process, [Link] and
[Link]. The [Link] file is used for full matching and
the [Link] file for partial matching. The unmatched item is written to the
[Link] file with record key of the matching key.
The matching process tries to read a record from the [Link] and compare it to the
[Link] of each work file on the [Link] file. If this record exists on
[Link] then a match has been found. The entries on [Link] and
[Link] referenced by the item found on [Link] are updated, as are
the originating entries for the current [Link]. The entry on [Link]
is removed. If the entry for the full [Link] does not exist on [Link], then a
record is created on [Link] work file for a matching message.
The partial matching procedure is similar to the full matching procedure, the difference being that this
uses the partial match key and the [Link] work file for matching.
The user using manual matching matches any unmatched or partial unmatched messages.
TEMENOS T24 User Guide
Page 4 of 28
Confirmation Matching
Detailed Process of Automatic Matching
TEMENOS T24 User Guide
Page 5 of 28
Confirmation Matching
Starting/Stopping Processors
Two phantoms, [Link] and [Link] automate the matching of
messages. The phantom [Link] selects the messages for automatic matching from
the [Link] and the [Link] matches the messages.
The [Link] application is used to control the starting, stopping and trouble shooting of these
phantoms.
The phantoms are background processes. Once these phantoms are started, they should run
continuously without being attached to a particular terminal and without any further intervention from
the user.
Two Phantoms automate the matching of messages
Automatic Matching Process
The process of automatic matching is divided into two distinct tasks; firstly to get the new messages
for automatic matching and secondly to perform the matching of the messages. As said above, these
are performed by two phantoms:
TEMENOS T24 User Guide
Page 6 of 28
Confirmation Matching
[Link]
The [Link] phantom selects messages from the [Link] in
readiness for matching. A message is selected for matching only if its message type is defined in the
[Link] file.
The message types requiring matching are held as records on [Link] file with the
S.W.I.F.T. message type as their key. The matching tags to be used for each message type are
defined within these records. Also, the [Link], SENDER or RECEIVER can be used for
matching.
The [Link] is built by locating, within the message, each tag specified on the message type
record of [Link] file and retaining the corresponding contents. These values are
concatenated to produce the [Link].
For example, for message type 300 the [Link] requiring match are 20 and 30T.
• [Link]
• RECORD ID 300
• KEY1 20
• KEY2 30T
The message MT300 holds the entry:
:20:REF1A
:30T:20000506
The tags would be located in the message and the values, “REFIA” for 20 and “20000506” for 30T and
are retained for match keys. In this case the [Link] would be “REFIA:20000506”. In the above
example only the relevant details are shown.
Two types of match key are generated, a full match key and a partial match key. If there is a value in
either match key then the message is selected for matching.
The status and various other details of the message are written to a record in the [Link] file.
The match keys are written to a separate record on the [Link] file. These two records
have the same key as received from the [Link] file and this is also the same as
on the originating S.W.I.F.T. message. The full contents of these two files are detailed later in this
document.
The processed message is deleted from the [Link]. The next message is selected
and processed. If there are no messages on the [Link] then the process waits for
the next message and goes to sleep.
After processing each message, the phantom checks to see if the user has requested to stop, in which
case the process terminates and exits.
TEMENOS T24 User Guide
Page 7 of 28
Confirmation Matching
Use [Link] for automatic matching
[Link]
Full Match
The [Link] phantom matches the messages from the [Link] file.
This reads the [Link] record and gets the match keys. For the message to be matched,
first it tries to find the match using the [Link] with the messages held on the
[Link] file. If a match is found, i.e. a record is found on the
[Link] file with the same match key, then the message on the [Link]
status is changed to ‘MAT’ (matched) and the key of matched message is copied into the field MATCH.
Similarly, the record of ‘matched with’ message is also modified. The message keys of these two
matched messages are removed from the [Link] records, in the field
[Link].
If full match is not found then a new record is created in [Link] file with the
[Link] record key.
TEMENOS T24 User Guide
Page 8 of 28
Confirmation Matching
[Link] to match the messages
Part Match
If a full match is not found then, a match is attempted from the [Link] with the items
already held in the [Link]. If a match is found on the
[Link] then the original message ID is added to the [Link] field
on this record (of [Link]) and all the message keys held on this record are
copied to the message record of new matching message on the [Link] file. Now, the
message key of this record is added to the messages, whose keys are held on the [Link] field
of [Link] record. In fact this field contains the list of all messages having
the same partial match key.
If a match is not found with the [Link] then a new record is created with
the ID of the PART MATCH KEY and the details containing the ID of the message being processed.
The STATUS on the [Link] is changed to “PROCESSED”.
The process is repeated for the next message. If there are no more messages to be processed then it
will wait for the next message.
TEMENOS T24 User Guide
Page 9 of 28
Confirmation Matching
After processing a message, the process checks to see if the user has requested a stop, in which
case the process terminates and exits.
Part Match using [Link]
TEMENOS T24 User Guide
Page 10 of 28
Confirmation Matching
Setup
Setup of Confirmation Matching is minimal. The two files that will need to be populated by the user are
the [Link] and [Link], which are described in more detail later.
The details here are provided based on a configured T24 database that is already producing inward
and outward messages.
[Link]
The [Link] table contains only a single SYSTEM record. It defines the number of days a
message need stay on the system once it has been matched and is archived to the history file.
Defines parameters for the Confirmation Matching application. The key to this file must always be
SYSTEM, this is the only key allowed. The [Link] parameter stores the number of
days that messages should remain on the [Link] application after successful matching,
before being archived to the history file and removed from the live file.
It is also possible to use a user defined routine in confirmation matching, the name of the routine is
specified here.
[Link] file
Manual Matching
Users can manually match the unmatched and partially matched items.
Different Context Based Workflow enquiries have been written to allow these enquiries to launch the
[Link] application and also to automatically populate the MATCH field of the record with data
from the ENQUIRY.
TEMENOS T24 User Guide
Page 11 of 28
Confirmation Matching
[Link]
The [Link] is used to define the message types to be matched and the match tags to
be used, for outgoing and incoming messages. The outgoing and incoming tags are used with the
S.W.I.F.T. message to form the match keys.
There are two types of tags; one the [Link] and the other the [Link].
These tags must be valid for the S.W.I.F.T. message type entered i.e. it corresponds to the message
defined in [Link] and should be valid field tags on the [Link]. The
MESSAGE TYPE, RECEIVER or SENDER can also be defined for the keys.
MATCHING TAGS
These tags are used to form the mandatory part of the match keys.
OPTIONAL TAGS
These are used to form the optional part of the match key.
[Link]
There is one extra field [Link] field on this file, the value of this field is held on the
[Link] file.
Defines valid message types for confirmation matching which must exist on the [Link]
application. If this message does not exist then an error is displayed as shown below.
Error is displayed if message does not exist
TEMENOS T24 User Guide
Page 12 of 28
Confirmation Matching
Once the message type is read successfully. The body of the message type contains rules for
matching this kind of message; these are mandatory and/or optional S.W.I.F.T. tags.
Message type rules
Notice that the [Link] and [Link] are multi-valued mandatory fields and the
[Link] and [Link] are multi-valued optional fields.
When these tags are entered into the message they are prefixed internally with ‘SW’ and then
checked against the [Link] application to check if they are valid S.W.I.F.T. tags. If
these tags do not exist then an error message is generated at entry time as shown in the following
image.
[Link] displays error if the tag does not exist
TEMENOS T24 User Guide
Page 13 of 28
Confirmation Matching
In our next example we have created an extra multiple entry for the [Link] and
[Link], notice that duplicate values have been entered, these are not allowed. At the
commit record stage, errors would be generated as shown below. This will also apply for the
[Link] and [Link].
Duplicate tags are not allowed
The tag enrichment displayed comes from the [Link] record so the user can verify the
correct tag(s) have been used.
Swift tag from [Link]
A further check is made on the [Link] application, from our example; the message
type is ‘300’. This message type is then suffixed with ‘.1.1’ so that it becomes 300.1.1, this must be a
valid key on the [Link] application. The record is read from [Link],
as displayed in the example screenshot below, and the system verifies that the tag is used in that
record.
TEMENOS T24 User Guide
Page 14 of 28
Confirmation Matching
Once check is made for a valid Swift tag, record is displayed from [Link]
Any S.W.I.F.T. tags entered into the message type ‘300’ must also exist in the [Link]
record. If it does not then an error is generated at entry time as shown below.
TEMENOS T24 User Guide
Page 15 of 28
Confirmation Matching
Tag must exist in the [Link] record for the message
[Link]
The delivery system will place all S.W.I.F.T. messages in the [Link] and those of
types defined in the [Link] application are passed forward to [Link].
TEMENOS T24 User Guide
Page 16 of 28
Confirmation Matching
[Link]
This file stores messages received by the delivery process. Originally the message key and the
message body are held in its raw format in the [Link]. The message is read and
written in a sensible format to the [Link] application. Most of the message details are
generated by the system from the S.W.I.F.T. message content.
WFM – Waiting for match
TEMENOS T24 User Guide
Page 17 of 28
Confirmation Matching
The STATUS will be defaulted to ‘WFM’, which stands for “Waiting For Match”. The MATCH field will be
empty and would allow a user to select a message key from a list of message generated from the
[Link] application.
Select a message key from list of messages generated
TEMENOS T24 User Guide
Page 18 of 28
Confirmation Matching
The STATUS flag can also be changed by selecting one from the predefined list.
Status flag can be changed from predefined list
TEMENOS T24 User Guide
Page 19 of 28
Confirmation Matching
[Link]
This file stores messages that are to be matched. When these messages are processed, if
corresponding messages do not exist on the [Link] application, then one is
created and marked as processed. It in effect becomes the unmatched side. If however a message is
matched against an unmatched message, then they are matched.
[Link]
The file stores messages from the [Link] application, the key being the full matching
criteria.
[Link]
The file stores messages from the [Link] application, the key being the partial matching
criteria.
Enquiries
The three main enquiries involved in Manual Matching are:
• [Link]
• [Link]
• [Link]
Running the Enquiries
The above enquiries can be run by:
• Selecting one of the enquiries from ENQUIRY Index Menu.
• Preceding the ENQUIRY Name with ‘ENQ’ at the command line.
• Through the stack list in the Enquiry Toolbar, which stores recently, used enquiries.
TEMENOS T24 User Guide
Page 20 of 28
Confirmation Matching
ENQ [Link]
This enquiry may be used to view details of a record on the [Link] File. The required record
is selected by entering the Message ID as the selection criteria.
Enquiry [Link] details of [Link] record
TEMENOS T24 User Guide
Page 21 of 28
Confirmation Matching
ENQ [Link]
This enquiry may be used to display inward swift messages for manual matching. You can choose to
view all messages. Other selection criteria include [Link], DATE and TIME. The displayed
messages show the [Link] and the [Link].
Enquiry [Link] displays inward Swift Messages for manual matching
TEMENOS T24 User Guide
Page 22 of 28
Confirmation Matching
ENQ [Link]
This enquiry may be used to display outward swift messages for manual matching and it is selected
and displayed similar to the [Link] Enquiry.
Enquiry [Link] displays Outward Swift Messages for manual matching
TEMENOS T24 User Guide
Page 23 of 28
Confirmation Matching
MANUAL MATCHING USING ENQUIRIES
Since the Match Keys for both the inward and the outward Swift Delivery Messages are displayed in
the above enquiries, possible matches, with similar Match Keys can be easily spotted.
Viewing Records
To see a more detailed view of the record, click the mouse on any of the Delivery Messages in the
[Link] or the [Link] Enquiries to display the following options:
View Record: (magnifying glass icon)
Shows the Delivery Message as a Report Enquiry, with the Message Key in the header, and full
details including Swift Body and Swift tags in the body of the report.
Delivery Message as Report Enquiry with Message Key in Header
TEMENOS T24 User Guide
Page 24 of 28
Confirmation Matching
View Details
This option may be used to view details of a record on the [Link] file. The [Link] are
arranged in ascending order with the corresponding [Link].
View details of a record on the [Link] file
TEMENOS T24 User Guide
Page 25 of 28
Confirmation Matching
Matching Records
Match Items
This option brings up the [Link] record for the relevant [Link].
Match items from [Link] record
TEMENOS T24 User Guide
Page 26 of 28
Confirmation Matching
Records can be manually matched from this screen, either by typing an existing delivery message key
in the MATCH field, or by double clicking on the Delivery Message key in the [Link] and
[Link] Enquiries.
Match records manually using [Link],[Link]
Using features such as Auto Launch Enquiries and displaying the messages can make the manual
matching a lot easier.
TEMENOS T24 User Guide
Page 27 of 28
Confirmation Matching
View [Link]
This file will not have a T24 program behind it as it contains the actual S.W.I.F.T. message in one field,
which could be too long for T24 to interpret. Viewing this file is done through a specially written enquiry
[Link]. The file is made up of a general T24 message key of D/R for delivery or
received and 8 -digit date and 7- digit time (from midnight). There is only one field that contains the
whole message.
TEMENOS T24 User Guide
Page 28 of 28
