R11 Release Highlights PDF

T24
R11 Release Highlights
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
TEMENOS T24 User Guide 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

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

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 Java Deployment

This SI covers the provision of a Java solution for T24.
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.
Application Framework released enhancements

Public API for adding OFS Bulk request
Enhancement 77846 Build 201010
A public API has been made available for adding OFS Bulk requests. It is now possible to use API to
enable Local Developments to add additional T24 vanilla requests to the OFS bulk transaction queue.
These local OFS requests are processed as part of the master (parent) database transaction.

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

 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
Enterprise Customer - Publishing

360 degree view of customer
When banks use different systems for different products but maintain the customer information in
Enterprise Customer, a complete 360 degree view for a customer will be provided. The 360 degree
view enquiry will collect information from non-T24 systems and display the arrangement details of the
customer, apart from non-financial information such as related parties, last contact made with
customer, potential products to sell to customer, etc.
New Service operations for Customer:
The following are the new service operations being introduced

 Activate Customer
 Update Physical Address
 get Physical Address
 getAddress
 Update Contact Preferences
 get Preferred Contact Point
 get Relationship Between Parties
 Update Related Party When Merged
 Merge Customer
 get Related Party Content
 get Customer With Legal ID
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.
AA performance and Infrastructure

This development is to supply values in Properties using AA.ARRANGEMENT.ACTIVITY as the front
end application to process activities with meaningful names for which values can be supplied. The
associated fields PROPERTY, FIELD.NAME, and FIELD.VALUE in AA.ARRANGEMENT.ACTIVITY
are used to load AA transactions from external systems into T24, and can be used to send AA service
requests to T24.
This makes it an easier task to load values into property fields. The fields that can be passed through
a service request can be obtained from the ACTIVITY.PRESENTATION property.

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
Banking Framework released enhancements

This section contains a high level overview of each enhancement that has been delivered by Banking
Framework.
Interest and Charges
Interest Basis E1 365/365

The INTEREST.BASIS E1 365/365 has been introduced from this build.
Interest Basis W (252/252) & W1 (21/252)

The INTEREST.BASIS W and W1 have been introduced to support the Brazilian method of interest
calculation.
Account Related Fees-Waiver by Fee Type

The application IC.CHARGE has been enhanced to include the field WAIVE.CHARGE in the multi
value set that is applicable for each charge or fee, so that specific charges or fee's can be waived
instead of waiving them all.
Update of Turnover figures in ACCT.ACTIVITY by reversals - Red Storno

The field REVERSE.TURNOVER has been added to ACCOUNT.PARAMETER, this will be used to
parameterize the effect of reversal transactions on turnover fields in the ACCT.ACTIVITY records.
IFRS
Impairment
Impairment Assessment & Capture - IFRS.DATA.CAPTURE (Validation)

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 Assessment & Capture -Individual (Update of EB.CASHFLOW)

The EB.CASHFLOW application has been enhanced to hold the expected cash flows and the details
required for carrying out the impairment accounting.
reclassification
Fair value to use rates for each cash flow date

IFRS Fair value rates are to be calculated based on PERIODIC.INTEREST table with multiple rates
for periods which include period rests. For each cash flow of the underlying contract the rates should
be retrieved from TERMRATE (using Interpolation logic used by the system if an exact match is not
found)
reclassification
Individual loss impairment calculation & Accounting

This enhancement provides the functionality for the calculation and accounting of the recoverable
value based on the expected cash flows and the subsequent impairment loss for individual contracts
valued at Amortised cost only.
reclassification
Impairment loss Calculation & accounting - individual assessment (Fair Value &
Schedule Provisioning)

This enhancement has introduced functionality to support the impairment loss calculation for contracts
valued at FAIRVALUE and FAIRVALUE through EQUITY. The following ACCOUNTING.HEAD‟s 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
reclassification.
Impairment of AFS Securities

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.
reclassification.
Impairment Loss Calculation & Accounting - Individual Assessment (Fair value &
schedule provisioning)

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.
reclassification.
Reversal of impair or unimpair operations

IFRS.DATA.CAPTURE has been enhanced to allow the reversal of records depending on their status.
If the IMPAIRMENT.STATUS field is set to one of the following
 IMPAIR
 IMPAR.AMENDMENT
 UNIMPAIR
The system will reverse the accounting entries and update the relevant EB.CASHFLOW and
IFRS.ACCT.BALANCES as relevant.
reclassification
Ability to correct an incorrect Sub Type

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.
reclassification.
Merge PD in order to calculate T24 balance

When a contract has an overdue balance a PD contract is created and the overdue balances are
moved to the PD contract. The field CONTRACT.BALANCE in IFRS.ACCT.BALANCE is now updated
with the combined balances from the both the original contract and the PD contract.
Repayment and write off assessment accounting

With this enhancement, accounting for an impaired contract will be raised in case of the following
events:
 Write-off
 Partial Payment and partial write-off
 Full Payment
reclassification.
Impairment Assessment and Capture - IFRS.IMPAIRMENT.CODE
Enhancement 28060 Build

IFRS suggests a list of acceptable impairment evidence, the application IFRS.IMPAIRMENT.CODE
has been introduced to contain the list of acceptable impairment evidence. There will be some
released common records into this application, but banks can input new records as required.
The application EB.CASHFLOW has been enhanced with the following fields
 DATE.IMP.EVIDENCE
 DATE.IMPAIRED
 DATE.UNIMPAIRED
Reversal of impairment accounting

This enhancement will introduce the accounting entries when an UNIMPAIR operation is performed.
Automatic link of collateral to Expected Cashflow

Through this enhancement the functionality has been introduced to calculate collateral so the IFRS
can use it for impairment calculations. The following addition fields have been introduced in
EB.CONTRACT.BALANCES to store this information.
 RISK.COLL.RGD.ID

 RISK.COLL.ID
 COLL.CCY
 ALLOC.AMT
Check that the impaired balance does not exceed the T24 balance

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) doesn‟t exceed the T24 book value in case of an impaired contract. If it exceeds an
exception is logged in EXCEPTION.LOG.FILE.
Maturity of an impaired Loan

Through the functionality in this enhancement the system will support the following maturity scenarios
for an impaired contract
 On Maturity, T24 Balance will be equal to all 'IF' Balances
 Expected cash flows beyond the Maturity Date
 On Maturity T24 Balances becomes '0'.
 Principle Decrease
HTM bonds to update EB.CASHFLOW

The Effective Interest Rate (EIR) method is a method of calculating the amortised cost of a financial
asset or a financial liability and of allocating the interest income or interest expense over the relevant
period.
The Effective Interest Rate of a bond is described as the rate that will discount the bond's future
interest payments and its maturity value to the bond's current selling price, that is current market price
or present value.
The effective interest rate is a bond investor's yield-to-maturity. The effective interest rate will likely be
different from the stated or contractual rate that appears on the face of the bond.
The SEC.ACC.MASTER application has an option to select "EIR" in the LINEAR.COMP.ACCR field as
a method to compute the daily amortisation cost of a bond. The other options available are "LINEAR"
and "COMPOUND".
SC Reval to identify local CCY gain or loss

The revaluation of Securities based on exchange rate movements that is the posting of revaluation
gains/losses should be posted to Equity (internal accounts).
Revaluation of currency profits/losses arising out of Positions held in foreign currency Securities in an
available for sale (AFS) Portfolio can be posted to internal suspense account categories.

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".
Reclassification
Reclassification of Assets (Capture)

Contracts for the applications LD, MM, AZ, SL and AA which were previously classified as HTF or AFS
may now be reclassified to LAR. The reclassification process is achieved through the application
IFRS.DATA.CAPTURE.
reclassification
Reclassification of Assets Process

Through the functionality added in this enhancement the ACCOUNTING.HEAD balance for
FAIRVALUE will be reduced if a contract is reclassified from AFS to LAR.
reclassification
Provisioning
PV Template layouts

The applications PV.MANAGEMENT, PV.PROFILE, PV.LOAN.CLASSIFICATION,
PV.ASSET.DETAIL and PV.CUSTOMER.DETAIL have been introduced for the new Provisioning
Module.
reclassification
PV Classification Processor - Contract Selection

The live file PM.MANAGEMENT.CTRL is introduced to hold the classification, calculation and posting
dates for the classification and provisioning process, ensuring that the correct contracts are selected.
reclassification,
PV Classification Processor - Manage PV Asset Detail

The application PV.ASSET.DETAIL is used to hold both classification and provisioning details.
Through this enhancement the following will update this file.

 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
reclassification
PV Classification Processor - Customer Classification

Through this enhancement the PV.CUSTOMER.DETAIL file can be updated by the following:
 The Classification process with the worst Classification for the selected contracts ( defined in
the PV.MANAGEMENT record) for the customer
 The Manual correction of the Classification for customer
reclassification.
PV Classification Processor - Classify

Additional validation has been added to the fields CLASS.RULE & API.RULE in the application
PV.MANAGEMENT.
reclassification.
PV Calculation Processor - Contract selection

Through the functionality introduced in this enhancement will ensure:
 The calculation process is triggered by the PV.MANAGEMENT.CTRL record for the company,
 The PV.ASSET.DETAIL records are correctly selected
 The PV.ASSET.DETAIL record is updated with the Calculation details
 The NEXT.CALC.DATE in the application PV.MANAGEMENT.CTRL is correctly cleared after
the calculation process.
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
reclassification.
PV Calculation Processor - (Do calculation)

Functionality has been introduced to enable the system to perform the calculations required for
provisioning. This enhancement is a continuation of the functionality delivered in enhancement 81149.
reclassification.

PV Calculation Processor - Manage PV Asset Detail

The functionality delivered in this enhancement is a continuation of that delivered by enhancement
81149.
The system will be able to get the classification applicable to a contract and to update the
PV.ASSET.DETAIL with the Calculation details.
reclassification.
PV Calculation Processor - IFRS manual Impairment

This enhancement will enable IFRS.DATA.CAPTURE records to be created in IHLD when the field
DEAL.IMPAIR is set to „MANUAL‟ in PV.PROFILE.
reclassification.
PV Calculation Processor - Collateral Mitigation

Under Standard Provisioning a Percentage calculation method is used for the provision calculation.
This calculation process takes into account any Collateral in order to mitigate the provision calculation.
The collateral allocations are derived from the EB.CONTRACT.BALANCES application and applied to
the provision types before calculating the provision. If the collateral amount is not exhausted by one
provision type it is applied to the next.
PV Customer and Asset Classification - Change and Amount Change

The PV.ASSET.DETAIL and PV.CUSTOMER.DETAIL applications maintain classification history in
previous fields. The latest classifications are stored in the LAST.CLASS.DATE and AUTO.CLASS
fields. When the number of previous fields becomes too great then a number of the previous multi-
value sets are moved to history files, PV.ASSET.DETAIL.HIST and PV.CUSTOMER.DETAIL.HIST, so
that any further changes can be maintained in the current file.
PV Posting Processor - Accounting Movements

Through this enhancement the system will raise accounting entries for provisioning. A new
ACCT.HEAD.TYPE PROVISION is also introduced.
reclassification.
PV Posting Processor - Posting Amounts

The functionality introduced will ensure that the PV.ASSET.DETAIL records are correctly selected for
the Posting process. It will also get the Posting Amount for the contracts included in the Group
impairment.

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.
reclassification.
Enterprise Customer - Publishing
360 degree customer view

The purpose of this enhancement is to show 360 degree view of customer positions comprising of
balances in arrangements, limits, portfolios, etc, held not only in T24 but also in external systems. This
has been developed as part of ECM phase 1 to make Customer a stand-alone module in T24.
NB This enhancement provides part of the functionality from the strategic enhancement 9281 Enterprise Customer Publishing.
Customer Services

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
Duplicate check and merge

This enhancement provides the ability to do a duplicate check to the customer records via the field
values provided for comparison in EB.DUPILICATE.TYPE and the ability to merge or unmerge two
customer records which are of a duplicate nature.
Business Intelligence
The following Strategic Initiatives have been delivered in R11 GA from Business Intelligence.
Insight wealth Management

The purpose of this enhancement is to provide “Assets under Management Dashboard and metrics”.
This will be extending to provide a broader Private and Wealth management set of BI metrics.
The key features of this SI are:
 Create new metrics for Wealth Management in Insight
 Build new dashboards using Wealth Management metrics

 Sell this as an added module to Insight for Wealth Management banks

 Include a Data Event module within Insight to send email alerts
Insight Web Services

New Insight Web Services are being built so that we can expose Insight dashboards in another
browser. This will return the dashboard based upon the user running the report and so will return only
the data the user is authorised to see.
Key benefits of this are:
 Insight Web Services allows the integration of Insight reports and dashboards with T24
 Improves demonstration facilities
 Allows Insight Dashboards and reports to be exposed via Web Services
 Facilitates the integration of BI with NEO
 Improves role-based user experience
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 bank‟s
General Ledger. This provides a variety of balance sheet and Profit & Loss reports showing actual
versus budget reporting over the financial year.

This development will define multiple levels of dashboards according to an employee‟s 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)
Business Intelligence released enhancements

TRisk
TRisk - Claim on Regulatory Retail Portfolio

As per the Basel II standardized Approach, the claims on Regulatory Retail Portfolios have to be
validated for four criterions to qualify for RWA treatment specific to that claims. It is essential for the
user to identify and flag the Regulatory Retail portfolios, so that further validation can be run within
TRisk to validate the Orientation, Product, Granularity and Low value of Individual Exposures criterion
for RRP.
TRisk has been enhanced through this development to meet the Granularity rule criterion for RRP,
thus making it fully compliant under Basel II Standardised Approach.
TRisk - CCF on Undrawn Portion

As per the Basel II standardized Approach, Off-balance-sheet items under the standardized approach
will be converted into credit exposure equivalents through the use of credit conversion factors (CCF)
and where there is an undertaking to provide a commitment on an off-balance sheet item, banks are to
apply the lower of the two applicable CCFs viz. CCF for the commitment and CCF for the Product.
TRisk has been enhanced through this development to meet the CCF rule criterion, thus making it fully
compliant under Basel II Standardised Approach.
TRisk - Claims on Sovereign

As per the Basel II standardized Approach, the claims on Sovereigns and Central banks that are
denominated in their local currency should attract RWA as per the National discretion process of
supervisory review.
TRisk has been enhanced through this development to meet the sovereign rule criterion, thus making
it fully compliant under Basel II Standardised Approach.
TRisk - Capture data related to other assets for RWA calculation
TRisk has been enhanced to capture data related to other assets held on the banking book for RWA
calculation. This is used by the Capital Requirement Report in T-Risk.

DW.EXPORT

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.
Enhancements to Syndicated Loans

The following functionality has been added to the system though this SI
• Interest Basis Addition
• Multi Product Functionality
• Interest Rate type
• Mid Life Interest Changes
• Partial interest payment
• Repayment schedules for USA
Corporate released enhancements

This section contains a high level overview of each enhancement that has been delivered in R11.
Miscellaneous Deals
MD - Last day commission for CSN.TYPE “END”

T24 will now collect today‟s 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.

The MD.BALANCES record will be updated with the last day accrual amount with
PAST.SCHED.TYPE as “ADJ”.
Syndicated Loans
SL - Change of loan interest calculation days basis

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 - Change of Loan interest rate type

SL.LOANS has now been enhanced so that it is possible to amend the interest rate type during the life
of the Loan under a Syndication. This means that the interest rate type can be amended from Fixed to
Floating and vice versa. The system will calculate and record the interest individually and pass as one
entry at maturity.
SL - Partial payment of interest

During online repayment of an SL LOANS contract, T24 will also allow the repayment of the interest
amount that has accrued on the amount of the repayment, instead of being calculated on the
outstanding loan amount and taken only at the next schedule date
SL - Repayment schedules

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.
SL - Granting multiple products under the same facility

T24 will now allow multiple products, Loans, Guarantees and Standby Credit to be created under the
same Facility in the Syndicated Lending (SL) module
SL - Brazil Method of Interest Calculation BS/252

SL has now been enabled to use the interest basis 252/252 and 21/252 (Brazilian method of interest).
This means that only business/working days, as per local currency, are considered under these Day
Basis.

Letter Of Credit
LC - Import LC Issue via ARC IB

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 client‟s limits
are updated at the time of input via ARC IB or at the time of input at the T24 Bank.
LC - Brazil Method of Interest Calculation BS/252

LC has now been enabled to use the interest basis 252/252 and 21/252 (Brazilian method of interest).
This means that only business/working days, as per local currency, are considered under these Day
Basis.
Payments
The following Strategic Initiatives have been delivered in R11 GA from Payments.
Payments Released enhancements

This section contains the details of all the new enhancements released in R11.
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

Upload files without Header information

Default Header information via a Version.
Delivery
In and Out Message Console

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 plug-
in 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
Process Orchestration released enhancements


Process Workflow
Activity Reusability

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.
Activity Duration Analytics

Two new fields EXPIRATION.HOURS and EXPIRATION.MINS were introduced in PW.ACTIVITY
which is used for reporting purpose. These fields define the duration in hours as well as in minutes.
The impact of the above fields can be monitored using few enquiries. They are
• PROCESS.WORKLOAD.MONITOR
• PROCESS.STATUS.VIEW
• PROCESS.DURATION.ANALYTICS
• PROCES.TIME.ANALYSIS
Arbitrary Loop

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

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

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
Basic Workflow Patterns

In a given process definition it is now possible to execute multiple activities in parallel. It is also
possible to have an exclusive choice among the parallel activities. Three new fields FLOW.ACTIVITY,

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.
Arrangement Architecture
Cooling off period for Lending and Deposits:
A loan amount can be repaid at any point of time and similarly a deposited amount can be withdrawn
at any point of time during the life of the contract. It is quite common to charge the customers for early
withdrawals or early pre-closure.
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

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.

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.
Partial withdrawal supported.
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 customer‟s
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.
Current and Savings Accounts Phase 1

This SI is to complete the move of all retail products from the legacy T24 modules into AA.
Specifically this project will move the Current and Savings account processing from the existing AC
module to AA.
Automatic Overdrafts:

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 customer‟s 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 Selection Criteria
o Link to classification rule or API
o Link to provisioning profile
Provision Profile:
Calculation Type (Percentage, IFRS, API)
 Source Balance
 Percentages
 Collateral Usage

 Collateral Value
 Accounting Type
Model Bank Upgrade

This SI is for a refresh / overhaul of the existing Retail Model Bank.
Rework of all model bank UI components to work with NEO.
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.
Retail released enhancements

Cooling off Period for arrangements

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.
Deposits Processing for Cooling Off Period

As detailed in enhancement 19289 this enhancements handles the actual processing for cooling off for
deposits. By utilising the field COOLING.PERIOD the system can be configured (if required) to give
the customer an option to change their mind. In the case of a deposit if the redemption activity is
triggered wit in the cooling period then no interest will be paid to the customer and any accrued
calculated interest will be reversed. Any charges of fees levied will be reimbursed to the customer.

Overdue Statistics

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.
Make Term/Maturity Optional

The TERM.AMOUNT Property Class fields TERM and MATURITY.DATE have been made optional at
arrangement capture stage. As long as LINEAR or ANNUITY payment type are not being used in the
arrangement these fields can now be left blank if required.
Enhance updating of Maturity Date for CRF reporting and Overview Enquiry

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.
Additional Validation for optional maturity

For call contracts, IFRS is not applicable as the future cash flows cannot be predicted. Hence
validations are to be performed such that for Call contracts – IFRS support is not required.
Lending Processing for Cooling Off Period

As in deposits, banks can offer the facility cooling period for loan arrangements where the customer
can repay the loan within the cooling period and all interest amount accrued till the repayment date is
reversed.
During cooling period of a lending arrangement, on payment of the principal amount using LENDING-
SETTLE-PAYOFF activity, any interest amount accrued but not made due or capitalised will be
reversed out. The account can then be closed. Any interest or charge amount that has been made due
needs to be settled by the customer.
Example Charge API Routine for Early Redemption/Withdrawal Penalty

AA.LOCAL.CALC.CHARGE.AMOUNT routine is attached to the field CHARGE.ROUTINE 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.

Relative dates - Payment schedule

Payment schedule property class has been modified to support defining relative dates in payment
schedule.
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.
Settlement Property - Due Processing

This enhancement covers the SETTLEMENT DUE PROCESSING. This gives the option of specifying
accounts for specific purposes, for example the liquidation of Principle, Interest and Charges.
Change Primary Owner

This enhancement facilitates the change of PRIMARY.OWNER for an arrangement. This is achieved
by triggering the activity CHANGE.PRIMARY-CUSTOMER. The activity class is released for
LENDING, DEPOSITS and SAVINGS product line. If limits are specified then they are updated and
balances are moved to the changed primary customer‟s limit.
Notification of Pending Cancel

In addition to the existing CANCEL processing functionality it is now possible to generate an advice
indicating the pending cancellation of the arrangement, a number of days in advance from the
cancellation activity from which the advice is to be generated.
Lending processing for Cancellation

Cancellation period can be specified in TERM.AMOUNT property class for LENDING product making
this function generic across all the product lines. Customer is expected to disburse the entire
committed amount within this cancellation period. If the arrangement is not fully disbursed then
arrangement would be cancelled. Already accrued interest will be reversed out. Any DUE interest
amount will have to be repaid by the customer. Penalty interest will not be reversed out.
Pay Processing

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.

Valuation and Interface to the SC Module

An arrangement will become active in a portfolio only after a disbursal of the same has been done (in
case of loans) or a settlement has been done (in terms of deposits).
Cross currency valuation i.e. arrangement being in any foreign currency and the portfolio being in local
currency (USD) is possible, with the system picking rates from the currency table automatically.
Any kind of changes made in the disbursed loan or settled deposit will clearly reflect in the portfolio
indicating movement of funds. Changes could be such as, change interest, redemption of funds,
payoff or closure, partial funding within cancel period, partial withdrawal from deposit, increase of term
amount, term etc.
Link to another Arrangement

The settlement property class has been enhanced to enable the settlement of dues/payouts by using
another arrangement. The PAYIN.ACCOUNT and PAYOUT.ACCOUNT can now be either a T24
account or an arrangement account. (This can be Lending, Deposit or Savings arrangement.)
Lending Processing for Cancelation

Pre notification and cancellation of a lending arrangement has now been made available in line with
the current functionality on offer for the deposit product line.
Negative Interest Rates

The negative interest rate functionality has been enhanced so that when the field NEGATIVE.RATE is
set to BLOCK.MARGIN, if the net rate on account of the margin is more negative than the negative
rate, then the margin is ignored.
Exchange rate processing

This enhancement provides for foreign currency settlement of bills for an arrangement. The user can
have foreign currency arrangements with local currency settlement accounts and vice-versa. Cross
currency settlement can also be set up where in settlement happens to a foreign currency account/
arrangement from another foreign currency arrangement with the local currency being a different
currency.
Brazilian Interest Basis for AA

This enhancement enables Arrangement Architecture to support the new interest basis W (252/252)
and W1 (21/252) to calculate interest based on the actual number of working days. AA will support
both the standard compounding method and the Daily yield compounding method. New field
“COMPOUND.YIELD.METHOD” has been introduced in this enhancement, which will accept either
“YIELD” (only when COMPOUND.TYPE is set to DAILY) or NULL.

Retail Accounts
Accounts Product Line

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
Balance & Availability - CRF Update

This enhancement is to introduce sign change process to underlying accounts of Arrangements,
similar to traditional T24 Accounts, for the ACCOUNTS PRODUCT LINE.
AA
Overdraft Limits

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.
AA
Minimum Interest or Charge amount

For the ACCOUNT product line, through this enhancement it is possible to define a minimum amount
for Interest and Charges property class, and then waive the amount that has been calculated if it is
less than the specified minimum amount. This is achieved through the introduction of the new fields in
the Interest and Charge product conditions respectively
 MIN.INT.AMOUNT and MIN.INT.WAIVE
 MIN.CHG.AMOUNT and MIN.CHG.WAIVE
AA.
Extension of Source Calculation Types

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.
AA.
Blocking of Funds

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.
AA.
Debit interest linked to a limit

The property classes INTEREST and CHARGE have been enhanced with the functionality of linking
the Accounts arrangement (PRODUCT.LINE ACCOUNTS) to LIMIT, for the calculation of tiered
interest or charge. This is made available through the field REFER.LIMIT available in the INTEREST
and CHARGE product conditions.
AA.
Referrals and Mandates

Through this enhancement the system can provide the facility to use Mandates, Referrals and
INACTIVE.MONTHS functionality at the arrangement level when using the account property class.
The following fields have been added to the applications AA.PRD.DES.ACCOUNT,
AA.PRD.PRF.ACCOUNT, AA.PRD.CAT.ACCOUNT and AA.ARR.ACCOUNT
 MANDATE.APPL
 MANDATE.REG
 MANDATE.REC
 REFERAL.CODE
 INACTIVE.MONTHS
AA.
Eligibility
Product eligibility definition - New property class

Through this enhancement the Property Class Eligibility is released.

AA.
Eligibility review/update triggered by customer static change

Through the functionality added in this enhancement the system will trigger an eligibility review/update
when static customer information is changed.
AA.
Changes to CHANGE.PRODUCT property - Add relative of customer birth to the

CHANGE.DATE field

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 customer‟s
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 customer‟s birth date.
AA.
New Activity and associated actions to evaluate and change product based on
eligibility

Through this enhancement the AA.ACTIVITY.CLASS EVALUATE.ELIGIBILITY has been released.
This will enable the system to evaluate a customer‟s eligibility to a product.
Start of day and End of day processes; have been created to re-review the eligibility of the customer.
AA
Routines to validate eligibility when running an enquiry or creating a new arrangement

New routines have been added to evaluate a customer‟s eligibility
AA.
Arrangement Closure

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.

 ACCOUNTS-REQUEST.CLOSURE-ARRANGEMENT
 ACCOUNTS- CLOSE.ARRANGEMENT
 ACCOUNTS-DEBIT.SETTLE-ARRANGEMENT
 ACCOUNTS-CREDIT.SETTLE-ARRANGEMENT
AA.
Transaction Rules
Rule Evaluation
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
AA.
Back Valued Interest and Charges Adjustments

This enhancement introduces reverse and replay functionality that is relevant for the Account product
line namely interest and charges. The CHARGE.OVERRIDE property class is added to the
ACCOUNTS product line. The following AA.ACTIVITY.CLASS records are released or amended
through this enhancement:
 ACCOUNTS-CHANGE.PRODUCT-ARRANGEMENT
 ACCOUNTS-TAKEOVER-ARRANGEMENT
 ACCOUNTS-RENEGOTIATE-ARRANGEMENT
 ACCOUNT-CHANGE.PRIMARY-CUSTOMER
 ACCOUNT-PERIODIC.RESET-INTEREST
 ACCOUNTS-ADJUST.ALL-BALANCE.MAINTENANCE
 ACCOUNTS-ADJUST.BALANCE-BALANCE.MAINTENANCE
 ACCOUNTS-CAPTURE.BALANCES-BALANCE.MAINTENANCE
 ACCOUNTS-CAPTURE.BILL-BALANCE.MAINTENANCE
 ACCOUNTS-UPDATE.BIL-BALANCE.MAINTENANCE
 ACCOUNTS-UPDATE-CHARGE.OVERRIDE

A new ACTIVITY type NORR is introduced.

AA
Interim Interest Capitalisation

The AA.ACTIVITY.CLASS is introduced in the ACCOUNTS product line to facilitate interim interest
capitalisation. This will allow interest to be capitalised mid period and the new period calculation start
date to be cycled.
AA
Arrangement Bundle
Product Bundle
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
AA
Interest Compensation - Calculation of interest

The BUNDLE functionality is being enabled through this enhancement. This includes the calculation
of interest accruals for the arrangements in the bundle, the pooling of balances from the donor
arrangement, calculation of consolidated interest accrual and upgrading the interest property for
interest calculation. The following fields have been introduced in AA.INTEREST.ACCRUALS and
AA.ARRANGEMENT
 EFFECTIVE.DATE
 LINKED.ARRANGEMENT
 LINKED.PROPERTY
AA

Interest Compensation - Managing sequence at COB

AA supports different product lines and it is imperative to decide the sequence of COB processing for
product line.
Order of product lines to be processed will be
 Deposits
 Savings
 Lending
 Accounts
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.
Loans and Deposits
Brazilian Interest Basis for LD

As part of this enhancement, LD will support the new interest basis W (252/252) and W1 (21/252) to
calculate interest and commission based on the number of working days. Interest/Commission
calculation, accrual and capitalisation to be based on the new interest basis. LD will support both the
standard compounding method and the Daily yield compounding method.
Retail Front Office
The following Strategic Initiatives have been delivered in R11 GA from Retail Front Office

Retail Front Office released enhancements

Teller
Support Teller Limit

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 Stock control

Field STOCK.UPD is introduced in TELLER.PARAMETER and TELLER.ID. If this field is set to YES,
the denomination units input in TELLER.ID during till closure is treated as final stock with teller and
overwrite the TT.STOCK.CONTROL with denomination units entered in TELLER.ID for each currency
denomination except Travellers Cheques denominations This functionality is catered only for “Cash”
Transactions.
Teller Charges

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.
Banker draft management

CHEQUE.TYPE has been modified to identify the issuance of drafts which are internal to the Bank.
Additional validations like validating the payee name, validating the draft are handled in this table.
CHEQUE.REGISTER.SUPPLEMENT gets updated when a new draft is issued through the Teller
module. The table can hold various statuses like issued, presented, cleared, exception, unknown,
cancelled, stopped, and returned. The current status of a draft can be known by referring this
application.
Loan Origination
Scoring

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

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

Two new T24 tables have been added, SG.SLA and SG.SLA.COMMITMENT. SG.SLA is a design-
time (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 run-
time (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

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.
SLA Monitor service

A new T24 service, SLA.MONITOR.SERVICE has been created which runs in the background. If the
deadline is reached and the activity or process is not complete then the status field will be marked as
BREACHED to indicate that the SLA has been breached, and a delivery message will be produced for
the department account officer if this has been configured in SG.SLA.
Arc Internet Banking
ARC-IB css commenting

A new T24 service, SLA.MONITOR.SERVICE has been created which runs in the background. If the
deadline is reached and the activity or process is not complete then the status field will be marked as
BREACHED to indicate that the SLA has been breached, and a delivery message will be produced for
the department account officer if this has been configured in SG.SLA.
Default class definitions are all placed in general.css which has been enhanced with more comments
for different classes and attributes. Custom.css is now empty except for a commented example of a
class definition so that bank-specific styles can be added as required. This makes it easier for
implementers to understand the css and to be able to make changes as required.
Option to restrict the input into a field with the drop-down enquiry in ARC-IB

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

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.
ARC-IB support for Google Chrome

ARC-IB now supports the Google Chrome web browser.
ARC-IB support for Safari Browser

ARC-IB now supports the Safari web browser. This is tested on Apple Mac, iPad and iPhone and on
PC.
ARC-IB support for Opera

ARC-IB currently now supports the Opera web browser.
Support for custom styles for individual element in ARC IB browser

The enhancement enables an implementer to create custom styles for individual Enquiries and
Versions in ARC IB. First, the class definition of the respective Enquiry, Version or Application needs
to be copied from general.css to custom.css. Firebug can also be used to search for class definitions.
Then the class definition can be modified as required and linked to a specific Enquiry, Version or
Application. This provides much more flexibility in tailoring the look of an ARC IB web site.
Arc Mobile Banking
Stock Application Brandings

The standard set of icons delivered with the software can be altered and new icons can be added.
The directory structure for icons should be named as follows:
 STOCK
 STOCK16
 STOCK22
 STOCK32
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.

Add SMS Statistics to Admin UI

The 'SMS' secondary tab in Notification displays a summary of all SMS transmitted and all SMS
pending transmission.
Provision for J2ME Check Application

The send Check button in the Customer->Channels tab which will help to send a link to the customer
mobile which will help the customer to check whether connection is established. Once the Send
Check button is pressed it takes to a screen where it gives you a field to send the link to customer in
the form of SMS.
Mobile Banking on XHTML
Enhancement 47598 Build 201012.

The send link button in the Customer->Channels tab helps to send link to the customer mobile which
will help the customer to establish the link with the Core Banking through which the customer can
make payment and do funds Transfer.
RX-TCQ Notification

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.
SMP-IP Address Source

During installation of the ARC Mobile product installation engineers are required to enter the
connection details of the SMPP host the ARC Mobile product is to connect to and the phone number
of name as to where the SMS originated. At present this is limited to numeric IP Addresses and
numeric phone numbers. Installation engineers need to be able to enter hostnames and none numeric
source addresses.
Mobile Banking on Windows Mobile 7
Enhancement 41600 Build R11

The customer of client bank can access M-Banking functionality via Windows Mobile 7 device. The
functionality is identical to the standard mobile banking functions. The functionality was specifically
developed to suite Windows Mobile 7 handset device.
Mobile Banking on iPhone

The customer of client bank can access M-Banking functionality via iPhone device. The functionality is
identical to the standard mobile banking functions. The functionality was specifically developed to suite
iPhone device.

Mobile Banking on Google Andriod
The customer of client bank can access M-Banking functionality via Andriod device. The functionality
is identical to the standard mobile banking functions. The functionality was specifically developed to
suite Andriod device.
Access Recent SMS

A teller who views the customer record can view the recent SMS interactions with the customer. The
details of the SMS interactions that are held in ARC mobile will also be available to the Teller. He can
also view the SMS interactions through ARC-IB.
Connections via proxy

A new proxy connection provision is provided in ARC Mobile which helps to connect to Corebanking
via proxy, instead of connecting directly through corebanking.
Jca Connector

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
Arc Mobile Product Line

A new product line, MOBILE.SERVICES, has been introduced to integrate ARC MOBILE application
with T24.
Business Events
Business Events Product

This product provides the ability to send SMS/Email/Secure Message alerts to customers, whenever
an event for which they had registered an interest takes place.
Securities
The following Strategic Initiatives have been delivered in R11 GA from Securities.

Third Party Custody and Order Routing

Introduction:
Third Party Custody and Order Routing:
* Capturing of externally held asset / positions.
* Consolidated valuation and performance reporting.
* Configurable order routing system.
* Handling of execution hub/internal broker.
The enhancement is for capturing the external or third party transactions and positions. The third party
positions can be held in a separate portfolio or within the same portfolio in designated sub accounts.
As part of this enhancement, a parameter driven order routing system
How it works
Third Party Custody and Order Routing
Third Party Custody
There is a growing trend in investment management market (especially the institutional business
segment) to break the value-added chain and assign different roles to different partners/entities.
In case of external custody, from an investment manager‟s 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 bank‟s
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.

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;
 For direct orders from the portfolio manager – The transactions are captured in bank‟s
system (shadow trades) once the final settlement details are known
 For trades through in house dealing desk, settlement is more complex
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 bank‟s 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 bank‟s 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

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 bank‟s 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:

Online Portfolio Valuation

Online Valuation and Margin Lending:
* Intra-day portfolio valuation based on triggers.
* Online Purchasing power checks and framework for margin trading.
The enhancement is for providing automatic portfolio valuation based on triggers to ensure that the
portfolio value is near real-time.
The triggers could be securities purchase/sale, account balance movements, any other non-securities
transaction linked to a portfolio or a price change in the underlying security. Besides, this will also
cover purchasing power calculations, online checks for availability of funds based on purchasing
power, margin trading framework and margin call updates.
How it works
Online Valuation
The valuation in T24 is triggered through one of the following:
* Valuation during close of business
* Invoking standard valuation enquires supplied in T24
Existing valuation process flow can be divided into three major segments based on the nature of
assets being processed. The segments are:
1. Accounts linked to a portfolio.
2. Security positions for a portfolio.
3. Non SC assets/liabilities linked to a portfolio.
Shortcomings in the existing valuation Process
* Doesn‟t cater to the requirement for “real time” or “near real time” valuations
* Every valuation process revalue‟s the entire portfolio and not just the component (segment) that has
changed.
In order to overcome some of these shortcomings and provide additional functionality related to this,
the following changes are proposed to the existing valuation process:
a. Real-time valuation based on triggers – Automatic intra-day valuation based on triggers like
price change, securities transactions, account balance movement, etc.
b. Ability to select portfolios that require real-time valuation;
c. Ability to revalue select components;

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.
Securities Released Enhancements

Repos
Repos/Non-Linear Accrual Method

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.
Repos and short sale accounting

A short sale of Securities can be linked to a REPO transaction, by the booking of the securities
delivered in a short sale being posted as a LIABILTY and backed by a borrow in REPO transaction.
The result of the assessment is recorded in balance sheet accounts and results according to type of
REPO. The main idea is to book the deal which has been done using securities received as collateral
from counterparty and deliver to other counterparty in short sale.
Corporate Actions
Securities - Swift MT564

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.
EUSD - EU Taxes for back-dated Corporate Action Events

Whenever a backdated corporate action event is Input, even though the sale may have already taken
place, the system will calculate EUSD tax. For cash events the allocation process is performed along
with the rework process at the initial stage to enable the tax calculation.

Corporate Action Standing Instruction at Security level

This enhancement provides the functionality to create standing instructions in T24 for clients on the
security level for the credit of any cash to a particular account. This standing instruction will accept
input of internal security number, diary type and account number. For the unique combination of
internal security number and diary type the specified cash account will be credited. These instructions
will be set up at the portfolio level as done for the existing "Interest / Income Payment Currency
Standing Instructions".
Securities Trading
Sub-account - to Sub-account Position Transfer

It is possible to use the POSITION.TRANSFER application to transfer a position to a Sub Account of
the user‟s choice. POSITION.TRANSFER will accept entry in the SUB.ACCT.TO field for the Sub
Account to which the position is to be transferred.
SC.REVAL to identify local CCY gain or loss

Through this enhancement new fields have been added to SC.ACC.MASTER,
SC.TRADING.POSITITON and SC.TRADING.POS.HISTORY which allows the system to perform the
revaluation of Securities based on exchange rate movements, that is the posting of revaluation
gains/losses, should be posted to Equity (internal accounts). Revaluation of currency profits/losses
arising out of Positions held in foreign currency Securities in an available for sale (AFS) Portfolio can
be posted to internal suspense account categories
Different Trade to Security currency
Enhancement 72763 Build- 201010

In SEC.TRADE processing for such as a single-sided Dealer Book transaction with a Customer it is
possible to have a Trade Currency that is not the same as the Security Currency. An override will be
produced if this is the case. The Account Currency used for Dealer Book processing will be the
Security Currency, which will be used for any further Close of Business processing such as
Revaluation, Coupon Accruals, etc. The SC.TRADING.POSITION will also be held in the Security
Currency.
On-line valuation - Buying Power

A Buying Power calculation is available as part of Order processing based on the margin of a Portfolio
and cash balances. The concept of Buying Power looks at the liquidity of the Portfolio, offering a view
of the amount available to invest which is more comprehensive than cash flow checks.
The customer‟s cash accounts, the margin value of the customer's Securities, and other assets add to
the Buying Power calculation whilst pending orders and other liabilities such as Derivatives can reduce
it. The potential positive cash flows from selling orders are not taken into account.
As part of the buying power calculation process new purchase orders and amendments to Pending
Orders are evaluated in terms of any additional risk added to the Portfolio before any approval and
routing to the exchange takes place. To achieve this objective, the execution of an order is simulated

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.
Real Time Valuation and Margin Lending

Is a real-time valuation engine for automatic intra-day revaluation of portfolios. The valuations will be
automatically performed for select portfolio based on triggers. Triggers are nothing but events that
have an impact on valuation and could either be transactions (purchase, deposit) or static in nature
(price change).
A margin lending/trading framework is now available giving the customer who purchases securities the
option to either pay for the securities in full or borrow part of the amount from the bank. The portion of
the consideration that the customer pays is his initial equity in the account. The margins are generally
used to leverage the investments and increase the buying power. The buying power and eligibility will
be calculated on the basis of facility granted to the customer or the initial margin requirements
applicable. T24 also has the capability to track margin calls including identification of the type of action
to be taken viz. top-up or sell-out.
SC Revaluation Process - Transaction Level

Revaluation of unrealized profit/loss for own book (AFS type of portfolios) positions can be posted at
transaction level. To switch on this processing, it is required to set the field TRANSACTION.REVAL to
YES in SC.STD.SEC.TRADE.
Revaluation entries are posted at transaction level rather than at position level. When a new
transaction closes out an existing position, then FIFO method is used.
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. 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.

Third Party Custody

Focussing specifically on the situation where the custody is external, the problems are more at the
portfolio manager‟s end. They need to get accurate information about all the positions/assets under
management for the purpose of carrying out portfolio analysis, performance monitoring, providing
consolidated valuations, etc. This information cannot be provided, currently from T24, as not all these
positions are held in the bank books. From an investment manager‟s 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.
The “third party custody” holdings information is vital in order to:
a. Enable consolidated portfolio analysis including performance monitoring; and
b. Offer client reporting that encloses external assets
In order to meet this objective, all external transactions have to be captured in T24 with all details like
brokerage, charges and the actual exchange rates. 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, the enhancement is for
extending it to the cash side as well. Besides, there will also be a mechanism to segregate internal
and external positions so that there is no risk of selling the external positions.
Amortization of Trailer fees

A trailer fee is a commission paid by the issuer of a fund to the bank for providing the bank‟s customer
with services such as holding, ongoing investment advices and other handling services of those
financial products. Fee can be paid by issuer either in advance or in arrears. From an accounting point
of view trailer fees are qualified as a non transaction related revenue. The booking of
amortizations/accruals aims to smooth and forecast the bank‟s P&L, and to avoid peaks in accounting.
Security
The following Strategic Initiatives have been delivered in R11 GA from the Security stream.

Secure Source Code

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 a
secure software Development Policy, The Security code review/Analysis is the process of auditing the
source code for an application to verify that the proper security controls are present, that they work as
intended, and that they have been invoked in all the right places. Code review is a way of ensuring
that the application has been developed so as to be “self-defending” in its given environment. Security
code review is a method of assuring secure application developers are following secure development
techniques.
Through the identification of the different types of malicious code that can be applied to our existing
code we can identify “patterns” that this malware may exist in. We take these “patterns” and identify or
create a static test tool they can be automatically run during compilation of the code to identify any
potential threats.
R11 Internal Penetration Testing

Penetration testing is the practise of ethically hacking software in order to expose security
vulnerabilities in order to identify and remedy those issues prior to the release of that software.
The TEMENOS security stream has carried out an internal penetration test every 3 months from R10
to R11 focusing on the BROWSER and ARC-IB interfaces based on the latest TEMENOS model bank
release at the time.
The internal penetration tests have used automatic as well as manual test processes and utilized
information and initiatives from OWASP (The Open Web Application Security Project), a well
respected independent 3rd party focused on improving the security of application software.
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.
Authentication Server Enhancements

Decoupling of Authentication Server and T24 credentials
ARC-IB has been using a process known as impersonation to translate authentication server
credentials (user/password/PIN/ One-time password etc) to the External User id and password
required by ARC-IB.

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.
Transaction\Verification Signing in 4TRESS
Transaction signing or Transaction Verification refers to the Internet-based security method of

securely identifying a user through a single or two factor authentication at a transaction level, rather
than at the traditional Session or Logon level.
In T24 for the ARC-IB product Transaction Signing offers secure authentication using 4TRESS (a 3rd
party Authentication Server) to verify a User‟s Identity prior to committing a transaction, Versions and
Users that utilize Transaction Signing can be easily customized .
For more information please follow this link Transaction Signing in 4TRESS
Support for ActivIdentity 4TRESS v7
ActivIdentity always sell the latest version of 4TRESS, Temenos need to keep up with any changes in
their APIs. From 4TRESS v7 due to be released later this year, they will only support a web services
interface, therefore ARC-IB code has changed to use this instead of the existing Java EJB interface
that was available in previous versions.
ARC-IB has been configured with the new 4TRESS v7 and tested to ensure that all current
functionality is supported and that there has been no change to existing workflows, User
documentation has also been updated where necessary for the R11 wiki.
Security released enhancements

Transaction Signing in 4TRESSE

In T24 for the ARC-IB product Transaction Signing offers secure authentication using 4TRESS (a 3rd
party Authentication Server) to verify a User‟s 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

Business Activity Monitoring

This SI is concerned with enabling the SYSTAR product to monitor Business Activities in T24
 Create CBE events from T24 to enable the Systar product to monitor a clients operations –
TechOps
 Create more events from TAFC to help developers understand where they are generating
warnings and errors in their code
 Monitor important TAFC services like the Transaction Journaling log duplication service.
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.
Object Model and SOA Framework (Customer)

This SI covers modifying T24 for the Customer component to prove the technology developed as part
of SI-6053. This covers some of the technology areas required of the "adapter layer." Specifically:
Customer adapter: The customer adapter is an example of an adapter that requires read only non-
transactional 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.
TWS Enhancements for AA and consuming WS

The T24 system will be more attractive by providing a generic way to consume external web services
as part of a T24 transaction or workflow. We know that our clients frequently introduce real time
functionality into their operations - such as credit checks before approving customer credit cards or the
validation of addresses while making a payment. This type of functionality is currently implemented
with complex local coding or sometimes not at all as the custom code is too costly to develop. This SI
proposes a new feature in our T24 Web Services (TWS) product that will be very attractive to new and
existing clients. This SI proposal will enable T24 web service offering to support Arrangement
Architecture (AA) transactions.

TAG Replacement and .net Connectivity

This SI proposes to simplify the Temenos Web Service offering by leveraging the standard platform
configuration services rather than a Temenos proprietary design. This will result in a simpler more fault
tolerant system that fully utilizes our existing architecture for deployment and high availability.
TAFC Platforms R11

Our customers expect T24 to run optimally on the latest hardware and software. To stay in touch with
our competitors and our customers‟ expectations, it is essential that we keep our application
framework tuned for the very latest operating system and hardware platforms. This proposal outlines
the modifications required to update the Temenos Application Framework „C‟ version (TAFC) and
recommendations for delivering these platforms with reduced cost.
SOA Framework released enhancements

This section contains a high level overview of each enhancement that have been delivered in R11.
TWS Composer

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

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

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.SERVICES-
NEW-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.

Swift 2010 updates (600 series)

The SWIFT 600 series of messages for 2010 have been upgraded to support all commodity
transactions as opposed to only supporting Precious Metals. The scope of this enhancement is purely
to continue the T24 support of metals trading using the FX module.
Linear Revaluation method for Swaps

A new Linear revaluation method has been introduced for Swaps according to which the Net Present
Value of each leg is calculated using the following formula: -
NPV = i = N
Σ CFi___________
i=1 (1+ R) ^ (D / B)
Where: -
N= Number of interest payments between the revaluation date and the maturity date
CF= 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= Number of days between the revaluation date and the corresponding cash flow date
B= Interest Day Basis
A new table SWAP.REVAL.PARAMETER has been introduced to take care of all the revaluation
related parameterisation.
Treasury released enhancements

Derivatives
Automatic Close out record created in SAM Company

During the Close of Business in a multi book environment, the Closeout record for the Customer side
and the Broker side (B2B) is now generated in the Company where the Customer‟s portfolio is held.
Money Market
Money Market support of Interest Basis E1 365/365

The INTEREST.BASIS E1 365/365 is now supported in the Money Market module.

Swaps
Swaps support of Interest Basis E1 365/365

The INTEREST.BASIS E1 365/365 is now supported in the Swaps module.
Change in accounting rules for Swaps with negative interest rates

The Asset and Liability Accrual Categories are now called Income and Expense Accrual Categories;
the respective fields in the SWAP.PARAMETER are changed accordingly. This change is brought
about to bring into effect a change in accounting rules for Swaps with negative interest rates.
A new Revaluation method for Swaps

A new Linear revaluation method has been introduced for Swaps according to which the Net Present
Value of each leg is calculated using the following formula: -
NPV = i = N
Σ CFi___________
i=1 (1+ R) ^ (D / B)
Where: -
N= Number of interest payments between the revaluation date and the maturity date
CF= 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= Number of days between the revaluation date and the corresponding cash flow date
B= Interest Day Basis
A new table SWAP.REVAL.PARAMETER has been introduced to take care of all the revaluation
related parameterisation.
Forward Rate Agreements
Contract wise positions for Trade FRA

For trade FRAs, an option can be given to value the contract wise positions daily instead of valuing the
net FRA positions from the trade date till the rate fixing date. Additionally for discounting the
Profit/Loss, an additional method of using the Long period and rate (for the period from Valuation date
to Maturity date) is also introduced. If New option of individual deal wise valuation for Trade deals is
enabled, deal wise present value P/L will be posted to the CATEG.ENTRY and contra to the internal
account.

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.
Asset Structures & Alerts

Asset Structures and Alerts (Phase 1) (SI - 2043)
Asset Structures and Alerts considers the unification of Asset Structures in T24 into a new framework
and adding customer/relationship manager focused Alerts to the current BEM framework, allowing the
configuration of alerts on many areas of Wealth processing, including Rebalancing Violations, Order
Management, Trading information, and Responsible Management information.
Asset Structures simplifies the creation of models, blends Asset Structures (Models) with
Segmentation Structures. Allows Fixed and Dynamic models in one model build tool. Introduces
Randomised Instrument selection/Stock Pick Lists.
Alerts & Events Introduces Proactive Portfolio Management to Private Wealth Users, Alerts feed into
Compliance and Worklists allowing and RM or a customer to manage their portfolio proactively and
react to changes before it‟s too late.
Client Reporting
Client Reporting - Ad-hoc Client Statements

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.
T24 Client reporting engine upgrade
Enhancement 5617

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.
Wealth Management Release Enhancements

This section contains a high level overview of each enhancement that have been delivered R11.
Rounding Functionality in Cash Management

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.
Dynamic Model Buckets in any Reference Currency

Allows specification of Dynamic Model with child nodes where the reference currency differs from the
root node reference currency.
See Dynamic Model Input and Integrity Check for further details.
Open Orders Impaction on Cash Management functionalities and Portfolio Valuation

Cash Management and Portfolio Valuation takes into account accrued interest on open orders for
bonds and takes latest market price for market orders or latest limit price for limit orders. See Request
Parameters for further details.
Minimum Trade Size for Rebalancing

It allows specification of minimum trade size for orders created on rebalancing of static models. Only
orders where the computed nominal is greater than or equal to the minimum trade size will be
generated. See Static Modelling for further details.
BV.REPORT.LOG Design Change

Change to record key for Backvaluation Report Log file. The Record key has been extended so that
records are unique for portfolio and processing date.
ARC-IB Improvements
ARC IB Phase 1 Improvements

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.
Asset Structures & Alerts
Asset Structures

Asset Structure Overlays can be defined and used to create all potential nodes for a dynamic model
based upon the asset structure as skeleton records. The applicable nodes can then be completed as
required for the model. See Create Asset Structure from Overlay for further details.
Alerts and Events

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

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

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

Wealth Management Administration Home Page
Model Bank Phase 2

Customer Onboarding, Tab for Foreign Exchange Dealer, Compliance home page.

R11 Release Highlights PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

R11 Release Highlights PDF

Uploaded by

Copyright:

Available Formats

T24

R11 Release Highlights

Information in this document is subject to change without notice.

Copyright 2005 TEMENOS Holdings NV. All rights reserved.

TEMENOS T24 User Guide Page 2 of 61

TEMENOS T24 User Guide Page 3 of 61

Transaction\Verification Signing in 4TRESS .................................................................................. 52

TEMENOS T24 User Guide Page 4 of 61

T24 Java Deployment

T24 for Java will have the following features:

Application Framework released enhancements

TEMENOS T24 User Guide Page 5 of 61

 Ability to identify contracts as “Individually Significant”

 Ability to define rules for possible reclassification

TEMENOS T24 User Guide Page 6 of 61

Enterprise Customer - Publishing

New Service operations for Customer:

The following are the new service operations being introduced

AA performance and Infrastructure

TEMENOS T24 User Guide Page 7 of 61

Banking Framework released enhancements

Interest and Charges

Interest Basis E1 365/365

Enhancement 32044 Build 201008

Interest Basis W (252/252) & W1 (21/252)

Enhancement 30230 Build 201011

Account Related Fees-Waiver by Fee Type

Enhancement 61191 Build 201011

Update of Turnover figures in ACCT.ACTIVITY by reversals - Red Storno

Enhancement 48658 Build 201010

Impairment Assessment & Capture - IFRS.DATA.CAPTURE (Validation)

Enhancement 40969 Build 201008

TEMENOS T24 User Guide Page 8 of 61

The application IFRS.DATA.CAPTURE is added to capture details of contracts to be used for

Impairment Assessment & Capture -Individual (Update of EB.CASHFLOW)

Enhancement 28057 Build 201008

Fair value to use rates for each cash flow date

Enhancement 19419 Build 201008

Individual loss impairment calculation & Accounting

Enhancement 28097 Build 201010

Enhancement 28085 Build 201012

Impairment of AFS Securities

Enhancement 26982 Build 201012

TEMENOS T24 User Guide Page 9 of 61

Enhancement 28085 Build 201013

Reversal of impair or unimpair operations

Enhancement 80481 Build 201014

Ability to correct an incorrect Sub Type

Enhancement 80480 Build 201014

TEMENOS T24 User Guide Page 10 of 61

Merge PD in order to calculate T24 balance

Enhancement 80477 Build 201014

Repayment and write off assessment accounting

Enhancement 28445 Build 201014

Impairment Assessment and Capture - IFRS.IMPAIRMENT.CODE

Enhancement 28060 Build

Reversal of impairment accounting

Enhancement 28460 Build 201014

Automatic link of collateral to Expected Cashflow

Enhancement 28566 Build 201014

TEMENOS T24 User Guide Page 11 of 61

Enhancement 80479 Build 201014

Maturity of an impaired Loan