Teller - TM - R15

T24 Teller
TECHMILL TRAINING
Teller – Product Overview
Till assigning to
Teller
Till Monitoring Tills

administration
Vault control
Head Teller
Till Transfer
authorisation Cash deposit and
withdrawal
Teller
Currency exchange
Local currency
transactions
Account transfer
Travelers cheque
Teller handling
Till transfer
Limits Foreign
currency Passbook Printing
Accounting transactions
Slide 2
TELLER Dependencies
 TELLER makes use of

 CUSTOMER
 ACCOUNT
 Core dependencies
 Delivery
 Accounting
 Limits
 TELLER also uses other Static tables
Slide 3
TELLER Dependencies – Product Related
 TELLER application is used to transfer money between Customer type

of accounts, internal accounts and PL Categories
 Customer type of accounts use 1000 to 9999 range of Category code
 Internal accounts use 10000 to 19999 range of Category codes

 Internal accounts are needed for handling Cash and Travelers cheques
 PL category codes use Category codes above 50000
Slide 4
TELLER Dependencies – Charges and Commissions
Charges and commissions for specific Teller operation

can be collected by linking through
TELLER.TRANSACTION
Also possible to accrue or amortise charges on

Daily or Monthly basis by using
ACCRUAL.FQU and ACCRUE.AMORT Fields.
AMORTISN.PERIOD Field used to indicate
the period of Accrual / Amortisation in months
or years. Of these, amortisation facility is relevant for
TELLER operations
Slide 5
TELLER Dependencies - Currency Related
COUNTRY
CURRENCY.PARAM
CURRENCY CURRENCY.MARKET
Buying and Selling exchange rates defaulted based on Currency market

chosen
Possible to choose Currency market for each side of a Teller transaction and
indicate it through TELLER.TRANSACTION
Debit transaction will default Buying rate and Credit transaction, Selling rate
Slide 6
Application Specific Parameters
Slide 7
TELLER - Parameter Tables
 Parameter tables for TELLER to be set-up :

 TELLER.DENOMINATION
 TELLER.PARAMETER
 ACCOUNT.CLASS
 TELLER.TRANSACTION
 TELLER.ID
 TELLER.PASSBOOK
 DEAL.SLIP.FORMAT
 APPL.GEN.CONDITION
 TT.GROUP.CONDITION
Slide 8
TELLER.DENOMINATION
 Description and currency wise value of denominations to be used in

Teller transactions defined here to be defaulted during transactions and
closing of Till
 If it is proposed to use the denomination facility in TELLER and TELLER.ID
applications, then, to be pre-defined here for each currency
 Denominations can be indicated for Cash as well as Travelers cheques
 DENOM.TYPE table is used to define various denomination types such

as Cash, Gift Cheques, Travelers Cheques, etc
 First 3 characters of Id to be a valid Currency

 Id can be like USD100, EURTC50
 Value can be indicated
 Values are represented as multiples or fraction of ONE unit and up to 3
decimals - 100.000 or 50.00 or 0.500
 Denominations defined in TELLER.DENOMINATION appear in

TELLER.ID
Slide 9
TELLER.PARAMETER
 Parameter file to define general rules and Category and Transaction

codes to be used for Teller System
 Rules can be set company wise and hence Id is Company code
 Vault information to be indicated in VAULT.ID and VAULT.DESC Fields

 Vault or central cash holding area is identified by a 4 digit number - 9999
 Mandatory to have at least one vault
 Possible to indicate more than one vault by multi-valuing these fields
Slide 10
TELLER.PARAMETER
 Exchange rate related choices
 System defaults buying and selling rates automatically. User may be

allowed to modify the rates or not by suitable choices made in RATE Field
1 Not allowed 2 Allowed but with overrides always
3 Allowed but with variance override
 Buying / Selling rate can be compared to Middle rate and profit or loss
posted to marketing exchange profit, if so opted in MKT.EXCH.METHOD
Field
If NONE is opted, both sides of transaction will have the same local
currency equivalent
If MIDDLE is opted, one side will have local currency equivalent at Middle
rate while the other side will have Buy or Sell rate equivalent
Profit / Loss posted to PL Category indicated in ACCOUNT.CLASS with
Ids MKTEXCHCR and MKTEXCHDR
Slide 11
TELLER.PARAMETER
 Category and Transaction codes to be used in various situations
 When there is a shortage or excess in Till balance during Closure of Till, it

could be transferred to internal account so that the Till balance tallies with
System. Category codes of such internal accounts are indicated in
SHORT.CATEGORY and OVER.CATEGORY Fields
 The transaction codes to be used for these situations are defined in

TRAN.CODE.SHORT and TRAN.CODE.OVER Fields
 Cash accounts to be handled by Teller defined in TRAN.CATEGORY multi

value Field
Category code for internal accounts for Cash and Travelers cheques
mentioned. System will maintain these internal accounts Currency and
Teller wise
If auto cash dispenser is proposed to be used, Category code for Cash to
be mentioned in AUTOCASH.CATEGORY Field also
Slide 12
TELLER.PARAMETER
 Category and Transaction codes to be used in various situations

 It is possible to specify a minimum rounding amount in CURRENCY file.
Then, while inputting transactions, TELLER.NET.AMOUNT is rounded to
this minimum amount by posting the difference to PL head indicated in
ROUNDING.CATEGORY Field
 Transaction codes used for crediting and debiting this PL head are indicated
in ROUND.TXN.CODE.CR and ROUND.TXN.CODE.DR Fields
 Splitting charges and tax from transaction amount

 It is possible to account Charges and taxes along with transaction amount
or split them and pass separate entries by opting for YES in
SPLIT.CHRG.ENTRIES Field
Slide 13
TELLER.PARAMETER
 Whenever a till balance goes to credit on authorisation of a Teller

transaction, option available to authorise the transaction or raise an
error message through TILL.BAL.AUTH.ERR Field
 If set to YES, an error message “CREDIT TILL CLOSING BALANCE” is
raised
 If set to NULL, system allows to authorise the transaction
 Denomination in multiple Internal account can be controlled by

setting CHECK.STOCK.AMT Field as Yes
 System will check for denomination for the amount mentioned in the
account
Slide 14
TELLER.TRANSACTION
 Defines default values and validations for each Teller transaction like
accounts to be used and currency markets for each leg, charges to be
taken etc
 Id is numeric. Up to 999 transaction records can be created
 While inputting a teller transaction, when this pre defined transaction

code is input, system automatically defaults all relevant values and
validates against rules set here
 Not possible to input transactions without using a pre defined
TELLER.TRANSACTION code
 Teller transactions consist of two sides – Debit and Credit. Rules for
each side are set separately. They could be defined in any sequence,
but System ensures that they are always contra
Slide 15
TELLER.TRANSACTION
 Transaction definition for Side 1

 TRANSACTION.CODE.1 Field to indicate a pre defined TRANSACTION
code
Debit / credit sign indicated in TRANSACTION file decides whether this
side is debit or credit. Value and Exposure dates also derived from here
 VALID.CURRENCIES.1 Field to indicate which currencies are allowed –
LOCAL, FOREIGN, or ANY
 VALID.ACCOUNTS.1 Field to indicate which type of accounts are allowed –
INTERNAL, PL, CUSTOMER or ANY
 CAT.DEPT.CODE.1 Field to indicate Category code of Internal account or
Profit & Loss
Category code can be mentioned alone or with DEPT.ACCT.OFFICER or
with NN99 – 10001 or 100011234 or 10001NN99
If this side is for debit to Customer account, then it should be left blank
Slide 16
TELLER.TRANSACTION
 Transaction definition for Side 1

 CURR.MKT.1 Field used to indicate the Currency market from which
exchange rates are to be defaulted to this leg. By default, System will use
Market 1
Rates from the indicated market will be used to derive local currency
equivalent which is the basis for calculating marketing exchange profit
 Similarly, rules defined for Side 2 in respective fields with suffix 2
 Markets have been defined for each leg for calculating marketing
exchange profit. Rate to be offered to Customer, deal rate, is derived
from market defined in DEAL.MARKET Field
 If left blank, market defined in CURR.MKT.1 is defaulted
 Market to be used for calculating exchange rate for Charges is

defaulted into CHARGE.MARKET Field from CURR.MKT.2
Slide 17
TELLER.TRANSACTION
 Charges / Commissions and Tax

 Charges and Tax to be collected for this transaction defined in
CHARGE.CODE multi value Field. Ids of FT.COMMISSION.TYPE and TAX
can be indicated here
 If Charges, commissions and Tax have to be split and accounted separately
in account, then SPLIT.CHRG.ENTRIES Field should be set to YES
 Charges for customer account to account transfer is flexible to be collected
from any customer account.
 Deal slips
 If deal slips are required to be printed, then PRINT.ADVICE Field to be set
as Yes and pre-defined Ids of DEAL.SLIP.FORMAT table to be indicated in
ADVICE.VERSION multi value Field
Slide 18
TELLER.TRANSACTION
 AUTO.DENOMINATE
 The user can choose whether the defaulting of the denomination should be
enabled at the transaction level or not. AUTO.DENOMINATE Field – with
allowable values, YES or NO
 When this field is set to YES, the system will support pre-filling the
denominations. When it is set to NO, the system will not default any
denominations. The user will be able to input the denomination
 DENOM.FILTER
 This feature allows the filtering of the denominations, based on the type of
transaction, and to restrict the denominations for a specific type of
transaction
Slide 19
TELLER.TRANSACTION
 Till to Till transfer transaction

 Transaction permitting Till to Till transfer including Vault to Till transfer is set
up with TELLER.TRANSFER Field indicating YES
 In such transaction, both accounts must be internal and without specifying
DEPT.ACCT.OFFICER code
 These transactions will allow the TELLER.ID Field to contain tellers other
than the current user and verify that the side 1 and side 2 currencies are the
same
 Customer account transfer

 If CUST.AC.TRANSFER Field is set to Yes, then both sides of a transaction
must be only customer accounts
 If the transfer is between different customers, then override has to be
approved
 Charges can be collected from any pre-defined customer account.
Slide 20
TELLER.TRANSACTION
 Signature verification
 It is possible to scan and store Customers’ signatures through

IMAGE.MANAGEMENT application
 When the Customer’s account is debited, then on input of account number,

signature can be displayed by using context sensitive enquiry
 If VERIFY.SIGNATURE is set as YES, and if the signature is not displayed

due to absence of the same, due approval of override is required
 If set as NO, no such override is generated
Slide 21
Workshop – 1
 Use Admin Menu > Retail Administration > Teller > Teller Transaction
 Create a new transaction in TELLER.TRANSACTION with the following

features:
 Transaction is to buy Foreign currency and pay local currency cash
 Use Transaction codes 3 and 53 for Bank notes Purchase and sale
respectively
 Category code for Cash is 10001
 FT.COMMISSION.TYPE of CASHWDWL to be used. Accounting entries
for charges to be separate from debit entry for buying foreign currency
 Teller transfer is not required
Slide 22
Workshop – 1 Solution
Slide 23
TELLER.ID
 This application is used to open tills, assign users to tills and close and
balance tills
 During implementation, this is required to be created for Vault(s)
 Subsequently, whenever a Till is allotted to a User, suitable records are
required to be created
 Id is Till number. For creating records for Vaults, Ids indicated in

TELLER.PARAMETER are to be used
 For records created for Vault, STATUS and USER Field should be left
blank
 Vaults cannot be opened or closed, hence transfers can take place to and
from the vault regardless of status
 For other tills, a user can perform transactions only when the till is open
and user is assigned to that till
Slide 24
TELLER.ID
 The field STOCK.UPDATE is used to update cash denominations

during till closure into TT.STOCK.CONTROL.The value of the filed can
be updated as NULL or YES
 Limits can be set for each tills by specific currency.Incase there is a

breach of the threshold the teller is warned by a override.
Slide 25
Preferential Grouping – APPL.GEN.CONDITION
 APPL.GEN.CONDITION with Id as TELLER can be used to form

groups for setting preferential conditions. Grouping could be based on
any field defined in STANDARD.SELECTION record for the application
or a local subroutine name
 Fields defined in STANDARD.SELECTION could be from the same
application or from any other application, with due links marked
 If RESIDENCE Field is defined in STANDARD.SELECTION for

TELLER as System Type ‘J’ and joined to CUSTOMER application as
CUSTOMER>CUSTOMER>RESIDENCE, we can form groups of
people based on residence:
 CONTRACT.GRP called USRES with RESIDENCE EQ US
 CONTRACT.GRP called OTHRES with RESIDENCE NE US
Slide 26
Preferential Grouping – TT.GROUP.CONDITION
 TT.GROUP.CONDITION can be set up to create default conditions

regarding charges to be taken and rate spread
 Id is the valid group created in APPL.GEN.CONDITION (example:

USRES) or customer Number indicated as C-NNNN
 Rate spread is indicated as % of preferential Rate on Customer Spread

for a Currency exchange (0, 50, 100 etc)
 Where groups of customers are given preferential Commission rates,

CHG.PERCENT Field is used to indicate what Percentage of the
Standard Commission should be applied for an indicated Commission
type
 Alternately, fixed amounts could be indicated for different charge currencies
using CHG.CCY and CHG.AMT Fields
Slide 27
Workshop - 2
 Use Command line and access TT.GROUP.CONDITION
 Set the following preferential treatment for one of your select customers
Whenever CASHWDWL commission is taken, then only 25% of the
normal amount of commission should be taken from this customer
Slide 28
Slide 29
Passbook for Savings Account
 It is possible to issue passbooks instead of statements to accounts duly

defined in ACCOUNT.CLASS as SAVINGS
 For those accounts, PASSBOOK Field should be set as YES in the

respective Accounts
 TELLER.PASSBOOK application to be set up for designing the

passbook and ATTRIBUTE Field to link printer attribute
 PASSBOOK.DEVICE Field of TELLER.ID application to indicate which

printer device is connected to this Teller
 Id of PRINTER.ID application to be indicated here
 Passbooks are updated by Teller using Function Verify in

TELLER.PASSBOOK.UPDATE application
Slide 30
TELLER.PASSBOOK
 Format for passbook can be defined in TELLER.PASSBOOK
 Details of what to be printed when:

 A new passbook is issued
like Customer's name & address
 A new page is printed
like balance brought forward
 An entry is printed
like Transaction amount, debit/credit column, balance etc
 The last line of the page is printed
like balance carried forward
 The last page of the passbook is printed
like New book issued message
Slide 31
TELLER.PASSBOOK
 Data printed can be any field from the following files:

 ACCOUNT, CUSTOMER, COMPANY, TRANSACTION, CURRENCY,
ACCOUNT.STATEMENT, STMT.ENTRY, CATEGORY,
DEPT.ACCT.OFFICER
 Any free format text or one of the following:

 CREDIT +ve amount from the entry
 DEBIT -ve amount from the entry
 BALANCE the new account balance
 TODAY today's date
 TELLER.ID the current teller Id
Slide 32
Quiz - 1
1) A Bank wants to issue passbooks for a group of current accounts

Which table should be used to enable this functionality and what should
be the Id of that table?
Ans : ACCOUNT.CLASS for a record Id called Savings. In that record
Category code 1001 should be included to enable this functionality
2) What is the purpose of defining SHORT.CATEGORY codes in

TELLER.PARAMETER?
Ans : To account for any cash shortages in tills
3) What is the use of MULTI.TILLS field in TELLER.PARAMETER?

Ans: To link more than one till to a user
4) Where can we opt for filtering denomination?

Ans: DENOM.FILTER field in TELLER.TRANSACTION table
Slide 33
Quiz - 1
5) What should be the status of record for VAULT in TELLER.ID – Open

or Closed?
Ans : It should be blank - neither open nor closed
6) What is the purpose of TELLER.PASSBOOK table?

Ans : To define formats for passbook printing
7) How is a till allotted to a User?

Ans: Using USER field in TELLER.ID application
8) What is the maximum number of tills that could be allotted to Users in

a Company?
Ans: 9998 as at least one till is needed to indicate Vault
Slide 34
TELLER - Build Sequence
1. ACCOUNT.CLASS Mandatory *
(MKTEXCHCR, MKTEXCHDR,SAVINGS) Optional
2. TELLER.DENOMINATION
3. TELLER.PARAMETER *
4. DEAL.SLIP.FORMAT
5. TELLER.TRANSACTION * DEAL.SLIP.FORMAT
Slide 35
TELLER - Build Sequence
Mandatory *
6. TELLER.PASSBOOK Optional
7. TELLER.ID * TELLER.PARAMETER
8. APPL.GEN.CONDITION
9. TT.GROUP.CONDITION APPL.GEN.CONDITION
Slide 36
TELLER – Product Features
Slide 37
Product Features
 TELLER Application is designed to provide retail cash operation
 Can also be used for

 posting entries between the tills
 handling Travellers cheques and Cheques sent for collection
 Can handle any type of transfer of money between Customer accounts,

Internal accounts and PL Heads
 Operations of Head Teller as well as other Tellers covered under

TELLER application
 TELLER.ID application used to open and close Tills
 All other Teller operations handled through TELLER
 Passbook updated through TELLER.PASSBOOK.UPDATE
Slide 38
Creating a new Till
 Creation of a Till is the first step necessary to allow Teller operations
 TELLER.ID application used to open and close Tills

 Id is the Till number that is proposed to be created
 4 digit number for vault. Defined in TELLER.PARAMETER
 STATUS should be set as OPEN while allotting a new Till and CLOSE
during Till closure
 USER Field indicates USER.ID of the User of the till
 Opening and Closing balances maintained by the System

 Balance shown with negative sign in line with Accounting rules – Debit what
comes in and Credit what goes out
Slide 39
Workshop - 3
 Use User Menu > Retail Operations > Teller > Head Teller Operations
> Till Administration > Create New Till
 Act like a Head Teller
 Create a new Till for yourself by using your User Id
 Use Till number as suggested by Trainer
Slide 40
Slide 41
Inputting Teller Transactions
 Each and every type of transaction is suitably pre-defined in

TELLER.TRANSACTION and versions created to guide the end user to
fill in only minimal input
 For accepting local currency cash for credit to Customer’s account, it is

enough if the end user mentions only the Customer’s account number and
amount of cash paid
 By suitable definition of TELLER.TRANSACTION, System is designed to

produce the debit side of transaction as Debit Cash and debit Internal
account automatically (say USD100011234)
 Credit amount is automatically filled by System depending on whether any

charges are involved in the transaction
Slide 42
Local Currency Transactions
 Cash amount
 Amount deposited or withdrawn by customer
 Currency set as No input field in version as USD is defaulted as LCY
 Account
 Credit Account into which cash deposited or Debit Account from where
withdrawn
 TELLER.TRANSACTION record set to allow only Local currency accounts
for these transactions
 Cheque number
 Cash withdrawal is normally permitted with a cheque number
 It is also possible to withdraw cash without giving a cheque number
 Denomination
 Acceptable denomination for various currencies have been set
 Actual receipt/payment to be indicated to match with amount
Slide 43
Workshop - 4
 Use User Menu > Retail Operations > Teller > Teller Operations >
Teller cash > Cash deposit Local
 Act as a Teller and accept USD 40,000 cash deposit into your customer’s
USD account in the denomination 200 USD 100 notes and 400 USD 50
notes
 Commit the record
Teller cash > Cash withdrawal Local
 Allow withdrawal of USD 20,000 from the same account
 Indicate cheque number as 456789. Pay amount in USD 50 denomination
 Accept overrides, if any, and commit the record. Get the records authorised
> Enquiries > Account Balances
 View balance of the same account. Drill down to look at list of transactions
Slide 44
Slide 45
Slide 46
Slide 47
Workshop - 4
> Till Administration> Create New Till
 Use the following Teller limit set up (Limit tab)
1. TILL.LIMIT : YES
2. LIMIT.CATEGORY : 10001
3. EXCLUDE.CCY : JPY
4. GLOBAL.FCY.EQV.LIM :10,000
5. LOCAL.CCY.LIMIT : 20,000
Teller cash > Cash deposit Local
 Act as a Teller and accept USD 21,000 cash deposit into your customer’s
USD account.
Slide 48
Slide 49
Handling Local Currency in FCY Accounts
 Account
 TELLER.TRANSACTION record set to allow Local and Foreign currency
accounts for these transactions
 Narration to record further details to appear in accounting entry and
Customer statements
 Exchange rate
 Defaults from currency table if not input
 Buying or selling rates suitably defaulted
 Middle rate used for marketing profit / loss calculation
Booked as marketing exchange profit or loss
 Waiving charges or charges collection

 YES waives predefined charges and NO collects charges
However, it is still possible to collect charges only for transactions beyond
a threshold amount by suitably defining in FT.COMMISSION.TYPE
Slide 50
Role Based Home Page on Teller
 Teller home page has custom set of menus / enquiries

 Front-end solution for users to process Teller Transactions
 Once a home page for Teller is invoked multiple screens are displayed
 Enables a User / Head Teller Supervisor to carry out his day to day work
related to Remittances
 Composite screen for Teller is divided into several sections

 Processing of Cash deposit , withdrawal, currency exchange, account
transfers, Travellers cheque etc.
 Menus available for Teller, Head Teller, task specific
 Components of Teller Home Page in the form of tabs, for easy navigation
Slide 51
Role Based Home Page for Cheques For Collection
 Two separate homepages for Cheques Collection Officer and Cheques

collection Supervisor
 Menu/Enquiries make the following available to the officer/Supervisor

 Customer search and drilldown to Customer Overview & Single Customer
View
 Enquiry to mark the record status as RETURNED/CLEARED
 Cheque change functionality to change the value date/exposure
date/cheque status for a set of cheque collection records
 Reports consisting of cheques collection enquiries
 Enquiries make the following available to the Supervisor

 Process workflow for cheque deposit in the Supervisor Home Page
 Authorisation/Deletion enquiries in Supervisor home page including Cheque
collection enquiry, cheque change functionality, Search customer enquiry
and Reports
Slide 52
Handling FCY Transactions
 Possible to handle two different foreign currencies also

 Set up for Teller transaction should allow foreign currency for debit and
credit sides
 Accept GBP amount and credit EURO account directly while USD is local
currency
Amounts to Buying GBP and selling EURO
 T24 works out cross currency rate for the transaction automatically and
defaults
 While transferring to accounts, possible to have future value date for

customer accounts
 Value date is used for interest calculation
Slide 53
Workshop - 5
Teller Cash > Cash deposit Foreign
 Accept a deposit of GBP 15,000 in GBP 50 denomination into your
Corporate Customer’s USD current account. Waive charges
 Accept GBP 10,000 in GBP 50 denomination, into your customer’s EUR
account. Do not waive charges
Teller Cash > Cash withdrawal Foreign
 Allow withdrawal of GBP 10,000 in GBP 50 denomination from the above
USD current account. Input Cheque No as 777777. Do not waive charges
 Validate and view System defaulted exchange rate and credit/debit

amounts. Commit and get the records authorised
Slide 54
Slide 55
Slide 56
Slide 57
Currency Exchange
 Versions for Foreign currency buying and selling designed to enable

minimum input at end user level
 Currency sold and amount to be indicated for FCY sale transactions
 Currency bought and amount to be indicated for FCY bought

transactions
 Exchange rate defaulted by System, if not manually input
 If WAIVE CHARGE is set as NO, charges are collected for FCY sale
transactions. Charges are waived for bought transactions
Slide 58
Workshop - 6
Enquiries > Cash Position by Till
 View your cash position
Currency Exchange > Exchange rate
 View exchange rate for GBP currency
Currency Exchange > Buy FCY against LCY cash
 Buy GBP 2,000 at the rate of 2.00 and commit
 Use denominations - GBP 50 and USD 100
 Through context sensitive enquiry, view details of accounting entries at

unauthorised stage. Observe accounting entry prepared for marketing
exchange loss. Get the record authorised
Slide 59
Slide 60
Slide 61
Slide 62
Slide 63
Workshop - 7
Currency Exchange > Sell FCY against LCY Cash
 Sell GBP 500 at the rate of 2.00 and commit
 Use denominations - GBP 50 and USD100
 Through context sensitive enquiry, view details of accounting entries at

unauthorised stage and observe accounting entry prepared for
marketing exchange profit
 Get the record authorised
 View your cash position
Slide 64
Slide 65
Slide 66
Till to Till Transfer
 TELLER.TRANSACTION permitting Till to Till transfer to be used

 Only in such case, System allows two different Ids of Teller to be indicated
in TELLER application
 TELLER.ID.2 and TO TELLER .ID.1Fields to indicate the Ids of Teller

created earlier. For Vault, Id is 9999
 In case of local currency transfer, only amount to be transferred to be

indicated
 In case of foreign currency transfer, currency also to be indicated
Slide 67
Workshop - 8
 Use User Menu > Retail Operations > Teller > Teller Operations > Till
Transfer > LCY Till Transfer
 Transfer USD 50,000 to another Till in denominations of USD 100(if till don't
have enough balance of USD 50,000 this transaction made after depositing
USD 100000 for existing till)
Transfer > Till to Vault
 Transfer entire GBP holding to Vault in denominations of GBP 50
 Act as Head Teller and authorise Till transfer made by another teller
Slide 68
Workshop - 8 Solution
Slide 69
Slide 70
Slide 71
Till Closure
 At the end of the day, after transferring cash with Tellers to Vault, the
tills are closed. Some banks may permit petty cash to be retained with
the Teller
 TELLER.ID application used to indicate that the till is now closed

 Cash retained with Teller to be indicated, currency wise
 Difference, if any, between cash on hand and what it should be, is indicated
by System
 If approved, the difference amount is transferred to an Internal account as
Cash overage or Cash shortage
 Next day, till could be again allotted to the same Teller through Head
Teller operations
Slide 72
Workshop – 9
 View your Till cash position
Transfer > Till to vault
 Transfer entire USD balance to Vault. Get the transfer authorised
Administration > Initiate Till Closure
 Close your Till by indicating cash with you
 Get the closure authorised
> Enquiries > Cash Position by Currency
 View overall till balances in all currencies
Slide 73
Slide 74
Slide 75
Slide 76
Slide 77
Workshop – 10
> Till Administration > Reopen Teller
 Act like a Head Teller and reopen your till again
Teller Cash > Cash Deposit Local - Foreign
 Accept USD 30,000 into your customer’s GBP account in in USD 100
denomination. Waive charges
 Get the record authorised
Slide 78
Slide 79
Slide 80
Workshop – 11
Teller cash > Cash withdrawal Local - Foreign
 Allow withdrawal of USD 15,000 from your customer’s GBP account. Do
not waive charges
 Input 121212 as cheque number. Do not waive charges. Pay in USD 100
denomination. Commit the records
 Allow withdrawal of USD 15,000 from your customer’s GBP account for
whom preferential condition was set in Workshop 2
 Input 131313 as cheque number. Do not waive charges
 Pay in USD 100 denomination
 Commit the records. Get the records authorised
 Observe the charges collected in both transactions. System recovered

less charges for preferential customer
Slide 81
Slide 82
Slide 83
TELLER – Other facilities
 Multi Tills set-up
 TELLER.PARAMETER to be set up to allow Multi Tills and to indicate

maximum number of tills for a User using MULTI.TILLS and MAX.TILLS
Fields
 TELLER.ID to be set up for the Main till and to indicate Ids of linked tills in
LINKED.TILLS Multi Field
All the linked tills should belong to the same User
System opens linked tills automatically whenever the Main till is opened
Closing of Tills to be done individually
TILL.TFR.ONLY Field can be set to Yes if it is intended to use this
TELLER.ID only for Till to Till transfer
 At transaction level, the till used to log into TELLER application is

automatically defaulted unless changed at application level
Slide 84
 Multi Tills (Cash bags)
 This feature enables a single user to have multiple Tills - a Master till and
other linked tills
 Multi tills act as an intermediary between the Vault and individual tills
 At the start of day, cash transferred from Vault to Master Till
 Whenever there is a shortage of cash in linked tills, cash can be transferred

from Master Till to the linked tills and if the till cash balance exceeds
permissible limits, then can be transferred to the Master Till, instead of
operating Vault every time
 At the end of day, all tills can be closed and cash transferred back to Vault
Slide 85
 Multi value transactions
 Side – 1 of a transaction input through TELLER application has the facility

to multi value ACCOUNT.1, AMOUNT.LOCAL.1, AMOUNT.FCY.1 and
NARRATIVE.1 Fields
 CUSTOMER.1 and CURRENCY.1 Fields are however single value fields

only
Hence possible to effect multiple credits / debits by using Side – 1 as long
as the Currency and Customer are same
 Possible to design suitable versions to accept

credits to / debits from multiple accounts of the same customer as long as
they are in the same currency
debit / credit to several internal accounts in same currency
 First account defaulted for Charges
Slide 86
Travellers Cheques Handling
Slide 87
Travelers Cheques - Features
 Travelers cheques processing could happen under two situations:

 Client issuer of Travelers cheques
Client required to record the amount / denomination / serial numbers of
Travelers Cheques issued to counterparts like Agents as well as own
Customers
 Client is not the issuer but uses Travelers cheques issued by others
 Handling Travelers cheques is similar to handling operations of other

internal accounts
 Certain points to be taken care of while designing and implementation of
handling Travelers cheques
Slide 88
Travelers Cheques
 Separate CATEGORY codes to be created for Travelers cheques stock

control and Travelers cheques contra accounts
 Advisable to create separate set of codes for each issuer to keep track
 TELLER.TRANSACTION records to be created for procurement, sale

and till transfer of Travelers cheques
 Suitable CURRENCY.MARKET, TRANSACTION records to be created and
used
 Advisable to create separate set of TRANSACTION codes for each issuer
as narration in statements may differ indicating Issuer name
 TELLER.DENOMINATION records to be created, Currency and

denomination wise if required in TELLER application
Slide 89
Travelers Cheques
 If separate rates are needed for sale of Travelers cheques, new record
to be created in CURRENCY.MARKET
 If an exclusive market is created, quotes for this market to be created in

CURRENCY records for respective currencies of Travelers cheques
 Separate versions available for procuring Travelers cheques stock.

Done through Head Teller operations
 Travelers cheque sales and Issuer wise Till Transfer possible
 Internal accounts can be defaulted if required through separate

versions
Slide 90
Travelers Cheques – Internal Accounts
 Internal Accounts for Stock control

 Necessary to open Internal accounts in all currencies of Travelers Cheques,
Issuer wise, for Travelers cheques stock control using Vault Id
 STOCK.CONTROL.TYPE Field in such Internal account has 3 options –
NULL, DENOM and SERIAL
If DENOM is indicated, then Teller has to indicate denomination while
inputting transactions
If SERIAL is indicated, then Serial number as well as denomination
become mandatory while inputting transactions
 SERIAL.NO.FORMAT Field mandatory if SERIAL is chosen
Defines format of serial number of a particular stock. Serial number input
on a TELLER transaction is validated against this field
Combination of Alphabetic, numeric, alpha numeric and mask
Slide 91
Travelers Cheques – Internal Accounts
 System maintains internal file TT.STOCK.CONTROL with details of

available TC stock, Denomination and Serial numbers
 Record Id is relevant internal account number
 Internal Accounts for Travelers Cheques contra

 Necessary to open Internal accounts in currency of Travelers Cheques,
Issuer wise, for Travelers cheques stock control using Vault Id
According to accounting requirements, either single contra account for all
Issuers or different account for each issuer can be opened
Advised to maintain Issuer specific contra accounts as this would help in
proper reporting of liabilities
 STOCK.CONTROL.TYPE and SERIAL.NO.FORMAT Fields left blank in this
case
Slide 92
Travelers Cheques
 The Teller module handles processing of both Issue and Purchase of

Traveller’s cheques (TC)
 Stock of TC is indicated as balance in an Internal Account

 In Model Bank category 10905 is used for issue, 15905 for contra and
10090 for Purchase
 Field STOCK.CONTROL.TYPE is set to SERIAL and SERIAL.NO.FORMAT
is defined as AA.NNN.NNN.NNN in Internal account EUR109059999
 Receipt of TC stock and transfer from vault to till through Head Teller
operations . Actual issue of TC to Customer through Teller operations
 TCs issued by any bank can be purchased. There is no control for

serial numbers during purchase
Slide 93
Travelers Cheques – Recording Receipt of Stock
 To record stock of Travellers Cheques Head Teller operations used
 Vault Id 9999 to be used in Internal accounts for TC Stock and Contra

to record receipt of stock at Vault
 When stock is transferred to another branch, our stock to be reduced.

 . Vault Id used in both Internal accounts
 When stock is transferred from Vault to Till, stock at Vault to be

reduced and stock at Till increased. Contra is not affected
 Vault Id and Till Id to be used in Internal account for TC stock alone
Slide 94
Workshop – 12
> Travelers Cheque > Teller Internal Account Menu >
Create/Amend Internal Account
 Open an Internal account in EUR for Vault Id 9999 for Category code
10905
 Choose SERIAL option for these Travelers cheques and indicate the serial
number format as XX.NNN.NNN.NNN. Get the record authorized
Slide 95
Slide 96
Workshop - 13
> Travelers Cheque > Receipt of TC Stock
 Record receipt of TC for EUR 50,000 in the following denomination
 400 Nos. of EUR TC 100 , 200 Nos. of EUR TC 50
 Use Serial Nos.OH.100.000.001 to OH.100.000.400 for EUR TC 100 and
OH.100.000.001 to OH.100.000.200 for EUR TC 50
 Get the record authorized
> Travelers Cheque > TC Stock Balance
 View the TC stock balance in EUR currency
Slide 97
Slide 98
Slide 99
Workshop - 14
> Travelers Cheque > Transfer of Stock – Other Branches
 Transfer TC stock of EUR 25,000 to Branch 1 in the following denomination
 200 Nos. of EUR TC 100 denomination – Serial No.OH.100.000.001 to
OH.100.000.200
 100 Nos. of EUR TC 50 denomination – Serial No.OH.100.000.001 TO
OH.100.000.100
 Get the record authorized
Slide 100
Slide 101
Workshop - 15
> Travelers Cheque > Teller Internal Account Menu > Create/Amend
Internal Account
 Open an Internal account in EUR for your Till for Category code 10905
 Check ‘Serial’ in STOCK.TYPE Field and mention serial number format as
XX.NNN.NNN.NNN
Travelers Cheque Admin > TC Tfr from Vault to Till - Same Branch
 Transfer stock of EUR 12,500 to your Till. Use 100 Nos. of EUR TC 100
and 50 Nos. of EUR TC 50 denomination. Indicate serial numbers in the
format XX.NNN.NNN.NNN (like OH.100.000.201 to OH.100.000.300)
Travelers Cheques Admin > TC Stock Balance
Slide 102
Slide 103
Slide 104
Slide 105
Travelers Cheques - Selling
 Travellers cheques can be sold against cash or against debit to

Customer’s account in any currency
 Internal account for the Till for TC Stock to be used
 Generally, at the end of every day, or at agreed periodic intervals,

funds are remitted to the Travellers cheque Issuer for the sales effected
 NOSTRO Funding for TC Issue to be used
 Internal account for TC contra for the Vault will be debited and funds
remitted as instructed
Slide 106
Workshop - 16
Travelers Cheques > Sell TC’s against cash
 Sell TC for EUR 5,000 for cash in EUR TC 100 denomination
 Use rate 1.42 and waive charges. Use USD 100 denomination for cash
Travelers Cheques > Sell TC’s against account
 Sell TC for EUR 2,500 against your Customer’s USD account
 Use EUR TC 50 denomination. Do not waive charges
 Before authorisation, using context sensitive enquiries, look at the

details of accounting entries prepared. Get the records authorised
Travelers Cheques Admin > TC Stock Balance
Slide 107
Slide 108
Slide 109
Slide 110
Workshop - 17
Enquiries > Till TC Issue Entries Today
 View Travelers cheques sold today at your Till in EUR
Travelers Cheque Admin> Nostro Funding for TC Issue
 Remit funds to Amex through their Nostro account 23817 for the value of
TC cheques sold today at your Till in EUR
 Through context sensitive enquiries, look at the accounting entries
Slide 111
Slide 112
Slide 113
Travelers Cheques - Buying
 Travellers cheques of other issuers can be bought against cash or by

credit to Customer’s account in any currency
 Advisable to open Internal accounts for each Issuer to keep individual

issuer wise track of TCs bought
 Pre defined Category Code of 10090 for TC bought
 Internal account for the Till for TC bought used
Slide 114
Workshop - 18
Travelers Cheque > Buy TC’s against Cash
 Buy TC for GBP 2,000 for cash. Use USD 100 denomination. Use rate 1.90
Travelers Cheques > Buy TC’s against Account
 Buy TC for EUR 2,500 against your Customer’s GBP account. Use
defaulted rate
 Before authorisation, using context sensitive enquiries, look at the

details of accounting entries prepared
 Get the records authorised
Travelers Cheque Admin > TC Stock balance
 View the TC stock available
Slide 115
Slide 116
Slide 117
Slide 118
TELLER - Other Features
Slide 119
Product Features - Accounting
 Accounting entries passed through TELLER are STMT.ENTRY and

CATEG.ENTRY for Debit/Credit to Accounts and PL heads
respectively
 PL heads include Interest, Charges and Commission
 Possible to split entries for Charges and Tax from Debit / Credit transaction
amount by suitable choice in TELLER.TRANSACTION
 Transaction codes specified through TELLER.TRANSACTION
Also uses transaction codes defined for FT.COMMISSION.TYPE
When Transaction codes are marked for DATA.CAPTURE usage, it is
possible to indicate Exposure date rules for Credit entries and Value date
rules for all entries
When these Transaction codes are used in TELLER, then these rules are
automatically made applicable here also, unless manually changed
Slide 120
Product Features - Delivery
 Deal slips can be printed for any Teller Transaction
 Ids of DEAL.SLIP.FORMAT to be printed for a transaction are attached

through ADVICE.VERSION multi value Field in
TELLER.TRANSACTION
 Deal slips are generated when the Teller hits the PRT.HOTKEY defined
in TERMINAL record
 If the Teller omits this then an override is generated
 TELLER.PASSBOOK.UPDATE application used with Verify function to

print Passbooks for Savings accounts defined in ACCOUNT.CLASS
and marked for Pass book printing in ACCOUNT application
Slide 121
System Maintained Files
 System maintains Internal file TT.STOCK.CONTROL with details of

available Cash, denomination and the quantity of currencies
 Maintained quantity wise for each Teller
 Internal Accounts for Cash

 As soon as a Teller opens his till, an Internal account will be created
 Id as Currency Code-Category Code – Teller Id
Slide 122
TT.STOCK.CONTROL
Slide 123
Standard Enquiries
 Standard enquiries available are:

 Cash position by Till
 Cash position by Currency
 Cash position by denomination
 TC Stock position by Currency
 Till cash entries today
 Till TC Issue entries today
 Till TC Buy entries today
 Account balances
 Reversed Teller Transactions
Slide 124
TELLER - Dependency Diagram
CUSTOMER
ACCOUNT TELLER.PASSBOOK
FT.COMMISSION.TYPE
CATEGORY DEAL.SLIP.FORMAT
FT.CHARGE.TYPE
CURRENCY
APPL.GEN.CONDITION
LIMIT
TT.GROUP.CONDITION
COLLATERAL
TELLER
TELLER.DENOMINATION
TELLER.PARAMETER
ACCOUNT.CLASS
TELLER.TRANSACTION TT.STOCK.CONTROL
TELLER.ID
Slide 125
Cheques for Collection
Slide 126
CC – Product Overview
Direct clearing ONLINE. ACTUAL.BAL

credit to
Customer
account AVAILABLE.DATE
Local AV.AUTH.CR.MVMT
clearing AVAILABLE.BAL
Cheques
for
collection Indirect clearing
credit through
Collection Suspense
Internal account
Account
Outstation
cheques Indirect clearing AVAILABLE.DATE
credit through AV.AUTH.CR.MVMT
Internal account AVAILABLE.BAL
Slide 127
CC - Parameter Tables
 Cheques for collection related tables to be set up
 ACCOUNT.PARAMETER
 CQ.PARAMETER
 BC.SORT.CODE
Slide 128
ACCOUNT.PARAMETER
 If Cheque issue management and collection operations are desired,

then the following are to be set up
 CHEQUE.REGISTER Field to be set to Yes
 RETURN.TXNS and RETURN.SUSP.CAT Fields to indicate the transaction
code and suspense category code to be used while returning cheques
 If transaction codes indicated in ACCOUNT.PARAMETER /

CQ.PARAMETER for collection are used, System triggers action to
treat the cheques as those sent for collection
 Cleared balance of Customer account will NOT be updated automatically on
the Credit value date
 System waits till the fate of the cheque as collected or returned is expressly
indicated to take suitable action
Slide 129
ACCOUNT.PARAMETER
 Fields that could be set up optionally for collecting cheques are

 CHQ.DEP.TXN and DEF.COLL.SUSP to indicate the transaction code and
Suspense Category code to be used for crediting Internal suspense account
while cheques are deposited
 CHQ.COL.TXN and CHQ.RET.TXN to indicate transaction codes to be
used for indicating collection and return respectively
 DEF.RET.SUSP to indicate Category code to be used when cheque sent for
collection is returned
 If these are not provided here, then Transaction codes used in similar
fields in CQ.PARAMETER are checked to decide whether Collection
processing is to be triggered
Slide 130
CQ.PARAMETER
 This table is used to define transaction codes for different stages in

Cheques collection – Deposit, Collection and return
 Also used to define suspense categories for indirect clearing
 Only one record for entire System wide usage

 CHEQUE.REGISTER Field to be set as Yes to indicate cheque
management system is needed
 CHQ.DEP.TXN and DEF.COLL.SUSP to indicate the transaction code and
Suspense Category code to be used for crediting Internal suspense account
while cheques are deposited and sent for collection
 Multi value fields. If Suspense Category code is indicated, System will
process it as Indirect clearing method and credit to this Suspense account
instead of Customer account
Slide 131
CQ.PARAMETER
 When the transaction code specified in CHQ.DEP.TXN Field is used in

FUNDS.TRANSFER / TELLER / DATA.CAPTURE applications,
System will automatically create a record in CHEQUE.COLLECTION
with status of 'DEPOSITED'
 If DEF.COLL.SUSP Field is also filled up for this CHQ.DEP.TXN Field,

then, instead of crediting the proceeds to Customer account indicated,
it will be deposited to the suspense account whose Category code is
indicated here
 CHQ.COL.TXN and CHQ.RET.TXN Fields to indicate transaction

codes to be used for indicating collection and return respectively
 DEF.RET.SUSP Field to indicate Category code to be used when cheque
sent for collection is returned
Slide 132
CQ.PARAMETER
 When CHEQUE.COLLECTION record status is changed to

'RETURNED', transaction code set in CHQ.RET.TXN Field is used
automatically
 Forward entries created on client account are deleted
 Real entries raised to credit the return suspense with the cheque amount
and debit the collection suspense account with the cheque amount
 Entries raised for any charges and/or tax specified in
CHEQUE.COLLECTION record
 If TELLER.ID Field is indicated as "Y", then appropriate Id of the Teller

will be used while building the collection suspense internal account
number in CHEQUE.COLLECTION
 If set as No, default Id of '0001‘ will be used for the Internal a/c
Slide 133
CQ.PARAMETER
 AUTO.CLEAR Field could be set as Yes to trigger automatic action to

set CHEQUE.COLLECTION records as CLEARED status during COB
 When setup as 'Y', during COB, the system will search for
CHEQUE.CHANGE application record with Id as AUTO.CLEAR and
perform the select defined in that record
 Otherwise, it will select all the CHEQUE.COLLECTION records whose
ORIG.VALUE.DATE is less than or equal to TODAY and CHQ.STATUS not
equal to CLEARED and RETURNED. It will automatically action all these
selected records to CLEARED status
 If automatic action is not desired, then this field could be set as No or

left blank
Slide 134
CQ.PARAMETER
 Records in CHEQUE.COLLECTION with status as "CLEARED" or

"RETURNED" will be moved to history file at the end of the number of
days defined in CC.POST.HIST Field
 Maximum of 99 days can be indicated
 CHEQUE.NUM.LEN Field can be used to define the standard length of

cheque number. Leading zeros will be automatically prefixed to the
cheque number if the length of the cheque number input is less than
the one defined here
 If this field is left blank, then any leading zeros will be trimmed
Slide 135
BC.SORT.CODE
 This application contains details of bank sort codes used in clearing

system and is used to define value and exposure date period for
different types of cheques for collection
 VALUE.DATE.PRD and EXP.DATE.PRD Fields used for this purpose
 Period can be indicated as Y to default System date, - / + nnC, or - / + nnW
to indicate Calendar or Working days
+03W will mean that the default value date is 3 working days forward from
the Run Date
+01C + 02W will mean that the default value date is 1 calendar day + 2
working days forward from the Run date
 Category codes for Suspense accounts can also be indicated Sort code
wise using CHQS.COLL.SUSP and CHQS.RET.SUSP Fields
Slide 136
BC.SORT.CODE
 EXP.KEY Field can be used to indicate a predefined record in

EXPOSURE.CONDITIONS file
 EXPOSURE.CONDITIONS can be set up to define exposure ladder rules
From the booking date, the first USD 2,000 to have exposure date after 1
day, the next 10% after 2 days, and the rest after 5 business days
 EXP.CCY can have a value of any Currency or REST
 EXP.TYPE can have either AMOUNT, PERCENTAGE or REST
EXP.CCY – USD; EXP.TYPE – AMOUNT; EXP.AMT - 2000; EXP.PRD -
1D
EXP.TYPE – PERCENTAGE; EXP.PERC – 10; EXP.PRD - 2D
EXP.TYPE REST; EXP.PRD - 5B
 Pre-defined Customer code can be optionally indicated for the financial

institution / clearing house in CUSTOMER.NO Field
Slide 137
CC - Build Sequence
Mandatory *
1. ACCOUNT.PARAMETER * Optional
2. CQ.PARAMETER *
3. BC.SORT.CODE * EXPOSURE.CONDITIONS
Slide 138
CC – Product Features
Slide 139
Cheque Collection - Features
 Cheque collection facility can be used for acceptance of Local clearing /

Outstation Cheques, batching them, if needed and marking collection /
returns
 Cheque collection processing could be done in two methods – Direct

and Indirect
 Crediting Customer account directly, but not allowing withdrawal till cleared.
Online Actual Balance updated but NOT Online Cleared Balance or
Working balance
 Crediting an Internal account initially till fate is known and crediting
Customer account only if cleared
 Under both methods, System updates AVAILABLE.DATE,

AV.AUTH.CR.MVMT and AVAILABLE.BAL multi value Fields
Slide 140
Cheque Collection
 FUNDS.TRANSFER or TELLER can be used for Cheque collection

facility by setting up FT.TXN.TYPE.CONDITION or
TELLER.TRANSACTION records to make use of appropriate
Transaction codes
 In both applications, separate versions are available to handle Direct

and Indirect methods
 Transaction input through the FT or TELLER application create records

automatically in CHEQUE.COLLECTION application with status as
‘Deposited’
Slide 141
Workshop - 19
 Use User Menu > Retail Operations > Account > Account Entries >
Today’s Account Balance
 View the Ledger balance of your Customer’s USD account
 Use User Menu > Retail Operations > Cheques for collection > Local
Cheques> Deposit Local Cheques – Direct Clearing
 Input 3 Cheques for USD 1000, USD 2000 and USD 3000 for collection to
the credit of USD Current account of your customer
 After authorizing each transaction, view the ledger balance. Drill down to
see the transaction after authorization
 Through context sensitive enquiry, view the accounting entries passed for
each transaction
Cheques > Cheque collection
 View the respective records in CHEQUE.COLLECTION
Slide 142
Slide 143
Slide 144
Slide 145
Slide 146
Slide 147
Slide 148
Slide 149
Slide 150
Slide 151
Slide 152
Slide 153
Workshop - 20
 Use User Menu > Retail Operations > Account > Account Entries >
Today’s Account Balance
 View the Ledger balance of your customer USD account
Cheques> Deposit Local Cheque- Indirect Clearing
 Input a Cheque of USD 1,500 accepted for collection to the credit of your
customer USD Current account
 After authorising the transaction, view the ledger balance. Look at the
transaction entries
 View the accounting entries through context sensitive enquiry
 Use User Menu > Retail Operations > Cheques for collection >
Enquires > Cheque Collection Details
 View the cheques pending collection in the savings account
 Drill down and view the respective records in CHEQUE.COLLECTION
Slide 154
Slide 155
Slide 156
Slide 157
Slide 158
Slide 159
Cheque Collection Features – CHEQUE.COLLECTION
 The status of cheques in CHEQUE.COLLECTION can be suitably

modified from DEPOSITED to CLEARED or RETURNED when the fate
is known
 Value date and exposure date can also be changed

 Value date defines the date when the entry is to be given value for interest
purposes and Exposure date defines the date on which the available
balance will be credited
 In case of Direct method

 Accounting entry to credit Customer account passed immediately, though
the Cheque is still under CHEQUE.COLLECTION with status ‘DEPOSITED’
 If value and exposure dates are changed when status is ‘DEPOSITED’, old
entries reversed and new entries generated
Slide 160
 In case of Direct method
 If the status is not changed even after value date, System passes
accounting entries by debiting and crediting Customer account with the
Cheque amount every day to effect change in value date
 When cheques are cleared, no further accounting entries are raised but
cheque amount is included under cleared balance. If the dates are changed
while changing the status to ‘CLEARED’, then change of dates will not be
effected as fresh accounting entries are not passed at this status change
 When cheques are returned, customer account is debited and internal

account for cheque return credited
Slide 161
 In case of Indirect method
 When cheques are cleared internal account for cheque sent on clearing
debited and customer account is credited
 If Value / Exposure dates are changed, the new dates will be incorporated
in accounting entries. As Customer account has not been created earlier,
there is no issue of reversal of old entries in this case
 When cheques are returned, internal account for cheque return is credited
Slide 162
Workshop - 21
Cheques > Cheque Collection
 Change the status of cheques for USD 1,000 and USD 1,500 as cleared
 Indicate Exposure date as the current date and value date as the next
working day
 Get the records authorised
 Use User Menu > Finance > Journal Facility > Accounting Entries
Enquiry > List of Transaction Entries
 View the effect on account balances and also the accounting entries
through Enquiry by using the CHEQUE.COLLECTION record Id
Slide 163
Slide 164
Slide 165
Slide 166
Slide 167
Workshop - 22
 Use User Menu > Retail Operations > Cheques for collection >
Outward Clearing Menu > Cheque Collection
 Change the status of cheque for USD 2,000 as Returned
 Authorise the Return
 Use User Menu > Finance > Journal Facility > Accounting Entries
Enquiry> List of Transaction Entries
 View the effect on account balances and also the accounting entries
through Enquiry by using the CHEQUE.COLLECTION record Id
Slide 168
Slide 169
Slide 170
Slide 171
Cheque Collection Features – CHEQUE.BATCH
 Cheque collection records can also be processed through

CHEQUE.BATCH application
 This helps group batches of cheques with status of ‘DEPOSITED’ together
for further processing
 Cheques drawn on a particular bank and sent on clearing on a given date
could be grouped together so that their fate could be handled together
Unforeseen event at a particular bank by which fate of cheques drawn on
it is delayed could be separated from other cheques
 When cheques are grouped in CHEQUE.BATCH, status of Cheque

automatically changed as ‘CLEARING’ in CHEQUE.COLLECTION
 No accounting entry is generated for this status change
Slide 172
Cheque Collection Features – CHEQUE.BATCH
 Status of Cheque could be changed subsequently only through

CHEQUE.BATCH
 If the status of entire batch is known, then it could be indicated as Collected
or Returned
 Status of individual Cheque collection record could also be indicated
separately, which will override the batch status
 If only 2 cheques in a batch are returned, the batch status could be set as
Collected and the individual status of the two cheques as Returned
 Possible to collect pre-defined charges and commission through

CHEQUE.COLLECTION / CHEQUE.BATCH
Slide 173
Cheque Collection Features – CHEQUE.CHANGE
 CHEQUE.CHANGE can be used to select cheque collection records or

cheque batches and group them for further processing
 APP.ID Field is used to indicate whether records of
CHEQUE.COLLECTION or CHEQUE.BATCH are to be selected
 Grouping can be done using SELECTION.FLD, OPERAND and

SEL.DATA Fields
 Group all records of CHEQUE.COLLECTION, whose Original value date
Equals 20th Jan 2008
 If CHEQUE.BATCH is selected as APP.ID and no further selections are

made, all the open cheque batches will be grouped together. This will
be useful at a Service Branch of the bank to combine the batches
received from various branches and present them to Clearing House
Slide 174
Cheque Collection Features – CHEQUE.CHANGE
 Based on the selection criteria, the system will select the

CHEQUE.COLLECTION / CHEQUE.BATCH records and process
according to instructions given in OPERATION Field
 Permitted operations are CLEARED, RETURNED, BATCH,REBATCH and
DATE.CHANGE
 If Operation is to REBATCH, the regrouped new batch Id will be displayed
as a no input field in BATCH.ID
 After Inputting the record, user has to open the record and use
Function VERIFY for due on-line processing
Slide 175
Workshop - 23
Cheques > Change Outward Clearing Details
 Select records from CHEQUE.COLLECTION, whose CREDIT.ACC.NO

equals your Customer’s Savings account and change the status as
‘CLEARED’
Slide 176
Slide 177
Draft Management
 A bank's cheque or Draft, are cheques issued against the funds of a

financial institution rather than an individual account holder.
 In TELLER application the CHEQUE.TYPE field classifies the

instrument as draft.
 The status of the draft is held in CHEQUE.REGISTER.SUPPLEMENT.

The table can hold various statuses like issued, presented, cleared,
exception, unknown, cancelled, Stopped and returned.
Slide 178
Quiz - 2
1) Which Balance will be updated immediately on authorisation of a

cheque deposited for collection?
Ans: Online actual balance
2) What accounting entries are generated when the cheque status is

shown as CLEARING in CHEQUE.BATCH?
Ans: No accounting entries are generated
3) When is the amount of a cheque deposited for collection available for

drawing?
Ans: On Exposure date
4) What happens if AUTO.CLEAR Field in CQ.PARAMETER is set as

yes?
Ans: During COB cheque collection status changes to CLEARED
Slide 179
CC - Dependency Diagram
CUSTOMER
ACCOUNT TELLER
CATEGORY
FUNDS.TRANSFER
CURRENCY
FT.COMMISSION.TYPE CHEQUE.COLLECTION
FT.CHARGE.TYPE
ACCOUNT.PARAMETER
CQ.PARAMETER ACCOUNT
BC.SORT.CODE (Customer type and Internal)
Slide 180
Teller Financial Services
Slide 181
Teller Financial Services - Introduction
 Teller Financial Services is a new initiative in R15
 This initiative came because of multiple tasks that a Teller is expected

to perform
 For multiple services availed, customer is charged individually for each

service
 TFS facilitates the capture of many transactions in one screen
 It consolidates entries, charges and advices
 It acts as a front end to TELLER, FUNDS TRANSFER and

DATA.CAPTURE applications
Slide 182
 TFS helps to:

 Set up Consolidation rules for accounting entries
 Parameterise the transactions that are performed using TFS once
 Perform more than one transaction simultaneously
 Choose to either charge the customers for each individual transaction or
charge a consolidated amount
 Provide the customer with a consolidated transaction slip
 Consolidate accounting entries in the Customer account
Slide 183
 Navigation is easy
 Data Defaulting
 Facilitates Inter branch and Multi book set up
 Status of child transactions can be controlled
Slide 184
TFS – Parameter Tables
 Parameterisation of TELLER and FUNDS.TRANSFER modules
 TFS.PARAMETER
 TFS.TRANSACTION
Slide 185
TFS.PARAMETER
 Basic Parameter table for the whole Company
 Six sets of parameterisation:

 Consolidation Parameter
 Usability Preferences
 Currency Conversions
 DC Related Parameters
 Interface Parameters, and
 Miscellaneous Parameters
Slide 186
TFS.PARAMETER- Consolidation Related
 To enable consolidation:
 SET.THIS.TO.ENABLE.IF.YOU.WANT.TO.HAVE.INDIVIDUAL.LEGS.TO.R
ESULT.IN.A.CONSOLIDATED.POSTING.ON.CUSTOMER.ACCOUNT
 WHEN.LEGS.ARE.COMBINED.SHOULD.IT.BE.GROSS.(DR.AND.CR.
GROUPED.SEPARATELY).OR.NET?
 Gross
 Net
Slide 187
 Main criteria for Consolidation is Value date
 Other Consolidation rules can be applied:

 By Currency
 By Transaction
 By Both
 Additional Consolidation Parameterisation : Consolidation of User input

legs is done by Value Date. Please specify here any additional
parameters for Consolidation
 The consolidated amount needs to go through a Washthrough account
 Category specified in “Internal Account category to be used for

Washthrough”
Slide 188
 “What is the Transaction type to be used for the Consolidated Leg?” is

used for transaction codes for the consolidated leg
 If Consolidation amount is Zero:

 Change to Gross – Have different entries for Credit and Debit
 Undo Consolidation
 Ignore Consolidation
Slide 189
 Cheques have different exposure dates
 Cash deposits should have same day availability
 A record in BC.SORT.CODE with VALUE.DATE.PRD &

EXP.DATE.PRD left blank has to be created
 Charges can also be consolidated
 The transaction type to be used for applying this consolidated charge

can be specified in “What is the Transaction Type to be used for
Charge Entry?”
Slide 190
 The API to return the Narrative for the Consolidated entry is specified in
the field labeled as “API to return the Narrative for the Consolidated
Transaction”
Slide 191
TFS.PARAMETER- User Comfort Related
 “Hot Fields” validate the data input
 BENEFICIARY.ID should be a Hot field
 “Based on the preferred workflow, define the fields that require

validation to happen on Field Input” can be used to specify the TFS
fields which need validation on input
 The values in TFS can be shown as a Combo –box or a Drop-down by

choosing the right option in the field “On the transaction screen, how
should the lookup for Transaction types appear?”
Slide 192
TFS.PARAMETER- User Comfort Related
 A desired set of multi-value can be automatically opened by specifying

that number in the field labelled as “Set the number of TFS Legs that
should be automatically expanded when Opening a new Transaction”
 VERSION and TRANSACTION.TYPE filter the transaction types to be

displayed on screen
Slide 193
TFS.PARAMETER- Currency Conversion Related
 When a transaction involves a currency different from the Debit account

and the Credit account currencies, system can calculate the Debit or
Credit currency equivalents
 The rate that can be used are:

 Buy/Sell
 Mid reval rate
 The rates can be specified in the field “Define your Rate preferences
for Currency Conversions. It can be left blank to be auto populated with
Common practice” for :
 When Buying FCY and Selling LCY
 When Buying LCY and Selling FCY
 When Buying FCY and Selling FCY
Slide 194
TFS.PARAMETER- Currency Conversion Related
 Market Exchange profit/loss = Difference between Local currency

equivalent using Buy Sell rate and Mid reval rate
 Transactions like Cash Deposit should not attract the calculation of

Market Exchange Profit or Loss
 Transactions like a Currency exchange should attract the calculation of

Market exchange profit/loss
 Market exchange profit/loss calculation should be disabled at Company

level and enabled at choice Transaction levels
 The field “Should we Allow TELLER to calculate Market Exchange

Profit?” should be used
Slide 195
TFS.PARAMETER- Data Capture Related
 When a TELLER or FT child transaction created by TFS needs to be

reversed, as long as it is in Live status, TFS will simply reverse them
 If in History status, offsetting Data Capture legs will be generated
 The transaction code used will be specified in “When DC is used to

Reverse a Transaction”
 The DC legs can be created with or without the Reversal marker
Slide 196
TFS.PARAMETER- Interface Related
 TFS uses T24 Open Financial Services to create transactions for each
TFS Leg, in FT or TT or DC module
 “Define how this front end talks to the Underlying modules (FT, TT and
DC)” can be used to specify the OFS.SOURCE record
 Child module specific definitions also need to be specified
 The same settings are available at Transaction levels
Slide 197
TFS.PARAMETER – Miscellaneous
 Exposure Dates can be :

 Single availability dates
 Multiple availability dates
 Revising a float input on a day in the past is not possible
 Float for the cheques can also be managed by using

AC.LOCKED.EVENTS
 The Online Cleared Balance and Working Balance on the account will
be immediately updated but the amount will really be ‘Locked’
 The difference lies in the internal reports sun based on the “Cleared
Balance” of all accounts
Slide 198
 “How should the system apply Forward Exposures?” to be used to

specify the method of managing float
 AML information can be used for :

 Just Information
 For Validation
Slide 199
 “The system uses Lookup tables for Legal Document Names, Issue
Authority, Communication Type etc. Which Lookup Tables should be
used for AML Dropdowns?” can be used to specify the kind of look up
tables for AML dropdowns
 The Look up tables will be the following in case of Customer setting:

 CUS.LEGAL.DOC.NAME for LEGAL.DOC.NAME Field
 CUS.COMM.TYPE for COMM.TYPE Field
 CUS.LEGAL.ISS.AUTH for LEGAL.ISS.AUTH Field
 If the setting is Native, the following tables will be required :

 TFS.LEGAL.DOC.NAME for LEGAL.DOC.NAME field
 TFS.COMM.TYPE for COMM.TYPE field
 TFS.LEGAL.ISS.AUTH for LEGAL.ISS.AUTH Field
Slide 200
 A Transaction limit can be specified in TFS
 Alerts can be generated if the Limit is breached
 The amount to be checked for Limit breaching can be:

 Consolidated amount
 Individual amount
 Choice of not to having any such Limits at all can be exercised
 A Global Limit as well as limits for individual currencies can be

specified
Slide 201
 The field labelled as “While Inputting transactions, if the user changes

the Transaction type of a Leg, which associated fields need to be
Cleared?”can be used to define which of the fields in a TFS leg need to
be changed /reset for re-calculation when the user changes the
transaction type
Slide 202
TFS.TRANSACTION
 TFS.TRANSACTION is a FIN type table set for the transaction types

used in TFS
 The Transaction parameterisation is classified into Basic and Advanced
Slide 203
TFS.TRANSACTION – Basic
 The narration on the Customer’s account statement for the

consolidated entry can be specified in the CONSOL.NARR Field
 A particular transaction can be excluded from consolidation
 CHEQUE.COLLECTION record cannot use a Wash through account

but will use a Primary account
 INTERFACE.TO and INTERFACE.AS hold child transaction module

definitions
 The Version used to create the child transaction can be specified in

OFS.VERSION
Slide 204
TFS.TRANSACTION – Basic
 Surrogate Account: Alternative account to Debit or Credit accounts on

each leg
 The SURROGATE.AC can be ACCOUNT.DR or ACCOUNT.CR
Slide 205
TFS.TRANSACTION – Advanced
 It is possible to use TFS to Reverse the transaction even if it has been

moved to History. TFS accomplishes this by creating offsetting DC
Legs for the Accounting entries raised by the original child transaction
 “When DC is used to Reverse a Transaction of this type (in History)

what should be the” will be used for Debit and Credit entries
respectively
 Exchange rates to be used during Currency exchange can be set up for

the below scenarios:
 When Buying FCY and Selling LCY
 When Buying LCY and Selling FCY
 When Buying FCY and Selling FCY
 Transaction CCY to Dr A/C CCY
 Transaction CCY to Cr A/C CCY
Slide 206
TFS – Product Features
Slide 207
TFS Product Features
 The TFS transaction can be launched by either of the two below

methods:
 As a drill-down from an Account enquiry, or
 Directly from the Menu
 The Bank user should be first allotted a Till and a Teller Id
Slide 208
Slide 209
Workshop – 24
 Use Role Based Home Pages > Home Page - Teller > Teller Operation
>Cash Deposit Foreign
 Accept GBP 20,000 into your customer’s USD account in GBP 50
denomination.
 Validate and view System defaulted exchange rate, charges and credit
amounts as relevant
 Commit and get the records authorised
 View the Till balance in Role based home page in teller operation
dashboard.
Slide 211
Workshop – 24
Slide 212
Workshop – 24
Slide 213
Workshop – 25
 Use Role Based Home Pages > Home Page - Teller > Teller Operation
>Cash Withdrawal Foreign
 Accept GBP 10,000 into your customer’s USD account in GBP 50
denomination.
 Validate and view System defaulted exchange rate, charges and credit
amounts as relevant
 Commit and get the records authorised
 View the Till balance in Role based home page in teller operation
dashboard.
Slide 214
Workshop – 25
Slide 215
Workshop – 25
Slide 216
Status of Child Transactions
 An authorised TFS transaction will give birth to self-authorised child

transactions
 A single-authoriser TFS transaction will have unauthorised child

transaction
 Errors and overrides raised by the child transactions will be present in

the TFS transaction as well
 If TFS is in INAO status, child transaction will also be in INAU
Slide 217
Status of Child Transactions
 If Consolidation is not enabled, then any individual TFS Leg can be

reversed independent of the other Legs
 If Consolidation is enabled, then all TFS Legs need to be reversed
 Any changes to the TFS transaction in unauthorised status will also be

updated to the child transactions
Slide 218
Defaulting of Data From TFS to TELLER
Slide 219
Defaulting of Data From TFS to FT
Slide 220
Defaulting of Data From TFS to FT
Data Capture
Leg 1
Data Capture
Leg 2
Slide 221
Account Default at Bank side
 Transactions where both sides of the Transaction is the Bank
 The Credit and Debit account numbers are defaulted based on the
Transaction currency of the TFS leg
 Defaulting not possible if the child transaction is on FT or DC
Slide 222
Account Default at Customer Side
 TFS defaults the first account of the customer is defaulted as the

Primary Account
 In case Consolidation is:

 Enabled: The wash through account is defaulted to the Primary account
 Disabled: The customer account if supplied will be defaulted
 To default the other side of the leg without showing both the Debit and
Credit accounts, surrogate accounts are used
Slide 223
Surrogate Account
 Surrogate Account: Alternative account to the Debit or Credit side of

the Leg
 The system determines which account (Primary or Surrogate)

corresponds to Debit and which to Credit by using the Field
SURROGATE.AC in TFS.TRANSACTION
 Input FROM and TO transactions and the system would default the
accounts as FROM and TO accounts
Slide 224
Other Features
 TFS supports Inter company transactions, provided the CUSTOMER is

shared between the T24 Company where the Customer of the financial
institution belongs to and the T24 Company that the user is currently
logged onto
 Market exchange Profit/Loss can be calculated by the Teller using TFS
 In case of a Transaction which does not attract the calculation of

Market exchange profit/loss, accounting entries will not account for the
profit or Loss. E.g. a Cash deposit
 In case of transactions like Currency exchange, Market exchange profit

or loss is accounted for
Slide 225
Bill Payment
 Carry out a transaction of a Bill Payment
 Either enter the Payee account as a Surrogate account or as the

Beneficiary
 TFS doesn’t support Wire/Telex transfers or Swift generation
 The beneficiary details can be input in the Bill Payment Tab
 Beneficiary Tab, if a Hot field, will validate the account on input
Slide 226
Workshop 26
 Use User Menu > Retail Operations > Teller > Financial Services >
Multi Till Operation -LCY
 Input a transaction for your customer using his USD account as the Primary
Account
 Deposit an amount of USD 10,000 in denominations of USD100
 Pay a Bill amounting to USD 2000 to another USD account
 Enable Consolidation in the transaction
 Accept all overrides
 While validating the transaction, view the entries being posted to the Wash
through account
 In the results tab, view the Child transactions created
 View a Teller transaction using the child transaction reference
Slide 227
Slide 228
Slide 229
Summary
We have so far seen
 Product Overview of Teller Module

 Dependencies of Teller module
 Learning linkage of Teller with other T24 static tables
 Learning to set up application specific Parameter tables
 Learning main business features of TELLER module including:
 Travelers Cheque handling
 Cheques Collection
 Teller Financial Services (TFS)
 Accounting, messages and enquiries
Slide 230
Thank You
TECHMILL TRAINING

Teller - TM - R15

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Teller - TM - R15

Caricato da

Copyright:

Formati disponibili

T24 Teller

Till Monitoring Tills

 TELLER makes use of

 TELLER also uses other Static tables

 TELLER application is used to transfer money between Customer type

 Customer type of accounts use 1000 to 9999 range of Category code

 Internal accounts use 10000 to 19999 range of Category codes

 PL category codes use Category codes above 50000

Charges and commissions for specific Teller operation

Also possible to accrue or amortise charges on

Buying and Selling exchange rates defaulted based on Currency market

 Parameter tables for TELLER to be set-up :

 Description and currency wise value of denominations to be used in

 DENOM.TYPE table is used to define various denomination types such

 First 3 characters of Id to be a valid Currency

 Denominations defined in TELLER.DENOMINATION appear in

 Parameter file to define general rules and Category and Transaction

 Rules can be set company wise and hence Id is Company code

 Vault information to be indicated in VAULT.ID and VAULT.DESC Fields

 Exchange rate related choices

 System defaults buying and selling rates automatically. User may be

 Category and Transaction codes to be used in various situations

 When there is a shortage or excess in Till balance during Closure of Till, it

 The transaction codes to be used for these situations are defined in

 Cash accounts to be handled by Teller defined in TRAN.CATEGORY multi

 Category and Transaction codes to be used in various situations

 Splitting charges and tax from transaction amount

 Whenever a till balance goes to credit on authorisation of a Teller

 Denomination in multiple Internal account can be controlled by

 Id is numeric. Up to 999 transaction records can be created

 While inputting a teller transaction, when this pre defined transaction

 Transaction definition for Side 1

 Transaction definition for Side 1

 Similarly, rules defined for Side 2 in respective fields with suffix 2

 Market to be used for calculating exchange rate for Charges is

 Charges / Commissions and Tax

 Till to Till transfer transaction

 Customer account transfer

 It is possible to scan and store Customers’ signatures through

 When the Customer’s account is debited, then on input of account number,

 If VERIFY.SIGNATURE is set as YES, and if the signature is not displayed

 If set as NO, no such override is generated

 Create a new transaction in TELLER.TRANSACTION with the following

 Id is Till number. For creating records for Vaults, Ids indicated in

 The field STOCK.UPDATE is used to update cash denominations

 Limits can be set for each tills by specific currency.Incase there is a

 APPL.GEN.CONDITION with Id as TELLER can be used to form

 If RESIDENCE Field is defined in STANDARD.SELECTION for

 TT.GROUP.CONDITION can be set up to create default conditions

 Id is the valid group created in APPL.GEN.CONDITION (example:

 Rate spread is indicated as % of preferential Rate on Customer Spread

 Where groups of customers are given preferential Commission rates,

 Use Command line and access TT.GROUP.CONDITION

 It is possible to issue passbooks instead of statements to accounts duly

 For those accounts, PASSBOOK Field should be set as YES in the

 TELLER.PASSBOOK application to be set up for designing the

 PASSBOOK.DEVICE Field of TELLER.ID application to indicate which

 Passbooks are updated by Teller using Function Verify in

 Format for passbook can be defined in TELLER.PASSBOOK

 Details of what to be printed when:

 Data printed can be any field from the following files:

 Any free format text or one of the following:

1) A Bank wants to issue passbooks for a group of current accounts

2) What is the purpose of defining SHORT.CATEGORY codes in