MicroBankingSuite

Account Statement Narratives

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means,
for any purpose, without the express written permission of TEMENOS HEADQUARTERS SA.

© 2015 Temenos Headquarters SA - all rights reserved.

 Account Statement Narratives User Guide

Table of Contents
Document History ............................................................................................................................. 3
Introduction ....................................................................................................................................... 4
Document Purpose ....................................................................................................................... 4
Assumptions ................................................................................................................................. 4
Exclusions ..................................................................................................................................... 4
References .................................................................................................................................... 4
Account Statement Narratives .......................................................................................................... 5
Overview ....................................................................................................................................... 5
Parameterisation ........................................................................................................................... 6
Narrative Parameters ................................................................................................................ 7
Narrative Formats.................................................................................................................... 11
AA Parameters ........................................................................................................................ 14
Notes .............................................................................................................................................. 18

2 MicroBankingSuite: Product
 Account Statement Narratives User Guide

Document History

Author Version Date

Lukasz Czechowicz 1.0 10th February 2017

Comments:

3 MicroBankingSuite: Product
 Account Statement Narratives User Guide

Introduction
Document Purpose
This document provides an overview of the Account Statement Narratives functionality and
describes how the functionality can be configured to meet specific business requirements. It is
aimed at business users that will work with the system and implementation teams that will configure
it.

Assumptions
It is assumed that the reader of this guide is proficient in the Temenos Core Banking system, worked
with the Browser channel application and understands the structure and navigation of the
MicroBankingSuite Role Based Home Pages. For configuring the functionality, it is assumed that
the reader has prior implementation experience and understands the technical concepts of the
Temenos Core Banking system.

Exclusions
None.

References
MicroBankingSuite Role Based Home Pages user guide.

4 MicroBankingSuite: Product
 Account Statement Narratives User Guide

Account Statement Narratives

Overview
The Account Statement Narratives functionality in the MicroBankingSuite provides a flexible way of
parameterising transaction narratives for clear and human-friendly presentation of financial activities
on an account. The new presentation of account activities is available in online enquiries and on
printed correspondence (PDF account statements). The functionality also fully supports multi-
language definition of narratives.
The functionality is driven by the following parameter tables:
 Narrative formats define textual descriptions of transactions (financial activities) that may
occur on an account.
 Narrative parameters link the different T24 applications and their transaction types with the
narrative formats.
 AA parameters define how the different financial components (e.g. principal, interest) of an
AA transaction are grouped and described under the main transaction narrative.
Sample PDF account statement documents are included in the MicroBankingSuite. Below is an
example of narratives on AA loan statement.

5 MicroBankingSuite: Product
 Account Statement Narratives User Guide

Parameterisation
Parameterisation of account statement narratives is done from the Parameters >> Account Tables
section of the selected Role Based Home Pages.

The Narratives menu opens the enquiries/applications used in the parameterisation of the account
statement narratives functionality.

6 MicroBankingSuite: Product
 Account Statement Narratives User Guide

Narrative Parameters
The Narrative Parameters section presents the narrative parameters defined in the system.

The following columns are included in this list.

Column Description

Parameter Id Id of the parameter record. More details on this below.

Application Application for which narrative formats are defined on this

parameter record.

Narrative Format List of the narrative formats linked in this parameter record.

The options displayed above the list or beside each narrative parameter, execute the following
functions:

Option Description

New Parameter Opens Narrative Parameter application for new record input.

View Parameter Opens Narrative Parameter record for viewing.

Edit Parameter Opens Narrative Parameter record for editing.

List Formats List all multi-language Narrative Format records for the selected
narrative format.

Narrative Parameter
Narrative Parameter application allows input/editing of the parameter records.
The parameter (record) Id can be defined as:

7 MicroBankingSuite: Product
 Account Statement Narratives User Guide

 2-character value referencing SYSTEM.ID stored on the statement entry being processed
and raised by the system’s application. Let’s call it the application main parameter
record. E.g. for entries raised:
- by FUNDS.TRANSFER application, SYSTEM.ID is FT
- by TELLER application, SYSTEM.ID is TT
- by PD.PAYMENT.DUE application, SYSTEM.ID is PD
- by AA.ARRANGEMENT.ACTIVITY application, SYSTEM.ID is AAAA, but in this
application it will be defined as AA
 2-character value referencing SYSTEM.ID concatenated with transaction type available in
the underlying application. Let’s call it the transaction specific parameter record. Such
Id format allows linking of narrative formats over multiple parameter records – to avoid
huge parameter record when many transaction types are used within
SYSTEM.ID/application – and to improve readability. The transaction type used when the
narrative is being built is taken from the application control field, as defined on the
application main parameter record. E.g.:
- Parameter record FT-BC will be used for statement entries raised by
FUNDS.TRANSFER transaction with TRANSACTION.TYPE = BC – as the
control field for FT is defined as TRANSACTION.TYPE.
- Parameter record TT-900 will be used for statement entries raised by TELLER
transaction with TRANSACTION.CODE = 900 – as the control field for TT is
defined as TRANSACTION.CODE.
During narrative build, when the transaction specific parameter is not defined, then the application
main parameter is used. I.e. the transaction specific parameter takes precedence over the
application main parameter.
The application screen is presented below.

The following fields are available on this application:

Field Description

Statement Parameters Tab

Application Application for which narrative formats are defined on this

parameter record. This is the application raising the statement entry.

Field This field, together with Operand/Value, forms a sub-value set for
defining conditions for linking the narrative format given in the
Statement Format field below.

8 MicroBankingSuite: Product
 Account Statement Narratives User Guide

Here a field from the above Application for the condition check is
defined.

Operand Operand for the above condition check.

Value Value for the above condition check. This can be either a constant
value, or a special keyword:
 &&ACCOUNT&& - account number for which statement
narratives are being built.
 &&ARRANGEMENT&& - AA arrangement reference linked
to account for which statement narratives are being built.

Statement Format The narrative format to be used when the condition specified above
is satisfied. The main (default) language format should be linked
here, and if narratives are being built in a different language, the
respective language format will be used (if defined) automatically by
the system. Only narrative formats defined for the same application
used on the parameter record can be used.

Application Parameters Tab

Application Application for which narrative formats are defined on this

parameter record.

Control Field Optional field from the above application, that can be used in the
record id for more specific definition of the parameter records. E.g.
for FUNDS.TRANSFER, instead of linking all funds transfer
narrative formats on single parameter record with ID equal to FT, by
setting the Control Field to TRANSACTION.TYPE, it is possible to
define parameter records per FT transaction type (e.g. FT-AC, FT-
BC, etc.)

Read from history? This flag says whether the system should read transaction record
(for which narrative is being built) from history file. If not set, the
transaction record would be only read from live file.

Special Keywords
The two special keywords (&&ACCOUNT&& and &&ARRANGEMENT) are used for discerning
the debit/credit side of transaction or arrangement activity.
In this example:

For a FUNDS.TRANSFER transaction with type equal to AC (internal account transfer), if the
narrative is being built for the account that appears in the DEBIT.ACCT.NO field of the
transaction, the ACCT.TRANSFER.OUT-GB format is used (resulting in “Transfer to account …”
narrative). Similarly, when the narrative is being built for the account that appears in the

9 MicroBankingSuite: Product
 Account Statement Narratives User Guide

CREDIT.ACCT.NO field of the transaction, the ACCT.TRANSFER.IN-GB format is used (resulting

in “Transfer from account…” narrative).
In this example:

For AA.ARRANGEMENT.ACTIVITY transaction with activity equal to LENDING-SETTLE-

SETTLEMENT (settle via instructions), if the narrative is being built for the arrangement (account)
on which the activity was executed, the LOAN.NEW.ARRANGEMENT-GB format is used
(resulting in “New loan contract” narrative), otherwise the ACCT.LOAN.SETTLEMENT-GB format
is used (resulting in “Disbursed loan …” narrative).

10 MicroBankingSuite: Product
 Account Statement Narratives User Guide

Narrative Formats
The Narrative Formats section presents all narrative formats defined in the system.

The following columns are included in this list.

Column Description

Format Id Id of the format record. It is a free text followed by hyphen and

language id.

Description Description of the narrative format.

Application Application for which narrative format is defined.

The options displayed above the list or beside each narrative parameter, execute the following
functions:

Option Description

New Format Opens Narrative Format application for new record input.

View Format Opens Narrative Format record for viewing.

Edit Format Opens Narrative Format record for editing.

Narrative Format
Narrative Format application allows input/editing of the parameter records.

11 MicroBankingSuite: Product
 Account Statement Narratives User Guide

The following fields are available on this application:

Field Description

Description Narrative format description.

Application T24 application that generates the transaction for which the
narrative is being defined.

Field or Text This multi-value field defines the components of the narrative. In this
field either a valid field from the above Application can be defined,
or a constant text – enclosed in double quotes.

Conversion This sub-value field, defines conversions to be applied on the value

of the Field or Text field. List of the available conversions is provided
in the following paragraph.

Narrative Conversions
The table below list the conversions available in narrative format definition.

Conversion Description

VALUE-x Return multi-value position x

SUBVALUE-x Return sub-value position x

EXTRACT*x*y Return substring starting from character x and with length y

ABS Return absolute value (of a numeric value)

DDMMMYYYY Convert date in internal format to DD MMM YYYY

LINK>application>field Return field from linked application

FIELD[x,y] Return field number y from array delimited by x

CHANGE*x*y Replace value x with value y

12 MicroBankingSuite: Product
 Account Statement Narratives User Guide

FMT*x Convert value using FMT function and x format

TEXT”x” Return text given by x

PREFIX”x” Prefix field value with x

POSTFIX”x” Postfix field value with x

AUDITDATE Returns year YYYYMMDD of the audit DATE.TIME field value

AUDITTIME Returns time HH:MM of the audit DATE.TIME field value

ACCTSAMECUSTOMER Returns null value if the account with number given by field value
does not belong to the customer for whom account statement is
being built

ACCTOTHERCUSTOMER Returns null value if the account with number given by field value
belongs to the customer for whom account statement is being built

There can be multiple conversions applied on the same field. In the example below:

The following will happen:

 If account given in CREDIT.ACCT.NO (on the FT transaction) does not belong to the
customer for whom the statement is being built, this narrative component is set to null and
conversion process stops.
 Return category of the account given in CREDIT.ACCT.NO – read ACCOUNT and return
value of CATEGORY field.
 Return short name of the category extracted above – read CATEGORY and return value
of SHORT.NAME field.
 Return first value of SHORT.NAME field.
 Prefix the above value (short name) with “your “.
 Postfix the above value (your short name) with “ “ (space).

13 MicroBankingSuite: Product
 Account Statement Narratives User Guide

AA Parameters
The AA Statement Parameter application is used for parameterising display of financial
components of an AA transaction.
Record Id is in format <aa_product_line>-<language_code>, thus it is allowed to configure display
separately for different AA product lines and different languages.

Field Description

Properties Tab

Property Class Property class of the financial component. This is a multi-value field.
Financial components on a statement will be displayed in the order
in which the property classes are defined on this record (using the
above example: first ACCOUNT – principal, then INTEREST –
interest, then CHARGE – charges).

Property Name Name of the property for the financial component available in the
property class. This is a sub-value field under Property Class.

Property Description Description of the property to be displayed on the statement – as

the financial component description.

14 MicroBankingSuite: Product
 Account Statement Narratives User Guide

Field Description

Balances Tab

Property Class Property class of the financial component. This is a multi-value field,
for display only – as defined on the previous Properties screen.

Group Name Balance group name. This is a sub-value field under Property Class.
Balance group links together different AA balance types in the
property class, e.g. movement on GRC, DEL, NAB balances is
grouped into OVERDUE balance group. This is so that on the
statement, movement on any of these balances would be described
as overdue.

Group Description Description of the above balance group, to be displayed on the

statement.

Balance Type Balance type (prefix). This is a sub-value field under Property Class.
This field together with Balance Group below allows assigning
balance types to balance groups.

Balance Group Balance group the above balance type should be assigned to.

15 MicroBankingSuite: Product
 Account Statement Narratives User Guide

Field Description

Narratives Tab

Property Class Property class of the financial component. This is a multi-value field,
for display only – as defined on the previous Properties screen.

Credit Condition This sub-value field under property class, defines condition for
displaying the credit narrative format given in the Credit Narrative
field (on the right). It can be either:
 <balance_group>-<property>, which means that the
respective credit narrative will be used if there is a credit
movement on the <balance_group> of the <property>. The
<balance_group> must be one of the groups defined in the
previous screen for the respective property class of the
<property>.
 “DEFAULT” text, which means that the respective credit
narrative will be used if no balance/property specific
condition is found. The default condition should be always
defined as the first condition.

Credit Narrative The credit narrative (i.e. for credit movement). The narrative can
include special keywords:
 &&PROPNAME&& - name of the property on which there is
balance movement, as defined in the Properties tab.
 &&BALGROUP&& - name of the balance group in which the
movement happened, as defined in the Balances tab.

Debit Condition This sub-value field under property class, defines condition for
displaying the debit narrative format given in the Debit Narrative field
(on the right). It can be either:
 <balance_group>-<property>, which means that the
respective debit narrative will be used if there is a debit
movement on the <balance_group> of the <property>. The
<balance_group> must be one of the groups defined in the
previous screen for the respective property class of the
<property>.
 “DEFAULT” text, which means that the respective debit
narrative will be used if no balance/property specific

16 MicroBankingSuite: Product
 Account Statement Narratives User Guide

condition is found. The default condition should be always

defined as the first condition.

Debit Narrative The debit narrative (i.e. for debit movement). The narrative can
include special keywords:
 &&PROPNAME&& - name of the property on which there is
balance movement, as defined in the Properties tab.
 &&BALGROUP&& - name of the balance group in which the
movement happened, as defined in the Balances tab.

In the record above, Credit Condition defined as OVERDUE-ACCOUNT, means a credit

movement on the OVERDUE group (so credit on GRC, DEL, NAB balance), for ACCOUNT
property. In such case, the component narrative will be ‘Repaid &&BALGROUP&&
&&PROPNAME&&’, which in the end will display as ‘Repaid Overdue Principal’ – the keywords
will be replaced by the descriptions defined for balance group and property.

17 MicroBankingSuite: Product
 Account Statement Narratives User Guide

Notes
Use this page to record your own notes.

18 MicroBankingSuite: Product