Aa Deposit Final

Arrangement Architecture - DEPOSITS
CITP PHASE II – JULY’11
SRINIVASAN A
TAMILSELVI C
Introduction to ARRANGEMENT ARCHITECHTURE
 The AA module provides a flexible framework that allows a number of new T24
modules to be created.
 The application provides a business component based architecture for the
management of products.
 Through arrangement architecture, components of banking products are
defined.
 These components can be used across lines of business according to the
requirements whether deposit or lending, internet services
© 2011 Capgemini - All rights reserved 2

Arrangement
 Understanding between Bank and Client
 Client buys a product of the Bank
 Each Arrangement can have different characteristic if defined at product level

 Can change if product characteristic is changed

Features of the AA module
 Ability to build families of products.
 Ability to inherit properties from the product family structure.
 Ability to determine the properties that a product is comprised of.
 Control of default values to be applied for product arrangements.
 Full control of scope between product and arrangement conditions.
 Design/Proof/Publish lifecycle for product management.
 The product builder can be used to create and maintain existing application (Mortgage,
Account, Loans and Deposits and AZ) product parameters.

The Complete Picture of AA
E
Temenos C
Release PRODUCT LINE PROPERTY CLASS ACTIVITY CLASS
I
PRODUCT PROPERTY I
GROUP C
C
ACTIVITIES
User O
Defined DEFINED
PRODUCT N
PROPERTY D

PRODUCT CREATING FLOW
Step 2 Step 3
Step 1
ADMIN MENU
ADMIN MENU
ADMIN MENU
PRODUCT
BUILDER
PRODUCT BUILDER
PRODUCT BUILDER
PRODUCTS
PROPERTY PRODUCT
CLASSES & CONDITIONS CREATE NEW
PROPERTIES PRODUCT GROUP
Enter the property

CREATE NEW created under step1 and
PROPERTY(for provide the actions for AMEND THE
property class) corresponding property. PROPERTIES CREATED
TO THE PRODUCT
GROUP.(provide
mandate properties).
After creating the
new property it will STEP 4
appear under ACTIONS PERFORMED AFTER
properties Create a new product and
CREATING A PRODUCT
amend the property conditions
CANCEL.PROOF
at product level and declare
CLOSE arrangement link.
PROOF
PUBLISH
WITHDRAW

STAGES

PARAMETER FILES
 AA.PRODUCT.LINE – Defined by Temenos
 AA.PRODUCT.GROUP – User creates based on requirement
 AA.PRODUCT – User creates based on requirement
 AA.PROPERTY.CLASS – Defined by Temenos
 AA.PROPERTY – User creates a property and attaches it to property class
 AA.ACTIVITY.CLASS – Defined by Temenos
 AA.ACTIVITY – User creates a activity and attaches it to activity class
 AC.BALANCE.TYPE – Used for COB Processing
 AC.ALLOCATION.RULE – Used for COB Processing

PARAMETER FILES
 AA.PRODUCT.DESIGNER - This is the master table for designing any product which the financial
Institution may wish to introduce. This is the table where users link the desired Properties (from
AA.PROPERTY) to the appropriate conditions.
 AA.ARRANGEMENT.ACTIVITY - The Arrangement Activity application serves both as a
mechanism to allow a user to initiate an Activity and as a record of each Activity that has been
processed against the Arrangement.
 AA.ARRANGEMENT – The AA.ARRANGEMENT file records generic information of the
arrangement contract.

Product Line – AA.PRODUCT.LINE
 Released by Temenos. Temenos has released 6 product lines
• LENDING
• INTERNET SERVICES
• PROXY SERVICES
• ACCOUNTS
• DEPOSITS
• OTHER
 Product Group should belong to a Product Line

PRODUCT LINE – AA.PRODUCT.LINE
 Product lines are based on functionality of banking areas. e.g. lending, deposits
 Temenos has defined property classes and each product line is constructed with
the use of Property Classes according to the requirement

PRODUCT LINE – Defined by Temenos
The highlighted Property Class are mandatory for Deposits in Product Line

Product Group – AA.PRODUCT.GROUP
 This is the second level of classification
 Products having similar characteristic grouped together
 Each product group will have unique characteristic
 Each product under the product group can inherit the same characteristic or can have
additional characteristic.

PRODUCT GROUP – AA.PRODUCT.GROUP
 New properties are defined at the Product group level, however existing property
classes can also be used

PRODUCT – AA.PRODUCT
 The last level of classification.
 All instances (in AA terms – Arrangements) of a product will have the same basic
attributes
 Products contain properties and property specific conditions(corresponding property
class) as defined by user
 Once a product is proof-read and published it is available under product catalogue

Product –Property Conditions
Default Negotiable
 The field Default Negotiable in “AA.PRD.DES.XXX” file holds the value as
• Yes : If the value is set it as “Yes” then the user can indicate whether the field
can be negotiated at the Arrangement Level
• No : If the value is set it as “No”, then the field can be indicated as non
negotiable at the Arrangement Level

Product –Property Conditions
Arrangement Link
 Determines whether Conditions specified for each property should perform the following:
• Tracking
• Non Tracking
• Custom Tracking
 Tracking :
Any changes to product conditions will get reflected at the Arrangement level
 Non Tracking :
Any changes to product conditions will not get reflected at the Arrangement level
 Custom Tracking :
Similar to Tracking, but the user can input any fields at the Arrangement level
Remaining fields are tracked at the product property level

Property Class – AA.PROPERTY.CLASS
 Released by Temenos
 Property classes are the building blocks and pre-defined by TEMENOS
 An existing property class cannot be amended and further a new property
class cannot be created
 Each product line with set of Property Classes are supplied by TEMENOS
 Property classes within Product Lines can be optional or mandatory.
 Where the Product Line has a mandatory Property Class, the Product Group
must have a property of that class. So for example every Deposit Product
Group must have a CUSTOMER property, to represent the owner.

PROPERTY CLASS - LIST

Property – AA.PROPERTY
 Characteristic of the Product
 One Property is mandatory for the Product
 Derived from Property Class
 Property Classes define the fundamental building blocks, a more specific classification
is necessary to fully describe a product
 Any property if desired can be created corresponding to the class
 Some property classes have multiple properties
 Example interest, charges classes can have multiple properties. (eg Principal interest,
Penalty interest, New arrangement fees, Account closing fees)

PROPERTY CONDITIONS – AA.PRD.DES.XXXX
 Property conditions are used for defining required values of the properties in the
product. (However derived from corresponding property class)
 For example, the conditions for the INTEREST property class are defined in
AA.PRD.DES.INTEREST and the fields are all interest related
 Same way, each property class record is linked to an application AA.PRD.DES.XXXX,
where XXXX is the ID of the property class. Values or default records are defined
within these applications
 Conditions defined for the properties are defaulted in when an arrangement is entered,
however it is possible to effect /give new values at arrangement level.
 Property conditions can be changed with effective dating, if required.

Activity Class – AA.ACTIVITY.CLASS
 Activity Classes are defined by Temenos and cannot be changed by the user
 It defines a behavior of an activity that acts on properties
 For e.g.: Adjustment of Interest accrual will result in an “Action” on the “Interest”
(Property class) – the Activity class is “DEPOSITS-ADJUST-INTEREST”

AA.ACTIVITY.CLASS - List

Activity – AA.ACTIVITY
 Activities are “actions performed on a property from a particular Product line”.
 An activity is an operation that can be applied to Arrangements
E.g.: Disburse, Accrue Interest, etc
 Banks can create their own activities based on existing Activity Classes
 Arrangements can only be updated via Activity (both Online & COB)

AA.ACTIVITY - List

PRODUCT BUILDER
Highlighted are the uses of different menu under Product builder
This menu is used

for designing a
new PRODUCT

AA.PRODUCT.DESIGNER
 Product building is done through AA.PRODUCT.DESIGNER application
 So product design is building up the product with conditions for properties of the property
classes supplied for that particular product line
 Advantage is that once a condition has been defined, it can be re-used in other product
lines also
 Handling multiple currencies for the product

ARRANGEMENT ID FORMAT
 Unique identification number for the arrangement contract. The format of the ID is as
follows:
 Arrangement activity ID - AAACT1000801J511S2
 Arrangement ID - AA10008GXK9G
 Alternate arrangement ID used for FT,TT transactions) – 43931 - USD

ARRANGEMENT STATUS
ARR.STATUS
This field indicates the status of the Arrangement during the life cycle of the contract.
The status can be standard statuses like,
 UNAUTH - The arrangement has been input and not Authorized yet.
 AUTH - The arrangement has been Authorized and LIVE.
 AUTH-FWD (Forward) - At this stage the Arrangement is not active and will be active
on a future date.
 CURRENT - The arrangement has begun disbursement. Even if partial disbursement
happens, this field would hold the same value.

ARRANGEMENT STATUS
 MATURED - Arrangement contract has matured and ALL DUES on this arrangement has
been cleared.
 EXPIRED - Arrangement contract has gone past its final payment date. But it still has
some dues left unsettled. But no-more disbursement can happen after status has
reached MATURED or EXPIRED.
 REVERSED - The arrangement contract has been reversed.
 CANCELLED - Arrangement contract has been Cancelled(Only for Deposits)
 CLOSE - Arrangement contract has been Closed
 PENDING.CLOSURE - Arrangement contract is ready for closure.

ARRANGEMENT CREATION
 Transaction in T24 are termed as Arrangements
 Arrangements are created using Product Catalog
 AA.PRODUCT.CATALOG application is used to create Arrangements in T24
 User Menu> Retail Operations> Deposits> Deposit Arrangements – Product Catalog

ARRANGEMENT CREATION
 Select a product from product catalog as shown under

AA.ARRANGEMENT.ACTIVITY
 In the popup screen, input the required fields as shown under
 AA.ARRANGEMENT.ACTIVITY application is used to create arrangements in T24

Available activities in AA.ARRANGEMENT.ACTIVITY
 On validation, the system will popup an application titled
“AA.ARRANGEMENT.ACTIVITY” with list of available activities as shown under






TRANSACTION FILES
Applications linked with transaction files are:
 Funds Transfer
 Teller

Activities
 Arrangement Activities are termed as Activities/Events in T24
 Some of the Arrangement Activities are listed below
 AA Deposit – fund
 AA Pay – out

AA Deposit – Fund (FT)
 Use User Menu > Retail Operations > Deposits > Deposit-Arrangements > Arrangement
Activities (FT) > AA Deposit - Fund

Prerequisites
 Prerequisites for AA Deposit - Fund(FT)
 Arrangement ID
 Account Number
 Use this icon to view the delivery preview before committing the AA Deposit – Fund.

AA Pay – Out (FT)
 Use User Menu > Retail Operations > Deposits>Deposit-Arrangements > Arrangement Activities (FT) >
AA Deposit - Payout
 Prerequisites for AA Deposit - Payout(FT)
 Arrangement ID
 Account Number

AUTHORISE THE TRANSACTION(FT)

Click this icon to authorise the
transaction

AA Deposit – Fund (TT)
 Use User Menu > Retail Operations > Deposits > Deposit-Arrangements > Arrangement
Activities (TT) > AA Deposit - Fund

AA Pay – Out (TT)
 Prerequisites for AA Deposit - Payout(TT)
 Arrangement ID
 Account Number

AUTHORISE THE TRANSACTION(TT)

Click this icon to authorise the
transaction

ACCOUNTING
Tables involved in Accounting are:
 STMT.ENTRY - Account
 CATEG.ENTRY - Profit and Loss
 RE.CONSOL.SPEC.ENTRY - Special Entry

ACCOUNTING
STMT.ENTRY
 This is the internal file which contains details of all entries over Customer and Internal Accounts.
 Entries are generated in this file by every on-line and batch process which involves debiting or crediting
Accounts.
 This file is used by any process which needs details of entries over Accounts, e.g. Account Statements.
 Only the See, Print and List functions may be used in this Application.

STMT.ENTRY FOR FT1001200740

ACCOUNTING
CATEG.ENTRY
 This is the internal file which contains details of all Profit and Loss entries.
 Entries are generated in this file by every on-line and batch process which involves debiting or crediting
Profit and Loss.
 This file is used by any process which needs details of Profit and Loss entries.
 Only the See, Print and List functions may be used in this Application.

CATEG.ENTRY FOR FT1001200740

ACCOUNTING
RE.CONSOL.SPEC.ENTRY
 The RE.CONSOL.SPEC.ENTRY file is so named as it contains the entries used to update the balances
on the consolidation files. The entries are those that are not passed through the CATEG.ENTRY or
STMT.ENTRY files.
 This file contains details of movements to the Asset and Liability Consolidation file, which are not
covered by a STMT.ENTRY record. The layout of this file is similar to that of the STMT.ENTRY file

RE.CONSOL.SPEC.ENTRY FOR FT1001200740

AC.BALANCE.TYPE
 These balance types are for reporting purposes.
 We can create new balance type for each products.
 Cannot amend existing Balances types.

AC.ALLOCATION.RULE
 It defines accounting events for accounting processing where the event is used to identify and determine
the type of accounting entries to be raised and the content of these entries.

ENQUIRIES
 Arrangements is an enquiry screen which is used to view the list of following
arrangements
• Authorized : To View the authorized arrangements
• Unauthorized : To authorize the unauthorized arrangements
• Pending : To complete the Arrangements by providing additional activities
• New Arrangement Offers

ENQUIRIES
Enquiries used to view the Arrangements can be accessed using

 User Menu > Retail Operations > Deposits > Deposit Arrangements –
Deposit Arrangement as shown under

AUTHORISED Arrangements
The list of authorized Arrangements are viewed
Click on the respective tabs to

view the list of Arrangements.

By clicking on
this icon user
can view the
Arrangement.


Arrangement - Bills
By clicking on this
icon user can view
the Arrangement
Bills.

Arrangement – Delivery Messages
By clicking on this
icon user can view
the Arrangement
Delivery Message.

Arrangement – Delivery Messages

Arrangements – Payment Schedule
By clicking on this
icon user can view
the Arrangement
Payment
Schedule.

UNAUTHORIZED Arrangements
By clicking on this
icon user can view
the arrangement.
By clicking on this
icon user can
Authorize the
Arrangement.

PENDING - Arrangements
By clicking on this
icon user can view
the arrangement.

REPORTS
Reports can be viewed using
 User Menu > Retail Operations > Deposits > Deposit Arrangements – Deposit
Arrangement as shown under
This enquiry is used to view the

report for an arrangement.

REPORTS
Required Arrangement ID is given and click the find option to view the report
We should provide
arrangement ID the
mandatory field .

ARRANGEMENT REPORT

Life Cycle of a PRODUCT
CREATION OF NEW PROPERTY:

CONDITIONS FOR PROPERTY

SYSTEM GENERATED ACTIVITY

PRODUCT GROUP CREATION

PRODUCT CREATION

PROOF THE PRODUCT

PUBLISH THE PRODUCT

PRODUCT CATALOG

PRODUCT IN PRODUCT CATALOG

Flow Diagram

www.capgemini.com/financialservices

Aa Deposit Final

Uploaded by

Copyright:

Available Formats

Aa Deposit Final

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

Aa Deposit Final

Uploaded by

Copyright:

Available Formats

Arrangement Architecture - DEPOSITS

CITP PHASE II – JULY’11

© 2011 Capgemini - All rights reserved 2

 Understanding between Bank and Client

 Client buys a product of the Bank

 Each Arrangement can have different characteristic if defined at product level

© 2011 Capgemini - All rights reserved 3

 Ability to build families of products.

 Ability to inherit properties from the product family structure.

 Ability to determine the properties that a product is comprised of.

 Control of default values to be applied for product arrangements.

 Full control of scope between product and arrangement conditions.

 Design/Proof/Publish lifecycle for product management.

Account, Loans and Deposits and AZ) product parameters.

© 2011 Capgemini - All rights reserved 4

© 2011 Capgemini - All rights reserved 5

Enter the property

© 2010 Capgemini - All rights reserved 6

© 2011 Capgemini - All rights reserved 7

 AA.PRODUCT.LINE – Defined by Temenos

 AA.PRODUCT.GROUP – User creates based on requirement

 AA.PRODUCT – User creates based on requirement

 AA.PROPERTY.CLASS – Defined by Temenos

 AA.PROPERTY – User creates a property and attaches it to property class

 AA.ACTIVITY.CLASS – Defined by Temenos

 AA.ACTIVITY – User creates a activity and attaches it to activity class

 AC.BALANCE.TYPE – Used for COB Processing

 AC.ALLOCATION.RULE – Used for COB Processing

© 2011 Capgemini - All rights reserved 8

AA.PROPERTY) to the appropriate conditions.

 AA.ARRANGEMENT.ACTIVITY - The Arrangement Activity application serves both as a

processed against the Arrangement.

 AA.ARRANGEMENT – The AA.ARRANGEMENT file records generic information of the

© 2010 Capgemini - All rights reserved 9

 Released by Temenos. Temenos has released 6 product lines

 Product Group should belong to a Product Line

© 2011 Capgemini - All rights reserved 10

the use of Property Classes according to the requirement

© 2011 Capgemini - All rights reserved 11

© 2011 Capgemini - All rights reserved 12

 This is the second level of classification

 Products having similar characteristic grouped together

 Each product group will have unique characteristic

© 2011 Capgemini - All rights reserved 13

classes can also be used

© 2011 Capgemini - All rights reserved 14

 The last level of classification.

© 2011 Capgemini - All rights reserved 15

 The field Default Negotiable in “AA.PRD.DES.XXX” file holds the value as

can be negotiated at the Arrangement Level

negotiable at the Arrangement Level

© 2011 Capgemini - All rights reserved 16

Remaining fields are tracked at the product property level

© 2011 Capgemini - All rights reserved 17

 Property classes are the building blocks and pre-defined by TEMENOS

 An existing property class cannot be amended and further a new property

class cannot be created

 Property classes within Product Lines can be optional or mandatory.

Group must have a CUSTOMER property, to represent the owner.