T24 Teller

TEMENOS EDUCATION CENTRE

Warning: This document, is protected by copyright law and international treaties. No part of this document
may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose, without the express written permission of TEMENOS HEADQUARTERS SA Unauthorized
reproduction or distribution of this presentation or any portion of it, may result in severe civil and criminal
penalties, and will be prosecuted to the maximum extent possible under applicable law.” Information in this
document is subject to change without notice
Teller – Product overview

Till assigning to
Teller

Till Monitoring Tills

administration
Vault control
Head Teller

Till Transfer
authorisation Cash deposit and
with drawal
Teller
Currency exchange
Local currency
transactions
Account transfer

Travellers cheque
Teller handling
Till transfer
Limits Foreign
currency Passbook Printing
Accounting transactions

Slide 2
TELLER - Introduction

 Typical daily operational cycle

 Assigning tills to Tellers by Head Teller
 Tellers carry out variety of transactions for Customers
Verify signature before making payments
Print deal slips and passbooks
 Money transferred from Vault to tills if needed
Intra day transfer of cash between tills
 Finally transfer balance to vault and close till
Small change left with Tellers or fully transferred
Cash physically checked and Shortage/overage in tills accounted

 Integrated with accounting and balance updates on real time

 T24 maintains Teller wise cash through internal accounts
 Debit balance in cash account of Teller implies cash available with Teller

Slide 3
TELLER dependencies

 TELLER makes use of

 CUSTOMER
 ACCOUNT

 Core dependencies
 Delivery
 Accounting
 Limits

 TELLER also uses other Static tables

Slide 4
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 Travellers cheques

 PL category codes use Category codes above 50000

Slide 5
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 6
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 7
Application specific Parameters

Slide 8
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 9
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 Travellers cheques

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

Cash, Gift Cheques, Travellers 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

Slide 10
TELLER.PARAMETER

 Top level 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 11
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 12
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 multi value Field

TRAN.CATEGORY
Category code for internal accounts for Cash and Travellers 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 13
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
If Charges and Tax have to be combined, could be done through
TRANSACTION table

Slide 14
TELLER.PARAMETER

 Multi-line Teller deal can be input through Desktop

 It comprises of a Master transaction, linked to several 'child' or 'leg'

transactions
 Master controls the overall charges and accounting of the entire 'set‘

 Multi-line deals allow the user to process multiple transactions while

building a running total for charge/commissions. The total of sales is
taken into consideration before applying default such as minimum
commission

 If a Customer account is involved, then accounts of the same customer

to be used in all legs

Slide 15
TELLER.PARAMETER

 Multi Line transaction details

 If charges are modified by inputting an amount manually, it is accounted by

using FT.COMMISSION.TYPE defined in MODIFY.CHARGE.CODE field
If this field is left blank, option to indicate amount manually is not available

 Any pre defined TELLER Version could be indicated along with sub-routine
which should be run at the end of a master transaction by indicating them in
VERSION and FINISH.ROUTINE fields

 When Teller finishes one leg of a multi- line deal, system can automatically
start a new leg or prompt each time asking whether to create a new leg or
finish by using AUTO.NEXT field
Yes - indicates that a new leg should be started automatically
NO or blank - means the Teller should be prompted each time

Slide 16
TELLER.PARAMETER

 Generally only one till is allotted to a user through TELLER.ID

 As long as that till is open, System will not allow another till to be
allotted to the same User

 However, if it is proposed to allot more than one till to a User, then,

MULTI.TILLS field should be set as Yes
 If this is set as Yes, then MAX.TILLS field opens up and is mandatory
 Upto 99 tills can be stipulated here

Slide 17
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. Upto 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 18
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 19
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 20
TELLER.TRANSACTION

 Charges / Commissions and Tax

 Charges and Tax to be collected for this transaction defined in multi value
field CHARGE.CODE. 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

 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
multi value field ADVICE.VERSION

Slide 21
TELLER.TRANSACTION

 AUTO.DENOMINATE
 The user can choose whether the defaulting of the denomination should be
enabled at the transaction level or not. Field AUTO.DENOMINATE – 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 number of denominations for a specific type
of transaction.

Slide 22
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

Slide 23
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 24
Workshop – 1

 Use MB 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 25
Workshop – 1 Solution

Slide 26
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 27
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 28
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 Fields CHG.CCY and CHG.AMT

Slide 29
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 30
Workshop – 2 Solution

Slide 31
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, Field PASSBOOK 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 32
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 33
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 34
Quiz

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?

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

TELLER.PARAMETER?

3. What is the use of MULTI.TILLS field in TELLER.PARAMETER?

4. Where can we opt for filtering denomination?

Slide 35
Quiz

5. What should be the status of record for VAULT in TELLER.ID – Open or

Closed?

6. What is the purpose of TELLER.PASSBOOK table?

7. How is a till allotted to a User?

8. What is the maximum number of tills that could be allotted to Users in a

Company?

Slide 36
TELLER - Build sequence

Mandatory *
1. ACCOUNT.CLASS
(MKTEXCHCR, MKTEXCHDR,SAVINGS) Optional

2. TELLER.DENOMINATION

3. TELLER.PARAMETER *

4. DEAL.SLIP.FORMAT

5. TELLER.TRANSACTION * DEAL.SLIP.FORMAT

Slide 37
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 38
TELLER – Product features

Slide 39
Product features

 TELLER Application 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 40
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. 9999 is reserved for Vault

 TILL STATUS should be set as OPEN while allotting a new Till and
CLOSE during Till closure
 TELLER field indicates USER.ID of the User of the till

 Denominations defined in TELLER.DENOMINATION appear in

TELLER.ID

 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 41
Workshop - 3

 Use MB 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 42
Workshop – 3 Solution

Slide 43
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 44
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 45
Workshop - 4

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Teller cash > LCY cash deposit - LCY A/c
 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

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Teller cash > LCY Cash withdrawal - LCY A/c
 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

 Use MB User Menu > Retail Operations > Teller > Head Teller
Operations > Enquiries > Account Balances
 View balance of the same account. Drill down to look at list of transactions

Slide 46
Workshop – 4 Solution

Slide 47
Workshop – 4 Solution

Slide 48
Workshop – 4 Solution

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
Workshop – 5

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Teller cash > LCY Cash Deposit - FCY A/c
1. Accept USD 20,000 into your customer’s GBP account in USD 50
denomination. Waive charges
2. Accept USD 40,000 for the same account in USD 100 denomination. Do
not waive charges

 Validate and view System defaulted exchange rate, charges and credit
amounts as relevant

 Commit and get the records authorised

 Through context sensitive enquiry, view details of accounting entries for

the second transaction for the charges to be recovered

Slide 51
Workshop - 5 Solution

Slide 52
Workshop - 5 Solution

Slide 53
Workshop – 6

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Teller cash > LCY Cash withdrawal - FCY A/c
 Allow withdrawal of USD 5,000 from your customer’s GBP account. Do
not waive charges. Input 654321 as cheque number. Pay in USD 100
denomination
 Allow withdrawal USD 20,000 from the same account. Do not waive
charges. Input 765432 as cheque number. Pay in USD 50 denomination

 Validate and view System defaulted exchange rate, commission and

debit amounts in both the cases. Commit the records. Accept overrides

 Observe System has not collected charges in the first case, though
opted to collect

 Get the records authorised

Slide 54
Workshop – 6 Solution

Slide 55
Workshop – 6 Solution

Slide 56
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 57
Workshop - 7

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Teller cash > FCY Cash deposit
 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

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Teller cash > FCY Cash withdrawal
 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 58
Workshop – 7 Solution

Slide 59
Workshop – 7 Solution

Slide 60
Workshop – 7 Solution

Slide 61
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 62
Workshop - 8

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Enquiries > Cash Position by Till
 View your cash position

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Currency Exchange > Exchange rate
 View exchange rate for GBP currency

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
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 63
Workshop – 8 Solution

Slide 64
Workshop – 8 Solution

Slide 65
Workshop – 8 Solution

Slide 66
Workshop - 9

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
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 get it authorised

 Observe accounting entry prepared for marketing exchange profit

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Enquiries > Cash Position by Till
 View your cash position

Slide 67
Workshop – 9 Solution

Slide 68
Workshop – 9 Solution

Slide 69
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

 FROM TELLER and TO TELLER fields 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 70
Workshop - 10

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Till transfer > LCY Till Transfer
 Transfer USD 50,000 to another Till in denominations of USD 100

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
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 71
Workshop - 10 Solution

Slide 72
Workshop – 10 Solution

Slide 73
Workshop – 10 Solution

Slide 74
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 75
Workshop – 11

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Enquiries > Cash Position by Till
 View your Till cash position

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Till transfer > Till to vault
 Transfer entire USD balance to Vault. Get the transfer authorised

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Till Administration > Initiate Till Closure
 Close your Till by indicating cash with you
 Get the closure authorised

 Use MB User Menu > Retail Operations > Teller > Head Teller
Operations > Enquiries > Cash Position by Currency
 View overall till balances in all currencies

Slide 76
Workshop – 11 Solution

Slide 77
Workshop – 11 Solution

Slide 78
Workshop – 11 Solution

Slide 79
Workshop – 11 Solution

Slide 80
TELLER – Multi line deals

 Multi-line deals allow the user to process multiple transactions while

building a running total for charges/commissions

 It comprises a Master transaction, linked to several 'child' or 'leg'

transactions. Master controls overall charges and accounting of the
entire 'set‘

 Salient features of Multi-line transactions:

 When client accounts are to be used, then client should be the same in the
entire set of legs in a multi-line deal
 Charges are calculated taking the multi-line as a single unit
 Charges can be standard or waived or modified by manual input
 Deal Slips for multi-line deals are produced through Enquiries
 Authorisation, Reversal and Copying only to Master Deal
 Multi-line Teller deal can be input through Desktop

Slide 81
Preferential charges for Multi line deals

 Group wise or Customer wise preferential charges can be set in

TT.GROUP.CONDITION
 Groups can be formed based on CUSTOMER or TELLER application
details

 In the case of Multi line deals, all the legs belong to the same customer
and charges are consolidated and applied based on the type

 If the Contract Group is constructed based on a field of CUSTOMER

application, all legs will have the same Contract Group, and the
relevant charge concessions defined in TT.GROUP.CONDITION will be
applied

 If Contract Groups are based on some other criteria and if the contract
groups are not the same across the legs of Multi line deals, then
TT.GROUP.CONDITION will not be applied

Slide 82
Workshop – 12

 Use MB User Menu > Retail Operations > Teller > Head Teller
Operations > Till Administration > Reopen Teller
 Act like a Head Teller and reopen your till again

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Teller cash > LCY Cash Deposit FCY A/c
 Accept USD 30,000 into your customer’s GBP account in in USD 100
denomination. Waive charges
 Get the record authorised

Slide 83
Workshop – 12 Solution

Slide 84
Workshop – 12 Solution

Slide 85
Workshop – 13

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Teller cash > LCY Cash withdrawal - FCY A/c
 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 86
Workshop – 13 Solution

Slide 87
Workshop – 13 Solution

Slide 88
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
Multi field LINKED.TILLS
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 89
TELLER – Other facilities

 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 90
TELLER – Other facilities

 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 91
Travellers cheques handling

Slide 92
Travellers cheques - features

 Travellers cheques processing could happen under two situations:

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

 Handling Travellers cheques is similar to handling operations of other

internal accounts
 Certain points to be taken care of while designing and implementation of
handling Travellers cheques

Slide 93
Travellers cheques

 Separate CATEGORY codes to be created for Travellers cheques

stock control and Travellers 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 Travellers 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 94
Travellers cheques

 If separate rates are needed for sale of Travellers 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 Travellers cheques

 Separate versions available for procuring Travellers cheques stock.

Done through Head Teller operations

 Travellers cheque sales and Issuer wise Till Transfer possible

 Internal accounts can be defaulted if required through separate

versions

Slide 95
Travellers cheques – Internal accounts

 Internal Accounts for Stock control

 Necessary to open Internal accounts in all currencies of Travellers
Cheques, Issuer wise, for Travellers 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 96
Travellers 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
 Could be maintained at Vault level if so opted in TELLER.PARAMETER

 Internal Accounts for Travellers Cheques contra

 Necessary to open Internal accounts in currency of Travellers Cheques,
Issuer wise, for Travellers 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 97
Travellers 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 EUR1090599990001

 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 98
Travellers 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 99
Workshop – 14 / Trainer Demonstration

 Use MB User Menu > Retail Operations > Teller > Head Teller
Operations > Travellers 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 Travellers cheques and indicate the serial
number format as XX.NNN.NNN.NNN. Get the record authorised

Slide 100
Workshop – 14 Solution

Slide 101
Workshop - 15

 Use MB User Menu > Retail Operations > Teller > Head Teller
Operations > Travellers 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
OF.050.000.001 to OF.050.000.200 for EUR TC 50.
 Get the record authorised

 Use MB User Menu > Retail Operations > Teller > Head Teller
Operations > Travellers Cheque > TC Stock Balance
 View the TC stock balance in EUR currency

Slide 102
Workshop – 15 Solution

Slide 103
Workshop – 15 Solution

Slide 104
Workshop - 16

 Use MB User Menu > Retail Operations > Teller > Head Teller
Operations > 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.OF.050.000.001 TO
OF.050.000.100.

 Get the record authorised

Slide 105
Workshop – 16 Solution

Slide 106
Workshop - 17

 Use MB User Menu > Retail Operations > Teller > Head Teller
Operations > Travellers 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

 Use MB User Menu > Retail Operations > Teller > Head Teller
Operations > Travellers Cheque > 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).

 Use MB User Menu > Retail Operations > Teller > Head Teller
Operations > Travellers Cheques > TC Stock Balance
 View the TC stock balance in EUR currency

Slide 107
Workshop – 17 Solution

Slide 108
Workshop – 17 Solution

Slide 109
Workshop – 17 Solution

Slide 110
Travellers 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 111
Workshop - 18

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Travellers 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

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Travellers 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

 Use MB User Menu > Retail Operations > Teller > Head Teller
Operations > Travellers Cheques > TC Stock Balance
 View the TC stock balance in EUR currency

Slide 112
Workshop – 18 Solution

Slide 113
Workshop – 18 Solution

Slide 114
Workshop – 18 Solution

Slide 115
Workshop - 19

 Use MB User Menu > Retail Operations > Teller > Head Teller
Operations > Enquiries > Till TC Issue Entries Today
 View Travellers cheques sold today at your Till in EUR

 Use MB User Menu > Retail Operations > Teller > Head Teller
Operations > Travellers Cheque > 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 116
Workshop – 19 Solution

Slide 117
Workshop – 19 Solution

Slide 118
Travellers 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 119
Workshop - 20

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Travellers Cheque > Buy TC’s against Cash
 Buy TC for GBP 2,000 for cash. Use USD 100 denomination. Use rate 1.90

 Use MB User Menu > Retail Operations > Teller > Teller Operations >
Travellers 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

 Use MB User Menu > Retail Operations > Teller > Head Teller
Operations > Enquiries > Till TC Buy Entries Today
 View the TC bought by your Till in GBP and EUR

Slide 120
Workshop – 20 Solution

Slide 121
Workshop – 20 Solution

Slide 122
Workshop – 20 Solution

Slide 123
TELLER - Other features

Slide 124
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 125
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 multi value Field ADVICE.VERSION in
TELLER.TRANSACTION

 Deal slips are generated when the Teller hits the PRT.HOT.KEY
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 126
Standard enquiries

 Standard enquiries available include:

 Cash position by Till

 Cash position by Currency

 Till cash entries today

 Account balances

 Till TC Issue entries today

 Till TC Buy entries today

Slide 127
TELLER - Dependency diagram

CUSTOMER
TELLER.PASSBOOK
ACCOUNT
FT.COMMISSION.TYPE DEAL.SLIP.FORMAT
CATEGORY
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 128
Cheques for collection

Slide 129
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 130
CC - Parameter tables

 Cheques for collection related tables to be set up

 ACCOUNT.PARAMETER

 CQ.PARAMETER

 BC.SORT.CODE

Slide 131
ACCOUNT.PARAMETER

 If Cheque issue management and collection operations are desired,

then the following fields are to be set up
 CHEQUE.REGISTER to be set as Yes
 RETURN.TXNS and RETURN.SUSP.CAT 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 132
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 133
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 134
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 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

Slide 135
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 136
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 137
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 138
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 Fields CHQS.COLL.SUSP and CHQS.RET.SUSP

Slide 139
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 140
CC - Build sequence

Mandatory *
Optional
1. ACCOUNT.PARAMETER *

2. CQ.PARAMETER *

3. BC.SORT.CODE * EXPOSURE.CONDITIONS

Slide 141
CC – Product features

Slide 142
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 multi value fields

AVAILABLE.DATE, AV.AUTH.CR.MVMT and AVAILABLE.BAL

Slide 143
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

 For both methods Direct and Indirect methods separate version are
available to handle

 Transaction input through the FT or TELLER application create records

automatically in CHEQUE.COLLECTION application with status as
‘Deposited’

Slide 144
Workshop - 21

 Use MB User Menu > Retail Operations > Account > Enquires >
Account Entries > Today’s Account Balance
 View the Ledger balance of your Customer’s USD Current account

 Use MB User Menu > Retail Operations > Cheques for collection >
Outward Clearing Menu > Outward clearing LCY - Direct
 Input 3 Cheques for USD 1000, USD 2000 and USD 3000 for collection to
the credit of USD Current account of your customer
 After authorising each transaction, view the ledger balance. Drill down to
see the transaction after authorisation
 Through context sensitive enquiry, view the accounting entries passed for
each transaction

 Use MB User Menu > Retail Operations > Cheques for collection >
Outward Clearing Menu > Cheque collection
 View the respective records in CHEQUE.COLLECTION

Slide 145
Workshop – 21 Solution

Slide 146
Workshop – 21 Solution

Slide 147
Workshop – 21 Solution

Slide 148
Workshop – 21 Solution

2 2

Slide 149
Workshop – 21 Solution

Slide 150
Workshop – 21 Solution

3
3

Slide 151
Workshop – 21 Solution

2 2

Slide 152
Workshop – 21 Solution

Slide 153
Workshop – 21 Solution

Slide 154
Workshop – 21 Solution

2 2

Slide 155
Workshop – 21 Solution

Slide 156
Workshop – 21 Solution

Slide 157
Workshop - 22

 Use MB User Menu > Retail Operations > Account > Enquires >
Account Entries > Today’s Account Balance
 View the Ledger balance of your customer USD account

 Use MB User Menu > Retail Operations > Cheques for collection >
Outward Clearing Menu > Outward Clearing LCY - Indirect
 Input 3 Cheques of USD 1,500, USD 2,500 and USD 3,500 accepted for
collection to the credit of your customer USD Savings account
 After authorising each transaction, view the ledger balance. Look at the
transaction entries
 View the accounting entries through context sensitive enquiry

 Use MB 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 158
Workshop – 22 Solution

Slide 159
Workshop – 22 Solution

Slide 160
Workshop – 22 Solution

3 3

Slide 161
Workshop – 22 Solution

3 3

Slide 162
Workshop – 22 Solution

3 3

Slide 163
Workshop – 22 Solution

Slide 164
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 and exposure dates 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 credit 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 165
Cheque collection features – CHEQUE.COLLECTION

 In case of Direct credit 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 166
Cheque collection features – CHEQUE.COLLECTION

 In case of Indirect credit 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 instead
credited

Slide 167
Workshop - 23

 Use MB User Menu > Retail Operations > Cheques for collection >
Outward Clearing Menu > 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 in the case of cheque for USD 1,500

 Get the records authorised

 Use MB User Menu > Treasury Operations > Finance > View
Authorised Entries
 View the effect on account balances and also the accounting entries
through Enquiry by using the CHEQUE.COLLECTION record Id

Slide 168
Workshop – 23 Solution

Slide 169
Workshop – 23 Solution

Slide 170
Workshop – 23 Solution

Slide 171
Workshop - 24

 Use MB User Menu > Retail Operations > Cheques for collection >
Outward Clearing Menu > Cheque Collection
 Change the status of cheques for USD 2,000 and USD 2,500 as Returned

 Use MB User Menu > Treasury Operations > Finance > View
Authorised Entries
 View the effect on account balances and also the accounting entries
through Enquiry by using the CHEQUE.COLLECTION record Id

Slide 172
Workshop – 24 Solution

Slide 173
Workshop – 24 Solution

Slide 174
Workshop – 24 Solution

Slide 175
Workshop – 24 Solution

Slide 176
Workshop – 24 Solution

Slide 177
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 178
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 179
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.FIELD, OPERAND and

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 180
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 Field OPERATION
 Permitted operations are CLEARED, RETURNED, RE-BATCH and
DATE.CHANGE
 If Operation is to RE-BATCH, 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 181
Workshop - 25

 Use MB User Menu > Retail Operations > Cheques for collection >
Outward Clearing Menu > Change Outward Clearing Details

 Select records from CHEQUE.COLLECTION, whose CREDIT.ACC.NO

equals your Customer’s Current and Savings account and change the
status as ‘CLEARED’

 Use Function Verify and Verify the record in CHEQUE.CHANGE

 Look at your accounts to see whether this has been effected

Slide 182
Workshop – 25 Solution

Slide 183
CC - Dependency diagram

CUSTOMER
ACCOUNT TELLER
CATEGORY
FUNDS.TRANSFER
CURRENCY

CHEQUE.COLLECTION
FT.COMMISSION.TYPE
FT.CHARGE.TYPE

ACCOUNT.PARAMETER
CQ.PARAMETER ACCOUNT
BC.SORT.CODE (Customer type and Internal)

Slide 184
Summary

 We have so far seen

 the dependencies and linkages between TELLER module and T24 Core
and other applications

 main business features of TELLER and CHEQUE.COLLECTION modules

Slide 185
Thank You

TEMENOS EDUCATION CENTRE

Warning: This document, is protected by copyright law and international treaties. No part of this document
may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose, without the express written permission of TEMENOS HEADQUARTERS SA Unauthorized
reproduction or distribution of this presentation or any portion of it, may result in severe civil and criminal
penalties, and will be prosecuted to the maximum extent possible under applicable law.” Information in this
document is subject to change without notice