T3TAAD - Arrangement Architecture - Deposits - R11.1

T3TAAD – Arrangement Architecture
- Deposits
TEMENOS EDUCATION CENTRE
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
Arrangement Architecture - Deposits - Objectives
 Introducing participants to Deposits Product Line and Property Classes
 Learning to set parameter tables, create Property and Product

conditions for Deposits Product Line
 Learning to create Deposits Product Group and Product, proof and

publish the product
 Learning about Deposits activities, Simulation
 Learning use of enquiries relevant to this module

AA Deposit Arrangement – Product overview
Constant Fixed
Periodic Floating
Repayment Linear
Periodic
Mixed
Actual
Arrangement
Level
Band
AA
Deposits Bullet
Repayment
Repayment
Schedule
AA Deposits – Product overview
Arrangement
Conditions
Arrangement
Negotiable
Deposit
Non Account
Deposit Negotiable
Product
Conditions
Bills for
payment
Tracking
Fund
Cancel
Deposit
Non Tracking Period
Account
Cancel /
Cooling
Pending
Off Period
closure
Closure on
Maturity / Closure
Earlier
AA Dependencies
 AA makes use of
 CUSTOMER
 ACCOUNT
 Core dependencies
 Delivery
 Accounting
 AA also uses other Static tables

AA Dependencies – Interest related
BASIC.RATE.TEXT
Floating interest
BASIC.INTEREST
AA Dependencies – Interest Related
Periodic interest
Bid rate is used

for AA Deposits
Generated daily
AA Dependencies - Currency related
COUNTRY REGION
HOLIDAY
CURRENCY.PARAM
CURRENCY CURRENCY.MARKET
Possible to indicate Countries and Regions in BUS.DAY.CENTRES Field in

Account Product Condition. Accordingly, while inputting an Arrangement,
holidays for those countries and regions will be checked and suitable
overrides generated
Currency is used in CURRENCY Field in AA.PRODUCT.DESIGNER Table
AA Dependencies – Currency related
 Different Interest day basis for calculation of interest possible

depending on methods followed for calculating number of days in an
interest period and days in a year
Key Days/Denominator
A 360/360
 A 360 / 360
A1 360/360
30 days in each month
A2 360/360
360 days in an year
B 366/360
 A1 360 / 360
C 366/366
Additional interest of February
D 360/366
calculated on last day
E 366/365
 A2 360 / 360
F 360/365
Additional interest earned of February
H 30/356
calculated on penultimate day
F1 360/365
F2 360/365
S Special
Application specific Parameters
AA - Tables used for building components
 Tables used for building re-usable components :
 AA.PROPERTY.CLASS
 AA.PROPERTY
 AA.PERIODIC.ATTRIBUTE.CLASS
 AA.PERIODIC.ATTRIBUTE
 AA.ACTIVITY.CLASS
 AA.ACTIVITY
 AA.PRD.DES.<PROPERTY.CLASS>
 AA.SOURCE.CALC.TYPE
 AA.PROPERTY.CLASS.ACTION
AA - Tables used for building components
 Released by Temenos:
AA.PROPERTY.CLASS
AA.PERIODIC.ATTRIBUTE.CLASS
AA.PROPERTY.CLASS.ACTION
AA.ACTIVITY.CLASS
 Tables set up during implementation:

AA.PROPERTY
AA.PRD.DES.<PROPERTY.CLASS>
AA.PERIODIC.ATTRIBUTE
AA.SOURCE.CALC.TYPE
These could be used across several products
AA.PROPERTY.CLASS
 Released by TEMENOS to define Actions and Attributes for any

underlying Property and Product condition
Type
Attributes controlled by TYPE Field Property
Class
CCY, OPT.CCY, DATED, MULTIPLE, MERGE,
FORWARD.DATED, TRACKING, NON.TRACKING ,
Product Line Balance
TRACKING.ONLY, ARRANGEMENT, TRIGGER
Prefix
ACCOUNTS, DEPOSITS,
INTERNET.SERVICES, LENDING,
PROXY.SERVICES, SAVINGS, OTHER
Pre-fixes for Balance types controlled
by BALANCE.PREFIX Field
CUR, ACC, DUE, AGE, EXP,

UND, PAY, UNC, TOT
AA.PROPERTY
 Property is a named type / instance of a Property Class

 Property is attached to Product Group from where it is derived in a Product
 Multiple properties of the same Property Class can be used in a Product, if
so allowed in the Property Class
Property
Class
Details defined at Product level cannot be
viewed or amended at Arrangement Level – PRODUCT
e.g ACCOUNTING Rules ONLY
Property
Property can suspend income. Applicable SUSPEND

only for INTEREST and CHARGE properties Property
Type
Property can suspend overdue incomes SUSPEND

Option possible only if SUSPEND also opted OVERDUES NULL
AA.PRD.DES.<Property Class>
 To be defined for every Property class, by associating Id of the

respective Property class
 AA.PRD.DES.TERM.AMOUNT, AA.PRD.DES.ACCOUNT
 Possible to create different Product Conditions for a Property Class

 Also possible to create different dated records for Product Condition
 Fields of a Product condition represent attributes of the associated

Property Class
Product Product
condition for Cancel condition for
Category
Term Amount Period Account
Posting
Amount Term Restrict Currency
AA.PRD.DES.<Property Class>
 Product conditions have to be Date specific if Property class is set so
 Can be currency specific if the corresponding Property Class allows it

 For product allowing multi currencies, product conditions for each of the
currencies must be defined
 Currency can be optional - e.g. Charge Product condition
 Currency and Effective Date form part of Product condition Id

 FIXED.RATE-USD-20100101; FIXED.INTEREST-GBP-20100101
 Possible to set conditions with future value date also
Attributes controlled by TYPE

Field Type Property
Class
CCY, OPT.CCY, DATED
Negotiation rules – Default Negotiable
 DEFAULT.NEGOTIABLE
 Mandatory Field
 Options: Yes and No
 Defines whether all attributes (Fields) of the Property Class can be
Negotiated or not
 Attribute level negotiation rules will always override this setting
 DEFAULT.ATTR.OPTION
 Optional Field
 Option to reset arrangement conditions from the product during rollover,
reset and change product activities
Option “RESETTING “ - conditions will be reset from Product
Option “NON-RESETTING” – conditions will be maintained from
Arrangement level
Negotiation rules –Negotiation rules
FOR ALL
DEFAULT.NEGOTIABLE ATTRIBUTES
NR.ATTRIBUTE NR.OPTIONS NR.TYPE NR.VALUE NR.MESSAGE
EB.
Negotiable COMPARISON.
Attribute of OVERRIDE
Non Negotiable TYPE Value for
Property class
Override comparison
(Fields of ERROR
Fix Value Equal, Like,
Arrangement)
Mandatory Range ….
Usual term : 5 years. Can be negotiated,

but only between 3 & 10 years
 This application holds information on actions performed in each

PROPERTY CLASS
 The information covers:

 Actions for each PROPERTY CLASS
 Accounting entry generated or not for the action
 Product Line
Deposits Property Classes, Properties
and Product Conditions
AA Deposits Property Classes - Overview
Term Amount Interest Charge Payment Rules
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting
Activity Activity Activity Periodic

Presentation Mapping Charges charges
CUSTOMER Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting

Customer - Property Class
 Customer Property class is mandatory

 Customer Property cannot be set as Tracking and it is Dated
Property
Type
Class
CUSTOMER
Attributes controlled by TYPE Field
DATED, NON.TRACKING
Balance
Prefix
Balance Prefix - Null

Customer – Product Condition
 Product conditions can be set regarding Owner, Primary Owner, Other

Party, Role and Notes
 Typically set as Negotiable at Arrangement level
 Primary owner in Arrangement used for Accounting, Reporting and Limit
 Other owners can be added at arrangement level
 Other parties (Guarantor, Co-signatory etc ) associated to an Agreement, to
be defined in AA.PARTY.ROLE
Owner1
Owner
Primary Owner
Owner 2
Other Party
Arrangement Other Party

Other Party
Customer – Arrangement features
 Customer entered into New Arrangement Activity

 This customer becomes the Primary Owner
 Must be a valid record in CUSTOMER application
 Primary owner automatically defaulted in the list of other owners
 User can add other owners manually
 Primary owner can be changed:

 Through update Customer activity
 Can be replaced with any valid T24 Customer
 Limit sanctioned to Primary owner alone can be used in Arrangement

 When primary owner is changed, limit reference checked, validated
Workshop - 1 CUSTOMER Settings
 Use Admin Menu > Product Builder > Product Conditions >
CUSTOMER
 Create a new Product Condition for which all attributes must be negotiable
at Arrangement level without any restriction
Workshop – 1 Solution
Account Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting

Account - Property Class
 ACCOUNT Property Class is Dated

 CUR, DUE, AGE, UNC, UND, EXP and PAY are the allowed Balance
Prefix
Property
Types Class
Attributes
ACCOUNT
DATED
Balance
Pre-fixes for Balance types controlled by Prefix
BALANCE.PREFIX Field
DEPOSITS – CUR, DUE, AGE, UNC, UND, EXP, PAY

Account – Product Condition
 Category
 Accounts use Customer type of Account Category codes
 Range 1000 to 9999
 Must be Non-contingent, avoid ranges meant for Nostro, Vostro
 Usually set as Non-Negotiable
 Posting Restrict
 Pre defined Posting restrictions used
 Debits or Credits or all transactions could be set to attract overrides
 Account Title, Short Title and Mnemonic

 Account Title for descriptive details
 Short title used for enrichment
 Mnemonic is used as alternate Id
 Currency
 Currency of Arrangement
 Defaulted from Currency of New Arrangement Activity
 Cannot be changed after authorisation of arrangement
 Base Date Type

 Option to determine calculation start date
Agreement - will start calculations from date of arrangement
Start - Will start from First or initial deposit date
 Securities valuation enquiry

 Portfolio number at arrangement level enables Securities valuation enquiry
 Stores the identification number of SEC.ACC.MASTER
 Bus Day Centres

 Holiday table of country / region to determine non-working days
 Date Convention
 Schedule for non-working days
Forward; Backward; Forward Same Month; Calendar
 Date Adjustment
 Value - All schedule events calculated on VALUE Date of Arrangement
 Period - Every schedule event calculated on previous schedule date
 Not applicable when Date Convention is Calendar
Account – Other features
 Account is required for all financial Arrangements

 Holds the Principal balance of the Arrangement
 Allows changes to the following Account attributes:

 Account Title
 Short Title
 Posting Restriction
 Mnemonic
Workshop – 2 – ACCOUNT settings
 Use Admin Menu > Product Builder > Product Conditions > ACCOUNT
 Create a new Product Condition
 Set the following rules:
Use Category Code 6701
Set Base Date Type to AGREEMENT
Fill in ACCOUNT.TITLE and SHORT.TITLE Fields with title names you
desire
CATEGORY must be NON-NEGOTIABLE
All other attributes, by default are Negotiable
Workshop - 2 Solution
Officers Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting

Officers - Property Class
 Property for Officers can be set as Tracking
 Update Action possible. Values in fields can be updated at

Arrangement level
 Will not generate Accounting entry
Property
Attributes
Types Class
DATED, TRACKING OFFICERS
Officers – Product Condition
 Primary Officer
Main officer responsible for the Product or Arrangement
 Other Officers
Other officers have specified role
Both of above must be a valid Officer in DEPT.ACCT.OFFICER file
 Roles for Other Officers

A Role for each officer can be defined
Must be a valid role defined in AA.OFFICER.ROLE Virtual Table
 Notes for Other Officers
 Default value is Account Officer defined in CUSTOMER record

Workshop – 3 – OFFICERS settings
 Use Admin Menu > Product Builder > Product Conditions > OFFICERS
 Set the following rules :
For Other Officer Use codes “20 “ and “27” and role as “Application”
and “Approval” respectively
 Set DEFAULT.NEGOTIABLE to Yes
Workshop - 3 Solution
Term Amount Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting

Term Amount - Property Class
Property Class
 Represents both commitment amount and the Term
TERM.AMOUNT
 Term amount is currency specific

Type
Balance
Attributes Prefix
CCY, DATED,
NON.TRACKING
Pre-fixes for Balance types controlled
by BALANCE.PREFIX Field
TOT
Term Amount – Product Condition
 Committed Amount
 Amount of deposit for the term
 Term
 Period of time by which the amount must be repaid to Customer
 Maturity Date
 Date on which term ends
 Calculated from Agreement Date and Repayment Term
 Cancel Period
 If committed deposit amount is not paid by the customer, system triggers
cancellation of deposit after this period
 Notification of Pending Cancellation

 Pre-advice by a specified number of days in advance
 Amount on Maturity
 On Maturity of arrangement, to keep remaining amount as Due or
Outstanding
 Pre-closure of Deposit within a time frame - Cooling Off Period

 Without any charge to Customer
 No Interest paid to Customer
 Cooling Period attribute

 Defines the period within which a customer can withdraw or pre-close the
arrangement
 Pre-closure of Deposit after the cooling off period

 Charge can be collected through periodic attributes and Activity Restriction
 Interest payment made during the Cooling Off Period

 Schedules configured and processed for Interest payment
 No reversal of Pay balances during redemption calculation
 Override to notify the user if activity scheduled during cooling period

 At arrangement level
 Also at funds transfer stage
 Cooling Period for rollovers

 Same principle as for regular deposits
 Base date Type to be set as Agreement in Account property
Term Amount – Call Deposit
 Some deposits may be considered as call products
 Term and Maturity Date attributes are optional at arrangement capture

level and in the related product condition
 Product where Term and Maturity date are not specified in Term
amount property is a call product
 For a Call product, Change Product property should not be configured
 If Change Product Property is configured with a value specified in

either Change Period or Change Date, it is considered Fixed Term
Term Amount – Call Deposit CRF Reporting
 CONSOLIDATE.COND will refer to REPORT.END.DATE in

AA.ACCOUNT.DETAILS instead of MATURITY.DATE for contract
maturity reports
 CRF reporting handles contracts with:

 Specified maturity dates
 No maturity date (Call)
 Specified renewal dates
 REPORT.END.DATE Field in AA.ACCOUNT.DETAILS is updated

thus:
 The next renewal date if it precedes the maturity date or
 The maturity date if there is no renewal scheduled before the maturity date
 NULL if it is a call contract and there is no renewal scheduled
Term Amount – Other features
 Funding of Deposit not automatic
 Cannot be run directly from the Arrangement
 Transfer funds from a specified account to a Deposits Arrangement
 APPLYPAYMENT activity for Partial repayment acceptable, if set so
 Subject to Expected Balance and Activity Restriction, if any
 Payments received in excess of Expected Balance held in UNC

Workshop – 4 – TERM DEPOSIT settings
TERM.AMOUNT
 Set default amount to 40,000 which can be changed to a minimum of
20,000, but not less and to a maximum of 200,000 and above with overrides
 Default term is 3 years which is negotiable between 1 and 5 years
 Term below 1 year can be allowed but beyond 5 years not to be allowed
 If the total deposit amount is not paid by customer within 5 days of opening,
the deposit arrangement should be cancelled
 Set DEFAULT.NEGOTIABLE to Yes
 Commit the record
Workshop – 5 – CALL DEPOSIT settings
TERM.AMOUNT
 Amount and Term attributes to be left blank
 Term ,Maturity Date and Cancel Period attributes to be made Negotiable
 Amount can be permitted up to 500,000, not above that
 Customer can withdraw / pre-close the arrangement within 5 days of
opening the deposit
 Set DEFAULT.NEGOTIABLE to No
Quiz 1 – Choose the correct Answer
1. The Primary Customer of an Arrangement can be changed only with a

Joint Owner
a) True
b) False
2. AA Account can use any Account Category Code

a) True
b) False
3. Term Amount Property Class holds two Amount attributes

a) True
b) False
4. The Roles of Other Parties (CUSTOMER) are defined in Virtual Table

AA.CUSTOMER
a) True
b) False
Activity Mapping Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting

Activity Mapping - Property Class
 Only one property can be attached to Product Group
 Values cannot be viewed or edited at arrangement level
 Arrangement level values track changes to Product condition
Property Class
ACTIVITY.MAPPING
Attributes
Type
DATED,
MERGE,
TRACKING.ONLY
Activity Mapping - Product Condition
 Transaction
 Deposit Payments and withdrawals in arrangements initiated through
Account based applications like FT, TELLER
 Transactions triggered through Transaction Codes
 Transaction Codes of other applications that trigger AA activities specified
 Transaction Activity
 Activity performed in an arrangement when a movement with associated
Transaction Codes is posted from FT, Teller etc
 Default Activities for unmapped Transaction Codes of Debits and

Credits can be specified
Activity Mapping – Links
 Transaction Type
ACDF
 Maps to Transaction Code
 Using FT.TXN.TYPE.CONDITION
FT.TXN.TYPE.CONDITION
 Which maps to Activity

 Using AA Activity Mapping 483
 Similar mappings for Activity Mapping

 AC.CASH.POOL
(AC.SWEEP.TYPE) and TELLER
(TELLER.TRANSACTION) DEPOSITS- APPLYPAYMENT-
DEPOSIT.PAYMENT.RULE
Workshop - 6 – ACTIVITY MAPPING settings
ACTIVITY.MAPPING
 Map Transaction Code 483 to DEPOSITS-APPLYPAYMENT-
DEPOSIT.PAYMENT.RULE activity
 Map Transaction Code 486 to DEPOSITS-APPLYPAYMENT-
DEPOSIT.PAYOUT activity
 Set DEPOSITS-CREDIT-ARRANGEMENT activity to Default Credit
 Set DEPOSITS-DEBIT-ARRANGEMENT activity to Default Debit
 Set DEFAULT.NEGOTIABLE to NO
Workshop – Solution - 6
Interest Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting

Interest – Property Class
 Multiple Interest properties can be defined

 Interest property is tracking
Property
Attributes Class
Types INTEREST
DATED, CCY, MULTIPLE,
TRACKING,
FORWARD.DATED
Balance
Prefix
Pre-fixes for Balance types controlled by
ACC, PAY
Interest – Product Condition
 Interest Types
 Fixed interest
Interest Rate to be specified
 Floating interest
Id of BASIC.RATE.TEXT table to be specified
 Periodic interest
Id of PERIODIC.INTEREST table to be input
Interest rate is defaulted for the TERM of the arrangement
Interest rate for TERM falling between periods defined in the table can be
interpolated
 If user inputs a rate, system will not default rates from

BASIC.INTEREST Table or PERIODIC.INTEREST Table
 Periodic Interest can be reset at predefined frequency

 Tiered interest Rates
 Interest rates can be defined as a single tier, or multiple tiers
 With multiple tiers, rate varies according to balance amount

Level – rate is level across the whole balance
Banded – rate varies between bands
 Each tier can have a different rate type
 Each tier can have different margins
 Minimum and Maximum rates for each tier can be defined

 Tier Amount
 Relates to RATE.TIER.TYPE Field
 Amounts can be entered if either BAND or LEVEL selected
 Tier Percent
 Allows a percentage of the principal to be allocated a specific rate or be
linked to a rate table
 Either Tier Amount or Tier Percentage can be opted for Band based
calculation, not both
 Interest Day Basis

 To calculate interest based upon several different day basis types
 Each T24 Interest Day Basis type is represented as a numerator and
denominator
A (360/360); B (366/360); C (366/366); D (360/366); ……
 Accrual Rule
 Include first day for interest accrual
 Include last day for interest accrual
 Include first and last days for interest accrual
 Compounding
 DAILY, WEEKn, Mnn, TWMTH, Nnnn
Slide 67
 Calculation Threshold
 Minimum balance to be maintained below which interest will not be
calculated
 Negative Rate
 Option to set negative interest rate on accounts in credit
 Can set negative interest or it may result due to higher negative spread
 If set to NO or NONE and interest rate falls below “0”, Zero interest will be
accrued
 If set to YES, negative rate can be input, negative margin can make the
final rate more negative
 If set to BLOCK MARGIN, negative effect due to margin not allowed
Slide 68
Interest – Other features
 Each interest component is represented by an Interest Property
 Accrue
 Calculates accrued interest, posts amount using associated accounting rule
 Periodic Reset
 Fixes the rate according to current Periodic Interest conditions
 May cause interest recalculation and change to payment schedule
 Scheduled or manual
 Change
 Manual change to any of the Interest attributes may cause interest
recalculation, may cause Payment Schedule to change
Workshop – 7 – FIXED INTEREST settings
 Use Admin Menu > Product Builder > Product Conditions > INTEREST
 Create a new Product Condition for fixed interest type
 Default interest rate is 6%, negotiable not below 5.5% but can go upto 6.5%
with an override if maximum rule is broken
 Use Interest Day Basis “B”
 Interest accrual to include first and last day
 Tier Type is SINGLE
 Attributes are negotiable by default
Workshop – 8 – FLOATING INTEREST settings
 Create a new Product Condition for floating interest type
 Use BASIC.INTEREST Table 1
 A default margin of 0.5%, negotiable but not below 0.25%. Also make the
upper limit 0.75% but can be allowed beyond with an override
 Minimum and Maximum rates are 7% and 9% respectively
 Use Interest Day Basis “C”
 Interest accrual to include Last Day
 Negative interest effect due to margin not allowed
 Attributes are negotiable by default
Workshop - 9 – Periodic Interest settings
 Create an Interest Product Condition with the following features:
 Use Periodic Interest Table 90
 Interpolate when Deposit Term is between specified periods
 Periodic Reset should happen automatically twice a year
 A default margin of 0.50%, negotiable down to 0.25% with an override if
exceeded. Cannot be negotiated beyond 0.75%
 Negative interest can be input or negative margin can make the final rate
more negative
 Use Interest Day Basis Table A
 Interest accrual to include First Day
 PERIODIC.PERIOD and PERIODIC.RESET are the only other negotiable
attributes
Quiz 2 – True or False
1. Activity Mapping Property provides the link between external

applications and arrangement activities when performing debit or credit
to an arrangement account
a) True
b) False
2. Periodic Reset for Interest is not allowed in AA

a) True
b) False
3. Each Tier amount can have different interest rate types and different
margins
a) True
b) False
Quiz 2 – True or False
4. Calculation Threshold for Interest specifies the minimum interest

amount for an arrangement
a) True
b) False
5. AA Supports Negative interest

a) True
b) False
Payment Schedule Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting

Payment Schedule – Property Class
 Defines Rules for paying Interest, paying Principal and collecting

Charges for a Deposit product
 Property can be viewed and values can be edited

Property
 Product condition is Dated, Forward dated Class
and Currency specific PAYMENT.
SCHEDULE
Attributes
Types
DATED, CCY,
FORWARD.DATED
Payment Schedule – Product Condition
 Payment Types:
 ACTUAL - Repayment of calculated property classes - Interest, charge
 CONSTANT - Requires both Term amount (Account) and Interest Property

to be specified
 LINEAR - Requires a term amount (Account) property to be specified
 Payment Methods :
 DUE - Amount is Due to or from customer
 CAPITALISE - Capitalise the amount
 PAY – Amount paid to customer
 MAINTAIN – Actual amount to be maintained for rollover

 Payment frequency
 Frequency at which payments will be made due
 Applicable for Payment Type
 Due frequency
 Frequency at which payments needs to be made due
 Applicable for properties within a Constant payment type
Principal and interest frequency must be the same as that of Payment
frequency
Charge property can have different frequency
 Payment frequency is defaulted when due frequency is null
 Deferred Periodic Charges defined in Payment Schedule

 Actual amount - for ad-hoc payments, actual amount for each payment
date to be defined
 Overrides the calculated amount
 Start Date – Indicates actual payment start date

 Defaulted from Base date, if start date not indicated
 End Date - Indicates actual payment end date
 Number of Payments can be indicated instead of End date
 Start date and End date fields can accept not only an absolute date but
also a ‘relative’ date
Defining relative dates
 Relative date in Start Date or End Date field based on events:

 START – Initial Deposit of arrangement
 MATURITY – Maturity of an arrangement
 RENEWAL – Renewal date for an arrangement
 Relative Start or End date for Start / Maturity / Renewal

 Can relate to past or future event
 Values can be chosen from calendar or entered directly
 If entered directly, input into the fields START.DATE and END.DATE

can be:
 R_XXXX + 2D - (Relative event XXX and offset by 2 Calendar days
forward)
 R_XXXX - 5Y - (Relative event XXX and offset by 5 Years backward)
 D_20001130 - ( Exact date specified as 30th Nov 2000)
 Recalculating Payment Schedule

 Possible to be scheduled
 Possible due to occurrence of certain activities
 Scheduled Recalculation
 Automatically at predefined frequency
weekly, monthly, yearly, etc
 Activity to trigger recalculation like:

 Update Charge
 Change Interest
 Change Term
 Increase / Decrease Term Amount
Slide 84
 Recalculation types
Payment – payment amount will be changed
Term – term of the arrangement will be altered
Residual – residual amount will be changed
Nothing – payments, term, and residual will be unchanged. Recalculation

frequency should be specified
Progressive Payment – Increase / decrease in calculated amount
Slide 85
 Bill Type indicates whether bill is produced for payment / information

 Payment – Payments made to customer like Interest
 Expected – Principal amount to be received from customer
 Bill can be produced prior to due date

 If interest is to be paid to customer on the 10th of every month and the bill is
to be issued on the 9th, this field will be set as ‘1’
 Combining due amounts into a single bill

 When amounts become due on the same date
 Notices are also to be issued on the same date
 Either a single bill can be generated or bills can be split to allow payments
from / to separate accounts
 Billing
 Make due activity
 All due amounts are billed - Principal, interest and charges
 Bills are generated whether payment is scheduled or ad-hoc
 Generates bill on due date or in advance by a specified no. of days
 Chaser fee charge can be linked to the activity
 Different payment types can be specified for different periods

 Start Date and End Date for each period must be specified
 User can also specify amount of repayment
When amount is manually input, system will not calculate repayment
amount
Workshop - 10 PAYMENT SCHEDULE Settings
PAYMENT.SCHEDULE
 Interest, at monthly frequencies, to be paid
 Attributes are negotiable
Workshop - 11
PAYMENT.SCHEDULE
 Linear monthly repayment
 Single bill for Principal and Interest
 Attributes are negotiable
Workshop Solution - 11
SETTLEMENT Property Class
Customer Interest Charge Payment Rules
Settlement Payout rules
Account Closure
Deposits
Officers Payment Schedule
Tax Accounting
Activity Activity Activity Activity

Presentation Mapping Charges Restriction
Settlement – Property
 Allows select settlement instructions for Deposits arrangements
 Links a mandate defined in the Direct Debit (DD) module to an

arrangement account
 Product condition is Date specific
Attributes SETTLEMENT
Types
Property Class
DATED
Settlement of Dues / Payout
 Multi-value set of fields for Receive and Payout transactions
 Receive definition based on Payment Types and related activity
 Payout definition based on Property and related activity
 Arrangement reference as PAYIN.ACCOUNT / PAYOUT.ACCOUNT

 Enables settlement of dues / pay-out using another arrangement / account
 Can either be a T24 account or an arrangement account
 PAYIN.ACTIVITY/PAYOUT.ACTIVITY - APPLYPAYMENT action only
 PAYIN.SETTLEMENT field to be set as Yes

Settlement Instruction - Receive
 Meant for Funds coming into the Arrangement
 Payment Type
 Link between Payment Schedule and Settlement property
 Can be sub valued for different types of Interest, Charges
 Pay-In Settle Activity

 Activity run to receive funds, only APPLYPAYMENT allowed
 Refers to AUTO.SETTLE field of respective Payment Schedule
 If set as Yes, fetches Settlement Account corresponding to Payment Type
 Active – can be set as ‘No’ to:

 Stop a settlement instruction at arrangement level
 Customer level settlement instruction for a payment type can be set
different for an arrangement
Settlement – Receive funds
 Could be either from a T24 ACCOUNT module (internal / nostro) or

from a T24 Arrangement or from DD mandate
 Receiving Fund examples:

 Funding of AA Deposit
 Receipt of scheduled Charges
 Settlement for Activity Charges

 Grouped under payment type ACTCHARGES
 Refers to AUTO.SETTLE field of respective Activity Charges property
 If set as Yes, fetches Settlement Account corresponding to Payment Type
 Activity charges property designed to settle out of UNC first, if available

Settlement – Receive funds – ACCOUNT.DEBIT.RULE
 Insufficient funds in Account indicated for a Payment Type
 Settlement process controlled by ACCOUNT.DEBIT.RULE
 Pay-In rule Field has values Full, Partial, None
 Full – Whether or not funds available, debit Pay-In account with full bill
amount
 If funds available partially, overdraft created for short amount
 Partial – Pay-In account debited only to extent of funds available
 None – Pay-In account not debited unless funds are available to settle
the bill in full
Settlement Instructions – Pay Out
 Meant for pay outs from an Arrangement
 Pay out examples:

 Pay-out of AA Deposit at maturity
 Scheduled Interest payment
 Could be to another T24 Account or T24 Arrangement
 Settle activity looks in settlement property based on the Property or

Property Class, fetches corresponding settlement instructions
 Pay-Out Settle Activity

 Activity run to pay funds, only APPLYPAYMENT allowed
Settlement Processing in different currencies
 Arrangement bills in one currency can be settled by:

 Another arrangement in same currency / another currency
 T24 Account in same currency / another currency
 Settlement processing is possible as follows:
Source Settlement Due bills

Arrangement Arrangement
LCY FCY -
FCY LCY -
FCY Same FCY -
FCY Different FCY -
LCY - FCY
Settlement of Direct Debits
 Settlement Method for payment - option is DD
 DD Transaction code must be mapped to AA activity through

ACTIVITY.MAPPING Product Condition
 Payment rules for DD set in APPLY.PAYMENT field in

PAYMENT.SCHEDULE Product condition
 Payment Type
 Can hold any payment type defined in payment schedule
 DD.DDI record status should be AVAILABLE

Workshop – 12 – SETTLEMENT Product Condition
SETTLEMENT
For receiving deposit funds:

 Payment type is DEPOSIT.PRINCIPAL
 Settle activity is to be defined as DEPOSITS-APPLYPAYMENT-
PR.DEPOSITS
 Settlement instructions should be active
 Pay-In account should be debited only to the extent of funds available
For paying out Interest / Charge / Principal:

 Define settle activity as DEPOSITS-APPLYPAYMENT-PO.DEPOSIT
 Settlement instructions should be active
Payment Rules Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting

Payout Rules Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting
Activity Activity Activity

Payout Rules
Presentation Mapping Charges
Payment Rules & Payout Rules – Property Classes
 Both define Rules for handling a payment

 Payment rules – Used when Customer pays to Bank
 Payout rules – Used when Bank pays to Customer
 Property Type is product only
 Product condition is Dated, Multiple and Tracking
Property
Class
PAYMENT
RULES
Attributes
Types
DATED, MULTIPLE, Property
TRACKING Class
PAYOUT
RULES
Payout Rules & Payment Rules – Product Condition
 Payment application type

Specifies how the payout / payment rules will apply to an arrangement
 Payments application order

 Oldest first – earliest one followed by later bills one after the other
 Oldest last – the latest one first and then the previous one, so on
 Property sequence
 Specifies the property sequence in which balances will be affected during
repayment
 Must be a valid property of Interest, Charge or Principal amount
Payout Rules Definition
 Funds in PAY / UNC / CUR balances can be withdrawn
 Payment application type can hold values: CURRENT.PAY, PAY and

DEPOSIT.RULE.PAY
Field Withdrawal Withdrawal Total withdrawal

from CUR from UNC from PAY balance
balance balance
PROP.APPL.TYPE CURRENT BLANK BLANK
APPLICATION.TYPE CURRENT.PAY PAY DEPOSIT.RULE.PAY
Deposit Redemption - other features
 Pre-closure of deposit possible with withdrawal of all available balances
 Simulation of a redemption / partial withdrawal from deposit

arrangement is possible
 Simulation can be on a current date / future date / back date
 Withdrawals / partial withdrawals in a given period of time can be

controlled through ACTIVITY.RESTRICTION and PERIODIC.RULES
 Charges can be attached to the above

 Charges can be made due / deferred
 Can be collected for all transactions / select transactions
 Charge API routine for early redemption / withdrawal penalty
Workshop – 13 PAYMENT RULES Setting
PAYMENT.RULES
 Choose Application Type as BILL.DATE
 Pay off Bills in the following order:
Properties : DEPOSITCHARGE
DEPADMINFEE
Earliest bills to be paid first
 All Attributes are negotiable by default
Workshop – 14 PAYOUT RULES Setting
PAYOUT.RULES
 Choose Application Type as DEPOSIT.RULE.PAYOUT
 Pay off Bills by Property in the following order:
Properties : ACCOUNT, DEPOSITINT
Earliest bills to be paid first
Activity Restriction Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting

Activity Restriction – Property Class
 This Property Class allows Multiple Properties and is TRACKING type
 Currency and Date Specific

 Product Condition to be created for every currency
Property Class
for
Attributes Types ACTIVITY
DATED, CCY, MULTIPLE, RESTRICTION
TRACKING,
FORWARD.DATED
Activity Restriction – Product Condition
 Full restriction of Activity

 Activity cannot be run altogether
e.g. Not to allow change of Term of Arrangement
 Error message is Mandatory
 Activities can be refined into a partial or conditional restriction

 Control activity but allow with override
e.g. Allow more than 5 deposit repayments in a year only after
approving override, deposit receipts must be in multiples of 100
 Override message is Mandatory
 It can be controlled by Periodic Rules
 For Transactions this can be refined into a partial or conditional

restriction
 Deposit receipts must be in multiples of 100
 It can be controlled by Periodic Rules
Workshop – 15 ACTIVITY RESTRICTION Settings
ACTIVITY.RESTRICTION
 Set the rule to restrict Prepayment of the Deposit to 40 Percent

(DEPOSIT-APPLYPAYMENT-PO.CURRENT)
 We would revisit this workshop in Periodic Attributes (LU5) to attach a

Periodic Attribute and the activity to restrict the prepayment of the Deposit
to 40 Percentage
 If user attempts to break the rule Override message to be displayed with a

Charge
 All Attributes are not negotiable by default

Workshop Solution-15
CHANGE PRODUCT Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting
Activity Change Activity Periodic

Presentation Product Charges charges
Change Product - Overview
 Property class is Date specific and TRACKING Type
Property
Attributes Class for
Types
CHANGE
DATED, TRACKING PRODUCT
Change Product – Product Condition
 Allowed Product
 Products to which switch is allowed
 If left blank switch is permitted to all products
 Switch is permitted only within the same product group
 Scheduled Switch of existing Arrangements to a different product

 CHANGE.DATE Field - Switch on a specific date, Date Convention ignored
 CHANGE.PERIOD Field - Switch after a particular period
 PRIOR.DAYS Field - Switch in advance to Switch Date by these days
Change product event happens in advance of Schedule Date
Effective Value of Switch is Schedule Date
e.g. Switch on 26 APRIL effective 01 MAY
 Switch can be Automatic or Manual
Change Product – Product Condition
 Change Activity
 Activity to be triggered on renewal of arrangement
 Mandatory if renewal date is specified
 Activities allowed are ROLLOVER, RESET and CHANGE.PRODUCT
 Change to Product
 Product to which arrangement to switch to on a date or a period
 Existing Arrangements can be changed to a different product

 This can be done manually or it can be scheduled
 Majority of conditions are overwritten by the new Product defaults

 Exceptions are: Customer, Account, Term Amount and Limit
Change Product – Deposit Renewal Activities
 ROLLOVER
 Renewal with existing arrangement conditions or with revised conditions
 Product conditions with TRACKING Option alone will be tracked
 RESET
 Reset happens on Payment end date
 Resets product conditions based on reset set up at product level for
different properties
Change Product – Deposit Renewal Activities
 CHANGE PRODUCT
 Resets to product conditions of the new product
 Based on reset set-up at product level of old product for different properties
 User initiated activity happens on renewal date
 Effects of DEFAULT.ATTR.OPTION on CHANGE.CONDITION Activity

 Change conditions would happen only when DEFAULT.ATTR.OPTION
Field is set RESETTING
 If set NON-RESETTING or NONE, new condition will not take effect for
arrangement
 RENEGOTIATE
 Activity used to change the arrangement conditions of different properties at
one stretch
Change Product – Product status
 Status of the product specified in AA.ARRANGEMENT
 PROCESSED – when arrangement moves from old product to new

product, status of old product is updated as PROCESSED
 CURRENT – Status indicates arrangement is running on the current

product
 SCHEDULED – If the product is scheduled for a future date, status is

updated as SCHEDULED
Workshop - 16
CHANGE.PRODUCT
 Change period is 6 months
 Set DEPOSITS-RESET-ARRANGEMENT activity for Change activity
 Switch to happen 3 days in advance to Change Period

CHARGE and ACTIVITY CHARGES Property Classes
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting

Charge – Property Class
 Multiple Charge properties allowed
 Currency is optional
Attributes
Types Property
DATED, OPT.CCY,
MULTIPLE, TRACKING, Class for
FORWARD.DATED Balance CHARGE
Prefix
ACC, PAY, DUE

Charge – Product Condition
 Charge Type
 Fixed or Flat
Charge amount should be set
USD 50; GBP 30, etc
 Calculated
Calculated on specified balances
2% on Transaction amount, 3% on Commitment amount, etc
 Charge Currency
 Currency of charge property
 Charge will be calculated for the charge property
 Amounts calculated rounded based on Currency of CHARGE property
 Can be different from currency defined in Id of the Product condition
 Tiered charges
 Level, Banded, Groups
 Calculation Type
 Flat
Charge amount should be set - USD 50; GBP 30, etc
 Percentage
Calculated on specified balances - 2% on Transaction amount
 Unit
Multiplication factor to arrive calculating charge - USD 2 per transaction
 Charge Rate
 Rate at which charge calculated
 Mandatory for Percentage Calculation Type
 Charge Amount
 Amount of charge
 Amount will be multiplied when Calculation type is UNIT
 Mandatory for Flat and Unit Calculation Type
 Minimum and Maximum Charge Amount can be set for each tier
 Cannot be input for Flat Calculation type
 Calculation Threshold
 Base amount below which charge amount will not be calculated
 Free Amount
 Deduction allowed on calculated charge
e.g. reduce USD 10 from calculated charge
 User defined Charge Routine

 Can be added to Activity Restriction / Activity Charges product condition
 Useful when Banks desire different / complicated methods of charge
calculations
Activity Charges – Property Class
 Define charge property when specific activities take place

 It is DATED, FORWARD.DATED and TRACKING type
Property
Attributes Class for
Types ACTIVITY
DATED, TRACKING,
FORWARD.DATED CHARGES
Activity Charges – Product Condition
 Activity attracting charge

 Activity Id to be input
 Must be a valid record in AA.ACTIVITY
 Any number of activities can be defined
 Charge Property
 Charge property triggered when activity is triggered
 Charge property for each activity can be defined when more activities are
charged
 Billing the charge

 Charge can be billed on occurrence of activity
 Can optionally be deferred by days after activity occurrence
Charge and Activity Charges – Other features
 Activity Charges
 Charge applied when Activity is performed. e.g. Deposits Redemption charge
 Can be billed or deferred or capitalised
 Scheduled Charges
 Charge applied on a particular day according to payment schedule e.g.
Deposits Annual fee
 Can be billed or deferred or capitalised
 Rule break Charges

 Charge applied when a periodic rule is broken
 Periodic rules defined in certain product conditions
e.g. Restrict maximum number of redemptions per year
Charge – Other features - Scheduled Charges
• Frequency defined
Defined in a Payment • Charge Property Attached
Schedule • Payment Schedule attached
to Product
• Flat Amount – Annual Fees

• Calculated on a base amount
Type of Charge • Base amount type defined in
AA.SOURCE.CALC.TYPE
• Depends on AA Account
Balance
• Payment Schedule Property
In Product with its condition
• Charge Property (defined in
Condition Payment Schedule) with its
condition
Charge – Other features - Break Rule Charges
Defined in specific
Product Conditions • Under Periodic Rules tab
• In Term Amount, decrease of

Based on failure of (Deposit) Term Amount in 1
Periodic Attributes year by 10%
• Linked to a Charge Property
• Charge Property (defined in

In Product Periodic Rules tab) with a
linked condition defined
Condition • Fixed or calculated on a base
amount
Activity Charges – other features
• Create New Arrangement

ACTIVITY BASED • Closure of a Deposit
• Redemption of a Deposit
• Links an Activity to a
Charge Property
Separate • Flat Charge
Property Class • Charge based on Balance
Type In
AA.SOURCE.CALC.TYPE
• Activity Charge Property
with its condition
In Product • Charge Property (linked
Condition to Activity Charge
Product Condition) with
its condition
Workshop – 17 – Fixed Charge Settings
 Use Admin Menu > Product Builder > Product Conditions > CHARGE
 Set the following rules
Fixed Charge of USD 100
Workshop Solution – 17
Workshop – 18 – Charge Condition Settings
Charges in USD
No charges for transaction amount up to 3,000
2% for transaction amount up to 20,000 with a minimum of 100
Additonally1.5% for transaction amount beyond 20,000 and up to 50,000
with a minimum of 500
Additionally 1% for transaction amount over 50,000 subject to a minimum
of 800 and maximum of 2,000
Workshop - 19
Charges in USD
No charges for transaction amount upto 5,000
Flat Charge of 100 for transaction amount upto 10,000
Flat Charge of 300 for transaction amount upto 30,000
Additionally 1.5% for transaction amount beyond 30,000and upto 50,000
with a maximum of 500
Additionally 1% for transaction amount over 50,000 subject to a maximum
of 5,000
Allow a rebate of 50 on charge amount
All Attributes are not negotiable by default
Workshop – 20 – Activity Charges Condition Settings
ACTIVITY.CHARGES
Charge to be levied when a new Deposit is opened
The Charge Property is DEPADMINFEE
This New Deposit Fee to be made DUE on occurrence of activity
 All Attributes are not negotiable by default
Charge Override Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting
Activity Activity Activity Charge

Presentation Mapping Charges Override
Charge Override – Property Class
 This property is dated and non-tracking
 Property appears in an arrangement after an Activity charge is triggered

and validated
Property Class for
CHARGE.OVERRIDE
Attributes
Types
DATED, NON.TRACKING,
TRIGGER
Charge Override – Product Condition
 Charge Amount
 User input activity triggers an activity charge / periodic charge
 On committing the activity, system defaults charge amount in arrangement
 Charge Actual Amount

 Value could be Null, Zero or a numerical value
 Charges are waived completely if value 0 is input
 Default charge as in CHG.AMT would be levied if this field is left blank
 User can modify this charge by inputting a new charge amount, if left
negotiable
 If more than one charge for the same activity is attached, user can
modify / waive all
 Charges collected during payout, redemption etc. cannot be modified or

waived
Workshop - 21 – CHARGE OVERRIDE
CHARGE.OVERRIDE
 Set the following:
3 Charge Properties - DEPADMINFEE, DEPOSITCHARGE,
PRINDECREASEFEE to be indicated under Property
Input Charge Actual Amount of 500 against DEPADMINFEE
Periodic Charges Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting

Periodic Charges – Property Class
 This property is dated
 Currency is optional
Property Class for

PERIODIC.CHARGES
Attributes
Types
DATED, OPT.CCY
Periodic Charges – Product Condition
 INC.ALL.DEF.CHGS
On the scheduled date whether all the deferred charges to be made due
 DEFERRED CHARGE
Charge property that are deferred and to be made due can be multi-
valued
 Both attributes can be set either at product level or at arrangement level

Workshop - 22 – PERIODIC CHARGES
PERIODIC.CHARGES
 Set the following:
Charge Properties - DEPADMINFEE and DEPOSITCHARGE to be
deferred
Tax Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting

Tax – Property Class
 Multiple Tax properties allowed
 Currency and Dated
Attributes Types Property

DATED, CCY, MULTIPLE Class for
Balance TAX
Prefix
DUE, AGE
TAX – Product Condition
 Property Class
 Tax can be collected currently for Interest and Charge
 Tax Code
 Tax table with rate for computation of tax for associated property class
 Either TAX.CODE or TAX.CONDITION allowed
 Tax Condition
 Valid TAX.TYPE.CONDITION
 Either TAX.CODE or TAX.CONDITION allowed
TAX – Product Condition
 Property
 Property on which Tax is calculated
 Tax can be collected currently for Interest and Charge properties
 Property Tax Code

 Tax table with rate for computation of tax for associated property class
 Either PROP.TAX.CODE or PROP.TAX.COND allowed
 Property Tax Condition

 Valid TAX.TYPE.CONDITION
 Either PROP.TAX.CODE or PROP.TAX.COND allowed
Workshop – 23 - Tax on Deposit Interest
 Use Admin Menu > Product Builder > Product Conditions > TAX
 Tax to be collected on Deposit Interest
 Property for Deposit Interest is DEPOSITINT
 For withholding tax, property tax condition is DEPTAX

Workshop – Solution 23 - Tax on Deposit Interest
Closure Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting

Closure – Property
 Handles closure of Arrangements
 Product condition is Dated and Tracking
Property Class
Attributes
Types for
DATED, TRACKING CLOSURE
Closure – Product Condition
 Closure Type
 MATURITY - Closure processing would depend on maturity date
 BALANCE - When all balances become Zero closure activity is scheduled
 Closure Method
 Valid options are Automatic, Manual and Online
 Specifies whether closure processing would be triggered automatically or
manually or Online
 Closure Period
 Indicates when CLOSURE activity would be processed for Automatic
closure
 Posting Restrict
 Specifies the account closure posting restriction code
Workshop - 24
 Use Admin Menu > Product Builder > Product Conditions > CLOSURE
 Closure to happen automatically on maturity
 Period for processing is 10 days
 Posting restriction code is 90
 All attributes are negotiable by default
Workshop - 25
 Use Admin Menu > Product Builder > Product Conditions > CLOSURE
 Closure to happen automatically when all balances become zero
 Period for processing is nil
 Posting restriction code is 90
 All attributes are negotiable by default
Quiz 3 - Match the Following
1. Activity Charge a) Not Currency dependent
2. Scheduled Charge b) DEPOSITS-NEW-

ARRANGEMENT
3. Break Rule Charge c) Payment Schedule
4. Charge Property Class d) Currency dependent Optional
5. Activity Charge Property Class e) Periodic Rules

Advanced Concepts Periodic Rules
AA.PERIODIC.ATTRIBUTE.CLASS
Property
 Released by TEMENOS to define Actions and Attributes for any Class
underlying Property and Product condition
Action
AA.PROPERTY.CLASS whose condition Periodic
uses the periodic rule Attribute
Comparison
Type Class
ACTIVITY.RESTRICTION, ACCOUNT,
CHARGE, INTEREST and TERM.AMOUNT
ACTION for AA.PROPERTY.CLASS Data Type
Routine
RECEIVE, REDEEM, INCREASE,
DECREASE ……
Comparison Types for rules defined in

EB.COMPARISON.TYPE Table
MINIMUM, MAXIMUM, +BASISPOINTS, .........

Data types allowed to use Periodic Rule ROUTINE that returns value for
are hard coded comparison routine to do comparison
from Property record. Valid entry in
AMT, PERIOD, A, D, N, R, DAO EB.API File
 Periodic Attribute is a named type / instance of a Periodic Attribute

Class
 Periodic Attribute is used in Product Condition
Rule that needs to be applied on a specific PR.ATTR.

period or life time of Arrangement. Is
CLASS
controlled by PERIOD.TYPE Field
PERIOD.
LIFE, INITIAL, REPEATING & ROLLING
TYPE
Periodic
Attribute
PERIOD field controls exact period for which PERIOD

Rule is defined
01D, 5M, 2Y,…
 Periodic Attribute is a named type / instance of a Periodic Attribute

Class
 Periodic Attribute is used in Product Condition
Rule that needs to be applied on a specific PR.ATTR.

period or life time of Arrangement. Is PERIOD.
TYPE CLASS
controlled by PERIOD.TYPE Field
LIFE, INITIAL, REPEATING & ROLLING
PERIOD field controls exact period for which Periodic

Rule is defined PERIOD Attribute
01D, 5M, 2Y,…
RULE.START Field represents Base Date ERROR /

AGREEMENT, ANNIVERSARY, RULE.START OVERRIDE
ARRANGEMENT, COOLING-OFF & START MESSAGE
RULE.ERR.MSG and RULE.OVE.MSG Fields

control generation of ERROR and
OVERRIDE messages respectively
Periodic Rules - Structure
Periodic Attribute Class
Property Class Comparison Type Routine
Periodic Attribute
Time Element
Periodic Rule in the Product Condition for the Property Class

Periodic Comparison
Break Result Break Charges
Attribute value
Periodic Attribute Class - Interest Property Class
 MAXIMUM RATE - Periodic Rule for Maximum Interest Rate
 MINIMUM RATE - Periodic Rule for Minimum Interest Rate
 RATE DECREASE - Periodic Rule for Rate Decrease
 RATE DECREASE TOLERANCE - Periodic Rule for Rate Decrease in

percentage
 RATE INCREASE - Periodic Rule for Rate Increase
 RATE INCREASE TOLERANCE - Periodic Rule for Rate Increase in

percentage
Periodic Attribute Class -Term amount & Account Property Class
Term Amount
AMOUNT DECREASE - Periodic Rule to control decrease in Principal
Amount
AMOUNT DECREASE TOLERANCE - Periodic Rule to control

percentage decrease in Principal Amount
AMOUNT INCREASE - Periodic Rule to control increase in Principal

Amount
AMOUNT INCREASE TOLERANCE - Periodic Rule to control percentage

increase in Principal Amount
Account
FULL.DEPOSIT – Periodic rule to control the deposit of full commitment
amount
Periodic Attribute Class - Activity Restriction Property Class
 TRANSACTION AMOUNT MAXIMUM - Periodic Rule to control

Maximum Transaction Amount
 TRANSACTION AMOUNT MINIMUM - Periodic Rule to control

Minimum Transaction Amount
 TRANSACTION AMOUNT MULTIPLE - Periodic Rule to control

Transaction Amount in Multiples, E.g. deposit amounts in 100s
 TRANSACTION AMOUNT TOTAL - Periodic Rule to control Total

Transaction Amount, E.g. total deposit amount not less than 100,000
 TRANSACTION COUNT TOTAL - Periodic Rule control Total Number

of Transactions, E.g. not more than 2 partial withdrawals in a year
 FULL.REDEEM - Periodic Rule to control Redemption of Deposit

Workshop - 26
 Use Admin Menu > Product Builder > Periodic Attributes > ACCOUNT
Property Class
 Set a Periodic Attribute for checking that only full deposit amount is
permitted while funding. Rule to be applied for life of arrangement, with
effect from start date of arrangement
 Use Admin Menu > Product Builder > Product Conditions > ACCOUNT
Property Class >
 Attach the periodic attribute to Account product condition – Use Fixed
Floating Deposit
Workshop - 27
 Use MB Admin Menu > Product Builder > Periodic Attributes >
TERM.AMOUNT Property Class
 Set a periodic attribute for decreasing Principal amount during the first year
of arrangement
 Use Admin Menu > Product Builder > Periodic Attributes > ACTIVITY
RESTRICTION Property Class>TOTAL.LOAN.REPAY.TOLERANCE
 Set a periodic attribute for restricting the Prepayment Restriction amount
during the Life of an arrangement
 Use Admin Menu > Product Builder > Product Conditions >ACTIVITY
RESTRICTION Property Class
 Attach the periodic attribute to Activity Restriction product
condition - Use Restrict Prepay – Workshop Number 15
Quiz 4 – Answer the following
1. TRANSACTION.AMOUNT.MAXIMUM Periodic Attribute Class can be

used to restrict the Term Amount
a) True
b) False
2. Periodic Attribute Classes are linked to Properties

a) True
b) False
3. Periodic Attribute Class is not a Property Class

a) True
b) False
Building Banking Products
AA - Tables used for building Banking Products
 Tables used for building Banking products from re-usable components :

 AA.PRODUCT.LINE
Designed by TEMENOS
 AA.PRODUCT.GROUP
 AA.PRODUCT.DESIGNER
 AA.PROPERTY and AA.PRD.DES.<PROPERTY.CLASS> set up

earlier could be used across several Products, if the underlying
Property class is same
 Composite screens used for building these for ease of operation

AA.PRODUCT.LINE
 High level definition of Business lines

 Defined by indicating the Property Classes that constitute the Business Line
 Used for building blocks to construct Product groups and individual
Products falling under the line
 Pre–defined by TEMENOS
Only description can be modified
 For Deposits Product Line, TEMENOS would have set

LINE.ATTRIBUTE Field as CCY and REPLAY
 For other lines like Internet services, this would be left blank
 Property Classes that constitute the line are to be marked as

Mandatory or not
 For a mandatory Property Class, there should be atleast one Property
present in its Product Groups and Products
 If any Property is to be included at a Product level, its Property class should
have been defined at Product line level – either as Mandatory or Optional
AA.PRODUCT.GROUP
 Groups of Products are formed from Product Lines

 Each Product group has a number of Properties associated with it
 Gives a basic shape to associated products
 Properties can be specified as Mandatory or not at this level

 Each Product Group must have atleast one mandatory Property for each
of the mandatory Property Classes of its Product Line
 A mandatory Property should be necessarily defined at Product Level
 Possible to indicate Internal or External as the Group Type

 Product Groups of Bank’s own Products marked as Internal and Groups of
other Banks’ Products as External
 External group products used for comparative analysis
 When a Property is added to a Product Group, Activities for the

Property are generated automatically
 REBUILD.ACTIVITIES Field to be set as YES
Workshop - 29 – Creation of New Product Group
 Use Admin Menu > Product Builder > Products > Product Lines –Deposits
Create a new Product Group with the following Settings:

PROPERTY CLASSES PROPERTY MANDATORY
ACCOUNT ACCOUNT YES
ACCOUNTING DEPOSITS YES
ACTIVITY.MAPPING ACTIVITY.MAPPING YES
CUSTOMER CUSTOMER YES
PAYMENT.RULES PR.DEPOSITS YES
TERM.AMOUNT COMMITMENT YES
PAYMENT.SCHEDULE DEPOSIT.SCHEDULE YES
INTEREST DEPOSITINT
ACTIVITY.RESTRICITON AR.PRINCIPAL.DECREASE
ACTIVITY.CHARGES ACTIVITY.CHARGES
ACTIVITY.PRESENTATION PRESENTATION
CHARGE DEPADMINFEE
OFFICERS OFFICERS
CLOSURE CLOSURE YES
TAX TAX
PERIODIC.CHARGES PERIODIC.CHARGES
PAYOUT.RULES PO.DEPOSIT YES
SETTLEMENT SETTLEMENT
CHARGE.OVERRIDE CHARGE.OVERRIDE
AA.PRODUCT.DESIGNER
 Products are designed from Product Group through this table

 Each Product to have all the mandatory Properties and any of the optional
Properties associated with its Group
 For each Property, Product condition should also be defined
 Possible to link more than one product condition to a Property

 User to define period after which additional conditions to be effective
 Can be defined in Days, Weeks, Months or Years
 Products for Inheritance only

 Non Saleable and acts only as Parent
 Does not undergo Proofing and Publishing validations
 Child Product
 PARENT.PRODUCT Field defines Parent to the Current product
 Will inherit properties from the Parent product defined in the field
AA.PRODUCT.DESIGNER
 Product Currency
 Currencies in which the product is available to be indicated through multi
value field
 Currency related product conditions should be available for each of the
Product currencies
 Calculation related features

 Some properties may require calculations for them
Interest and charges may be calculated as percentage of a specified
balance
 User to define source balance and source property for calculation
Workshop –30 – Creation of New Product
 Use Admin Menu > Product Builder > Products > Product Lines – Deposits
> Product Groups
 Create a Product under Product Group created in previous Workshop with the
following settings:
PROPERTY PRODUCT CONDITIONS ARR.LINK

ACCOUNT FIXED.FLOATING.DEPOSIT NON TRACKING
DEPOSITS DEPOSIT TRACKING
ACTIVITY.MAPPING DEPOSIT TRACKING
CUSTOMER DEPOSIT NON TRACKING
PR.DEPOSITS DEPOSIT.PAY.RULE TRACKING
DEPOSITS.SCHEDULE FIXED.FLOATING.DEPOSIT NON TRACKING
COMMITMENT TRGDEPOSIT NON TRACKING
DEPOSITINT FIXED.FLOATING.LEVEL NON TRACKING
ACTIVITY.CHARGES TRGPRODUCT TRACKING
PRESENTATION DEPOSIT TRACKING
DEPADMINFEE 250 TRACKING
OFFICERS DEPOSITS TRACKING
CLOSURE AUTOBAL.CLOSURE TRACKING
TAX TAX NON TRACKING
PO.DEPOSIT DEPOSIT.PAYOUT TRACKING
SETTLEMENT DEPOSITS NON TRACKING
contd....
Workshop –30 (continued)
 Set the following in calculation source tab:
Calculated Property Source Type Source Balance

DEPOSITINT CR.AVERAGE CURACCOUNT
 Product is available in USD

Proofing and Publishing
 Building a Product in AA is a three stage process

 Designing
 Proofing
 Publishing
 In the design stage, the designers make use of available components

to design – their actions have no effect on live products
 To make a new product available to operational staff, it needs to be

made available in Product Catalog
 The designer must Proof the product to check that there are no errors in the
design (particularly where hierarchies are involved)
 It should then be duly published to be included in Catalog
 Proofing and publishing will perform processing from parent down to all
children
Proofing and Publishing Products
Product Management
Proof
Create Product Proofed Publish Product
Designer Products Catalog
Fix
Modify
Product design Operations

Effective dates
 Available Date
 The date from which the current product is available
 System starts looking for valid conditions for all Properties from this date
onwards
 Expiry Date
 The date from which this Product ceases to exist
 It only means that new Arrangements may not be input from this date for
the Product
 Existing Arrangements under the Product will continue
 Errors and Suggestions

 When proofing fails, errors are listed out
 System provides suggestions for rectification of these errors
Workshop – 31 – Proof and Publish the Product
 Use Admin Menu > Product Builder > Products > Product Lines –
Deposits > Product Groups > Products
 Proof the Product created in the previous workshop with :

a) Available date as today
b) Online/service as online
 Then Publish and commit the record

Workshop - 32 – Creation of New Arrangement
 Use User Menu > Retail Operations > Deposits > Deposit
Arrangements - Product Catalog > Product Groups > Your Product
Group > Your Product
 Create an Arrangement for your Customer for the Product published in
previous Workshop
 Look at the defaulted Term and amount of Arrangement. Is it as per your
condition set in workshop 4? Change the term to 1Y and amount to USD
100000.
 Look at the PAYMENT.SCHEDULE property.
 Commit the Arrangement
 See and accept the overrides
 Notice that a charge for New arrangement (DEPADMINFEE) is made due
 Get the record authorised
Workshop - 32
Workshop - 32
Financial Activities
Teller Deposit Funding
Funds Transfer ACTIVITY Apply Repayment

MAPPING
Account related
Deposit Payout
Applications
 Payments from and into an AA Account can be done through ACCOUNT related
applications
 Activity is selected based on Transaction Code

Workshop – 33 – Funding the Deposit Arrangement
 Use User Menu > Retail Operations > Deposits >Deposit Arrangements
> Arrangement Activities (FT) > AA Deposit Fund
 Select the arrangement opened for your customer
 Deposit USD 50,000, debiting Customer’s Current account in USD
 Note down the error message as we have made FULL DEPOSIT as YES
 Modify the deposit amount as USD 100,000 and debit the Customers
Current Account in USD
 Approve Overrides
1. How are activities auto generated ?

a) When a property is used for the first time in a Product Line
b) When a property is used for first time in a product line with
REBUILD.ACTIVITIES set to YES in AA.PRODUCT.GROUP
c) When a new Product Group is created
d) When a new Property is used in a AA.PRODUCT.DESIGNER
2. Which of the following is not an Activity in an Arrangement ?

a) Increasing commitment amount
b) Interest accrual
c) Enquiry
d) Crediting Arrangement
3. Negotiation Rule for an attribute is FIX.VALUE. What will be the impact

when the Arrangement Link for this is set to CUSTOM.TRACKING ?
a) Will track the attribute value irrespective of Negotiation Rule.
b) Will not track the attribute value
c) FIX.VALUE cannot be negotiated but will be tracked
d) CUSTOM.TRACKING will not allow negotiation
4. How can you set allowed Currency in AA.PRODUCT.DESIGNER?

a) Option ‘ALL’ in CURRENCY Field will allow all currencies
b) Restricted Currencies can be specified in CURRENCY Field to allow all
other currencies
c) Allowed Currencies to be input in the multi value ‘CURRENCY’ Field
d) A Product can be set only for Local Currency
Simulation
Simulation - Overview
 Simulation replicates real time scenario

 For a new or existing arrangement for a set of conditions
 Repayment amounts for changes in principal, interest rate, tenor, charges,
Pay out amount for closure of arrangement on a specific date
 Simulation does regular updates as if a real activity but stores data in

simulated files
 Checks conditions and negotiation rules, generates override and error
messages
 Calculates maturity date, charges, repayment amounts
 Prepares repayment schedule
 Simulated data are not real and the projected data are stored in SIM files
 Live arrangement will not be created or updated
 Option to convert simulation activity into live
Simulation - Process
 Can be run for various combinations of projected activities

 Run on the current or a future date
 For a defined period of time
With a start date and end date
 Multiple simulations can be run for a single arrangement

 More than one activity can be simulated in a single run
Change of term, change of principal and change of interest rate
 Arrangement under any AA product can be simulated
 Simulated activity can be retained for a specified period

Simulation – Sub Systems
 Simulation data capture

 Capture data for simulation of new arrangement
 Capture data as part of simulating activities for live arrangement
Renewal, payout calculation for existing deposits
 Simulation runner
 For a specified period
 For specified set of activities
 Simulation Service
 Run simulation for the captured data with the help of service
Run TSA.SERVICE agent and BNK/AA.SIMULATION.SERVICE
This stores required data in different files for retrieval later
Quiz 6– Choose the correct Answer
1. What is Simulation in AA ?
a) Process of payout of AA Deposit
b) Process of replicating a real time scenario
c) Process of closing an Arrangement
d) Process of creating an Arrangement
2. Which of the following is true about Simulation in AA ?

a) It does real activity and updates / creates live records
b) Simulated records cannot be executed into live records
c) It does real activity but will not update / create live records
d) Simulation is possible only for existing arrangements
Pre-requisite for Simulation workshops
 Use Command Line > TSA.SERVICE,

 Set BNK/AA.SIMULATION.SERVICE to START
 Set TSM to START
 Run the SERVICE
 Log in to Putty
 Type START.TSM –DEBUG
 Check tSA ‘**’ number for BNK/AA/SIMULATION.SERVICE
 If the agents are already running, type –CLEAR.FILE F.TSA.STATUS
 Log in to another putty session

 Type tSA **
 BNK/AA/SIMULATION.SERVICE is manually launched
Workshop – 34 – Simulation of an Arrangement
Arrangements > Product Catalog > Product Groups > Term Deposits >
AA Deposits > Long Term Deposit
 Simulate an arrangement for your customer effective today
 Deposit amount USD 1,00,000 for 1 year
Arrangements > Arrangements > New Arrangement Offers
 Open your simulated arrangement, view arrangement conditions and
Schedule
 Convert the simulated arrangement to a live one through ‘Execute’
Arrangements - Deposit Arrangements > Authorised
 View the live arrangement and authorise
Workshop – 35– Deposit Funding
Arrangements > Arrangement Activities (FT) > AA Deposit - Fund
 Select the arrangement opened in the previous workshop
 Deposit USD 5,00,000
 Approve Overrides
 View the activity log, financial summary and payment schedule of

deposit arrangement
Workshop - 36
 Pick the same deposit arrangement created through simulation
 Customer desires to know pre-closure amount on a future date
 Payout date – 3 months from arrangement start date
 View the simulated preclosure

 Activity Log
 Bills
 Payment schedule
Workshop – 37– Primary Customer Change
 Use User Menu > Retail Operations > Deposits –Deposit

Arrangements >Deposit Arrangements
 Select an Arrangement record of your customer created earlier and Change
the existing Primary Owner of the arrangement with different customer
Workshop - 38 - Creation of Securities Portfolio
 Use User Menu > Private Operations > Securities>Front Office>Client

Maintenance>Private Customer>Choose Customer Securities Data
• Include individual customer created earlier as an investor of securities
 Use User Menu > Private Operations > Securities>Front Office>Client

Maintenance>Private Customer>Choose Securities Portfolio
 Create the portfolio for your customer as under
 Currency : USD
 Choose any desired values for Portfolio Program and Management
Account from the dropdown list
 Use a suitable account name for the portfolio
 Use USD account of your customer as Account No. and Safekeeping
Account
Workshop -39 - ENQ SC.VAL.COST
 Use User Menu > Credit Operations > Retail Lending – Arrangements >
Product Catalog > Term Deposits >AA Deposits > Long Term Deposit
 Input an Arrangement for USD 300,000 for 1 years for your individual
customer
 Now mention the Portfolio ID created for the customer in the Portfolio ID of
the Account property in the Arrangement
 Commit and accept overrides, if any
 Get the record authorised.
 Go to the Command line and type ENQ SC.VAL.COST and key in the
Portfolio ID mentioned in the Arrangement and view the Deposit
Arrangement included in your portfolio.
AA Advanced Accounting
AA Accounting –overview
Arrangement Accounting
Activity Events
Accounting
Property Action
Product
Condition Financial
Reporting
Balance 1
Allocation
Balance 2 Rules SPEC.ENTRY
Balance ‘n’
STMT.ENTRY
Update CATEG.ENTRY
Balances
Arrangement Balances - Overview
 Some Properties of an Arrangement have one or more associated

Balances
 A property can have Balances in different states depending on status
 Some activities update Balances

 Balances are updated through T24 accounting
 Balances are used

 In financial reporting
 As the basis for calculation of interest or charges
 For applying certain types of periodic restriction
AC.BALANCE.TYPE
 Balance Type is a Financial Component of a Product

 Definition of Product specifies which balance types the Product should be
comprised of
 Reporting Type
 Contingent, Non-contingent and Internal
 Balance types are hard coded in T24
 AC.BALANCE.TYPE application offers ability to create additional

balance types and define relevant characteristics
 Decompose Balance Types
 Post or suppress entries for Internal Balance Types
 Post to Internal Balance Type
 Existing Balance types used by the system cannot be changed via
AC.BALANCE.TYPE application
Balance Prefix
Possible Prefixes for

Deposit Product Line:
CUR = Current Balance
TERM.AMOUNT, ACCOUNT
ACC = Current Accrued

Balance
INTEREST, CHARGE
DUE = Due Balance

ACCOUNT, CHARGE
AGE = Overdue Balance

ACCOUNT
UNC = Unallocated Credit

ACCOUNT
UND = Unallocated Debit

ACCOUNT
EXP = Expected Balance

ACCOUNT
PAY = Payable Balance

ACCOUNT, INTEREST, CHARGE
AC.BALANCE.TYPE
 Balance Types
 Contingent
Reported as Contingent - Off-Balance Sheet Item
 Non-Contingent
Reported in Balance Sheet
 Internal
Not to be used for Reporting
 Virtual
Summation of specified balances
Used for calculation purposes
 Activity Update
 Option to update dated historical balance file
(ACCT.ACTIVITY)
 Suspend Balance
 Option to suspend posting to PL
Workshop - 40
Arrangements > Product Catalog > Product Groups > Term Deposits >
AA Deposits > Fixed Floating Deposit
 Create a new Arrangement and get it authorised. While authorising note
down the AA Account Number
 Use Command Line

 Look at EB.CONTRACT.BALANCES, ACCT.BALANCE.ACTIVITY, account
record and Arrangement Balances
Arrangements > Arrangement Activities (FT) > AA Deposit - Fund
 Deposit commitment amount using FT and get it authorised
 Use Command Line

 Look at the account record, ACCT.BALANCE.ACTIVITY,
EB.CONTRACT.BALANCES and Arrangement Balances
Linking Balances to Calculations
 Interest and Charge properties can base their calculations on specific

balances
 This can include virtual balances
 And can include ‘memo’ balances
 Provides a variety of calculation options

Linking Balances to Calculations
 Specify Properties and Balances linked for calculations in

CALCULATION.SOURCE Tab in Product (AA.PRODUCT.DESIGNER)
Set Calculation property , Source Balance and Source Type
Link to AC.BALANCE.TYPE is made through Source Balance

Quiz 7
1. Balance prefixes are indicated in ACCOUNTING Property Class

a) True
b) False
2. Virtual Balance is the sum of selected balances

a) True
b) False
3. Balance Prefixes in AA Deposits are user definable

a) True
b) False
 This application holds information on actions performed in each

PROPERTY CLASS
 The information covers:

 Actions for each PROPERTY CLASS
 Accounting entry generated or not for the action
 Product Line
Activities Overview
 Activities are operations that can be applied to Arrangements

 Example : Deposit, Apply Payment, Accrue Interest
 Arrangements can only be updated via Activity (both online and COB)
 In fact, creating a new Arrangement is also an activity
 Activities are grouped into Activity Classes

 Defined by Temenos
 Activity Class defines behaviour
Activity Class Actions- DEPOSIT-CHANGE-INTEREST
Update Interest
Evaluate Activity Restriction
Calculate Activity Charges
Send Message Activity Messaging
Evaluate Alerts
Actions Property Classes
Slide 257
Activity - DEPOSIT-CHANGE-DEPOSITINT
Update DepositInt
Evaluate Activity Restriction
Calculate Activity Charge
Send Message Activity Messaging
Evaluate Alerts
Actions Properties
Slide 258
Accounting Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting

Accounting - Property Class
 Property for Accounting cannot be viewed or edited at arrangement

level
 Update Action possible.

 Will not generate Accounting entry
Property Class
Type for
DATED, MERGE, TRACKING.ONLY ACCOUNTING
Accounting – Product Condition
 Rules defined for every property requiring accounting entries

 Allocation rules defined for each action of property
 ACCT.ACTION Field - Accounting Action

 Action of respective properties for which rules are defined
 Must be ACTION having ACCOUNTING stated to YES in
AA.PROPERTY.CLASS
 ACCT.RULE Field - Allocation Rule

 Accounting rule associated with property and accounting action
 Must be a valid record in AC.ALLOCATION.RULE
 PROPERTY Field
 Indicates the Property to which following accounting rules apply
Accounting – Product Condition
 Charges / commission taken can be amortised over a period specified

in Accounting property
 Accrue Amort
 This should be set as AMORT
 Accrue Period
 Should be set as MATURITY or a valid period to be defined (1M, 1Y)
Accounting Balances and Data
Current balances
ARRANGEMENT EB CONTRACT
ID: Arrangement No.
BALANCES
1 ID: AA Account ID
Arrangement
Master
Current balance amounts STMT.ENTRY
Account No = Arr A/c
Balance Type = Multi Bal Type
1
ACCT
ACCTACTIVITY
ACTIVITY
ACCOUNT ID: Contract/Account
ACCT.BALANCE.ACTIVITY
ID: Contract/Account
[.balance] - YearMonth
ID: Contract/Account
ID: Account [.balance] - YearMonth
* [.balance] - YearMonth CATEG.ENTRY
Hist Balance and mvmt
Working Balance Hist Balance and mvmt Account No = Arr A/c
Hist Balance
By value dateand mvmt
By value date Profit and Loss Movement
By value date
Link to T24 apps
Crf Key Data
Historic Balances Accounting Entries
Interest Calc
SPEC.ENTRY
Deal No = Arr A/c
CRF Type = Multi Bal Type
Workshop - 41
 Use Admin Menu > Product Builder > Property Classes and Properties
> CHARGE
 Create a new Property for CHARGE Property class
Workshop - 41
Workshop - 42
 Use Admin Menu > Product Builder > Accounting > Balance Types
 Create new balance types with prefixes ACC, PAY, DUE for your new
CHARGE property created earlier
 Use Admin Menu > Product Builder > Accounting > Allocation Rules
 Create a new Allocation Rule for the new CHARGE property (You can copy
Accounting Allocation Rule “DEBIT-CHARGE” and change the P&L
Category retaining other details)
 Use Admin Menu > Product Builder > Product Conditions > Accounting
 Create a new Product Condition and assign the above rule to your
CHARGE property (Copy the existing Product condition and replace the
new allocation rule to your CHARGE property)
Workshop - 43
 Use Admin Menu > Product Builder > Products > Deposits
 Open your Product Group
 Add your CHARGE property to Charge Property Class
 Rebuild the Product Group
 Use Admin Menu > Product Builder > Products > Deposits > Your
Product Group
 Open your Product, add a product condition to your CHARGE property
 Replace the existing product condition for ACCOUNTING Property with the
new one you have created
 Proof and publish the product
Balance Maintenance Property Class
Payment
Customer
Schedule
Account Closure
Deposits
Activity
Officers
Restriction
Tax Accounting
Activity Activity Activity Balance

Presentation Mapping Charges Maintenance
Balance Maintenance - Property Class
 Property class allows to capture bills, balances and adjust balances of

bills taken over from contracts
 Contracts can be taken over from existing legacy system or existing T24
Deposit modules into AA module

Property
Class for
Type BALANCE.
DATED, NON.TRACKING, CCY,
MULTIPLE, ARRANGEMENT MAINTENANCE
Balance Maintenance – Product Condition
 Capture Bill
 Capture Balance
 Adjust Bill
 Adjust Balance
 Write Off Bill
 Write Off Balance

Balance Maintenance – Capture Bill
 Allows a single bill to be captured for an arrangement

 Total OS Amount
 Amount OS by property
 Original Amounts
 Bill Date
 Due Date
 Dates are before start date of arrangement in T24
 Amounts are made due and then will be aged by processing as part of
the same activity
 Other ‘side’ of movement is handled by allocation rules – usually

suspense or wash account
Balance Maintenance – Capture Balance
 Allows non bill related balances to be captured for an arrangement
 For example accrued interest, charges
 Dates are before start date of arrangement in T24
 Other ‘side’ of movement is handled by allocation rules

Balance Maintenance – ADJUST BILL
 Allows existing bill amounts to be adjusted

 Amounts can be increased or decreased
 Can be adjusted to zero
 Multiple Bills can be adjusted in the same transaction
 Balance Maintenance property will show balances as per the effective

date of the adjustment activity

 Net movement between bills can be zero
Balance Maintenance – ADJUST BALANCE
 Allows existing non bill related balances to be adjusted

 Amounts can be increased or decreased
 Can be adjusted to zero
 Multiple Balances can be adjusted in the same transaction


 Net movement between bills can be zero
Balance Maintenance – Write off Bill
 It is an ADJUST BILL activity
 Allows existing bills to be written off

 Amounts are automatically set to zero
 Bill status set to written off
 Multiple Bills can be written off in the same transaction


Balance Maintenance – Write off Balance
 Allows existing non bill related balances be written off

 Selected Balances are decreased to zero
 Multiple Balances can be written off in the same transaction


Balance Maintenance – ADJUST ALL
 Allows adjustment of bills and non bills related balances in the same
transaction
 Balances and amounts can be increased and decreased
 Combination of Adjust Bill and Adjust Balance
 Bills can be written off
 Amounts can be written off

 Net effect of adjustment can be zero
Balance Maintenance – Others
Typical sequence of steps involved in migration:
 Take-over Arrangement
 Capture outstanding Principal
 Capture overdue Bills
 Capture current accruals

Balance Maintenance Activities
Take Over Activities – Capture Bills and Balances

Direct Financial Adjustments
Enquiries
 Built in enquiries within Arrangement record
 Balance
Commitment amount, Current principal, pending charges, unspecified
credit, unspecified debits, etc
 Activity log
Displays all activities executed in date and sequence
Provides access to the Arrangement Activity record to view activity details
Basis for reverse and replay processing and shows corrected activities
 Bills
Due date, activity type, bill amount, outstanding, status - whether due or
settled
Enquiries
 Built in enquiries within Arrangement record
 Messages
Messages relating to activities
 Payment Schedule
Scheduled date, amount, outstanding principal, interest and total etc
 Account Details
Maturity date depending on term
Workshop - 44
Arrangements > Authorised Arrangements
 Select the arrangement opened for your customer
 Look at the following through the respective enquiry tabs
Balances
Activity Log, drill down to view an activity
Bills and drill down a bill to look into the details
Payment Schedule and open two records and see the contents
Summary
 You have learnt about :

 Deposits Product Line and Property Classes
 Setting parameter tables, creating Property and Product conditions for
Deposits Product Line
 Creating Deposits Product Group and Product, proofing and publishing the
product
 Deposit activities, Simulation, Reverse and Replay
 Balance Types and move balances
 Accounting flow in AA
 Using enquiries relevant to this module
Thank You
TEMENOS EDUCATION CENTRE

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

T3TAAD - Arrangement Architecture - Deposits - R11.1

Uploaded by

Copyright:

Available Formats

T3TAAD - Arrangement Architecture - Deposits - R11.1

Uploaded by

Document Information

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

T3TAAD - Arrangement Architecture - Deposits - R11.1

Uploaded by

Copyright:

Available Formats

T3TAAD – Arrangement Architecture

 Introducing participants to Deposits Product Line and Property Classes

 Learning to set parameter tables, create Property and Product

 Learning to create Deposits Product Group and Product, proof and

 Learning about Deposits activities, Simulation

 Learning use of enquiries relevant to this module

 AA also uses other Static tables

Bid rate is used

Possible to indicate Countries and Regions in BUS.DAY.CENTRES Field in

 Different Interest day basis for calculation of interest possible

 Tables used for building re-usable components :

 Tables set up during implementation:

 Released by TEMENOS to define Actions and Attributes for any

CUR, ACC, DUE, AGE, EXP,

 Property is a named type / instance of a Property Class

Property can suspend income. Applicable SUSPEND

Property can suspend overdue incomes SUSPEND

 To be defined for every Property class, by associating Id of the

 Possible to create different Product Conditions for a Property Class

 Fields of a Product condition represent attributes of the associated

 Product conditions have to be Date specific if Property class is set so

 Can be currency specific if the corresponding Property Class allows it

 Currency and Effective Date form part of Product condition Id

 Possible to set conditions with future value date also

Attributes controlled by TYPE

NR.ATTRIBUTE NR.OPTIONS NR.TYPE NR.VALUE NR.MESSAGE

Usual term : 5 years. Can be negotiated,

 This application holds information on actions performed in each

 The information covers:

Term Amount Interest Charge Payment Rules

Activity Activity Activity Periodic

Term Amount Interest Charge Payment Rules

Activity Activity Activity Periodic

 Customer Property class is mandatory

Balance Prefix - Null

 Product conditions can be set regarding Owner, Primary Owner, Other

Arrangement Other Party

 Customer entered into New Arrangement Activity

 Primary owner can be changed:

 Limit sanctioned to Primary owner alone can be used in Arrangement

Term Amount Interest Charge Payment Rules

Activity Activity Activity Periodic

 ACCOUNT Property Class is Dated

DEPOSITS – CUR, DUE, AGE, UNC, UND, EXP, PAY

 Account Title, Short Title and Mnemonic

 Base Date Type

 Securities valuation enquiry

 Bus Day Centres

 Account is required for all financial Arrangements

 Allows changes to the following Account attributes:

Term Amount Interest Charge Payment Rules

Activity Activity Activity Periodic

 Property for Officers can be set as Tracking

 Update Action possible. Values in fields can be updated at

Both of above must be a valid Officer in DEPT.ACCT.OFFICER file

 Roles for Other Officers

 Notes for Other Officers

 Default value is Account Officer defined in CUSTOMER record

Term Amount Interest Charge Payment Rules

Activity Activity Activity Periodic