T24 Navigation and Environment R14 D-1

T24 Navigation and Environment R14 D-2

T24 Navigation and Environment R14 D-3
 T24 consists of the code base- which is the code for applications and services.

Enquiries, versions and Menus are built for different roles in a bank and the
configuration is created for a Model bank with best practice processes based on our
experience in implementations.

T24 Navigation and Environment R14 D-4

 Model Bank is currently packaged with Pre-configured products and processes in
Retail, Wealth, Corporate, Payments and Treasury business domains. The objective of
Model Bank is to reduce implementation effort, by building a robust set of Products
and Processes which can be delivered out of the box.
This is supported with a good Reference System T24 User Guides, Model Bank
Reference Documentation and Help Text.
T24 Model Bank includes the following

System Parameters

Customized Screens, Reports, Home Pages, Internet Banking Pages

Products

Static Data - Customer, Brokers, Counterparties Banks/Agents

Financial data - Accounts, Deposits, Loans, Portfolios

Populated with transactions across all Products to feature the different
functionalities

Enquiries/Reports pre-populated with data

Home Pages with attractive dashboard

T24 Navigation and Environment R14 D-5

T24 Navigation and Environment R14 D-6
 Enter your Username and Password to login to T24

T24 Navigation and Environment R14 D-7

7
 This is the home page that you see as soon as you log in to browser. We will soon see
how we can customize the home page & the menus without writing a single line of code

T24 Navigation and Environment R14 D-8

 There are various methods of creating a record in T24.
The first method to input a new record is by typing the <Application name>
followed by a space and the function for input- I , followed by another space
and the keys F3 in the command line.

The most frequently used method to input a new record is to click on the new
deal icon when the application is launched. In this illustration you have launched
the CUSTOMER application and a new customer can be input by clicking the new
deal icon.

If you are working in a classic mode then type in the <APPLICATION> I followed
by Ctrl+F+Enter .

T24 Navigation and Environment R14 D-9

 After an application is launched, the user can input the ID and use any of the buttons
depending on the function to be invoked, viz Edit, View and Action
button(interchangeably referred to as function or operation).
EDIT Button - New record is displayed for input or existing record is opened for
amendment
ACTION Button - Record is displayed and Authorise, Delete, Reverse or Verify operations
enabled appropriately
VIEW Button - Opens a record in See mode

This is an alternative method to giving the function along with the application and ID in
the command line of the Home Page

T24 Navigation and Environment R14 D-10

 We see a sample record in the CUSTOMER application. The application name and the record Id(
Customer number) are displayed. Details of the CUSTOMER are filled into the various fields.
The VALIDATE button is used to validate the data entered in the fields. Errors will be raised on
validation
The COMMIT button will commit the record and save the contents of the record into the
corresponding database table.
The HOLD button is useful, when the user does not want to commit the data entered into the
database, but at the same time does not want to lose the information input. The data input is
saved to be modified, committed or discarded later as per the users discretion.
The next set of buttons are Functions enabled on using the ACTION button for an existing record
ID. For a NEW record these will be disabled.
In T24, DELETE function is used to delete an unauthorized record. T24 will never re-generate the
ID of such a record. Once generated the ID is never re-used unless manually input by the user.
The AUTHORISE function is to be used to authorise the record. An authorizer should be different
from the user who input the record.
Any record which has been authorized cannot be deleted and can be removed from the live files
only by using the REVERSE function. This moves the record to history.
The button which looks like the NEXT button is used to verify a record. This is applicable only for
certain applications. In FOREX and MONEY.MARKET applications, deals are prepared orally
through brokers sometimes. When the written confirmations are later received, verify function
is used to record time and date of receipt of confirmation.
The Up arrow button is displayed when a function is applied on a record. This button is used to
return to the application

T24 Navigation and Environment R14 D-11

 For additional information on any of the field in an application, click on the Field Label
and online helptext is displayed.

The button with the letter i is useful to invoke predefined context sensitive enquiry.
For example you may view additional information of the related customer 100295 by
clicking on the Context Enquiry.

One significant and important feature in T24 is called multi value and sub value facility.
Multiple data can be stored in a field by dynamically expanding the field during
transaction input.

+ symbol is used to for multi valuing a filed. When the field name begins with GB, it
indicates a language multi value. For example the CUSTOMER may have short name in
different languages.

When the field name does not begin with GB, it indicates a multi value field. For
example a CUSTOMER may have multiple email IDs.

Sub Value When a multi value field is made up of multiple values. For eg a
CUSTOMER may have a residence and an office address. The residence address is
composed of multiple lines that make up the address.

T24 Navigation and Environment R14 D-12

T24 Navigation and Environment R14 D-13
 After data is entered into a record, the Validate Button can be used to find out if there
are errors. Errors will be displayed with a link to the field containing the erroneous data
and must be corrected before the record is committed

The Commit button also invokes the Validations

T24 Navigation and Environment R14 D-14

T24 Navigation and Environment R14 D-15
 When a record is committed, Overrides may be raised. Overrides are warnings.

T24 Navigation and Environment R14 D-16

 An override is a warning message generated to inform the Inputter about some data
that is input in the record and needs confirmation from the User for committing the
record with the given values.
For example, A customer wants to withdraw $100 from his savings account which has a
balance of $150. Assume that by T24 norms, the minimum balance in the savings
account should be $100. When transaction is input to debit $100, on committing it T24
generates an override about the insufficient funds available.

Override Messages are displayed with the Accept Override link and this must be clicked
to store the record in the database. The override message is stored as part in the
OVERRIDE field as part of the record.

If you do not want to accept the Override, you may either put the record on hold to
correct it later or amend the record and commit it again.

T24 Navigation and Environment R14 D-17

17
T24 Navigation and Environment R14 D-18
18
T24 Navigation and Environment R14 D-19
19
T24 Navigation and Environment R14 D-20
T24 Navigation and Environment R14 D-21
 Go to role based home page in the T24 menu and check out the home pages customized
according to role of the bank employees . Shown here is a sample home page for a Head
Teller.

T24 Navigation and Environment R14 D-22

 Every user can access a branch or multiple branches( in case of a bank having many
branches) . They use core T24 applications, user defined screens , functions to access
them , fields to input data , workflows in which many applications are interlinked
logically and enquiries to view reports .

T24 Navigation and Environment R14 D-23

 1. Every bank employee who needs to login and perform any action in T24 must
have a profile or a record in USER application.
2. Rights and privileges for a user are defined in the user profile . For example,
access can be given only to FUNDS TRANSFER and CUSTOMER applications and
also restrict the access only to Input and List functions.
3. The user profile is a record in the USER application

T24 Navigation and Environment R14 D-24

 COMPANY table holds one record per company created in the installation.
The company mnemonic is used as the file prefix.
The ID of a record in the COMPANY table is referred to as the company code in T24. The
format is CCGGGLLLL Where: CC is Country Code GGG is Company Group Code and LLLL
is Local Code. For example GB-001-0001

T24 Navigation and Environment R14 D-25

 LOCAL COUNTRY : This field holds the country code where the company is situated.
LOCAL REGION : This field identifies the region in the country in which the company is
physically situated.
LOCAL CURRENCY : This field holds the local currency of the company.

APPLICATION : The Bank may restrict the access of applications to different companies.
A company may have access to a set of applications only. This field holds the various
applications that are installed in the company. Different companies of a bank may have
different set of applications installed.

FINANCIAL YEAR END : This field holds the current financial year end date and the
frequency from there on.

Sharing of files among different branches can also be set in COMPANY application

T24 Navigation and Environment R14 D-26

 This illustration shows how files are shared by different branches based on what
information they hold customer, financial or installation parameters.

CUS CUSTOMER and COLLATERAL are CUS type of files . A branch may opt to share it
with other branches or have its own data.
FIN Financial tables like ACCOUNT and FOREX are not shared among branches. Each
branch maintains its own data.
INT Installation files like DATES, SPF only hold information that can be used across
branches and hence shared by all branches.

T24 Navigation and Environment R14 D-27

 As shown in the illustration, the Financial files are not shared. Files of type FIN are
exclusively maintained for each Branch. Installation files are always shared by all the
branches of the bank. As represented in the figure, there is only one set of the files
whose type is INT, shared by all branches. Customer files can be configured to be
shared between branches or Not shared. As shown Branch 1 and Branch 2 share the
files with type = CUS, whereas branch 3 has its own copy of Customer files. Like CUS
types, the FIN type files can also be configured to be shared between some branches
and exclusive for some. Where can these configurations be defined? In the COMPANY
record for the Branch.

T24 Navigation and Environment R14 D-28

 CUS type of files store customer related details.
These files can be shared by companies or each company can have its own
file.
File name format for CUS files is F<MNEMONIC>.<APPLICATION>. For
example, FBNK.CUSTOMER
FIN type of applications store the financial information related to a company.
FIN files are not shared. Financial information as a practice is stored company
wise. Financial information is crucial in deciding the health of the Bank and
its branches and thus is stored company wise.
As these files are company specific, the mnemonic of the company is a part of
the file name to identify to which company the files belong to.
File name format is F<MNEMONIC>.<APPLICATION>. For example,
FBNK.ACCOUNT
INT type of files or applications are specific to one T24 installation.
Such type of files are not company specific and there is only one file in the
first Lead Company irrespective of the number of branches in an installation.
All the other Lead and Branch companies can access these files.
As these files are installation specific, the company mnemonic is not part of
the file name. The file name is F.<APPLICATION>. For example, F.SPF,
F.COMPANY are some INT type of files.

T24 Navigation and Environment R14 D-29

 Applications in T24 are broadly classified into INT, CUS and FIN. There are other sub-
types too, but are not in the scope of this learning unit.

INT - Parameter tables or static tables that are common to all companies in the
installation fall under this category. For example SPF, PROTOCOL, COMPANY etc. where
only one file exists at database level regardless of the number of companies.

FIN - Application files store financial data. For example ACCOUNT,

LD.LOANS.AND.DEPOSITS etc. Financial information is always specific to a company.
Thus these type of applications will require multiple files at database level depending on
the number of companies.

CUS - Application files store customer related information. T24 gives the bank two
options of storing this type of data. The first option being similar to the INT type where
there will only be one file at database level irrespective of the number of companies if
the data is to be shared among the companies or multiple files at database level to store
company specific data if data is not shared between companies.

FILE.CONTROL application contains data about application classification.

T24 Navigation and Environment R14 D-30

 T24 maintains and uses its own dates.
T24 does not consider the system date but date from the DATES table. However some
applications consider the system date. For example, in the USER application
START.DATE.PROFILE field takes into consideration the current systemdate and not
T24 date.
DATES application is used to define the dates for the previous, the current and the
next working day
The DATES table need not be manually updated to change the current working day.
Dates are rolled forward automatically during the Close Of Business process.
All Companies defined in T24 will have a record in DATES table. ID of a record in DATES
is COMPANY.ID
DATES is an INT type of file and therefore the file name at database level is F.DATES.
Holidays are stored in another table, which will be discussed as we proceed

T24 Navigation and Environment R14 D-31

 The DATES application is used to store the previous, the current and the next
working day. When the dates are rolled forward, only working days are
considered.
The ID of a record in DATES table is the Company code.
TODAY : This field denotes the current T24 date.
LAST WORKING DAY : This field holds the date of the previous working day before
COB was run.
NEXT WORKING DAY : This field holds the date of the next working day with
respect to today.
The values in the above 3 fields will be updated during COB.
Values for these fields are populated during Close of Business after referring to
the HOLIDAY table (To be discussed next).
Every transaction in T24 will contain a Value Date which refers to the date on
which the transaction will affect the banks books of accounts. Some T24 modules
support a backward or a forward value date. The maximum back value and
forward value possible is stored here.
BACK VALUE MINIMUM : This field specifies the minimum back value date for a
transaction.
BACK VALUE MAXIMUM : This field specifies the maximum back value date.
FORWARD VALUE MINIMUM : This field specifies the minimum forward value
date.
FORWARD VALUE MAXIMUM : This field specifies the maximum forward value
date.
VERSION, LOCAL PAYMENT DAY and LOCAL DISPO DAY fields are reserved for
future use and are not used currently.

T24 Navigation and Environment R14 D-32

 1. The purpose of the HOLIDAY table is to indicate the public holidays for each
Country, or Region within a Country.
2. HOLIDAY is an INT type of file and therefore the file name at database level is
F.HOLIDAY.
3. This table is referred during COB to determine T24s next working day.
4. This table is also referred by T24 to check for holidays and weekend days when
dates are input in any transaction.
5. The ID of a record in this table is in the format <CountryCode RegionCode
Year>. For example GB 00 2010, AT 00 1988, etc..

Even before you set up a record in the HOLIDAY application, the REGION and
COUNTRY tables must be set up since they are part of the record ID.

T24 Navigation and Environment R14 D-33

 To set a particular day as a holiday in a month, the following fields are used
JANUARY DECEMBER : These fields hold the days that need to be declared as holidays in the
respective months. Valid values are 01 until 31 (if applicable). Space is the delimiter.
WEEKEND DAYS : This is a Multi value field that is used to define the days that are weekends.
Valid input will be any of the days from Monday to Sunday
MTH 01 TABLE - MTH 12 TABLE : These fields are no input fields. These are populated based on
values in fields JANUARY - DECEMBER, WEEKEND DAYS and WRK WKND JANUARY - WRK
WEEKEND DECEMBER. This field can hold H W X as values. H stands for Holiday, W stands for
Working day and X stands for No more days in the month.
WRK WKND JANUARY - WRK WEEKEND DECEMBER : These fields holds the days which are
actually weekend days but to be declared as working days for each month. Valid values are 01 to
31 (if applicable)
It is not possible in T24 to declare Current day and the next day as holidays. T24 needs at least
one day time to declare a working day as a holiday. For example, if today is 9th Jan and
tomorrow is 10th Jan, you cannot set both 9th and 10th as holidays in T24. On 9th Jan you can
only set 11th Jan and above days as holidays.
If there is any unforeseen situation and you have to declare a holiday during the middle of the
day on 9th Jan, then the Administrator should run COB for 9th Jan before closing so that the
dates are rolled over to 10th Jan which is the next working day.
If there is a situation that you have to set 10th Jan as a holiday on 9th Jan, then the
Administrator has to run COB both for 9th Jan and 10th Jan so that the dates are rolled over to
11th Jan which is the next working day. Running COB back to back blindly may not solve this
issue. Certain applications may require local development. If transactions come in through
interfaces or ATMs on the physical 10th Jan, they will be taken as transactions for 11th Jan only
as T24 date has already been rolled forward.
In typical situations, COB can also be run remotely by an Administrator.

T24 Navigation and Environment R14 D-34

 1. True
2. False Errors must be corrected. Record cannot be committed otherwise
3. False Mnemonic is prefixed for CUS and FIN files
4. False Holiday table
5. True
6. False - FIN files are not shared since they contain Financial information
specific to one company only.

T24 Navigation and Environment R14 D-35

T24 Navigation and Environment R14 D-36