T24 Post Closing

TEMENOS EDUCATION CENTRE

Warning: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.
Copyright © 2010 Temenos Headquarters SA
Post Closing - Objectives

 Overview

 Creation of Database for Previous Period

 Creation of Back-dated accounting adjustment entries

 Updating Database for Previous Period

 Generation of Reports for Previous Period reflecting the adjustment

entries passed

 Closing of Prior period

Slide 2
Post Closing – Product Overview

Revised
Prior period
Financial Reports
Data Base
Historic Prior period
Transactions
affecting
Accounts and
Financial Post PL Heads
Data Base Closing through
FT / DC

Current period
Transactions
Financial
Data Base
Current

Current period Current period

Reports Reports

Slide 3
PC.PERIOD

 This is an installation level application used to specify the Companies

for which the previous periods’ database will be kept open

 The record will be processed during COB using

PC.CREATE.DATABASE batch program and database for the open
period will be created by copying necessary data from the current
accounting database

 Id will be equal to Today. If there are trailing holidays, Id will be equal

to the Period-end date updated in PERIOD.END Field of Company’s
DATES record

 Initially the value will be OPEN for PERIOD.STATUS Field

If the Periods’ database is to be closed for all Companies, it can be set
to CLOSED

Slide 4
PC.PERIOD

 Id of an operative Company to be specified in

COMPANY Field

 Status of the Company’s database for the

period set in the Id defined in COMP.STATUS
Field
 In case of a Multi-Book Environment,
COMP.STATUS Field can be set up only for
Lead Companies

 The path of the database to store the files

related to the financial period specified in the
Id is specified in DBASE.PATHNAME Field
 Not necessary to define a separate path for
each PC.PERIOD

Slide 5
Inputting Transactions for Prior Accounting Period

 Only Funds Transfer (FT) and Data Capture (DC) applications can be
used to input transactions, to affect prior accounting period(s)
 ACCOUNTING.DATE Field in FT and DC used to specify the prior period
accounting date

 Input and Authorise the FT/DC record with appropriate Accounting

Date and Value Dates
 Prior period accounting database in “Open” status, with period dates
greater than or equal to ACCOUNTING.DATE Field will be affected by
the transactions
 VALUE.DATE Field is used only for interest calculation purposes and
might be different from the ACCOUNTING.DATE Field

Slide 8
Inputting an FT Transaction with Accounting Date

 For inputting FT transactions with an

Accounting Date, in the related
FT.TXN.TYPE.CONDITION, Post Closing
should be allowed
 Update ALLOW.POST.CLOSE Field to Y
in FT.TXN.TYPE.CONDITION record for
Account transfer (Id: AC)

 Inputting a Funds Transfer transaction with

an Accounting Date
 In this example, the amount is transferred
to a PL Category from an Account with an
Accounting Date of 05th December 2009

Slide 9
Accounting Entries

 In the STMT.ENTRY, the following

fields will be updated for
transactions with an Accounting
Date

 ACCOUNTING.DATE
Specified in the transaction

 PC.PERIOD.END
Date(s) of the open PC.PERIOD
records greater than or equal to
ACCOUNTING.DATE, to which
the adjustment entry will
be applied

Slide 10
Accounting Entries

 In the CATEG.ENTRY, the following

fields will be updated for transactions
with an Accounting Date

 ACCOUNTING.DATE
Specified in the transaction

 PC.PERIOD.END
Date(s) of the open PC.PERIOD
records greater than or equal to
ACCOUNTING.DATE, to which the
adjustment entry will be applied

Slide 11
Inputting Data Capture Transactions with Accounting Date

 Data Capture Debit Entry to an Account & Credit Entry to PL Head with
ACCOUNTING.DATE
 Accounting Date is 05th December 2009 and Processing Date is 17th
December, 2009

Slide 12
Live Tables for Adjustment Entries

 The live table PC.STMT.ADJUSTMENT is updated with the Ids of

STMT.ENTRIES which have Accounting Dates

 Id is Account Id - Date (greater than or equal to Accounting Date) of the earliest

open prior period Database - STMT.ENTRY Id

 Data is STMT.ENTRY Id

 When no PC.PERIOD is open (with Date greater than or equal to Accounting

Date), Date will be updated to 99999999

 This table is used to update the prior accounting period database with
adjustments

Slide 19
Live Tables for Adjustment Entries

 The live table PC.CATEG.ADJUSTMENT is updated with the Ids of

CATEG.ENTRIES which have Accounting Dates

 Id is PL Category-Date (greater than or equal to Accounting Date) of the earliest

open prior period Database - CATEG.ENTRY Id

 Data is CATEG.ENTRY Id

 When no PC.PERIOD is open (with date greater than or equal to Accounting

Date), Date will be updated to 99999999

 This table is used to update the prior accounting period database with
adjustments

Slide 20
Updating Prior Period Database with Adjustment Entries

 Create a record in
PC.UPDATE.REQUEST for the Prior
period database, which needs to be
updated with the adjustment & Verify it
 Ensure that TSM in TSA.SERVICE is in
Start mode
 PC.UPDATE.REQUEST is a Service
defined in TSA.SERVICE to update the
open prior period accounting database
with accounting entries which have
accounting dates. Set
SERVICE.CONTROL Field to AUTO
 Start TSM from the ‘jsh’ prompt
At Jsh ..> START.TSM –DEBUG
 Start the required number of agents for the
service PC.UPDATE.REQUEST

Slide 21
Updating Prior Period Database with Adjustment Entries

 When the PC.UPDATE.REQUEST

service is run, the Field: PC.APPLIED is
updated to Y in STMT.ENTRY with
Accounting Date

 The entries with Accounting Date are

applied to all the open PC database with
date equal to or greater than the
Accounting Date

Slide 25
Updating Prior Period Database with Adjustment Entries

 When the PC.UPDATE.REQUEST

service is run, the Field PC.APPLIED is
updated to Y in CATEG.ENTRY with
Accounting Date

 The entries with Accounting Date are

applied to all the open PC database
with date equal to or greater than the
Accounting Date

Slide 26
Printing CRF Reports for a Prior Period

 Printing Financial reports for a prior

Accounting period to reflect the
accounting adjustments input through
transactions with Accounting dates

 To print CRF reports, verify

RE.STAT.REQUEST record with
PC.PERIOD.END Field equal to the
Date of a prior accounting period as
specified in PC.PERIOD application

Slide 27
Printing Consolidated CRF Reports for a Prior Period

 To consolidate CRF reports of multiple

Companies, verify the
RE.CONSOL.REQUEST record with the
field PC.PERIOD.END equal to the Date
of a prior accounting period as specified
in PC.PERIOD application

 COMPANY.CONSOL is used to specify

the Companies whose data need to be
consolidated, default reporting currency,
etc
 Its Id is specified in the field CONSOL.NO
of RE.CONSOL.REQUEST

Slide 28
Closing Prior Period Database

 Using PC.PERIOD, database for a previous period can be closed

Company-wise by setting COMP.STATUS Field to CLOSED
 Cannot close a Company, if there are pending adjustments for this period or
a previous period

 Using PC.PERIOD, database for a previous period for all Companies

can be closed by setting the PERIOD.STATUS Field to CLOSED
 Cannot close a period, if the previous ones remain open
 Cannot close a period, if there are pending adjustments for this period or a
previous period
 Once a period is closed, cannot change any field in PC.PERIOD

 If a period is closed, any adjustments posted to the period using FT or

DC transactions, will be ignored

Slide 29
Summary

 You have learnt about

 The Post Closing module, its functionalities and various related processes

 Creation of open prior accounting periods

 Inputting accounting adjustment transactions

 Updating the adjustment transactions to database of prior accounting

periods

 Generate financial reports for prior accounting periods

 Closing Prior Period Database

Slide 34
Thank You
TEMENOS EDUCATION CENTRE
Warning: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.
Copyright © 2010 Temenos Headquarters SA