Sharing Information Between Companies

Branches Working on Holidays

COMPANY.GROUP
Example of File Classification
Global Processing
Impact on versions
Transferring Account and Contracts
ACCOUNT.CLASS
INTERCO.PARAMETER
COMPANY
HOLIDAY
BATCH.HOLIDAY

This field defines the holiday table that will be used to control the T24 batch cycling.

It is possible to define a BATCH.HOLIDAY value that is different to either the OFFICIAL.HOLIDAY or BRANC

For example the bank may decide to run a batch 365 days per year even if on some days none of the bran

The holiday table defined for this field will NOT be used as a default in any date calculations made for bus

Validation Rules:

Mandatory input for the master company, if no input is made it will default to the value of the BATCH.HOL

Must be a valid entry on the REGION table, i.e. a two character country code followed by 2 numeric chara

If only the 2 character country code is input then the field value will be appended with 00

Unless GLOBAL.PROCESSING is set to Y in the SPF, SYSTEM record then this field must be the same as the

For a book company, this field must be same as its lead company's BATCH.HOLIDAY

BRANCH.HOLIDAY
This field defines the Business holiday table used by this company (or branch).

It can be different to the OFFCIAL.HOLIDAY table.

An example would be where the Official country working days

The branch working days could be Monday to Saturday (or even all 7 days) irrespective of Official public h

The CURRENT.DAY field on the DATES record for the company will indicate the type of business day.

NORMAL the branch is open on an official working day

RESTRICTED the branch is open on an official holiday, e.g. a weekend or public holiday

CLOSED the branch is closed i.e. the holiday table for the branch indicates a non working day, or the day c

It is possible to determine whether a VERSION can be run based on the value of the CURRENT.DAY, so tha
If the BRANCH.HOLIDAY is different to the OFFICIAL.HOLIDAY then the LOCAL.COUNTRY will be blank an

If they are the same then the first two characters of the OFFICIAL.HOLIDAY field will be used to populate t

Validation Rules:

Optional input, if no input is made it will default to the value of the OFFICIAL.HOLIDAY field

Must be a valid entry on the REGION table, i.e. a two character country code followed by 2 numeric chara

If only the 2 character country code is input then the field value will be appended with 00

OFFICIAL.HOLIDAY
Defines the Official business holiday table for the local country related to this company.

This field will be used to control the update of the LOCAL.COUNTRY field, which is now made no input.

Validation Rules:

2 character country code, or 2 character country code appended with 00

If only 2 characters are entered then

The last 2 characters must be 00

A value must be present in this field

he OFFICIAL.HOLIDAY or BRANCH.HOLIDAY.

f on some days none of the branches are open.

y date calculations made for business activities.

ult to the value of the BATCH.HOLIDAY field in the master company record

ode followed by 2 numeric characters

ppended with 00

is field must be the same as the BATCH.HOLIDAY field of the master company record

s) irrespective of Official public holidays.

e the type of business day.

ublic holiday

s a non working day, or the day corresponds to a value on the BRNACH.CLOSED field for the company

alue of the CURRENT.DAY, so that business activities can be restricted when a branch is open on an official holiday.
OCAL.COUNTRY will be blank and the BRANCH.HOLIDAY will be used to populate the LOCAL.REGION field.

AY field will be used to populate the LOCAL.COUNTRY field and the LOCAL.REGION.FIELD will be blank.

CIAL.HOLIDAY field

ode followed by 2 numeric characters

ppended with 00

this company.

which is now made no input.

MULTI COMPANY
IMPACT ON VERSIONS
internal account
Inter-Company Accounting
INTERCOMP.CO
This is set when intercompany entries are to be channeled thro

Fields LEAD.COMPNAY, ROUTING.COMPANY and ROUTING. MN

First precedence goes to ROUTING.COMPANY, if the same not s

If there is an intercompany entry between company A and com

In company A

Debit account in company A

Credit C from A intercompany account

In company C

Debit A from C intercompany account

Credit account in company C

This means that every company needs to keep intercompany a

Setting this field would generate the following entries if compa

In company A

Debit customer account

Credit B from A intercompany account

In company B

Debit A from B intercompany account

Credit C from B intercompany account

In company C

Debit B from C intercompany account

Credit customer account The advantage is fewer intercompany

es are to be channeled through a selected company. The main reason for setting this field is to reduce the number of intercompany accoun

MPANY and ROUTING. MNEMONIC are not set for Transaction company’s lead company then transactions routed through this company.

OMPANY, if the same not set company in this field used as a Routing Company 1.

tween company A and company C then the following entries will be generated.

ds to keep intercompany accounts to link to all other companies.

following entries if company B is set as the INTERCOMP.CO and a separate routing company not defined for company C.

age is fewer intercompany accounts, the disadvantage is more accounting entries

number of intercompany accounts required.

routed through this company.

or company C.
Financial Accounting and Reporting
Sharing Information Between Companies

The files are grouped according to purpose and some of these groups may be shared with other companies. The opti

T24 tables can be grouped into various types some of which can be shared between Lead companies. A description

Note: Before installation of the system, the above decisions must be reached with the bank. The files classifications

INT Installation Level

CUS Customer level

CST Customer tables

FIN Financial

FRP Financial reporting

FTD Financial table definitions

FTF Financial tables data

CCY Currency tables

NOS Nostro tables

n Between Companies

d according to purpose and some of these groups may be shared with other companies. The options are taken when setting up a company

ouped into various types some of which can be shared between Lead companies. A description of the various table types follows:

ation of the system, the above decisions must be reached with the bank. The files classifications can then be adjusted through FILE.CONTRO

There is only one copy of installation level tables in a T24 database so the actual table name does not include a
company mnemonic. Examples of INT level tables include COMPANY, USER, VERSION and ENQUIRY

The CUSTOMER and related tables, often include the customer number in the key. Examples include
CUSTOMER.DEFAULT and LIMIT. This type of table can be shared between lead companies.

Parameter tables related to customer examples include INDUSTRY and SECTOR, together with parameter tables
for limits, collateral and position management. This type of table can be shared between lead companies.

There always is one copy of a financial table per Lead Company. All branches linked to a Lead Company share
the same financial table. Examples include ACCOUNT, FUNDS.TRANSFER and TELLER
There is one copy of a financial table for every company in the system; examples include the COB job list tables
and REPGEN work files like RGP.TRANS.JOURNAL2
Financial parameter tables that do not contain data with amounts or rates linked to a particular local currency.
Examples include the GEN.CONDITION type tables and BASIC.INTEREST. This type of table can be shared
between lead companies.

Financial parameter tables that contain financial data, often contain local currency amounts. Examples include
GROUP.DEBIT.INT, GENERAL.CHARGE and TAX. This type of table can be shared between lead companies.

Tables containing currency related information examples include CURRENCY and PERIODIC.INTEREST. This type
of table can be shared between lead companies.
Tables related to NOSTRO accounts. Examples include AGENCY and NOSTRO.ACCOUNT. This type of table can
be shared between lead companies.
hen setting up a company record and cannot be changed.

ble types follows:

sted through FILE.CONTROL

Branches Working on Holidays

In a multi branch system, it is possible that not all branches follow the working practices of the Lead Company, for ex

It is possible to define three different holiday tables on the COMPANY application: -

OFFICIAL.HOLIDAY
The business holiday table for the local country

BRANCH.HOLIDAY
The business holiday table for this company

BATCH.HOLIDAY
The holiday table controls the days the COB processing occurs.
For example, it is possible to set the system up to run COB processing 365 days per year, with some branches open o
If a branch is open on an official holiday then it is possible to restrict at VERSION level what applications can be run.
tices of the Lead Company, for example the head office may not work at weekends whereas the branches do.

year, with some branches open on weekends for restricted business activities.
el what applications can be run.
COMPANY.GROUP

COMPANY.GROUP codes are used to identify the various operating companies, using the T24 system. The COMPANY

Thus for each of the T24 COMPANY records for the same operating company, the COMPANY.GROUP must be the sam

The format of the Company Code is:

CC GGG LLLL

Where:
CC - Is the Country Code
GGG - Is the Company Group Code
LLL - Is the Local Code

Note: Local code must be different for each location/ branch within one country even if the processing is run in diffe

The COMPANY.GROUP code thus forms the centre portion of the individual COMPANY records.
g the T24 system. The COMPANY.GROUP code is part of the 'T24 Company key and as such helps in identifying a particular operating compa

OMPANY.GROUP must be the same. Therefore, the same COMPANY.GROUP codes need to be created at each of the locations where the org

en if the processing is run in different environments.

ing a particular operating company of 'T24 Companies that have been set up for it. This helps in reports and so on. being grouped/combine

ch of the locations where the organisation is operating the T24 system.

d so on. being grouped/combined.
Examples of File Classification

The classification of the file can be found in the relevant FILE.CONTROL records. The following are some example cla

FIN Company classification:

The Account application is an example of a FIN file. INT - Installation

CUS - Customer
CST - Customer Table
CUS FIN - Financial
The Customer application is an example of a CUS file. FTD - Financial Table Descriptive
FTF - Financial Table Financial
CCY - Currency
CCY NOS - Nostro

The Currency application is an example of a CCY file.

CST

The Industry application is an example of a CST file.

For the parameter table levels there is a default company. For Customer Tables and for Financial Tables there is the o

The allowed applications are : CUSTOMER , ACCOUNT, SEC.ACC.MASTER,FATCA.CUSTOMER.SUPPLEMENTA

CUSTOMER file can be used for all the CONDITION. PRIORITY records.

ACCOUNT file can be used for ACCOUNT & STATEMENT records.

SEC.ACC.MASTER can be used for FX.MARGIN and all SC related CONDITION.PRIORITY records.

FATCA.CUSTOMER.SUPPLEMENTARY.INFO can be used for TAX related CONDITION.PRIORITY records.

e following are some example classifications.

e Descriptive

for Financial Tables there is the opportunity for file(s) to be linked to a different Company from the default. Depending on local conditions t

FATCA.CUSTOMER.SUPPLEMENTARY.INFO

ON.PRIORITY records.

NDITION.PRIORITY records.
Depending on local conditions these parameter tables may be held at Lead company level or shared between groups of Lead companies.
een groups of Lead companies.
Global Processing

Global Processing allows the COB processing in a Multi Company environment to be run independently at Lead Com

The global processing module also provides the following functionality:

Full transaction management in the end of day process

A resilient fault tolerant end of day process (the system cannot stop due to an error with a contract)
Use of online backups rather than traditional backup
Global processing functionality is restricted to lead companies, i.e. all branches linked to a Lead Company are pro
Ability to post accounting entries to companies that are offline from a company that is online
 run independently at Lead Company or Lead Company group level. If the Lead Companies in a T24 database are located in a variety of tim

ror with a contract)

nked to a Lead Company are processed together

hat is online
ase are located in a variety of time zones then the COB processing can take place at a convenient time for the relevant group, with the othe
he relevant group, with the other groups in the system online.
Transferring Account and Contracts