MULTI-COMPANY

&
MULTI-BOOK
 MULTI-COMPANY
 GLOBUS/T24 supports operation of multiple
companies within one system. These can operate
independently or they can share CUSTOMER files
and/or certain files that contain controlling
(“static”) financial information. Companies can
also share operation of Nostro accounts. SMS
maintains security of access at company level.

 Transactions can take place involving accounts in

different companies and appropriate entries will
be made to inter-company accounts automatically.

 You can produce CRF reports for combinations of

companies with currencies converted as required.
 MULTI – BOOK
 Multi Book product has been developed to simplify multi
branch processing mainly in terms of system setup and
enhanced enquiry and reporting functionality.

 It allows independent financial entities to produce

independent balanced books while sharing the same
financial data files
 CUSTOMER
 NOSTRO ACCOUNT

 The major differences between Multi Book and Multi

Company are
 All financial level data is held in a single database.
 Close of Business processing all branches linked to the
same lead company are processed in the same job.
 It is relatively simple to move a customer accounts and
contracts from one branch to another, without the need to
close and reopen them and similarly to be able to close and
merge branches within the same branch structure.
 TYPES OF COMPANY
 3 possible Types of company in GLOBUS
 Master Company
• This is the first company set up in GLOBUS installation
(normally BNK)
• It owns a complete set of data tables.
• The master company can also be a Lead Company
 Lead Company
• This is identical to a normal multi company
• It can share files with other companies and stores all
financial level data in its own set of tables.
• A lead company is defined on installation by indicating
that the financial tables are to be owned by the company
being created.
 Branch Company
A branch company is defined on installation by
indicating that the Customer files, financial tables
are all to be owned by the Master/Lead company being
created.
 Deciding which structure
to set up
 Multi Company
 A set of Lead companies which can share various
data table types
 Multi Branch
 A set of Branches linked to Master Company
sharing the master company tables with the
exception of financial reporting (FRP) tables
 Combined
 A set of Lead companies, which can share
various data table types where each Lead
company may also have a set of Branch companies
liked to it if required
***With both the MC and MB installed it is
possible to set up the system to combines
all types of company
 Deciding which structure
to set up
 A Multi Branch structure should be
set up if
 Share the local currency
 Share CUSTOMER file
 There is no requirement for separate
COB processing for different group of
companies
 A Multi Company structure set up is
required if
 There is more than 1 local currency
 It is required to have more than 1
CUSTOMER file
 INTERCO.PARAMETER
 The INTERCO.PARAMETER contains the
details of whether a multi-company
accounting environment is being
used.
 There is only one record (SYSTEM) on
this file; if the record is missing
then GLOBUS/T24 assumes that a
single company environment exists.
 This record need to be authorised
before creating the second company.
INTERCO.PARAMETER for
Multi Company
INTERCO.PARAMETER for
Multi Branch
INTERCO.PARAMETER for
combined MB and MC
Setting up a New
Company
Information about the new company must be
obtain before creating the new company
 Mnemonic
 Local currency
 Financial year-end
 The sub-division number
 Files to be shares or not shared
 Company digits in the Account Number (Mainly
for Multi Company)
 Applications to be run under the company
 Applications requiring the AUTO.ID function
 Creation of the COMPANY record
 Create new record in the COMPANY.GROUP file if required
 Run the application CREATE.MASTER.COMP.BATCH. This will
reverse out all the Batch records and create new batch
records for the existing company with the company mnemonic
at the front. Only for Multi Company.
 Check BATCH.NEW.COMPANY
 Run application COMPANY.CREATE
 This application replaces COMPANY.INS
 Objective is to make the creation of a new company
 Reduce the amount of Data to input into a new COMPANY
record
 Default as much data as possible from the existing company
record
 Automate the creation of authorized records for the new
company as much as possible.
 Using the verify (V) function control will be passed to
COMPANY application in installation mode where the new
company record will be updated.
 Sample of COMPANY.CREATE
for a Branch

FINANCIAL.COM will determine whether a Lead or a Branch

Company is being created.
DEFAULT.COM is used to identify the company record that
will provide the data to default values into the new
company record
 After creation of the New
Company
 Modify USER records so that access to the new company is
allowed.
 Input and Authorise the DATES record for the new
company. On this record the RUN.DATE and
NEXT.WORKING.DAY must be the same as on the first
company created.
 Create an ABBREVIATION for changing to New Company.
 Update the INTERCO.PARAMETER SYSTEM record. The above is
done before signing onto the New Company. It will be
necessary to sign off and on again to obtain use of the
modified details to the USER and INTERCO.PARAMETER file
records.
 Create a record in the REVALUATION.PARAMETER file with
parameters set up for the following: ‘AL’ – Asset and
Liability revaluation, ‘FX’ – Forex, ‘FX.SP’ – Forex
spot revaluation, and ‘FX.RB’ – Forex rebate revaluation
 Input and authorise the records on the BATCH file,
Parameter level files, DATE record etc.
Company record
 HOLIDAY RECORD
 It is possible that not all branches
will follow the working day of Lead
company, HO may not work at weekends
whereas the branches do.
 3 different holiday tables can be
defined in the COMPANY record
 OFFICIAL.HOLIDAY
• The business holiday table for local country
 BRANCH.HOLIDAY
• The business holiday table for this company
 BATCH.HOLIDAY
• The holiday table that controls which days
the COB processing occurs
 Inter Branch/Compnay
Accounting
 Whenever there is an account in transaction
that belongs to another book/company, then the
inter- book/company entries will be raised.
Example : Debit AC/1 in HO and Credit with
AC/2 in Santhom Branch/company
HO
DR. AC/1
CR. Inter-Branch/company Account : Santhom
Branch

Santhom Branch
DR. Inter-Branch/Company Account : HO
CR. AC/2
Internal Account Format
Multi Company
 The standard format of T24 internal account is :
CCY : CATEGORY : NNNN
Where :-
CCY a alphabetic character currency code
CATEGORY is 5 digit numeric category code
NNNN is 4 digit numeric identifier which will be sub division
code
Multi Book
 In the Multi-book setup there is an additional 4 numeric character
sub division code of the company that owns the internal account
CCY : CATEGORY : NNNN : SSSS
Where :
CCY a alphabetic character currency code
CATEGORY is 5 digit numeric category code
CATEGORY is the inter-branch account category from the
ACCOUNT.CLASS record, ID = INTERCO
SSSS Sub Division Code
TRANSFER ACCOUNT/CONTRACTS
A customer can ask for his/her
accounts and contracts to be
transferred to another branch.
 EB.COMPANY.CHANGE application
will be used to process
 CLOSE/MERGE BRANCH
 Using EB.TNSFER.COMPANY
application
 ID is the company to be closed
Thank You