Click to edit Master text styles
CUSTOMER
Second level
Third level
COURSE MAP
During the next sessions
on CUSTOMER module, we
ES
ST
PL
shall be discussing
RU
AM
CT
• The CUSTOMER structure with
UR
EX
E
linked tables
• Special features of T24 CUSTOMER
CUSTOMER module
W
E S
OR
R
• Example inputs in relevant TU
KS
E A
applications, files
HO
F
P
• Workshops to understand the
features
2
OBJECTIVE
To comprehend
• Customer application and the basic information required
• Tables and applications linked
• Creation of Customer defaults, groups and other special features
• Definition for important fields
• Creation of a Customer record with relevant database
3
COURSE AGENDA
SESSION I
• Introduction to CUSTOMER Application
• Linked Tables and applications
BREAK
SESSION II
• Some important field definitions
• Examples and Workshop exercises
4
INTRODUCTION
5
INTRODUCTION
Introduction to CUSTOMER Application
• Core application within T24 system
• Associated tables need to be defined for creation of database
• Must be set up before recording any customer activity
• Central to the organisation of:
– information.
– services.
– profit and loss
• Creation of record is not linked to existence of an account or
contractual relationship
6
CUSTOMER APPLICATION
Introduction to CUSTOMER Application
• Primary record prior to any activity in T24.
• Contains only descriptive details of the CUSTOMER.
• No financial data is recorded
• Base record.
• Linked to Accounts and Contract applications.
• Only one record should exist for each customer.
7
TYPES OF CUSTOMER
Introduction to CUSTOMER Application
• Customers could be
– Clients - Private, Corporate
– Agents - Other banks, Brokers
– Counterparties - Other banks - Retail and Corporate, Guarantors
• Record opened based on nature as well as category of customers
8
RELATIONSHIP BETWEEN
CUSTOMER AND PRODUCTS Introduction to CUSTOMER Application
CUSTOMER
A/C BASED CONTRACT BASED
CURRENT ACCOUNT LOANS
SAVINGS ACCOUNT MM
NOSTRO ACCOUNT FOREIGN EXCHANGE
USD ACCOUNT SECURITIES
9
CUSTOMER ID
Introduction to CUSTOMER Application
• CUSTOMER ID is an integral part of the record
• System always refers to the Customer base record for all basic
information.
• Customer is identified by this unique numeric code. It can have 10
digits, ranging from 1 to 9999999999
10
LINKED TABLES
11
STATIC TABLES LINKED TO CUSTOMER
Linked Tables and Applications
COUNTRY
LOCAL
REFERENCE RELATION
LANGUAGE
SECTOR
GLOBAL
CUSTOMER STATIC TABLES STATUS
LINKED TO CUSTOMER
DEPT.ACC
RESIDENCE
T.OFFICER
CUSTOMER
INDUSTRY
STATUS
NATIONALITY TARGET
12
COUNTRY
Linked Tables and Applications
• Nationality and Residence fields of Customer record gets the
country code from this table.
• Core table in T24
• Id is 2 letter code such as PL, IN,US
• ID is a standard SWIFT abbreviation.
• Code can be used in fields such as Place of Birth, additional
Passport fields ( local reference) if included in Customer table.
13
COUNTRY
Linked Tables and Applications
14
RELATION
Linked Tables and Applications
• Specifies the various types of relation that could exist between one
Customer and another.
• Used for grouping customers, for reporting and information
purposes
• 99 different relation codes can be defined.
• Can be used to define corporate Customer Relations as well as
private Customer Relations
• Any pairings can be set up through this table
15
STATIC TABLES-RELATION
Linked Tables and Applications
16
LANGUAGE
Linked Tables and Applications
• Identifies the Languages that may be used on the System while
defining multilingual fields.
• A code same as, or similar to the Country code associated with that
Language may be used.
• Should be set up first when installing the General tables
• Identifies the Language to be used for correspondence.
• At present four languages are used.
• English, French, German, Spanish
• Additional languages can be added to this table. However, T24 will
not translate these other languages automatically .
• T24 is not a translating machine
17
LANGUAGE
Linked Tables and Applications
18
LANGUAGE
Linked Tables and Applications
19
SECTOR
Linked Tables and Applications
• Enables grouping the customers into various sections.
• Grouping is required for applying different rates of charges or for
reporting purposes.
• Customers grouping is done to identify the legal status of the
customers like individual, partnership, private company, public
company, Government etc
• Also used in CUSTOMER.DEFAULT records
• ID of this table is four digits numeric.
• 9999 different sectors are possible in T24
• Mostly used by Banks for defining the CONDITION.PRIORITY along
with CATEGORY
20
SECTOR
Linked Tables and Applications
21
SECTOR
Linked Tables and Applications
22
DEPT.ACCT.OFFICER
Linked Tables and Applications
• Identifies the main Account officer attached to the specific
customer.
• Can define the companies to which restricted or prohibited from
• Holds information about the officer
• Defaulted on all Customer transactions within T24
• Can be overridden by another account officer code at the
transaction or product level.
• Used in generation of MIS information at the Account officer level.
• ID is four digit numeric.
23
DEPT.ACCT.OFFICER
Linked Tables and Applications
24
INDUSTRY
Linked Tables and Applications
• Defines the activity of the customer
• Industry level details are required for the bank to deploy the funds
in adequate proportion.
• ID is four digit numeric. Enables creation of 9999 different types of
industries
• Activity could be manufacturing, trading, financial service,
agriculture etc which can further be divided into the second level
activity of the customer
• Can hold two levels of activities
• ID is four digit numeral with 9999 values.
25
INDUSTRY
Linked Tables and Applications
26
TARGET
Linked Tables and Applications
• Identifies the targeted customers.
• How a customer is viewed by the bank for its marketing strategy
• Customers can be targeted for different types of products like loans,
deposits, Credit cards etc.
• ID is four digit numeric.
27
TARGET
Linked Tables and Applications
28
CUSTOMER.DEFAULT
Linked Tables and Applications
• Enables grouping of customers
• Reduces the data input while creating a CUSTOMER record
• Defines frequently used combinations of codes for
– INDUSTRY
– DEPT.ACCT.OFFICER
– TARGET
– COUNTRY (Nationality and Residence)
– CUSTOMER.STATUS
linked through the SECTOR code.
• Simplifies the opening of a new CUSTOMER record with mandatory
fields updated automatically upon inputting the specific Sector code
29
CUSTOMER.DEFAULT
Linked Tables and Applications
• Customers are grouped based on SECTOR.
• SECTOR ID is used for this table.
• Whenever you input sector code while recording a Customer record,
the following fields will be automatically populated from this table.
• ACCOUNTS.OFFICER, INDUSTRY, TARGET , NATIONALITY,
CUSTOMER.STATUS, RESIDENCE
• Also defines whether Address(Street) is mandatory or not.
30
CUSTOMER.DEFAULT
Linked Tables and Applications
31
CUSTOMER.STATUS
Linked Tables and Applications
• Codes defined are assigned to CUSTOMER records of T24
• Enables the bank to classify their clients by any kind of criteria
defined locally.
• Enables standard codes for highlighting specific information about
a CUSTOMER
• Identifies the quality of the customer
• Can be defined by the bank as per its own practice.
• Can be used in conjunction with standard ratings set by Standard
and Poor or Moodys. AAA, AA, High rated
32
CUSTOMER.STATUS
Linked Tables and Applications
33
GLOBAL.CUSTOMER
Linked Tables and Applications
• Identifies all the multi-national Customers to whom the bank will
assign a unique identification number on a worldwide basis .
• When entered in a CUSTOMER record, will link together various
Customer records through this common ID
• The Head-office can consolidate the data from different branches on
a worldwide basis
• Specifies a unique identification number for a multi-national
customer.
• Identify the customer who is having various accounts with various
branches of the same bank across the globe.
• ID enables consolidation of the Global Customer exposure and the
profitability
34
GLOBAL.CUSTOMER
Linked Tables and Applications
35
LOCAL REFERENCE FIELDS
Linked Tables and Applications
• Enables addition of more information as per the Bank’s specific
requirements
• Unique for each Bank
• Fields thus created can not be deleted and hence care should be
taken in designing the local reference fields.
36
LOCAL REFERENCE FIELDS
Linked Tables and Applications
37
IMPORTANT FIELDS
38
MNEMONIC (MANDATORY)
SOME IMPORTANT FIELDS
• Alternate way of referencing the customer. It is similar to ID.
• It should be unique across T24.
• System will automatically update the internal file
“MNEMONIC.CUSTOMER” which allows the user to display the
customers as Mnemonic sequence instead of Customer ID.
39
MNEMONIC.CUSTOMER
SOME IMPORTANT FIELDS
40
SHORT NAME (MANDATORY)
SOME IMPORTANT FIELDS
• Identifies the name of the customer in more descriptive form.
• Used for on-line enrichments in any field where a customer ID or
Mnemonic is input. Name 1 (M) – Similar to the above.
41
STREET
• Though a non mandatory field input is required.
• System will not permit committing the record without input.
42
CUSTOMER.LIABILITY
SOME IMPORTANT FIELDS
• Identifies the customer who is liable for the advances/loans to be
granted to this customer.
• Could be self or another customer.
• A CUSTOMER has to be liable for himself first before he can be
made liable for other Customers
• Field gets updated either at the time of creation of the record or
through COB if done subsequently through the application
LIMIT.CHANGE, on-line.
43
CUSTOMER.LIABILITY
SOME IMPORTANT FIELDS
44
NATIONALITY and RESIDENCE
SOME IMPORTANT FIELDS
• 2 alpha characters (Uppercase)
• Country code characters.
• Mandatory input if no default value has been specified on the
CUSTOMER.DEFAULT table for the corresponding Sector Code or
the VERSION file [Ref: UTILITIES].
• Otherwise input is optional and will override default value.
• Should be as defined in COUNTRY table.
45
RELATION.CODE
SOME IMPORTANT FIELDS
• Shows if any other customer is related to this customer. If so how
he/she is related to this customer.
• Customers may be linked together as Husband/Wife, Parent/Child,
Head Office/Branch, Company/Subsidiary etc.
• Any pairings as setup in the RELATION table can be input.
• Only one side needs to be input, as the corresponding relationship
is automatically defaulted.
46
SECTOR
• Mandatory field
• Used for Customer classification.
• Constitution of the customer is described such as individual,
corporate body, government etc
• Value defined in the table SECTOR
47
DEPT.ACCT.OFFICER
SOME IMPORTANT FIELDS
• Officer responsible for the customer.
• Enables to determine the departmental profit and loss from this
customer.
OTHER.OFFICER
• Must be at a higher level than the DEPT.ACCT.OFFICER.
48
INDUSTRY
SOME IMPORTANT FIELDS
• Identifies the industry where the customer belongs
• Codes are defined in the table INDUSTRY
• Assigned to each Customer record to identify their industry.
• Only main industry to be specified in case of Customers dealing in
more than one industry
• Maximum of 9999 codes
49
TARGET
SOME IMPORTANT FIELDS
• Defines the Target code for customers.
• Bank can assess the business routed through the targeted
customers.
• Meant for statistical purpose only.
• Range 1- 9999
• Stored in table TARGET
• Takes definition such as Prime Customer, High Net Worth etc.
50
POSTING.RESTRICTION
SOME IMPORTANT FIELDS
• Identifies any restrictions for entries on a Customer.
• Override required to accept any entry meeting the conditions.
• Optional input. No default value.
• Code stored in POSTING.RESTRICT table.
51
CONFID.TXT
SOME IMPORTANT FIELDS
• Masking the customer’s name for the sake of confidentiality
• Field controls the generation of the standard text in the
‘Ordering Customer’ fields of the SWIFT messages
• standard text is defined in the ORD record in DE.TRANSLATION.
52
EXAMPLES
53
CUSTOMER-BASIC DATA
Examples and Workshop exercises
54
CUSTOMER.DEFAULT
Examples and Workshop exercises
55
CUSTOMER
Examples and Workshop exercises
Values defaulted from
customer.default record on input of the
sector defined under 9900
56
CUSTOMER
Examples and Workshop exercises
57
DE.ADDRESS
58
FINAL WORD
Examples and Workshop exercises
We have covered
• CUSTOMER application with its important fields
• Related tables required to be set up before making a successful
input in CUSTOMER application
We shall now be able to create a record for a CUSTOMER with
all relevant data input, in our books.
59