Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
TEMENOS T24
SWIFT 2015 Installation Notes
Version 6.0
No part of this document may be reproduced or transmitted in any form or by any means,
for any purpose, without the express written permission of TEMENOS HEADQUARTERS SA.
TEMENOS Confidential Page 1 SWIFT Standards 2015 Installation notes.docx
2010 Temenos Headquarters SA - all rights reserved.
SWIFT Standards MT November 2015
Table of Contents
1 Introduction .................................................................................................................................... 5
2 Update Details ................................................................................................................................ 5
3 Installation Process ....................................................................................................................... 8
3.1 Updates ................................................................................................................................ 8
3.2 Installation of S5 Module ...................................................................................................... 8
3.2.1 SPF .................................................................................................................................... 8
3.2.2 COMPANY ......................................................................................................................... 9
3.2.3 T24.UPGRADE Service ..................................................................................................... 9
3.3 SWIFT.PARAMETER table ................................................................................................ 10
4 New functionality ......................................................................................................................... 11
4.1 Overview of Swift 2015 changes ........................................................................................ 11
4.2 SWIFT.PARAMETER......................................................................................................... 11
4.2.1 Example Restricted currency ........................................................................................ 12
4.3 Overview and Setup for TAG59F ....................................................................................... 14
4.3.1 Funds Transfer ................................................................................................................. 15
4.3.2 Standing Order ................................................................................................................. 18
4.3.3 Example Tag 59F ............................................................................................................. 20
4.3.3.1 Funds Transfer Outward ........................................................................................... 20
4.3.3.2 FT Inward Tag 59F ....................................................................................................... 21
4.4 Swift Ref ............................................................................................................................. 23
4.4.1 Identify using OFFICE TYPE ........................................................................................... 23
4.4.2 Identify using Group type ................................................................................................. 24
4.4.3 Default identification ......................................................................................................... 24
4.5 Forex/Swap MT360 & MT361 ............................................................................................ 24
4.5.1 Configuration .................................................................................................................... 25
4.5.1.1 Forex ............................................................................................................................ 25
4.5.1.2 Swap............................................................................................................................. 29
5 Further Information ...................................................................................................................... 34
5.1 Contact Details ................................................................................................................... 34
1 Introduction
This document contains the installation process for the Swift 2015 changes.
2 Update Details
The following table contains details of the updates that are required to be installed for the Swift 2015
changes
T24Update R11_FT_StandingOrders_23
T24Update R11_AC_PaymentNetting_5
T24Update R11_FT_Contract_57
Payment changes T24Update R11_DE_Inward_2
T24Update R11_DE_Outward_15
T24Update R11_DE_ModelBank_11
T24Update R11_DE_Messaging_7
T24Update R11_FT_Delivery_5
Payment changes
T24Update 201408_FT_Contract_16
Forex 201408_FX_Contract_11
Swaps 201408_SW_Delivery_2
T24Update 201507_IN_IbanAPI_1
For Release R07 R08 and R09 please contact your account manager.
Note In addition to the above updates the activation of the changes will also be dependent on the
installation of the S5 Module; please contact your account manager.
As previously advised releases prior to R13 are subject to a fixed price charge, please contact your
account manager for further details.
3 Installation Process
The following process should be followed to install the swift 2015 changes.
3.1 Updates
Please refer to the table above which contains details of the updates that are required per release. The
standard updated installation process should be followed.
For clients on Release R13 or above both the SF and S5 modules are required to be installed in the
system.
3.2.1 SPF
Add the new product to the PRODUCTS field on the SPF (System Parameter File). In the following
field, PRODUCT.CODES, enter the product code you have been given. Authorise the record.
3.2.2 COMPANY
Add the new product to the APPLICATIONS field on the COMPANY file. When the upgrade service is
running each COMPANY record is checked to see what products are installed; updates are released
for any existing products or when installing a new product the required files are created and any
records for that new product are released. Most new products will have files created even if no records
are released so updating the COMPANY record(s) is a vital step.
The TSA.SERVICE T24.UPGRADE is also used to add new products to T24. Before running the
service the BATCH record associated with the service (E.G BNK/T24.UPGRADE) needs to have the
product code(s) added to the DATA field. It is recommended that once the product(s) have been
installed that the BATCH record is amended again to clear the DATA field ready for the next upgrade.
Once the BATCH record is authorised the T24.UPGRADE service can be run.
The same post install actions need to be taken as in a full release upgrade.
Note: In the live environment this should be done on the date that you require these changes to
be live
NOTE: Please do the below setup initially in the test environment and then in the live
environment after confirmation of test results.
4 New functionality
4.1 Overview of Swift 2015 changes
The following enhancements have been made to T24 to
Provide the ability to restrict certain currencies from being used in specific payment
messages
Support TAG59F
IBAN - Provide the ability to identify a Unique National ID
4.2 SWIFT.PARAMETER
A new table SWIFT.PARAMETER is introduced providing the following functionality.
Provision to restrict certain currencies from being used in specific message types
Allow the activation of the new changes in the environment on a specific date
The fields RESTRICTED.CCY and MESSAGE.TYPE are used to define currencies that are restricted
from being used in certain message types.
For example precious metals are restricted to the MT6xx series messages. The following example
shows the currency code XAU being restricted for MT101 message types.
If a restricted currency is entered into a transaction, where the field SEND.PAYMENT is set to Yes;
the system checks for the restriction of the currency for both the debit and credit in the
SWIFT.PARAMETER table; if the currency is restricted, a corresponding override is generated.
Should the override be accepted the payment message is moved to the REPAIR queue when the
formatting service SWIFT.OUT is run.
The DE.O.HEADER record is moved to repair when the SWIFT.OUT Service is run.
IN.BEN.CNTY.59F
IN.BEN.TOWN.59F
1. Create four new records in LOCAL.TABLE with id as given below
Note for Releases R07, R08 and R09 the following LOCAL.REFERENCE fields are required to be
configured in FUNDS.TRANSFER
Below is a preview of the outgoing message with the fields mapped to Tag 59F.
An inward message is updated in the system. The following fields are populated with the
relevant data from the inward message from Tag 59F
IN.BEN.NAME
IN.BEN.ADDRESS
IN.BEN.COUNTRY
IN.BEN.TOWN
The following example shows a set of records where one record is a Head Office and the
others are Domestic Branches:
RECORD KEY OFFICE PARENT OFFICE KEY NATIONAL ID INSTITUTION NAME STREET ADDRESS 1
OFFICE TYPE
BD0000000ABW DB BD0000000ACR 12000 UNICREDIT BANK Wienerstrasse 24
AUSTRIA AG
In this example T24 will use the record BD0000000ACR as this is the only record with the OFFICE TYPE
defined as HO.
RECORD KEY OFFICE PARENT OFFICE KEY NATIONAL ID INSTITUTION NAME STREET ADDRESS 1
OFFICE TYPE
BD0000000ACR HO BD0000000ACR 12000 UNICREDIT BANK Schottengasse 6-8
AUSTRIA AG
In this example T24 would use record BD0000000JB5 as this record is the only record with the
GROUP.TYPE is defined as Parent
RECORD KEY OFFICE GROUP TYPE COUNTRY NATIONAL ID INSTITUTION NAME
TYPE CODE
BD0000000JB5 HO Parent US 11300595 CAMBRIDGE TRUST COMPANY
In this instance T24 would use record BD0000000ACE as this is the 1st record in the list
above
RECORD KEY OFFICE COUNTRY NATIONAL INSTITUTION NAME CITY
TYPE CODE ID
BD0000000ACE DB AT 11990 UNICREDIT BANK AUSTRIA Ternitz
AG
4.5.1 Configuration
In addition to the updates, the following configuration is required to support the above changes for
releases R10, R11, R12, R13, AMR14, AMR15, 201407, 201408, 201412 and 201507.
Note: The version names used in the below screen shots can be configured as per the client requires
4.5.1.1 Forex
Field level validation for METAL.TYPE and QUANTITY
When METAL.TYPE is GOLD, QUANTITY must be GOZ or TOZ
When METAL.TYPE is PALL, PLAT or SILV, then QUANTITY must be GOZ
Validation errors should be raised if any other values are specified for QUANTITY.
Step 1
Create a version for FOREX.
Step 2
Create a record in EB.API for the version routine.
Step 3
Attach the version routine to do the validation for METAL.TYPE and QUANTITY fields.
Example
The following example shows the field validation within the Forex module using the above version and
routine.
4.5.1.2 Swap
The following configuration is required to support the changes in the Swap module.
Step 1
Create a MARKET.RATE.TEXT with RATE.TEXT as OTHER.
Step 2
Attach the routine to the swap 360/361 message in the DE.MAPPING application.
Step 3
Create a contract in Swaps and commit the record
Delivery Message
5 Further Information
5.1 Contact Details
Area Product Manager Contact Address