Ai PDF

GLOBUS USER GUIDE
ACCOUNTS, INTEREST & CHARGES
Return to Main
Menu
CHAPTER 2
ACCOUNTS, INTEREST &

CHARGES
Ref : AI
April 2000
Release G10.2.02
GLOBUS USER GUIDE
TABLE OF CONTENTS
2
ACCOUNTS, INTEREST & CHARGES .............................................................2-1

2.1 Introduction..............................................................................................................................2-1
2.1.1
Client Account..................................................................................................................2-2
2.1.2
Internal Accounts..............................................................................................................2-5
2.1.3
Account Number Format ..................................................................................................2-6
2.1.3.1 Client format ................................................................................................................2-6
2.1.3.2 Internal Format ............................................................................................................2-6
2.1.4
Account Input ...................................................................................................................2-7
2.1.4.1 Customer Account input ..............................................................................................2-7
2.1.4.2 Internal account input ..................................................................................................2-9
2.1.5
NOSTRO Accounts ........................................................................................................2-10
2.1.6
Account balances............................................................................................................2-10
2.1.6.1 OPEN.ACTUAL.BAL...............................................................................................2-10
2.1.6.2 OPEN.CLEARED.BAL.............................................................................................2-10
2.1.6.3 ONLINE.ACTUAL.BAL ..........................................................................................2-10
2.1.6.4 ONLINE.CLEARED.BAL ........................................................................................2-10
2.1.6.5 WORKING.BALANCE ............................................................................................2-11
2.1.7
Account Closure .............................................................................................................2-11
2.1.8
Interest, Premium Interest, Charges And Statement Parameters ....................................2-13
2.1.9
Interest Calculation Overview ........................................................................................2-16
2.1.10 Interest Capitalisation And Accrual................................................................................2-17
2.1.11 Interest Related Tax And Charges ..................................................................................2-17
2.1.12 Account Maintenance Charges .......................................................................................2-18
2.1.13 Offsetting And Waiving Charges ...................................................................................2-19
2.1.14 Limits..............................................................................................................................2-19
2.1.15 Account Statements ........................................................................................................2-20
2.1.16 Account Violations .........................................................................................................2-21
2.1.17 Account Sweeping..........................................................................................................2-23
2.1.17.1 AC.SWEEP.TYPE.....................................................................................................2-23
2.1.17.1.1 Maintenance (Standard Sweep)........................................................................2-23
2.1.17.1.2 Surplus (Return Sweep)....................................................................................2-23
2.1.17.1.3 Twoway (Sweep and return sweep) .................................................................2-23
2.1.17.2 AC.ACCOUNT.LINK ...............................................................................................2-25
2.1.17.3 Account Sweeping History ........................................................................................2-26
2.2 Payment Netting .....................................................................................................................2-27
2.2.1
Overview ........................................................................................................................2-27
2.2.2
Accounting for net payments..........................................................................................2-29
2.2.3
Installing the payment netting function ..........................................................................2-29
2.2.4
Setting up the payment netting suspense accounts .........................................................2-30
2.2.5
Setting ACCOUNT.PARAMETER for payment netting ...............................................2-31
2.2.6
Use of the NETTING.STATUS field on contracts .........................................................2-31
2.2.7
The NETTING.ENTRY application...............................................................................2-32
2.2.8
The NETTING application .............................................................................................2-32
2.2.9
Parameter Files ...............................................................................................................2-33
2.2.9.1 ACCOUNT.PARAMETER- Controls Account & Defaults ......................................2-33
2.2.9.2 ALT.ACCT.PARAMETER - Alternative Account numbers.....................................2-34
2.2.9.3 POSTING.RESTRICT - Posting restrictions.............................................................2-35
2.2.9.4 REFERAL - Referral .................................................................................................2-36
2.2.9.5 ACCOUNT.CLASS - Defining internal and other accounts .....................................2-37
2.2.9.6 AC.STMT.PARAMETER - Defaults for account statements....................................2-42
2.2.9.7 STMT.GEN.CONDITION - Defaults for statement frequencies...............................2-43
2.2.9.8 ACCOUNT.STATEMENT - Statement details for an individual account ................2-44
Ref : AI
April 2000
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.9 Ad-hoc Interim transaction (MT942) reports.............................................................2-45

2.2.9.10 ACCT.GROUP.CONDITION - Rules for accounts .................................................2-46
2.2.9.11 SAVINGS.PREMIUM - Parameters for premium types ...........................................2-48
2.2.9.12 PREMIUM.DETAILS - Details of premiums paid on account .................................2-49
2.2.9.13 NOTICE.WITHDRAWAL - Notices given on notice accounts ................................2-50
2.2.9.14 NOSTRO.ACCOUNT - Nostro accounts ..................................................................2-51
2.2.9.15 PAYMENT.STOP - Instructions to stop payments ...................................................2-52
2.2.9.16 PAYMENT.STOP.TYPE - Reasons for stopping a payment ....................................2-53
2.2.9.17 NETTING.PARAMETERS.......................................................................................2-54
2.2.9.18 NETTING.AGREEMENT.........................................................................................2-55
2.2.9.19 NETTING.ENTRY....................................................................................................2-56
2.2.9.20 CREATE.NETTING..................................................................................................2-57
2.2.9.21 NETTING ..................................................................................................................2-58
2.2.10 Internal Files ...................................................................................................................2-59
2.2.10.1 ACCT.ACTIVITY - History of account activity .......................................................2-59
2.2.10.2 ACCT.AVAILABILITY - History of availability of funds on Accounts ..................2-60
2.2.11 Reporting ........................................................................................................................2-61
2.2.11.1 Overdraft Report ........................................................................................................2-61
2.3 INTEREST & CHARGES.....................................................................................................2-62
2.3.1
Introduction ....................................................................................................................2-62
2.3.2
Group And Special Conditions .......................................................................................2-62
2.3.3
Interest Calculations .......................................................................................................2-63
2.3.4
Interest Application And Accrual ...................................................................................2-64
2.3.4.1 Daily accrual ..............................................................................................................2-64
2.3.4.2 Waiving of credit interest...........................................................................................2-64
2.3.5
Special Cases ..................................................................................................................2-66
2.3.6
Interest Related Charges .................................................................................................2-66
2.3.7
ACCOUNT maintenance charges...................................................................................2-67
2.3.8
Offsetting And Waiving Charges ...................................................................................2-68
2.3.9
Pre-Notification of debit interest and / or charges ..........................................................2-68
2.3.10 Savings Accounts ...........................................................................................................2-72
2.3.11 Parameter Files ...............................................................................................................2-72
2.3.11.1 CONDITION.PRIORITY..........................................................................................2-73
2.3.11.2 ACCT.GEN.CONDITION ........................................................................................2-73
2.3.11.3 ACCOUNT.ACCRUAL ............................................................................................2-76
2.3.12 Debit Interest Conditions................................................................................................2-77
2.3.12.1 GROUP.DEBIT.INT .................................................................................................2-77
2.3.12.2 ACCOUNT.DEBIT.LIMIT .......................................................................................2-79
2.3.12.3 ACCOUNT.DEBIT.INT............................................................................................2-80
2.3.12.4 GENERAL.CHARGE ...............................................................................................2-81
2.3.12.4.1 Interest Related Charges...................................................................................2-82
2.3.12.4.2 Ledger Fee Charges..........................................................................................2-83
2.3.13 Credit Interest Conditions...............................................................................................2-84
2.3.13.1 GROUP.CREDIT.INT...............................................................................................2-84
2.3.13.2 ACCOUNT.CREDIT.INT .........................................................................................2-86
2.3.14 CHARGES .....................................................................................................................2-87
2.3.14.1 Interest Related Charges ............................................................................................2-87
2.3.14.2 Ledger Fee Charges ...................................................................................................2-87
2.3.14.3 DEBIT.INT.ADDON.................................................................................................2-88
2.3.14.4 HIGHEST.DEBIT .....................................................................................................2-89
2.3.14.5 GOVERNMENT.MARGIN ......................................................................................2-91
2.3.14.6 INTEREST.STATEMENT........................................................................................2-92
2.3.14.7 BALANCE.REQUIREMENT ...................................................................................2-93
2.3.14.8 NUMBER.OF.CREDIT.............................................................................................2-94
2.3.14.9 NUMBER.OF.DEBIT ...............................................................................................2-95
2.3.14.10 TURNOVER.CREDIT .........................................................................................2-96
Ref : AI
April 2000
Release G10.2.02
GLOBUS USER GUIDE
2.3.14.11 TURNOVER.DEBIT ............................................................................................2-97

2.3.14.12 TRANSACTION.CHARGE .................................................................................2-98
2.3.15 Interest And Charges Processing ....................................................................................2-99
2.3.16 Interest Accruals .............................................................................................................2-99
2.3.16.1 ACCR.ACCT.CR and ACCR.ACCT.CR2 ................................................................2-99
2.3.16.2 ACCR.ACCT.DR and ACCR.ACCT.DR2................................................................2-99
2.3.16.3 ACCR.ACCT.CH ......................................................................................................2-99
2.3.17 Interest Capitalisation ...................................................................................................2-100
2.3.17.1 GROUP.CAPITALISATION ..................................................................................2-100
2.3.17.2 ACCT.CAPITALISATION .....................................................................................2-101
2.3.17.3 ACCT.INTERIM.CAP ............................................................................................2-101
2.3.17.4 ACCT.SUSP.SETTLE.............................................................................................2-102
2.3.17.5 TABLE.CAPITALIS.CORR ...................................................................................2-102
2.3.18 ENQUIRIES .................................................................................................................2-103
2.3.18.1 INFO.ACCT.CR and INFO.ACCT.CR2 .................................................................2-103
2.3.18.2 INFO.ACCT.DR and INFO.ACCT.DR2.................................................................2-103
2.3.18.3 INFO.ACCT.CH......................................................................................................2-103
2.3.18.4 INFO.ACCT.PREMIUM.........................................................................................2-103
2.3.18.5 ACC.CURRENT.INT ..............................................................................................2-104
2.3.19 FILES USED ................................................................................................................2-105
2.3.19.1 ACCT.ACTIVITY...................................................................................................2-105
2.3.19.2 STMT.ACCT.CR and STMT.ACCT.CR2...............................................................2-106
2.3.19.3 STMT.ACCT.DR and STMT.ACCT.DR2 ..............................................................2-106
2.3.19.4 STMT.ACCT.CH.....................................................................................................2-108
2.3.19.5 CORR.ACCT.CR and CORR.ACCT.CR2 ..............................................................2-109
2.3.19.6 CORR.ACCT.DR and CORR.ACCT.DR2..............................................................2-110
2.3.19.7 ACCR.ACCT.TRAN.CH.........................................................................................2-111
2.3.19.8 STMT.ACCT.TRAN.CH.........................................................................................2-111
2.3.20 END OF DAY ..............................................................................................................2-113
2.3.20.1 INT.POST.NEXT ....................................................................................................2-113
2.3.20.2 EOD.ACCT.SUSP ...................................................................................................2-113
2.3.20.3 EOD.ACCT.ACTIVITY..........................................................................................2-113
2.3.20.4 EOD.UPDATE.ACCT.ACT....................................................................................2-113
2.3.20.5 EOD.CAPITALIS.CORR ........................................................................................2-113
2.3.20.6 EOD.CAPITALISATION .......................................................................................2-114
2.3.20.7 DAILY.CHARGES.EOD ........................................................................................2-114
2.3.20.8 EOD.REBUILD.ACCT.GRP.COND ......................................................................2-114
2.3.20.9 EOD.REBUILD.ACCT.AVAIL ..............................................................................2-114
2.3.20.10 EOD.ACCRUAL ................................................................................................2-114
2.3.21 DELIVERY ..................................................................................................................2-115
2.4 CHEQUE ISSUE & MANAGEMENT...............................................................................2-116
2.4.1
Introduction ..................................................................................................................2-116
2.4.2
Setting up ACCOUNT.PARAMETER.........................................................................2-117
2.4.3
Issuing Cheques to Customers......................................................................................2-118
2.4.3.1 Setting up a cheque type ..........................................................................................2-118
2.4.3.2 Setting up a charging structure for the issuing of cheques.......................................2-118
2.4.3.3 Linking a transaction code to a cheque type ............................................................2-119
2.4.3.4 Issuing & Registering of Cheques ...........................................................................2-120
2.4.4
Issuing Bank Drafts ......................................................................................................2-121
2.4.5
TELLER using cheque number ....................................................................................2-121
2.4.5.1 Presenting a cheque presented earlier ......................................................................2-122
2.4.5.2 Stopped Cheques......................................................................................................2-123
2.4.5.3 Returned Cheques ....................................................................................................2-126
2.5 Deposited Cheque Collection...............................................................................................2-127
2.5.1
Set-up............................................................................................................................2-127
Ref : AI
April 2000
Release G10.2.02
GLOBUS USER GUIDE
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.8
2.5.9
Transaction codes .........................................................................................................2-127

Category Code ..............................................................................................................2-129
Suspense Accounts .......................................................................................................2-130
Account Parameter .......................................................................................................2-131
Bank Sort code .............................................................................................................2-132
FT LOCAL CLEARING and FT BC PARAMETER ..................................................2-132
Cheque collection .........................................................................................................2-133
Cheque Batch................................................................................................................2-141
2.6 Bulk Accrual of Interest and Charges................................................................................2-147

2.6.1
Introduction ..................................................................................................................2-147
2.6.2
Accounts to be accrued in bulk.....................................................................................2-148
2.6.2.1 Setting Group Accrual Parameter ...........................................................................2-148
2.6.2.2 Switching Standard Account Accrual Off................................................................2-150
2.6.2.3 Rebuilding Group Accrual.......................................................................................2-151
2.6.2.4 Calculation of Daily Accrual Figures ......................................................................2-153
2.6.2.5 Posting of Group Accrual ........................................................................................2-154
Ref : AI
April 2000
Release G10.2.02
GLOBUS USER GUIDE
2 ACCOUNTS, INTEREST & CHARGES

2.1
Introduction
The ACCOUNT module (and its Interest & Charges routines) caters for the creation,
maintenance and control of all types of accounts handled by GLOBUS. It also provides:
Calculation of interest on client accounts
Calculation of premium interest on client accounts
Calculation of charges relating to the maintenance and servicing of accounts
Pre-notification of debit interest and/or charges on client accounts
Production of statements, overdraft and referral reports
Accounts can be classified as one of two types, client accounts or internal accounts. Client
accounts are those owned by an external customer such as current accounts, savings accounts
etc. Internal accounts are those owned by ourselves such as suspense accounts.
There are no actual general ledger accounts in GLOBUS. To allow for accurate and detailed
accounting analysis, profit and loss balances are not held in an account, instead consolidated
balances and movements are kept at the lowest reporting level by use of specific category
codes which are used by all applications to record profit and loss entries. The usage of these
virtual general ledger accounts is explained in the Reporting chapter of the user guide.
Ref : AI
April 2000
2-1
Release G10.2.02
GLOBUS USER GUIDE
2.1.1 Client Account

A client ACCOUNT can be one of many different types, a simple current account, overdraft or
savings accounts and many more. GLOBUS strength lies in the flexibility with which new
account types can be added to it in order to meet the banks ongoing requirements.
GLOBUS is a CUSTOMER orientated system. An ACCOUNT is connected to a CUSTOMER
record and thus the owner and address details are not entered on the individual ACCOUNT.
This eliminates the need for extensive maintenance of customer information such as when a
customer changes their address.
When GLOBUS is installed, part of the implementation process is to configure the types of
accounts the bank wishes to offer and their characteristics. Typically this would include the
debit/credit interest rates, interest & charges capitalisation frequencies, statement production
cycle, other account group conditions etc. Once these key files are set up the addition of a new
client ACCOUNT is very simple.
The processing options available on client accounts include:
Posting Restrictions
Referral Conditions
Alternate Account ids
Mnemonic codes
Joint account holders
Liquidation of interest to another ACCOUNT
Pre-Notification of debit interest due
Charges capitalised to another ACCOUNT
Pre-Notification of charges due
Interest & Charges settled in currencies other than the ACCOUNT currency
Combining balances across accounts before interest calculations
System information fields such as balances etc.
These options are detailed later in this guide.
Ref : AI
April 2000
2-2
Release G10.2.02
GLOBUS USER GUIDE
An example of a simple current account is shown below:
Figure 2-1 Simple Current ACCOUNT
In , the ACCOUNT 0000010146 has a field MNEMONIC which contains a value of DBLUSD.
This mnemonic can be entered into any standard GLOBUS ACCOUNT field and is translated
automatically into the correct ACCOUNT number.
Ref : AI
April 2000
2-3
Release G10.2.02
GLOBUS USER GUIDE
A NOSTRO account is a special type of account, identified by the CATEGORY code and the
LIMIT.REF field containing the word NOSTRO. As it is a shadow of the VOSTRO account
maintained by the correspondent the client id is informational the real account owner is you.
An example of a NOSTRO account is shown below:
Figure 2-2 ACCOUNT - Example Nostro account
When setting up a Nostro Account the client of the ACCOUNT should not receive a
statement, or debit/credit advices. These should be re-directed to your reconciliations
department. Create a print re-direct address for the correspondent (e.g. US0010001.C100002.PRINT.2 on DE.ADDRESS) then in DE.PRODUCT create a record for the Nostro
Account (e.g. US0010001.A-0000010022.ALL.ALL) this will prevent any advices for this
ACCOUNT being sent to your correspondent.
For information on the GLOBUS Reconciliations module, its capabilities and how it can
assist your Reconciliation Department in their daily workflow please refer to the User Guide
chapter for that module.
Ref : AI
April 2000
2-4
Release G10.2.02
GLOBUS USER GUIDE
2.1.2 Internal Accounts

Internal accounts are not related to a CUSTOMER record, and are used for maintenance of
cash accounts, accrued profits, suspense accounts, tax and capital accounts. Since there is no
CUSTOMER record related to internal accounts, details such as account title and short title
need to be specified when the account is created.
The account number of an internal account consists of the currency, category and a
subdivision number.
An example of a simple internal account, a cash account, is shown below:
Figure 2-3 Simple internal ACCOUNT (Cash Account)
Ref : AI
April 2000
2-5
Release G10.2.02
GLOBUS USER GUIDE
2.1.3 Account Number Format

GLOBUS can use many different Account id structures, these can be any of the ones we
supply or new checkdigit types can be created on request. To match existing styles you can
also apply an Account mask which makes it easier for the User to visualise the account is
structure.
2.1.3.1 Client format
The ACCOUNT number on client accounts is a number of up to 16 characters. The format of

the number can be validated if required, for example by the use of check digits or the
automatic inclusion of the CUSTOMER number.
The length and checkdigit type used for an ACCOUNT is defined in the COMPANY
application, in the fields:
ACCT.CHECKDIG.TYPE
ACC.BKNO.PREFIX
ACCOUNT.MASK
Please refer to the HELPTEXT on these fields for the settings you require.
2.1.3.2 Internal Format
The format of an internal account consists of the currency, the category code of the account
and a sequential number. This structure is shown below:
USD - 10100 - 0001
|
|
|
=SWIFT CURRENCY CODE e.g. FRF, USD,
|
|
=CATEGORY CODE (range 10000-19999)
|
=SEQUENTIAL NUMBER (0001-9999)
Figure 2-4 Format of an internal account number
Some fixed internal ACCOUNT records are required by GLOBUS applications and must exist
prior to entering any transactions on these applications. These are listed in the
ACCOUNT.CLASS records and are detailed in the field RECORD.TYPE. It is recommended
that the local currency ACCOUNT records be input manually. GLOBUS is able to open any
foreign currency ACCOUNT required automatically, providing that one exists for the specific
ACCOUNT category.
The ACCOUNT will have the text RECORD.AUTOMATICALLY.OPENED set in fields
ACCOUNT.TITLE.1; ACCOUNT.TITLE.2 and SHORT.TITLE, these can then be amended
whenever convenient.
Ref : AI
April 2000
2-6
Release G10.2.02
GLOBUS USER GUIDE
2.1.4 Account Input

2.1.4.1 Customer Account input
Customer accounts are only opened manually. The ACCOUNT number of a CUSTOMER
ACCOUNT can be up to 16 numeric characters, subject to local restrictions and requirements;
such as check digit validation.
Figure 2-5 ACCOUNT - Details of a customer account
Some details, such as the ACCOUNT title, CUSTOMER who owns the ACCOUNT,
CATEGORY and CURRENCY, are input at this time. However, an extensive range of
characteristics are defined on related parameters tables. This enables an ACCOUNT to be
opened with a minimum of details minimum of details required on input and majority of the
processing characteristics defaulted from group level parameters. Consequently, when these
characteristics change, perhaps because of a change in business policy, the modification need
only be applied once to the group level parameter, which automatically processes all the
related ACCOUNT records with the new settings.
Ref : AI
April 2000
2-7
Release G10.2.02
GLOBUS USER GUIDE
The types of characteristics that can be set up on the related parameters include:
Interest rates and methods

Interest capitalisation frequency
Statement generation
Charges
Posting restrictions.
Premium Interest rates methods & capitalisation frequency
Other parameters defining validation rules for transactions over accounts
The majority of these parameters are linked to the accounts CONDITION.GROUP. The
CONDITION.GROUP defines the way the ACCOUNT is processed. It is set automatically by
using characteristics pre-defined by the user. For example the CONDITION.GROUP for a
current account for corporate clients may be different to that for private clients. This might
mean that corporate clients received statements daily by default whereas private clients
received them monthly.
Generally these characteristics are defaulted by CONDITION.GROUP but they may be
overridden for particular accounts whenever required. For example the default statement
frequency for private clients in the above example was monthly, however this could be set too
weekly for a particular ACCOUNT.
Ref : AI
April 2000
2-8
Release G10.2.02
GLOBUS USER GUIDE
2.1.4.2 Internal account input
Internal ACCOUNT records may be opened manually or automatically. The id of an internal

account consists of a CURRENCY, CATEGORY and a suffix.
Figure 2-6 Example of an internal Account
Ref : AI
April 2000
2-9
Release G10.2.02
GLOBUS USER GUIDE
2.1.5 NOSTRO Accounts

Nostro ACCOUNT records have a key in the same format as a CUSTOMER ACCOUNT and
the account servicing bank is treated as a CUSTOMER for most purposes.
2.1.6 Account balances
The following balances are held on the ACCOUNT record in GLOBUS.
2.1.6.1 OPEN.ACTUAL.BAL
This field contains the Actual Non-Cleared Balance or Ledger Balance of the Account as at
the start of the day.
2.1.6.2 OPEN.CLEARED.BAL
This field contains the Cleared Balance of the Account as at the start of the day. This includes
the value of all entries over the Account except any credit entries or reversed debit entries
with Exposure Dates in the future.
For credit and reversal debit entries with Exposure Dates in the future, this field is updated in
the start of day processing on the appropriate date.
It is possible to split a single entries amount to clear in separate periods. This feature is called
exposure date splitting. For more information on this feature refer to the following sections in
the user guide (Local Clearing, Application Accounting, System Tables & Teller)
2.1.6.3 ONLINE.ACTUAL.BAL
This field contains the most up to date Actual Balance of the Account. This is the same as the
actual balance at the start of day (OPEN.ACTUAL.BAL) plus the value of all fully Authorised
entries since the start of day.
2.1.6.4 ONLINE.CLEARED.BAL
This field contains the most up to date Cleared Balance of the Account. This is the same as
the cleared balance at the start of day (OPEN.CLEARED.BAL) plus the value of all fully
Authorised entries since the start of day excepting any credits or reversal debit entries with
future Exposure Dates.
For credit and reversal debit entries with Exposure Dates in the future, this field is updated at
start of day processing on the appropriate date.
Ref : AI
April 2000
2-10
Release G10.2.02
GLOBUS USER GUIDE
2.1.6.5 WORKING.BALANCE
This field contains the present balance of the Account, which is used, for checks done by the
LIMITS System in GLOBUS. At the start of day this figure will be the same as the cleared
balance figure (ONLINE.CLEARED.BAL).
For Nostros and Internal Accounts the field is updated by all accounting entries when they
have been fully Authorised. For other Customer Accounts it is updated by debit entries when
they are Validated and by credit entries when they have been fully Authorised excepting for
any credit or reversal debit entries with Exposure Dates in the future.
For credit and reversal debit entries with Exposure Dates in the future, this field is updated in
start of day processing on the appropriate date.
Funds on an Account can be locked (also known as blocked or held amounts) by using the
two fields FROM.DATE and LOCKED.AMOUNT.
An override will be required where an application takes an Account below the value of all the
locked funds.
2.1.7 Account Closure

The procedure for closing an ACCOUNT is as follows:
Using application ACCOUNT.CLOSURE you need to enter the ACCOUNT number, as the
record id and the system will calculate outstanding interest, premium interest and charges.
You may amend the capitalisation date, settlement account and the posting restriction to be
placed on the ACCOUNT record.
The example screen in Figure 2-7 ACCOUNT.CLOSURE shows the ACCOUNT.CLOSURE
record:
Ref : AI
April 2000
2-11
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-7 ACCOUNT.CLOSURE
Interest and Charges are calculated on the value dated balances and ACCOUNT activity
statistics stored in the ACCT.ACTIVITY file, taking into account all entries over the
ACCOUNT up to and including the last end of day processing.
When an ACCOUNT is flagged for closure, any entries over the ACCOUNT require an
override.
During end of day processing the following working day, if the OPEN.ACTUAL.BAL and
OPEN.CLEARED.BAL are both zero, the ACCOUNT is closed.
If either balance is not zero, the ACCOUNT remains open in which case interest capitalisation
can be set to occur every End of Day, only in the first End of Day or never at all, depending
on how the parameter CAP.INTEREST was set at the time of closing the ACCOUNT.
When the ACCOUNT is closed, it is removed from the live ACCOUNT file and written to the
ACCOUNT History file (ACCOUNT$HIS) with a RECORD.STATUS of CLOSED, a closing
statement is produced and any remaining Standing Orders are cancelled.
Ref : AI
April 2000
2-12
Release G10.2.02
GLOBUS USER GUIDE
2.1.8 Interest, Premium Interest, Charges And Statement Parameters

When an ACCOUNT is opened a number of characteristics related to the processing of
interest, premium interest, charges, and statements are defined using a flexible series of
parameters. These parameters are linked to the accounts CONDITION.GROUP.
The CONDITION.GROUP is assigned automatically using information in the fields specified in
CONDITION.PRIORITY. For example you can specify that the ACCOUNT processing
characteristics (i.e. the CONDITION.GROUP) are to be set on the basis of the SECTOR of the
client and the CATEGORY code of the ACCOUNT being opened. This would enable different
ACCOUNT types for based on the kind of client. This would be set on the
CONDITION.PRIORITY table.
Whenever an ACCOUNT is opened, GLOBUS assigns a CONDITION.GROUP to the
ACCOUNT depending on the criteria specified in the ACCT.GEN.CONDITION table. The
CONDITION.GROUP defines the type of processing that GLOBUS will perform on the
ACCOUNT.
A wide range of other parameters are then linked to this processing group defining the
processing for the ACCOUNT such as when interest is to be applied, how often statements are
to be produced, how charges are to be levied on the account, etc.
Often these specifications may be overridden for a particular ACCOUNT. For example the
GROUP.DEBIT.INT parameter specifies the debit interest rate to be applied by default to all
the ACCOUNT records in that CONDITION.GROUP. However if the debit rate for a particular
ACCOUNT needs to be different then a record will be entered on the ACCOUNT.DEBIT.INT
table.
Ref : AI
April 2000
2-13
Release G10.2.02
GLOBUS USER GUIDE
The structure of tables controlling interest, charges and statements is shown below.
ACCOUNT USING
INDIVIDUAL SETTINGS
ACCOUNT.DEBIT.INT
ACCOUNT.CREDIT.INT
DEBIT.INT.ADDON
GENERAL.CHARGE
GOVERNMENT.MARGIN
HIGHEST.DEBIT
BALANCE.REQUIREMENT
INTEREST.STAT EMENT
TURNOVER.DEBIT
TURNOVER.CREDIT
TRANSACTION.CHARGE
NUMBER.OF.DEBIT
NUMBER.OF.CREDIT
ACCT.STATEMENT.CHARGE
HIGHEST DEBIT CHARGE
TA X
Figure 2-8 Structure of the account default tables
Ref : AI
April 2000
2-14
Release G10.2.02
GLOBUS USER GUIDE
PRIORITY SETTING
LEVEL
CONDITION.PRIORITY
Record = ACCOUNT
Record = STATEMEN T
CATEGORY
SECTOR
INDUSTRY
ACCT.GEN.CONDITION
STMT.GEN.CONDITION
record - 1 to 9999
record - 1 to 9999
TARGE T
CUSTOMER.S TA TUS
COUNTRY
DECISION LEVEL
GROUP.CAPITALISATION
record - 1 to 9999
f or RESIDENCE
f or NATIONALITY
GROUP
LEVEL
GROUP.CONDITION
GROUP CCY
LEVEL
GROUP.DEBIT.INT
GENERAL.CHARGE
GROUP.CREDIT.INT
ACCT.GROUP.CONDITIO
N
ACCOUNT USING GROUP

CONDITIONS
DEBIT.INT.ADDON
BALANCE.REQUIREMENT
GOVERNMENT.MARGIN
TURNOVER.DEBIT
SAVINGS.PREMIUM
HIGHEST.DEBIT
TURNOVER.CREDIT
INTEREST.STAT EMENT
TRANSACTION.CHARGE
NUMBER.OF.DEBIT
NUMBER.OF.CREDIT
ACCT.STATEMENT.CHARGE
HIGHEST DEBIT
CHARGE
TA X
Figure 2-9 Structure of the group tables
Ref : AI
April 2000
2-15
Release G10.2.02
GLOBUS USER GUIDE
2.1.9 Interest Calculation Overview

The Interest and Charges module using the following parameters control interest calculation
in the Account module, they are explained in more detail in the latter part of this chapter.
GROUP.DEBIT.INT
GROUP.CREDIT.INT
ACCOUNT.DEBIT.INT
ACCOUNT.CREDIT.INT
Interest may be calculated on a daily, average, or highest/minimum balance basis using value
dated balances.
The movements/balances on different accounts in the same currency can be combined and
interest calculated on the net result.
Rates can be fixed or linked to basic rates plus or minus a margin.
Different rates can be specified for different balance levels and may be linked to the same or
different basic rates. The rates may apply to the whole of the balance or to the part between
two balance levels.
Using group level conditions, it is possible to use the limits on individual accounts as the first
level for debit interest so that one rate can be charged up to the limit on any account and
another rate when the limit has been exceeded.
Interest can be calculated on a 366/365, 366/360, 360/365, 366/366, 360/366 or 360/360 days
basis.
Back valued entries generate automatic adjustments to previously calculated interest.
For any accounts where interest conditions or rates are changed with effect prior to the last
interest application, the system generates adjustments on request.
Ref : AI
April 2000
2-16
Release G10.2.02
GLOBUS USER GUIDE
2.1.10 Interest Capitalisation And Accrual

Interest capitalisation and accrual for the ACCOUNT module is controlled by the Interest and
Charges module using the following parameters:
GROUP.CAPITALISATION
ACCT.CAPITALISATION
ACCT.INTERIM.CAP
Interest may be capitalised daily, every business day, every 1-9 weeks, twice a month (on the
15th and the last day of the month) or every 1-99 months (using any day of the month). The
capitalisation dates can be specified at group or account level. Cycles may be different for
debit and credit interest.
Special interim capitalisation may be requested without affecting the regular cycle.
It is possible to accrue interest normally on a monthly basis and specify certain types of
accounts with daily accrual.
2.1.11 Interest Related Tax And Charges

Charges and taxes in the ACCOUNT module are controlled by the Interest and Charges
module.
Tax on interest is calculated at application time and is controlled using the TAX application.
Certain additional charges based on the debit interest application may be applied on the same
date, these include:
Charge Type
DEBIT.INT.ADDON.
GOVERNMENT.MARGIN
HIGHEST.DEBIT
INTEREST.STATEMENT
Description
a percentage of the amount of debit interest to be
applied
an additional interest rate applied to each debit interest
calculation.
a percentage of the largest debit balance.
a charge for providing a detailed interest statement
when debit interest is applied.
Table 2-1 Standard Charge types
Ref : AI
April 2000
2-17
Release G10.2.02
GLOBUS USER GUIDE
2.1.12 Account Maintenance Charges

The Interest and Charges module controls all maintenance charges in the ACCOUNT module.
Account maintenance charges may be levied monthly, quarterly or six monthly, always at the
end of the appropriate month. The same capitalisation cycle is used for all types of
ACCOUNT.
Charges are calculated from the second month of opening an account by default. If it is
desired to calculate the charges from the month in which the account was opened instead, a
flag viz. CHARGE.FIRST.MONTH must be set to a value of YES on the
ACCOUNT.PARAMETER application.
There are main types of charges, as follows:
Charge Type
BALANCE.REQUIREMENT
TRANSACTION.CHARGE
NUMBER.OF.CREDIT
NUMBER.OF.DEBIT
TURNOVER.CREDIT
TURNOVER.DEBIT
HIGHEST DEBIT
Description
A flat charge can be levied if a certain average or
minimum balance is not maintained. A range of
charges for different balances may be specified.
Charges can be made for the specific transactions
passed over an ACCOUNT.
This table allows a fixed charge to be specified for
each chargeable credit entry, which passed over an
ACCOUNT during the Capitalisation period.
This table allows a fixed charge to be specified for
each chargeable debit entry, which passed over an
ACCOUNT during the Capitalisation period.
This table allows for a percentage charge on the total
amount of credit entries
This table allows for a percentage charge on the total
amount of debit entries
A percentage of the largest balance applied on
charge frequency.
Table 2-2 Maintenance Charges
Charges may be combined into one account entry or applied separately. Free, minimum and
maximum amounts can be specified for each charge. Separate charges can be defined for
specific currencies and local currency charges used as the default for all non-specified
currencies.
Ref : AI
April 2000
2-18
Release G10.2.02
GLOBUS USER GUIDE
2.1.13 Offsetting And Waiving Charges

On specific ACCOUNT records, charges may be calculated for information only and then
waived. Charges may also be waived if a certain average or minimum balance is maintained,
if the amount of the charge is below a value worth charging or if the ACCOUNT has not been
into debit.
It is possible to specify that charges do not apply to foreign currency accounts.
Notional credit interest can be calculated and offset against the charges.
2.1.14 Limits
The LIMIT.REFERENCE field on the ACCOUNT connects the ACCOUNT with the LIMIT
system. Limits are checked at each on-line transaction and at end of day. The value in this
field will automatically be set to NOSTRO for that type of ACCOUNT or a valid
LIMIT.REFERENCE relating to a product or global LIMIT.
For certain types of limit product it is possible to net credit account balances and debit
account balances (the usual practice is to only include debit balances for limits checking). If
an account with a credit balance is to be included in the limits checking, the field
ALLOW.NETTING should be set to YES.
Ref : AI
April 2000
2-19
Release G10.2.02
GLOBUS USER GUIDE
2.1.15 Account Statements

Account statements show details of all entries over the ACCOUNT since the last statement.
Entries are listed in transaction date sequence and may show both transaction date and value
date.
Statements can be produced every working day, every 1-9 weeks, twice a month (on the 15th
and the last day of the month) or every 1-99 months (using any day of the month as the
anniversary or on the month end date).
Two statement cycles may be specified for each account, e.g. weekly and monthly.
These cycles may be independent or combined:
Separate : Statements for each cycle show details of all entries since the last statement in the
same cycle, regardless of the other cycle.
Combined : Statements are produced on the dates specified by both cycles, but only contain
details of entries since the last statement from either cycle.
If there have been no entries since the last statement, the statement may be suppressed unless
six months have elapsed.
Special interim statements, showing details of all entries since the last regular cycle 1
statement, may be produced any day without affecting the regular statement cycles.
When a duplicate / interim statement is produced on request a charge may be applied for the
issue of the statement.
This charge is usually deferred until the next time the statement is printed in accordance with
the statement frequency. The charge may now be made immediately, together with the
production of a debit advice detailing the charge made, when the duplicate statement is
produced.
The field PRINT.ROUTINE on the PRINT.STATEMENT file can be used to specify the name of
an external routine written by the users that will be called to print the statement. If this field is
populated the program will call this routine and ignore the normal printing process.
Another field CHARGE.ROUTINE on the PRINT.STATEMENT file could used to specify the
name of an external routine written by the users that will be called to apply an immediate
charge to the account for which the statement is being reprinted.
The alternative method of raising the charge accounting entries would be to use the Generic
Accounting Interface.
Ref : AI
April 2000
2-20
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-10 PRINT.STATEMENT - Example
2.1.16 Account Violations

The AC.VIOLATION file is used to record and report violations that occur on an account
within
a
statement
period.
All
transactions
eligible
(i.e.
defined
in
ACCT.GROUP.CONDITION) are recorded in this file whether or not the number of
transactions equals the threshold concerned. If the number of eligible transactions equals or
exceeds the TXN.THRESHOLD for the ACCT.GROUP.CONDITION, the AC.VIOLATION
record is flagged as being in violation (i.e. VIOLATION.STATUS = Y). This file is updated
daily during the End-of-Day processing but may also be updated manually if a transaction
needs to be added or a status changed. Transactions are held by STMT.ENTRY id. Records
remain on the AC.VIOLATION file for the length of time defined in the RETENTION.PERIOD
field on the relevant ACCT.GROUP.CONDITION.
Account violations occurring prior to the completion of a statement period will be generated
in the End-Of-Day processing and held on the AC.VIOLATION file with an id composed of
the account number alone.
On completion of the statement period all entries on the AC.VIOLATION file held with an id
of the account number, will be amalgamated into the violation record for the statement period
just passed, i.e. that held on the AC.VIOLATION file with an id composed of both the account
number and the statement period having just passed.
Ref : AI
April 2000
2-21
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-11 Example of AC.VIOLATION record
Ref : AI
April 2000
2-22
Release G10.2.02
GLOBUS USER GUIDE
2.1.17 Account Sweeping

Account Sweeping is a mechanism for creating automatic payments across a number of
accounts at the EOD phase based on the balance reaching a predefined Trigger amount.
This functionality runs off two main tables, AC.ACCOUNT.LINK, which defines which
accounts are to be linked together in a given sweep, and AC.SWEEP.TYPE, which defines the
different styles of sweep available.
Sweeping happens at the End of Day during SYSTEM.END.OF.DAY2 in a job called
AC.EOD.ACCOUNT.SWEEP. The resulting movements are then stored on the live file
AC.ACCOUNT.SWEEP.HIST.
2.1.17.1 AC.SWEEP.TYPE
Sweep types can be defined with different transaction codes for the sweep or return sweep.
There is also the facility to plug in a routine for calculating the amount to sweep. If this
routine were not present then the processing would move to do a default sweep to the absolute
minimum or maximum value as set on the link record. Lastly, for different sweep types you
can define the direction of the sweep as Maintenance, Surplus or Twoway.
2.1.17.1.1 Maintenance (Standard Sweep)
This sweep involves sweeping from the from account to the to account when the to account
falls below its minimum limit.
2.1.17.1.2 Surplus (Return Sweep)
This sweep involves the sweeping of funds from the to account to the from account when the
balance in the to account goes above the maximum value
2.1.17.1.3 Twoway (Sweep and return sweep)
This style is simply a Maintenance sweep and a surplus sweep in one link. In this case, the
maintenance sweep always goes first.
In all cases, either the amount of the sweep is defined in the API routine or it is enough to
bring the balance back to the relevant maximum or minimum amount. The from account can
never be brought below its minimum amount.
There is also the facility to enable the sweeping mechanism to take into account the limits of
the accounts used when calculating trigger amounts. This would mean an account with a
trigger amount of 200 and a Limit of 100 would trigger when the balance passed 100. This
is achieved by setting the USE.LIMITS field to YES
For return sweeps the funds will always go into the first account in the ACCOUNT.FROM field.
However, by setting the field PRIOROTISE.OD you can specify the sweep to clear any
overdrafts amongst the from accounts first. This would mean that if there was two from
Ref : AI
April 2000
2-23
Release G10.2.02
GLOBUS USER GUIDE
accounts with the first having a balance of 200 and the second -50, the sweep would place
50 in the second account and 150 in the first.
Figure 2-12 AC.SWEEP.TYPE
Ref : AI
April 2000
2-24
Release G10.2.02
GLOBUS USER GUIDE
2.1.17.2 AC.ACCOUNT.LINK
Accounts will be linked through a new table. It will allow multiple to and from accounts to be
linked from across multi company environments. You would assign the SWEEP.TYPE for that
link as well. The last part of the link would be the relevant minimum/maximum amounts for
the to account and the minimum amount of the from account. The Accounts may be of any
currency or customer. If an account has a posting restriction on it then an override will be
raised. Similarly you cannot close an account that has an active AC.ACCOUNT.LINK
Figure 2-13 AC.ACCOUNT.LINK
Ref : AI
April 2000
2-25
Release G10.2.02
GLOBUS USER GUIDE
2.1.17.3 Account Sweeping History
All sweeps will be recorded in a live table called ACCOUNT.SWEEP.HIST. This table is
keyed by account and month. It will hold all the sweeps done on that account within the given
month. They will be sorted by day swept and accompanied by a unique reference of debit
accountcredit accountdate.
Figure 2-14 AC.ACCOUNT.SWEEP.HIST
Ref : AI
April 2000
2-26
Release G10.2.02
GLOBUS USER GUIDE
2.2
Payment Netting
2.2.1 Overview
The payment netting facility provides the ability to automatically net payments with a
counterparty in the same currency and with the same value date. Netting is permitted only
when a NETTING.AGREEMENT is held with the counterparty. The netting agreement has a
finite life and indicates which currencies may be netted with this counterparty.
Net payments must be agreed and approved before the payment is generated. This is done
using the NETTING application. GLOBUS will automatically consolidate payments eligible
for netting into a netting group which will appear as a single record on the NETTING
application. This record may then be reviewed and confirmed with the counterparty.
Authorisation of the NETTING record will generate the single netted payment.
During the review of the NETTING record, individual payments may be rejected for inclusion
in this net payment. Any payments thus rejected will remain in suspense and will
automatically be included in the next netting group created for the same currency, customer
and value date. Once a payment has been selected for netting it can only be made using the
NETTING application.
Netting groups may be created during the GLOBUS overnight batch (based upon forward
deals) or on-line (using the CREATE.NETTING application) for spot deals.
The accounting entries for payments that are to be net pass across a suspense account, which
should have a zero balance once all net payments have been sent.
Individual payments that are to be net are recorded on the NETTING.ENTRY application. This
is a live file; i.e. it is not available for input. There is one NETTING.ENTRY record for each
contract.
Ref : AI
April 2000
2-27
Release G10.2.02
GLOBUS USER GUIDE
Pa
en
ym
or
ts f
ne
g
ttin
NETTING.
ENTRY
Re
jec
te
Pa
ym
en
ts
dp
ay
m
for
ne
tt
ing
en
ts
FOREX
ym
en
en
ts
pa
pa
ym
Ne
t
Si
ng
le
ts
NETTING
Nostro account
Figure 2-15 Net payments processing diagram
Ref : AI
April 2000
2-28
Release G10.2.02
GLOBUS USER GUIDE
2.2.2 Accounting for net payments

Payments that are netted pass across a suspense account. For example if we are paying US
dollars to a counterparty with a value date of spot, and are expecting one receipt of US dollars
funds from the same counterparty with the same value date then if we are not netting
payments, GLOBUS will generate the following entries:
dr./cr.
Credit
Debit
Account
Nostro
Nostro
Amount
15M
12M
Ccy
USD
USD
Value
Spot
Spot
Generated by
Contract
Contract
Table 2-3 Accounting entries - no netting
If the payments were netted then GLOBUS would generate the following:
dr./cr.
Credit
Debit
Debit
Credit
Account
Netting suspense
Netting suspense
Netting suspense
Nostro
Amount
15M
12M
3M
3M
Ccy
USD
USD
USD
USD
Value
Spot
Spot
Spot
Spot
Generated by
Contract
Contract
Netting
Netting
Table 2-4 Accounting entries - with netting
All entries in the above examples are STMT.ENTRY records
2.2.3 Installing the payment netting function

The following steps need to be followed:
1.
2.
3.
4.
5.
6.
Ref : AI
Open new TRANSACTION codes for netting entries

Open a new CATEGORY code for netting suspense accounts
Open an ACCOUNT.CLASS record for NETTING.
Open the netting suspense accounts (only one is mandatory)
Input the NETTING.PARAMETERS record
Set the ACCOUNT.PARAMETER to allow netting
April 2000
2-29
Release G10.2.02
GLOBUS USER GUIDE
2.2.4 Setting up the payment netting suspense accounts

The payment netting facility requires suspense accounts. Setting up these accounts is done in
two stages: an ACCOUNT.CLASS record is created and then a suspense account is opened
which will act as a template for all the suspense accounts.
The ACCOUNT.CLASS record to be established has a key of NETTING. This record is used by
GLOBUS to determine the characteristics of the suspense accounts to be set up to hold the
netted payments. Before setting up the record a new CATEGORY code should be created for
netting suspense accounts. This code will be referenced by the ACCOUNT.CLASS parameter.
Figure 2-16 An example ACCOUNT.CLASS record defining the netting suspense account
Ref : AI
April 2000
2-30
Release G10.2.02
GLOBUS USER GUIDE
Once this is complete the internal netting suspense accounts may be opened using the
ACCOUNT application. The id of these accounts is the same as any other internal ACCOUNT,
i.e. the CURRENCY, CATEGORY, and a four-digit identifier. E.g. USD149550001
Figure 2-17 Example payment netting suspense account
2.2.5 Setting ACCOUNT.PARAMETER for payment netting

The ACCOUNT.PARAMETER contains a field (NETT.PAYMENTS) which must be set to YES
for payment netting to take place.
2.2.6 Use of the NETTING.STATUS field on contracts

All contracts whose payments may be netted contain a field called NETTING.STATUS. This
field may be used at contract input time to stop the payments arising from this contract being
netted.
Ref : AI
April 2000
2-31
Release G10.2.02
GLOBUS USER GUIDE
2.2.7 The NETTING.ENTRY application

The NETTING.ENTRY application contains details of all entries being netted. Records are
created here upon authorisation of the original contract. When an individual payment has been
successfully included in a net payment then its entry on this file is updated.
2.2.8 The NETTING application

The NETTING application is the main control over the net payments process. All individual
payments selected for netting are combined into a single netting record for the counterparty,
currency, and value date combination. This record may then be reviewed and amended if
necessary. Once the net payment is correct the netting record is authorised and GLOBUS will
create the single net payment or receipt accounting and delivery messages.
Individual payments may be dropped from a net payment at this point. If dropped they will
remain in suspense until captured in another net payment. Therefore once a payment has been
selected for netting, it can only be paid using the NETTING application. Individual payments
may, of course, be removed from netting by reversing and re-inputting the source contract and
ensuring that the NETTING.STATUS field is set to NO on the re-input.
Ref : AI
April 2000
2-32
Release G10.2.02
GLOBUS USER GUIDE
2.2.9 Parameter Files

2.2.9.1 ACCOUNT.PARAMETER- Controls Account & Defaults
The ACCOUNT.PARAMETER record contains high level specifications for the ACCOUNT
application. For example:
Number of days forward for cash-flow processing

Whether accounting is performed on a value date or booking date basis
Whether accounts can be referenced by an alternative id or not
Whether the customer number must form part of the account number
Whether payments can be netted
How settlement defaulting is to take place
There is only one record, with an ID of SYSTEM.
Figure 2-18 ACCOUNT.PARAMETER - Master control of the Account module
Ref : AI
April 2000
2-33
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.2 ALT.ACCT.PARAMETER - Alternative Account numbers
Specifies the structure of an alternative ACCOUNT number.
Figure 2-19 ALT.ACCT.PARAMETER - Defining an alternative account number
In practise where GLOBUS has replaced an existing system it may be a short-term

requirement to allow the access to client accounts using the old account numbers. In order to
allow this, a special parameter file, ALT.ACCT.PARAMETER needs to be set-up. This tells
GLOBUS how the other system account number structure was defined.
Once this is set up it is possible to enter the old account number on the ACCOUNT record in
the field ALT.ACCT.ID.
An index is kept in ALTERNATE.ACCOUNT, the id is the external system account number
and the single field GLOBUS.ACCT.NUMBER contains the GLOBUS equivalent.
Ref : AI
April 2000
2-34
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.3 POSTING.RESTRICT - Posting restrictions
This file contains various types of restrictions that may be defined, such as Post No Debits,
Whereabouts Unknown.
The system will automatically close any ACCOUNT that has a posting restriction in the 90-99
range as soon as all balances are zero. Posting restrictions in the range 80-89 are used for
accounts, which are pending closure.
Where an ACCOUNT has a value in the field POSTING.RESTRICT and attempts are made to
pass entries to it, an override message will be issued.
Figure 2-20 POSTING.RESTICT - Defining-posting restrictions
Ref : AI
April 2000
2-35
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.4 REFERAL - Referral
A referral is the reporting of an ACCOUNT movement or balance to an account officer

(DEPT.ACCT.OFFICER) when certain conditions are met. For example an ACCOUNT may
be referred when it exceeds a particular debit value, or when certain types of transaction are
passed across the account etc.
A referral is only the reporting of the ACCOUNT to the account officer by means of an
overnight report. A posting restriction (a stronger form of referral) should be used if an
override message at input is required.
The REFERAL table contains the pre-defined referral conditions. These are then loaded onto
the ACCOUNT record in the REFERAL.CODE field. Multiple referral codes may be specified
on an ACCOUNT.
Figure 2-21 Referral example
Ref : AI
April 2000
2-36
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.5 ACCOUNT.CLASS - Defining internal and other accounts
This table file has two main types, ACCOUNT and CLASS.
ACCOUNT.CLASS records with a RECORD.TYPE of ACCOUNT provide the CATEGORY code
portion when building an internal ACCOUNT number (such as netting suspense account).
The use of CLASS as the RECORD.TYPE is used to identify a group of ACCOUNT records (e.g.
under a heading like NOSTRO) by matching the ACCOUNT details against those held in the
ACCOUNT.CLASS record.
Figure 2-22 ACCOUNT.CLASS - Example of a class parameter
When the RECORD.TYPE is ACCOUNT then the CATEGORY code must be valid and in the
range 10000 to 19999.
Ref : AI
April 2000
2-37
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-23 ACCOUNT.CLASS - Example of an account parameter
When the RECORD.TYPE is CLASS the CATEGORY and SECTOR code fields are treated as
multi value associated fields. Either field may be null, but not both at the same time.
Duplications of CATEGORY and SECTOR code combined are not allowed within one entry
on the ACCOUNT.CLASS table.
Ref : AI
April 2000
2-38
Release G10.2.02
GLOBUS USER GUIDE
The following records are among those permitted:

Key
Description
NOSTRO
Identifies a NOSTRO ACCOUNT.
VOSTRO
Identifies a VOSTRO ACCOUNT.
BRANCH
Identifies an ACCOUNT belonging to a BRANCH of Company processed.
BANK
Identifies an ACCOUNT belonging to a Bank.
MORTGAGE
Identifies a Mortgage ACCOUNT
MGDEPOSIT
Identifies a Mortgage Deposit ACCOUNT
SAVINGS
Identifies an ACCOUNT as a Savings ACCOUNT.

Table 2-5 ACCOUNT.CLASS - CLASS record types
Ref : AI
April 2000
2-39
Release G10.2.02
GLOBUS USER GUIDE
For accounts the following Ids are valid.

Key
Description
SUSPENSE
DATA.CAPTURE which have not been authorised.
DIFFERENCE
DATA.CAPTURE entries to balance a batch.
SUSPCREDIT
Accounting suspense entries when the original entry can not be posted due
to ACCOUNT not being present or override condition has been met.
SUSPDEBIT
SUSPLMMCR
SUSPLMMDR
SUSPFXCR
SUSPFXDR
Loans and Money Market entries when the true

known for the payment or receipt.
Foreign Exchange entries when the true
the payment or receipt.
ACCOUNT is not yet
ACCOUNT is not yet known for
EXCHADJ
Unrealised profit and loss produced by the revaluation of foreign exchange

contracts.
EXCHALFWD
Used to post the P & L produced by the revaluation and contingent balances
in a value dated accounting system.
RESFWDCR
To be used by the FOREX system when posting the interest accruals on

Foreign Exchange contracts using the straight line or Interest revaluation
method.
RESFWDDR
RESSWAPCR
RESSWAPDR
BROKER
Used to identify the provision account to be used to book the brokerage.
NETTING
SUSPSCDR
Suspense ACCOUNT for net payments.

Suspense ACCOUNT which the Securities module will use.
SUSPSCCR
SCDIFF
SUSPFRACR
SUSPFRADR
SUSPFTBULK
Suspense ACCOUNT which the FRA.DEAL module will use.
SUSPFTINWD
Suspense ACCOUNT which the FT module will use for Bulk transfers
and incoming deals.
SUSPPD
Wash through Account used by accounting for past due payments
Ref : AI
April 2000
2-40
Release G10.2.02
GLOBUS USER GUIDE
Key
SUSPSLCR
SUSPSLDR
TFLC
Description
Suspense ACCOUNT which the Syndicated Loans module will use.
Suspense ACCOUNT which the LC module will use.
LCAMORT
LCDIFF
PLCLOSE
Used at year end closing of PL
INTERCO
Used for passing entries between inter-company Accounts

Table 2-6 ACCOUNT.CLASS - ACCOUNT record types
Ref : AI
April 2000
2-41
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.6 AC.STMT.PARAMETER - Defaults for account statements
The purpose of this table is to define defaults for ACCOUNT statement details when opening
new ACCOUNT records.
This table determines whether the default ACCOUNT.STATEMENT record is set to produce
statements when there has been no movement, descriptive statements, interest and charges
statements and advices and tax advices and the minimum number of months for a statement to
be produced if at all. If no record exists the default will be NO and the minimum frequency
will be 6 months.
These settings can of course be overridden on the ACCOUNT.STATEMENT record itself.
Figure 2-24 AC.STMT.PARAMETER - Statement defaults for accounts
Ref : AI
April 2000
2-42
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.7 STMT.GEN.CONDITION - Defaults for statement frequencies
When a new ACCOUNT is opened, an ACCOUNT.STATEMENT record, specifying the date

and frequency for printing account statements is generated automatically by the system. The
default frequency is determined by the STMT.GEN.CONDITION table.
Figure 2-25 STMT.GEN.CONDITION - Specifying defaults for statement frequencies
Ref : AI
April 2000
2-43
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.8 ACCOUNT.STATEMENT - Statement details for an individual account
When a new account is opened, an ACCOUNT.STATEMENT record is automatically

generated by the system. This specifies the date and frequency for printing statements,
whether statements are to be printed if there have been no movements and various other
statement production options. Defaults are taken from other parameter tables such as the
STMT.GEN.CONDITION and AC.STMT.PARAMETER but these can of course be overridden
by input to this table.
The key to the table is an ACCOUNT number.
Figure 2-26 ACCOUNT.STATEMENT - Statement details for a single account
Ref : AI
April 2000
2-44
Release G10.2.02
GLOBUS USER GUIDE
The ACCOUNT.STATEMENT application also allows for the production of a SWIFT MT942
messages. These can be generated at specified times during the day via a phantom process.
Consult the APPLICATION DELIVERY user guide on controlling the phantom process.
Figure 2-27 ACCOUNT.STATEMENT fields for timed MT942 messages
These message types can also be produced on an ad-hoc basis as detailed in the next section.
2.2.9.9 Ad-hoc Interim transaction (MT942) reports
A customer may authorise another financial institution to receive statements and transaction
reports of his accounts. There is a facility to produce Interim Transaction Reports (SWIFT
MT942) on-line on an ad-hoc basis. Requests are entered through the application
DE.MT942.REQUEST where 942 is a new message type for this type of account statement.
Note the V function is required to invoke the message creation.
Figure 2-28 Verify a DE.MT942.REQUEST record to request an interim transaction report
Ref : AI
April 2000
2-45
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.10 ACCT.GROUP.CONDITION - Rules for accounts
Figure 2-29 ACCT.GROUP.CONDITION - Account Group Condition Parameters
The record id for this parameter file is the condition group and the currency of the account/s.
Rules on deposits, withdrawals and premium interest applying to accounts belonging to
condition group and defined for specific currency are entered here.
Further the record id for the parameter file may be suffixed with a date in the YYYYMMDD
format. This date specifies that the record is a change request for the condition group &
currency combination specified in the first part of the key. The request records are processed
in the End of Day processing and the new values of the parameters are passed into the active
record using the values from this record request record.
It is recommended that the copy function be used to create the request record from the active
record prior to changing any parameters.
Additionally, where the requirement exists to record and report transaction violations on an
account or accounts within a particular group, this may be achieved by defining the threshold
permissible before the violation occurs and the transactions eligible to trigger a violation. The
following example demonstrates how this may be achieved.
Ref : AI
April 2000
2-46
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-30 Defining violating transaction codes and thresholds
In the example above, for ACCOUNT.GROUP 1, the number of transactions, with a

transaction code of 2, 84 or 85, permissible within a statement period, may collectively add up
to, but not exceed, 5 transactions. If this threshold (TXN.THRESHOLD) is exceeded, the account
is in violation and this will be recorded on the account violations file (AC.VIOLATION). The
above example is set up to record violations if more than 5 cash withdrawals or more than 3
cheque withdrawals occur within the statement period defined for the account group into
which this account falls.
The RETENTION.PERIOD field defines how long records remain on the AC.VIOLATION file
before being transferred to the history file, AC.VIOLATION.HIST. Additionally, this field also
determines when transactions are deleted from the history file. They will be deleted after
twice the period defined. For example, if 12M is entered in this field, a violation record will
remain on the AC.VIOLATION file for 12 months, it will then be transferred to the
AC.VIOLATION.HIST file. The record would then remain on the AC.VIOLATION.HIST file
for a further 24 months before being deleted.
Ref : AI
April 2000
2-47
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.11 SAVINGS.PREMIUM - Parameters for premium types
Figure 2-31 SAVINGS.PREMIUM - Parameters for premium types
An option of premium interest on accounts has been provided for in GLOBUS. The actual
parameters used in the calculation & processing of premium interest on the accounts is
specified on this application. The premium types defined here are linked to the account via the
ACCT.GROUP.CONDITION record. The INTEREST.BASIS field in this table may not be set
to the C2 interest basis
Ref : AI
April 2000
2-48
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.12 PREMIUM.DETAILS - Details of premiums paid on account
An account that capitalises premium interest will create details of the movements that were
used in the calculation process. This file details all such movements with information on the
value date, amount, date from which premium was paid, date to which premium was paid,
number of days for which premium was paid, unrounded premium amount and the rounded
premium amount.
Figure 2-32 PREMIUM DETAILS - Details of premium interest
Ref : AI
April 2000
2-49
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.13 NOTICE.WITHDRAWAL - Notices given on notice accounts
Some types of accounts can be set up to have notice withdrawal conditions. In such a situation
for a withdrawal to be effected on the account a notice must have been given that satisfies the
notice conditions set up on the ACCT.GROUP.CONDITION application. These notices are
given through this application.
Figure 2-33 NOTICE WITHDRAWAL - Notice given for withdrawal
Ref : AI
April 2000
2-50
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.14 NOSTRO.ACCOUNT - Nostro accounts
Figure 2-34 NOSTRO.ACCOUNT - Specifying default Nostro accounts
Default NOSTRO accounts for currency and application are entered in the file
NOSTRO.ACCOUNT.
Defaults can be set for each application; even for transaction types within that application.
FOREX has a unique option where the dealer can enter a letter indicating which NOSTRO
should be used, these equate with the input order; so the first FX default would be A, the
second B and so on.
Ref : AI
April 2000
2-51
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.15 PAYMENT.STOP - Instructions to stop payments
The PAYMENT.STOP table allows all payment stop instructions to be recorded. These are
input against the account to which they relate. All stop instructions for one ACCOUNT
number is maintained on the same record.
Figure 2-35 PAYMENT.STOP - Instructions to stop payments
It should be noted that PAYMENT.STOP will only have an impact upon Cheque Issue &
Management (see section 2.4) when the PAYMENT.STOP record has been authorised.
Ref : AI
April 2000
2-52
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.16 PAYMENT.STOP.TYPE - Reasons for stopping a payment
The PAYMENT.STOP.TYPE table allows the definition of up to 99 reasons for stopping a

payment (e.g. Cheques Lost, Cheques Destroyed etc.).
The table is used by the PAYMENT.STOP application to describe the reason for each stop
instruction.
Figure 2-36 PAYMENT.STOP.TYPE - Reasons for stopping a payment
Ref : AI
April 2000
2-53
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.17 NETTING.PARAMETERS
The NETTING.PARAMETERS application controls the payment netting facility. Only one
record may exist (with the id of system). It specifies the TRANSACTION codes to be used for
netting payments, the number of days prior to the payment value date that netting records
should be created, and the period that history should be kept before netting information is
purged from the system.
Figure 2-37 NETTING.PARAMETERS - control of the payment netting facility
Ref : AI
April 2000
2-54
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.18 NETTING.AGREEMENT
The NETTING.AGREEMENT application contains agreements with counterparties to net

payments of the same currency and value date. One agreement can be made with each
counterparty (CUSTOMER) and the agreement may specify that only payments of particular
currencies may be netted and only payments arising from particular GLOBUS applications
may be netted.
The agreement lasts for a finite period as specified in the start and end date fields. The
agreement may be input and amended at any time.
Figure 2-38 NETTING.AGREEMENT - permitting payment netting for a customer
Ref : AI
April 2000
2-55
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.19 NETTING.ENTRY
The NETTING.ENTRY file contains details of all individual payments that are netted. The id
of the records is the original contract id. The record contains details of each payment arising
from the contract where the payment is being netted.
Figure 2-39 NETTING.ENTRY - details of payments being netted
The NETTING.ENTRY record also holds details of the status of each individual payment.
Each individual payment can have one of two statuses - waiting to be included in a net
payment and included in a net payment. The status is recorded in the field NP.REF. If this
field does not contain a value then the individual payment is waiting to be netted. Once the
individual payment has been included in a net payment then this field will be updated with the
reference of the NETTING record.
Ref : AI
April 2000
2-56
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.20 CREATE.NETTING
This application is used to create netted payments on-line. Verification of a

CREATE.NETTING record will activate the payment netting process. This will combine all
outstanding payments that match the specified criteria into NETTING records. These can then
be reviewed, amended if necessary, and authorised thus creating the net payments.
Payments can be netted for any combination of counterparty, currency and value date. Thus a
record can net all outstanding payments for a single counterparty, only those for a single
currency for that counterparty etc. The specification of counterparty is mandatory.
Figure 2-40 CREATE.NETTING - on-line creation of net payments
Ref : AI
April 2000
2-57
Release G10.2.02
GLOBUS USER GUIDE
2.2.9.21 NETTING
The netting application is used to review, and modify if necessary, net payments. GLOBUS
creates NETTING records automatically during the overnight batch run or on-line using
CREATE.NETTING. These records are created with a status of hold ready for review and
possible input. Once a NETTING record has been confirmed as being valid (possibly
following confirmation with the counterparty) it should be authorised. GLOBUS will then
generate the single net payment.
Figure 2-41 NETTING - reviewing and modifying net payments
Settlement details, such as bank to bank information, may be added to the NETTING record
and will be used on the resultant net payment. Additionally individual payments may be
removed from the netting record if necessary by using the NETTING field. Payments removed
from the record will remain in suspense until another netting record is generated (either in the
GLOBUS batch or by the CREATE.NETTING application).
Ref : AI
April 2000
2-58
Release G10.2.02
GLOBUS USER GUIDE
2.2.10 Internal Files

2.2.10.1 ACCT.ACTIVITY - History of account activity
This is an internal file containing details of account balances and activity used to calculate
interest and charges. It is also used in the calculation of average balances in the Management
Information module.
Details are held in separate records for each account for each month in which there has been
any activity over the account or in which the value dated balance changes. Full details of all
balance changes are included as well as details of transaction activity by transaction code.
Figure 2-42 ACCT.ACTIVITY - History of account activity
Ref : AI
April 2000
2-59
Release G10.2.02
GLOBUS USER GUIDE
2.2.10.2 ACCT.AVAILABILITY - History of availability of funds on Accounts
This is an internal file containing details of account balances, activity and availability of funds
used in penalty charge processing. It is also used in the correct implementation of some rules
that place restrictions on the movements on the accounts. These rules are specified on the
ACCT.GROUP.CONDITION application.
Figure 2-43 ACCT AVAILABILITY - Availability of funds on Accounts
Details are held in separate records for each account.
Ref : AI
April 2000
2-60
Release G10.2.02
GLOBUS USER GUIDE
2.2.11 Reporting
2.2.11.1 Overdraft Report
This will show details of all accounts whose LIMIT is exceeded and any overdrawn accounts
with no limit specified.
Figure 2-44 Overdraft report
Ref : AI
April 2000
2-61
Release G10.2.02
GLOBUS USER GUIDE
2.3
INTEREST & CHARGES
2.3.1 Introduction
The Interest and Charges system is part of the essential core of GLOBUS and it is used to
define and calculate the credit and debit interest, and charges on the ACCOUNT records
within the database.
Interest and charges are only applicable to CUSTOMER ACCOUNT records. These are
calculated in the End of Day processing and applied to the accounts at user defined intervals.
ACCOUNT records can be defined into logical groups with different debit and credit interest
conditions applied only to those groups. However, it is also possible to define special
conditions, which apply only to an individual account within a group.
2.3.2 Group And Special Conditions

Conditions for the calculation and application of interest and charges are specified for groups
of accounts and can be overridden with special conditions for individual accounts.
ACCOUNT groups are determined automatically on the basis of CUSTOMER and ACCOUNT
details such as COUNTRY (residence), SECTOR, CATEGORY and CURRENCY. The criteria
used and their order of priority are stored in user-defined tables, CONDITION.PRIORITY and
ACCT.GEN.CONDITION.
Ref : AI
April 2000
2-62
Release G10.2.02
GLOBUS USER GUIDE
2.3.3 Interest Calculations

Interest may be calculated on a daily, average, or highest/minimum balance basis using value
dated balances.
A further restriction can be imposed on the minimum balance calculation, by calculating the
interest on the minimum balance between two dates (for example between 10th and the last
day of the month, both days included). These dates can be customised at account or group
level, in the applications ACCOUNT.CREDIT.INT & GROUP.CREDIT.INT.
For example, assume a credit balance on the 31st of the month of 2,500 and an Account
Interest record, which specifies an applicable rate of 10 per cent to be calculated on a MINIMUM
balance. If the following account balances have been recorded for the account in
ACCT.ACTIVITY:
Day No
5
8
10
20
25
Turnover Credit
5,000
Turnover Debit
-4,900
900
-500
2,000
Balance
5,000
100
1,000
500
2,500
If no dates are specified then on the 31st the account will receive a payment of interest
calculated on 100 at 10%. However, if the interest is to be calculated on a minimum balance
for a specified period within the account capitalisation period, i.e. for a starting date of 10th
and an end date of 31st then the account will receive a payment of interest calculated on 500 at
10%.
Accounts opened or closed after or before the start date of the specified range can be
customised not to accrue any interest for that period. These flags can be customised at
account or group level, in the applications ACCOUNT.CREDIT.INT & GROUP.CREDIT.INT.
The movements/balances on different accounts in the same currency can be combined and
interest calculated on the net result.
different basic rates. The rates may apply to the whole of the balance or to the part between two
balance levels.
Using group level conditions, it is possible to specify limits on individual accounts so that one
rate can be charged up to the limit and another rate when the limit has been exceeded.
Interest can be calculated on a 360/360, 366/360, 366/366, 360/366, 366/365 and 360/365 days
basis.
Ref : AI
April 2000
2-63
Release G10.2.02
GLOBUS USER GUIDE
Back valued entries generate automatic adjustments to previously calculated interest. For any
accounts where interest conditions or rates are changed with effect prior to the last interest
application, the system generates adjustments on request.
2.3.4 Interest Application And Accrual

Interest may be applied daily, every working day, every 1-9 weeks, twice a month on the 15th
and the last day or every 1-99 months on any day of the month. The application dates can be
specified at group or account level. Cycles may be different for debit and credit interest.
Special interim applications may be requested without affecting the regular cycle.
It is possible to defer debit interest and / or charge application to an account in GLOBUS in
order to provide the facility of Pre-Notification to the customer. This facility has been
discussed as another heading in this section.
2.3.4.1 Daily accrual
ACCOUNT with daily accrual. Daily accrual can be set for local currency accounts, foreign
currency accounts or both using the DAILY.ACCR.ALLTYPE
field on the
ACCOUNT.ACCRUAL record. Alternatively daily accrual can be set for specific categories or
accounts using the DAILY.ACCR.CATG and DAILY.ACCR.TYPE fields.
2.3.4.2 Waiving of credit interest
It is possible to waive credit interest depending on the number and type of transactions passed
over the account. The feature is controlled with the help of the fields TXN.THRESHOLD,
TXN.CODE.GRP & WAIVE.CR.INT. This has been illustrated below:
Figure 2-45 ACCT.GROUP.CONDITION - How to waive credit interest
Ref : AI
April 2000
2-64
Release G10.2.02
GLOBUS USER GUIDE
As shown in the above figure all accounts that belong to the group 1 denominated in USD
will check if a transaction code 2 was passed on the account. If this is the case then credit
interest on the account will be waived. (Note only calculations will be performed and stored
on the INFO.ACCT.CR/CR2 files in such a case).
Details on the status related to the above will be stored on the AC.VIOLATION file as
illustrated below:
Figure 2-46 AC.VIOLATION - Waive interest status
Ref : AI
April 2000
2-65
Release G10.2.02
GLOBUS USER GUIDE
2.3.5 Special Cases

Interest may be paid or received from another ACCOUNT in the same currency.
Credit interest may be calculated for the purpose of offsetting debit interest only and not for
application. In this case debit and credit interest application dates must be the same.
Interest may be suspended for specific accounts i.e. not posted to profit and loss.
It is possible to calculate interest for information only and not accrue or apply it e.g. for
NOSTRO ACCOUNT records.
Detailed interest statements may be printed for specified ACCOUNT records whenever
interest is applied.
2.3.6 Interest Related Charges

Tax on interest is calculated at application time.
Certain additional charges based on the debit interest application may be applied on the same
date, these include:
DEBIT.INT.ADDON
a percentage of the amount of debit interest to be applied.
GOVERNMENT.MARGIN
an additional interest rate applied to each debit interest

calculation.
HIGHEST.DEBIT
a percentage of the largest debit balance.
INTEREST.STATEMENT
a charge for providing a detailed interest statement when

debit interest is applied.
Ref : AI
April 2000
2-66
Release G10.2.02
GLOBUS USER GUIDE
2.3.7 ACCOUNT maintenance charges

ACCOUNT maintenance charges may be levied monthly, quarterly, six monthly or yearly,
always at the end of the appropriate month. The same application cycle is used for all
ACCOUNT records. There are two main types of charges as follows:
Balance based:
A flat charge can be levied if a certain average or minimum balance is not maintained. A
range of charges for different balances may be specified.
Transaction based:
Charges can be made for the transactions passed over an ACCOUNT. These may be based on
the number or the volume of transactions and may be different for debit and credit or for each
transaction type. Each transaction type may be included or excluded from the calculations.
The various types of transaction charges are as follows:
Number of credit
Number of debit
Turnover credit
Turnover debit
Transaction type
Charges may be combined into one account entry or applied separately. Free, minimum and
maximum amounts can be specified for each charge.
Separate charges can be defined for specific currencies and local currency charges used as the
default for all non-specified currencies.
Ref : AI
April 2000
2-67
Release G10.2.02
GLOBUS USER GUIDE
2.3.8 Offsetting And Waiving Charges

On specified ACCOUNT records, charges may be calculated for information only and then
waived.
Charges may also be waived if a certain average or minimum balance is maintained, if the
amount of the charge is below a value worth charging or if the account has been into debit.
It is possible to specify that charges do not apply to foreign currency ACCOUNT records.
Notional credit interest can be calculated and offset against the charges.
2.3.9 Pre-Notification of debit interest and / or charges

The Code of Good Banking Practice in the U.K sets out standards of services that customers
should be able to expect from their banks. One element of the code is that the bank should
give all private individual customers 14 days notice before debiting their accounts with
interest and/or bank charges relating to overdrafts.
Debit interest and charges are calculated on the capitalisation date, the positing of the amounts
to the customer account may be deferred for a number of days (e.g. 14 days). In this case the
interest and/or charges are posted to a suspense account on the capitalisation date, then posted
to the actual account (and backed out of suspense) on the deferred date. Where interest and/or
charges are deferred the details of the calculations are held in the application AC.PENDING
which allows adjustment of the amounts.
The number of days by which debit interest and/or charge related debit amounts scheduled for
posting to accounts are to be deferred is specified in the ACCT.GROUP.CONDITION
application. This also controls the suspense account category and to be used for deferring
interest/charges.
Ref : AI
April 2000
2-68
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-47 Setting up parameters for Pre-Notification of debit interest and / or charges
Subsequent corrections performed on accounts will take place on the next capitalisation date.
The pending debit interest and/or charges will be transferred from the suspense accounts to
the actual accounts after the notice period has been served (i.e. during the Batch run of the
deferral date).
The amounts of debit interest, charges and, if applicable, taxes will be stored in a standard
GLOBUS application AC.PENDING that will be accessible to all types of reports and
enquiries. It will be possible to make adjustments to or even waive completely the debit
interest and / or charges pending on the account. This has been illustrated below:
Ref : AI
April 2000
2-69
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-48 Making adjustments to pending debit interest
Ref : AI
April 2000
2-70
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-49 Making Adjustments to pending charges
Ref : AI
April 2000
2-71
Release G10.2.02
GLOBUS USER GUIDE
2.3.10 Savings Accounts

An ACCOUNT can be classified as a Savings ACCOUNT (see ACCOUNT.CLASS) using the
CATEGORY field. A savings ACCOUNT can be issued a passbook, instead of regular
statements and be subject to additional conditions of withdrawal notices etc. (see
ACCT.GROUP.CONDITION).
2.3.11 Parameter Files

The following Parameter files have to be set up before the interest and charges can be
activated. In fact, it will not be possible to open any CUSTOMER ACCOUNT records before
the Parameter files and the debit and credit interest conditions have been set up in the
database.
All interest and charges conditions defined are based on an effective date that is part of the
key of the record. Modifications to any existing records will have to be done carefully since
the conditions defined will be applicable from the effective date. Therefore a change in the
interest rate will have to be reflected by opening a new condition record from the date the
change is applicable rather than modifying an existing record.
Ref : AI
April 2000
2-72
Release G10.2.02
GLOBUS USER GUIDE
2.3.11.1 CONDITION.PRIORITY
This application defines which fields are to be used for setting various group conditions, and
once authorised it cannot be changed. The bank must work out which criteria are required for
use particularly for ACCOUNT conditions. It is better to include more items than may be
required initially.
Figure 2-50 Condition Priority example
2.3.11.2 ACCT.GEN.CONDITION
Every group of ACCOUNT records that the Bank wants to classify is defined in this
application. This classification will be based on the conditions defined in the application
CONDITION.PRIORITY.
The purpose of this table is to define the rules for grouping together ACCOUNT records for
which the same interest and charges conditions apply.
Conditions for the calculation and application of interest and charges may then be specified
for the groups and overridden with special conditions for individual ACCOUNT records.
Ref : AI
April 2000
2-73
Release G10.2.02
GLOBUS USER GUIDE
ACCOUNT groups are determined on the basis of CUSTOMER and ACCOUNT details such
as COUNTRY (residence), SECTOR and CATEGORY. The criteria used and their order of
priority are specified in the CONDITION.PRIORITY file in the record whose Id is ACCOUNT.
Only the fields selected in the CONDITION.PRIORITY file are included in general condition
records.
Each general condition record specifies the combination of field values defining one
ACCOUNT group. The Id of the general condition record is referred to in other parts of the
system as the condition group.
Before any ACCOUNT can be opened, a suitable general condition record must exist in order
to determine the Group to which the ACCOUNT belongs, also a capitalisation frequency
record, debit and credit interest conditions (in the CURRENCY of the ACCOUNT) for that
group must have been defined.
Whenever input to an ACCOUNT record occurs, a condition group value is recalculated
according to the details held in this table. The ACCOUNT and CUSTOMER details must
conform to every field value defined within the general condition record. Amending an
ACCOUNT or CUSTOMER record may result in new interest conditions being applied and
possibly an adjustment to interest previously calculated.
If the details of an ACCOUNT match more than one general condition record, the priority
order is used to determine the group. (The higher priority field with a match wins. priority 1 is
the highest priority.)
An overall default condition (no value specified in any field) must be the first
ACCT.GEN.CONDITION record loaded.
The example below illustrates that the group number 4 (Staff Savings Accounts) is defined as
any ACCOUNT opened in the system with a CATEGORY code of 6000 having a CUSTOMER
number whose SECTOR code is 1250
Ref : AI
April 2000
2-74
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-51 ACCOUNT.GEN.CONDITION
Ref : AI
April 2000
2-75
Release G10.2.02
GLOBUS USER GUIDE
2.3.11.3 ACCOUNT.ACCRUAL
This is a parameter file used to define the interest accrual and posting conditions in the Bank.
Typically data like accrual cycles (Daily, Monthly etc.), foreign or local currency accruals are
specified in this application. The actual interest and charges rates applicable to each ACCOUNT
are defined in other files.
The purpose of this table is to provide the system with information at COMPANY level about
how and when to process accruals of interest and charges on CUSTOMER ACCOUNT records
and whether interest capitalisation is inclusive or exclusive of the balance on capitalisation
date, the value dates of interest entries generated and the day on which the entries are booked.
Interest accruals may be processed daily or monthly on any day of the month. ACCOUNT
charges may only be processed at calendar month end.
ACCOUNT with daily accrual.
Dates for interest capitalisation are specified at group level
GROUP.CAPITALISATION table and for a specific ACCOUNT
ACCT.CAPITALISATION table.
in
in
the
the
Figure 2-52 Account Accrual
Ref : AI
April 2000
2-76
Release G10.2.02
GLOBUS USER GUIDE
2.3.12 Debit Interest Conditions

Debit interest conditions can be defined either at group level (i.e. for a group of ACCOUNT
types) or at an ACCOUNT level if the debit interest conditions for the Account are different
from those of the group it belongs to.
Tax can also be taken on debit interest.
Charges are included as part of the debit interest conditions.
2.3.12.1 GROUP.DEBIT.INT
This file defines the group level debit interest conditions for all the ACCOUNT records in a
group. GLOBUS allows definition of two debit interest conditions to be applicable on an
ACCOUNT.
The file also allows the user to specify the calculation method of debit interest for groups of
accounts and provides the link to the GENERAL.CHARGE table where the charges applicable
to the same group are defined. Interest can be calculated on a Daily, Average, or Highest
balance basis using value dated balances.
two balance levels.
Using group level conditions, it is possible to use the limits on individual ACCOUNT records
as the first level for debit interest so that one rate can be charged up to the LIMIT on any
ACCOUNT and another rate when the LIMIT has been exceeded. (Limits for an individual
ACCOUNT are specified in the ACCOUNT.DEBIT.LIMIT) In this case a maximum of 2 rates
may be specified.
For example it is possible to have one debit interest calculated on the daily balance at 10%
and another one on the average balance at 12%.
This can be linked to the TAX table to take a TAX on the debit interest. Refer to the User
Guide chapter for System Tables for further details.
Ref : AI
April 2000
2-77
Release G10.2.02
GLOBUS USER GUIDE
This file also specifies the charges applicable to the group of ACCOUNT records. Refer to
GENERAL.CHARGE for more details.
Figure 2-53 GROUP.DEBIT.INTEREST
Ref : AI
April 2000
2-78
Release G10.2.02
GLOBUS USER GUIDE
2.3.12.2 ACCOUNT.DEBIT.LIMIT
This table allows overdraft limits to be specified for individual ACCOUNT records, which can
then be used as the LIMIT for the first rate of debit interest specified in the appropriate
GROUP.DEBIT.INT condition.
If a GROUP.DEBIT.INT record contains 2 rates, but no LIMIT for the first rate, the overdraft
LIMIT specified for each ACCOUNT in this table is used as the LIMIT for the first rate.
In this way it is possible to specify a different LIMIT for the first rate for each ACCOUNT,
without having to specify separate ACCOUNT.DEBIT.INT condition records.
If there is no LIMIT specified in this table for a particular ACCOUNT, a LIMIT of zero is
assumed, and the 2nd rate specified is effective for all balances.
Figure 2-54 ACCOUNT.DEBIT.LIMIT example
Ref : AI
April 2000
2-79
Release G10.2.02
GLOBUS USER GUIDE
2.3.12.3 ACCOUNT.DEBIT.INT
Any ACCOUNT that has a special set of debit interest conditions different from the group it
belongs to has to be defined in this file. When the interest is processed, GLOBUS will check
this file to see if a particular ACCOUNT has special conditions defined and if not will use the
general conditions for the group the ACCOUNT belongs to.
This can be linked to the TAX table to take a TAX on the debit interest. Refer to TAX in the
chapter on System Tables for details.
This file is also used to process the charges applicable to the ACCOUNT. Refer to
GENERAL.CHARGE for details.
Figure 2-55 ACCOUNT.DEBIT.INT
Ref : AI
April 2000
2-80
Release G10.2.02
GLOBUS USER GUIDE
2.3.12.4 GENERAL.CHARGE
This application provides the link between all the different charges in GLOBUS to the
ACCOUNT conditions and is used to specify for ACCOUNT groups which charges are to be
levied and what balance overrides are allowed. The GENERAL.CHARGE record applicable to
a particular ACCOUNT is specified in the relevant GROUP.DEBIT.INT or
ACCOUNT.DEBIT.INT record.
There are basically two types of charges within GLOBUS:
Interest related
Ledger Fee
Interest related charges are processed when the interest is capitalised or accrued. Ledger fee
charges are typically calculated at Monthly, Quarterly, Half-yearly or Yearly frequencies as
defined on the COMPANY record.
If the ACCOUNT has maintained a higher balance than that specified, calculated charges can
be waived. Separate sets of balance level details are specified for interest related charges and
for ledger fee charges.
Figure 2-56Example of Highest Debit Charge in General.Charge
Ref : AI
April 2000
2-81
Release G10.2.02
GLOBUS USER GUIDE
2.3.12.4.1 Interest Related Charges
Interest related charges include:
DEBIT.INT.ADDON
GOVERNMENT.MARGIN
HIGHEST DEBIT
INTEREST.STATEMENT
DEBIT.INT.ADDON, GOVERNMENT.MARGIN and HIGHEST.DEBIT are charged when

debit interest is applied. Either DEBIT.INT.ADDON or HIGHEST.DEBIT may be charged but
not both. INTEREST.STATEMENT is levied each time debit interest is applied.
Ref : AI
April 2000
2-82
Release G10.2.02
GLOBUS USER GUIDE
2.3.12.4.2 Ledger Fee Charges
Ledger fee charges may be applied Monthly, Quarterly, Half yearly or Yearly as specified in
the COMPANY record, always at the end of a calendar month.
The charges can be based on:
BALANCE.REQUIREMENT
NUMBER.OF CREDIT
NUMBER.OF DEBIT
TURNOVER.CREDIT
TURNOVER.DEBIT
TRANSACTION CODE SPECIFIC
HIGHEST DEBIT
Either NUMBER.OF.CREDIT with NUMBER.OF.DEBIT can be used to base charges or

TURNOVER.CREDIT with TURNOVER.DEBIT, but not both. It is possible to combine all
these charges into one charge. A notional amount of credit interest may be calculated and
deducted from the charge amount.
A waive marker may be set in ACCOUNT records to indicate that charges should be
calculated but not applied.
No Ledger fee charges are calculated on balances and activity in the month in which an
ACCOUNT is opened or closed, (unless the ACCOUNT.CLOSURE date is the last day of the
month).
Transaction code specific charges are applied in accordance with the rest of the charges
defined on the GENERAL.CHARGE record but can also be calculated on a daily basis. The
details of the charge scales are defined on the TRANSACTION.CHARGE application.
The GENERAL.CHARGE record referred to in the relevant GROUP.DEBIT INT record or
ACCOUNT.DEBIT.INT record specifies which of the following interest related charges are
applicable to an ACCOUNT. In each case the rate applicable is that ruling on the date of debit
interest application.
Ref : AI
April 2000
2-83
Release G10.2.02
GLOBUS USER GUIDE
2.3.13 Credit Interest Conditions

Similar to the debit interest conditions, credit interest conditions can be defined either at
group level or at an ACCOUNT level.
TAX can be taken on the credit interest paid to the ACCOUNT.
2.3.13.1 GROUP.CREDIT.INT
This file defines the group level credit interest conditions for all the ACCOUNT records in a
group. Two credit interest conditions can be defined to be applied on a group.
This table allows the specification of a calculation method for credit interest for the defined
groups. ACCOUNT groups are determined automatically on the basis of CUSTOMER and
ACCOUNT details such as COUNTRY (residence), SECTOR, CATEGORY and CURRENCY
as defined in ACCT.GEN.CONDITION.
Interest can be calculated on a Daily, Average or Minimum balance basis using value dated
balances.
Rates can be fixed or linked to basic rates (defined in the BASIC.INTEREST table) plus or
minus a Margin.
two balance levels.
For example it is possible to have one credit Interest calculated on the Daily Balance at 10%
and another one on the average balance at 12%.
This can be linked to the TAX table to take a TAX on the credit interest.
Ref : AI
April 2000
2-84
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-57 GROUP.CREDIT.INT
Ref : AI
April 2000
2-85
Release G10.2.02
GLOBUS USER GUIDE
2.3.13.2 ACCOUNT.CREDIT.INT
Any ACCOUNT that has a special set of credit interest conditions different from the group it
belongs to has to be defined in this file. When the interest is processed, GLOBUS will check
this file to see if a particular ACCOUNT has special conditions defined and if not, will use the
general conditions for the group the ACCOUNT belongs to.
This can be linked to the TAX table to take a tax on the credit interest. Refer to TAX table in
System Tables.
Figure 2-58 ACCOUNT.CREDIT.INT
Ref : AI
April 2000
2-86
Release G10.2.02
GLOBUS USER GUIDE
2.3.14 CHARGES
There are two types of charges are allowed within GLOBUS. They are Interest Related
Charges and Ledger Fee charges.
2.3.14.1 Interest Related Charges
Interest Related Charges include Debit Interest Add-on, Government Margin, Highest Debit
Charge and Interest Statement Charge. Debit Interest Add-on, Government Margin and
Highest Debit are charged when debit one interest is applied. Either Debit Interest Add-on or
Highest Debit may be charged but not both. Interest Statement Charge is levied each time
debit interest is applied.
2.3.14.2 Ledger Fee Charges
Ledger Fee Charges may be applied monthly, quarterly, half yearly or yearly as specified in
the Company record, always at the end of a calendar month.
The charges can be based on Highest Debit, Balance Requirement, Number of Credits,
Number of Debits, Turnover of Credits, Turnover of Debits and non immediate Transaction
charges depending on the Transaction Codes. Either the number of credits and debits or the
turnover figures can be charged, but not both. It is possible to combine all these charges into
one charge. A notional amount of credit interest may be calculated and deducted from the
charge amount.
A special type of ledger fee charge called transaction code based charge may be defined to be
applicable to a specific general charge or to all general charges. These charges are applied in
accordance with the other ledger fee charges but additionally can be calculated on a daily
basis.
A waive marker may be set in Account records to indicate that charges should be calculated
but not applied.
No Ledger Fee Charges are calculated on balances and activity in the month in which an
Account is opened or closed, (unless the Account Closure date is the last day of the month).
The GENERAL.CHARGE record referred to in the relevant GROUP.DEBIT.INTEREST
record or ACCOUNT.DEBIT.INTEREST record specifies which of the following interest
related charges are applicable to an Account. In each case the rate applicable is that ruling on
the date of Debit 1 interest application.
Ref : AI
April 2000
2-87
Release G10.2.02
GLOBUS USER GUIDE
2.3.14.3 DEBIT.INT.ADDON
The purpose of this table is to specify a supplementary flat percentage charge, which is to be
applied to the overdraft (debit 1) interest amount calculated by the system on capitalisation
date. No DEBIT.INT.ADDON is possible for debit 2 interest.
DEBIT.INT.ADDON represents the same type of charge as Highest Debit and for this reason
they cannot both be specified for application to any one particular Account.
Figure 2-59 DEBIT.INT.ADDON example
Free, minimum and maximum amounts of charge can be specified by currency and default
values can be input for currencies not specified.
Ref : AI
April 2000
2-88
Release G10.2.02
GLOBUS USER GUIDE
2.3.14.4 HIGHEST.DEBIT
This table allows the specification of a percentage charge, based upon the highest debit
balance recorded on an ACCOUNT during the application period for debit interest (debit 1) or
during the application of the ledger fee charges.
Separate charges can be defined for specific currencies, including local currency. A default
charge, in local currency equivalent, can be defined to cover all accounts in currencies not
specifically mentioned.
Figure 2-60 HIGHEST.DEBIT example
The highest debit charge can be treated as a ledger charge taken on the charge frequency
defined in the Company application. In making a calculation for the charge a provision is
made to allow the charge to be calculated for an entire charge period or monthly within the
charge period.
The field called HIGHEST.DEBIT.CH on the GENERAL.CHARGE application allows for the
specification of a highest debit record id. Any charge id linked to this field will be calculated
and posted according to the rules programmed for the charges.
Fields on the STMT.ACCT.CH, ACCR.ACCT.CH and INFO.ACCT.CH record all the
information related to this new charge.
Ref : AI
April 2000
2-89
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-61 Example of Highest.Debit.Chg on General.Charge.
Ref : AI
April 2000
2-90
Release G10.2.02
GLOBUS USER GUIDE
2.3.14.5 GOVERNMENT.MARGIN
GOVERNMENT.MARGIN is a supplementary flat percentage charge calculated on overdraft

balances by the system on capitalisation date and collected on behalf of the Government.
The same percentage charge is applicable for all currencies. However, it is possible to specify
minimum and maximum amounts for specific currencies as well as local currency equivalent
amounts, which apply to all other currencies.
If there are no overdraft balances during the debit interest capitalisation period, no
Government Margin charge is made.
Figure 2-62 GOVERNMENT.MARGIN example
Ref : AI
April 2000
2-91
Release G10.2.02
GLOBUS USER GUIDE
2.3.14.6 INTEREST.STATEMENT
The purpose of this table is to specify a flat fee, which is levied at the time of capitalisation of
debit interest. Specific charges can be entered by currency. For all currencies not specifically
mentioned, a default charge can be entered in local currency equivalent.
The GENERAL.CHARGE record referred to in the relevant GROUP.DEBIT.INT record or
ACCOUNT.DEBIT.INT record specifies which of the following ledger fee charges are
applicable to an ACCOUNT and whether each charge should be applied to the ACCOUNT as
a separate entry, or combined into one entry with other ledger fee charges.
All ledger fee charges are applied on the same day, monthly, quarterly six, monthly or yearly,
at the end of the appropriate month, as specified in the COMPANY record. In each case, the
details applicable are those ruling on the date of the charges application.
Figure 2-63 INTEREST.STATEMENT examples
Ref : AI
April 2000
2-92
Release G10.2.02
GLOBUS USER GUIDE
2.3.14.7 BALANCE.REQUIREMENT
The purpose of this table is to define a fixed ACCOUNT charge to be applied if a specified
balance is not maintained.
A range of charges for different balances may be specified.
The required balance may be defined as the minimum or average balance over a given period.
The charge is applied monthly, quarterly, six monthly or yearly as specified in the COMPANY
record. The GENERAL.CHARGE record specifies whether the calculation is in one step,
covering the balances over the whole period, or in monthly steps, applying the appropriate
charge for each month during which the required balance is not maintained.
Figure 2-64 BALANCE.REQUIREMENTS example
Ref : AI
April 2000
2-93
Release G10.2.02
GLOBUS USER GUIDE
2.3.14.8 NUMBER.OF.CREDIT
This table allows a fixed charge to be specified for each chargeable credit entry, which passes
over an ACCOUNT during the capitalisation period. Alternatively, the TURNOVER.CREDIT
table may be used to specify a charge expressed as a percentage of the total value of the
entries. Only one of these two types of charges can be specified for each ACCOUNT.
Entries are chargeable only if the record on the TRANSACTION table corresponding to the
transaction code in the entry contains Y in the TURNOVER.CHARGE field.
If the associated GENERAL.CHARGE record indicates that charges for debit and credit entries
should be combined, the total number of chargeable entries is calculated and then the details
from the NUMBER.OF.CREDIT table are used.
The amount per entry and free, minimum and maximum amounts may be defined for specific
currencies. Default amounts in local currency equivalent may also be defined and are used for
accounts in currencies for which no amounts are specified.
Figure 2-65 NUMBER.OF.CREDIT examples
Ref : AI
April 2000
2-94
Release G10.2.02
GLOBUS USER GUIDE
2.3.14.9 NUMBER.OF.DEBIT
This table allows a fixed charge to be specified for each chargeable debit entry, which passes
over an ACCOUNT during the capitalisation period. Alternatively, the TURNOVER.DEBIT
table may be used to specify a charge expressed as a percentage of the total value of the
entries. Only one of these two types of charges can be specified for each ACCOUNT.
The details of this table are exactly the same as the NUMBER.OF.CREDIT table. If the
associated GENERAL.CHARGE record indicates that charges for debit and credit entries
should be combined, the total number of chargeable entries is calculated and then the details
from the NUMBER.OF.CREDIT table are used.
Figure 2-66 NUMBER.OF.DEBIT examples
Ref : AI
April 2000
2-95
Release G10.2.02
GLOBUS USER GUIDE
2.3.14.10
TURNOVER.CREDIT
This table is used to specify a percentage charge on the total value of chargeable credit
entries, which pass over an ACCOUNT during the capitalisation period. Alternatively, the
NUMBER.OF.CREDIT table may be used to specify a fixed charge per entry. Only one of
these two types of charges can be specified for each ACCOUNT.
Entries are chargeable only if the record on the TRANSACTION table corresponding to the
transaction code in the entry contains Y in the TURNOVER.CHARGE field.
If the associated GENERAL.CHARGE record indicates that charges for debit and credit entries
should be combined, the total value of chargeable entries is calculated and then the details
from the TURNOVER.CREDIT table are used.
Free, minimum and maximum amounts may be defined for specific currencies. Default
amounts in local currency equivalent may also be defined and are used for accounts in
currencies for which no amounts are specified.
Figure 2-67 TURNOVER.CREDIT examples
Ref : AI
April 2000
2-96
Release G10.2.02
GLOBUS USER GUIDE
2.3.14.11
TURNOVER.DEBIT
This table is used to specify a percentage charge on the total value of chargeable debit entries,
which pass over an ACCOUNT during the capitalisation period. Alternatively, the
NUMBER.OF.DEBIT table may be used to specify a fixed charge per entry. Only one of these
two types of charges can be specified for each ACCOUNT.
The details of this table are exactly the same as the TURNOVER.CREDIT table. If the
associated GENERAL.CHARGE record indicates that charges for debit and credit entries
should be combined, the total value of chargeable entries is calculated and then the details
from the TURNOVER.CREDIT table are used.
Figure 2-68 TURNOVER.CREDIT examples
Ref : AI
April 2000
2-97
Release G10.2.02
GLOBUS USER GUIDE
2.3.14.12
TRANSACTION.CHARGE
This table allows a charge, determined by the TRANSACTION code, to be specified for each
entry that passes over an ACCOUNT during the capitalisation period. These charges may be
specified to be calculated on a daily basis.
The TRANSACTION table specifies which TRANSACTION.CHARGE (if any) is applicable to
each different TRANSACTION code.
The charge amount can be expressed either on a unit basis, which represents the cost per
entry, or as a percentage of the total value of the entries.
The amount per entry, free amount, minimum amount and maximum amount may be defined
for specific currencies. Default amounts, in local currency equivalent, are used for accounts in
currencies for which no amounts are specified.
Figure 2-69 TRANSACTION.CHARGE example
Ref : AI
April 2000
2-98
Release G10.2.02
GLOBUS USER GUIDE
2.3.15 Interest And Charges Processing

Interest is calculated on value dated balances. All entries over an ACCOUNT are considered
to have a value date, which is the date on which the entry affects the (value-dated) balance for
interest purposes.
If no value date is entered in a transaction, it may be added automatically by the system,
depending on rules specified in the TRANSACTION code table (TRANSACTION), or rules
specified in the application which generated the transaction (e.g. MONEY.MARKET).
If no value date has been entered or generated in an entry, a default of the booking date is
assumed, i.e. the entry is considered to affect the balance for interest purposes on the same
day as it is processed.
2.3.16 Interest Accruals

2.3.16.1 ACCR.ACCT.CR and ACCR.ACCT.CR2
These files contain details of the calculation of the credit interest that has been accrued on an
ACCOUNT but has not yet been posted to the account.
The files ACCR.ACCT.CR and ACCR.ACCT.CR2 are similar in layout and denote the CR or
the CR2 interest respectively.
2.3.16.2 ACCR.ACCT.DR and ACCR.ACCT.DR2
These files contain details of the calculation of the debit interest that has been accrued on an
ACCOUNT but has not yet been posted to the account.
The files ACCR.ACCT.DR and ACCR.ACCT.DR2 are similar in layout and denote the DR or
the DR2 interest respectively.
2.3.16.3 ACCR.ACCT.CH
This file contains details of the calculation of the charges that have been accrued on an
ACCOUNT but have not yet been posted.
Ref : AI
April 2000
2-99
Release G10.2.02
GLOBUS USER GUIDE
2.3.17 Interest Capitalisation

2.3.17.1 GROUP.CAPITALISATION
The purpose of this table is to specify the next date and subsequent frequency of application
of debit and credit interest, for a group of Accounts.
Interest may be applied on any day of the month. Cycles may be different for debit and credit
interest, (e.g. debit interest may be charged monthly and credit interest paid quarterly) unless
credit interest is only to be calculated as an offset to debit interest.
The date of debit interest application is also used as the date of application of interest related
charges. (These are DEBIT.INT ADDON, GOVERNMENT.MARGIN, HIGHEST.DEBIT and
INTEREST.STATEMENT)
If the Last Day Inclusive field in the ACCOUNT.ACCRUAL file contains Y, interest is
calculated on balances with value up to and including the capitalisation date. The value date
of the interest entry booked is the day after the capitalisation date. If Last Day Inclusive
contains NO only balances up to and including the previous working day are included. The
value date of the interest entry booked is the day after the last balance included.
Interest entries are booked to the ACCOUNT on the day they are calculated, or on the next
working day, depending on the application posting day specified in the
ACCOUNT.ACCRUAL record.
If the capitalisation date falls on a non-working day, the application is processed on the
previous working day, unless a month end accrual day falls before the capitalisation date, in
which case the application is processed on the next working day. In either case, the
calculation is up to the capitalisation date and the entries generated have the same value date
as they would have had if they had been processed on that date.
Figure 2-70 GROUP.CAPITALISATION example
Ref : AI
April 2000
2-100
Release G10.2.02
GLOBUS USER GUIDE
2.3.17.2 ACCT.CAPITALISATION
This table allows interest capitalisation dates to be specified for individual accounts,
overriding the dates specified for the associated group in the GROUP.CAPITALISATION
table.
The details included in this table are exactly the same as the GROUP.CAPITALISATION
table.
Figure 2-71 ACCT.CAPITALISATION example
2.3.17.3 ACCT.INTERIM.CAP
Used to request interim interest applications on particular ACCOUNT records, without

affecting the normal application cycles. The interim applications requested will be processed
during the end-of-day run on the day specified.
Figure 2-72 ACCT.INTERIM.CAP example
Ref : AI
April 2000
2-101
Release G10.2.02
GLOBUS USER GUIDE
2.3.17.4 ACCT.SUSP.SETTLE
Used to request settlement of interest and charges, which have been suspended and not
booked to Profit and Loss. The end of day program EOD.ACCT.SUSP removes the requested
amounts from the SUSPENSE.AMOUNT fields in the ACCOUNT record and generates the
appropriate entries for Profit and Loss.
2.3.17.5 TABLE.CAPITALIS.CORR
Used to request recalculation and correction of previously applied interest. (The system
automatically recalculates and corrects interest when entries with value dates prior to the last
interest application are processed, but does not automatically recognise back-valued changes
to interest rates or conditions.) The requested recalculations are processed during the
end-of-day run on the day specified.
Figure 2-73 TABLE.CAPITALIS.CORR example
Ref : AI
April 2000
2-102
Release G10.2.02
GLOBUS USER GUIDE
2.3.18 ENQUIRIES
2.3.18.1 INFO.ACCT.CR and INFO.ACCT.CR2
These applications may be used to request on-line calculations of credit interest for CR and
CR2. The results are for information only and no entries are generated.
The file layouts for the two files are similar and INFO.ACCT.CR calculates the CR Interest
and the INFO.ACCT.CR2 calculates the CR2 Interest.
The Verify function is used to initiate the calculations.
2.3.18.2 INFO.ACCT.DR and INFO.ACCT.DR2
These applications may be used to request on-line calculations of debit interest for DR and
DR2. The results are for information only and no entries are generated.
The file layouts for the two files are similar and INFO.ACCT.DR calculates the DR Interest
and the INFO.ACCT.DR2 calculates the DR2 Interest.
2.3.18.3 INFO.ACCT.CH
This application may be used to request on-line calculations of charges. The results are for
information only and no entries are generated.
2.3.18.4 INFO.ACCT.PREMIUM
This application may be used to view on-line calculations of premium interests. The
calculations are initiated from an enquiry called INFO.ACCT.PREMIUM. The results are
for information only and no entries are generated.
Ref : AI
April 2000
2-103
Release G10.2.02
GLOBUS USER GUIDE
2.3.18.5 ACC.CURRENT.INT
This enquiry may be used to view on-line for an Account any Interest rate changes for a given
period.
Figure 2-74 Enquiry - ACC.CURRENT.INT
Ref : AI
April 2000
2-104
Release G10.2.02
GLOBUS USER GUIDE
2.3.19 FILES USED

2.3.19.1 ACCT.ACTIVITY
ACCT.ACTIVITY contains details of ACCOUNT balances and activity used to calculate

interest and charges
Details are held in separate records for each ACCOUNT for each month in which there has
been any activity over the ACCOUNT or in which the value dated balance changes.
The details held in this file for the calculation of interest include value-dated balances and
total debit and credit turnover for each value date.
The details held for the calculation of charges include the total number of entries with each
different TRANSACTION code processed during the month, and the total value of the entries
with each TRANSACTION code. These details are held in the record for the month in which
the entries are processed, regardless of the value dates of the entries.
The value dated balances are also used for the calculation of BALANCE.REQUIREMENT
charges and for determining whether a high enough balance has been maintained for waiving
charges and for calculating credit interest to offset charges.
This file is updated during the end of day process EOD.ACCT.ACTIVITY with the details of
every entry which has been generated during the day and also during the end of day
capitalisation processes, EOD.CAPITALIS.CORR and (unless next day posting is specified in
the ACCOUNT.ACCRUAL table) EOD.CAPITALISATION.
A new ACCOUNT activity record is generated every time an entry is encountered with a value
date or booking date in a month in which the ACCOUNT has not previously had any entries.
If an entry has a Value date in a different month from the booking date, at least 2 ACCOUNT
activity records are updated, one containing the value dated balances for interest purposes, the
other containing the numbers and amounts of transactions for charge purposes.
If an entry has a value date earlier than entries that have previously been processed for the
same ACCOUNT, all subsequent value dated balances are updated. This may involve updating
several ACCOUNT activity records. (Refer to Figure 2-42 ACCT.ACTIVITY - History of
account activity on page 2-59
Ref : AI
April 2000
2-105
Release G10.2.02
GLOBUS USER GUIDE
2.3.19.2 STMT.ACCT.CR and STMT.ACCT.CR2
These files contain details of the calculation of the credit interest that has been booked to the
client ACCOUNT.
The files STMT.ACCT.CR and STMT.ACCT.CR2 are similar in layout and denote the CR or
Figure 2-75 STMT.ACCT.CR Example
2.3.19.3 STMT.ACCT.DR and STMT.ACCT.DR2
These files contain details of the calculation of the debit interest that has been booked to the
client ACCOUNT.
The files STMT.ACCT.DR and STMT.ACCT.DR2 are similar in layout and denote the DR or
Ref : AI
April 2000
2-106
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-76 STMT.ACCR.DR Example
Ref : AI
April 2000
2-107
Release G10.2.02
GLOBUS USER GUIDE
2.3.19.4 STMT.ACCT.CH
This file contains details of the calculation of the charges that has been booked to the client
ACCOUNT.
Figure 2-77 STMT.ACCT.CH Example
Ref : AI
April 2000
2-108
Release G10.2.02
GLOBUS USER GUIDE
2.3.19.5 CORR.ACCT.CR and CORR.ACCT.CR2
These files contain details of the previous calculation of credit interest, which have been
capitalised and recalculated and corrected. The new details are held on the STMT.ACCT.CR
(CR2) files.
The files CORR.ACCT.CR and CORR.ACCT.CR2 are similar in layout and denote the CR or
Figure 2-78 CORR.ACCT.CR Example
Ref : AI
April 2000
2-109
Release G10.2.02
GLOBUS USER GUIDE
2.3.19.6 CORR.ACCT.DR and CORR.ACCT.DR2
These files contain details of the previous calculation of debit interest, which have been
capitalised and recalculated and corrected. The new details are held on the STMT.ACCT.DR
(DR2) files.
The files CORR.ACCT.DR and CORR.ACCT.DR2 are similar in layout and denote the DR or
Figure 2-79 CORR.ACCT.DR Example
Ref : AI
April 2000
2-110
Release G10.2.02
GLOBUS USER GUIDE
2.3.19.7 ACCR.ACCT.TRAN.CH
This file contains the details of the currently accrued transaction code based charges if these
were defined to be calculated on a daily basis on the TRANSACTION.CHARGE application.
Details of calculated charge amounts are used from this file at the time of capitalising charges,
when also these details are transferred to the STMT.ACCT.TRAN.CH file.
Figure 2-80 ACCR.ACCT.TRAN.CH Example
2.3.19.8 STMT.ACCT.TRAN.CH
This file contains the details of the previously applied transaction code based charges. A new
record is stored into this file for every capitalisation date for an account.
Ref : AI
April 2000
2-111
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-81 STMT.ACCT.TRAN.CH Example
Ref : AI
April 2000
2-112
Release G10.2.02
GLOBUS USER GUIDE
2.3.20 END OF DAY

The following programs run the BATCH and their general functions are described below:
2.3.20.1 INT.POST.NEXT
If interest entries have been generated for posting the next day, these must be processed
before any other ACCOUNT module end-of-day programs.
This Batch job posts interest entries generated during the previous end-of-day run if NEXT is
specified in the application posting day field in the ACCOUNT.ACCRUAL record.
The interest and charges module includes the following programs which must be run during
end-of-day processing, after processing any interest entries generated the previous day and
after the end-of-day processes which generate accounting entries for the various other
transaction processing modules. The programs must be run in this order.
2.3.20.2 EOD.ACCT.SUSP
Settles suspended interest and charges as requested via the table ACCT.SUSP.SETTLE, by
removing the requested amounts from the suspense amounts in the ACCOUNT record and
generating the appropriate entries for Profit and Loss.
2.3.20.3 EOD.ACCT.ACTIVITY
Updates opening balances in account records and the value dated balances and activity details
in the ACCT.ACTIVITY file used to calculate interest and charges.
It also updates files used by other end-of-day procedures in the ACCOUNT module in printing
account statements and in determining accounts to be included in the overdraft and referral
reports and accounts with back-valued entries, which may require corrections of interest
previously, applied and accounts which may be closed.
2.3.20.4 EOD.UPDATE.ACCT.ACT
Adds booking date information to the ACCT.ACTIVITY file for any entry made during the day
for which the value date did not equal the booking date.
2.3.20.5 EOD.CAPITALIS.CORR
Recalculates interest previously applied and generates correcting entries. It automatically

processes any accounts which have had entries with value dates prior to the last application
date, and also processes any accounts selected via TABLE.CAPITALIS.CORR.
Ref : AI
April 2000
2-113
Release G10.2.02
GLOBUS USER GUIDE
2.3.20.6 EOD.CAPITALISATION
Calculates and applies interest and charges on regular capitalisation dates (specified in the
GROUP or ACCT CAPITALISATION tables), on any interim application dates selected via
ACCT.INTERIM.CAP and for ACCOUNT records flagged for closure.
2.3.20.7 DAILY.CHARGES.EOD
Calculates on a daily basis, the charges that have accrued on accounts that have been linked to
transaction code based daily charges.
2.3.20.8 EOD.REBUILD.ACCT.GRP.COND
Some of the parameters in the ACCT.GROUP.CONDITION file cannot be changed on-line.

This is because a change made to them necessitates rebuilding the ACCT.AVAILABILITY file.
Therefore any changes to be made to these parameters are created into a request record, which
carry over the new values to the active records. This program is responsible for these
functions.
2.3.20.9 EOD.REBUILD.ACCT.AVAIL
The ACCT.AVAILABILITY file is crucial to the correct validations on account transactions. If

any of the parameters governing these validations change the ACCT.AVAILABILITY file
becomes out of sync and needs to be rebuilt for all of the accounts affected. This program
handles the rebuild of the ACCT.AVAILABILITY file.
2.3.20.10
EOD.ACCRUAL
Processes accrual of interest and charges on customer accounts, generating entries for profit
and loss. The days on which interest and charges are accrued are specified in the
ACCOUNT.ACCRUAL table. Interest may be accrued daily or monthly (on any day of the
month). Charges may be accrued monthly, at calendar month end, or only booked to profit
and loss when they are applied.
Ref : AI
April 2000
2-114
Release G10.2.02
GLOBUS USER GUIDE
2.3.21 DELIVERY
The delivery system is used to produce interest statements and interest and charges advices.
Formats, addresses and numbers of copies required are specified within the delivery system.
Interest and charges advices may be printed or sent via SWIFT.
The interest and charges module passes the required information to the Delivery system,
which transforms it into the appropriate messages.
The interest statement has a delivery code of 1950 and interest and charges advices have the
Delivery code of 1990.
Ref : AI
April 2000
2-115
Release G10.2.02
GLOBUS USER GUIDE
2.4
CHEQUE ISSUE & MANAGEMENT
2.4.1 Introduction
GLOBUS provides functionality for banks that have requirements to manage the issuing and
registration of cheques and bank drafts issued to their clients.
Banks can record requests for chequebooks ordered by customers and, as and when these
cheques are received from the vendors, issue them to the appropriate customer.
When a chequebook is issued to the client the range of the cheque numbers will be recorded
into a cheque register. Furthermore, when cheques are presented, stopped or returned, this
can also be recorded in the cheque register.
There is also the functionality to charge the client for the issuing of chequebooks, for charges
to be applied on the usage of cheques by the customers, and also a periodic charge for
possession of a chequebook.
On the presentation of a cheque, the cheque register is consulted to confirm that:
The Cheque number is valid for the account on which it is drawn

The Cheque has not been presented before
The Cheque has not been stopped by the client
When a cheque does not conform to the above rules, an override is requested. If the override
is accepted the cheque may still be used.
On completion of the above transaction the cheque register is updated with the last status on
the cheque.
Banks can issue cheques and drafts drawn on them. Details for these are stored in a similar
manner to customer cheques. Further details regarding the following could be obtained from
the system if required.
The name of the client to whom the cheque/draft was issued

The beneficiary of the cheque
The amount and currency of the cheque
The date and place of issue
The cheque number
Ref : AI
April 2000
2-116
Release G10.2.02
GLOBUS USER GUIDE
2.4.2 Setting up ACCOUNT.PARAMETER

To enable cheque processing functionality, the CHEQUE.REGISTER field on the
ACCOUNT.PARAMETER application needs to be set to a value of YES. This has been
illustrated as under:
Figure 2-82 ACCOUNT.PARAMETER setting required for Cheque Issue & Management
Ref : AI
April 2000
2-117
Release G10.2.02
GLOBUS USER GUIDE
2.4.3 Issuing Cheques to Customers

2.4.3.1 Setting up a cheque type
The first step towards issuing cheques on accounts is to set up a CHEQUE.TYPE record. This
record will allow specify certain default parameters associated with a class of cheques. An
example has been illustrated as under:
Figure 2-83 Setting up a Cheque Type
2.4.3.2 Setting up a charging structure for the issuing of cheques
The user can set up the charging rules in the CHEQUE.CHARGE application to levy charges
on cheques issued, cheques used, and also a periodic charge for having the cheque facility, as
illustrated under:
Figure 2-84 Setting up a Cheque Charge Type
Ref : AI
April 2000
2-118
Release G10.2.02
GLOBUS USER GUIDE
2.4.3.3 Linking a transaction code to a cheque type
In order to invoke the processing that will validate cheques issued to a client account, a
TRANSACTION record will need to be linked to the CHEQUE.TYPE created in step 4.3.1.4.
The transaction code used in the accounting entry raised for the cheque transaction must be
linked into a CHEQUE.TYPE record for the system to perform the extra validation associated
with cheque issue and management. An example of this has been illustrated as under:
Figure 2-85 Linking the CHEQUE.TYPE to TRANSACTION
Ref : AI
April 2000
2-119
Release G10.2.02
GLOBUS USER GUIDE
2.4.3.4 Issuing & Registering of Cheques
Cheques are issued to clients through the CHEQUE.ISSUE application. This has been
illustrated as under:
Figure 2-86 Issuing cheques to a customer
In the example above the client account 18888 has been issued 20 cheques of cheque type
CURR on the 22nd February 2000. The customer has also been charged $5.00 on the 22nd
February 2000 for the issuing of cheques. The cheque numbers will start from 10000 and go
up to 10020.
This action would create a cheque register update as shown under:
Figure 2-87 Updated Cheque Register
As seen in the figure above account number 18888 now has cheque 100001-100020 issued to
it.
Ref : AI
April 2000
2-120
Release G10.2.02
GLOBUS USER GUIDE
2.4.4 Issuing Bank Drafts

Bank drafts and cheques issued by the bank may be registered using the same procedure as
that detailed above, with the difference of using a Nostro account instead of a client account.
Thus a new cheque type for bank drafts would need to be set up (with Nostro accounts is the
category field), and a TRANSACTION record to be use when issuing drafts. The
TRANSACTION record would have to have CREDIT flagged in the DEBIT/CREDIT
indicator (as opposed to debit for client cheques). No CHEQUE.CHARGE record would be
required.
It should be noted that at present it is not possible to run a TELLER or FUNDS.TRANSFER
deal where both sides of the transaction refer to TRANSACTION records where the
CHEQUE.IND field is set to YES. In other words, it is not possible for a client to buy a
registered bank draft using their own registered cheques.
2.4.5 TELLER using cheque number
It is now possible to pass a TELLER transaction that debits the account number on which the
cheques were issued. The system will respond with overrides when cheques that have already
been presented or stopped are presented on a transaction.
Ref : AI
April 2000
2-121
Release G10.2.02
GLOBUS USER GUIDE
2.4.5.1 Presenting a cheque presented earlier
The following screen shot depicts how the system responds when attempting to present a
cheque already presented earlier to the system.
Figure 2-88 Entering a Teller Transaction for a cheque number already presented
Ref : AI
April 2000
2-122
Release G10.2.02
GLOBUS USER GUIDE
2.4.5.2 Stopped Cheques
In order to stop cheques the user will need to enter a PAYMENT.STOP record for the account
number on which the cheque has been issued (see section 2.2.9.15). This done as shown
under: The PAYMENT.STOP record must be authorised before the stop comes into effect.
Figure 2-89 Stopping Cheques
Ref : AI
April 2000
2-123
Release G10.2.02
GLOBUS USER GUIDE
This action would update the CHEQUE.REGISTER file as shown under:
Figure 2-90 Cheque Register after stopping cheques
Ref : AI
April 2000
2-124
Release G10.2.02
GLOBUS USER GUIDE
Now when an attempt is made to use a stopped cheque on a transaction the system responds
with an override message that has been illustrated in the figure below:
Figure 2-91 Teller Override on attempting to use a stopped Cheque
Ref : AI
April 2000
2-125
Release G10.2.02
GLOBUS USER GUIDE
If the answer to this override were Y then the TELLER record would record this message
into its OVERRIDE fields as shown under:
Figure 2-92 Override Message stored on TELLER
2.4.5.3 Returned Cheques
If a cheque is to be returned, then, by entering YES in the RETURN.CHEQUE field on

FUNDS.TRANSFER, it automatically returns a cheque, taking the payment from a return
suspense account as set in ACCOUNT.PARAMETER. The account that the transfer was
originally to have been from is then stored in DRAWN.ACCOUNT, which is found on both the
FUNDS.TRANSFER and STMT.ENTRY applications. The ranges in CHEQUE.REGISTER are
maintained as normal.
Ref : AI
April 2000
2-126
Release G10.2.02
GLOBUS USER GUIDE
2.5
Deposited Cheque Collection
The system handles the collection of deposited cheques, this is in addition to the normal
method of clearing cheques. The cheque clearing system takes cheques entered through
TELLER, FUNDS.TRANSFER or DATA.CAPTURE and creates a Cheque Collection Record
for each cheque. The cheque collection record can be processed individually or through
CHEQUE.BATCH which groups batches of cheques together for processing. The processing
caters for cheques deposited into the GLOBUS bank that clear in a certain or uncertain
number of days. For example foreign cheques may take an uncertain number of days to clear,
with this functionality GLOBUS can deal with this. While the cheques are waiting to be
collected the funds are posted to a Suspense account, upon the successful collection the funds
are the credited to the customer. If the cheque is returned the funds are suspense to a returned
suspense account.
2.5.1 Set-up
The cheque collection functionality is triggered by TRANSACTION codes. New transaction
codes are created to indicate whether processing is required or not. After the new transaction
codes have been created they are input onto the Account parameter record. For every
transaction created through Funds Transfer, Data Capture or Teller the system checks the
account parameter record for the transaction code. If the transaction code is not found on the
account parameter record the Cheque Collection processing is bypassed.
2.5.2 Transaction codes

New transaction codes must be created as a means of identifying the transaction to be
processed through the cheque collection processing.
There are two method of deciding which suspense account the funds go for clearing and
returns, the suspense category is either defined on the Bank Sort Code record or on the
account parameter record with the transaction code. The transaction code decides where the
funds should be put; there are a minimum of three transaction codes required on the account
parameter record. A transaction code must be created for the Collection of Cheques, the
Clearing of Cheques and the Return of Cheques. Multiple transaction codes can be set for
each of the mentioned cheque actions. The account parameter accepts multiple transaction
codes as a unique transaction code could be created for Funds Transfer, Data Capture and
Teller.
For example a cheque is deposited using a TRANSACTION code that is on the account
parameter record the transaction is then posted to the collection suspense account (as defined
by the collection category code on the ACCOUNT.PARAMETER record) and a Cheque
collection record is created.
Ref : AI
April 2000
2-127
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-93 Example of a cheque deposit transaction code for Cheque Clearing
Figure 2-94 Example of a collection transaction code
Ref : AI
April 2000
2-128
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-95 Example of a returned cheque transaction code
The above example transaction codes will be used though the remainder of this manual. The
transaction codes are entered onto the Account Parameter record and also used by the Teller
Transaction codes.
2.5.3 Category Code

New CATEGORY codes will need to be created to enable the set up of the new suspense
accounts. These CATEGORY codes specify which suspense account the funds should be held
in. The CATEGORY codes can be defined on the ACCOUNT.PARAMETER record and/or the
Bank sort code record, the differences will be explained later on. There must be at least one
category code for each transaction code. The category codes must be between the range of
10000 and 19999, thus defining them as internal accounts.
Figure 2-96 Example of a general cheque collection suspense category
Ref : AI
April 2000
2-129
Release G10.2.02
GLOBUS USER GUIDE
2.5.4 Suspense Accounts

Internal suspense accounts need to be created for each CATEGORY code. These internal
suspense accounts are updated when the corresponding transaction codes are used in a
transaction. As there are three main CATEGORY types required so too is there a need to create
a minimum of three internal Suspense accounts.
As the cheque progresses through the deposited Cheque Collection system the funds move
with it through the internal suspense accounts until the cheque it cleared. If the cheque is
returned then the returned suspense account will contain the value of the returned cheque.
Figure 2-97 Example of the general suspense account
Ref : AI
April 2000
2-130
Release G10.2.02
GLOBUS USER GUIDE
2.5.5 Account Parameter

The ACCOUNT.PARAMETER record determines whether or not the deposited cheque
collection functionality should be invoked. If the ACCOUNT.PARAMETER record has the
CHQ.DEP.TXN, DEF.COLL.SUSP, CHQ.COLL.TXN, CHQ.RTN.TXN and the DEF.RTN.SUSP fields
entered then the deposited cheque collection functionality is invoked.
The system decides what processing to invoke by locating the transaction code in the
transaction code fields (CHQ.DEP.TXN, CHQ.COLL.TXN and CHQ.RTN.TXN) on the ACCOUNT
.PARAMETER record.
If the TRANSACTION code is found the system then assigns a CATEGORY code to the
transaction. The CATEGORY code can come from two places; the BC.SORT.CODE record for
the bank sort code used in the transaction or from the ACCOUNT.PARAMETER record
(transaction codes can have associated category codes).
Figure 2-98 Example of the Account Parameter record
Ref : AI
April 2000
2-131
Release G10.2.02
GLOBUS USER GUIDE
2.5.6 Bank Sort code

Bank sort code records can be created with CATEGORY codes. The CATEGORY codes are
only used to suspense deposited cheque collection transactions if the
ACCOUNT.PARAMETER record is set. If the ACCOUNT.PARAMETER record has been set,
and a bank sort code is used by the transaction the system will firstly check the sort code
record for a CATEGORY code to suspense the funds. If there is no CATEGORY code it will
use the CATEGORY code from the ACCOUNT.PARAMETER record.
Having the CATEGORY codes on the BC.SORT.CODE records allow the funds to be posted
to individual suspense accounts for each bank.
Figure 2-99 Example of a BC.SORT.CODE record
2.5.7 FT LOCAL CLEARING and FT BC PARAMETER

The FT.BC.PARAMETER and the FT.LOCAL.CLEARING files go hand in hand. If you need
to create or modify the FT.BC.PARAMETER record then the FT.LOCAL.CLEARING record
should also be checked and/or updated. For further information on the FT.BC.PARAMETER
file and the FT.LOCAL.CLEARING file see the Funds Transfer and/or Local Clearing User
Guides.
Ref : AI
April 2000
2-132
Release G10.2.02
GLOBUS USER GUIDE
2.5.8 Cheque collection

The cheque collection records are created through Funds Transfer, Data Capture and Teller.
The normal processing for these applications occur however if the transaction code is found
on the account parameter record the system will also create a cheque collection record. In
Teller the TELLER.TRANSACTION code record contains the TRANSACTION code used in
the contract and in FUNDS.TRANSFER the FT.TXN.TYPE.CONDITION code record contains
the TRANSACTION code used in the contract.
Figure 2-100 Example of a FUNDS.TRANSFER record that will create a Cheque Collection record
In the above example the FT.TXN.TYPE.CONDITION record ICCH has a TRANSACTION

code of 551 (Deposited Cheque), therefore a cheque collection record has been created. For
every Funds Transfer, Data Capture and Teller transaction created the system searches
through the list of TRANSACTION codes on the ACCOUNT.PARAMETER trying to locate the
TRANSACTION code of the deal. The field on the ACCOUNT.PARAMETER where the
TRANSACTION code is found determines what processing is required for Cheque collection.
Normal account processing takes place on the transaction. In the below the example you will
see that the USD Nostro account has been debited $543.00 while the internal suspense
account has been credited with the $543.00, the customer account has not been credited. The
internal suspense account has been derived from the BC.SORT.CODE record 123 which has a
Collection suspense CATEGORY of 10400.
Ref : AI
April 2000
2-133
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-101 Example of the debit STMT.ENTRY record created for the above FUNDS.TRANSFER
Ref : AI
April 2000
2-134
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-102 Example of the credit STMT.ENTRY record created for the above FUNDS.TRANSFER
On the credit STMT.ENTRY record the CHQ.COLL.ID field indicates the Cheque Collection id
- Customer Account number.
The record is now available for processing through Cheque Collection. The Cheque collection
record shows the cheques status. Cheque Collection records are created with a status of
Deposited, this indicates a cheque has been entered into GLOBUS and is waiting to be
processed. Cheques can be processed individually in Cheque collection or in batches through
the Cheque Batch application (see Cheque Batch section).
Ref : AI
April 2000
2-135
Release G10.2.02
GLOBUS USER GUIDE
A Cheque can be Clearing, Cleared or Returned. The cheque collection CHQ.STATUS field
indicates what status the cheque is at. Cheques are usually sent for Clearing, and can come
back either returned or cleared. The Cheque collection record then has the CHQ.STATUS field
changed to the appropriate status.
The cheque collection record is processed through changing the CHQ.STATUS to the required
status. The status will be changed to clearing which means the cheque has been sent to the
appropriate bank for action. The reply from the bank will determine which status is to be
entered next, if the cheque is cleared the cheque collection record CHQ.STATUS field is
changed to cleared.
Figure 2-103 Example of a cleared Cheque collection record
The cheque collection record with a CHQ.STATUS of cleared will create the following
accounting entries. The accounting entries will credit the customer account and debit the
internal suspense account completing the transaction. Note no accounting entries are
generated when the cheque status changes from deposited to clearing.
Below the are all the entries raised by a cleared cheque with charges when processed through
the Cheque Collection application.
Ref : AI
April 2000
2-136
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-104 Accounting Entries raised
There are five entries raised by the clearing of a CHEQUE.COLLECTION record, the
crediting of the customer and the debiting of the suspense account are standard. There is one
entry for charges and the other two entries come from a linked FT.CHARGE.CODE.
Ref : AI
April 2000
2-137
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-105 Example of the debit STMT.ENTRY for the Cleared Cheque Collection record
Ref : AI
April 2000
2-138
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-106 Example of the credit STMT.ENTRY for the customer of a Cleared Cheque Collection
record
Cheques can be bounced/returned by the other bank this results in the funds being transferred
from the internal cheque collection suspense account to the returned cheque collection
suspense account. The returned suspense account can be derived from the either the
BC.SORT.CODE file or the ACCOUNT.PARAMETER file.
Ref : AI
April 2000
2-139
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-107 Example of a returned Cheque in Cheque Collection
Along with the normal accounting entries for the Funds Transfer there is the debiting of the
cheque collection suspense account and the crediting of the returned cheque collection
suspense account.
Figure 2-108 Accounting entries raised for a returned cheque
Ref : AI
April 2000
2-140
Release G10.2.02
GLOBUS USER GUIDE
2.5.9 Cheque Batch

CHEQUE.BATCH is the application that provides a method of clearing multiple deposited
cheques. Cheques can be of varying currencies and denominations with the validation
ensuring the entered total of each currency matches the calculated total for the batch. The
cheques are then returned by the external banks either Cleared or returned. The entire batch
can be updated, or individual items can be updated.
CHEQUE.COLLECTION records can only be added to the CHEQUE.BATCH record if they
have a status of Deposited, which will be changed to Clearing, as they are entered into the
CHEQUE.BATCH record.
The CHEQUE.COLLECTION record can be added in either by entering the
CHEQUE.COLLECTION ids individually into the CHEQUE.BATCH record or the can be
entered in a group by selecting a group from an ENQUIRY and then dropping the group into
the CHQ.COLL.ID field. The later method of populating the CHEQUE.BATCH record
automatically opens a new multi-value for each item in the group. This can be done using the
standard windows selection methods. Hold down the CTRL key, highlight the selected items
with the mouse pointer, drag the selection to the CHQ.COLL.ID field then drop the selection
into the field.
Figure 2-109 Example of the Cheque Batch record being populated by drag and drop from an enquiry
Ref : AI
April 2000
2-141
Release G10.2.02
GLOBUS USER GUIDE
The six items from the enquiry that are highlighted are dragged to the CHQ.COLL.ID field
which expands. The cheque batch record will look as below:
Figure 2-110 Example of the Cheque Batch record after being populated by drag and drop method
The CHEQUE.BATCH application will update the status of all the Cheque collection records
on the batch automatically. The record will stay with a status of clearing until a cheque or all
the cheques have been either cleared or returned.
Ref : AI
April 2000
2-142
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-111 Example of a Cheque Collection record updated by Cheque Batch
If a CHEQUE.COLLECTION record is part of a CHEQUE.BATCH the status of the record

can only be updated through the CHEQUE.BATCH application. In CHEQUE.BATCH it is
possible to update the status of individual CHEQUE.COLLECTION record or to update the
whole batch by changing the OVERALL.STATUS field to the desired status. Changing the
overall status field will update every CHEQUE.COLLECTION record that currently has a
status of clearing with the status entered in the OVERALL.STATUS field.
In the below example the cheque for USD 990.00 is returned, the individual status of the
CHEQUE.COLLECTION record has been updated leaving the status of all other
CHEQUE.COLLECTION record unchanged. The returned cheque funds will be posted to the
return Cheque Suspense account.
Ref : AI
April 2000
2-143
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-112 Example of a Cheque Batch record where one cheque has been returned
If the remaining cheques come back cleared then the OVERALL.STATUS can be updated to
cleared, this will populate all remaining status fields that have a status of clearing to Cleared.
Ref : AI
April 2000
2-144
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-113 Example of Cheque Batch record with Overall Status set to Cleared
All CHEQUE.COLLECTION records on this CHEQUE.BATCH record that have a status of

clearing have been set to cleared. Below is the CHEQUE.COLLECTION record that has been
returned noting this record has not been updated since the status had been set to returned.
Ref : AI
April 2000
2-145
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-114 CHEQUE.COLLECTION ID CC951070023 has status of CLEARED
Figure 2-115 CHEQUE.COLLECTION ID CC951070033 has status of RETURNED
Ref : AI
April 2000
2-146
Release G10.2.02
GLOBUS USER GUIDE
2.6
Bulk Accrual of Interest and Charges
2.6.1 Introduction
Interest and charges for accounts are accrued either on a DAILY or MONTHLY basis, the
default frequency being monthly. The frequency is normally defined in the
ACCOUNT.ACCRUAL application. Daily accruals may be requested for all accounts, all
foreign or all local, or by product category.
Whenever an ACCOUNT is capitalised (defined by the frequency in
GROUP.CAPITALISATION or ACCT.CAPTALISATION) the accrual calculation is repeated
to ensure that the accrued interest in P&L is accurate and the accrual balance in the CRB is
reversed.
When a daily (or other period) accrual is required for the accounts, however the accrual
entries do not need to be raised for each individual account, the level of currency, department
and product category or group should be sufficient. Accrual entries should be raised as a
single P&L (CATEG.ENTRY) and special (RE.CONSOL.SPEC.ENTRY) for each grouping.
When an ACCOUNT is capitalised, or a detailed accrual is required, the system will ensure
that the group accrual figure for as given account is reversed to avoid reporting the same
figure twice.
Ref : AI
April 2000
2-147
Release G10.2.02
GLOBUS USER GUIDE
2.6.2 Accounts to be accrued in bulk

This new bulk accrual facility is created to allow these daily (or other) periodic accruals and
postings to be performed at a high level. Where bulk accrual takes place the accrual
calculation is simplified and is simply on a daily accrual figure. The daily accrual figure can
be revised when an individual account moves.
2.6.2.1 Setting Group Accrual Parameter
The accounts to be accrued in bulk are identified by the GROUP.ACCRUAL.PARAM

application. See Figure below.
Figure 2-116 GROUP.ACCRUAL.PARAM
This identifies which product categories are to be accrued, the frequency of the accrual and
recalculation of daily accrual figures. Refer to Helptext for more information.
A rebuild of the group accrual files is necessary when a GROUP.ACCRUAL.PARAM
record is input and whenever the parameter settings for group accrual have been
changed. Refer to the Rebuilding Group Accrual section of this user guide.
In order to avoid accrual duplication, the table below has been provided to cross validate
GROUP.ACCRUAL.PARAM settings against ACCOUNT.ACCRUAL.
Ref : AI
April 2000
2-148
Release G10.2.02
GLOBUS USER GUIDE
ACCOUNT.ACCRUAL
ALLTYPE
DAILY.ACCR.TYPE
GROUP.ACCRUAL.PARAM
CATEGORY
ACCR.ALL.TYPE
BOTH
RESULT
INPUT ?
NO
LOCAL
BOTH
SAME
DIFFERENT
LOCAL
SAME
DIFFERENT
FOREIGN
SAME
DIFFERENT
NONE
SAME
DIFFERENT
FOREIGN
BOTH
SAME
DIFFERENT
LOCAL
SAME
DIFFERENT
FOREIGN
SAME
DIFFERENT
NONE
SAME
DIFFERENT
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
NO
NO
YES
NO
NO
NO
NO
NO
NO
NO
NO
YES
NO
NO
YES
NO
NO
NO
NO
NO
NO
NO
NO
YES
NO
NO
YES
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
BOTH
LOCAL
FOREIGN
NO
YES
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
YES
NO
NO
YES
NO
NO
YES
NO
NO
YES
NO
Table 7 Cross-validating GROUP.ACCRUAL.PARAM against ACCOUNT.ACCRUAL settings
Ref : AI
April 2000
2-149
Release G10.2.02
GLOBUS USER GUIDE
2.6.2.2 Switching Standard Account Accrual Off
For the Group accrual to take effect, the standard accrual processing needs to be switched off
for categories of account in the ACCOUNT.ACCRUAL application. See figure below.
Figure 2-117 Switching standard Account Accrual Off
Ref : AI
April 2000
2-150
Release G10.2.02
GLOBUS USER GUIDE
2.6.2.3 Rebuilding Group Accrual
A rebuild of the group accrual files is necessary when a GROUP.ACCRUAL.PARAM

record is input and whenever the parameter settings for group accrual have been
changed.
The Group Accrual files can be rebuilt on-line or as part of the batch processing.
The application REBUILD.GROUP.ACCRUAL is used to drive the rebuilding of Group
Accrual. The figure below shows the accrual of all current accounts.
Figure 2-118 REBUILD.GROUP.ACCRUAL
Note: REBUILD.GROUP.ACCRUAL is run in Verify mode for an on-line rebuild.

To run the rebuild during the batch processing, the ad-hoc batch job
B.REBUILD.GROUP.ACCRUAL, contained in the GROUP.ACCRUAL.EOD BATCH record,
needs to be set to run. Input into the DATA field is the id of the REBUILD.GROUP.ACCRUAL
record, which will be executed in the batch.
Ref : AI
April 2000
2-151
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-119 Rebuilding GROUP ACCRUAL during the batch
Ref : AI
April 2000
2-152
Release G10.2.02
GLOBUS USER GUIDE
2.6.2.4 Calculation of Daily Accrual Figures
Each account subject to group accrual will store a daily average accrual figure for each type
of interest and/or charge defined. This figure will be re-calculated either when an account
moves or when a scheduled recalculation is run. The figure is calculated by projecting the
interest forwards to the next capitalisation date (based on the current account balances). The
projected interest / charge amount is then divided by the period of the calculation to give an
average daily amount. The daily amount will be stored in the application
GROUP.ACCRUAL.DETAIL (See figure below); amounts will be held by P&L category.
Figure 2-120 GROUP.ACCRUAL.DETAIL
Ref : AI
April 2000
2-153
Release G10.2.02
GLOBUS USER GUIDE
2.6.2.5 Posting of Group Accrual
The GROUP.ACCRUAL.DETAIL application will be consolidated periodically by currency,

product category and department, the total balances will be held in the
GROUP.ACCRUAL.BALANCES application (See figure below). The periodic accrual process
will post the difference between the previous total and the current accrual total.
Figure 2-121 GROUP.ACCRUAL.BALANCES
Ref : AI
April 2000
2-154
Release G10.2.02
GLOBUS USER GUIDE
Index of Tables & Figures

Table 2-1 Standard Charge types....................................................................................................................2-17
Table 2-2 Maintenance Charges......................................................................................................................2-18
Table 2-3 Accounting entries - no netting.......................................................................................................2-29
Table 2-4 Accounting entries - with netting ...................................................................................................2-29
Table 2-5 ACCOUNT.CLASS - CLASS record types...................................................................................2-39
Table 2-6 ACCOUNT.CLASS - ACCOUNT record types............................................................................2-41
Table 7 Cross-validating GROUP.ACCRUAL.PARAM against ACCOUNT.ACCRUAL settings .......2-149
Figure 2-1 Simple Current ACCOUNT............................................................................................................2-3
Figure 2-2 ACCOUNT - Example Nostro account ..........................................................................................2-4
Figure 2-3 Simple internal ACCOUNT (Cash Account).................................................................................2-5
Figure 2-4 Format of an internal account number..........................................................................................2-6
Figure 2-5 ACCOUNT - Details of a customer account ..................................................................................2-7
Figure 2-6 Example of an internal Account .....................................................................................................2-9
Figure 2-7 ACCOUNT.CLOSURE .................................................................................................................2-12
Figure 2-8 Structure of the account default tables ........................................................................................2-14
Figure 2-9 Structure of the group tables ........................................................................................................2-15
Figure 2-10 PRINT.STATEMENT - Example.............................................................................................2-21
Figure 2-11 Example of AC.VIOLATION record.........................................................................................2-22
Figure 2-12 AC.SWEEP.TYPE .......................................................................................................................2-24
Figure 2-13 AC.ACCOUNT.LINK .................................................................................................................2-25
Figure 2-14 AC.ACCOUNT.SWEEP.HIST ...................................................................................................2-26
Figure 2-15 Net payments processing diagram..............................................................................................2-28
Figure 2-16 An example ACCOUNT.CLASS record defining the netting suspense account ....................2-30
Figure 2-17 Example payment netting suspense account........................................................................... ...2-31
Figure 2-18 ACCOUNT.PARAMETER - Master control of the Account module.....................................2-33
Figure 2-19 ALT.ACCT.PARAMETER - Defining an alternative account number .................................2-34
Figure 2-20 POSTING.RESTICT - Defining-posting restrictions ...............................................................2-35
Figure 2-21 Referral example................................................................................................... .......................2-36
Figure 2-22 ACCOUNT.CLASS - Example of a class parameter .............................................................2-37
Figure 2-23 ACCOUNT.CLASS - Example of an 'account' parameter ......................................................2-38
Figure 2-24 AC.STMT.PARAMETER - Statement defaults for accounts ..................................................2-42
Figure 2-25 STMT.GEN.CONDITION - Specifying defaults for statement frequencies...........................2-43
Figure 2-26 ACCOUNT.STATEMENT - Statement details for a single account.......................................2-44
Figure 2-27 ACCOUNT.STATEMENT fields for timed MT942 messages.................................................2-45
Figure 2-28 Verify a DE.MT942.REQUEST record to request an interim transaction report .................2-45
Figure 2-29 ACCT.GROUP.CONDITION - Account Group Condition Parameters ................................2-46
Figure 2-30 Defining violating transaction codes and thresholds.................................................................2-47
Figure 2-31 SAVINGS.PREMIUM - Parameters for premium types .........................................................2-48
Figure 2-32 PREMIUM DETAILS - Details of premium interest ...............................................................2-49
Figure 2-33 NOTICE WITHDRAWAL - Notice given for withdrawal.......................................................2-50
Figure 2-34 NOSTRO.ACCOUNT - Specifying default Nostro accounts ...................................................2-51
Figure 2-35 PAYMENT.STOP - Instructions to stop payments ..................................................................2-52
Figure 2-36 PAYMENT.STOP.TYPE - Reasons for stopping a payment...................................................2-53
Figure 2-37 NETTING.PARAMETERS - control of the payment netting facility.....................................2-54
Figure 2-38 NETTING.AGREEMENT - permitting payment netting for a customer ..............................2-55
Figure 2-39 NETTING.ENTRY - details of payments being netted ............................................................2-56
Figure 2-40 CREATE.NETTING - on-line creation of net payments..........................................................2-57
Figure 2-41 NETTING - reviewing and modifying net payments ................................................................2-58
Figure 2-42 ACCT.ACTIVITY - History of account activity .......................................................................2-59
Figure 2-43 ACCT AVAILABILITY - Availability of funds on Accounts..................................................2-60
Figure 2-44 Overdraft report ................................................................................................... .......................2-61
Figure 2-45 ACCT.GROUP.CONDITION - How to waive credit interest .................................................2-64
Figure 2-46 AC.VIOLATION - Waive interest status............................................................................... ....2-65
Ref : AI
April 2000
2-155
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-47 Setting up parameters for Pre-Notification of debit interest and / or charges .......................2-69
Figure 2-48 Making adjustments to pending debit interest ..........................................................................2-70
Figure 2-49 Making Adjustments to pending charges ..................................................................................2-71
Figure 2-50 Condition Priority example.........................................................................................................2-73
Figure 2-51 ACCOUNT.GEN.CONDITION .................................................................................................2-75
Figure 2-52 Account Accrual...........................................................................................................................2-76
Figure 2-53 GROUP.DEBIT.INTEREST.......................................................................................................2-78
Figure 2-54 ACCOUNT.DEBIT.LIMIT example..........................................................................................2-79
Figure 2-55 ACCOUNT.DEBIT.INT..............................................................................................................2-80
Figure 2-56Example of Highest Debit Charge in General.Charge...............................................................2-81
Figure 2-57 GROUP.CREDIT.INT ................................................................................................................2-85
Figure 2-58 ACCOUNT.CREDIT.INT...........................................................................................................2-86
Figure 2-59 DEBIT.INT.ADDON example ....................................................................................................2-88
Figure 2-60 HIGHEST.DEBIT example.........................................................................................................2-89
Figure 2-61 Example of Highest.Debit.Chg on General.Charge. ................................................................2-90
Figure 2-62 GOVERNMENT.MARGIN example.........................................................................................2-91
Figure 2-63 INTEREST.STATEMENT examples.........................................................................................2-92
Figure 2-64 BALANCE.REQUIREMENTS example ...................................................................................2-93
Figure 2-65 NUMBER.OF.CREDIT examples ..............................................................................................2-94
Figure 2-66 NUMBER.OF.DEBIT examples .................................................................................................2-95
Figure 2-67 TURNOVER.CREDIT examples................................................................................................2-96
Figure 2-68 TURNOVER.CREDIT examples................................................................................................2-97
Figure 2-69 TRANSACTION.CHARGE example ........................................................................................2-98
Figure 2-70 GROUP.CAPITALISATION example ....................................................................................2-100
Figure 2-71 ACCT.CAPITALISATION example .......................................................................................2-101
Figure 2-72 ACCT.INTERIM.CAP example ...............................................................................................2-101
Figure 2-73 TABLE.CAPITALIS.CORR example .....................................................................................2-102
Figure 2-74 Enquiry - ACC.CURRENT.INT...............................................................................................2-104
Figure 2-75 STMT.ACCT.CR Example .......................................................................................................2-106
Figure 2-76 STMT.ACCR.DR Example.......................................................................................................2-107
Figure 2-77 STMT.ACCT.CH Example.......................................................................................................2-108
Figure 2-78 CORR.ACCT.CR Example.......................................................................................................2-109
Figure 2-79 CORR.ACCT.DR Example.......................................................................................................2-110
Figure 2-80 ACCR.ACCT.TRAN.CH Example ..........................................................................................2-111
Figure 2-81 STMT.ACCT.TRAN.CH Example...........................................................................................2-112
Figure 2-82 ACCOUNT.PARAMETER setting required for Cheque Issue & Management .................2-117
Figure 2-83 Setting up a Cheque Type .........................................................................................................2-118
Figure 2-84 Setting up a Cheque Charge Type............................................................................................2-118
Figure 2-85 Linking the CHEQUE.TYPE to TRANSACTION .................................................................2-119
Figure 2-86 Issuing cheques to a customer...................................................................................................2-120
Figure 2-87 Updated Cheque Register..........................................................................................................2-120
Figure 2-88 Entering a Teller Transaction for a cheque number already presented ...............................2-122
Figure 2-89 Stopping Cheques.......................................................................................................................2-123
Figure 2-90 Cheque Register after stopping cheques ..................................................................................2-124
Figure 2-91 Teller Override on attempting to use a stopped Cheque ........................................................2-125
Figure 2-92 Override Message stored on TELLER.....................................................................................2-126
Figure 2-93 Example of a cheque deposit transaction code for Cheque Clearing ....................................2-128
Figure 2-94 Example of a collection transaction code ........................................................................... ......2-128
Figure 2-95 Example of a returned cheque transaction code .....................................................................2-129
Figure 2-96 Example of a general cheque collection suspense category ....................................................2-129
Figure 2-97 Example of the general suspense account ................................................................................2-130
Figure 2-98 Example of the Account Parameter record .............................................................................2-131
Figure 2-99 Example of a BC.SORT.CODE record ....................................................................................2-132
Figure 2-100 Example of a FUNDS.TRANSFER record that will create a Cheque Collection record ..2-133
Figure 2-101 Example of the debit STMT.ENTRY record created for the above FUNDS.TRANSFER2-134
Figure 2-102 Example of the credit STMT.ENTRY record created for the above FUNDS.TRANSFER2135
Ref : AI
April 2000
2-156
Release G10.2.02
GLOBUS USER GUIDE
Figure 2-103 Example of a cleared Cheque collection record ....................................................................2-136

Figure 2-104 Accounting Entries raised .......................................................................................................2-137
Figure 2-105 Example of the debit STMT.ENTRY for the Cleared Cheque Collection record..............2-138
Figure 2-106 Example of the credit STMT.ENTRY for the customer of a Cleared Cheque Collection
record ......................................................................................................................... ............................2-139
Figure 2-107 Example of a returned Cheque in Cheque Collection...........................................................2-140
Figure 2-108 Accounting entries raised for a returned cheque ..................................................................2-140
Figure 2-109 Example of the Cheque Batch record being populated by drag and drop from an enquiry2141
Figure 2-110 Example of the Cheque Batch record after being populated by drag and drop method...2-142
Figure 2-111 Example of a Cheque Collection record updated by Cheque Batch....................................2-143
Figure 2-112 Example of a Cheque Batch record where one cheque has been returned .........................2-144
Figure 2-113 Example of Cheque Batch record with Overall Status set to Cleared.................................2-145
Figure 2-114 CHEQUE.COLLECTION ID CC951070023 has status of CLEARED............................2-146
Figure 2-115 CHEQUE.COLLECTION ID CC951070033 has status of RETURNED.........................2-146
Figure 2-116 GROUP.ACCRUAL.PARAM ................................................................................................2-148
Figure 2-117 Switching standard Account Accrual Off ..............................................................................2-150
Figure 2-118 REBUILD.GROUP.ACCRUAL .............................................................................................2-151
Figure 2-119 Rebuilding GROUP ACCRUAL during the batch ...............................................................2-152
Figure 2-120 GROUP.ACCRUAL.DETAIL ................................................................................................2-153
Figure 2-121 GROUP.ACCRUAL.BALANCES..........................................................................................2-154
Ref : AI
April 2000
2-157
Release G10.2.02

Ai PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Ai PDF

Hochgeladen von

Copyright:

Verfügbare Formate

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

ACCOUNTS, INTEREST &

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

ACCOUNTS, INTEREST & CHARGES .............................................................2-1

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

2.2.9.9 Ad-hoc Interim transaction (MT942) reports.............................................................2-45

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

2.3.14.11 TURNOVER.DEBIT ............................................................................................2-97

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

Transaction codes .........................................................................................................2-127

2.6 Bulk Accrual of Interest and Charges................................................................................2-147

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

2 ACCOUNTS, INTEREST & CHARGES

Calculation of interest on client accounts

Calculation of premium interest on client accounts

Calculation of charges relating to the maintenance and servicing of accounts

Pre-notification of debit interest and/or charges on client accounts

Production of statements, overdraft and referral reports

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

2.1.1 Client Account

These options are detailed later in this guide.

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

An example of a simple current account is shown below:

Figure 2-1 Simple Current ACCOUNT

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

Figure 2-2 ACCOUNT - Example Nostro account

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

2.1.2 Internal Accounts

Figure 2-3 Simple internal ACCOUNT (Cash Account)

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

2.1.3 Account Number Format

2.1.3.1 Client format

The ACCOUNT number on client accounts is a number of up to 16 characters. The format of

2.1.3.2 Internal Format

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

2.1.4 Account Input

Figure 2-5 ACCOUNT - Details of a customer account

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

Interest rates and methods

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

2.1.4.2 Internal account input

Internal ACCOUNT records may be opened manually or automatically. The id of an internal

Figure 2-6 Example of an internal Account

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

2.1.5 NOSTRO Accounts

GLOBUS USER GUIDE

ACCOUNTS, INTEREST & CHARGES

2.1.7 Account Closure