AA 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 pur pose, without the express written permission of TEMENOS Holdings NV. Copyright 2006 TEMENOS Holdings NV. All rights reserved.

Arrangement Activities  Arrangement Activities 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 Arrangemen Arrangements ts is accomplish accomplished ed 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 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. 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 t herefore servicing of an arrangement is exactly the same whether running online or during the close of business (i.e. single source).  Additionally,  Additional ly, certain Actions may require accounting. accounting. During product product definition, definition, event-based  Accounting Rules Rules are established established and linked linked to the relevant relevant Actions.

Activity Logging, Backdating, and Reversals Each Activity performed on an arrangement is effective dated and stored on the arrangement’s arrangement’ s Activity Log. T24 stores the sequence of activities, links to any financial financial   transactions (e.g. deposits, withdrawals, withdrawals, disbursements, repayments, etc.), and links to all accounting entries. The combination of an effective dated Activity Log and single-source processing processing allows for the servicing of activity reversals as well as backdated activities. activities. Upon reversal of an activity, T24 T 24 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 occurring as a result of the t he reversal. To process a backdated activity, T24 follows the same procedure used for reversed activities (i.e. reversal and replaying of subsequent activities. Arrangement Activities  Arrangement Activities Activities

Defining Activities  Activities are performed performed on either either the entire Arrangement Arrangement (i.e. New Arrangement) or or on a specific Property (i.e. Change Principal Interest). Since Properties are user-defined 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 f or servicing may differ between lines. An Activity is therefore an instance of an Activity Class.  Activity records are are created in T24 primarily primarily to allow allow users to enter enter language specific specific descriptions. The actions performed by an activity are determined at run-time by substituting the relevant Property names for the Property Class names.

 A c tiv tivi i ty Cla C las ss D efini efi nition tion Each Activity Class lists the Property Class Actions in the order in which they will be

 

processed. Additionally 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  Additional ly an Activity Class is is categorized by how it is triggered: triggered: User – User  –initiated initiated by a user (e.g. New Arrangement, Arrangement, Change Interest, etc.) Transaction – Transaction  –runs runs as a result of a T24 T 24 transaction (e.g. Disburse, Make Payment, Payment, etc.) Scheduled – Scheduled  –run run during close of business (e.g. Accrue Interest, Make Due, Age Bill, etc.)  Arrangement Activities Activities - Arrangement Arrangement Activities Page Arrangement Activities  Arrangement Activities Activities

Structure Figure 1 - Activity Class Attributes

 A c tiv tivii ty Ins ta tanc nce e There are three types of Activity records: Entire Arrangement – Arrangement – When  When a Product Line is installed, T24 creates records for the  Activities which which effect an entire arrangement arrangement (e.g. (e.g. Lending-New-Arrangement, Lending-New-Arrangement, Lending-Close-Arrangement). Property – Property  – When  When a Property is defined by the user, T24 builds any corresponding  Activity Class instances. instances. For example example if a Principal Principal Interest property is created, instances for all Interest Activity Classes will be created. User Defined – Defined – Users  Users can create Activity Class instance to segregate a single Activity Class (e.g. DISBURSE DISBURSE-TERM.AMOUNT) -TERM.AMOUNT) into multiple transaction-spe t ransaction-specific cific Activities (e.g. Disburse via ATM, Disburse via Teller, T eller, etc.).  Activities created by T24 can not be modified modified by the user. user. The user however 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 Activities - Arrangement Arrangement Activities Page Arrangement Activities  Arrangement Activities Activities

Processing Activities  Activities are initiated initiated directly by a user, during COB, or as a result result of a transaction (e.g. FT, TT, etc) on an Arrangement. Once initiated, T24 dynamically determines the appropriate  Actions by substituting substituting the appropriate appropriate Property names names (based upon the Product being being serviced) and then executing each Action in sequence.  An Activity has no business business logic logic (i.e. code) as all all of the business logic logic is contained 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.

 A r r ang ement A c tiv tiviiapplicatio ty The Arrangement Activity application n 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 Effective Date. Once the Arrangement Arrangement ID is is entered, the Activity Activity field will be populated with the valid activities for the correspond corresponding ing product. Once an Activity has been selected and any necessary user input completed, if there t here 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 T 24 transaction, details of the transaction and the activity amount are recorded on the Arrangement Activity record. record. In the case of a transaction that results in multiple activities (e.g. a repayment which is for f or more than the due amount), multiple records are created and the ID of the first f irst activity is stored as the linked activity.  Arrangement Activities Activities - Arrangement Arrangement Activities Page Arrangement Activities  Arrangement Activities Activities Figure 5 - Transaction initiated Arrangement Activity

Us er Input of an an A ctivi ctivitty Unlike other T24 applications an Arrangement does not have a single record through which a user inputs the arrangement values. values. A user must first select which Activity they wish to accomplish, accomplis h, 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 Activity in the top pane and and the Properties Properties in the bottom pane. 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 Activities - Arrangement Arrangement Activities Page Arrangement Activities  Arrangement Activities Activities

Activity Logging  An arrangement’s arrangement’s Arrangement Arrangement Activity records represent represent a full history history of the activities activities   processed, in their original sequence. Certain activities such as “accrue interest” and  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 any corresponding corresponding Arrangement Arrangement Property changes changes done against against the arrangement. When an Activity is processed, the Activity and the Arrangement Properties affected are updated in the arrangement’s Activity Log record.  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 Activities - Arrangement Arrangement Activities Page Arrangement Activities  Arrangement Activities Activities

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

 

 Arrangement Activities Activities - Arrangement Activities Page