Introduction to Retail Lending

The Lending module in AA.PRODUCT.LINE provides high-level definition of the business components (Property Classes) required for Lending Product Line.

The Product Lines are defined by Temenos and cannot be created by the user.

The financial institution then uses the business components to build individual deposit product based on the customer target segment requirements.

Below is the list of Property Classes of the Lending Product Line.

The application provides the ability to allow the user to construct banking products by combining different business components. The Product Lines, which provide functionality for different banking areas are licensed by Temenos; each Product Line utilises a number of Property Classes (business components) that are configurable.

The main features of the product builder are given below:

• Ability to build families of products
• Ability to inherit properties from the product family structure
• Ability to determine the properties that a product is comprised of
• Control of default values to be applied for product arrangements
• Dated conditions for products
• Full control of scope of negotiation between product and arrangement conditions
• Control of negotiation of attributes over time
• Design, proof and publish lifecycle for product management
• The product builder can be used to create and maintain existing application (Mortgage, Account, Loans and Deposits and AZ) product parameters

The Accounting Property Class is used by all products. Arrangement Architecture (AA) uses activity-based accounting. Each Property has different actions, which require accounting. For each action, a corresponding allocation rule definition is required. Allocation rules can be defined either at Property or Property Class level. The categories to which the interest or charges have to be posted are also defined in this Product Condition. In Model Bank, the charges are amortised.

The Activity Charge Property Class defines the charges that has to be applied when a particular activity is triggered on the arrangement. The charges so applied can be made due, capitalised or deferred. In the model bank, for a Mortgage loan product a principal decrease fee is applied for a principal decrease activity and a new arrangement fee is applied when a new arrangement is created.

The Activity Mapping Property Class provides the link between external applications and arrangement activities when a transaction is performed on an arrangement account. A debit or credit to an arrangement account triggers the applications such as Funds Transfer, Teller, Clearing, etc., which are linked by relevant transaction codes using this Product Condition.

The Agent Commission property class is possible to record the agent and the agent arrangement for a given financial arrangement and monitor what are the default events that trigger commissions and ability to provide a spread over the default commission rates and give the ability to provide an overriding amount, as against the predefined commission calculation.

The Alerts Property Class is used by all products. It enables alerts to be sent to the customer for various activities in an arrangement. Alerts can be subscribed at the arrangement level by using EB.ALERT.REQUEST. Multiple owners of the arrangement are allowed to subscribe different alerts on that arrangement. The subscription of alerts can be restricted based on the role of the customer in that arrangement.

The Activity Presentation is an optional Property Class that allows to define versions used for various Properties during arrangement activities. The versions can be defined at Property Class, Property and Activity levels.

The Activity Restriction Property Class is used to specify the 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.

The Activity Messaging Property Class links the Soft Delivery module to Arrangement Architecture module. Messages are sent based on the role and activity performed on an arrangement. This record allows either specific Activities or Activity Classes to be defined and linked to the records of EB.ADVICES.

The Balance Maintenance Property Class allows the user to capture bills and balances, and adjust the balances of the bill for the contracts, which have been taken over from existing legacy system or Temenos' Lending module into the AA module.

The actions such as CAPTURE.BILL, ADJUST.BILL and so on., help in capturing the bill and its balances into the new system.

The Charge Property Class is used for all charge calculations in AA. The charge can be a scheduled , periodic or an activity based charge. It can be fixed or calculated based on band or level. The currency in which the charge has to be applied can also be defined. It is possible to define a minimum charge and also to waive the charge.

The Charge Off property class enables the customer to charge off various properties financial balances in arrangements. This can be a partial charge-off, a series of partial charge-off transactions, or a total charge-off. Feature Dual Accounting – i.e. having two sets of books; the Customer Record vs. the Bank Record and applying payments “independently” to the two records is enabled.

The Charge Override Property Class enables the customer to modify the ad-hoc charges triggered by an Activity. The user can either waive or modify the activity charge or rule break charge.

The Change Product property class defines the rules and behaviour for allowing arrangements of one product to be changed to another product. The CHANGE.PRODUCT property can be included in a product if arrangements are allowed to be changed to another product during its lifetime. The Property Class allows the definition of restrictions on products that change can be made to and when a scheduled change should be applied. It can also be used to define the roll over conditions for an arrangement.

The Closure Property Class is used to close an arrangement account. An arrangement account can be closed automatically or manually. This is defined in the product condition. On reversal of a new arrangement, closure is triggered automatically.

Cooling period functionality is available in the Closure Property Class (PC), for Accounts, Deposits, Lending, Rewards and Safe Deposit Box. If the customer chooses to cancel (that is, payoff) the loan within the cooling period, any charges and interest are waived off based on the product condition setup.

The Constraint Property Class is used to define constraints on the arrangement. The constraint indicates the maximum period an arrangement that can be backdated with an error or override.

The Customer Property Class is used by all products. This property class is used to define all the parties involved in an arrangement. The customer is always defined at the arrangement level. Each arrangement can have one or more legal owners defined in OWNER

The Eligibility Property Class is used to evaluate eligibility of a customer for a specific product based on a set of rules. Here, first the EB.CONTEXT has to be created. Based on this, rules are defined using Rules Engine. Once these rules are validated, the EB.RULES.VERSION and EB.RULES are created in the system.

This Facility Property Class controls the list of available services for an arrangement account. When an external activity (financial/non-financial) is triggered and the corresponding service group is identified as blocked for this account, then an error message appears to stop the activity.

The Interest Property Class is used for all interest definition and processing in AA. A product defined and processed in AA can have multiple interest properties defined (for example, principal interest, penalty interest, commission, etc.) Interest rates can be define as Fixed , Floating, Periodic or Linked Rate (referring an interest property from other arrangement). Tiered interest can also be defined. Further it is possible to define a Negative Rate, Minimum interest amount and waive the interest.

The Limit Property Class primarily controls the use of Limit module by the product. The user can set up single or shared limit and can define Limit Reference applicable for a specific product such that the same is set as default in an arrangement. For a new limit, at the arrangement level, the user should provide New in the Limit Serial field. Further limits can be set to use the Limit module or it can be managed only within the arrangement architecture framework.

The Officers Property Class enables the user to define:

• Product
• Arrangement specific officers
• Officer’s roles
• Primary officer
• Additional officer

The Overdue Property Class controls the ageing process of the bills raised in arrangement. The ageing period, statuses and accounting treatment of the outstanding balance can be defined. It is possible to define penalty interest to be applied on the overdue amounts and/or current balances. Bills can be aged based on the number of outstanding bills or days. It is also possible to define that all bills of an arrangement have to be aged to the present status. Accounting entries can be made to raise for every status movement and chaser advices can be scheduled.

The Payoff Property Class is used to produce a payoff statement, which is given to a customer when a loan payoff is considered. It shows the current status of the account, including the updated accrued interest and penalty applicable, if any. An expiry date can be defined for the payoff statement and the loan statement shows the additional daily interest to be charged till the expiry date.

The payoff amount is calculated by using the simulation framework.

The Payment Rules Property Class controls the sequence and order in which the bills or outstanding balances that required to be settled. An arrangement can contain several outstanding bills and each bill can be comprised of multiple amounts (for example, principal, principal interest, penalty, tax, charges, etc.). When a customer makes a payment, the entire due amount cannot be satisfied. This Property Class is used to define the method by which a single payment is applied to multiple bills and multiple amount types.

The Payment Schedule Property Class is used by all products which have amounts billed (that is, made due or capitalized 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 AA.PAYMENT.TYPE file is used to define the standard payment types such as Constant, Linear, Actual and Fixed Equal, etc., that can be used by a product. This payment type is then attached to each payment schedule definition. The start and end date can be specified. The user can specify the repayment of arrangement to commence after ‘n’ months from the arrangement date or ‘n’ months before the maturity or ‘n’ months after the change product or reset and rollover has happened.

The Payout Rules Property Class is used by various Product Lines, which have amounts billed and made due for payment to the customer. It is used to define the method by which a single payment is applied to multiple bills and multiple amount types.

The Periodic Charges Property Class is used to define a charge to be applied in relation to a period of time. The charge currency can be specified and the charge can be set to be deferred. A minimum and maximum charge amount can be defined.

The Reporting Property Class defines parameter for IFRS compliance of AA. It is also used to configure position management reporting.

The Statement Property class is used to define the legacy ACCT.STATEMENT feature at Arrangement Architecture 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 if advices are to be produced or not, when interest and charges are applied, and whether detailed interest statements (interest scale) should be produced.

The Settlement Property Class is used for various Product Lines to control the settlement related functions of all the Product Lines. Settlement can be handled by linking any customer account within the system, the account and bank details of another bank by using Direct Debit and beneficiary of the customer.

The Settlement Property Class specifies the counter booking details with the Counter Booking Account, Dr Counter Booking Activity and Cr Counter Booking Activity fields. The Default Settlement Account is considered as the default account for both Pay-in and Pay-out Activities, if the Pay in or Pay out account is not specified. But, if the accounts are specified for the Pay in or Pay out, then those accounts precedes over the specified default settlement account.

The Dormancy Property Class allows the user to control the parameterisation of inactive or dormant accounts and movement of these accounts into various buckets at arrangement or product level. It can control 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.

The Tax Property Class allows the user to control and define tax that has to be calculated for various financial property. Tax definition can be done at both Property Class and Property Tax level. The tax can be attached both at TAX and TAX.GEN.CONDITION level.

The Term Amount Property Class is used by financial products which involve an amount of money that is lent or deposited for a specified period of time. This property class controls the commitment made by the bank and the customer.