CRS Setup

Transact Common Reporting Standards Implementation

TR3PRCRS - R22 Revision 1 English

©2023 Temenos Headquarters SA - all rights reserved.

Copyright Notice
©2023 Temenos Headquarters SA - all rights reserved.

Warning: This document is protected by copyright law and international treaties. Unauthorised reproduction
of this document, or any portion of it, may result in severe and criminal penalties, and will be prosecuted to
the maximum extent possible under law.

Disclaimer
Warning: Any mention of files, links to files or hyperlinks is strictly informational. Files, links to files or
hyperlinks are only valid for the TLC Classroom Training and NOT TLC Online.
 Lesson Overview

I am going to Parameter CRS Corporate CUST.REASONABLENESS.CH Aggregation

CRS.CUST.SUPP.INFO
describe Tables Customers ECK.PARAMETER Process

©2023 Temenos Headquarters SA - all rights reserved.

 Parameter Tables
ST.REGULATORY.PARAMETER - tracks the regulations releases - performs checks before
releasing the new functionality for the existing regulations. ID will be the regulations set
name

RT.REGULATORY.RULES – Holds the indicia rules for client identification and field mapping
rules to the CRS.CUST.SUPP.INFO

CRS.PARAMETER - regulations specific parameter file - holds the high level details
required for the regulations such as the effective date of the regulations, participating
jurisdictions, reporting currency, etc. ID will be the company code

ST.AGGREGATION.PARAM - Rules required for the balance aggregation process of pre-

existing accounts such as the frequency to perform the balance aggregation process,
relation level, relation codes and the criteria to exclude from the balance aggregation
process by the regulation rules. ID <Regulations set name>-<Company code>
©2023 Temenos Headquarters SA - all rights reserved.
 Parameter Tables » ST.REGULATORY.PARAMETER
ID of ST.REGULATORY.PARAMETER should be a valid Regulation set ID like CRS
The field CURR.RULE.BOOK holds date of Regulations set. Range starts of 1950 – 2049, anything before and
after the specified year would throw an error.
Once the year is amended and authorised the previous values get updated in the field PREV.RULE.BOOK
AUTO.CREATE.RECS for CRS record is to check whether indicia updation or automatic creation of
supplementary info records allowed or not
YES – CCSI records are created only when a customer has one or more indicia conditions present
ALL – CCSI records are created for all CUSTOMERs irrespective of whether one or more indicia
conditions are present on the CUSTOMER record
INDICIA.CUST.SELECT.API field is to define the API that returns the customers to be processed in automatic
creation of CCSI service.

©2023 Temenos Headquarters SA - all rights reserved.

 Parameter Tables » RT.REGULATORY.RULES
RT.REGULATORY.RULES is a parameter table which enables the user to define indicia
calculation rules for CRS and define the mapping of fields for the creation of the CCSI for
customers

This application for CRS constitutes the Customer Identification rules, Document rules
and Indicia Determining rules with the CCSI tables.

Users can define the field mappings that are to be used to populate the CCSI record and
configure the mapping process for the indicia related fields.

Once the mapping is configured, the CRS record is automatically created for customers
(AUTO.CREATE.RECS in ST.REGULATORY.PARAMETER = YES, RT.CREATE.REGULATORY.RECS
and ST.IDENTIFY.INDICIA services to be set as Auto)

Note: By Default, CCSI record will be updated for the seven Indicia available in the core.
The user can create different other rules for Indicia mapping using this application.

©2023 Temenos Headquarters SA - all rights reserved.

 Parameter Tables » RT.REGULATORY.RULES
Field Name Allowed Value Description
BASE.ID.TABLE A record from PGM.File Holds details about the base table that is used by the process

BASE.TABLE.KEY Mandatory input when Sys or This field specifies how the base table is linked to the application
User Linked app given defined in the corresponding User or sys linked app.

DESC Description To mention the description of the Rule Purpose

RETURN.RESULT YES - Return the Result This field specifies whether the result of the check is to be
NO – Do not Return the returned or not. Options available
Result
YES*ERROR - Return the error
to the calling routine

RT.REGULATORY.R
The ID of the Customer Reasonableness Check Parameter can be
ULES.ID
any free text ID ending with .CORE are used for internal purposes

RULE.API a valid record in EB.API This field holds the API to process the rule
©2023 Temenos Headquarters SA - all rights reserved.
 Parameter Tables » RT.REGULATORY.RULES
Filed Name Allowed Value Description
RULE.FIELD This field holds the conditions that are to be checked
• Value can be in the format
ApplicationName>FieldName. Fieldname must be a
valid system/local field in the application defined.
• Value can also be @ followed by Api Name,
where Api name should be valid record in EB.API.
• Value can be any RULE.TYPE that is previously
defined.

RULE.NUM This field holds a random number to this particular rule or

any number till 999
logic check
RULE.OPERAND This field must contain a value when the associated Operation to be performed on the field defined in
set field - RULE.FIELD is defined RULE.FIELD
RULE.RESULT Should be in the format IF TRUE/FALSE Statement This field holds The actual result to be returned to the
ELSE Statement calling routine. Could be based on the condition defined
in RULE.FIELD or could be any free text.

©2023 Temenos Headquarters SA - all rights reserved.

 Parameter Tables » RT.REGULATORY.RULES
Field Name Allowed Value Description
RULE.TYPE Value can be Alpha This field holds the name of the particular rule or logic check
numeric
RULE.VALUE Can be any free text or This field holds the value to be checked for the definition given in
Application>FieldName RULE.FIELD along with the RULE.OPERAND.
RULE.VERIFN any number till 999 This field specifies the dependent rule number after which this
particular rule is to be processed.
SYS.LINKED.APP Noinput field. This field specifies the applications that are used in the
RULE.FIELD set
USER.LINKED.APP Only for the applications This field specifies the applications that are used in the Rule Apis
defined in Sys or User
linked app will be tracked
for changes to process the
rule

©2023 Temenos Headquarters SA - all rights reserved.

 Parameter Tables » RT.REGULATORY.RULES

©2023 Temenos Headquarters SA - all rights reserved.

 Parameter Tables » CRS.PARAMETER
CRS Parameter – Customer Company wise records

Field Name Details

EFFECTIVE.DATE Effective date of agreement for the regulatory – back dated date available. Used to
identify the customers as existing or new based on this date.

PARTNG.JURIDICTION Countries participating with regulatory requirements

TELEPHONE.CODE International Digit code of PARTNG.JURIDICTION, e.g. +44
INDICIA.CALC.RTN Routine to calculate the Indicia Status. If no routine Indicia strength is not calculated.

AUTO.STATUS.UPDATE If Indicia changes system to work out Indicia irrespective of Customer reporting status

ACCOUNT.TYPE Used to define different types of accounts used for classification

ACCOUNT.SUB.TYPE Further classification of the account type such as HIGH or LOW based on which
balance aggregation is being performed

©2023 Temenos Headquarters SA - all rights reserved.

 Parameter Tables » CRS.PARAMETER
Field Name Details
CLOSE.REL.BAL.TYP If the previous day customer balances should be calculated when the
CRS.STATUS is changed to INACTIVE
REPORTING.CCY Specify the currency to be used for Balance aggregation process
INITIAL.AGGR.BUILT Identify whether the initial aggregation process is performed for all the existing
customers. Updated YES after first aggregation
BAL.AMT.AGGR.FROM Lower range and upper range of the aggregation amount for the corresponding
BAL.AMT.AGGR.TO ACCOUNT.TYPE this will be used during account classification for the existing
accounts
DUE.DILIGENCE.DATE Specifies the dates for the following account types: Pre-existing Individual Low,
Pre-existing Individual High, Pre-existing Entity High

REPORTING.DATE Reporting date for the above stated account types and it can be either today or
future dates
SC.GRACE.DAYS Maximum number of days within which the client is supposed to submit his Self-
Certification Document. This field is used to calculate the CUT.OFF.DATE when
the REQ.DATE is specified in CRS.CUST.SUPP.INFO.
EIN Holds the identification number used by the sending tax administration to
identify the Entity Account Holder
©2023 Temenos Headquarters SA - all rights reserved.
 Parameter Tables » CRS.PARAMETER
Field Name Details
TELE.CONT.TYPE Specifies the contact type for the telephone number to be considered for telephone
indicia calculation. Chosen option will be compared to Contact type field value in
customer record

POA.CODE Specifies the relation code to be referred for POA indicia calculation. POA can be
calculated at Customer level and arrangement level.
For Customer level, relation code will be prefixed with CU- <Relation code>
For Arrangement level, relation code will be prefixed with AA- <AA.CUSTOMER.ROLE>

INCARE.OF Specifies the In Care Address Purpose, which is considered for identifying In Care indicia.
Chosen option will be compared to Address purpose field value in customer record

©2023 Temenos Headquarters SA - all rights reserved.

 Parameter Tables » CRS.PARAMETER

Country specific regulatory changes in CRS can be easily adapted without changing the
core CRS module
Now, Transact will allow country specific customization for which new fields have been
introduced.

Field Name Details

COUNTRY.RULE Individual/Null – One XML record per customer as per OECD standard format
Bulk - which will produce one merged XML record per company by triggering merger
routine.

EB.TRANSFM.KEY 1st value – used to apply XSLT on individual CRS.REPORT.BASE records

2nd multivalue – This is must when country.rule is Bulk. It is used to apply XSLT on
merged XML file

©2023 Temenos Headquarters SA - all rights reserved.

 Parameter Tables » CRS.PARAMETER

Bulk – Bulk XML

Individual – records per
One XML record per company. EB
customer transform key is
mandatory.

EB.TRANSFORM- It has the mapping XSLT format for final reporting.

Ex: CRS.LUXEMBOURG.XSLT contains Luxembourg regulatory reporting format

©2023 Temenos Headquarters SA - all rights reserved.

 Parameter Tables » CRS.PARAMETER » Rules Mapping
Once the rules have been defined for the CRS indicia in RT.REGULATORY.RULES, the user should
link the field mapping with the RULE.TYPE and RULE.ID fields.

RULE.TYPE & RULE.ID becomes mandatory when the field AUTO.CREATE.RECS for CRS is set to YES
in ST.REGULATORY.PARAMETER

©2023 Temenos Headquarters SA - all rights reserved.

 Parameter Tables » CRS.PARAMETER » Document Synchronization
In CRS.PARAMETER, the field REQD.DOC.TYPE is used to indicate documents related to CRS
processing

When a Financial Institution maintains and updates documents through Temenos Transact Document Management
module, the details of the forms related to CRS can be automatically synchronized to CCSI record.

These documents are user configurable in the CUST.DOCUMENT,

CRS.PARAMETER and RT.REGULATORY.RULES applications.

The CRS.CUST.SUPP.INFO records for the customers are automatically updated for the document information through
ST.IDENTIFY.INDICIA/ST.UPDATE.INDICIA jobs, based on the mapping definitions in
the RT.REGULATORY.RULES application.

Following fields in CCSI are updated, SELF.CERTIFICATION, SC.CUST.REF, SC.REQ.DATE, SC.RECV.DATE, SC.CUT.OFF.DATE
and SC.DOC.STATUS based on the various stages of document submission

©2023 Temenos Headquarters SA - all rights reserved.

 Parameter Tables » CRS.CLIENT.TYPE
The purpose of this table is to make a connection between different combinations of
CUSTOMER field values to a specific CRS Client Type; e.g. Sector 1001 and Target 1 are
INDIVIDUALS.

This table allows us to override the mapping rules set at CRS.PARAMETER level and
specify individual rules that apply to only one CRS Client Type.

©2023 Temenos Headquarters SA - all rights reserved.

 Parameter Tables » CRS.CLIENT.TYPE

Field Name Details

Description Descriptive information for the type of customer
CRS.CODE Valid CRS code under which this client type is classified. This value defined in this field is
used to classify the CCSI Customer as either INDIVIDUAL/ORGANISATION.
Value is any of the following:
CRS101 - ENTITY- REPORTABLE.PERSON
CRS102 - INDIVIDUAL
CRS103 - ENTITY-PASSIVE.NFE
REST - Additional for the client types who doesn't fall under above three categories yet to
be reported.
RULE.TYPE Group of fields used to override the general mapping rules established in CRS.PARAMETER
for one particular CRS Client Type.
RULE.TYPE – possible values Indicia <rule to use for indicia identification> or Mapping
RULE.ID <rule to use for mapping CRS.CUST.SUPP.INFO field values from Customer record>
RULE.ID – value from RT.REGULATORY.RULES table, where all mapping rules are defined
and stored.

©2023 Temenos Headquarters SA - all rights reserved.

 CRS.CUST.SUPP.INFO
CRS.CUST.SUPP.INFO - table holds the supplementary information for a customer related
to CRS.

ID is Customer ID - To be created for customer as necessary. Automatic creation of CCSI

record for customers are possible based on set up at ST.REGULATORY.PARAMETER

Holds information pertaining to Indicia Specification and Basic Customers information

inclusive of KYC, self certification

Date of Birth of the Individual / Date of incorporation for entities defaulted

Determines if Reporting FI obtained self certification as part of account opening

Applicable for Pre-existing Entity High, New Individual Accounts and New Entity Accounts

©2023 Temenos Headquarters SA - all rights reserved.

 CRS.CUST.SUPP.INFO » Automatic Creation of CCSI
AUTO.CREATE.RECS in ST.REGULATORY.PARAMETER for CRS record is to check whether indicia updation or
automatic creation of supplementary info records allowed or not

ST.IDENTIFY.INDICIA is a service to identify and automatically calculate indicia and;

• Automatically create the CRS.CUST.SUPP.INFO record for newly Active customers
• Automatically create the CRS.CUST.SUPP.INFO record for existing customers who have not previously warranted a
CRS.CUST.SUPP.INFO record.
• Automatically update the existing CRS.CUST.SUPP.INFO record (if any) prompted by changes to customers static
data.

• ST.INDICIA.TRIGGER is the trigger file, which keeps track of the customers whose indicia related fields are
amended.

©2023 Temenos Headquarters SA - all rights reserved.

 CRS.CUST.SUPP.INFO » CRS Territories
▪ CRS module supports the functionality for mapping CRS territories to their associated
fiscal jurisdiction and recording several phone prefixes for the same ISO country code.

©2023 Temenos Headquarters SA - all rights reserved.

 CRS.CUST.SUPP.INFO
Field Name Details
CRS.CUSTOMER.TYPE State if the customer is an ‘Individual’ or an ‘Entity’.
If Entity’, then further granular level classification
KYC.CHECK Indicates if KYC check is performed
SELF.CERTIFICATION Determines whether the Reporting Financial Institution has obtained a self-certification as part of
the account opening documentation to determine Account Holder’s Residence for tax purposes.

BIRTH.INCORP.DATE Birth date or Company Incorporation date, this information will be returned from underlying
Customer fields
BIRTH.INCORP.PLACE Birth place or Company Incorporation place
TAX.RESIDENCE Tax Residence of the customer based on the self-certification
Multivalued when customer has more than one tax residence
TAX.IDENTITY.NO Tax Identification Number (TIN) – associated to tax residence
ADDRESS.TYPE Country address of customer - inline with Indicia checks for customer address

ADDRESS.COUNTRY Country code for the above address

TELEPHONE.NO Telephone Number of the Customer in the following format, e.g.+44-123456

TELEPHONE.COUNTRY Arrived at based on the code prefix used

©2023 Temenos Headquarters SA - all rights reserved.
 CRS.CUST.SUPP.INFO
Field Name Details
STANDING.INSTRUCT Country code if customer is having standing orders
POA.HOLDER.COUNTRY Country code of power of attorney or authorised signatory
ROLE.TYPE Details of the Controlling Persons of Entity – enabled only when CRS client type is selected
as Entity - Passive NFE
CUSTOMER.ID Transact ID of controlling person if available for customer
CUSTOMER.NAME To populate Name of controlling person if customer ID not available
CUSTOMER.REFERENCE Unique ID reference of controlling persons specified above
DATE.OF.BIRTH Date of birth of the Controlling Person
PLACE.OF.BIRTH Place of Birth of the Controlling Person
RT.TAX.RESIDENCE Tax Residence of the Controlling Person
TIN Tax Identification Number (TIN) of the Controlling Person
CTRLG.PERSON.TYPE This field holds the CRS code under which the controlling person will be classified. This is
to populate the tag CtrlgPersonType tag in the report.
ADDRESS This field is used to store the address of the Role Type person
©2023 Temenos Headquarters SA - all rights reserved.
 CRS.CUST.SUPP.INFO
Field Name Details

INDICIA ‘Yes’ if any of the indicia's are met else No

REP.JURD.RES Store Residence for more than one Reportable Jurisdiction

REP.WAIVER.REVD Indicates if a Waiver document has been received by the FI from the Customer if they
want their Account Information to be Non-Reportable

CRS.STATUS Reportable or Non-Reportable or Inactive

STATUS.CHANGE.DATE Date on which the CRS.STATUS is changed to INACTIVE. Used for calculating the previous
day's customer balances

CHANGE.REASON Descriptive field to record the reason, if the CRS.STATUS populated by the system is
changed by the user

LAST.AGGR.DATE The date on which the last aggregation for the customer
happened
©2023 Temenos Headquarters SA - all rights reserved.
 CRS.CUST.SUPP.INFO
Field Name Details
SC.CUST.REF Holds the customer reference or holder reference given in the field CUSTOMER.REFERENCE
who has submitted SC document

SC.REQ.DATE Date on which the self-certification form is required

SC.RECV.DATE Date on which the self-certification form is received
SC.CUT.OFF.DATE Date within which the self-certification form is to be submitted including the grace period.

SC.DOC.STATUS This field will hold the value “UNDOCUMENTED” when the self-certification document is not
submitted by the client even after the cut-off date

These fields are used to show the indicia conditions if any and the respective jurisdiction
INDICIA.SUMMARY For example, When the customer’s residential address Country Code is United Arab Emirates,
and the fields are set as below:
INDICIA.COUNTRY Indicia Summary – Residence
Indicia Country – AE

©2023 Temenos Headquarters SA - all rights reserved.

 CRS.CUST.SUPP.INFO » Static Changes
In Transact, customer static information like Residence, Address, Telephone Details & Power Of Attorney
Details are stored in CUSTOMER, DE.ADDRESS/DE.CUSTOMER.PREFERENCES table.

Any change in the information in these table, indicia will be recalculated which triggers indicia update in
work file named ST.INDICIA.TRIGGER

Batch Job ST.UPDATE.INDICIA which monitors selected changes to the CUSTOMER, DE.ADRESSS,
DE.CUSTOMER.PREFERENCES, AA.ARRANGEMENT & TZ.PAYMENT.REPORTS

Any appropriate update in data then the indicia on the CRS.CUST.SUPP.INFO record is updated in cob process

©2023 Temenos Headquarters SA - all rights reserved.

 CRS.CUST.SUPP.INFO » Static Changes
Application Fields Referred Indicia
Residence Residence
Address Purpose InCare
PoBox number PoBox
Contact Type
CUSTOMER IDD Prefix Telephone Number
Contact Data
InCare, PoBox, Hold mail,
Address Country
Power of Attorney
Relation Code
Power of Attorney
Rel Customer
Hold Output
Hold Mail Start
DE.ADDRESS Hold Mail
Hold Mail End
Address Country
Hold Output
DE.CUSTOMER.PREFERENCES Hold Mail Start Hold Mail
Hold Mail End
AA.ARRANGEMENT.ACTIVITY Customer. Role Power of Attorney
Mapping as per
BIRTH.INCORP.PLACE of CCSI Country of Incorporation
RT.REGULATORY.RULES
©2023 Temenos Headquarters SA - all rights reserved.
 CRS.CUST.SUPP.INFO » Static Changes

Application Fields Referred Indicia

TZ.PAYMENT.REGULATORY.REPORT Payment Country

Account with Bank Country

Acct with Bank Standing Instruction
STANDING.ORDER
Bic Iban Ben
Iban Ben
Acct with Bank
BENEFICIARY Iban Ben
BIC Iban Ben

©2023 Temenos Headquarters SA - all rights reserved.

 CRS.CUST.SUPP.INFO » INDICIA » Country of Incorporation
Country of Incorporation is considered as CRS Indicia for Legal entities
CCSI record that has CRS.CUSTOMER.TYPE value of CRS101 and CRS103 are legal entities
BIRTH.INCORP.PLACE field in CCSI holds Country of Incorporation for legal entity.
For this legal entity, system will consider Country of Incorporation as CRS Indicia
If Country of Incorporation is Participating Jurisdiction under CRS, then this customer will be considered as Reportable

Client type with

CRS101 and CRS103
are Legal entities

©2023 Temenos Headquarters SA - all rights reserved.

 CRS.CUST.SUPP.INFO » INDICIA » Country of Incorporation

CRS.CLIENT.TYPE is ENTITY-
REPORTABLE.PERSON which
is CRS101. Its
BIRTH.INCORP.PLACE is SG
which is Participating
Jurisdiction under CRS.
Hence CRS.STATUS is
marked as REPORTABLE.

Note: BIRTH.INCORP.PLACE for individual customer is not considered as an indicia

©2023 Temenos Headquarters SA - all rights reserved.
 CRS.CUST.SUPP.INFO » INDICIA » Standing Instruction
Standing order indicia is identified based on the recurring payments transferred to a
beneficiary account and maintained in a reportable jurisdiction.
From R21, the Standing order Indicia processing functionality is based on the standing order or deposit
arrangement.

Recurring payments can occur through deposit arrangements/standing orders and are
identified based on the following conditions:

• Deposit arrangements with payout property and payout beneficiary defined in settlement
condition with more than three payment schedules from the effective date of the activity.

• Standing orders of Fixed Type (FI) Or Balance Outward (BO) Type .

Standing instruction indicia is met, if the pay-out beneficiary country is participating

jurisdiction under CRS

©2023 Temenos Headquarters SA - all rights reserved.

 CRS Corporate Customers » CRS.CLIENT.TYPE
Indicia identification differs for
individuals and corporates hence system
should have the capability to distinguish
the customers.

CRS.CUSTOMER.TYPE field in CCSI

application indicates the type of customer. INDIVIDUALS

Automatic indicia identification process

would categorize a customer as either
INDIVIDUAL or ENTITY. ENTITIES/CORPORATES

©2023 Temenos Headquarters SA - all rights reserved.

 CRS Corporate Customers » RT.REGULATORY.RULES
▪ CRS INDICIA MAPPING rules must be defined for Corporate customers for the additional 2
fields:
▪ Controlling Person Residence
▪ Entity Headquarters

©2023 Temenos Headquarters SA - all rights reserved.

 CRS Corporate Customers » CCSI

©2023 Temenos Headquarters SA - all rights reserved.

 CUST.REASONABLENESS.CHECK.PARAMETER
As per CRS regulations, all financial institutions should undertake reasonableness tests for all the CRS
customers to check any inconsistencies on CRS information

CUST.REASONABLENESS.CHECK.PARAMETER must be configured

In this application, define parameters or sources used for checking the reasonableness of CRS customers

©2023 Temenos Headquarters SA - all rights reserved.

 CUST.REASONABLENESS.CHECK.PARAMETER
ID should be CRS for the record of reasonableness check of CRS customers
‘Onb Tax Ctry From and To’ &
‘Post Onb Chk Ctry From and To’ are set of multivalue fields used to define the
applications and the fields that are to be checked for reasonableness test during
onboarding and post onboarding phase.

©2023 Temenos Headquarters SA - all rights reserved.

 CUST.REASONABLENESS.CHECK.PARAMETER
In CRS.CUST.SUPP.INFO ;
TIN.NOT.PROVIDED.CODE and TIN.NOT.PROVIDED.REASON are the fields to capture the cause for non
submission of TIN
TIN.NOT.PROVIDED.CODE – Mandatory field when Tax Identity No. is not given. Field has three Options to
specify the reason code when TIN is not provided. OECD permitted values are
• A - If the account holder’s residence country does not issue TIN to its residents
• B - Otherwise if the account holder is unable to obtain TIN. Specify the reason in Tin not provided reason field
• C - TIN is not required. Select only when the relevant country/jurisdiction does not require the collection of TIN
issued.

TIN.NOT.PROVIDED.REASON - Field to specify the reason for not providing TIN. Mandatory field when
TIN.NOT.PROVIDED.CODE is selected as B

©2023 Temenos Headquarters SA - all rights reserved.

 CUST.REASONABLENESS.CHECK.PARAMETER

©2023 Temenos Headquarters SA - all rights reserved.

 CUST.REASONABLENESS.CHECK.PARAMETER » Enquiry
CRS.REASONABLENESS.CHECK is an enquiry used for bank users to perform reasonableness check

When there is no data inconsistency, enquiry result for CRS customer will be OK

Enquiry result will be NOK for below reasons

When in case of any inconsistencies in data (mismatch) in parameterized fields

Also when the parameterized fields has local jurisdiction

©2023 Temenos Headquarters SA - all rights reserved.

 Aggregation Process » ST.AGGREGATION.PARAM
ST.AGGREGATION.PARAM holds details required by the regulatory for the balance aggregation
ID is regulatory name and company code : CRS-GB0010001

©2023 Temenos Headquarters SA - all rights reserved.

 Aggregation Process » ST.AGGREGATION.PARAM
Field Name Details

RELATION.LEVEL If the relationships are defined at customer level in T24 CUSTOMER. However, if the
field is set to ACCOUNT, the relationships will be checked at individual account level
and only the balances of accounts that are held jointly will be attributed to all the joint
holders

CUSTOMER.RELATIONSHIP is now added as an option in addition to CUSTOMER &

ACCOUNT level relation. This allows banks to identify the relationship of the
reportable customer to the other customers via CUSTOMER.RELATIONSHIP table.

RELATION.CODE Details of related customers, whose balances are considered for aggregation
this relationship code definition is for aggregating the balance of other related
customers apart from automatic aggregations

©2023 Temenos Headquarters SA - all rights reserved.

 Aggregation Process » ST.AGGREGATION.PARAM
Field Name Details

ACCT.AGGR.RTN Local routine for balance aggregation batch jobs.

BAL.BUILD.RTN Local routine for balance aggregation batch jobs. flexibility to build the customer
balances.

EXC.FOR.ACCT Categories of accounts/deposits/products to be excluded from aggregation

process

EXC.RULE.APPL name of the application to be excluded from the balance aggregation process.
Only SAM is allowed in this field now

EXC.RULE.FIELD Interdependent fields. All must be populated or left blank.

EXC.RULE.OPERAND System fields and local reference fields from application allowed with operands
EXC.RULE.VALUE as NE or EQ and the values and
comparison value

©2023 Temenos Headquarters SA - all rights reserved.

 Aggregation Process » ST.AGGREGATION.PARAM
Field Name Details

ENT.CUST.FIELD Fields names from Customer table

ENT.CUST.OPND Operands as NE or EQ and the values and
ENT.CUST.VAL Fields values from Customer table

CUS.REL.ROLE & CUSTOMER.RELATIONSHIP role and CUSTOMER.RELATIONSHIP group to be used for

CUS.REL.GROUP balance aggregation

Closed Accounts/contracts should also be shared between different

ST.AGGREGATE.BALANCES based on relationships

AA.CUSTOMER.ROLE defined in ST.AGGREGATION.PARAM should be considered for

balance aggregation and shared reporting for both live and closed AA retail accounts
and contracts.

Remember : The assets positions of the Customer will be considered from the Transact
'AC’ ‘AA’ 'LD' 'MM' and 'SC' modules
©2023 Temenos Headquarters SA - all rights reserved.
 Aggregation Process » ST.AGGREGATE.BALANCES
Live Table- contains aggregated balances of a customer.
Positions are considered from 'AC' ‘AA’ 'LD' 'MM' and 'SC' module.
Built during month end COB
ID : Regulation name, customer number along with the date of the balance aggregation
Aggregated balance will be created for each regulation and customer.
Drill Down Enquiry is available to view aggregate balances break-up of all accounts held by a
customer

©2023 Temenos Headquarters SA - all rights reserved.

 Lesson Summary

Parameter CRS Corporate CUST.REASONABLENESS.C

I described CRS.CUST.SUPP.INFO Aggregation Process
Tables Customers HECK.PARAMETER

©2023 Temenos Headquarters SA - all rights reserved.

Thank you

tlc.temenos.com