T24 Accounting Set-Up - For Consolidation - R15

T24 Accounting Set-up – For Consolidation
Agenda
01 Learning Objectives
02 Consolidation
03 Consolidation of Assets and Liabilities
04 Consolidation of Profits and Losses
05 Consolidation Utilities
2
Learning Objectives
T24 Accounting Set-up > Learning Objectives
About Consolidation
Consolidation Parameters for Assets and Liabilities
Consolidation Parameters for Profits and Losses
3
Agenda
02 Consolidation
4
Consolidation – Basis for generation of the GL-Reports
T24 Accounting Set-up > Use of consolidation > Flow diagrams
Entries affecting STMT.ENTRY

Account balances
(Non contingent) Consolidation of
ASSETS &
LIABILITIES
REPORT CREATION
Entries affecting RE.CONSOL. HEADER
all other SPEC.ENTRY
Assets & Liabilities
LINE COLUMN
…………...
…………..…
Consolidation of
Entries affecting CATEG.ENTRY PROFITS & LOSSES
PL Heads
5
Consolidation - Overview
T24 Accounting Set-up > Use of consolidation > Flow diagrams
ACCOUNT
Files updating
MONEY.MARKET
STMT.ENTRY, RE.CONSOL.SPEC.ENTRY and
CATEG.ENTRY
FOREX
P/L KEY CREATION A/L KEY CREATION

(CONSOLIDATE.COND - PROFIT&LOSS) (CONSOLIDATE.COND - ASSET&LIAB) ETC
online online
PL.CONSOL.
CONSOL.UPDATE.
UPDATE.WORK
WORK
during COB during COB
CONSOLIDATE. Central Reporting Files CONSOLIDATE.

PRFT.LOSS ASST.LIAB
6
CONSOLIDATE.COND
T24 Accounting Set-up > consolidation > CONSOLIDATE.COND
 CONSOLIDATE.COND contains the criteria for consolidation of

accounting entries
 Separate selections can be made for Assets and Liabilities and

Profit & Loss
 Two records - ASSET&LIAB and PROFIT&LOSS
 Default rules, Company specific rules possible
7
Agenda
02 Use of Consolidation
8
Consolidation for Assets & Liabilities
T24 Accounting Set-up > A/L Consolidation
 4 fixed parameters and upto 12 User definable parameters
 Fixed parameters are Application, Currency market, Position type

and Currency
 User definable parameters can be chosen from a single value field

 General file (CUSTOMER)
• Industry, Sector, Nationality, Residence
 Local files (any contract / account file)
• Product category, Tenor, Dealing officer
9
CONSOLIDATE.COND and Reporting
 Consolidation is done with

reporting in mind
 Hence, as soon as
CONSOLIDATE.COND
default records are
authorised, field names for
selection in
RE.STAT.REP.LINE
application are
automatically finalised
 For Assets and Liability
as well as Profit and Loss
10
Consolidation for Assets & Liabilities
User definable parameters are defined in Associated multi value fields
Let’s take first a look on the option

Naming the definable parameter CUSTOMER
The parameter is named through NAME
Field
• Unique Mnemonic used for Display
• Can be any meaningful tag up to 12 2 Options are available
alpha numeric characters
• CUSTOMER: Criteria will
be fetched directly from
CUSTOMER file
• LOCAL: Criteria is not
Naming the File related to definable stored in CUSTOMER file.
parameter Then it has to be listed
The name of the file from which the each application and field
definable parameter is chosen can be from where the information
specified through FILE.NAME Field has to be fetched
11
Consolidation for Assets & Liabilities – Option CUSTOMER
Option CUSTOMER
Naming the Field to be chosen
 The name of the field is specified through FIELD.NAME. It has to be a valid
T24-internal field name
 Name of a Single-valued Field & Field length not greater than 10
Example: Looking for the T24-internal

field name of field “SECTOR” CUSTOMER file
Place the cursor on

the required field
The T24-internal
field name will be
displayed at the
bottom in brackets
12
Consolidation for Assets and Liabilities – Option CUSTOMER
13
 It is further possible to combine values of a choice

for CUSTOMER fields
 A single value can be accumulated
 A range of values can be accumulated
 Values not specified can be accumulated as
REST
 If REST is not specified, then missing values
keep their own value
• Sector 1000 will appear as 1000 in KEY,
while – eg. “AC.1.TR.USD.1001.1000”
• Sectors 1001 to 2000 will be grouped and
called as 2000 – eg.
“LD.3.TR.GBP.21051.2000”
• All Sectors greater then 2000 will be
grouped as REST in the Key – eg.
“MM.9.TR.JPY.21001.REST”
14
Any customer
who has a sector
which is greater
then 2000
will appear under
Consol Key
“REST”
15
 For CUSTOMER file, if a

particular Key variable
required only for specific
conditions
 Conditions can be chosen
through fields
CONSOL.ON.FILE to
CONSOL.END
Example 1
Sector to appear in KEY only if

resident of USA & then to be
grouped as 1000, 2000 and
REST as stipulated here
16
Example 2
Residence to appear in KEY only if Nationality is US or UK
17
Example 2
Residence to appear in KEY only if Nationality is US or UK
18
Consolidation for Assets and Liabilities – Option LOCAL
Option LOCAL:
Criteria is not stored in CUSTOMER file. Then it has to be listed each application and
field from where the information has to be fetched
Fields associated with MULTI.VALUE.NO Field to define

parameters for LOCAL variables
MULTI.VALUE.NO Field to contain the order of user defined

variable
LOCAL.FILE.NAME Field is used to specify the name of the File

holding information
Example: ACCOUNTS Application and ACCOUNT Local file name
Define Application-wise and only where needed
19
Option LOCAL:
In the lower section of the CONSOLIDATE.COND-record you specify the applications and
the fields from where the information for the criteria shall be fetched
For this the fields from MULTI VALUE NO down to

LOCAL FIELD NAME are used
ATTENTION: In field MULTI VALUE NO the

number of the related consolidation criteria must be
specified
In field APPLICATION the Application has to be

specified which shall be evaluated. The next slides
contain the allowed values
In field LOCAL FILE NAME you have to specify the

T24-internal name of the Application. They may be
checked in PGM.FILE
In field LOCAL FIELD NAME you have to specify
the T24-internal name of the required field within
the Application.
20
Allowed values in fields APPLICATION and LOCAL.FILE.NAME
Value in field APPLICATION Value in field

LOCAL.FILE.NAME
SECURITIES • SECURITY.MASTER
• SEC.ACC.MASTER
DX.TRANSACTION
DERIVATIVES SWAP
SWAP SL.LOANS
SLL.LOANS PRE.SYNDICATION.FILE
SLP.PRESYN FACILITY
SLF.FACILITY LETTER.OF.CREDIT
LETTER.OF.CREDIT SY.TRANSACTION
STRUCT.PRODUCTS BL.REGISTER
BILLS
Continued next slide
21
Allowed values in fields APPLICATION and LOCAL.FILE.NAME
Value in field APPLICATION Value in field

LOCAL.FILE.NAME
ACCOUNTS ACCOUNT
GROUP.ACCRUAL GROUP.ACCRUAL.BALANCES
FID.ORDER FD.FID.ORDER
FID.ORDER FD.FIDUCIARY
FID.PLACEMENT FOREX
FOREX FRA.DEAL
FRA ND.DEAL
NDF LIMIT
LIMITS LD.LOANS.AND.DEPOSITS
LOAN.DEPOSIT MD.DEAL
MISC.DEALS MD.DEAL MONEY.MARKET MM.MONEY.MARKET
PAYMENT.DUE PD.PAYMENT.DUE
POSITIONS RE.POSITION.BALANCE
22
Example
 Product category is defined as consolidation criteria
 Criteria can be named CATEGORY
 For LD application the field CATEGORY is fetched for this criteria
2
1
23
 Naming the Field used for consolidation

 LOCAL.FIELD.NAM Field is used to specify the Field from the
LOCAL.FILE.NAME to return consolidation KEY variable value
 Field names likely to be different for different Applications
 Can be any single valued field

 Local reference field indicated with suffix
 One variable may return different types of information for different
applications
24
 Possible to combine values of a variable from a LOCAL file
 Can be indicated Application wise
 A single value can be accumulated
 A range of values can be accumulated
 Values not specified can be accumulated as REST
 If REST is not specified, missing values keep their own value
25
 Combining values from two fields

 LOCAL.FIELD.NAM Field can pick values from two fields using a slash
 Example: VALUE.DATE/FIN.MAT.DATE
 Used when the initial time is to be calculated (ATTENTION: Not the
remaining run time)
 Two date fields must be entered
 T24 will calculate the difference between these dates as initial period
 Combination details entered in LOCAL.START and LCL.COMBINED
Fields
 Values must be in ascending order
 Last value must be REST
 Possible to capture the difference as 0 (Call) or number between 1 to
999
(Days notice) or as days (nD) or months (nM)
 They can then be suitably grouped and labeled Call, 7 days Notice,
3 months contract, Short term, Long term etc
26
Example 1: MM with notice period 1 day
27
Example 2: MM with run time 2 weeks
28
Exactly matched classifications for time bands
 EXACT.RANGE Field set to YES to consolidate exactly matched

initial period classifications with a suffix E
 Segregation of selections
 LCL.COMBINED Field is set to segregate selections as 7D (7days), 1M
(1 month), and REST, and EXACT.RANGE Field is set to YES
 Those with initial period of exactly 1 month will be consolidated as 1ME
 Those above 7 days but up to 1 month will be consolidated together as
1M
 If EXACT.RANGE Field not set, then all those above 7 days and up to and
including 1 month consolidated together as 1M only
29
30
Amount-wise classification in multi-currency environment
 LOCAL.FIELD.NAM Field can be used
 To report initial amount in any currency converted into a common

currency
 Format: n/m – names of first field an amount field and second a

currency field
 LOCAL.CCY Field - A valid currency code to convert amount to a

common currency
 Combination details entered in LOCAL.START and LCL.COMBINED

Fields
31
Example: MM with Principal Amount 155.500 USD
1 2
= 155.500 USD
32
Consolidation for Assets and Liabilities – Other features
Self balancing Contingent Entries
 A contingent can be one sided entry or passed as a set of self-balancing

entries
 A loan of USD 10,000 with value-date tomorrow
Dr FORWARDB USD 10,000 or
Dr FORWARDDB USD 10,000 and Cr FORWARDDBBL USD 10,000
 Option set for Forex contracts through FX.SELF.BAL Field
 For all other contracts through CONT.SELF.BAL Field

 If self balancing entries are to be raised, this field will be set to Y
33
 Linking Application Files to General File

 Fields KEY.APPLICATION to KEY.LOCAL. FIELD provide link from
the Application files to General file.
 Mandatory for each application. For example have a look at the following
 KEY.APPLICATION MONEY.MARKET
 KEY.GEN.FILE CUSTOMER
 KEY.LOCAL.FILE MM.MONEY.MARKET
 KEY.LOCAL.FIELD CUSTOMER.ID
 Currently, CUSTOMER is the only General file
 Normally the Model Bank-setup may be used
34
Revaluation of Contingents
 Contingents can be selectively revalued
 Values to be furnished application wise and within an application any

relevant contingent asset type against the Fields FWD.REV.APP and
FWD.REV.TYPE. For example
FWD.REV.APP MONEY.MARKET
FWD.REV.TYPE FORWARDDB
FWD.REV.APP LETTER.OF.CREDIT
FWD.REV.TYPE ADVICE
CONFIRM
 FWD.REV.APP Field
ALL to cover all applications
 When contingents are revalued, there would be no effect on P&L
35
Consolidation of Limits
 LIMIT.TO.TAKE Field can be Set to ADVISED, INTERNAL, ONLINE or

NONE
 ADVISED = Limit amount told to the customer
 INTERNAL = Limit amount sanctioned be the credit committee of the bank
 ONLINE = The limit amount which is actually available for use
 NONE = Non Consolidation of Limits
 Keys formed like LI.1.TR.USD…, LI.1.TR.GBP… etc if option other than

NONE is chosen
36
37
Position Accounting – consolidated entries for Assets and Liabilities
 Possible to raise consolidation entries for A&L Positions

 Field POSITION.ENTRY will be used for that.
 Possible Options:
Value in field POSITION.ENTRY Meaning
ACCOUNT Creation AL(Non Contingent),

ALFWD(Contingent),
FXSP(Contingent) and
FXFWD(Contingent) entries
SUMMARY CAL keys with Asset types

FORWARDPOS and LIVEPOS
generated by grouping all forward
positions together and live positions.
Movements will be booked for the
total difference between yesterday
and today’s positions.
NONE No Consolidation Entries or Keys for

that
38
Example Position Accounting Example in POSITION file:

Situation on the 25.01.2012
between CHF and USD
Field POSITION.ENTRY set to
SUMMARY
CAL key for the 25.01.2012 for CHF

One RE.CONSOL.SPEC.ENTRY for this
AL-position
39
Consolidation for Assets and Liabilities – CAL-Keys
 The Parameters set up in CONSOLIDATE.COND determine how the

consolidated Accounting records for Assets and Liabilities (CAL-keys) will
be built.
 Those records are stored in CONSOLIDATE.ASST.LIAB
System designed
Fixed selections
Application Ccy Market Pos Type Currency
User designed
Selections from CUSTOMER ACCOUNT MM SWAP FX LD LC MG Etc
CONSOLIDATE.
COND
Category Sector Residence Etc.
40
Consolidation for Assets and Liabilities – CAL-Keys
Example CAL-Key
Because of the fixed and the user-defined criteria a CAL-Key may

look like this
AC.1.TR.USD.1001.1001.GB…….1000
This means concretely:

USD Current Account balance of British residents engaged in
Sector 1001 and belonging to Industry 1000
41
Consolidation for Assets and Liabilities – CAL-Keys – Asset types
Example CAL-Key
 The amounts in the CAL-Keys are split by Asset types.
 Eg: Asset types held in the CAL-Key for an account:

 USD 62,945.51: Asset type “CREDIT“ (= Credit Balances)
 USD -35,009.59: Asset type “DEBIT” (= Debit Balances)
 USD -57.39: Asset type “51000” (= “Interest payable”)
 USD 21.28: Asset type “50000” (= “Interest receivable”)
42
Consolidation for Assets and Liabilities – CAL-Keys – Asset types
Example CAL-Key
43
Account DEBIT and CREDIT Asset Types
Change in Account balance sign
44
CAL Key Balances
 Within a CAL key, balances are held Asset type wise
 TYPE Field indicates Asset type
 BALANCE Field indicates Opening balance, if any
 DEBIT.MOVEMENT Field, debit movement of the day
 CREDIT.MOVEMENT Field, credit movement of the day
 For foreign currency balances, LOCAL.BALANCE, LOCAL.DEBIT.MVE,

LOCAL.CREDT.MVE Fields indicate respective local currency equivalents
 Closing balance is not indicated as a single figure

Shown maturity date wise using sub value Fields MAT.DATE and
SCHD.AMOUNT
45
CAL Key Balances
Account application
Keys will hold
Debit as well as
Credit balances
But under different
Asset types
46
CAL Key Balances
47
Contingent Asset Types – an Illustrative List
Balance Asset type Applications
Contingent FORWARDCR MM, SC, LD, FR

Principal FORWARDDB MM, SC, LD, FR, MG, SL
FXSPOTBUY FX
FXSPOTSELL FX
FXFWDBUY FX
FXFWDSELL FX
ISSUE LC
ADVICE LC
CONFIRM LC
CONTDB AC, MD
CONTCR AC, MD
OFFCR, OFFDB AC
NOTIONALCR SW
NOTIONALDB SW
LIVECMT LD, SL
LINE LI
DXFUTBUY DX
48
Non Contingent Asset Types – An Illustrative List
Non contingent CREDIT AC

Principal DEBIT AC
LIVECR MM, SC, LD
LIVEDB MM, SC, LD, MG, SL
OVERDUEDB PD, LD
NABDB PD, LD
OVERDUECO PD
NABPR PD
PAYRES LC
49
Accrued P & L Asset types – An Illustrative List
Interest accruals – 50000 / 50100 AC

Payable
PL Category codes as defined in
LMM.INSTALL.CONDS table LD, MM
FX.PARAMETERS FX
Interest accruals - 51000 / 51100 AC
Receivable
PL Category codes as defined in

LMM.INSTALL.CONDS LD, MM
FX.PARAMETERS FX
Charge accruals - PL Category codes as defined in
Payable LMM.CHARGE.CONDITIONS LD
Charge accruals - PL Category codes as defined in
Receivable BALANCE.REQUIREMENT AC
NUMBER.OF.DEBIT AC
NUMBER.OF.CREDIT AC
LMM.CHARGE.CONDITIONS LD
50
Quiz
Xxx?
1. A Bank wants to consolidate Accounts and contracts
based on Currency It should then set CONSOLIDATE.COND
to make choices from all the underlying applications
2. A consolidation key looks like

LD.1.TR.USD.21051.1001.6M… representing loan of
Category code 21051. This means that in
CONSOLIDATE.COND, the fifth choice is set as Category
code
3. If a Bank is having keys like
LD.1.TR.USD.21051.1001.6M…FOWARDDB and
LD.1.TR.USD.21051.1001.6M…FOWARDDBBL, it means it
has opted for self balancing contingent entries in
CONSOLIDATE.COND
4. A Bank wants to set duration as choice in

CONSOLIDATE.COND only for some contracts but not for
accounts. This is possible in T24
51
Group Work - 1
 What do the following KEYS stand for? Settings as per Model Bank
1. AC.1.TR.CHF.1001.1001.FR.....1000
2. FX.1.TR.GBP.20030.3001.JP.....3100
3. LD.1.TR.GBP.21051.2001.US.6M....2810
4. LD.1.TR.GBP.21003.3001.GB.1Y....4320
5. MM.1.TR.GBP.21031.3501.US.N....3100
52
Slide 52
Agenda
53
Consolidation for Profit and Loss
T24 Accounting Set-up > P/L Consolidation
 1 fixed parameter and upto 12 User definable parameters
 Fixed parameter is either PL or CP
 User definable parameters can be chosen from a single value field

 General files (CUSTOMER or CATEG.ENTRY)
• Industry, Sector, Nationality, Residence
 Local files (any contract / account file)
• Product category, Tenor, Dealing officer
 Choice for Local files can be made only if the same had been
chosen for Assets and Liability consolidation
54
Consolidation for Profits & Losses
User definable parameters are defined in Associated multi value fields
Let’s take first a look on the option

Naming the definable CUSTOMER or CATEG.ENTRY
parameter 2 Options are available
The parameter is named through
NAME Field CUSTOMER or
• Unique Mnemonic used for CATEG.ENTRY: Criteria will
Display be fetched directly from
• Can be any meaningful tag up to CUSTOMER- or
12 alpha numeric characters CATEG.ENTRY-file
LOCAL: Criteria is not
stored in CUSTOMER- or
Naming the File related to CATEG.ENTRY-file. Then it
has to be listed each
definable parameter
application and field from
The name of the file from which the
where the information has
definable parameter is chosen can be
to be fetched
specified through FILE.NAME Field
55
Consolidation for Profits & Losses – Option CUSTOMER or CATEG.ENTRY
Option CUSTOMER or CATEG.ENTRY

Naming the Field to be chosen
 The name of the field is specified through FIELD.NAME. It has to be a valid
T24-internal field name
 Name of a Single-valued Field & Field length not greater than 10
Example: Looking for the T24-internal field name of the field CATEG.
where the Profit-/Loss-Category in CATEG.ENTRY is stored ENTRY
file
Place the cursor on

the required field
The T24-internal
field name will be
displayed at the
bottom in brackets
56
Consolidation
of
Interest
received
57
 For CUSTOMER and

CATEG.ENTRY file, if
a particular Key
variable required only
for specific conditions
 Conditions can be
chosen through fields
CONSOL.ON.FILE to
CONSOL.END
Example
“PLDepartment to appear in KEY only if resident of USA”
 To be grouped as LOAN for Department officers between 1 to 100
 And as PYMT for those between 2001 and 2100.
 Other Department officer to appear individually
 This Customer would appear under KEY “LOAN”
58
Consolidation for Profits & Losses – Option LOCAL
 The LOCAL key components used for A/L record can be mapped into P&L
record
 Ensures Assets and Liabilities and Profit and Loss keys share same
Local file components
 FILE.NAME Field specified as LOCAL
 Mapping done for select applications in APPLICATION Field

 LOCAL.FILE.NAME Field
only AL allowed
 LOCAL.FIELD.NAM Field
Consolidation element name in CONSOLIDATE.COND for AL
59
60
 Like for A/L also for P/L splits can been carried out on
 For this map the Asset and Liability key into the Profit and Loss key
 Attention: The splits are the same as in A/L.
61
Consolidation for Profits & Losses – Other features
 Fields KEY.APPLICATION to KEY.LOCAL. FIELD provide link from

Application files to General files
 These details should be input for PROFIT.LOSS application, by multi

valuing fields once again
 KEY.APPLICATION PROFIT.LOSS
 GEN.FILE CUSTOMER and CATEG.ENTRY
 KEY.LOCAL.FILE CATEG.ENTRY
 KEY.LOCAL.FIELD PRODUCT.CATEGORY
 Currently, CUSTOMER and CATEG.ENTRY are the two General files for
consolidation of Profit and Loss
62
Consolidation for Profits & Losses – Other features
Self balancing Contingent Entries
 A contingent P&L entry can be one sided entry or passed as a set of self-
balancing entries
 A P&L entry for USD 10,000 with value-date tomorrow in a value-dated
system
Contingent credit entry for 10,000 with SYSTEM.ID=CP, consolidated
under CP…. Key
 or two entries, with an additional contingent debit entry for 10,000 with
SYSTEM.ID=CB, consolidated under a CB… key
 Self balancing entries raised by setting CONT.SELF.BAL Field to Y
63
Consolidation for Profit and Loss
 RE.CONSOL.PROFIT contains CPL key wise, currency wise, date wise Ids
of CATEG.ENTRY records
 Optional generation – Parameterise Fields UPDT.CONSOL.PROFIT,

CATEG.START and CATEG.END
 UPDT.CONSOL.PROFIT Blank or NONE options
 If the field is blank, range of PL Category codes for update of
RE.CONSOL.PROFIT defined in multi value Fields CATEG.START and
CATEG.END
 If they are also left blank, then produced for all PL Categories
64
Consolidation for Profits & Losses – CPL-Keys
 The Parameters set up in CONSOLIDATE.COND determine how the

consolidated Accounting records for Profits and Losses (CPL-keys) will be
built.
 Those records are stored in CONSOLIDATE.PRFT.LOSS
System designed PL or CP
Fixed selection Enriched with the underlying FX.POS.TYPE – for
example “TR” for “Trading Position”
User designed CUSTOMER CATEG.ENTRY AC FX LD LC MG Etc

Selections from
PL Category Residence Application selections as defined for AL
65
Example CPL-Key
Because of the fixed and the user-defined criteria a CPL may look
like this
PL.51001.21052.2001.55.SG.6M.......GB0010001
This means concretely:

Interest Income for SINGAPORE Customers who belong to
Sector 2001 and on the 6M Loan with Category 21052. The
responsible Department is 55
66
Example CPL-Key
Note that the each CPL key will have the balances by different
currency.
67
 Within a CPL-Key, balances are held Currency wise
 DATE.LAST.UPDATE Field: Last date of update of the CPL record

CPL records will be updated only whenever there is a movement in
the record or at month beginning
 CURRENCY Field indicates the Currency of Income / expenditure

originally booked
 BALANCE Field indicates the accumulated total from month beginning

till date prior to DATE.LAST.UPDATE as local currency equivalent
 CCY.BALANCE Field indicates the same but in currency in which

earned / incurred
68
CPL Key Balances
 DEBIT.MOVEMENT Field: Debit movement on DATE.LAST.UPDATE,

as local currency equivalent
 CCY.DEBIT.MVE Field indicates the same in currency in which earned /

incurred
 CREDIT.MOVEMENT Field: Credit movement on

DATE.LAST.UPDATE, as local currency equivalent
 CCY.CREDT.MVE Field indicates the same in currency in which

earned/ incurred
 BALANCE.YTD Field indicates the accumulated balance from start of

financial year up to the previous month end as local currency equivalent
 CCY.BALANCE.YTD Field indicates the same in currency in which

earned / incurred
69
CPL Key Balances
70
Slide 70
CP Key Consolidation
71
Slide 71
Quiz
Xxx?
1. If a Bank has opted for self balancing contingent entries in

CONSOLIDATE.COND, it will have CP as well as PL keys
2. A Bank can set one set of rules for consolidating CP keys

and another set of rules for consolidating PL keys
3. A Bank has not chosen sector for consolidating AL keys.

Hence, it cannot choose sector for consolidating PL keys
also
4. A Bank has chosen duration of Call, Notice, 1 month, 3

months and Rest for consolidating Money Market
application keys for Assets and Liabilities. It can now choose
the duration for PL Key consolidation as Call, Notice, 1
month, 6 months, 1 Year and Rest
72
Agenda
73
CAL and CPL Key Life
T24 Accounting Set up > Consolidation Utilities
 The keys always give a snapshot picture as at COB of the previous day
 New keys are generated automatically when there is a need
 CAL keys, once created are perpetual as long as there is Opening or

Closing balance
 CPL file is wiped out at every year-end

 Balance transferred to the internal account specified in
ACCOUNT.CLASS record with Id ‘PLCLOSE’
 Done in the Batch job PL.MOVE.TO.AL during year end closing
 Live file PL.YR.END.ENTRY holds details of individual movements from
CPL to this internal account
74
CAL Key and Static Changes
User designed
Selections from
CUSTOMER ACCOUNT MM SWAP FX LD Etc
Sector Residence Category Term /

tenor
AC.1.TR.USD.1000.
AC.1.TR.USD.6000.
.1200.US
.1200.US
.1100.GB
.1200.GB
British
USD Current Account balance of US residents
residents
British engaged
engaged
residents in
in Sector
in Sector
engaged 12001200
Sector is
is is
1100
USD Savings Account balance of US residents engaged in Sector 1200 is
75
CPL Key and Static Changes
User designed
Selections from
CUSTOMER CATEG.ENTRY ACCOUNT MM SWAP FX LD Etc
Sector Residence PL Product Term /

Category Category tenor
PL.50000.6000. 1100.GB..
Interest expense on Savings Account of British residents engaged in Sector 1100
PL.50000.6000. 1200.GB..
Interest expense on Savings Account of British residents engaged in Sector 1200
PL.50000.6000. 1200.US..
Interest expense on Savings Account of US residents engaged in Sector 1200

PL.50000.1000. 1200.US..
Interest expense on Current Account of US residents engaged in Sector 1200

76
KEY Balances and Account / Contract Balances
 Consolidated keys maintain balances grouped from several accounts and

several contracts
 Balance look up files maintain account-wise and contract-wise balances
 These balances are maintained independent of each other

 Account / Contract balance look-up files maintained on-line and during
COB by Application actions
 KEY balances updated during COB by accounting entries/Consolidation
work files CONSOL.UPDATE.WORK and
PL.CONSOL.UPDATE.WORK
 The end-of-day balances calculated from the balance look-up files
should match with the closing balances in the consolidation keys
 Details of accounts / contracts grouped under a particular Consol Key is

available in Consol lookup table RE.CONSOL.CONTRACT
77
Workshop - 1
 Look at the consol look up files. Make a note of the account and contract
numbers coming under the look up files
78
Workshop –Solution
79
Balance Look up Files
A/L KEY for Account A/L KEY for LD

Credit Balance USD 1,250 51001 USD 125
Debit Balance USD 835 FWDDB USD 23,450
50000 USD 13 LIVEDB USD 145,549
RE.CONSOL.CONTRACT
AC… RE.CONSOL.CONTRACT
Account No. 123567 LD…
Account No. 832689 Contract No. LD0333500023
Contract No. LD0512400128
EB.CONTRACT.BALANCES:
EB.CONTRACT.BALANCES :LD0333500023
123567
EB.CONTRACT.BALANCES:
EB.CONTRACT.BALANCES : LD0512400128
832689
80
Workshop - 2
 View the balances of contract Ids noted down in the previous workshop
through the respective balance look up files
81
Workshop – Solution
82
Other Useful Look up Files
 RE.CONSOL.PROFIT
 Contains list of CATEG.ENTRY records that are linked to each CPL key
for a given Currency and run date
 CATEG.ENT.ACTIVITY
 Contains list of CATEG.ENTRY records that are linked to each
Category for a given run date and Company and multi thread reference
 RE.CONSOL.SPEC.ENT.KEY
 Contains list of RE.CONSOL.SPEC.ENTRY records that are linked to
each CAL key for a given Asset type and run date
83
Batch for Regeneration of CRF Base
 Batch REGEN.CRF.xxx
 Separate Batches
application- wise, for A&L,
P&L, etc.
 Two jobs
RE.CLEAR with
appropriate DATA value to
clear the CRF keys
RE.CREATE.xxx to
regenerate the CRF keys
 Jobs should be made Adhoc
after running
 Great care must be taken
while using these jobs
84
Key Learning Points
In this course you have learnt
Use of Consolidation
Consolidation Parameters of Assets and Liabilities
Consolidation Parameters of Profits and Losses
Utilities of Consolidation
85
Thank You
NOTICE
These training materials are the copyrighted work of Temenos Headquarters SA and other companies in the
TEMENOS group of companies (The Copyright Owner). The training materials contain protected logos, graphics and
images. Use of the training materials is restricted solely for use by licensed end users, partners and employees.
Any un-licensed reproduction by any means, redistribution, editing, transformation, publishing, distribution, or public
demonstration of the training materials whether for commercial or personal gain is expressly prohibited by law, and
may result in severe civil and criminal penalties. Violators will be prosecuted to the maximum extent possible. Such
training materials shall not be represented, extracted into or included in part, or in whole, as part of any other training
documentation without the express permission of the Copyright Owner, which must given in writing by an authorised
agent of the Copyright Owner to be valid. Where such permission is given a clear and prominent notice must be
displayed on any and all documentation accrediting the Copyright Owner with having copyright over the
materials. End-user licenses will in no event contain permissions extending the use of these training materials to
third parties for commercial training purposes.
Without limiting the foregoing, copying or reproduction of the training materials in part or in whole to any other sever
or location for further reproduction or redistribution is expressly prohibited, unless such reproduction is expressly
licensed by the Copyright Owner.
Copyright © 2010 Temenos Headquarters SA

T24 Accounting Set-Up - For Consolidation - R15

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

T24 Accounting Set-Up - For Consolidation - R15

Uploaded by

Copyright:

Available Formats

T24 Accounting Set-up – For Consolidation

Consolidation Parameters for Assets and Liabilities

Consolidation Parameters for Profits and Losses

Entries affecting STMT.ENTRY

P/L KEY CREATION A/L KEY CREATION

during COB during COB

CONSOLIDATE. Central Reporting Files CONSOLIDATE.

 CONSOLIDATE.COND contains the criteria for consolidation of

 Separate selections can be made for Assets and Liabilities and

 Two records - ASSET&LIAB and PROFIT&LOSS

 Default rules, Company specific rules possible

 4 fixed parameters and upto 12 User definable parameters

 Fixed parameters are Application, Currency market, Position type

 User definable parameters can be chosen from a single value field

 Consolidation is done with

User definable parameters are defined in Associated multi value fields

Let’s take first a look on the option

Example: Looking for the T24-internal

Place the cursor on

 It is further possible to combine values of a choice

 For CUSTOMER file, if a

Sector to appear in KEY only if

T24 Accounting Set-up > A/L Consolidation

Fields associated with MULTI.VALUE.NO Field to define

MULTI.VALUE.NO Field to contain the order of user defined

LOCAL.FILE.NAME Field is used to specify the name of the File

Example: ACCOUNTS Application and ACCOUNT Local file name

Define Application-wise and only where needed

For this the fields from MULTI VALUE NO down to

ATTENTION: In field MULTI VALUE NO the

In field APPLICATION the Application has to be

In field LOCAL FILE NAME you have to specify the

Allowed values in fields APPLICATION and LOCAL.FILE.NAME

Value in field APPLICATION Value in field

Continued next slide

Allowed values in fields APPLICATION and LOCAL.FILE.NAME

Value in field APPLICATION Value in field

 Naming the Field used for consolidation

 Field names likely to be different for different Applications

 Can be any single valued field

 Possible to combine values of a variable from a LOCAL file

 Can be indicated Application wise

 A single value can be accumulated

 A range of values can be accumulated

 Values not specified can be accumulated as REST

 If REST is not specified, missing values keep their own value

 Combining values from two fields

Example 1: MM with notice period 1 day

Example 2: MM with run time 2 weeks

Exactly matched classifications for time bands

 EXACT.RANGE Field set to YES to consolidate exactly matched

Amount-wise classification in multi-currency environment

 LOCAL.FIELD.NAM Field can be used

 To report initial amount in any currency converted into a common

 Format: n/m – names of first field an amount field and second a

 LOCAL.CCY Field - A valid currency code to convert amount to a

 Combination details entered in LOCAL.START and LCL.COMBINED

Example: MM with Principal Amount 155.500 USD

Self balancing Contingent Entries

 A contingent can be one sided entry or passed as a set of self-balancing

 Option set for Forex contracts through FX.SELF.BAL Field

 For all other contracts through CONT.SELF.BAL Field

 Linking Application Files to General File