Scribd
Upload
822 views32 pages

Directory Structure of T24

This document discusses file naming conventions in T24 multi-company bank setups. It explains that each company has its own set of files with the company mnemonic added to the file name (e.g. FCOM1.ACCOUNT). INT files like F.COMPANY are shared across all companies while FIN files are company-specific. It also describes different multi-company setup types including multi-book, extended multi-company, and setups with branches in different countries each needing their own currency.

Uploaded by

Preethi Gopalan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
822 views32 pages

Directory Structure of T24

This document discusses file naming conventions in T24 multi-company bank setups. It explains that each company has its own set of files with the company mnemonic added to the file name (e.g. FCOM1.ACCOUNT). INT files like F.COMPANY are shared across all companies while FIN files are company-specific. It also describes different multi-company setup types including multi-book, extended multi-company, and setups with branches in different countries each needing their own currency.

Uploaded by

Preethi Gopalan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 32

This is the contents of the T24 bnk.

data
directory when only the Master Company
is
present
 Now when we add another company, a new
set of files get created. But, how can you
 have two files with the same name at database
level?
So in order to differentiate one Company
file set from another, the Company
Mnemonic is part of the file name
 All files at jBASE level follow the naming
convention F.Filename. So this is how you
 arrive at the naming convention that T24 uses –
F<Mnemonic>.FileName
An example of a multi company set up. At
least one Lead Company for each local
currency should be created in T24
If there is only one Lead Company with
multiple Branch Companies, the T24
installation is called a Multi Book Setup.
All Branches will share the files of the Lead
Company
In an installation of T24 in which the local
currency is the same, then there is no need
to create different Lead companies.
However, if you need you may also create
multiple
Lead companies with the same currency
Multiple Lead Companies with Branch
Companies is referred to as an
Extended Multi Company Setup.
INT files will be shared by all the Lead and
Branch Companies. Example –
F.COMPANY, F.SPF.
FIN files are Company specific. Example –
FCOM1.ACCOUNT,
FCOM2.ACCOUNT, FCOM3.ACCOUNT.
CUS files can be Company specific or can
be shared.
Banks that implement T24 can have
branches around the world. Different
countries
have different local currencies. In such a
case in T24 you should create at least one
Lead company for each local currency in
T24
INT type of files are always shared by all
Lead and Branch companies
CUS type of files are shared in most
installations, but can also be separate for
Lead
companies. All these files are stored at the
Central Server
FIN type of files cannot be shared. Each
Lead company should have one set of FIN
files.

You might also like