GLOBUS USER GUIDE

TELLER

Return to Main
Menu

CHAPTER 35

TELLER

Ref : TT

December 1999

Release G10.2.00

GLOBUS USER GUIDE

TELLER

TABLE OF CONTENTS
35

TELLER ..............................................................................................................35-1
35.1

Introduction .......................................................................................................................35-1

35.2

Transaction Overview.......................................................................................................35-2

35.3
Setting up Teller ................................................................................................................35-3
35.3.1 Accounts .........................................................................................................................35-3
35.3.2 Set up the Vault ..............................................................................................................35-3
35.3.3 Set up the Tills................................................................................................................35-4
35.4

Defining Teller Transactions ............................................................................................35-5

35.5

Opening Tills......................................................................................................................35-7

35.6

Closing Tills .......................................................................................................................35-8

35.7
Stock Control ...................................................................................................................35-10
35.7.1 Internal Account ...........................................................................................................35-10
35.7.2 Travellers Check Accounting .......................................................................................35-12
35.7.3 TELLER.DENOMINATIONS.....................................................................................35-16
35.7.4 Serial Numbers .............................................................................................................35-16
35.8
Multi-line Transactions Overview .................................................................................35-17
35.8.1 Multi-line Usage ...........................................................................................................35-18
35.8.2 The Master & Child Deals............................................................................................35-21
35.8.3 Multi-line Charging ......................................................................................................35-22
35.8.3.1
Modifying multi-line charging ............................................................................35-23
35.8.4 Available Functionality ................................................................................................35-24
35.8.4.1
Copy....................................................................................................................35-24
35.8.4.2
Delete ..................................................................................................................35-24
35.8.4.3
Reverse................................................................................................................35-24
35.8.4.4
Authorise.............................................................................................................35-24
35.9

Printing Advices ..............................................................................................................35-25

35.10 Updating Passbooks (Definition)....................................................................................35-27

35.10.1
Setting the GUI local printer port ............................................................................35-30
35.11

Updating Passbooks (Processing)...................................................................................35-31

35.12

Default Processing ...........................................................................................................35-33

35.13

Enquiries ..........................................................................................................................35-35

35.14

End of Day Processing ....................................................................................................35-37

Ref : TT

December 1999

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35 TELLER
35.1 Introduction
The TELLER module in GLOBUS processes a wide variety of retail transactions. It
incorporates the administration of Tills, processing of local and foreign currency transactions,
Travellers checks, denomination control, passbook updates, advice production, automatic
charges, rate defaulting etc.

Figure 35-1 Head & Standard Teller menus

The wide variety of transactions can be accommodated easily by the menu system, and can be
customised for each user or bank.

Ref : TT

December 1999
35-1

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35.2 Transaction Overview

Although the system processes many different types of transactions, the basic mechanism for
balancing entries, defaulting rates and charges is the same. Hence, all transactions are processed
by the one application (TELLER) but the screen prompts can be varied by tailored VERSION
with specific defaults being controlled by a TELLER.TRANSACTION.
Each transaction prepares two balancing accounting entries (more when charges are present).
Invariably one side will be the 'client' (side 1) and the balancing entry will be the teller cash
account (side 2), i.e. a simple cash deposit will entail a credit to the CUSTOMER ACCOUNT and
a debit to the teller cash ACCOUNT.
In the TELLER system the cash that is held at a teller's position is recorded in an internal
ACCOUNT defined as:
e.g.

CURRENCY-CASH CATEGORY- TELLER ID

USD-10000-0012

The cash CATEGORY is specified in the TELLER.PARAMETER file. It is the balance of these
ACCOUNT records which will be reconciled with the actual cash when the till is closed.
Cheques should be posted directly to collection accounts and not held by teller (defined in
TELLER.TRANSACTION). This allows for easy reconciliation of funds as each cheque is
recorded as a separate entry to this ACCOUNT.
It is possible to specify an exposure date on the teller contract, which is used to decide when the
funds credited will be updated to the cleared balance on the ACCOUNT record. It is also possible
to clear funds on a single teller transaction on multiple dates. This information is entered in the
exposure date ladder fields (EXP.SPLIT.DATE & EXP.SPLIT.AMT). Although the splitting
information can be entered manually, they may also be made to default using either the
TRANSACTION record or the BC.SORT.CODE record. Refer to (Local Clearing & System
Table for further information on setting up exposure date splitting defaults)
It is also possible to default the value date on the credit side by specifying a sort code that
points to a BC.SORT.CODE record set up with a default value date period.

Ref : TT

December 1999
35-2

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35.3 Setting up Teller

The TELLER system may already be set up with a number of transaction types, defaults,
CATEGORY codes, menus, advice formats etc. However, before transactions can be processed
the following steps must be taken:

35.3.1 Accounts
Enter the local currency ACCOUNT records for the CATEGORY codes used by the Teller
system. These are specified in TELLER.PARAMETER (cash account and over/short categories)
and in TELLER.TRANSACTION for the cheque collection accounts.

35.3.2 Set up the Vault

The vault is viewed as a special till by the system, in that it is not opened/closed or balanced like
the other tills, but transfers to and from the vault can still take place. The vault id is entered first
in the TELLER.PARAMETER file (this gives it these special characteristics) and then defined on
the TELLER.ID file.

Figure 35-2 Defining defaults in TELLER.PARAMETER

The vault should be loaded initially using the DATA.CAPTURE system to transfer the cash to the
vault ACCOUNT(s). The vault internal ACCOUNT records are defined as:
CURRENCY-CASH CATEGORY- TELLER ID
e.g.
USD-10000-9999

Ref : TT

(one entered in TELLER.PARAMETER)

December 1999
35-3

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35.3.3 Set up the Tills

Each Till is associated with a USER record and contains one or more currencies. The till
numbers should be entered on the TELLER.ID file and set to Open. Cash can then be transferred
to the tills from the vault using the teller transfer function (this can alternatively be performed
using DATA.CAPTURE by posting directly to the till accounts).

Figure 35-3 Defining teller details in TELLER.ID

Note:
As the till is actually an internal ACCOUNT in GLOBUS its balance can be adjusted by
functions other than TELLER e.g. DATA.CAPTURE or FUNDS.TRANSFER. When closing the
till you are required to enter the cash balance which is then checked against the balance of the till
ACCOUNT (See Opening and Closing Tills).

Ref : TT

December 1999
35-4

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35.4 Defining Teller Transactions

The system will already be set up with a number of TELLER.TRANSACTION records
(cash/cheque deposit, foreign currency buy/sell ) but different types can be added using the
TELLER.TRANSACTION file.
To add a new transaction type the system will require a definition of the defaults to apply when
generating the entries for the transaction. The defaults are TRANSACTION codes, CATEGORY
& department codes, valid currencies, charges, etc.

Figure 35-4 Example TELLER.TRANSACTION record

Essentially the transaction is defined with an input side and a balancing side, e.g. a cash deposit
to a customer account would be constructed of:
Side 1:
Side 2:

Credit to CUSTOMER ACCOUNT

Debit to teller cash ACCOUNT.

The various TRANSACTION codes and CATEGORY codes would be defaulted from the
TELLER.TRANSACTION record.

Ref : TT

December 1999
35-5

Release G10.2.00

GLOBUS USER GUIDE

TELLER

Figure 35-5 TELLER.TRANSACTION selling foreign currency

This example shows the definition of a transaction which sells foreign currency (cash) and
debits a clients local ACCOUNT. The teller would enter the amount of foreign currency
required (side 1) and the system would automatically calculate the local amount required (side
2). This transaction uses CURRENCY.MARKET 10 which would be used to default a different
exchange rate than the standard market of 1. The TELLER.TRANSACTION definition also
shows we will take a commission and the TELLER.PARAMETER record controls whether a
marketing exchange profit should be taken.

Ref : TT

December 1999
35-6

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35.5 Opening Tills

In order for a till (TELLER.ID) to be used it must be opened and assigned to a specific USER.
The system will ensure that only that USER can input transactions to that till. It is possible to
change the current teller/user without closing the till by assigning a different USER. Normally,
each morning it is common practise for the Teller to visually check the cash in their till prior to
beginning the days work. In GLOBUS the Teller would Open the till.

Figure 35-6 Opening a till using TELLER.ID

Ref : TT

December 1999
35-7

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35.6 Closing Tills

Closing of the Till can comprise of several operations.

Balancing the Till by the amount of currencies

Balancing the Till by Entering the denominations (thereby calculating the amount)
Compensating where the Till is short in a currency
Compensating where the Till is over in a currency
Authorising the Till closure

The closing of a till allows the teller to balance the actual contents of the till against the balance
held by the system. On closure the teller is prompted for the till balance (in each currency) and
this is compared to the current system balance.
Alternatively, if the Teller has been set to use denominations the entering of the number of units
in each denomination (i.e. 150 USD100 bills would be USD15000.00) would force the physical
count to agree the till balance to the cash account.
If a difference is found then an override is required. Answering yes to the override will
automatically adjust the system balance to the till balance and post the balancing entries to the
over & short ACCOUNT records defined in the TELLER.PARAMETER file.

Figure 35-7 Closing a till using TELLER.ID

Ref : TT

December 1999
35-8

Release G10.2.00

GLOBUS USER GUIDE

TELLER

When forcing the Till closing by denominations it would be preferable to set-up a special
VERSION that required the input of each number of units of the held currencies. The next
screenshot gives an indication of this but shows the balance as well for information.

Figure 35-8 Closing by Denominations

Note:
When re-opening the till the system will check that the system balance has not moved since the
last closure. If this is the case then the till cannot be opened until the system balance is adjusted
(via DATA.CAPTURE) to match the till closing balance.

Ref : TT

December 1999
35-9

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35.7 Stock Control

It is possible in GLOBUS to keep a track of the currency notes/bills and/or Travellers checks
by currency and denominations. In the case of currency it is useful, or sometimes a mandatory
banking requirement, to track the amount of currency held by denomination, if only to be able
to provide a service to your clients.
Travellers checks are more closely controlled by serial number as well as the denominations
held.
The basic requirements for using this are:

Internal Accounts in the Travellers check currency

TELLER.DENOMINATION records for the face value of the checks

The serial mask/check digit routine on the Account.

35.7.1 Internal Account

We first create a CATEGORY code for the type of Travellers Checks, one for each issuer
would be appropriate. An additional offset CATEGORY code is also required as these
accounts are held on-balance sheet and should have equal and opposite entries at all times.
They may both be re-directed to off-balance sheet reporting if required.
So that we can record the amount/denominations and serial numbers of checks we have
entrusted to our counterparties (Bureaux, Travel Agents and other Banks) we need a third
CATEGORY code.
A simple example would appear :USD-19101-9999
USD-19101-0001
USD-19301-9999
USD-19201-9999

Vault stock of Amex TCs held

Held in Till number 0001
Held in Trust by our Clients
Contra Account for above

dr USD 150,000
dr USD
1,000
dr USD 20,000
cr USD 171,000

You can therefore have a new CATEGORY to record Citicorp T/Cs in, say,
USD-19401-9999, and according to your accounting requirements use the same contra accounts
or one for each issuer.
On the internal Account you will see fields which control the use of denominations and serial
numbers. You can decide to have no control, use denominations, or use serial numbers
(including denominations).

Ref : TT

December 1999
35-10

Release G10.2.00

GLOBUS USER GUIDE

TELLER

The serial check digit/mask can be set independently for each currency where the serial
number range of the issuer is not standard across currencies. Remember that you can also
have multiple issuers for one currency. This is controlled by the CATEGORY code.

Figure 35-9 The Account fields controlling serial/denominations

Ref : TT

December 1999
35-11

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35.7.2 Travellers Check Accounting

The basic accounting for dealing with Travellers Checks is:
Your own receipts/sales:

On receipt of stock for yourself

Debit TC Stock Account
Credit TC Contra Account

On Sale of TC to customer
Debit Client TC Amount and Charges
Credit PL with charges
Credit Stock Account

Pay Issuer for Days Sales

Credit Nostro (in cover of payment)
Debit Contra Account

For Trusted Clients:

On receipt of stock for trusted client

Debit TC Stock Account Trusted Clients
Credit TC Contra Account

On Sale of TC to customer by Trusted Client

Debit Trusted Client TC Amount and Charges
Credit PL with charges
Credit Stock Account Trusted Clients

Pay Issuer for Days Sales

Credit Nostro (in cover of payment)
Debit Contra Account

Of course you may wish to receive all travellers checks into your stock account and then
allocate to your trusted clients from there.
The ENQUIRY TC.STOCK.IN.BANK shows the stock held by currency, denomination and serial
number ranges.

Ref : TT

December 1999
35-12

Release G10.2.00

GLOBUS USER GUIDE

TELLER

Figure 35-10 TC Stock held by Bank

A similar ENQUIRY TC.STOCK.IN.TRUST shows the stock allocated to trusted clients.

Figure 35-11 TC Stock held at Trusted sites

And also the ENQUIRY TC.RETAILER.STOCK shows the stock held at a specific site:

Ref : TT

December 1999
35-13

Release G10.2.00

GLOBUS USER GUIDE

TELLER

Figure 35-12 Stock held by a specific Trusted Client

We have provided an Enquiry, TC.STOCK, which displays the stock by CATEGORY,

CURRENCY and/or TELLER.ID, which can be used to verify the sales made that day.
As usual the ENQUIRY can drill down into the GLOBUS database for more details.

Figure 35-13 The TC.STOCK Enquiry display

We can drill down into the stock account for more detail:

Ref : TT

December 1999
35-14

Release G10.2.00

GLOBUS USER GUIDE

TELLER

Figure 35-14 Selecting the next level of detail

By using the GUI right-click feature the next Enquiry selection is being shown:

Figure 35-15 Right click for next selection

Ref : TT

December 1999
35-15

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35.7.3 TELLER.DENOMINATIONS
These records identify the units, coins and notes that are available. When a transaction
requiring the use of denomination is entered these can be used to identify the stock levels of
each currency at note/coin level.
Example:
USD1000
One thousand US Dollar Bill/TC
USD500
Five Hundred US Dollar Bill/TC
USD5CENT Five Cent coin

1000.000
500.000
0.050

Note the id is for clarity it is the actual value of the unit that is important (it caters for 0 to 3
decimal unit currencies), note the above example does not mean there are 3 decimals in USD.

35.7.4 Serial Numbers

It is advisable to create TELLER.TRANSACTION records and customised VERSIONs for the
Receipt/Sale of Travellers checks, together with others for dealing with clients to whom you
provide Travellers checks on a trust basis.

Ref : TT

December 1999
35-16

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35.8 Multi-line Transactions Overview

Multi-line Teller deals are unique to users operating with either the Desktop or GUI interface.
Whilst the transactions can be viewed via 'classic' text based interface software the newer
features can only be used with GUI or more preferably the Desktop interface.
A multi-line deal is comprised of a Master transaction containing links to each 'child' or 'leg'
and controls the overall charges & accounting of the 'set'.
The words 'leg' and 'child' have the same meaning within the context of multi-leg transactions.
The purpose of multi-line deals is to progress from the original design of Teller which was
essentially a 2 entry transaction (a credit & a debit). For example the sale of one foreign
currency against local. With default charging this could mean that a customer with 3
transactions is charged too much commission overall, or the Teller has to adjust the charges
manually.
Multi-line deals allow the user to process multiple sale transactions whilst building a running
total for charge/commissions. The total of sales is taken into consideration before applying
defaults such as minimum commissions.
To invoke a multi-line deal instead of using F3 to get the next id you must enter the
character '-' in place of the id. This will tell the system to use multi-line transaction
id's.
There are a few considerations to take into account when using Multi-line transactions:

There should only be one client in the set of legs comprising the multi-line deal.
Charges are calculated taking the Multi-line as a complete unit
Charges can be standard or modified at input time
Deal Slips for Multi-line deals are produced via Enquiries
Only Multi-line deals can use the Copy function
Authorisation, Reversal & Copy is done via the Master Deal only

Ref : TT

December 1999
35-17

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35.8.1 Multi-line Usage

Let's consider an example where we are selling 2 Currencies to a client, receiving payment
and commissions in Local currency. We can choose the menu item for this TELLER,SELLFM
and system selects input mode for us.
As it's the first input the systems prompts the User to identify which Teller they are:

Figure 35-16 System prompts for Till Number

It is convenient to allow the system to generate the next id so we type the character '-' in the id
area, without the quotes of course:

Figure 35-17 Entering the '-' character

Which is then transposed into the correct id format as:

Figure 35-18 The system generated id

Entering the data is done the same way as usual, it will only be when we complete the deal
and press F5 or the Commit Data toolbar icon that the special processing starts to become
apparent.

Ref : TT

December 1999
35-18

Release G10.2.00

GLOBUS USER GUIDE

TELLER

Let's carry on with the input:

Figure 35-19 First leg of a Multi-line deal

Note:
The transaction id is TT/00084/00044-01 which indicates we are in Multi-line mode and this is
the first leg of the deal.
Depending on whether the VERSION is set for Zero authoriser input or requires a separate
authoriser the next dialog box may appear different.

Figure 35-20 Commit Data choices

With a zero authoriser the deal can be completed (Finish), this button will not appear at this
stage if the deal needs an independent authoriser.

Figure 35-21 Options without zero authoriser version

Ref : TT

December 1999
35-19

Release G10.2.00

GLOBUS USER GUIDE

TELLER

What do the various choices mean and what do they do?

NEXT
Accepting this choice means you wish to add further deals to the multi-line set. You will be
taken to a fresh input screen and the id will be incremented. In the example earlier we started
with TT/00084/00044-01 and the next number would be TT/00084/00044-02.
MODIFY
This option allows the user to modify the charges across a multi-line deal. It is covered in the
Modifying multi-line charging section of this guide.
EXIT
This simply exits the user from the current deal. Similar to finishing a normal deal.
For Zero Authoriser VERSION only we will also have:
FINISH
It will trigger the authorisation of all the legs of the deal. If any of the legs are on hold, the
authorisation will be stopped. If an override message is generated on any leg which requires
an independent authoriser the deal will of course be left unauthorised (usually status INAO)
until such authorisation is provided.
So we choose NEXT and do the second leg of the deal:

Figure 35-22 Second leg of a Multi-line deal

Again on committing the data we are asked to choose to FINISH, NEXT, MODIFY or EXIT.

Ref : TT

December 1999
35-20

Release G10.2.00

GLOBUS USER GUIDE

TELLER

If we choose FINISH:
The deal and all the legs are authorised. Accounting, especially the charges are finalised*.

If we choose NEXT:
We get a new input screen with the incremented id.

If we choose Exit:
We have an opportunity to come back and do further deals (we defer the FINISH)

If we choose MODIFY:
We get more options as discussed later.

* The accounting updates are processed real-time for each leg, the charges are calculated but
may change with further input.

35.8.2 The Master & Child Deals

Lets have a look at the Master deal raised from the above example:

Figure 35-23 Master Deal

Ref : TT

December 1999
35-21

Release G10.2.00

GLOBUS USER GUIDE

TELLER

We can see the individual id's of the multi-line legs, the accounting information, and in this
case the id's of the accounting items (including the charges).
Not much point making a VERSION for this information.
The child deals are where the majority of the transaction data is held:

Figure 35-24 A child leg of a deal

35.8.3 Multi-line Charging

Charging on Multi line deals differs from single line deals. Each charge type is taken from
each separate TELLER.TRANSACTION used on the legs of the deal. Each Charge type is then
applied across the total balance across all the legs of the deal. The amount of each charge is
stored on the header record for the multi line deal. The charges are all calculated at the Local
currency and converted to the currency of the first leg and posted to the corresponding
account.

Ref : TT

December 1999
35-22

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35.8.3.1 Modifying multi-line charging

At the end of each leg the user has the opportunity to modify the charge over the entire multi
line deal. This is done by pressing the MODIFY button (as shown in Figure 35-20 and Figure
35-8). This then gives the user three options. Waive, Modify and Standard.

Figure 35-25 Modify Options

WAIVE
This option waives completely the charge from the entire multi line deal.
MODIFY
This option takes the user to a new dialog box that asks them which account to post the
charges to. The accounts appear, as buttons with the accounts MNEMONIC or account number if
the is no MNEMONIC. Once the user has chosen the account to post to they are prompted to
choose the amount in the currency of that account to post as a charge. This process is shown
in Figures 35-18 and 35-19 where the user chooses to post 200 Australian dollars to the
account with the MNEMONIC, FREDAUD.
STANDARD
This option reverts the charges of the multi line deal to the default charges that would have
normally been levied across it. These are described in section 35.7.3

Figure 35-26 Choosing Account to Post to

Figure 35-27 Choosing Amount to Post

Ref : TT

December 1999
35-23

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35.8.4 Available Functionality

The standard GLOBUS functions operate slightly differently on multi line TELLER. The
following features are specific to multi-line.

35.8.4.1 Copy

Copy on a multi line TELLER will only work if performed on a HEADER portion of a multi
line deal. It serves to copy the entire multi line deal to a new set of IDs. The copy is done leg
by leg and the header is rebuilt after each individual copy (This means that if between original
input and copy the charges on the TELLER.TRANSACTIONS used change, the copied deal
will have different amounts to the original). All unique data (Cheque serial numbers etc.) is
deleted and the Teller ID is replaced with the ID of the currently signed on TELLER. Once
the copy function has been run and GLOBUS asks the ID of the new deal, pressing F3 or
entering - will work to get the next available ID. There is no way of zero authorising a Multi
line TELLER copy. If any of the legs of a multi line deal are in hold status then the deal will
not copy.

35.8.4.2 Delete

Delete works the same as in other applications. The only difference being if you delete a leg
from a multi line deal it will rebuild the header. If you delete the line header it will then delete
in turn each leg. To maintain the integrity of the deal it will rebuild the header after each leg it
deletes.

35.8.4.3 Reverse

Similar to Copy, reverse only works on header deals. It also will not perform zero
authorisations.

35.8.4.4 Authorise

Authorise can only be performed on header records. It then goes through each leg and
authorises them individually. If any legs are in hold status then the authorisation will not be
allowed.

Ref : TT

December 1999
35-24

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35.9 Printing Advices

Advices can be printed from any teller transaction. Their format and content are user definable
by means of the DEAL.SLIP.FORMAT utility.
To define an advice the details should be entered into the DEAL.SLIP.FORMAT file. This file
essentially describes what data should be extracted from the deal and where on an advice it
should be printed. It also allows free format text, totalling and data to be extracted from
associated files.

Figure 35-28 DEAL.SLIP.FORMAT layout example

This advice can now be linked to an individual transaction by entering the DEAL.SLIP.FORMAT
key(s) into the ADVICE.VERSION field of the TELLER.TRANSACTION record. If the advice
should be printed by default then the PRINT.ADVICE field in the TELLER.TRANSACTION
record should be set to 'Y'. An override will be requested if the teller does not subsequently
produce the advice.

Ref : TT

December 1999
35-25

Release G10.2.00

GLOBUS USER GUIDE

TELLER

Figure 35-29 Linking the deal slip to a TELLER.TRANSACTION

The advice is printed whenever the PRT.HOTKEY is depressed, which is defined on the
TERMINAL record, or if the deal slip button is clicked when using the GUI. The advice can be
printed at any stage during the transaction which means that the advice can be signed by the
customer prior to committing the transaction.

Ref : TT

December 1999
35-26

Release G10.2.00

GLOBUS USER GUIDE

35.10

TELLER

Updating Passbooks (Definition)

Passbooks can be issued to savings accounts (see ACCOUNT.CLASS & ACCOUNT). When an
entry is passed across a passbook ACCOUNT, from any application, the details are recorded and
the TELLER system will update the passbook when it is presented.
The layout of the passbook must be defined in the TELLER.PASSBOOK file. This describes the
physical dimensions of the book in addition to 'header' type information, e.g. CUSTOMER name
& address, and positions of the debit/credit columns. In fact, the entire content of the passbook is
user definable - see TELLER.PASSBOOK for further details.
To set up the system for passbook printing you must do the following:
1.
2.
3.
4.

Define the TELLER.PASSBOOK format.

Define the 'device' on the appropriate TELLER.ID.
Ensure that the TERMINAL can support a local print function.
Set up any printer attributes - see TELLER.ID & PRINTER.ATTRIBUTES.

Figure 35-30 Defining the passbook layout using TELLER.PASSBOOK

Ref : TT

December 1999
35-27

Release G10.2.00

GLOBUS USER GUIDE

TELLER

This definition has the client details printed when a new book is issued (NEW), the balance
carried forward as the first line of each page (FIRST) and the entries themselves on each detail
line (LINE). It also defines the dimensions of the passbook and any printer attributes that should
be downloaded when the device is initiated.

Figure 35-31 Defining the passbook device on TELLER.ID

To inform the system that the teller has access to a passbook device the device name is entered
on the TELLER.ID record. The device name is used to form the key to the
PRINTER.ATTRIBUTES file which is made up from PASSBOOK.DEVICE and the attributes
defined on the TELLER.PASSBOOK record in the ATTRIBUTE field. In this example the key to
the PRINTER.ATTRIBUTES file in our example is therefore ND90.INIT.
To direct the output to the passbook device the TERMINAL record used by the teller must have a
local print sequence defined. The exact sequence will depend on the terminal or terminal
emulator used. It is normally referred to as slave or transparent print mode.

Ref : TT

December 1999
35-28

Release G10.2.00

GLOBUS USER GUIDE

TELLER

Figure 35-32 Defining the local print sequence in the TERMINAL record

Before the data is sent to the printer any defined initialisation sequence is sent and a reset
sequence is sent on completion of the print. This should be used to direct output to the passbook
print head (if the device performs journal printing as well) and to set margins font size etc. In this
way you can ensure that the output will always be consistent and the passbook not corrupted
because the printer has been reset.

Figure 35-33 Attributes stored on the PRINTER.ATTRIBUTES file

Ref : TT

December 1999
35-29

Release G10.2.00

GLOBUS USER GUIDE

TELLER

35.10.1 Setting the GUI local printer port

To set the printer for local printing within GUI, you need to specify the printer port to use.
This is done from the menus/options dialog box as per the screen below:

Figure 35-34 Setting printer port

Note that the port can be local to your PC, lpt1 or lpt2. Or it can be a network port as in the
above example.

Ref : TT

December 1999
35-30

Release G10.2.00

GLOBUS USER GUIDE

35.11

TELLER

Updating Passbooks (Processing)

The passbook will be updated during the <F5> authorisation processing in TELLER. The system
will prompt with:

Figure 35-35 Passbook Prompt

Informing you of the next page, line, the ACCOUNT number, the number of entries left and the
balance on the passbook. You can then :

<OK> to update the book

NN to change the current line
P NN to change the current page
NEW for a new passbook
<CANCEL> or <F1>/<ESC> to cancel.

If <F1> is selected then you will be given the option to abort all passbook entries printed for this
transaction "A", update entries printed so far "U" (leaving outstanding entries for the next print)
or reprint the entries again "R".

Figure 35-36 next screen

Ref : TT

December 1999
35-31

Release G10.2.00

GLOBUS USER GUIDE

TELLER

On completion of the print you will be prompted with "Passbook update ok? Yes, Abort,
Reprint"
If you reply:

Y

A

R

or <CR> then the transaction will be completed.

abort, then all entries will remain on the passbook outstanding list.
the entries will be reprinted from the beginning.

NOTE: When Aborting, it is only the passbook printing phase that is aborted - the current
TELLER transaction is still processed.
All prompts are held on the STATIC.TEXT record PASSBOOK.UPDATE for translation.
To update a passbook with outstanding entries, without processing a transaction, use the
application TELLER.PASSBOOK.UPDATE.

Ref : TT

December 1999
35-32

Release G10.2.00

GLOBUS USER GUIDE

35.12

TELLER

Default Processing

The TELLER system provides an interface to other modules within GLOBUS by use of the
TELLER.DEFAULT application.
Essentially it provides the ability for a TELLER transaction to be created automatically by
another module, thus containing all necessary information - accounts, amounts, rates, charges
etc., which can then be accessed by the teller by simply entering a reference number.
For example, closing an ACCOUNT. If a client wishes to close his ACCOUNT the teller must
perform two transactions within GLOBUS. Firstly the ACCOUNT record must be closed. This
will inform the teller of all outstanding credit/debit interest, charges, tax etc. and secondly the
teller must pay the client the amount due. However, in order to perform the latter he would have
to enter the details from the ACCOUNT.CLOSURE screen into TELLER. What the account
closure procedure actually does is to record the details in TELLER.DEFAULT (id of ACCOUNT
number) and the teller pulls the details automatically into a TELLER transaction by entering the
ACCOUNT number into the OUR.REFERENCE field.

Figure 35-37 Account closure creates a TELLER.DEFAULT record

Ref : TT

December 1999
35-33

Release G10.2.00

GLOBUS USER GUIDE

TELLER

Once the TELLER.DEFAULT record has been processed it cannot be reprocessed. The layout of
TELLER.DEFAULT is exactly the same as TELLER itself but includes ten additional fields
which can include free format data and two fields to record that the record has been processed,
the process date and the transaction reference number.

Figure 35-38 The TELLER.DEFAULT record

The link to TELLER.DEFAULT is through the OUR.REFERENCE field in TELLER. If this is

entered prior to any other data then the associated TELLER.DEFAULT record will be loaded.

Ref : TT

December 1999
35-34

Release G10.2.00

GLOBUS USER GUIDE

35.13

TELLER

Enquiries

The ENQUIRY records provided with the system allow the teller to view his current cash
position (TELLER.POSITION), the cash held by all other tellers & vault (TELLER.OVERALL) and the
entries, in chronological order, passed across the teller cash account(s) (STMT.ENT.TODAY).
There are other Enquiries associated with Travellers checks, detailed previously in this chapter.

Figure 35-39 Individual teller position

Figure 35-40 Overall teller positions including vault

Ref : TT

December 1999
35-35

Release G10.2.00

GLOBUS USER GUIDE

TELLER

This is in addition to the standard List facility which enables the user to list all TELLER
transactions, with any selection criteria in any sort order.
For the STMT.ENT.TODAY ENQUIRY the ACCOUNT to be entered for the selection criteria should
be the teller's cash ACCOUNT (CURRENCY: CATEGORY CODE: TELLER ID).
For client ACCOUNT inquiries, STMT.ENT.TODAY will give the current ACCOUNT balance
including all entries today. The ACCOUNT balance can also be obtained from the main
ACCOUNT record.

Ref : TT

December 1999
35-36

Release G10.2.00

GLOBUS USER GUIDE

35.14

TELLER

End of Day Processing

Two functions are performed at the End of Day for teller transactions TT.END.OF.DAY.
1.

Remove any unauthorised transactions and place on hold.

2.

Transfer all authorised transactions to history.

This means that, under normal circumstances, the transaction file is empty at the start of each
day.
If passbook processing is active then the End of Day process, TELLER.PASSBOOK.STMT, will
update the ACCOUNT.STATEMENT & associated files with the details of passbooks updated
today (see TELLER.PBOOK.PRINTED). This process emulates the updates that would take
place if a statement had been produced - a passbook update is viewed as a statement by the
system.

Ref : TT

December 1999
35-37

Release G10.2.00

GLOBUS USER GUIDE

TELLER

Index of Tables & Figures

Figure 35-1 Head & Standard Teller menus ..................................................................................................35-1
Figure 35-2 Defining defaults in TELLER.PARAMETER ..........................................................................35-3
Figure 35-3 Defining teller details in TELLER.ID ........................................................................................35-4
Figure 35-4 Example TELLER.TRANSACTION record.............................................................................35-5
Figure 35-5 TELLER.TRANSACTION selling foreign currency................................................................35-6
Figure 35-6 Opening a till using TELLER.ID................................................................................................35-7
Figure 35-7 Closing a till using TELLER.ID .................................................................................................35-8
Figure 35-8 Closing by Denominations...........................................................................................................35-9
Figure 35-9 The Account fields controlling serial/denominations..............................................................35-11
Figure 35-10 TC Stock held by Bank............................................................................................................35-13
Figure 35-11 TC Stock held at Trusted sites ................................................................................................35-13
Figure 35-12 Stock held by a specific Trusted Client ..................................................................................35-14
Figure 35-13 The TC.STOCK Enquiry display ...........................................................................................35-14
Figure 35-14 Selecting the next level of detail ..............................................................................................35-15
Figure 35-15 Right click for next selection ...................................................................................................35-15
Figure 35-16 System prompts for Till Number............................................................................................35-18
Figure 35-17 Entering the '-' character ........................................................................................................35-18
Figure 35-18 The system generated id ..........................................................................................................35-18
Figure 35-19 First leg of a Multi-line deal ....................................................................................................35-19
Figure 35-20 Commit Data choices ...............................................................................................................35-19
Figure 35-21 Options without zero authoriser version................................................................................35-19
Figure 35-22 Second leg of a Multi-line deal ................................................................................................35-20
Figure 35-23 Master Deal ..............................................................................................................................35-21
Figure 35-24 A child leg of a deal..................................................................................................................35-22
Figure 35-25 Modify Options ........................................................................................................................35-23
Figure 35-26 Choosing Account to Post to ...................................................................................................35-23
Figure 35-27 Choosing Amount to Post ........................................................................................................35-23
Figure 35-28 DEAL.SLIP.FORMAT layout example .................................................................................35-25
Figure 35-29 Linking the deal slip to a TELLER.TRANSACTION..........................................................35-26
Figure 35-30 Defining the passbook layout using TELLER.PASSBOOK ................................................35-27
Figure 35-31 Defining the passbook device on TELLER.ID.......................................................................35-28
Figure 35-32 Defining the local print sequence in the TERMINAL record ..............................................35-29
Figure 35-33 Attributes stored on the PRINTER.ATTRIBUTES file .......................................................35-29
Figure 35-34 Setting printer port .............................................................................................. ....................35-30
Figure 35-35 Passbook Prompt ................................................................................................... ..................35-31
Figure 35-36 next screen ....................................................................................................... .........................35-31
Figure 35-37 Account closure creates a TELLER.DEFAULT record .......................................................35-33
Figure 35-38 The TELLER.DEFAULT record ......................................................................................... ..35-34
Figure 35-39 Individual teller position .........................................................................................................35-35
Figure 35-40 Overall teller positions including vault ..................................................................................35-35

Ref : TT

December 1999
35-38

Release G10.2.00