| Bookmark Name | Actions |
|---|
Introduction to Retail Accounts
ⓘContent enriched:New structure and revised (Docs 2.0)
Retail Accounts (AR) is one of the modules under Arrangement Architecture (AA) umbrella of products and is part of the Temenos Retail Banking suite of products.
The AR module provides financial account functionality and its maintenance for a financial institution. The module allows the user to create current or checking and savings accounts using the AA framework, under the Accounts Product Line, and perform a series of related activities on it.
A few of the key functionality included are:
- Create a new account arrangement
- Perform credit or debit activity or transactions for the account
- Accrue credit or debit interest accruals
- Capitalise interest to account balances
- Monitor charges and commissions
- Monitor inactivity or dormancy
- Issue cheque book or passbook
- Issue mandates
Configuring Retail Accounts
The AA.PRODUCT.LINE application provides a high-level definition of the business components (Property Classes), required to construct a product belonging to that line.
A Product Line is described by Property Classes which constitute it. A financial institution can use these building blocks (Property Classes) to construct individual products, which can then be made available for sale to its customers.
AR has the following Property Classes.
|
|
|
The AA.PROPERTY is an instance of AA.PROPERTY.CLASS and these components constitute an account product. The Property Classes and Properties are made Mandatory or Optional based on the AA.PRODUCT.GROUP level but subject to the Product Line definition. The AA.PRODUCT.DESIGNER is used to create the Account Products required.
Illustrating Model Parameters
The product conditions of a Property Class are evaluated to bring out the features of the Property Class. The system defaults the values in the product condition in an arrangement during its creation. The negotiability or default values and other restrictions are also defined in the product condition. These product conditions along with the properties derived from the Property Classes are grouped together to build products.
The product conditions are dated and some of the product conditions have currency as part of their ID. When the currency forms a part of the product condition ID, the user needs to create different conditions for each currency in which the product is available. When a new condition is created or an existing one is amended, the product to which the condition is linked has to be proofed and published.
| S.NO | Parameters | Description |
|---|---|---|
| 1 | Account |
The Account Property Class is used by all the products which are account based. This Property Class primarily controls the description of the account. The ACCOUNT property allows the user to define and control balance tTreatment, posting restriction, linked account number (for memo accounts), currency market, date convention related setup for the account. Although the account names are account specific, generic titles can be defaulted from the product and can be replaced or given additional detail at the arrangement level. Each Temenos Transact product defined and processed in AA can have a single ACCOUNT Property defined. |
| 2 | Activity Charges |
The Activity Charges Property Class defines the charges that have to be applied when a particular activity is triggered on the arrangement. The charges so applied can be made due, capitalised or deferred. The user can enable auto settle the charges made due from unallocated credit balance by setting this to Yes. In accounts, charges are enabled for dormancy, settle payoff and ageing. This Property Class is also extensively used for all AA related modules, charges are set for various other activities. |
| 3 | Activity Restriction |
The Activity Restriction Property Class is used to specify a restriction on a particular transaction. The restriction rules including the relevant periodic attributes and activities are defined in the product condition. These rules are then used to define activity based or property based restrictions. A rule if broken can be set to result in an override or error. A charge can be attached for this and can be set to be made due, capitalised or deferred. For the AR module, activity restriction is extensively used for restricting transactions by number, type, etc. This is also extensively used in other modules to restrict the user from doing various user activity based on the life cycle status of contracts. |
| 4 | Balance Availability |
The Balance Availability Property Class allows the user to control the following features pertaining to AR Module:
|
| 5 | Dormancy |
The Dormancy Property Class allows the user to control the parameterisation of inactive or dormant accounts and movement of the same into various buckets at the arrangement or product level. The same can be controlled based on period, and some exceptions or rules also can be added for evaluation and movement. The user can include or exclude certain activity or activity class for the evaluation. It is possible to
|
| 6 | Facility |
The Facility is a service component for financial products designed using arrangement architecture. The Facility Property Class controls the list of available services for an arrangement account. When an external activity (financial or non-financial) is triggered and the corresponding service group is mapped to an activity through Activity Mapping and EB.EVENTS. And the same came allowed or restricted or charged corresponding error message is raised to stop the activity. |
| 7 | Inheritance |
The Inheritance Property Class is used for BN pool structure for inheriting the product conditions set at Parent level arrangement to the Child level arrangement accounts. The product conditions that are set for inheritance are attached to Property records with type as Inheritance Only. The properties to be inherited can be controlled both at source and target level. |
| 8 | Interest |
The Interest Property Class is used for all interest definition and processing in AA. A Temenos Transact product defined and processed in AA can have multiple interest properties defined (for example, principal interest, penalty interest, commission, etc. Interest rates can be defined as fixed , floating , periodic or linked rate (referring an INTEREST property from other arrangement), routine based calculation. Tiered interest can also be defined. Further it is possible to define a negative rate, minimum interest amount and waive the interest. Interest adjustment can be done in run time, and adjustment related detail or values can be captured in adjustment related fields. |
| 9 | Limit |
The Limit Property Class primarily controls the use of LIMIT module by the product. We can set up single or shared limit. We can define the LIMIT.REFERENCE applicable for a specific product such that the system defaults the same in an arrangement. For a new limit, at the arrangement level, the LIMIT.SERIAL has to be given as NEW. The AR Module can have self-contained secondary limit without having actual limit attached to it. Overdraft status or notice for AR module is handled inside the Limit Property class. Further Limits can be set to use the LIMIT module (AL and AD) or it can be managed only within the arrangement architecture framework. |
| 10 | Payment Schedule |
The Payment Schedule Property Class is
used by all products which have amounts billed (that is,made due) or capitalised
or Pay. A Payment Schedule can be comprised of one or more Payment
definitions with conditions such as payment Type and Method, arrangement
Properties, Dates and Amounts. The |
| 11 | Periodic Charges |
The Periodic charges Property Class acts as a container to group different charge properties and calculate a periodic charge amount. The Payment Schedule Property Class drives this Property class. A periodic charge property can be attached in payment schedule and on schedule date periodic charge amount is calculated. At the arrangement level adjustment can be done by the user on whole periodic charge. |
| 12 | Statement |
The Statement Property class is used to define the legacy ACCT.STATEMENT feature at the AA level. Statements may be produced daily (every working day), every 1-9 weeks, twice a month (on the 15th and the last day of the month) or every 1-12 months on any day of the month. Up to nine statement cycles may be specified for each account, and each statement cycle is independent. In addition to this, special interim statements can be enabled. This property class also controls whether or not advices are to be produced when interest and charges are applied, and whether detailed interest statements (interest scale) should be produced. Within a statement cycle, it is possible to define multiple frequencies with a combination of weekly and monthly, such that statements are produced on the dates specified by both frequencies, but only contain details of entries since the last statement in that cycle. |
Illustrating Model Products
The AR Product Line provides current and savings account functionality for Temenos Transact. The module allows the user to create savings or current accounts using the AA framework under the Accounts Product Line.
|
S.No |
Product Name |
Product Attributes |
|---|---|---|
|
1 |
Current Accounts |
|
|
2 |
Savings Accounts |
|
|
3 |
Summary Accounts |
|
Add Bookmark
save your best linksView Bookmarks
Visit your best linksIn this topic
Are you sure you want to log-off?