Professional Documents
Culture Documents
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.
Table of Contents Introduction .............................................................................................................................................. 5 Application Framework ............................................................................................................................ 5 T24 Java Deployment .......................................................................................................................... 5 Application Framework released enhancements ................................................................................. 5 Public API for adding OFS Bulk request .......................................................................................... 5 Banking Framework................................................................................................................................. 6 IFRS Phase 2 ....................................................................................................................................... 6 Impairment ....................................................................................................................................... 6 Reclassification of Assets ................................................................................................................ 6 Enterprise Customer - Publishing ........................................................................................................ 7 360 degree view of customer ........................................................................................................... 7 New Service operations for Customer: ............................................................................................ 7 Data quality ...................................................................................................................................... 7 AA performance and Infrastructure ...................................................................................................... 7 Banking Framework released enhancements ..................................................................................... 8 Interest and Charges ........................................................................................................................ 8 Provisioning .................................................................................................................................... 13 Enterprise Customer - Publishing .................................................................................................. 16 Business Intelligence ............................................................................................................................. 16 Insight wealth Management ............................................................................................................... 16 Insight Web Services ......................................................................................................................... 17 T-Risk DW.EXPORT .......................................................................................................................... 17 Insight DW ......................................................................................................................................... 17 Insight Generic ................................................................................................................................... 17 Insight TCE ........................................................................................................................................ 18 Business Intelligence released enhancements.................................................................................. 18 TRisk .............................................................................................................................................. 18 Corporate ............................................................................................................................................... 19 Enhancements to Syndicated Loans ................................................................................................. 19 Corporate released enhancements ................................................................................................... 19 Miscellaneous Deals ...................................................................................................................... 19 Syndicated Loans ........................................................................................................................... 20 Letter Of Credit ............................................................................................................................... 21 Payments ............................................................................................................................................... 21 Payments Released enhancements .................................................................................................. 21 Funds Transfer ............................................................................................................................... 21
Page 2 of 61
Delivery .......................................................................................................................................... 22 Process Orchestration ........................................................................................................................... 22 PW Designer ...................................................................................................................................... 22 Various enhancements to PW ........................................................................................................... 22 Process Orchestration released enhancements ................................................................................ 22 Process Workflow........................................................................................................................... 23 Retail Banking ....................................................................................................................................... 24 Term Deposits .................................................................................................................................... 24 Arrangement Architecture .............................................................................................................. 24 Cooling off period for Lending and Deposits: ................................................................................. 24 Current and Savings Accounts Phase 1 ............................................................................................ 26 Loan Provisioning .............................................................................................................................. 27 Model Bank Upgrade ......................................................................................................................... 28 Retail released enhancements .......................................................................................................... 28 Arrangement Architecture .............................................................................................................. 28 Retail Accounts .............................................................................................................................. 32 Loans and Deposits........................................................................................................................ 37 Retail Front Office.................................................................................................................................. 37 Retail Front Office released enhancements ...................................................................................... 38 Teller............................................................................................................................................... 38 Loan Origination ............................................................................................................................. 38 Arc Internet Banking ....................................................................................................................... 39 Arc Mobile Banking ........................................................................................................................ 40 Business Events ................................................................................................................................ 42 Business Events Product ................................................................................................................... 42 Securities ............................................................................................................................................... 42 Third Party Custody and Order Routing ............................................................................................ 43 Online Portfolio Valuation .................................................................................................................. 46 Securities Released Enhancements .................................................................................................. 47 Repos ............................................................................................................................................. 47 Corporate Actions ........................................................................................................................... 47 Securities Trading .......................................................................................................................... 48 Security .................................................................................................................................................. 50 Secure Source Code .......................................................................................................................... 51 R11 Internal Penetration Testing ....................................................................................................... 51 Security Processes ............................................................................................................................ 51 Authentication Server Enhancements ............................................................................................... 51
Page 3 of 61
Transaction\Verification Signing in 4TRESS .................................................................................. 52 Security released enhancements ...................................................................................................... 52 SOA Framework .................................................................................................................................... 52 Business Activity Monitoring .............................................................................................................. 53 Object Model and SOA Framework (Customer) ................................................................................ 53 TWS Enhancements for AA and consuming WS .............................................................................. 53 TAG Replacement and .net Connectivity........................................................................................... 54 TAFC Platforms R11 .......................................................................................................................... 54 SOA Framework released enhancements ......................................................................................... 54 TWS Artifacts ................................................................................................................................. 54 Treasury ................................................................................................................................................ 55 Swift 2010 Updates (600 series) ........................................................................................................ 56 Linear Revaluation method for Swaps ............................................................................................... 56 Treasury released enhancements ..................................................................................................... 56 Derivatives ...................................................................................................................................... 56 Money Market................................................................................................................................. 56 Swaps ............................................................................................................................................. 57 Forward Rate Agreements ............................................................................................................. 57 Wealth Management ............................................................................................................................. 58 ARC IB ............................................................................................................................................... 58 Asset Structures & Alerts ................................................................................................................... 58 Client Reporting ................................................................................................................................. 58 Model Bank ........................................................................................................................................ 59 MiFID.................................................................................................................................................. 59 Investment Profiling ........................................................................................................................... 59 Wealth Management Release Enhancements .................................................................................. 59 ARC-IB Improvements ................................................................................................................... 60 Asset Structures & Alerts ............................................................................................................... 60 Client Reporting.............................................................................................................................. 61 MiFID .............................................................................................................................................. 61 Model Bank .................................................................................................................................... 61
Page 4 of 61
Introduction
This document provides where possible a high level overview of the Strategic Enhancements that have been delivered in R11 GA, along with a breakdown of the individual enhancements that form them.
Application Framework
The following Strategic Initiatives have been delivered R11 GA from Application Framework.
T24 for Java will have the following features: Deployable on any Java-compliant platforms including mainframes, and will take full advantage of the features offered by JEE platforms, such as Application Server deployment and Clustering. All connections to T24 database will be made via JDBC, to industry standards, and will be XA compliant. No proprietary drivers will be required. Will include a full, feature rich development environment for T24 in Eclipse, including standard debugging facilities.
The SI also covers performance analysis and improvement for the Java solution, as well as the first pilot deployment with, which is currently ongoing.
Page 5 of 61
Banking Framework
The following Strategic Initiatives have been released in R11 from Banking Framework.
IFRS Phase 2
The following briefly highlights the requirements to provide the IFRS2 functionality within T24:
Impairment
Ability to identify contracts as Individually Significant Ability to manually capture and record objective evidence of impairment at contract or group level. Ability to manually capture and record the expected Cash flow and Collateral Value and to calculate a recoverable value for a contract. Ability to calculate impairment loss Ability to perform an impairment test for contracts and generate the appropriate accounting entries for impairment loss that may be significant or prolonged. Ability to automatically process impairment provisioning, triggered by the past due aging of Arrangement Accounts (AA). Ability to reverse impairment for relevant contracts Ability to group contracts with same credit risk characteristics Ability to calculate the impairment provisioning for impaired and unimpaired groups and to generate the accounting entries. Ability to generate required accounting entries for financial events affecting an impaired contract (e.g. repayment, write-off, rescheduling etc).
Reclassification of Assets
Ability to define rules for possible reclassification Ability to calculate the EIR for an instrument previously valued at fair value and reclassified to amortised cost. Ability to provide information for Disclosure
Page 6 of 61
Ability to assess for impairment if instrument is reclassified as Loans and Receivable, Held to Maturity or Available for Sale and generate the required accounting entries
Data quality
The main feature of a master customer data system is to avoid duplicate data being maintained. This will be provided at a minimum level by catching duplicate records as and when they are input through the EB.DUPLICATE.CHECK application that is already available and then allowing users to merge the existing duplicate records.
Page 7 of 61
Products are built by users, and named activities are created for those products. Once this process is over users may wish to publish these products as web services. For example, Create New Personal Loan or Amend Interest Recurring Deposits may be the exposed services while personal loan and deposits could be the named products created, with AA publishing controlling the process. AA has many utility routines such as charge calculations and interest calculations which can be exposed as web services so that other systems can access these functions. These routines can be executed through an ACTIVITY which can also be exposed. Subroutines in T24 can therefore be exposed without having to use a VERSION or an ENQUIRY. Local reference fields from property files can be input or amended with the local reference field names being shown as field labels rather than LOCAL.REF.1, etc
Page 8 of 61
The application IFRS.DATA.CAPTURE is added to capture details of contracts to be used for impairment accounting, reclassification of financial instruments and takeover of the existing contracts for IFRS accounting. This enhancement covers fields and field validation only.
NB This enhancement provides part of the functionality from the strategic enhancement 9366 IFRS impairment and reclassification,
Impairment loss Calculation & accounting - individual assessment (Fair Value & Schedule Provisioning)
Enhancement 28085 Build 201012 This enhancement has introduced functionality to support the impairment loss calculation for contracts valued at FAIRVALUE and FAIRVALUE through EQUITY. The following ACCOUNTING.HEADs have been introduced to facilitate this; AMORTISED.UNDER.IMP, IMPAIR.FAIRVALUE, IMPAIR.FV.ADJ.DEC, IMPAIR.FV.ADJ.INC. The main features of this enhancement are: Accounting for contracts valued at Fair Value, and both Fair Value and Amortised cost Impairment schedule processing. Impairment of Foreign Currency contracts, and revaluation of Provision
NB This enhancement provides part of the functionality from the strategic enhancement 9366 IFRS impairment and reclassification.
Page 9 of 61
The unrealised loss arising from Available for sale (AFS) portfolios will be booked under profit and loss category if the underlying Security in which the portfolio held the position is classified as impaired. The subsequent profits (i.e. still unrealised loss) after Impairment will be booked under the existing profit suspense account. The impairment can also be cancelled and revaluation will happen as per the existing functionality.
NB This enhancement provides part of the functionality from the strategic enhancement 9366 IFRS impairment and reclassification.
Impairment Loss Calculation & Accounting - Individual Assessment (Fair value & schedule provisioning)
Enhancement 28085 Build 201013 The functionality introduced through this enhancement is is designed to do impairment loss calculation for contracts valued at FAIRVALUE and FAIRVALUE through EQUITY. This enhancement includes the following: Accounting for contracts valued at Fair Value, and both Fair value and Amortised cost Impairment schedule processing. Impairment of Foreign Currency contracts, and revaluation of Provision Additional validation on field Operation and Effective date in IFRS.DATA.CAPTURE
The following new accounting heads have been introduced AMORTISED.UNDER.IMP IMPAIR.FAIRVALUE IMPAIR.FV.ADJ.DEC IMPAIR.FV.ADJ.INC.
The fields ASSET.TYPE, ASSET.NAME, ACCT.HEAD have been renamed to ACCT.HEAD.TYPE in applications IFRS.ACCT.BALANCES, IFRS.ACCOUNTING.DETAILS, IFRS.POSTING.DETAILS and IFRS.ACCT.METHODS.
NB This enhancement provides part of the functionality from the strategic enhancement 9366 IFRS impairment and reclassification.
The system will reverse the accounting entries and update the relevant EB.CASHFLOW and IFRS.ACCT.BALANCES as relevant.
NB This enhancement provides part of the functionality from the strategic enhancement 9366 IFRS impairment and reclassification
Page 10 of 61
IFRS.DATA.CAPTURE has been enhanced to accept a new operation 'CORRECTION'. Through this it is now possible to amend the IAS.SUBTYPE and IAS.CLASSIFICATION of a contract if it has been incorrectly classified at input. The system will reverse any previous accounting entries and recalculate as of today.
NB This enhancement provides part of the functionality from the strategic enhancement 9366 IFRS impairment and reclassification.
NB This enhancement provides part of the functionality from the strategic enhancement 9366 IFRS impairment and reclassification.
Page 11 of 61
Check that the impaired balance does not exceed the T24 balance
Enhancement 80479 Build 201014 Through the functionality introduced in this enhancement a check will be performed during the COB that the total balance of all the impairment ASSET.TYPES does not exceed the T24 book value. If it exceeds an entry in EXCEPTION.LOG.FILE will be booked with an error message. A check is also performed to see if the Recoverable value (NPV of the expected cash flow + Present value of collateral) doesnt exceed the T24 book value in case of an impaired contract. If it exceeds an exception is logged in EXCEPTION.LOG.FILE.
Page 12 of 61
If the FX.REVAL field in the SEC.ACC.MASTER application is set to "Y" then revaluation of currency profits/losses will be posted during the SC.REVAL.PROCESSING during the close of business. Input to the FX.REVAL field is only allowed for AFS type Portfolios. The resulting revaluation entries will be posted to the Categories as specified in the SEC.ACC.MASTER fields UNREAL.FX.PRT and UNREAL.FX.LOSS, depending on whether there is a gain or a loss. The actual posting method will be based on the value entered in the REVAL.POST.METHOD field of the SEC.ACC.MASTER that is, "I/O" or "ADJ".
Provisioning
PV Template layouts
Enhancement 81141 Build 201012 The applications PV.MANAGEMENT, PV.PROFILE, PV.LOAN.CLASSIFICATION, PV.ASSET.DETAIL and PV.CUSTOMER.DETAIL have been introduced for the new Provisioning Module.
NB This enhancement provides part of the functionality from the strategic enhancement 9366 IFRS impairment and reclassification
The Classification process with the Classification details The Calculation process with Calculated amount The Provisioning process with the re-calculated and posted amount The Manual correction of the Classification or Provision amount
NB This enhancement provides part of the functionality from the strategic enhancement 9366 IFRS impairment and reclassification
NB This enhancement provides part of the functionality from the strategic enhancement 9366 IFRS impairment and reclassification.
The selection will be triggered if the NEXT.CALC.DATE from the PV.MANAGEMENT.CTRL record is less or equal to the Period End date
NB This enhancement provides part of the functionality from the strategic enhancement 9366 IFRS impairment and reclassification.
Page 14 of 61
NB This enhancement provides part of the functionality from the strategic enhancement 9366 IFRS impairment and reclassification.
Page 15 of 61
The selection will be triggered if the NEXT.POST.DATE from the PV.MGMNT.CONTROL record is less or equal to the Period End date.
NB This enhancement provides part of the functionality from the strategic enhancement 9366 IFRS impairment and reclassification.
Customer Services
Enhancement 43265 Build 201012 The following customer services have been released Activate Customer Get Related Party Content Update Customer Preferences Get relation between parties Get preferred Contact Point Update and get operations on Customer address Get carrier address Get customer with Legal ID
Business Intelligence
The following Strategic Initiatives have been delivered in R11 GA from Business Intelligence.
Page 16 of 61
Sell this as an added module to Insight for Wealth Management banks Include a Data Event module within Insight to send email alerts
T-Risk DW.EXPORT
T-Risk currently works from T24 enquiries. This SI will change T-Risk to work from DW.EXPORT data. The benefits of this are: Allows T-Risk and Insight to share data (single source) Close any Gaps discovered in current implementations Clients are all looking for an integrated Insight + T-Risk solution.
Insight DW
As BI becomes increasingly important to banks, Temenos aspires to selling Insight to any bank whether or not they have T24. This has significant commercial importance to Temenos and can open doors into new accounts where the bank is not currently looking to change their core system.
To position Insight as a generic BI solution we have to publish the Insight data model as well as publish a standard interface for Insight. In this way banks or system integrators can supply customer and financial data to Insight via a standard interface, and then the Insight functionality and standard reports become available to the bank.
Insight Generic
This enhancement forms the first step in making Insight a generic BI solution for any banking system.
The development of this SI will be closely linked to SI 19432 Insight Data Model. Insight Retail Metrics Insight is currently focused around financial measures and performance based around the banks General Ledger. This provides a variety of balance sheet and Profit & Loss reports showing actual versus budget reporting over the financial year.
Page 17 of 61
This development will define multiple levels of dashboards according to an employees responsibility. It will include a Data Event module within Insight to send email alerts.
Insight TCE
This SI enhances the existing Insight data extract tool to do the following: Allows continuous extract of transactions during business hours Allows intraday T24 transaction events to be generated from Insight Allows incremental changes to be supplied to Insight rather than a full end of day extract (i.e. customer change)
Page 18 of 61
DW.EXPORT
Enhancement 65238 Build 201009 This enhancement provides a utility to configure DW.EXPORT while implementing it for the first time.
Corporate
The following Strategic Initiatives have been delivered in R11 GA from Corporate.
Miscellaneous Deals
MD - Last day commission for CSN.TYPE END
Enhancement 51085 Build 201009 T24 will now collect todays accrued commission amount along with the commission amount accrued till the previous day when online maturity takes place. The following must be present for this to happen, ONLINE.MAT must be set to YES, with the EB.ACCRUAL.PARAM value set as BOTH or LAST, CSN.PAYMENT.TYPE as END.
Page 19 of 61
will
be
updated
with
the
last
day
accrual
amount
with
Syndicated Loans
SL - Change of loan interest calculation days basis
Enhancement 52584 Build 201012 SL.LOANS has now been modified to allow the user to amend the INTEREST.BASIS field on a contract on any day during the life of the loan. The system will record the entries separately and calculate the total interest and pass as one entry at maturity
SL - Repayment schedules
Enhancement 52600 Build 201012 T24 now allows the user to specify the amortisation period for which the repayment schedule has to be defined and this facility gives the borrower the advantage of borrowing for a shorter term whilst repaying a regular reduced amount (than would normally be paid) according to the extended annuity schedule.
Page 20 of 61
Letter Of Credit
LC - Import LC Issue via ARC IB
Enhancement 16211 Build 201013 The ability for Corporate Clients to request the Issuance of Letters of Credit through Internet Banking (ARC IB) has been re-written. It is now possible to input all relevant Letter of Credit details via ARC IB and to monitor the progress of their request at all times via ARC IB enquiries, for example, to ascertain whether T24 Bank has acted on their request, to ascertain whether the request has been dealt with or perhaps returned for more details. T24 Bank also has the option to decide whether the clients limits are updated at the time of input via ARC IB or at the time of input at the T24 Bank.
Payments
The following Strategic Initiatives have been delivered in R11 GA from Payments.
Funds Transfer
FT Bulk Payments
Enhancements 59073 and 73319 Build 201012 Using the t24 File Upload applications it is possible to do the following in Funds Transfer Bulk processing: Ignore fields in a Source file by defining "*" in Versions Upload Fixed Length files
Page 21 of 61
Upload files without Header information Default Header information via a Version.
Delivery
In and Out Message Console
Enhancement 26555 Build 201008 The DE.MM.O.END.OF.PERIOD application in the DELIVERY module has become a Service.
Process Orchestration
The following Strategic Initiatives have been delivered R11 GA from Process Orchestration
PW Designer
Process Workflow Designer will allow definition of workflows by modelling the business workflows graphically. The PW Designer will be an eclipse plug-in and will work alongside an additional eclipse plug-in for modelling business workflows, which, once the model is complete, exports the model in XML. The XML export is consumed by the PW Designer plug-in, and the workflow model is then enriched with further information required for PW, such as T24 versions, file names and related attributes. The plugin with then interface with T24 to create the underlying process definitions, activities etc. in PW.
Various enhancements to PW
Various enhancements to Process Workflow, including Pattern based workflow Activity Reusability Activity duration analytics Loan Origination Model Bank PW requirements Abstraction layer
Page 22 of 61
Process Workflow
Activity Reusability
Enhancement 14269 Build 201005 A new field ACTIVITY.OWNER is introduced in PW.PROCESS.DEFINITION. The user can either define the OWNER at activity level or Process definition level. The OWNER field defined in PW.PROCESS.DEFINITION takes precedence over the OWNER defined at activity level.
Arbitrary Loop
Enhancement 26655 Build 201015 Activities which have already been executed within a process can be revisited without any condition. This is achieved by following fields in PW.PROCESS.DEFINITION - PATTERN.CONSTRUCT, ROUTE.TO.ACTIVITY, ROUTE.ACTIVITY.STATUS and PRE.REQ.CONSTRUCT
Structured Loop
Enhancement 26656 Build 201015 Activities which have already been executed within a process can be revisited without any condition. This is achieved by following fields in PW.PROCESS.DEFINITION - PATTERN.CONSTRUCT, ROUTE.TO.ACTIVITY, ROUTE.ACTIVITY.STATUS and PRE.REQ.CONSTRUCT. The field ROUTE.EVAL.CONDITION is introduced in PW.PROCESS.DEFINITION to define a routine name which controls the execution of activity based on a condition. If the condition is true, the system will loop back to the already executed activities.
Recursion
Enhancement 26657 Build 201015 An activity can be executed recursively till the given condition is true. The fields RECURSION.EVAL.CONDITION, RECURSION.EVAL.RULE and CONSTRUCT.STATUS are introduced in PW.PROCESS.DEFINITION to define the recursion
Page 23 of 61
CASE.ACTIVITY and DEF.ACTIVITY have been introduced in PW.PROCESS.DEFINITION to define these patterns.
Retail Banking
The following strategic initiatives have been delivered in R11 GA from Retail Banking.
Term Deposits
The purpose of this SI was to enhance the current features in the deposit module with a generic development approach across all product lines.
It is required to allow withdrawal or pre-closure of the deposited/disbursed amount within a time frame termed as Cooling-off period without charging the customer. In case of deposits bank will not pay any interest and for loans customer will not owe any interest.
Any charges that have been collected during cooling period need to be reversed back. Rollover: Term Amount controls the conditions and restrictions for the amount and term that can be committed to the customer. Actual amount and term of the arrangement can be defined at arrangement level or the defaulted values from the product level can be used as it is. With some products at the end of the
Page 24 of 61
term, a customer can choose to rollover the account this can be performed manually or automatically. The option is also available to change the product at rollover.
The term definition is used to calculate a maturity date for the arrangement contract, this date can either be entered directly or will default based upon the effective date of the property and applying the defined term value.
In case of call contracts, both term and maturity date can be left blank, this would facilitate automatic rollover of arrangements. Overdue Statistics: Overdue can either be specified in terms of days or by number of bills. This development was based on the requirements for savings plans.
As and when a bill moves into a particular aging status, the relevant details like the current aging status and the date of movement is stored in the respective bill. AA updates overdue status in each bill and also updates the overall arrangement overdue status.
The information is recorded relating to overdue statistics such as number of times, average days, average amount and the dates in which funds have moved into and out of a particular aging status. Once an arrangement reaches a particular aging status all further bill amounts, as and when the bills are issued, will be added to the oldest aging status irrespective of the aging status of the bill. Relative dates in Payment Schedule: The start date and end date can be used to define the payment schedule in such a way that all the schedules can fall within this period. For example a deposit is required to start one month from first receipt of funds. * R_XXXX + 2D - (Relative event XXX and offset by 2 Calendar days forward) * R_XXXX - 5Y - (Relative event XXX and offset by 5 Years backward) * D_20001130 - (Exact date specified as 30th Nov 2000) Following relative events can be defined: * START - First deposit, first disbursement. * MATURITY - Maturity of arrangement. * RENEWAL - Renewal date for arrangement.
A relative date start date or end date can be defined based on events. The illustration shows how to define an end date as maturity minus 2 weeks. R_MATURITY 2W. Cancellation period: The option of scheduling cancellation of a deposit account by specifying the number of days before which the account will be cancelled, can be set by the number of days before hand as to when the pre-notification advice is to be generated and sent to the customer, before the account is cancelled.
Page 25 of 61
The arrangement will move to pre-close status or cancelled if not funded or partially funded respectively.
Funds lying in the current account will automatically be moved to the unallocated balance once the cancellation period has crossed and the account is only partially funded, with the option of redeeming the funds that have either been fully deposited as per commitment or partially.
Any accrued interest during the cancellation period will be reversed if the account is not funded within the cancel period. A deposit can be funded even after it has moved to cancel status, after cancellation period, if the fund transfer is back dated. If the deposit is fully funded, backdated, account will move to current status and if not funded or partially funded, will remain cancelled.
Pre-notification is also possible for takeover contracts, but with effect from the date of takeover and not from the original date of contract. Deposits: New deposits products have been configured with auto rollover functionality.
Rollover of Deposits arrangements is similar to what is available in Lending Product line. Rollover of the outstanding principal on the renewal date would happen based on the payment schedule definition. The Rollover period should be within the term specified.
Funds lying either in the payable principle balance, unallocated balance or current balance can be withdrawn with the suitably defined rules.
Excess amount paid over a bill automatically moves to the unallocated balance, thereby making it available for withdrawal. The option of controlling the withdrawals from a contract in a given period of time can be controlled by restrictions created; inclusive of charge creation for withdrawals more than the permissible ones. The charges can also be deferred over a certain period of time, depending upon the customers requirement.
A charge API for collecting charges during Partial withdrawal. A local charge amount routine can be attached to calculate the charge amount for early redemption activity. This API can be enhanced with different calculation methods as per the requirement of the customer.
Page 26 of 61
There will be no need to create a limit AA will do this automatically; overdraft limits can be defined and maintained as part of the product definition. Account rules (Activity Restriction): This will provide a single screen through which all rules relating to the application / waiving or interest and charges will be defined. Periodic Charges: The equivalent of General Charge and all of its associated tables on one screen. Charging frequency set at product / arrangement level. Eligibility rules: Rules based eligibility checking linked to rules engine - is a replacement for condition priority Enhanced change primary owner: The new primary owner does not need to be a joint holder. If limits are specified then they are updated and the balances are moved to the changed primary customers limit. The ability to define a bundle new product line.
Products allowed for example mortgage plus current / savings account plus term deposits. These can be defined to include mandatory products, maximum number of products, interest options and repayment schedules. The potential use of this facility is for example offset mortgage products, interest pooling allowing combined interest and bonus interest in addition to arrangement level interest. Settlement Property: The settlement property has been enhanced to provide a facility where the user can mention an internal account for settling the dues in case of lending arrangements and for liquidation purposes in case of deposits and savings arrangements.
Loan Provisioning
The components of the new Provisioning Module (PV), this module will be developed in conjunction with the Banking Frame work stream, please refer to this stream for specific details on the new module. Provision Management: Frequency, default settings Classification Groups o o o Selection Criteria Link to classification rule or API Link to provisioning profile
Provision Profile: Calculation Type (Percentage, IFRS, API) Source Balance Percentages Collateral Usage
Page 27 of 61
Re-work all major retail enquiries, versions and transactions so they only show relevant and required information (i.e. an account to account transfer that just has from and to account numbers (searchable by customer and amount most retail capability in model bank is very poorly thought out). Add or enhance some process orchestrated capabilities one stop account opening is totally unusable even if this is now strictly front office there are loads of similar examples such as payment investigations etc, that should be better automated. Add proper retail products to model bank. Build a model ledger that would require only moderate customisation to address most cases. Improve the documentation. Rebuild Teller functions around the new multi line teller delivered as part of R10. Build better management processes associated with the new model bank.
Arrangement Architecture
Cooling off Period for arrangements
Enhancement 19289 Build 201005 The TERM.AMOUNT Property Class controls the conditions and restrictions for the amount and term that can be committed to / from the customer. The processing for Product Lines DEPOSITS, LENDING and SAVINGS has been enhanced with a new field called COOLING.PERIOD which accepts a value of nnnnD, nnnnW or nnnnM. The live table AA.ACCOUNT.DETIALS has also been updated with a new field COOLING.DATE. This enhancement forms the basis for the cooling of process for Deposits and Lending products.
Page 28 of 61
Overdue Statistics
Enhancement 19307 Build 201006 Overdue in AA are handled by the OVERDUE Property Class. As and when a bill moves into a particular aging status, the relevant details like the current aging status and the date of movement is stored in the respective bill. AA updates the overdue status in each bill and also updates the overall arrangement overdue status in AA.ACCOUNT.DETAILS. For the LENDING Product Line a new live table called AA.OVERDUE.STATS is used to store by arrangement information relating to overdue statistics such as number of times, average days, average amount and the dates in which funds have moved into and out of a particular aging status.
Enhance updating of Maturity Date for CRF reporting and Overview Enquiry
Enhancement 19300 Build 201007 A new field REPORT.END.DATE has been introduced AA.ACCOUNT.DETAILS. This field is updated based not only on MATURITY.DATE but also for contracts with no maturity being specified and for renewal contracts.
Page 29 of 61
Settlement Property
Enhancement 56319 Build 201009 The Settlement property has been enhanced to provide a facility where the user can mention an internal account for settling the dues in case of lending arrangements and for liquidation purposes in case of Deposits and savings arrangements.
Pay Processing
Enhancement 56324 Build 201010 The settlement pay processing covers the option to specify accounts for liquidation of Principal, interest and charge. Settlement property has the facility where the user can mention an internal account for settling the dues in case of lending arrangements and for liquidation purposes in case of Deposits and savings arrangements.
Page 30 of 61
Page 31 of 61
Retail Accounts
Accounts Product Line
Enhancement 63652 Build 201009 This enhancement provides the functionality to create savings and current accounts using AA framework under the ACCOUNTS Product Line and do some basic activities on it. Some of the key points of this enhancement are: Creation of new accounts arrangement Credit activity for the account Debit activity for the account Credit / Debit Interest accruals Capitalisation of accrued interest to account balance
NB This enhancement provides part of the functionality from the strategic enhancement 10299 Savings and Current Accounts in AA
Overdraft Limits
Enhancement 25817 Build 201012 The functionality introduced through this enhancement is to provide for the setting up and managing a default system generated limit for the ACCOUNTS product line.
NB This enhancement provides part of the functionality from the strategic enhancement 10299 Savings and Current Accounts in AA
NB This enhancement provides part of the functionality from the strategic enhancement 10299 Savings and Current Accounts in AA.
Page 32 of 61
As a part of ACCOUNT product line development, the calculation of the interest of an account / arrangement is based on the various balance types. To facilitate this, the functionality introduced in this enhancement will now support the additional calculations; AVERAGE and HIGHEST for Debit balance type AVERAGE and LOWEST for Credit balance type.
NB This enhancement provides part of the functionality from the strategic enhancement 10299 Savings and Current Accounts in AA.
Blocking of Funds
Enhancement 89385 Build 201013 The BALANCE.AVAILABILITY PROPERTY.CLASS has been introduced to hold settings for available balance updates and credit check functionality through fields AVAIL.BAL.UPD and CREDIT.CHECK. Also the NOTICE conditions can be set up through this property class. This PROPERTY.CLASS is available for the Accounts Product line.
NB This enhancement provides part of the functionality from the strategic enhancement 10299 Savings and Current Accounts in AA.
NB This enhancement provides part of the functionality from the strategic enhancement 10299 Savings and Current Accounts in AA.
Page 33 of 61
Changes to CHANGE.PRODUCT property - Add relative of customer birth to the CHANGE.DATE field
Enhancement 26166 Build 201015 Through the functionality delivered in this enhancement it is possible to calculate the change product date relative to the birth date of a customer. For example A customer who currently holds a minor account, would no longer be eligible to hold this type of account once he reaches the age where is considered to be a major. With the current change product property class attributes, one has to manually calculate the change date relative to the customers birth date and give that in CHANGE.DATE field of change product property class. To automate this process, the field CHANGE.PERIOD should be converted into a relative period field such that user can indicate that the change date could be calculated relative to the customers birth date.
NB This enhancement provides part of the functionality from the strategic enhancement 10299 Savings and Current Accounts in AA.
New Activity and associated actions to evaluate and change product based on eligibility
Enhancement 26139 Build 201015 Through this enhancement the AA.ACTIVITY.CLASS EVALUATE.ELIGIBILITY has been released. This will enable the system to evaluate a customers eligibility to a product. Start of day and End of day processes; have been created to re-review the eligibility of the customer.
NB This enhancement provides part of the functionality from the strategic enhancement 10299 Savings and Current Accounts in AA
Arrangement Closure
Enhancement 11410 Build 201015 Through this enhancement the functionality to close an arrangement is introduced into the Accounts product line. The following AA.ACTIVITY.CLASSES have been introduced to facilitate this functionality.
Page 34 of 61
NB This enhancement provides part of the functionality from the strategic enhancement 10299 Savings and Current Accounts in AA.
Transaction Rules
Rule Evaluation Enhancement 72965 Build 201013 With the functionality released in this enhancement it will be possible to define the Periodic rule to find the Minimum or maximum balance amount in account, Minimum, Maximum balance Increase in a Account and Minimum Initial credit to the Account. The following additional Periodic Attribute classes have been released for the Property Class ACTIVITY.RESTRICTION Minimum Balance Maximum Balance Maximum Balance Increase Minimum Balance Increase Minimum Initial Deposit
NB This enhancement provides part of the functionality from the strategic enhancement 10299 Savings and Current Accounts in AA.
Page 35 of 61
Arrangement Bundle
Product Bundle Enhancement 56310 Build 201014 The AB module Arrangement Bundle will provide the product bundling functionality for T24. The module will allow retail products to be bundled together. A new Product Line "BUNDLE" is introduced, along with the PRODUCT.BUNDLE and INTEREST.COMPENSATION property classes. The PRODUCT.BUNDLE property class is used to store the arrangements that form part of a Bundle. The INTEREST.COMPENSATION property class is used to store the source and target interest properties. The following AA.ACTIVITY.CLASS'S have been released BUNDLE-NEW-ARRANGEMENT BUNDLE-UPDATE-PRODUCT.BUNDLE BUNDLE-UPDATE-INTEREST.COMPENSATION LENDING-MANAGE-INTEREST DEPOSITS-MANAGE-INTEREST SAVINGS-MANAGE-INTEREST ACCOUNTS-MANAGE-INTEREST
NB This enhancement provides part of the functionality from the strategic enhancement 10299 Savings and Current Accounts in AA
NB This enhancement provides part of the functionality from the strategic enhancement 10299 Savings and Current Accounts in AA
Page 36 of 61
An arrangement which is of bundle can be either DONOR or RECIPIENT. The arrangement that is the DONOR will be run first and then RECIPIENT arrangements will run.
Page 37 of 61
Teller
Support Teller Limit
Enhancement 24015 Build 201010 Through the functionality released by this enhancement T24 will support teller limits. It is possible to set upper limits on tills by currency. When a limit is exceeded the system will generate an override for the user.
Teller Charges
Enhancement 24022 Build 201012 T24 provides flexibility to collect charges from any desired account for customer account to account transfer transactions. To allow this, a field CHG.TYPE is introduced in TELLER.TRANSACTION and TELLER applications. CHARGE.ACCOUNT field at TELLER level is enabled that allows the user to specify the charge account .The charge account can be in any currency.
Loan Origination
Scoring
Enhancement 95279 Build 201015 SA.SCORE.LIMIT table defines the following parameters in addition to the available functionality. 1. Interest Spread to allow preferential spread for customers based on score ratings 2. Pre-payment percentage 3. Scoring status
Page 38 of 61
4. Risk rating Moreover, Currently if a field blank in SA.SCORE.TXN then system gives the user the option to consider it as default 0 or to include Null fields as elements for calculation of scoring.
SLA Framework
Enhancement 84264 Build 201014 Two new T24 tables have been added, SG.SLA and SG.SLA.COMMITMENT. SG.SLA is a designtime (i.e. configuration) table to define the SLA metrics. The SLA represents the turnaround time for a PW Process Definition or a PW Activity. It can be defined as time or days and calendar days or working days. SLAs can apply to one or across all companies. SG.SLA.COMMITMENT is the runtime (i.e. transaction) table whose records represent the deadline for the particular process or activity transaction, which will be a date and possible a time as well. If and when the deadline is missed the status is updated as breached in the SLA commitment, and also an alert may be sent to the subscriber if Send Delivery is marked as Yes. From a business perspective, the subscriber would be the Account Officer.
SLA Interface to PW
Enhancement 84276 Build 201015 Fields to link SLA with PW Process Definition and PW Activity have been added. If monitoring by SG product is required, then when the process or activity starts and ends, PW will update the SLA module.
Option to restrict the input into a field with the drop-down enquiry in ARC-IB
Enhancement 39268 Build 201014 When Enquiry dropdown appears against a field, if the bank wants the user to select values only from the dropdown rather than typing a value into the field, the field DISPLAY.TYPE can be set as "DROPDOWN.NOINPUT" in the VERSION application against the field which has enquiry attached to
Page 39 of 61
it. The field will appear as no-input but with the drop down. An example usage is on a debit account field, the user can only select from the Enquiry rather than typing in an account number.
This structure is essential for correct functioning. For internal application (i.e. application used by the client staff) typically only STOCK16 is utilized for displaying screen icons. Once the set of localised icon files has been created, it should be zipped up as a single file stockicons.zip and will be used when the installer is executed. In the stockicons.zip file contains the core banking logo has to be update accordingly. The company logo has to be updated in the following location ../stockicons/stock/mobile_splash_vast.png, which would be displayed in the Mobile Handset.
Page 40 of 61
RX-TCQ Notification
Enhancement 56657 Build 201011 An additional even type RX-TCQ in ARC Mobile which helps any banking system (including T24) that detects event of a cheque being deposited by a customer can trigger such an event and ARC Mobile will process the notification. The information containing the cheque details is given in a flat file and his pasted in a notifications file with the file name .not extension for the Arc mobile to process.
Page 41 of 61
Jca Connector
Enhancement 60747 Build R11 Client upgrades the version to R11 where TC-Server Connectivity is deprecated, then JCA connector can be used. ARC Mobile has a standard set of OFS messages cached and the OFS messages are suitable but the communication mechanism (TC-Server) is not suitable. Hence there is a need to separate the OFS commands from the connection mechanism and be able alter the connection mechanism in the future
Securities
The following Strategic Initiatives have been delivered in R11 GA from Securities.
Page 42 of 61
In case of external custody, from an investment managers perspective, there should be an operational framework that will enable him to provide consolidated reporting and monitor the performance of the portfolios taking into account the externally held positions as well. This development aims to fully integrate the positions held externally with a custodian into T24 to offer a consolidated view to the portfolio managers for portfolio analysis (performance, valuation, constraint checks, etc.) and offer a client reporting that encloses external assets not held within the banks custodian network. In order to facilitate accurate performance reporting, all transactions will be captured with all settlement details like commissions, fees, forex rate and other charges.
Page 43 of 61
Internal and external holdings can exist for the same client. Hence, hybrid forms of internal and external custody will be supported. Even though the concept of external custody exists for the security positions, this needs to be now extended to the cash side as well. Besides, there should also be a mechanism to segregate internal and external positions so that there is no risk of selling the external positions. In order to cater to this requirement, these will be the enhancements to the system at a broader level: A. Separate identifier for external positions these can be either 1. Designated portfolios or 2. Designated sub accounts within the same portfolio; B. Separate identifier for external transactions; C. Handle orders for external custody positions both direct and those through in-house dealing desk; Example Let us consider a following example: Customer buys 1000 IBM @ USD 105, Commission USD 1000 and other charges USD 500 Customer Net - 106500 Brokerage - 900 Broker Net - 105900 Unlike direct orders, the settlement is more complex as there should be an additional outside trade to settle with the custodian. In the first step, the transaction is settled with the broker. Since this position has to be cleared, there will be a second (outside trade) to clear the position by settlement with the custodian. The first trade is for settlement of this transaction with the broker (in this case, ML). The existing functionality can cater to this requirement. The second trade is for clearing out the position from the banks books by settlement with the custodian. In this, the transaction codes from the original trade will be reversed. The price will be recomputed to take into account the commissions and other charges in order to square-off the accounting of the original trade, while leaving the originally generated PL entries in place. Continuing with the above example: Sell 1000 IBM @ 106.5 (net amount (106500)/nominal) Customer net amount will be 106500. The broker net amount will be the same as the customer net amount (USD 106500 in this example). The following entries will be raised for this trade: The third trade will be the shadow trade to capture the external position in banks books. From here on, the flow for in-house dealing orders will be the same as direct orders. D. Amend trade accounting to cater to external positions trade will be amended to raise contingent (off balance sheet accounting); Example For direct orders from the portfolio manager The transactions are captured in banks system (shadow trades) once the final settlement details are known For trades through in house dealing desk, settlement is more complex
Page 44 of 61
There will be no commissions/charges on the broker side and the broker side amount will be the same as customer side amount in all external custody transactions. Shadow accounting
It must be noted that both the client account and suspense account are contingent accounts and will not affect the banks books. E. Combined valuation for both internal and external custody positions SC POS ASSET to be enhanced to have valuations at sub account level; F. Handle corporate actions in respect of external positions; G. Possibility to exclude external positions from fee calculations;
Order Routing The Securities orders result either from a modelling session (bulk orders) or specific client requests that are captured via the front office. These orders, either individually or as a group, will be transmitted to an executing broker. Once executed in the market, the execution details are captured in the system and processed culminating in settlement of the transaction. The system also allows capturing of previously traded orders. There are instances where the orders will not be transmitted directly to the executing broker from the front offices (branches). Instead, the orders will be transmitted to the execution hub(s) or internal broker from the locations. The execution hubs will manage all the orders received from various locations. In such cases, once authorized, orders will be automatically routed from the location to the trading desk in the execution hubs. There can be more than one execution hubs in which case the orders will be routed to the correct hub based on pre-defined rules. Once executed, the hubs will transmit the execution details to the location where the orders originated. The orders may be cancelled at any point of time before the execution in which case the status has to be mirrored in the hub. Throughout the life cycle of the order, the order status will be available to both the location and the hub. As part of the enhancement, the orders originating from a location (company or book) will be routed to an execution hub (another company or book) based on pre-defined conditions. The execution hub will then handle the street side executions and pass back the order/execution status to the originating location. Both internal and external custody orders can be routed. An order will automatically be created in the routed company on authorization of the order in the originating company. Once this order is executed, trades will be created both in the routed company (for street side settlement) and the originating company for updating the actual customer positions. In the execution hub (routed company), there will be two trades: 1. The street side trade routed through the cross trading or wash portfolio. The broker will be the executing broker from the original order and the settlement will be to the Depository specified in the original order. 2. The second trade will be to deliver the stock to the beneficiary. As far as the execution hub is concerned, the beneficiary is the originating company from where the order was routed. The originating company will be identified by means of a portfolio defined for it in the executing (routed) company. The second (reverse) trade will be between the cross trading portfolio and the portfolio of the originating company held in the executing company. On completion of all the trades, cross trading portfolio will be squared off and the executing company will report holdings of the originating company. A diagrammatic representation of the proposed order routing system is given below:
Page 45 of 61
Page 46 of 61
For portfolios requiring real time valuation, valuation will be automatically performed (through service) whenever there are triggers. The triggers can be portfolio specific (new buy/sell transaction, funds transfer, etc.) or global (price change) that impacts multiple portfolios. The valuation will be automatically performed for the component that has undergone a change to ensure that the valuation is real time or close to real time at any point of time.
Repos
Repos/Non-Linear Accrual Method
Enhancement 34398 Build 201009 Through the functionality provided in this enhancement Repo contracts may be accrued based on the Effective Rate. The new field EFFECTIVE.RATE in the REPO.TYPE application indicates that this applies to this type of Repo. If this field is set, and if the notional rate is provided the system will calculate the maturity value and the effective rate, and pass this information to the underlying Money Market contract. Similarly, if the effective rate is provided then the system will calculate a notional rate and Maturity value, and pass this information to the underlying Money Market contract. The new fields EFF.INT.BASIS and EFFECTIVE.RATE exist in the REPO application to facilitate this process.
Corporate Actions
Securities - Swift MT564
Enhancement 27424 Build 201009 MT564 for Corporate Action notification when Issuers give incentives to holders for voting well before the final deadline has an EARLY.DEADLINE date via the SC.PRE.DIARY and DIARY applications to hold the effective date. The date will appear in the ETPD qualifier of the MT564.
Page 47 of 61
Securities Trading
Sub-account - to Sub-account Position Transfer
Enhancement 49733 Build 201009 It is possible to use the POSITION.TRANSFER application to transfer a position to a Sub Account of the users choice. POSITION.TRANSFER will accept entry in the SUB.ACCT.TO field for the Sub Account to which the position is to be transferred.
Page 48 of 61
and the effects on buying power are calculated. The order is only accepted and routed if the buying power is greater than the order amount. The calculation is made in Reference currency or Valuation currency if it is different. An override is produced if the calculation indicates a risk.
Order Routing
Enhancement 19098 Build 201015 The Securities orders result either from a modelling session (bulk orders) or specific client requests that are captured via the front office. These orders, either individually or as a group, will be transmitted to an executing broker. Once executed in the market, the execution details are captured in the system and processed culminating in settlement of the transaction. The system also allows capturing of previously traded orders. In such cases, there will be no execution but only the trade processing and settlement. There are instances where the orders will not be transmitted directly to the executing broker from the front offices (branches). Instead, the orders will be transmitted to the execution hub(s) from the locations. There can be more than one execution hub in which case the orders will be routed to the correct hub based on pre-defined rules. Once executed, the hubs will transmit the execution details to the location where the orders originated. The enhancement is for addressing the above requirement of routing orders to the execution hub. In T24 parlance, the execution hub can be another company or book depending on multi-company and multi-book set-up. The enhancement is to cater to the following related requirements: a. Implementing the execution hub concept; and b. Routing orders to in-house broker/dealer.
Page 49 of 61
Security
The following Strategic Initiatives have been delivered in R11 GA from the Security stream.
Page 50 of 61
Security Processes
Secure development is the term largely associated with the process of producing reliable, stable, bug and vulnerability free software. To address this, the security technology team has come out with secure software Development Policy. The Objective of this document is to guide the organization, the developers and the other stake holders to follow a secured software development lifecycle. This document also gives guidelines on how to include security issues and requirements/mandatory compliance requirements right from the beginning of the software life cycle. This document also covers about the various controls to ensure that security is applied throughout the SDLC Phase. The purpose of this guideline is also to assist the organization in building security into the Existing IT development processes. This must result in more cost-effective, risk-appropriate security control identification, development, and testing. This Document focuses on the information security components of the SDLC. This document lays down the guidelines to be followed during each phase of software development and software maintenance at Temenos. It provides an overview of the procedures to be followed and also lists the documents to be prepared and the templates to be used for preparing these documents.
Page 51 of 61
This creates complications in terms of encrypting and storing these credentials in the Authentication Server as well as additional costs to clients, as the most secure solution to perform such encryption is to use numerous, expensive Hardware Security Module (HSM) to perform the encryption. The decoupling of Authentication Server and T24 credentials reduces the number of credentials required to, a credential for 4TRESS and one for a failover 4TRESS server; this represents a significant saving in terms of complexity and cost to our clients.
In T24 for the ARC-IB product Transaction Signing offers secure authentication using 4TRESS (a 3rd party Authentication Server) to verify a Users Identity prior to committing a transaction, Versions and Users that utilize Transaction Signing can be easily customized.
SOA Framework
The following Strategic Initiatives have been delivered in R11 GA from SOA Framework
Page 52 of 61
The end result will be to use Systar as a Business Activity Monitoring (BAM) solution specifically designed to streamline the close-of-business (COB) process within the Temenos T24 Model Bank environment. The Systar BAM for T24 COB solution constantly monitors all jobs and channels to proactively alert the right people if there is the potential for a COB issue.
Customer adapter: The customer adapter is an example of an adapter that requires read only nontransactional data access. The adapter framework will provide a database connection for the context; this connection will be reused in subsequent calls. A client buying T24 that wants to keep an existing Customer system will implement a "Customer Adapter" according to our T24 customer API and the implementation will mostly contain SQL statements.
Page 53 of 61
TWS Composer
Enhancement 56814 Build 201010 From R11, TAG has been replaced by Temenos Web Service Composer (TWS Composer). TWS Composer is available in two versions, TWS Composer (EE) and TWS Composer (.NET). Tws Composer is designed to provide robust SOA web services of T24, and exposes Business Services and Business Operations as WS-I compliant Web APIs via JEE (plug-in to Eclipse IDE and war file) or .NET (plug-in to MS Visual Studio and WCF Web Service packages).
NB This enhancement provides part of the functionality from the strategic enhancement 22706 TAG replacement and .NET connectivity.
Component Updates
From R09, a new update process was introduced that gave a client the ability to find and apply upgrades on a component basis. This means it is now possible for changes to be isolated and delivered with fewer fixes and for specific components. The TWS Java (EE) Eclipse plug-in component is not currently available as a T24 Update. Updates are available for the dependent components within T24. See the section of this document entitled System Component Requirements.
TWS Overview
The TWS Java (EE) product facilitates the exposure of existing T24 functionality via SOAP web services.
TWS Artifacts
TWS-PLUGIN
TWS (EE) provides an Eclipse plug-in environment for selecting T24 business operations to expose as web services and for constructing the run-time TWS-WAR artifact. Artifact: com.temenos.tws.plugin_<plugin-version>-<t24-version>.jar
Page 54 of 61
TWS-WAR
The Web Application Archive (WAR) file provides a web service interface to T24 when deployed in an application server. It is constructed by the user with the TWS-PLUGIN. Artifact: <user-provided-name>.war For further information on the use and installation click the following link TWS Composer
Arrangement Architecture
Enhancement 73121 Build 201011 TWS Java(EE) R11 supports transaction input via AA Versions. When defining Business Operations in the PW.ACTIVITY table for AA transactions, the PRODUCT and ACTIVITY to be used must be specified in the AUTOM.FIELD and AUT.NEW.CONTENT fields of the specified VERSION record. The screen shot below shows the PRODUCT PERSONAL and ACTIVITY INTERNET.SERVICESNEW-ARRANGEMENT specified in the VERSION record AA.ARRANGEMENT.ACTIVITY, AA.NEW.NOCCY.PW.
Internationalisation support
TWS Java(EE) R11 supports Internationalisation. This requires configuration of the relevant OFS.SOURCE record in T24 and, in TOCF(EE), configuration changes to both browserParameters.xml and t24-ds.xml. Please refer to the TWS Java(EE) Internationalisation Guide for full configuration instructions.
Miscellaneous Changes
Direct connection pooling (Tomcat) Progress bar for TWS project creation wizard Eclipse Plug-in Landscape" references replaced with T24Services JBoss JMS ConnectionFactory JNDI name reset to default.
Caveats
Linked applications: FOREX with SWAP and LD.LOANS.AND.DEPOSITS with Schedules are only supported via the callOFS web method.
Treasury
The following Strategic Initiatives have been delivered in R11 GA from Treasury.
Page 55 of 61
Where: N= CF= Number of interest payments between the revaluation date and the maturity date Cash Flow considered for each period
R= Zero Coupon Rate for the corresponding interest period / Rate derived from PI Table for the corresponding period depending upon the Zero Coupon Rate field in SWAP REVAL PARAMETER D= B= Number of days between the revaluation date and the corresponding cash flow date Interest Day Basis
A new table SWAP.REVAL.PARAMETER has been introduced to take care of all the revaluation related parameterisation.
Money Market
Money Market support of Interest Basis E1 365/365
Enhancement 24746 Build 201010 The INTEREST.BASIS E1 365/365 is now supported in the Money Market module.
Page 56 of 61
Swaps
Swaps support of Interest Basis E1 365/365
Enhancement 24747 Build 201010 The INTEREST.BASIS E1 365/365 is now supported in the Swaps module.
Where: N= CF= Number of interest payments between the revaluation date and the maturity date Cash Flow considered for each period
R= Zero Coupon Rate for the corresponding interest period / Rate derived from PI Table for the corresponding period depending upon the Zero Coupon Rate field in SWAP REVAL PARAMETER D= B= Number of days between the revaluation date and the corresponding cash flow date Interest Day Basis
A new table SWAP.REVAL.PARAMETER has been introduced to take care of all the revaluation related parameterisation.
Page 57 of 61
Wealth Management
The following Strategic Initiatives have been delivered in R11 GA from Wealth Management.
ARC IB
ARC IB Improvements (SI - 9850) ARC IB Improvements focus on Brand Distinction within the Temenos Model Bank brand, Real World homespaces and examples and clean simple usable pages.
Client Reporting
Client Reporting - Ad-hoc Client Statements
Enhancement 25097 Build 201015 Client Reporting - ad hoc Reports extends existing T24 Client reporting solution for R10 (COB batch Standard Client Statement reporting on monthly portfolio based data) with on demand reporting for portfolio on any required period.
Page 58 of 61
T24 Client reporting engine (Orchestrate v2.0) - focused on increasing the processing volumes by upgrading the technology and improving scalability.
Model Bank
Model Bank Improvements (SI - 20835)
Model Bank Improvements considers the following enhancements to Model Bank. 1. Enriched Customer On-boarding: - A customer on-boarding and investment proposal process including high quality orchestrate output. 2. Data Enrichment: - Additional portfolios with realistic data, including positions, prices, historical valuations and performance. 3. Compliance Homepage: - A new compliance homepage targeted at a back office compliance officer in a Wealth Management style institution. 4. FX Dealer TAB: - A Wealth focused Treasury homepage for the completion of FX orders raised by Wealth Management processes. Increased functional coverage, focused role based homepages. "What you want, when you need it". Coverage includes: Front Office Operations, Relationship Manager, Dealer, Compliance Officer, Settlement Analyst, Corporation Actions, Portfolio Admin, and Credit Officer.
MiFID
Wealth Management - R11+ (SI-107636)
This will include MiFID Securities Compliance & changes to the Front Office Home screen. A new homepage has been introduced based on external recommendations and client implementation experience which includes all Private Banking compliance checks in one homepage. MiFID compliance checks are included; Instrument Knowledge, Trade Time & Post Trade checks. For further details see the MiFID documentation on the European Commission website
Investment Profiling
Wealth Management - Investment Profiling (SI-126343) Investment Profiling re-uses existing T24 functionality to provide a full investment profiling suite, including MiFID questionnaires to capture the clients appetite for risk as well as investment strategy recommendation resulting in a client receiving a dynamically created customised investment profile report. This includes workflows to accept/reject the report and to trigger full customer on boarding.
Page 59 of 61
Allows specification of rounding method and units for proposed nominal for cash investments and proposed FX spot amount for cash sweeping and hedging. See Request Parameters for further details.
ARC-IB Improvements
ARC IB Phase 1 Improvements
Enhancement 21534 Build 201014 ARC-IB access for Private Clients, ability to view portfolios and valuations online, ability to enter orders online, access to retail ARC-IB features and graphical portfolio views.
Page 60 of 61
Private Wealth Management Alerts can be subscribed to, either at Portfolio level or Relationship Manager level and used to alert the customer or Relationship Manager via a preferred channel e.g. SMS, email or secure message upon occurrence of predefined events. See Alerts for further details.
Client Reporting
Ad-hoc Client Statements
Enhancement 25097 Build 201015 Private Wealth Management Customer Reporting can produce ad-hoc Client Statements by running a pre-specified set of T24 enquiries online for a specific portfolio, for a particular date range. This functionality can be used to rerun the monthly reports after data corrections or back-valuations, run reports to give the latest data, or for creation of custom reports to be run online. See Adhoc Reporting for further details.
MiFID
MiFID Compliance
Enhancement 107637 Build 201015 MiFID Compliance for T24 comprises the ability to determine suitability of a securities instrument for trade by a particular customer, dependent on risk profile of the instrument and the customer's attitude to risk, as well as providing the tools to ensure Best Execution of the securities deal. Pre and Post Trade checks are also covered by this enhancement. See Compliance for further details.
Model Bank
Model Bank Phase 1
Enhancement 30688 Build 201009 Wealth Management Administration Home Page
Page 61 of 61