Arrangement Activities

Arrangement Activities
This document describes a T24 AA Property Class and it is assumed that the reader has read and is
familiar with the concepts described in the T24 Arrangement Architecture Product Summary.

Overview
Servicing of T24 Arrangements is accomplished through Arrangement Activities. Activities
are business functions which are triggered either by a user, the close of business, or another
T24 application like Funds Transfer or Teller.
Examples of Arrangement Activities are:
 New Arrangement
 Change Interest
 Recalculate Payment Schedule
 Apply Payment

Unlike most other T24 applications in which the user enters data in a record and T24
determines the required actions, an Arrangement Activity is first explicitly selected and any
necessary input is restricted to the appropriate attributes.

Activities, Actions, and Accounting

Each Activity is comprised of one or more Actions which are the specific units of processing
performed by a Property Class (e.g. Issue Bill or Accrue Interest). Actions can only be run
via an Activity and therefore servicing of an arrangement is exactly the same whether
running online or during the close of business (i.e. single source).
Additionally, certain Actions may require accounting. During product definition, event-based
Accounting Rules are established and linked to the relevant Actions.

Activity Logging, Backdating, and Reversals

Each Activity performed on an arrangement is effective dated and stored on the
arrangement’s Activity Log. T24 stores the sequence of activities, links to any financial
transactions (e.g. deposits, withdrawals, disbursements, repayments, etc.), and links to all
accounting entries.
The combination of an effective dated Activity Log and single-source processing allows for
the servicing of activity reversals as well as backdated activities.
Upon reversal of an activity, T24 effectively reverses any subsequent activities and then
replays the arrangement moving forwards as if the reversed activity had not occurred. This
can result in new activities (e.g. overdue processing) occurring as a result of the reversal.
To process a backdated activity, T24 follows the same procedure used for reversed activities
(i.e. reversal and replaying of subsequent activities.

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV.

Copyright 2006 TEMENOS Holdings NV. All rights reserved.

Arrangement Activities
Arrangement Activities

Defining Activities
Activities are performed on either the entire Arrangement (i.e. New Arrangement) or on a
specific Property (i.e. Change Principal Interest). Since Properties are user-defined,
Temenos has specified the composition of each Activity as an Activity Class which targets
either a Property Class or the entire Arrangement.
Each Activity Class is defined as a series of Property Class Actions and is Product Line
specific as the actions used for servicing may differ between lines. An Activity is therefore an
instance of an Activity Class.

Activity records are created in T24 primarily to allow users to enter language specific
descriptions. The actions performed by an activity are determined at run-time by substituting
the relevant Property names for the Property Class names.

Activity Class Definition

Each Activity Class lists the Property Class Actions in the order in which they will be
processed. Additionally if a particular Property Class requires user input it will be flagged to
indicate this.
The key of the each AA Activity Class is comprised of a Product Line, Verb, and Property
Class:
 LENDING-NEW-ARRANGEMENT
 DEPOSITS-CHANGE-INTEREST
 LENDING-CALCULATE-PAYMENT.SCHEDULE
 DEPOSITS-ACCRUE-INTEREST

Additionally an Activity Class is categorized by how it is triggered:

 User –initiated by a user (e.g. New Arrangement, Change Interest, etc.)
 Transaction –runs as a result of a T24 transaction (e.g. Disburse, Make Payment,
etc.)
 Scheduled –run during close of business (e.g. Accrue Interest, Make Due, Age Bill,
etc.)

Arrangement Activities - Arrangement Activities Page

Arrangement Activities
Arrangement Activities
Structure

Figure 1 - Activity Class Attributes

Activity Instance
There are three types of Activity records:
 Entire Arrangement – When a Product Line is installed, T24 creates records for the
Activities which effect an entire arrangement (e.g. Lending-New-Arrangement,
Lending-Close-Arrangement).
 Property – When a Property is defined by the user, T24 builds any corresponding
Activity Class instances. For example if a Principal Interest property is created,
instances for all Interest Activity Classes will be created.
 User Defined – Users can create Activity Class instance to segregate a single Activity
Class (e.g. DISBURSE-TERM.AMOUNT) into multiple transaction-specific Activities
(e.g. Disburse via ATM, Disburse via Teller, etc.).

Activities created by T24 can not be modified by the user. The user however can update
and maintain their description fields.
The key of the each T24 maintained Activity is comprised of a Product Line, Verb, and
Property as shown below:
 LENDING-NEW-ARRANGEMENT
 DEPOSITS-CHANGE-PRINCIPAL.INTEREST
 LENDING-CALCULATE-REPAYMENT
 DEPOSITS-ACCRUE-CREDIT.INTEREST

Structure

Figure 2 - Activity Attributes

Arrangement Activities - Arrangement Activities Page

Arrangement Activities
Arrangement Activities

Processing Activities
Activities are initiated directly by a user, during COB, or as a result of a transaction (e.g. FT,
TT, etc) on an Arrangement. Once initiated, T24 dynamically determines the appropriate
Actions by substituting the appropriate Property names (based upon the Product being
serviced) and then executing each Action in sequence.
An Activity has no business logic (i.e. code) as all of the business logic is contained within
the Actions. Each Action determines whether it needs to perform any processing based
upon a context of the Activity and the Arrangement details. If no processing is necessary it
simply exits and the next Action is started.

Arrangement Activity
The Arrangement Activity application serves as both a mechanism to allow a user to initiate
an Activity and as a record of each Activity that has been processed against an
Arrangement.
For new arrangements the only activity available is ‘New Arrangement’. The user must enter
the Customer and Product desired. For financial products the currency is also required.

Figure 3 - Arrangement Activity Fields for 'New Arrangement''

For existing arrangements, the user or T24 must specify an Arrangement ID, the desired
Activity, and an Effective Date. Once the Arrangement ID is entered, the Activity field will be
populated with the valid activities for the corresponding product. Once an Activity has been
selected and any necessary user input completed, if there are any associated Activity
Charges, the charge fields will be updated accordingly.

Figure 4 - Arrangement Activity with Charge Fields

For activities initiated by a T24 transaction, details of the transaction and the activity amount
are recorded on the Arrangement Activity record. In the case of a transaction that results in
multiple activities (e.g. a repayment which is for more than the due amount), multiple records
are created and the ID of the first activity is stored as the linked activity.

Arrangement Activities - Arrangement Activities Page

Arrangement Activities
Arrangement Activities

Figure 5 - Transaction initiated Arrangement Activity

User Input of an Activity

Unlike other T24 applications an Arrangement does not have a single record through which a
user inputs the arrangement values. A user must first select which Activity they wish to
accomplish, T24 will display all of the Arrangement’s Properties and allow input into any
necessary ones.
This is accomplished through the use of a specific composite window which displays the
Arrangement Activity in the top pane and the Properties in the bottom pane. Initially the
bottom pane would be blank and based on the Arrangement and Activity selected, it will be
dynamically populated.

Figure 6 - Example of the Arrangement Activity Input Screen

Arrangement Activities - Arrangement Activities Page

Arrangement Activities
Arrangement Activities

Activity Logging
An arrangement’s Arrangement Activity records represent a full history of the activities
processed, in their original sequence. Certain activities such as “accrue interest” and
“amortise charge” will not result in stored records as these activities will frequently be
processed daily.
To allow reversals and back-valuations, it is essential to keep a log of the processed
Activities and any corresponding Arrangement Property changes done against the
arrangement. When an Activity is processed, the Activity and the Arrangement Properties
affected are updated in the arrangement’s Activity Log record.

Figure 7 - Activity Log Attributes

The details of each Activity are stored in the Activity Log Details application.

Figure 8 - Activity Log Details Attributes

Arrangement Activities - Arrangement Activities Page

Arrangement Activities
Arrangement Activities

Activity Property Classes

Arrangement Activities can also be affected by conditions defined in the following Activity
Property Classes:
 Activity Advices – sending messages through the T24 Delivery system
 Activity Charges – charging the customer for using an activity
 Activity Presentation – specific Property Class versions to be used when inputting an
activity
 Activity API – user defined routines to be processed pre- or post- action

Arrangement Activities - Arrangement Activities Page