Arrangement Architecture - Accounts - TM - R15

T24 Retail Accounts
TECHMILL TRAINING
Objectives – Retail Accounts
In this course, you will be introduced to Retail Accounts with the mention of some
basic and important Property Classes
After completing this learning unit, you will be able to:
 Understand the product overview of T24 Accounts and Retail Accounts
 Identify Application specific parameter tables for designing a Retail Account

product
 Configure a Retail Account Product
 Perform user activities and transactions related to the Product

Account - Product Overview
Slide 3
Account Features
Accounts
Credit Debit
balance balance
Interest Charges Charges Interest

expenditure income income income
Fixed Floating Fixed Floating
Statement Passbook
Cheque
book
Closure
Slide 4
Arrangement Accounts
Slide 5
Arrangement Accounts – Product overview
Eligible
Negotiable
products /
Default product
Non
Negotiable
Arrangement
Conditions
Arrangement
Account
Product
Tracking
Conditions
Arrangement
Account
Non Tracking
Limit Credit Debit

Balance Balance
Eligibility
Interest Interest
expense Income
Arrangement
Account
Charge Charge
Income Income
Slide 6
Arrangement Accounts
Application specific Parameters
Slide 7
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
8
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.CLASS (User Defined)
AA.PERIODIC.ATTRIBUTE
AA.SOURCE.CALC.TYPE
These could be used across several products
9
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 ,
TRACKING.ONLY, ARRANGEMENT, TRIGGER, Product Line Balance
VARIATION Prefix
ACCOUNTS, DEPOSITS,
INTERNET.SERVICES, LENDING,
PROXY.SERVICES,
PRODUCT.BUNDLE, RELATIONSHIP
PRICING, OTHER Pre-fixes for Balance types controlled by
BALANCE.PREFIX Field
CUR, ACC, DUE, AGE, EXP, UND,

PAY, UNC, TOT
Slide 10
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
PRODUCT ONLY FORWARD.DATED

Details defined at Product level cannot be Future dated properties appear alongside
viewed or amended at Arrangement Level current condition as multiple tabs for
negotiation at a later date
SUSPEND RESIDUAL ACCRUAL

Property can suspend income. Applicable Property When interest accrued is greater than
for INTEREST and CHARGE properties Type amount made due, excess amount moved
to RES<INTEREST>
SUSPEND OVERDUES
Property can suspend overdue incomes
Option possible only if SUSPEND also ACCRUAL.BY.BILLS
opted Null Accrues the penalty interest and allocates
it proportionally to each bill based on
calculation balance
CREDIT
Property (Charge) is payable to customer
Slide 11
AA.PRD.DES.<Property Class>
 To be defined for every Property class, by associating Id of the

respective Property class
 AA.PRD.DES.ACCOUNT, AA.PRD.DES.INTEREST
 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
Category condition for
Account
Posting
Restrict Currency
Slide 12
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-PHP-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
Slide 13
 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
Slide 14
Arrangement Accounts Property
Classes, Properties and Product
Conditions
Slide 15
OFFICERS Property Class
Charge Eligibility
Customer Payment
Schedule
Closure
Activity
Account Restriction
Accounting
Tax
Activity Activity Activity Balance

Presentation Mapping Charges Availability
Slide 16
Officers - Property Class
 Property for Officers can be set as Tracking
 Update Action possible

 Will not generate Accounting entry
Property
Class
OFFICERS
Attributes:
Balance Prefix
DATED, TRACKING, NIL
VARIATION
Slide 17
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
Slide 18
Workshop - Creating a new Officers Product Condition
 Use Admin Menu > Product Builder > Product Conditions > OFFICERS
 Create a new Product Condition
 Set the following rules :
For Other Officer Use codes “20 “ and “21” and role as “Application”
and “Approval” respectively
 Set DEFAULT.NEGOTIABLE to Yes
Slide 19
Solution - Creating a new Officers Product Condition
Slide 20
ACTIVITY.MAPPING Property Class
Charge Eligibility
Customer Payment
Schedule
Closure
Activity
Account Restriction
Accounting
Tax
Activity Activity Balance

Officers
Presentation Charges Availability
Slide 21
Activity Mapping - Property Class
 Values cannot be viewed or edited at arrangement level
 Arrangement level values track changes to Product condition
Property Class
ACTIVITY.MAPPING
Attributes:
Balance Prefix
DATED, MERGE NIL
TRACKING.ONLY
Slide 22
Activity Mapping – Links
 Transaction Type
AC
 Maps to Transaction Code
 Using FT.TXN.TYPE.CONDITION
FT.TXN.TYPE.CONDITION
 Which maps to Activity

 Using AA Activity Mapping 258
213
 Similar mappings for Activity Mapping

 AC.CASH.POOL
(AC.SWEEP.TYPE) and TELLER
(TELLER.TRANSACTION) ACCOUNTS-CREDIT-ARRANGEMENT
ACCOUNTS-DEBIT-ARRANGEMENT
Slide 23
Activity Mapping - Product Condition
 Transaction
 Payments and withdrawals in Account 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
Slide 24
Workshop – Creating Activity Mapping Product
Condition
 Use Admin Menu > Product Builder > Product Conditions >
ACTIVITY.MAPPING
 Map Transaction Code 213 to ACCOUNTS-DEBIT-ARRANGEMENT
activity
 Map Transaction Code 258 to ACCOUNTS-CREDIT-ARRANGEMENT
activity
 Set ACCOUNTS-CREDIT-ARRANGEMENT activity to Default Credit
 Set ACCOUNTS-DEBIT-ARRANGEMENT activity to Default Debit
 Set DEFAULT.NEGOTIABLE to NO
 Commit the record
Slide 25
Solution - Creating Activity Mapping Product Condition
Slide 26
Quiz – Answer the following
1. Accounts Arrangements include Customer Accounts, Internal Accounts,

contingent accounts as also Nostro and Vostro accounts
a) True
b) False
2. Eligibility conditions help in creating different Product Catalogues for

different customers
a) True
b) False
3. It is possible to Issue / Manage cheques, cards, statements, passbook,

notice accounts through Arrangement Overview
a) True
b) False
Slide 27
Accounts
Slide 28
Arrangement References
 Arrangement Number
 Definitive, Unique reference of the Arrangement
 Account Number
 Is typically the reference number given to the Customer (i.e., Cheque Book)
 Internally, is also the GL reference of the Arrangement
 Structure and validation configured in COMPANY
 Alternate Account numbers

 External/Alternate references to the Account component of the arrangement
i.e., Legacy Reference, IBAN etc.
 Structure and validation configured in ALT.ACCT.PARAMETER
 AA.ARRANGEMENT.ACTIVITY Reference
 Key to an “Activity” done on an arrangement.
Slide 29
ALT.ACCT.PARAMETER
 Possible to reference T24 account numbers through alternate account

numbers also
 ALT.ACCT.PARAMETER Table should be set up to indicate conditions for

check digit and size of alternate account numbers
 In ACCOUNT.PARAMETER, ALTERNATE.ACC.IDS Field to be set as Y

and ALTERNATE.ID Field to be used to indicate access identifiers defined
in ALT.ACCT.PARAMETER
 Alternate account number should be loaded into ALT.ACCT.ID Field in

individual accounts
 System automatically maintains the old and corresponding new numbers in

ALTERNATE.ACCOUNT file
Slide 30
ALT.ACCT.PARAMETER settings
Slide 31
Account Maintenance - Inactive Flag & Reset Inactive
Flag
 Inactive marking in account
 When an account remains inactive without any debit/credit transactions

from Customer side, treated as in active, Entries accepted after overrides
 Period in months for deciding inactivity defined in INACTIVITY.MONTHS

Field in COMPANY table
 System updates INACTIV.MARKER Field as Y in Account accordingly
 Marker can only be reset through ACCT.INACTIVE.RESET application

 Id is Inactive Account number
Slide 32
Account - Property Class
 ACCOUNT Property Class is Dated

 CUR, UNC, UND are the allowed Balance Prefix
Property
Class
ACCOUNT
Attributes: Balance Prefix

CUR, UNC,
DATED UND
Slide 33
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
 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
Slide 34
 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
Slide 35
 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
 Anniversary
 Stores the Anniversary Date of the arrangement
Slide 36
Account – Other features
 REFERAL
 Must be an existing code in REFERAL table
 Account details / details of entries referred in EOD report
 INACTIVE MONTHS
 Period in months for deciding inactivity
 Can be set as negotiable at arrangement level
Slide 37
Account – Passbook
 PASSBOOK
 To be set as ‘Y’ if passbook issue is desired
 Possible to change value from ‘Y’ to ‘No’ through UPDATE activity
Slide 38
Account – Other features
 Account is required for all financial Arrangements

 Holds the Principal balance of the Arrangement
 Origination Reference
 Possible to indicate external reference identifier
 Customer Reference, Account Reference
 Allows changes to the following Account attributes:

 Account Title
 Short Title
 Posting Restriction
 Mnemonic
Slide 39
Workshop – Creating a Referal condition
 Using the command line, create a REFERAL condition to refer

accounts with debit balance of / equivalent to PHP 50,000 and above
 These balances are due to movements of the day
 Get the record authorised
Slide 40
Solution - Creating a Referal condition
Slide 41
Workshop – Creating a new Account product condition
 Use Admin Menu > Product Builder > Product Conditions > ACCOUNT
 Set the following rules:
Use Category Code 6001
Set Base Date Type to AGREEMENT
Fill in ACCOUNT.TITLE and SHORT.TITLE Fields with title names you
desire
CATEGORY must be NON-NEGOTIABLE
Use the Referral code created in the earlier w/s
All other attributes, by default are Negotiable
Slide 42
Solution - Creating a new Account product condition
Slide 43
1. It is possible to capture alternate account numbers, by mapping them to

Account records and defining them in Availability product condition
a) True
b) False
2. When an Accounts arrangement has a posting restriction ‘Post no

credit’ defined, no interest credits will be posted to the account
a) True
b) False
Slide 44
Balances and Availability
Slide 45
Account Maintenance - Lock Funds
 It is possible to block funds in an account with start and end dates for
blocking using AC.LOCKED.EVENTS application
 Details of locking automatically maintained in accounts as date wise ladder

in FROM.DATE and LOCKED.AMOUNT Fields
 LOCKED.WITH LIMIT Field in ACCOUNT.PARAMETER and ACCOUNT

 To check Limit on an account in the Locked amount checking
 Default value is NO to ignore limit for locked amount processing
 When this field is set at both levels, account goes by the lowest level
definition
Slide 46
Account Maintenance - Lock Funds
 Locked amount check can be done on current balance or Available

balance
 For shortfall, Overrides raised are different for current balance with
limit, without limit and future cash flows
 Override ‘ACCT.BAL.LT.LOCKED’ is raised for an account with no limit for
locked amount checking ‘LIMIT.WORKING.LT.LOCKED ‘ is raised for an
account with limit
 If future cash flows are checked with out limit and if the available date is
less than the worst locked amount, Override
‘AVAIL.LOCKED.OVERDRAFT’ is raised
 If future cash flows are checked with limit and if the available date is less
that the worst locked amount, Override
‘AVAIL.LOCKED.LIMIT.OVERDRAFT’ is raised
Slide 47
Account Balances
 AA Balances
 CURBALANCE – Ledger Balance (EB.CONTRACT.BALANCES)
 Online Cleared balance

 Values of all authorised entries over the Account
 Except any credit or reversal debit entries with future exposure dates
 Working balance
 Value of cleared balance and unauthorised debit entries. Useful for limits
 Online Actual balance

 Online cleared balance and credit entries with future exposure date
 Available balance
 Maintained as a ladder to show date wise cash flow in an account, includes
Forward dated entries produced by contract applications and STO
Slide 48
Balances
49
AA.SOURCE.CALC.TYPE
 Source calculation Types:
DAILY – Value dated balance, not supported for Charge
AVERAGE – Average balance over the Interest / Charge period
HIGHEST – Highest absolute balance over the Interest / Charge period
LOWEST – Lowest absolute balance over the Interest / Charge period
50
AA.SOURCE.CALC.TYPE
 MONTHLY
 Applicable only for Interest
 Calculated balance for each month, not supported for Charge
 MONTHLY Options:
 Average Monthly – similar to average, average balance split by month
 Highest Monthly – similar to highest, highest balance split by month
 Lowest Monthly – similar to lowest, lowest balance split by month
 PROPERTY
 Based on Property, calculated on highest / lowest / average / daily balances
 TXN.AMOUNT
 Based on Activity, calculated on transaction amount
Slide 51
Balance Availability Property Class
Charge Eligibility
Customer Payment
Schedule
Closure
Activity
Officers Restriction
Accounting
Tax
Activity Activity Activity Balance

Presentation Mapping Charges Availability
Slide 52
Balance Availability Property Class
 Balance Availability Property Class is Dated and Tracking
 Can define settings for available balance updates and credit check
 Can setup Notice conditions
Property Class
BALANCE.
AVAILABILITY

NIL
DATED, TRACKING
Slide 53
BALANCE.AVAILABILITY Property Class
 Fills in for ACCT.GROUP.CONDITION on the following aspects

 Notice Accounts
 Credit Check
 Available Balance Update at Product level
 Field NOTICE.WITHDRAWAL to record advance notice from Customer
54
Balance Availability – Notice Withdrawal
 Possible to set up Notice Savings accounts in which withdrawals above

specified amounts need agreed notice periods
 NOTICE.AMOUNT Field to indicate maximum local currency amount

that can be drawn without notice
 NOTICE.PERIOD Field specified in days, weeks, months or year
 NOTICE.AVAILABILITY Field specify the period for which funds will be

kept available after the notice period - in days, weeks, months
 E.g. Notice of 1 month after which funds will be kept available only for 5
working days. If amount is not drawn within this period, fresh notice is
required to be given
 Notice of withdrawal recorded through NOTICE.WITHDRAWAL
Slide 55
Balance Availability – Available Balance
 Through CREDIT.CHECK Field, Available balance or Working balance

could be set to be checked for overdraft or limit checking
 Available holds unauthorised and authorised transactions
 Working ignores unauthorised credits and future authorised credits
 Available Balance update field

 Any unauthorised entry to be included in Available balance
 Debits, Credits, Both and None are choices
Slide 56
Account – Locking of funds
 It is possible to block funds in an account with start and end dates

using AC.LOCKED.EVENTS application
 Details of locking maintained in accounts as date wise ladder in

FROM.DATE and LOCKED.AMOUNT Fields
 LOCKED.WITH.LIMIT Field in ACCOUNT

 If marked as Yes, credit checking on Locked amounts will include Limit
if account has locked funds and is linked to a Limit
 Default value is NO, ignores limit for locked amount processing
 Enquiry of locked amount available in Arrangement Overview
Slide 57
Workshop – Balance Availability, Notice Settings
BALANCE.AVAILABILITY
 Set the following rules:
Notice amount is 50000
Notice period required is 3 days
Balance kept available for 2 days
Credit check to be made on available balance for both debits and credits
All other attributes, by default are Negotiable
Slide 58
Solution - Balance Availability, Notice Settings
Slide 59
Eligibility
Slide 60
Eligibility
 Eligibility requirements for products can apply to:

 Customer level products (e.g. Relationship Pricing or Internet Services)
 Traditional “financial” products (e.g. loans, accounts, deposits)
 Eligibility checking enables:

 Ability to specify eligibility criteria at the level of each product
 Ability to evaluate if a customer is eligible for a particular product
 Frequency of eligibility requirement checking:

 For some products, only once when the product is taken out
 Rechecked during the life of the arrangement
Customers who are no longer eligible (e.g. they are no longer resident)
may need to be moved to another product
61
Types of Eligibility
 Eligibility criteria defined at individual product level

 Based on customer characteristics / attributes
 Defined for a product in the product designer

 Returns an error / override if eligibility evaluation fails
 If no rules are defined, the product is available for all
 Types of eligibility:
 Customer must be less than 18 (student)
 Customer must be over 18, a local resident, full time employed
 Customer must be a corporate local resident
 Customer must be a foreigner (Non-resident)
 Customer’s salary must be above 2M PHP per annum
62
Establishing Eligibility
 Eligibility requirements typically revolve around customer information :

 Customer Type (e.g. Student, Staff, Resident, Non-Resident, Business)
 Relationship Value (e.g. their total business with the bank)
 Relationship Length (i.e. how long have they been a customer)
 Age
 Establishing eligibility
 Filter the Product Catalogue to show only the products that the customer is
eligible for
 Check the customer’s eligibility during “New Arrangement” activity
 Checking of eligibility requirement

 When the product is taken out
 When the primary customer changes
 When there is a product change
 Checked / Rechecked during the life of arrangement
63
Eligibility - Features
 Eligibility Review setup at the Product / Arrangement level

 Change in Customer static can trigger an Eligibility Review during the
following Close of Business
 Periodic evaluation
 Consequences of Eligibility Review Failure

 Change Product
 Ignore – this results in logging the failure on the arrangement
64
ELIGIBILITY Property Class
Charge Settlement
Balance
Availability
Account Closure
Officers Eligibility
Accounting
Tax
Activity Activity Activity Activity

Presentation Mapping Charges Restriction
Slide 65
Eligibility – Property
 Based on Eligibility conditions defined, eligibility of a customer for a

product is evaluated
 Product condition is Tracking and Date specific
Property
Class
ELIGIBILITY
Attributes:
Balance Prefix
VARIATION
66
Eligibility
 Replaces the current functionality provided by ACCT.GEN.CONDITION
 Customer provided a choice of eligible products, under SCV
 Eligibility definition updated through Product Designer
 Eligibility validated when:

 Creating a new arrangement
 Running an enquiry
 Eligibility review / update triggered by static change in customer
 Evaluate and change product to default product based on eligibility
Slide 67
Evaluate and Change product based on Eligibility
Slide 68
Eligibility product conditions
 Eligibility rules
 Rule applicable from Rules engine – multi value
 Eligibility Failure type – Error / override
 Review Failure Action – Change Product / Ignore
 Currency
 Currency specific rules, applicable from same Rules engine- multi value
 Ccy Eligibility failure type – Error / override
 Review Ccy failure action - Change Product / Ignore
 Periodic review
 Review frequency mandatory
 Static Review
Slide 69
Workshop – ELIGIBILITY Product Condition
ELIGIBILITY
 Opt for CUSTOMER.AGE.LT.18 rule and IS.LOCAL.RESIDENT rule from
the rules engine
 Both rules should throw an error if eligibility check fails
 Change Product is the option on review of eligibility for both
 Opt for static review
 Default product for Savings Account is SAVINGS.DEFAULT
Slide 70
Solution - Eligibility product condition
Slide 71
Interest
Slide 72
Features of Interest in AA Accounts
 Multiple Interest Properties

 Each interest component is represented by an Interest Property
 Interest Types
 Fixed interest
 Floating interest
 Negative interest rate possible on accounts in credit
 Interest Calculation
 Average, highest, lowest for a period
 Interim interest capitalisation possible
 Possible to specify a minimum interest amount to be charged
Slide 73
Features of Interest – Tiered Interest rates
 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
Slide 74
Interest Adjustments - Reverse & Replay
 ACTIVITY.TYPE in AA.ACTIVITY.CLASS determines activities that will

not trigger reverse / replay of processed activities
 NOREPLAY – Activity will not be reversed / replayed by any Activity
 NOREVERSE – Activity cannot be manually reversed by User
 NORR – Activity will not trigger reverse / replay of other activities
 Possible to adjust Interest through reverse and replay mechanism
Slide 75
Interest Property Class
Charge Eligibility
Customer Payment
Schedule
Account Closure
Activity
Accounting
Tax
Activity Activity Activity Periodic

Presentation Mapping Charges charges
Slide 76
Interest – Property Class
 Multiple Interest properties can be defined

 Interest property is tracking
Property
Class
INTEREST
Attributes:
Balance Prefix
DATED, CCY, MULTIPLE, ACC, DUE
TRACKING, PAY
FORWARD.DATED,
VARIATION
Slide 77
Interest – Product Condition
 Rate
 Fixed rate input directly
 Floating index – variable base rate tied to BASIC.INTEREST
 Margin Type
 Single / Multiple
 Margin Operand
 Add / Subtract from floating rate
 Margin Rate
 Spread
Slide 78
 Tier Maximum Rate

 Applicable for floating rate
 Specify a maximum rate for the tier
 Tier Minimum Rate

 Applicable for floating rate
 Specify a minimum rate for the tier
 Rate Tier Type

 Single – Single rate for entire balance amount
 Level – Interest at different rates, based on balance amount
 Band - Rate of each tier to be applied to the portion of the balance that falls
within the tier
Slide 79
 Tier Amount
 Relates to RATE.TIER.TYPE Field
 Amounts can be entered if either BAND or LEVEL selected
 Tier Percent
 Relates to RATE.TIER.TYPE Field
 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
Slide 80
 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
 Calculates accrued interest, posts amount using associated accounting rule
 Compounding
 DAILY, WEEKn, Mnn, TWMTH, Nnnn
Slide 81
 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 82
 Minimum Interest Amount

Minimum interest to be charged for an Arrangement
Compared with accrued amount, if less than minimum, waived / charged
 Waive Minimum Interest

If set as Yes, no amount charged, otherwise, minimum amount charged
 On Activity recalculate Rate

Interest can be set to reset on an Activity, in field Recalculate
System checks the rate table BI, retrieves a new rate
Slide 83
Interest – Other features
 ACCRUAL.BY.BILLS in Interest Property accrues the penalty interest

and allocates it proportionally to each bill based on calculation balance
 System also allows for repayment of penalty interest and adjustment

(i.e. waiving or reducing) of the penalty interest based on bill by bill
basis
Slide 84
Workshop – 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
Slide 85
Solution – Setting a fixed Interest rate
Slide 86
Workshop – Floating Interest settings
 Use Admin Menu > Product Builder > Product Conditions > INTEREST
 Create a new Product Condition for floating interest type
 Use BASIC.INTEREST Table 1
 A default margin of 0.5%, negotiable down 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
 Tier Type is SINGLE
 Negative interest effect due to margin not allowed
 Attributes are negotiable by default
Slide 87
Solution – Floating Interest rate settings
Slide 88
Charges
Slide 89
Charge and Activity Charges – Other features
 Activity Charges
 Charge applied when Activity is performed
 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
Slide 90
Charge – Other features - Scheduled Charges
Slide 91
Charge – Other features - Break Rule Charges
Slide 92
Activity Charges – other features
Slide 93
CHARGE and ACTIVITY CHARGES Property Classes
Charge Payment Rules
Customer Payment
Schedule
Account Closure
Activity
Accounting
Tax

Slide 94
Charge – Property Class
 Multiple Charge properties allowed
 Currency is optional
Property
Class
CHARGE
Attributes:
Balance Prefix
DATED, OPT.CCY, ACC, DUE
MULTIPLE, TRACKING,
FORWARD.DATED,
VARIATION
Slide 95
Charge – Product Condition
 Charge Type
 Fixed or Flat
Charge amount should be set
PHP 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
Slide 96
 Calculation Type
 Flat
Charge amount should be set - PHP 50; GBP 30, etc
Zero charge acceptable
 Percentage
Calculated on specified balances - 2% on Transaction amount
 Unit
Multiplication factor to arrive calculating charge - PHP 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
Slide 97
 User defined Charge Routine

 Can be added to Activity Restriction / Activity Charges product condition
 Useful when Banks desire different / complicated methods of charge
calculations
 Calculation Threshold
 Base amount below which charge amount will not be calculated
 Free Amount
 Deduction allowed on calculated charge
e.g. reduce PHP 10 from calculated charge
 Minimum Charge Amount

 Minimum Charge to be specified for an Arrangement
 Compared with computed charge amount, if less than minimum, waived /
charged
 Waive Minimum Charge

 If set as Yes, no amount charged, otherwise, minimum amount charged
Slide 98
Activity Charges – Property Class
 Define charge property when specific activities take place

 It is DATED, FORWARD.DATED and TRACKING type
Property
Class
ACTIVITY.
CHARGES
Attributes:
Balance Prefix
FORWARD.DATED,
VARIATION
Slide 99
Activity Charges – Product Condition
 Activity attracting charge

 Activity Id on which charge would be applied
 Any number of activities can be multi-valued, defined
 Charge Property
 Charge property triggered when activity is triggered
 Period
 Method
 Due
 Defer
 Capitalise
Slide 100
Activity Charges – Settlement related
 Settle Activity
 Repayment activity to be triggered when there is UNC
 Auto Settle
 Option Yes will fetch settlement account
 If option No, will not settle through settlement property
 Settlement of Activity Charges process:

 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
 Settle activity, a secondary activity, defined for settling from UNC
 Activity charges property designed to settle out of UNC first, if available
Slide 101
Workshop – Setting a fixed charge
 Use Admin Menu > Product Builder > Product Conditions > CHARGE
 Set the following rules
Fixed Charge of PHP 10
 All Attributes are negotiable by default
Slide 102
Solution – Setting a fixed charge
Slide 103
Workshop – Setting of a calculated charge
Charges in PHP
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
Slide 104
Solution – Setting of a calculated charge
Slide 105
Workshop – Setting up a mixed charge
Charges to be collected in PHP.
Flat Charge of 5 for transaction amount upto 500.
Flat Charge of 10 for transaction amount upto 5,000.
Additionally 0.20 % for transaction amount beyond 5,000 and upto 25,000
Additionally 0.10% for transaction amount over 25,000
All Attributes are not negotiable by default.
Slide 106
Solution – Setting up a mixed charge
Slide 107
Workshop – Setting up Activity Charges
ACTIVITY.CHARGES
1) Charge to be levied when an accounts arrangement is closed
The Charge Property is ACCHARGE
This Fee is to be capitalised on occurrence of activity
2) Charge to be levied during International ATM withdrawal
The Charge Property is TXNFEE
This fee is to be deferred
 All Attributes are not negotiable by default
Slide 108
Solution – Setting up an Activity charge
Slide 109
Charge Override Property Class
Customer Payment
Schedule
Account Closure
Activity
Accounting
Tax
Activity Activity Activity Charge

Presentation Mapping Charges Override
Slide 110
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
CHARGE.
OVERRIDE
Attributes:
Balance Prefix
DATED, TRIGGER, NON. NIL
TRACKING
Slide 111
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
 Waive Reason – Reason given by user for waiving charges

 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
 Fields relating to Actual and Waived charges can be viewed in

AA.CHARGE.DETAILS and AA.BILL.DETAILS
Slide 112
Charge Override – Product Condition
Fields relating to Actual and Waived charges can be viewed in

AA.CHARGE.DETAILS and AA.BILL.DETAILS
A new option is introduced in ACCOUNTING property to raise separate

accounting entries for calculated charge and waived amount, such that it
could be booked in separate profit and loss category.
Slide 113
Periodic Charges Property Class
Customer Payment
Schedule
Account Closure
Activity
Accounting
Tax

Slide 114
Periodic Charges – Property Class
 This property is dated
 Currency is optional
Property
Class
PERIODIC.
CHARGES
Attributes:
Balance Prefix
DATED, OPT.CCY, NIL
VARIATION
Slide 115
Periodic Charges features
 Equivalent to GENERAL CHARGE
 Possible to define individual charge properties and deferred activity

charges
 Overall Minimum / Maximum can be defined
 Can be waived unconditionally
 Can be waived based on Conditions
 Possible to waive based on Conditions and apply an alternate Charge
Slide 116
Types of Periodic Charges
 Various types of Periodic charges that can be levied
 Based on count of activities in a period

 Activity Id and charge property to be defined
 Charge fee based on activity count
 Source calculation type set as ‘COUNT’ in Product designer
 Based on highest balance in a period

 Charge fee can be fixed / calculated
 Source calculation type set as ‘DRMAXIMUM’ in Product designer
 Based on sum total of transaction amounts

 Charge fee can be a percentage on transaction amount
 Source calculation type set as ‘TXNAMOUNT’ in Product designer
Slide 117
Periodic Charges – Product Condition
 Currency
 Mandatory input
 Can be different from arrangement currency
 Can be multi-valued for minimum / maximum
 Minimum / Maximum
 Can be input currency wise
 Waive charge
 To be marked as Yes for total waiver
 Charge / Activity
 Charge property and activity to be defined
 Can be multi-valued
Slide 118
Periodic Charges – Product Condition
 DEFERRED CHARGE
 Activity charge / Rule break charge / Activity restriction charge
 APP.METHOD set to DEFER in respective properties
 Charge property that are deferred and to be made due can be multi-valued
 INC.ALL.DEF.CHGS
 Instead of defining the above field
 On the scheduled date whether all the deferred charges to be made due
 To be marked as Yes
 On scheduled date system clubs all deferred charges to raise a single bill
 Both attributes can be set either at product level or at arrangement level
 Record in AA.CHARGE.DETAILS created
Slide 119
Workshop - Setting up a Periodic Charge
PERIODIC.CHARGES
 Create a new Product Condition for collecting periodic charges
 Set the following:
Currency for charge is PHP
A minimum charge of 15 and a maximum charge of 65 to be set
Charge Property CHEQUEWD to be attached to activity ACCOUNTS-
ENCASHCHQ-ARRANGEMENT
(for this charge, input COUNT in source balance)
HIGHESTDEBIT to be defined for next charge property
(for this charge, input DRMAXIMUM in source balance)
Slide 120
Solution – Setting up a Periodic Charge
Slide 121
Quiz - Match the Following
1. Activity Charge a) ACCOUNTS-NEW-

ARRANGEMENT
2. Scheduled Charge b) Not Currency Dependent
3. Break Rule Charge c) Payment Schedule
4. Charge Property Class d) Currency dependent Optional
5. Activity Charge Property Class e) Periodic Rules
Slide 122
Payment Schedule, Settlement of
dues and Payment rules
Slide 123
PAYMENT.SCHEDULE Property Class
Charge Eligibility
Customer Payment
Schedule
Closure
Activity
Account Restriction
Accounting
Tax

Officers
Slide 124
Payment Schedule – Property Class
 Defines Rules for paying Interest, funding Principal and collecting

Charges for an Accounts product
 Product condition is Dated, Forward dated

and Currency specific
Property Class
PAYMENT.
SCHEDULE
Attributes:
Balance Prefix
DATED, CCY, NIL
FORWARD.DATED
Slide 125
Payment Schedule – Product Condition
 Payment Types:
 ACTUAL - Repayment of calculated property classes - Interest, charge
 Payment Methods :
 DUE - Amount is Due to or from customer
 CAPITALISE - Capitalise the amount
 PAY – Amount paid to customer
 Payment frequency
 Frequency at which payments will be made due
 Applicable for Payment Type
Slide 126
 Actual amount - for Adhoc 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
Slide 127
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)
Slide 128
 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
Slide 129
 Recalculation types
Payment – payment amount will be changed
Residual – residual amount will be changed
Nothing – payments and residual will be unchanged. Recalculation frequency

should be specified
Progressive Payment – Increase / decrease in calculated amount
Term – Term will be altered (not applicable for Accounts)
Slide 130
 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 10 th 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
Slide 131
Payment Schedule – Billing features
 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
 User can also specify amount of repayment

When amount is manually input, system will not calculate the amount
Slide 132
Workshop - Scheduling Quarterly Interest Payment and
Received
PAYMENT.SCHEDULE
 Interest payment to start from a day after the initial deposit is made
 Interest to be paid and received quarterly on the first Monday
 All attributes are negotiable
Slide 133
Solution – Scheduling Quarterly Interest Payment and
Received
Slide 134
Workshop - Scheduling Payment for Current Account
PAYMENT.SCHEDULE
 Create a new payment schedule Product Condition for Current accounts
 Interest to be set for payment semi-annually for credit interest and monthly
for debit interest
 Periodic charge – LEDGERFEE to be scheduled monthly
 Both interest and charge to be made due
 Bills must not be combined
Slide 135
Solution – Scheduling Payment for Current Account
Slide 136
Settlement of dues
Slide 137
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
Slide 138
Settlement – Activity Class – PAY-IN Activity
 PAYIN-ACTIVITY
 Activity to source the payment amount from Pay-in Account
 To be left blank if sourced from non-arrangement Account
 If sourced from Arrangement Account:
ACCOUNTS-DEBIT-ARRANGEMENT
DEPOSITS-APPLYPAYMENT-PO.DEPOSIT
 PAYIN-SETTLE-ACTIVITY
 Activity triggered to apply the payment received
 ACCOUNTS-APPLYPAYMENT-ACCOUNTS.PAYMENT.RULES
 DEPOSITS-APPLYPAYMENT-PR.DEPOSITS
 LENDING-APPLYPAYMENT-PR.REPAYMENT
139
Settlement – Activity Class – PAY-OUT Activity
 PAYOUT-ACTIVITY
 Activity triggered for applying payment in Pay-out Account
 To be left blank if paid into a non-arrangement Account
 If paid to an Arrangement Account:
ACCOUNTS-CREDIT-ARRANGEMENT
DEPOSITS-CREDIT-ARRANGEMENT
 PAYOUT-SETTLE-ACTIVITY
 Activity triggered to pay the property PAYBALANCE
 ACCOUNTS-APPLYPAYMENT-ACCOUNTS.PAYOUT
 DEPOSITS-APPLYPAYMENT-PO.DEPOSITS
140
SETTLEMENT Property Class
Charge Limit
Balance
Availability
Account Closure
Officers Eligibility
Accounting
Tax
Activity Activity Activity Activity

Presentation Mapping Charges Restriction
Slide 141
Settlement – Property
 Allows select settlement instructions for Deposits, Loans and

Arrangement accounts
 Links a mandate defined in the Direct Debit (DD) module to an

arrangement account
Property Class
SETTLEMENT

NIL
DATED
142
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
 Fetches Settlement Account corresponding to Payment Type in Payment
schedule
 Pay-In Activity
 Activity run to pay out funds when the receiver is an Arrangement
 Active – can be set as ‘No’ to:

 Stop a settlement instruction at arrangement level
Slide 143
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
 Repayment to a loan
 Making an Initial Deposit on an ACCOUNT product
 Payment of Interest / Charges
 Settlement for Activity Charges

 Grouped under payment type CHARGE
 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
Slide 144
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 – Debit Pay-In account with full bill amount, irrespective of funds
 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
Slide 145
Settlement Instructions – Pay Out
 Meant for payouts from an Arrangement
 Pay out examples:

 Pay-out of AA Deposit at maturity
 Interest Liquidation
 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
 Payout Activity
 Activity run when the receiver of funds is another arrangement
Slide 146
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
Slide 147
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
Slide 148
Workshop – Settlement instructions
SETTLEMENT
 Create a new Product Condition:
Payment Type Pay-in settle activity

Interest Only ACCOUNTS-APPLYPAYMENT-ACCOUNTS.PAYMENT.RULES
Charge ACCOUNTS-APPLYPAYMENT-ACCOUNTS.PAYMENT.RULES
Property Class Pay-out settle activity

Interest ACCOUNTS-APPLYPAYMENT-ACCOUNTS.PAYOUT
 Active to be marked as YES for all of the above
 Pay-in rule to be marked as Partial for Charge payment type
Slide 149
Solution – Settlement instructions
Slide 150
Payment Rules Property Class
Customer Payment
Schedule
Account Closure
Activity
Accounting
Tax

Slide 151
Payout Rules Property Class
Customer Payment
Schedule
Account Closure
Activity
Accounting
Tax
Activity Activity Activity

Payout Rules
Presentation Mapping Charges
Slide 152
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 Class
PAYMENT RULES
PAYOUT RULES
Attributes:
Balance Prefix
DATED, MULTIPLE, NIL
TRACKING
Slide 153
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
Slide 154
Payout Rules Definition
 Funds in UNCACCOUNT / CURACCOUNT can be withdrawn
 Payment application type can hold values: CURRENT.PAY, PAY and

DEPOSIT.RULE.PAY
Field Withdrawal from Withdrawal

CUR balance from UNC
balance
PROP.APPL.TYPE BALANCE BLANK
APPLICATION.TYPE CURRENT.PAY PAY
Slide 155
Workshop – PAYMENT RULES Setting
PAYMENT.RULES
 Choose Application Type as BILL.PROPERTY
 Earliest bills to be paid first
 Pay off Bills in the following order:
Properties : DRINTEREST
 Remainder Activity - ACCOUNTS-CREDIT-ARRANGEMENT
 Bills not to be processed before due date
Slide 156
Solution - PAYMENT RULES Setting
Slide 157
Workshop – PAYOUT RULES Setting
PAYOUT.RULES
 Choose Application Type as DEPOSIT.RULE.PAYOUT
 Pay off Bills by Property in the following order:
Properties : CRINTEREST
Earliest bills to be paid first
Slide 158
Solution – Payout rules setting
Slide 159
Periodic Attributes Rules
Slide 160
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
Slide 161
AA.PERIODIC.ATTRIBUTE.CLASS – User Defined
 Users can create periodic attribute

 Property Class whose condition uses the periodic rule
 Action to be performed on the property class. It is a multi value field
 Multiple comparison types from EB.COMPARISON.TYPE table
 Data Types – AMT, RATE, etc
 Value Routine - Should be valid entry in EB.API file. If no routine is input,

system triggers an error
 Type – Cap, Floor, Balance Type
 System Generated
 This field is left blank for a user defined periodic attribute class
 ‘Yes’ displayed if the periodic attribute class is released by Temenos

Workshop
 Use Admin Menu > Product Builder > Additional Settings > Periodic
Attributes
 Create a new Periodic Attribute Class
 In the Context tab, select the property class Payment Schedule
 Enter multiple actions Update, Make Due, Capitalise by using the multi
value
 In the Comparison tab, select multiple comparison types – minimum,
maximum, -tolerance, +tolerance
 Enter the routine AA.GET.ACTIVITY.VALUE in the ‘Value routine’ field
 Select the ‘Data.Type’ as ‘Amt’
 View the periodic attribute class created
Workshop Solution
2
3
4
 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 period or life time of PR.ATTR.
Arrangement. Is controlled by CLASS
PERIOD.TYPE Field PERIOD.
LIFE, INITIAL, REPEATING & ROLLING TYPE
Periodic
Attribute
PERIOD field controls exact period for PERIOD

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

Class

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

which 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
Slide 166
AA.PERIODIC.ATTRIBUTE – User Defined
 Periodic Attribute is a named type / instance of a Periodic Attribute Class


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

which Rule is defined
RULE.START Periodic
01D, 5M, 2Y,…
Attribute
RULE.START Field represents Base Date COMPARISON .TY
AGREEMENT, ANNIVERSARY, PE
ARRANGEMENT, COOLING-OFF & START ERROR /
OVERRIDE
TYPE
MESSAGE
COMAPRISON.TYPE to be selected from
predefined comparison types in periodic
attribute class
RULE.ERR.MSG and
RULE.OVE.MSG Fields control
Type should be a valid type defined in generation of ERROR and
periodic attribute class OVERRIDE messages
Periodic Rules - Structure
Slide 168
Workshop
Attributes
 Create a new Periodic Attribute ‘Actual Amount’ for the periodic attribute
class created in the previous workshop
 Give a suitable description
 Select the ‘Type’ as life
 Select the comparison type. Note that the comparison type selected should
have been defined in the user defined periodic attribute class
 Select the rule type as Agreement
 Commit the record. You have now created a periodic attribute for a user
defined periodic attribute class which can be used in the product
Workshop Solution
2
Periodic Attribute Class - Activity Restriction Property
Class
Transaction Amount & Count related:
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. amounts in 100s
TRANSACTION AMOUNT TOTAL - Periodic Rule to control Total

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

of Transactions, E.g. not more than 2 withdrawals in a year
Slide 171
Periodic Attribute Class - Activity Restriction Property
Class
Balance Related:
MAXIMUM BALANCE
 Restrict transaction by checking any balance type, specifying an amount
MAXIMUM BALANCE INCREASE

 Restrict increase in amount of balance type, specifying the difference
amount
MINIMUM BALANCE
 Restrict transaction by checking any balance type, specifying an amount
MINIMUM BALANCE INCREASE

 Restrict increase in amount of balance type, specifying the difference
amount
MINIMUM INITIAL BALANCE

 Restrict the initial transaction, specifying an amount
Slide 172
Periodic Attribute Class - Interest & Charge Property
Class
 MAXIMUM RATE - Rule for Maximum Interest Rate
 MINIMUM RATE - Rule for Minimum Interest Rate
 RATE DECREASE - Rule for Interest Rate Decrease
 RATE DECREASE TOLERANCE - Rule for Rate Decrease in %age
 RATE INCREASE - Rule for Interest Rate Increase
 RATE INCREASE TOLERANCE - Rule for Rate Increase in %age
 MAXIMUM CHARGE – Rule for Maximum Charge
 MINIMUM CHARGE – Rule for Minimum charge
Slide 173
Workshop - Periodic Attribute for decrease in Interest
Rate
Attributes > INTEREST Property Class
 Set a Periodic Attribute for decrease in Interest Rate during any 1 year
period. Rule to be applied with effect from start of arrangement
Slide 174
Solution – Periodic attribute for decrease in Interest
Rate
Slide 175
Workshop – Periodic attribute for Minimum Credit in an
Account
 Use MB Admin Menu > Product Builder > Additional Settings > Periodic
Attributes > Activity Restriction Property Class > Initial Balance >
Minimum Initial Balance
 Set a Periodic Attribute for Minimum Initial Credit for life of the Product.
Slide 176
Solution – Periodic attribute for Minimum Credit in an
Account
Slide 177
Activity Restrictions and Transaction
rules
Slide 178
Activity Restriction
 Complete restriction of Activity

 Activity cannot be run altogether
Not to allow change of Customer, Not to allow change of Product
Amount below Minimum Balance not accepted as initial deposit
 Error message is Mandatory
 Partial or conditional restriction

 Control activity but allow with an override
Allow more than 5 Debits in an Account in a year only after approving
override, Allow receipts in an Account only in multiples of 100
 Override message is Mandatory
 Periodic Rules
 Enables definition of rules with a time element
Slide 179
Activity Restriction Types
Slide 180
Activity Restriction – Scheduled Interest / Charge
related
 Possible to restrict activities related to scheduled Interest and Periodic

charge properties
 Property should have been defined in the Payment Schedule property
 Restrictions can be based on:

 Transaction count / transaction amount / balances
 When activity restriction rule is broken:

 Waive the Interest or Charge Property amount and apply an alternate
Interest or Charge Property
 Or apply the actual Interest amount ignoring any alternate Interest
 If the activity restriction rule is not broken:

 Waive the Interest or Charge Property amount and apply an alternate
Interest
 Or apply the actual Interest amount, ignore alternate Interest
Slide 181
ACTIVITY.RESTRICTION Property Class
Charge Eligibility
Customer Payment
Schedule
Closure
Activity
Account Mapping
Accounting
Tax

Officers
Slide 182
Activity Restriction – Property Class
 This Property Class allows Multiple Properties and is TRACKING type
 This Property is Product Only
 Currency and Date Specific

Property Class
ACTIVITY.
RESTRICTION
Attributes:
Balance Prefix
DATED, CCY, MULTIPLE,
NIL
TRACKING,
FORWARD.DATED,
VARIATION
Slide 183
Activity Restriction Property
Run
Rule
Run
Rule
Slide 184
Activity Restriction product condition – Rules tab
related
 Rule Name
 Any name as desired
 Any number of rules can be multi-valued
 Periodic Attribute
 Valid record from AA.PERIODIC.ATTRIBUTE
 Activity Class / Activity

 Activity class or activity to be restricted
 Balance
 Balance type on which rule should apply
 Value
 Actual value of the balance type
Slide 185
Activity Restriction product condition – Activity tab
related
 Activity Class / Activity

 Activity class or activity that needs to be restricted, can be multi-valued
 Run the rule – rule created in rules tab
 Break Result – can be error / override
 Override / Error message – appropriate message to be added
 Break rule charge – charge property for collecting charges when

periodic rule is broken
 App period - Periodic charges applied at the end of this period
 App method – Periodic charges made Due / capitalise / defer
Slide 186
Activity Restriction product condition – Property tab
related
 Property
 Interest / Charge properties defined in Payment Schedule
 Run the rule

 Rules created under rules tab
 Evaluation
 Break – Breaking the rule
 Satisfy – Satisfying the rule
 Evaluation Result
 Apply Interest / charge property amount
 Waive Interest / charge property amount
 Alternate Property
Slide 187
Workshop - Setting restrictions in Current Accounts
 Use Admin Menu > Product Builder > Additional Settings > Periodic Attributes
> ACTIVITY.RESTRICTION – TRANSACTION.COUNT.TOTAL > New
Condition
 Create a Periodic Attribute applicable for any one month period, in an Arrangement
to restrict total no. of transactions
 Use Admin Menu > Product Builder > Additional Settings > Periodic Attributes
> ACTIVITY.RESTRICTION – MINIMUM.BALANCE > New Condition
 Create a Periodic Attribute applicable for life of an Arrangement to restrict minimum
balance in the account
ACTIVITY.RESTRICTION
 Define a rule for maintaining minimum daily balance of 50 under periodic attribute
MINIMUM.BALANCE and for maximum cheque withdrawals of 5.
 LEDGERFEE charge is waived when both the previously defined rules are satisfied.
 All attributes are set as negotiable
Slide 188
Solution - Setting restrictions in Current Accounts
Slide 189
Solution - Setting restrictions in Current Accounts
Slide 190
Workshop – Setting restrictions in Notice Accounts (a)
Attributes > ACTIVITY.RESTRICTION –
TRANSACTION.AMOUNT.TOTAL > New Condition
 Create a Periodic Attribute applicable for monthly repeating periods starting
with calendar date to restrict total transaction amount
Attributes > ACTIVITY.RESTRICTION – MAXIMUM.BALANCE > New
Condition
 Create a Periodic Attribute applicable for life of an Arrangement to restrict
maximum balance in the account
Attributes > ACTIVITY.RESTRICTION –
TRANSACTION.COUNT.TOTAL > New Condition
 Create a Periodic Attribute applicable for a rolling monthly periods to restrict
transaction counts in the account
Slide 191
Solution - Setting restrictions in Notice Accounts (a)
Slide 192
Solution - Setting restrictions in Notice Accounts (a)
Slide 193
Workshop – Setting restrictions in Notice Accounts (b)
 Create a new Product Condition for Notice accounts
 Defining a rule for minimum initial balance of 1000 while crediting an
arrangement
 If minimum opening balance goes below 1,000, an override is to be
generated and MINBALFEE is collected for breaking the rule
 Define maximum balance not to exceed 2M, when exceeded, an error is to
be generated
 Restrict the total cash withdrawals amount to 5000 when cash withdrawals
occur within monthly periods defined. When the rule is broken, no credit
interest is to be paid to the customer for the period
 Assess whether the maximum transaction count does not exceed zero for
cash withdrawals. When rule is not broken, bonus is to be paid to the
customer
Slide 194
Solution - Setting restrictions in Notice Accounts (b)
Slide 195
Solution - Setting restrictions in Notice Accounts (b)
Slide 196
Workshop – Setting restrictions in Savings Accounts
 Create a new Product Condition for setting restrictions in savings Accounts

 Minimum balance to be maintained in the arrangement is 500. During debit
activity, if the balance goes below 500, an override to be generated and a
MINBALFEE to be collected on a defer basis
 Total transaction count for cash related withdrawals not to exceed 3 in a 1
month repeating period. When the rule is broken, credit interest is waived
for the period
Slide 197
Solution - Setting restrictions in Savings Accounts
Slide 198
Solution - Setting restrictions in Savings Accounts
Slide 199
Workshop – Setting restrictions in Student Accounts
 Create a new Product Condition for setting restrictions in student Accounts

 Define a rule for restricting minimum balance to 0 under periodic attribute
MINIMUM.BALANCE. The related balance to be defined
 CRINTEREST is waived when the customer breaks the rule of keeping a
minimum balance of zero (balance goes into negative)
 All attributes to be set as negotiable
Slide 200
Solution - Setting restrictions in Student Accounts
Slide 201
Workshop – Setting restrictions in Staff Accounts
Create a new Product Condition for setting restrictions in staff

Accounts:
 Define a rule for restricting opening balance to 100, if the minimum initial
balance, goes below 100, an error is to be generated
 Defining a minimum balance of 0 to be maintained in the account. If the
minimum balance in the arrangement during debit activity, goes below 0, an
override is set to be generated
 Restrict count of cash deposits per month to 5. If the count of cash deposits,
exceeds 5 per month, an error is to be generated
Slide 202
Solution - Setting restrictions in Staff Accounts
Slide 203
1. TRANSACTION.AMOUNT.MAXIMUM Periodic Attribute Class can be

used to restrict the increase in Current Account Balance
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
Slide 204
Tax Property Class
Customer Payment
Schedule
Account Closure
Activity
Accounting

Slide 205
Tax – Property Class
 Multiple Tax properties allowed
 Currency and Dated
Property
Class
TAX

DUE, AGE
DATED, CCY, MULTIPLE
Slide 206
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
Slide 207
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
Slide 208
Workshop – Setting Tax on Savings Account Interest
 Use Admin Menu > Product Builder > Product Conditions > TAX
 Tax to be collected on Savings Account Interest
 Property for Savings Account Interest is CRINTEREST
 All attributes are not negotiable
Slide 209
Solution - Tax on Savings Account Interest
Slide 210
Account Closure
Slide 211
Arrangement Closure
 Request for Closure - (Overview > New Activity)

 Can be undone by Reversing
 Settle out of Teller or FT
 Triggers an ACCOUNT Closure

 Cannot be undone
 ‘Reactivation’ activity brings Arrangement back to Live status
 Possible to close online or in Close of Business
212
Closure Property Class
Customer Payment
Schedule
Account
Activity
Accounting
Tax

Slide 213
Closure – Property
 Handles closure of Arrangements
 Product condition is Dated and Tracking
Property
Class
CLOSURE
Attributes:
Balance Prefix
DATED, TRACKING
214
Arrangement Closure
 Arrangement Closure a two step process:
 Request closure activity

 Calculates accrued interest, tax, if any for credit interest
 Updates final balance as on current date
 Charges for closure can be attached to this activity
 Possible to reverse through reactivation, charges not reversed
 Settlement for closure through funds transfer / teller
 Validation for account closure:

 Forward dated balances, exposure dates
 Account being closed tied up as a settlement account
 Status is not Pending Closure / Closed
215
Arrangement Closure
 Account balance is equal to zero

 Arrangement status moves to Pending closure
 Account balance is less / greater than zero

 Arrangement status moves to Request closure
 Request Closure status:

 No further interest accruals
 Credit / Debit to account still possible
 No activity other than settlement activity for closure can be run
 Reversal of Request closure activity possible
216
Closure – Product Condition
 Closure Type
 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
217
Workshop - Automatic closure
 Use Admin Menu > Product Builder > Product Conditions > CLOSURE
 Closure to happen automatically on balances becoming zero
 Period for processing is 10 days
 Posting restriction code is 90
 All attributes are negotiable by default
Slide 218
Solution – Automatic closure of Account
Slide 219
Workshop - Online closure of Account
 Use Admin Menu > Product Builder > Product Conditions > CLOSURE
 Closure to happen Online
 Period for processing is nil
 Posting restriction code is 90
 All attributes are negotiable by default
Slide 220
Solution – Online closure of Account
Slide 221
1. Payin rule is marked as None in Settlement product condition. This

indicates that this settlement is stopped till marked otherwise
a) True
b) False
2. Payment rules are used when Bank pays dues to Customer and
Payout rules are used when Customer pays dues to Bank
a) True
b) False
3. Once a closure activity is triggered and is completed in an

arrangement, it is possible to bring the Arrangement back to Live
status through a ‘Reactivation’ activity
a) True
b) False
Slide 222
Building Banking Products:
Retail Accounts Arrangements
Slide 223
Workshop - Creation of an Accounts Product Group
 Use Admin Menu > Product Builder > Products > Product Lines –Accounts
 Create a new Product Group with the following Settings:
PROPERTY CLASS PROPERTY MANDATORY
ACCOUNT BALANCE YES
ACCOUNTING ACCOUNTING YES
ACTIVITY.MESSAGING MESSAGING
ACTIVITY.MAPPING ACTIVITY.MAPPING YES
ACTIVITY.CHARGES ACTIVITY.CHARGES
ACTIVITY.PRESENTATION PRESENTATION
CUSTOMER CUSTOMER YES
INTEREST CRINTEREST
DRINTEREST
LIMIT LIMIT
OFFICERS OFFICERS
CHARGES ACCHARGE
TXNFEE
CHEQUEWD
PAYMENT.SCHEDULE SCHEDULE
ACTIVITY.RESTRICTION AR.ACCOUNT
CLOSURE CLOSURE YES
BALANCE.MAINTENANCE BALANCE.MAINTENANCE
BALANCE AVAILABILITY BALANCE.AVAILABILITY
ELIGIBILITY ELIGIBILITY
CHANGE.PRODUCT RENEWAL
CHARGE.OVERRIDE CHARGE.OVERRIDE
PERIODIC.CHARGES LEDGERFEE
TAX TAX
PAYMENT.RULES ACCOUNTS.PAYMENT.RULES YES
PAYOUT.RULES ACCOUNTS.PAYOUT YES
SETTLEMENT SETTLEMENT
Slide 224
Solution – Creation of an Accounts Product Group
Slide 225
Solution – Creation of an Accounts Product Group
Slide 226
Workshop – Creation of a Default Accounts Product
 Use Admin Menu > Product Builder > Products > Product Lines –
Accounts > Product Groups
 Create a default Product under Product Group created in previous Workshop with
the following settings:
PROPERTY PRODUCT CONDITION ARR.LINK

ACCOUNTING ACCOUNTS Tracking
BALANCE CURRENT.ACCOUNT.DEFAULT Non-Tracking
CRINTEREST NONE Non-Tracking
LIMIT SINGLE Non-Tracking
SCHEDULE NEGOTIABLE Non-Tracking
PRESENTATION SAVINGS.ACCOUNT Tracking
CUSTOMER STANDARD NON - TRACKING
OFFICERS SAV.CURR.ACCOUNTS Non-Tracking
CLOSURE ACCOUNT.CLOSURE Non-Tracking
BALANCE.MAINTENANCE NEGOTIABLE Non-Tracking
ACTIVITY.MAPPING ACCOUNTS Tracking
ACCOUNTS.PAYMENT.RULES ACCOUNTS.PAYRULE Tracking
ACCOUNTS.PAYOUT ACCOUNTS.PAYOUT Tracking
SETTLEMENT ACCOUNTS Non-Tracking
contd....
Slide 227
Workshop – Creation of a Default Accounts Product
 Set the following in calculation source tab:
Calculated Property Source Type Source Balance

 Product is available in PHP
CRINTEREST CR.MINIMUM CURBALANCE
 Amend the Eligibility product condition created earlier to have default product configured here
Slide 228
Solution – Creation of a Default Accounts Product
Slide 229
Solution – Creation of a Default Accounts Product
Slide 230
Solution – Default record creation
Slide 231
Accounts Arrangement
Slide 232
Workshop - Creating an Accounts arrangement
 Use User Menu > Retail Operations > Account Arrangement > Account
Arrangement - Product Catalog > Retail Accounts > Product Groups >
Your Product Group > Your Product
 Create an Arrangement for your Customer for the Product published in
previous Workshop
 Look at the Account Schedule. Are interest definitions for debit and credit
available. Check if, Ledgerfee set for periodic charge is also defined
 Click on the settlement tab. Payin and Payout accounts of the customer are
to be fed in
 Commit the Arrangement
 Accept overrides, if any
Slide 233
Solution - Creating an Accounts arrangement
Slide 234
Understanding the Arrangement Overview
User Menu > Retail Operations > Account Arrangement > Account Arrangement
Label Description
Arrangement Contract reference
Account Arrangement Account Reference
Product Product of the Account
235
Label Description
Ledger Cleared Balance + Uncleared
Balance funds
Cleared All authorised Credits and
Balance Debits (only cleared funds=no
future exposure dated credits
included)
Working Cleared Balance +
Balance Unauthorised Debits
Available Limit Overdraft Available
Overdraft
236
Label Description
Locked Funds Enquiry on
AC.LOCKED.EVENTS and
“New” Icon
Financial AVAILABLE Balance multi-
Summary value set from ACCOUNT
Record
Accruals Interest accruals till date
237
Label Description
Activity Log Lists all Current and Pending
Activities
Recent Txns Recent transactions on the
account in descending order
Enquiries General Account related
enquiries
238
Label Description
New Activity Facilities in Accounts and
amendment of existing Activity
239
Account Activities and Transactions
Slide 240
Financial Activities
Teller Account Funding
Funds Transfer ACTIVITY Apply Repayment

MAPPING
Settlement Account Payout
 Payments from and into an AA Account can be done through ACCOUNT related applications
 Activity is selected based on Transaction Code
 Settlement Property enables some of these Activities
Slide 241
Workshop – Transfer between Arrangement Accounts
Use User Menu > Retail Operations > Account Transactions > Draft
Issue/Account Transfer > Transfer between Accounts
 Select two arrangement account numbers
 Input a transfer of PHP 25,000 between the accounts
Slide 242
Solution – Transfer between Arrangement Accounts
Slide 243
Workshop – Payment of Arrangement loan
Use User Menu > Role based Home Pages > Payment Services > Home
Page - Payments > Funds Transfers > Payments / Accounts Transfer
 Select a lending arrangement and a current account arrangement
 Input a transfer of PHP 7,500 to pay into the loan arrangement
Suggestion: Trainees can create a back dated AA Loan with automatic

disbursement and try a pay back to that arrangement.
Slide 244
Solution – Payment of Arrangement loan
Slide 245
Workshop – Back dated credit in an Arrangement
Use User Menu > Role based Home Pages > Retail Operations > Home
Page – Customer Service Agent > Payments / Accounts Transfer
 Select an arrangement account opened a month back
 Transfer a sum of PHP 32,500 into this arrangement from another

arrangement account with value date a month back
 Observe the accrued interest
Slide 246
Solution – Back dated credit in an Arrangement
Slide 247
Slide 248
Slide 249
Workshop – Eligibility checking in Retail account
Use Admin Menu > Product Builder > Product Conditions > ELIGIBILITY
 Pick out the Children record
 View eligibility settings in Children account
Use User Menu > Retail Operations > Product Catalog > Retail Accounts
> Product Groups > Savings Account > Savings Account (Notice)
 Verify how they work at arrangement level when you open an arrangement for a
person above 18 years and a customer who is a foreigner
Slide 250
Solution – Eligibility product condition
Slide 251
Solution – Checking eligibility in an arrangement
Slide 252
Solution – Checking eligibility in an arrangement
Slide 253
Workshop – Change Product to a different Product Group
Use User Menu > Retail Operations > Find Accounts > Authorised
 Pick a Savings Account arrangement
 Through New Activity tab, change the product to Current arrangement
account
 Observe the error generated
Slide 254
Solution – Change Product
Slide 255
Workshop – Reverse / Replay of back dated entries
Use User Menu > Retail Operations > Find Account > Authorised
 Pick an existing arrangement
 Input a back dated FT to credit the account with 20,000
 Authorise the same
 View the activity log through arrangement overview
Slide 256
Solution – Reverse / Replay of back dated entries
Slide 257
Slide 258
Slide 259
Quiz 5 – Choose the correct Answer
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
Slide 260
Quiz 5 – Choose the correct Answer
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
Slide 261
Account Facilities & Enquiries
Slide 262
Account Facilities
 Issue Card
 Manage Card
 Issue Cheque
 Stop Cheque
 Stop Amount
 Revoke Stop
 Notice withdrawal
 Statement Frequency
 Update Statement Frequency
 Print Passbook
Slide 263
Account Enquiries
 Statement Entries Today
 Today’s Transactions
 Forward Movements
 Interest Rate Changes
 Cheques Issued
 Cheques Presented
 Stopped Cheques
 Revoked Cheques
Slide 264
Statements
Slide 265
Statement Generation and Enquiries
 ACCOUNT.STATEMENT record auto generated for all new Accounts
 It has Date and frequency for printing account statements, as defined in

STMT.GEN.CONDITION table
 Possible to change frequency at Account level using

ACCOUNT.STATEMENT
 Can be accessed through Facilities tab in Arrangement Overview
 Account Statement and Statement entries today available for enquiry

through Arrangement Overview – Enquiries tab
 AC.PRINT.MASK application used to mask entries from appearing in a

statement
Slide 266
Workshop – Statement Frequency Set up and Enquiries
 Use Role Based Home Page > Retail Operations > Home Page –
Customer Service Agent > Arrangements> Accounts > Authorised
 Select an existing Arrangement
 Select New Activity and Account Facilities
 Choose Statement Frequency
 Set Statement Frequency as Monthly
 Select Enquiries, View the Statement Entries Today
 View Today Transactions
Solution – Statement Frequency
Slide 268
Solution – Statement Frequency
Slide 269
Solution - Enquiries
Slide 270
Forward Movements
Slide 271
Workshop – Forward dated transaction and enquiry
 Use User Menu > Retail Operations > LCY Draft Issue/Account
Transfer > Transfer between Accounts

 Input a forward dated credit for PHP 25,000
 View the forward movements through arrangement overview
Solution – Forward dated transaction
Slide 273
Solution – Forward movement enquiry
Slide 274
Interest Rate Change
Slide 275
Workshop – Debit Interest rate change
Customer Service Agent > Arrangements > Accounts > Authorised
 Select “New Activity” Tab and Choose debit interest change activity
 Change debit interest rate
 Get the change activity authorised
 View the change in interest rate through arrangement overview
Solution – Debit Interest rate change in Arrangement
Slide 277
Slide 278
Slide 279
Retail Account Maintenance
Slide 280
To Change the Customer
ACCOUNT
ACCOUNT,CHANGE.PRIMARY.OWNER Version
Only CUSTOMER field

Open for Input
(controlled at
VERSION level)
281
To Change the Customer
AA
Only CUSTOMER field

Open for Input
(controlled at by
ACTIVITY CLASS)
282
To Attach Overdraft Limit
ACCOUNT
ACCOUNT,ATTACH.LIMIT.HP Version
Only LIMIT.REF field

Open for Input
(controlled at
VERSION level)
283
To Attach Overdraft Limit
AA
Only LIMIT Property is

Open for Input. All
others are disabled
284
Posting Restrict
Slide 285
Workshop – Create Arrangement with POSTING RESTRICT
Customer Service Agent > Product Catalog > Retail Accounts > Current
Account > Fully Negotiable Account
 Create a New Fully Negotiable Account Arrangement for a customer
 Select “Account” Tab and set the POSTING.RESTRICT as “1” No Debits
allowed for this Arrangement
 Commit the Record and
 Get the Record Authorised
 Use User Menu>Retail Operations> LCY Draft Issue/Account Transfer>

Transfer between Accounts
 Input a Funds transfer by debiting the Arrangement account for PHP 10,000
and credit to customers account
 Commit Record, Note the override message
Solution – Arrangement with Posting Restrict
Slide 287
Solution – Funds Transfer with Posting Restrict
Slide 288
Notice Accounts
Slide 289
Locking of Amounts
Slide 290
Workshop – LOCKED AMOUNT
 Use Role Based Home Page> Retail operations > Homepage –

Customer Service Agent > Arrangements> Account > Authorised
 Use your existing current account
 Block PHP 5,000 for 1 month from today
 View the locked amount created in your account
Slide 291
Solution – Locking of Funds in an Arrangement Account
Slide 292
Account Closure Related
Slide 293
Workshop –CLOSURE OF ARRANGEMENT with Locked
Amount
 Use Role Based Home Page> Retail operations > Homepage –

Customer Service Agent > Arrangements>Account > Authorised
 Select the Arrangement record of your customer with the locked Amount
used in the previous workshop
 Do a REQUEST.CLOSURE Activity and
 View the Message and accept the Overrides, if any
 Get the record Authorised
 View the Status of the Arrangement

Solution – Closure of Arrangement with Locked Amount
Slide 295
Solution – Closure Activity with Locked Amounts
Slide 296
Solution – Closure of Arrangement – View Status
Slide 297
Workshop – Closure of Arrangement with Zero Balance
 Use Role Based Home Page> Retail Operations > Homepage –

Customer Service Agent > Arrangements>Account >Authorised
 Pickup the Arrangement with Zero balance and do a Request Closure
activity through New Activity Tab
 Get the record Authorised
 View the Status of the Arrangement
Slide 298
Solution – Closure of Arrangement
Slide 299
Slide 300
Slide 301
Primary Customer Change
Slide 302
Workshop –Primary Customer Change
 Use Role Based Home Page> Retail Operations > Homepage –

Customer Service Agent > Arrangements>Account >Authorised
 Select an Arrangement record of your customer created earlier and Change
the existing Primary Owner of the arrangement with different customer
Solution – Primary Customer Change
Slide 304
Solution – Primary Customer Change
Slide 305
Solution – Primary Owner Change
Slide 306
Eligibility
Slide 307
Workshop – Eligibility Checking
 Choose a Customer whose age is more than 25 Years
Customer Service Agent> Product Catalog >Retail Accounts > Current
Account Group > Student Account (Child)
 Create a New Student Account Arrangement for the above selected
Customer
 View the Eligibility Condition
 Commit the Record
 View the Error Message
Solution – Viewing the Customer Record
Slide 309
Solution - Eligibility
Slide 310
AA Advanced Accounting
Slide 311
AA Accounting –overview
Arrangement Accounting
Activity Events
Accounting
Property Product Action
Condition Financial
Reporting
Balance 1
Allocation
Balance 2 Rules SPEC.ENTRY
Balance ‘n’
STMT.ENTRY
Update CATEG.ENTRY
Balances
Slide 312
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
Slide 313
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
Slide 314
Balance Prefix
Possible Prefixes for

Accounts 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
PAY = Payable Balance

ACCOUNT, INTEREST, CHARGE
Slide 315
AC.BALANCE.TYPE
 Reporting Types
 Contingent - Off-Balance sheet item
 Non-Contingent – In Balance Sheet

 Internal - Not Reported
 Virtual - Sum of specified balances
 Activity Update
 Option to update historical balance file
 Suspend Balance
 Option to suspend posting to PL
 Change asset type

 If the account moves from debit to credit
or vice versa
Slide 316
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
Slide 317
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
Slide 318
 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
Slide 319
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
Slide 320
Activity Class Actions- ACCOUNTS-CHANGE-INTEREST
Update Interest
Evaluate Activity Restriction
Calculate Activity Charges
Send Message Activity Messaging
Actions Property Classes
Slide 321
Activity - ACCOUNTS-CHANGE-CRINTEREST
Update CrInterest
Evaluate Activity Restriction
Calculate Activity Charge
Send Message Activity Messaging
Actions Properties
Slide 322
Accounting Property Class
Charge Limit
Customer Payment
Schedule
Account Closure
Activity
Accounting
Tax

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

level
 Update Action possible, will not generate Accounting entry
Property Class
ACCOUNTING
Attributes:
Balance Prefix
DATED, MERGE, NIL
TRACKING.ONLY
Slide 324
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
Slide 325
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)
Slide 326
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
Slide 327
AC Allocation Rules and AC Posting Detail
 Allocation Rules take an event and creates a number of entries by

specifying
 Target Balance
 Contra Balance
 Transaction Codes to Use
 Movement Detail
 Multiple Targets and Contra Targets can be created from same event
 Will allow additional movements to be created if required
 Target options include P&L, Internal Account, specific Balance Type
 Default is balance type supplied with the entry through
AC.POSTING.DETAIL
 Posting Detail allows detailed content of the entry to be defined

 Entry type
 References, Narratives etc
Slide 328
Workshop–View Account & Accounting information
after FT
 Use User Menu > Retail Operations > LCY Draft Issue/Account
Transfer > Transfer between Accounts
 Input a Funds transfer for the arrangement created in the earlier workshop
 Commit Record, Note the override message, if any
 Use Command Line

 Look at the ACCT.BALANCE.ACTIVITY, EB.CONTRACT.BALANCES and
Arrangement Balances
Slide 329
Solution–View Account & Accounting information after
FT
Slide 330
Solution–View Account & Accounting information after
FT
Slide 331
Workshop – Rebuilding Product group & Product
 Use Admin Menu > Product Builder > Products > Accounts
 Open your Product Group
 Add your CHARGE property to Charge Property Class
 Rebuild the Product Group
 Use Admin Menu > Product Builder > Products > Accounts > 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
Slide 332
Solution – Rebuilding Product group
Slide 333
Solution – Rebuilding Product
Slide 334
Solution – Proofing & Publishing the Product
Slide 335
Retail Accounts - A Review
In this course, you were introduced to Retail Accounts. Emphasis was given on
some basic and important Property Classes.
Having completing this course, you will now be able to:
 Understand the product overview of T24 Accounts and Retail Accounts
 Identify Application specific parameter tables for designing a Retail Account

product
 Configure a Retail Account Product
 Perform user activities and transactions related to the Product

Arrangement Architecture - Accounts - TM - R15

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

Arrangement Architecture - Accounts - TM - R15

Uploaded by

Copyright:

Available Formats

T24 Retail Accounts

After completing this learning unit, you will be able to:

 Understand the product overview of T24 Accounts and Retail Accounts

 Identify Application specific parameter tables for designing a Retail Account

 Configure a Retail Account Product

 Perform user activities and transactions related to the Product

Interest Charges Charges Interest

Fixed Floating Fixed Floating

Limit Credit Debit

 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, UND,

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

PRODUCT ONLY FORWARD.DATED

SUSPEND RESIDUAL ACCRUAL

 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

 This application holds information on actions performed in each

 The information covers:

Activity Activity Activity Balance

 Property for Officers can be set as Tracking

 Update Action possible

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

Activity Activity Balance

 Values cannot be viewed or edited at arrangement level

 Arrangement level values track changes to Product condition

 Which maps to Activity

 Similar mappings for Activity Mapping

 Default Activities for unmapped Transaction Codes of Debits and

1. Accounts Arrangements include Customer Accounts, Internal Accounts,

2. Eligibility conditions help in creating different Product Catalogues for

3. It is possible to Issue / Manage cheques, cards, statements, passbook,

 Alternate Account numbers

 Possible to reference T24 account numbers through alternate account

 ALT.ACCT.PARAMETER Table should be set up to indicate conditions for

 In ACCOUNT.PARAMETER, ALTERNATE.ACC.IDS Field to be set as Y

 Alternate account number should be loaded into ALT.ACCT.ID Field in

 System automatically maintains the old and corresponding new numbers in

 Inactive marking in account

 When an account remains inactive without any debit/credit transactions

 Period in months for deciding inactivity defined in INACTIVITY.MONTHS

 System updates INACTIV.MARKER Field as Y in Account accordingly

 Marker can only be reset through ACCT.INACTIVE.RESET application

 ACCOUNT Property Class is Dated

Attributes: Balance Prefix

 Account Title, Short Title and Mnemonic

 Base Date Type

 Securities Valuation enquiry

 Bus Day Centres

 Account is required for all financial Arrangements

 Customer Reference, Account Reference

 Allows changes to the following Account attributes:

 Using the command line, create a REFERAL condition to refer

 These balances are due to movements of the day