R22AMR ReleaseHighlights
R22AMR ReleaseHighlights
R22 AMR
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.
3
Analytics
Analytics
Analytics
5
Analytics
6
Analytics
features:
l Triggering the jobs along with the EOD processes, as and when required.
l Addition of Read ADS designer component to read data from ADS target
database.
7
Analytics
The AEH Consumer component reads the data from Azure Event Hub (AEH)
whereas, the AEH Producer and Kafka Producer components write the data to
AEH and Kafka, respectively in JSON and Avro formats. Also, the Kafka
Consumer component is enhanced to read data in JSON and Avro formats.
l Select columns
l Provide file names
l Define number of files to be generated
l Change the column formats (data type and timestamp type)
l Transfer generated file to remote systems (FTP, SFTP and FTPS)
8
Analytics
functionalities:
l Datatype of the tables created in target Database are based on the source
and target data type mapping from MySQL database.
l A column can be made an identity column in target database based on the
metadata values.
l Based on the ‘tableType’ and ‘Stagingonly’ Metadata information, tables
are created in target database with all the provided constrains.
TDE now supports Keycloak authentication that allows single sign-on for Admin,
Designer, Deployer and Scheduler modules.
The modules such as TemenosMetaService (TMS) and Risk service that
expose REST endpoints to third party applications (like Semantic Query Layer
and IRIS) are also embedded to Keycloak features.
Users can reset the password using their mail ID and configure their password
policies.
9
Analytics
Data Hub (TDH), for any customer to export data from Transact.
10
Analytics
11
Analytics
and the record information is not available for re-run. A new work file,
DW.INCREMENTAL.BACKUP.WRK.FILE is now introduced, which retains the
records to be extracted for the last working day. This allows re-run of the
incremental service for the last business date.
12
Analytics
application without using single sign-on. Here, signing in and out of browser
applications is handled by TDE itself and in case of a forgotten password, it
provides the functionality to reset or obtain a new password.
Along with table level lineage, lineage at column level helps to understand the
transformation changes or transformation applied over individual columns.
13
Analytics
14
Analytics
15
Analytics
16
Analytics
l Date enrichment rule feature to design and evaluate the rules for APIs.
l Nested Condition in Condition Rule with multiple condition options.
l Field order input for response fields to identify in which order the schema
should be constructed.
l Datatype for extension field for evaluating the rule in expected format if
multiple rules are available in one extension field.
l Absolute operation in Calculation Rule to obtain absolute values.
17
Analytics
l Filter: this type of chart is used to apply a fixed filtering parameter on any of
the Information Tile within a Dashboard. This filter is applied by the
information tile and dashboard designer.
l Heatmap: this type of chart use colours to show data patterns and data
concentration at a glance. It consists of two categorical parameters
(allocated to the X and Y axes) and a numerical data series (used as a
data series).
l Treemap: this type of chart is used to capture the value of individual data
points within the structure of a hierarchy of parameters.
l Bubblechart: this type of chart is used to represent data patterns through a
bubble-shaped elements in diagram.
18
Analytics
19
Analytics
20
Analytics
21
Analytics
Value at Risk (VaR) calculations at the holding and portfolio levels. You must
create a classification rule for the component, to use it in VaR calculations and
you can schedule it to run on an adhoc basis or a scheduled frequency (daily,
monthly, and quarterly). This feature provides flexibility for the end-user to
modify calculation parameters, perform intra-day calculations and near-real time
VaR calculations.
22
Analytics
23
Analytics
When retrieving data, query options can be used to set criteria for the data
needed, and the report columns that should be returned.
To sum up, Quick Reports' data API endpoints allows users to:
24
Analytics
25
Analytics
26
Analytics
l Quick Reports
l Information Tiles
l KPIs
l Pivot Reports
27
Analytics
28
Analytics
29
Payments
Payments
Payments
United Kingdom » CHAPS Clearing » Bank
Transfer
Available from: 202105
Complying with the ISO 20022 message standard adopted by CHAPS, the
SWIFT MT messages are replaced with the ISO20022 XML (pacs.009 format)
messages. This functionality allows banks, using the Temenos Payments Hub,
to handle the inward and outward interbank payments from CHAPS in
ISO20022 (pacs.009) format.
31
Payments
32
Payments
33
Payments
34
Payments
level for Cross Border Payments and Reporting Plus (CBPR+) payments. This
information is passed to Delivery (DE) module so that the DE module can add
technical headers based on the configured interface. The exit API provision by
Temenos Payments enables banks (L3) to add technical headers on top of the
transformed data (payload) before sending the file to the network or clearing
interface.
35
Payments
36
Payments
37
Payments
Temenos Payments can receive a pacs.009 cover from CHAPS clearing, and
generate an outward or redirected cover in pacs.009 cover format to CHAPS
based on the configuration.
38
Payments
payment, and inform the bank to perform FX posting if an Inward Instant payment
is received with credit account currency different from the Transaction currency.
39
Payments
40
Payments
Temenos Payments can receive clearing directory from TIPS, save the same in
table, and use it to perform reachability check before releasing payments to
clearing. This functionality provides additional information such as maximum
amount accepted by other participant or participants in TIPS. This maximum
amount detail along with other details is included in the TIPS directory for each
authorised account user in TIPS (User BIC). Temenos Payments supports the
41
Payments
reachability check based on the threshold defined and helps in validating the
reachability of the counterparty bank.
42
Payments
43
Payments
44
Payments
45
Payments
46
Payments
47
Payments
48
Payments
49
Payments
logic is applicable for both bank initiated (recalls) and customer initiated (RFRO)
cancellation requests.
Tunisia » Clearing
Available from: 202108
The Clearing House in Tunisia (SIBTEL) has introduced the e-clearing system.
The e-clearing system is part of the modernisation of the Tunisian banking
system. It aims to reduce recovery times by means of reliable, secure, efficient
and fast electronic clearing.
This functionality allows banks to capture and validate the cheque collection
request for the cheques that are being presented for the first time (code 30) and
also for the cheques that are being represented (code 31, 32, 33).
50
Payments
Click here to understand the installation and configuration updates for this
enhancement.
51
Payments
52
Payments
Direct Debit
Supporting Continuous Gross Settlement Model in SEPA
Credit Transfer
Clearing Return Code
Supporting pain.002 Version 2 in TPH
Viewing LNR File Received in TPH for SEPA Direct Debit
Viewing LNR File Received in TPH for SEPA Credit Transfer
53
Payments
54
Payments
55
Payments
Click here to understand the installation and configuration updates for this
enhancement.
56
Payments
57
Payments
58
Payments
59
Payments
60
Payments
l TPH processes the customer payment pacs.008 having G005 service level
code as gpi payment (like G001).
l TPH sends pacs.002 (based on Relationship Management Application
(RMA)), if PPSWMX module is installed in following scenarios:
o When bank user manually accepts a gSRP request from the manual
action queue for a payment waiting for cover.
o When a MT299/trck.002 is received with RJCT status by the gpi
instructed bank and the payment has not reached final status.
61
Payments
Determination
Balance check and Reservation for fixing rate – Funds
Reservation
Balance check and Reservation for fixing rate – Forex
62
Payments
l Receive and map DRR sent to or received from TIPS through EBA RT1
Clearing, which contains the information related to transactions exchanged
with TIPS, in addition to the existing report containing EBA RT1
transactions.
l Receive RSF file for TIPS (through EBA RT1), in addition to the existing
RSF file received for EBA RT1. The DRR Enquiry format also displays
details of payments made to TIPS participants through EBA RT1. RSF
enquiry displays all the data such as, settlement with EBA RT1, TIPS
DCA, and TIPS Technical account as per the selection criteria.
These data received and mapped are displayed in a report format through an
enquiry.
63
Payments
64
Payments
Temenos Payments has now enhanced the ability of POA to support generating
59F in the outgoing MT message based on the user input in the payment. Even
if the user does not impose, TPH can now generate 50F in the outgoing MT
message based on the configurable parameter and if the required details are
present in customer table.
Temenos Payments is now enhanced to allow:
65
Payments
66
Payments
l SWIFT XML ISO based confirmation messages that are sent to tracker or
received from tracker are displayed in GPI confirmation list.
l New columns are introduced in GPI confirmation enquiry list to display
fields in SWIFT XML ISO based messages.
l The detailed view of confirmation details is shown as a new section in the
GPI confirmation enquiry list.
l Design of displaying party details is changed (each party displayed as a
row in the list) in GPI details screen.
l Additional parties in the SWIFT ISO payment chain are now displayed in
GPI details screen.
l The roles for each party in the payment chain in GPI details screen can be
renamed.
67
Payments
l SWIFT XML ISO based confirmation messages that are received from
tracker are displayed in GPI confirmation list.
l Additional columns in the GPI confirmation enquiry list are introduced to
display fields in SWIFT XML ISO based messages.
l The detailed view of confirmation details is shown as a new section in the
GPI confirmation enquiry list.
68
Payments
l Registering Proxy Id
l Resolving proxy of a requestor and payer during RTP initiation and
reception respectively
Banks can now use the proxy identifier to initiate an RTP request instead of
using an account number or an IBAN. The recipient (payer) can also be
identified by a proxy instead of account number or IBAN.
69
Payments
70
Payments
71
Payments
72
Payments
73
Payments
74
Payments
l Capture Liquidity Transfer Requests (LTR) from both Payment Order (PO)
and Order Entry (OE) to be sent to Target Instant Payment Settlement
(TIPS) clearing.
l Generate outgoing LTR to be sent to TIPS clearing.
l Process incoming response messages received from TIPS clearing
against the original LTR message.
75
Payments
(LTA) from Target Instant Payment Settlement (TIPS) clearing. The received
LTA undergoes a process to determine if it qualifies a payment booking. If
qualified as a payment, Temenos Payments resolves the market account
numbers received in the advice to internal accounts of the bank, till the payment
is done. Processing of LTAs’ helps the banks liquidity management team in
better management of the bank’s liquidity position with TIPS.
76
Payments
the ordering customers has to be available for a customer, for all types of
payments.
This functionality allows banks to capture the CUIT, CUIL or CDI of the ordering
customer for COELSA CT (Credit Transfer) or DD (Direct Debit) payments, and
store the value in the POR.SUPPLEMENTARY.INFO application.
77
Payments
78
Payments
79
Payments
l The user amends the value of the Fx Contract Id field and re-submits an
inward or outward cross-currency payment from the repair queue.
l Payee or requestor can provide the expiry time component during RtP
initiation.
l Payee or requestor can indicate whether the RtP request requires
immediate approval from the payer.
l The RtP framework can expire an RtP upon the receipt of rejection
message from clearing house due to timeout of the payer response.
Click here to understand the installation and configuration updates for this
enhancement.
80
Payments
81
Payments
82
Payments
83
Payments
entire N02s received for that batch. On reception of the N04 EOB, the system
will check to see for which batch the N04 is received. The system will identify
the corresponding record and cross check the total amount and count of the
entire CT in N04 with the total amount and count of batch. If there is a mismatch,
all the payments in the corresponding batch will not be processed and remain in
the 235 status.
84
Payments
execution date of the original instant credit transfer. The Additional Information
tag of camt.029 instant recall negative response has been updated to mandatory
and the multiplicity has been increased to 13. A new purpose code (RRTP) has
been published in the Equens rule book to link RTPs with instant payments.
85
Payments
86
Payments
l Fetch RtP requests for the payer from an established Pay UK Repository
Service Provider (RSP)
l Send the payer’s RtP response, due date extension requests, and notes to
the RSP
l Update the information for RtPs available in Temenos data store from the
RSP
87
Payments
88
Payments
89
Payments
90
Payments
l Generic TPR version with standard rules for MT and ISO messages.
l Analyse the non-STP ISO messages repaired by TPR.
91
Installation and
Configuration
Notes
Payments
Payments
Ensure that the AC, RC, and CQ modules are available. Read the respective
module for more information.
93
Payments
Configure the time zone in the COMPANY table to get the date and time in
specified time zone. If not configured, the system uses the UTC date and time.
94
Technical Notes
Payments
Payments
Temenos Payments » Warehousing Future
Dated Bulk Payments and Cancelling
Warehoused Bulk Payments in FTBM
Available from: 202105
96
Payments
97
Payments
TGTCLM-LAU-Compliance=MXKEYSTORE
TGTCLM-BAH-Compliance=
TGTCLM-APIName=
TGTCLM-IntegrityRequired=true
98
Payments
99
Payments
clearing or L3 team can fetch the multi BIC sender or receiver values.
l CORE_Settlement_BIC_NCC_Sender
l CORE_Settlement_BIC_NCC_Receiver
100
Payments
available only from the effective date configured in the record below.
NOTE: The date here is configured as 15 Apr 2021, for unit testing purpose.
101
Payments
The date here is configured as 15 Apr 2021, for unit testing purpose.
102
Regulatory
Compliance
Regulatory Compliance
The Batch and Real time Alert Managers of the Profile and Suspicious Activity
Prevention (SAP) modules are enhanced with additional fields, which allows the
user to view and add pre-configured dashboard charts based on customer
transaction and other parameters used. This functionality also enables to add
custom report charts in the dashboard and share the dashboard charts with other
users and enables the user to see the ordering/beneficiary customer’s risk
values in Profile and SAP Alert Evaluation page.
104
Regulatory Compliance
105
Regulatory Compliance
Click here to understand the installation and configuration updates for this
enhancement.
106
Regulatory Compliance
107
Regulatory Compliance
108
Regulatory Compliance
109
Regulatory Compliance
debited from or credited to the specific accounts. The created account groups
are used as parameters in different rule conditions in the Profile or SAP module
(both SAP and Real Time) to generate alerts. This helps to monitor the
transactions of suspicious accounts.
110
Regulatory Compliance
111
Regulatory Compliance
it and trigger alerts in the Customer Information File (CIF) Alert Manager. The
Watchlist Manager maintains the imported information as a public list.
112
Regulatory Compliance
messages are routed to the CIF scan queue (CIF alert manager).
113
Regulatory Compliance
114
Regulatory Compliance
115
Regulatory Compliance
Regulatory Compliance
116
Regulatory Compliance
117
Regulatory Compliance
118
Regulatory Compliance
Click here to understand the installation and configuration updates for this
enhancement.
Click here to understand the installation and configuration updates for this
enhancement.
119
Regulatory Compliance
Temenos Transact validates whether the user who gave consent still has
access to view the details of the requested account(s) in their online permissions
managed in Spotlight. This functionality provides support for PSD2 in an Infinity
architecture.
120
Regulatory Compliance
121
Regulatory Compliance
122
Regulatory Compliance
Click here to understand the installation and configuration updates for this
enhancement.
123
Regulatory Compliance
This functionality supports the ability to re-submit the CRS XML file for a specific
set of accounts.
This functionality supports the ability to re-submit the FATCA XML file for a
specific set of accounts.
FATCA.XML.REQUEST
FATCA.TAX.BASE
Resubmission of the FATCA XML File for a Specific Set of
Corrected Accounts
124
Regulatory Compliance
125
Regulatory Compliance
This functionality allows a user to capture multiple GIIN numbers when multiple
numbers are provided by customers and supports the correct GIIN format and
protects against user input error.
126
Regulatory Compliance
l Banks can takeover the charge-off and recovery balances for IFRS charge-
off from legacy system.
l Balances can be accounted based on the accounting requirements of
Non-Refundable Fees and Cost as per FAS91 requirements.
127
Regulatory Compliance
information along with the income and tax information required for reporting as
per IRS regulations.
128
Regulatory Compliance
129
Regulatory Compliance
130
Regulatory Compliance
Click here to understand the installation and configuration updates for this
enhancement.
131
Installation and
Configuration
Notes
Regulatory Compliance
133
Regulatory Compliance
Regulatory Compliance
CZ.ERASURE.PROCESS CZ.CUS.PRE.ERASURE.PROCESS
CDP.BUILD.PORTABLE.RESULT CZ.CDP.ACCESSIBILITY.PRE.PROCESS
134
Regulatory Compliance
CDP.BUILD.ACCESS.RESULT CZ.CDP.ACCESSIBILITY.PRE.PROCESS
With the above set up in one of the batch records, all type of requests captures
are moved to $HIS and if this is not set up, the records will continue to remain in
the LIVE table.
This is a one-time configuration and removal of the HIS.MVMT flag later will not
stop the records from being moved to $HIS.
135
Technical Notes
Regulatory Compliance
Regulatory Compliance
137
Regulatory Compliance
138
Regulatory Compliance
139
Regulatory Compliance
140
Temenos Infinity
Temenos Infinity
Digital Banking
l Payment
l Download Report option: For each transfer under Transfers tab in
Manage Transactions screen, the Download Report option is
displayed. When a user clicks this option, the application will
download the report that holds the details of the transfer.
l Display of Override messages – EU Transfer and Payment Flows:
When a user inputs a transfer or payment in Infinity, it is validated in
Transact. As part of this payment validation, Transact can generate
one or more override messages. In Transact, each override can be
configured to be shown as an error message or informational
message on the Infinity Customer app.
l A few cases on how this reflects in Infinity based on override
settings in Transact is given below:
Only 1 as error
Error Message - Payment Input
message
All 3 as error
Error Error Error Payment Input
messages
All 3 as info
Message Message Message Payment Review
messages
messages
l Approvals Enhancements
l Signatory/Approver Groups based Approval Matrix: Customers
can now choose from the two modes of Approval Matrix - User-
Based or Signatory-Group based. Approval Matrix has been
enhanced to support the usage of Signatory/Approver groups in
setting rules for monetary and non-monetary feature actions. When
the rule is applied on a particular transaction, any member of the
signatory group can be used to fulfill the criteria of the approval rule
that is referencing the group instead of specific users. In the
Signatory-Group based approval matrix, the rule setting supports
complex conditions which allow logical operators AND and OR and
their logical combinations where each condition in the rule consists
of two parts,
l Number of approvals required.
l Signatory Groups from where the approvals are required.
l Approver and Requestor Dashboard Enhancements to Support
Signatory-Group Based Approvals: The approval history
information contains Signatory Group information as well. The view
pending approvals from users list displays the names of users in the
Signatory Group from whom an approval is pending. The Pending
Approver list is divided into respective sections in case multiple
authorizations (Max/Transaction, Daily and Weekly) are breached.
l Ability to Setup and Manage Signatory/Approver Groups:
Signatory Groups are used to group users with same signatory
power. Signatory Groups can be created for each level of hierarchy
within an organization. For each customer, the business
administrator can create multiple Signatory or Approver Groups and
add users who have approval permissions to these groups. A
signatory group is assigned to a customer and online banking users
(external users) are then referenced in these Signatory Groups. The
Signatory Groups can be accessed and customized through a
Infinity Spotlight
Infinity Spotlight application is used to set up and maintain customer and
employee-related information and to configure the behavior of digital banking
applications associated with this information.
What's New:202110
The following features have been introduced in Infinity Spotlight:
Infinity Spotlight
What's New:202204
The following features have been introduced in Infinity Spotlight:
Infinity Components
Infinity components are the building blocks of the digital banking application.
These are self-contained entities that represent a business module such as
accounts, transaction details, and beneficiary management. They support
dynamic and responsive user interfaces across multiple channels – mobile,
tablets, and desktops.
l Add Payee
l Transaction List
l Unified Transfer Flow- Acknowledgment on Responsive Web
l Unified Transfer Flow- Acknowledgment on Mobile Native
l Unified Transfer Flow- Confirmation on Responsive Web
l Unified Transfer Flow- Transfer Type on Responsive Web
l Unified Transfer Flow- Transfer Type on Mobile Native
l Unified Transfer Flow- Make a Transfer on Mobile Native
Infinity Component also provides the following business use cases that has
been developed using multiple components.
Infinity Wealth
This Infinity release brings a new business solution: Temenos Infinity Wealth.
Temenos Infinity Wealth is a digital investment solution that provides a complete
digital customer experience for servicing wealth products from retail and mass
affluent customers up to High-Net Worth Individuals. The solution offers a next-
generation investment experience that allows financial institutions to engage
with investors easily and conveniently in the digital age. Investors can access
their investment products wherever they are, react fast to market changes and be
in complete control of their portfolio using self-service capabilities and real-time
data. The solution supports financial institutions to digitalize their wealth
management service, and at the same time enables banks to confidently access
the affluent market and convert savers to investors by digitally servicing long-
term investment products at low cost.
l All features are integrated with the Triple A Plus (TAP) system.
l Transactions for positions: Displays the list of transactions performed for
an instrument for the selected period.
l Instrument details per asset type: Displays the data points for an
instrument depending on the asset class to which it belongs.
l New IRIS header for Infinity and the impact on override processing:
Overrides and errors are handled in Infinity based on the configuration.
Infinity Origination
Enables banks and credit union members to open deposit accounts with a
seamless process across multiple channels and submit retail and business loan
requests quickly.
l Documents management
l View uploaded files/documents (and related meta-data)
through Origination client app.
l Ability to upload files/documents from Document
Tab/Manual Review Task and Customer Action task.
l Single/Multiple documents can be uploaded for an
application.
l Claim/Release/Withdraw application capability is
available.
l Add notes to the application.
l Configuration
l Support for Arabic language.
l Support for RTL Layouts: Support for internationalization and
localization (multi-language support).
SME Origination
l Product Selection
l Integration with Marketing Catalog Microservice (MCMS) for
displaying the Product Groups, Products (within the group), Product
features, Short description, and Benefits.
l Integration with loan simulator for simulation of monthly payment
amount based on requested loan amount and repayment term.
l Multi-feature selection support.
l Company Information
l Supporting all types of businesses.
l Capturing business Information.
l Capturing related companies’ details.
l Capturing multiple business addresses.
l Capturing financial information.
l Signatory Information
l Multiple signatory addition
l Individual ID and address information (iterative)
l Business Loans
l Unsecured lending is supported.
l Single facility is supported.
l Integration with loan simulator for simulation.
l New screen to capture loan details.
l Overdraft Loans
l Unsecured lending is supported.
l Single Facility is supported.
l New screen to capture loan details.
l Evidence/Document upload
l Evidential requirement subject to data entered and application
purpose.
l Documentation is archived for reuse, stored as a system of record.
l Save and Resume: Capability for save and resume the application post
personal info of the application raiser is captured.
l Addition of Additional Questions screen to collect Information
l Existing customer action framework of Open/Submitted/Skipped
Questions is leveraged.
l This section can be used by L2/L3 teams to ask additional questions
even before submitting the application.
l Summary before submission: Review details before application
submission with options to navigate back to previous screen and make
changes to the details captured.
l Product Selection
l Income and Employment Details
l Co-Applicant
l Document
l Summary
l Verification
l Additional Questions
l Submit Application
l Document Checklist: Capability to upload documents based on
Document Checklist defined in DMN per product and
introduction of separate section as Documents in the
Origination app (in the previous release, document upload was
done in Additional Question step).
l Infinity Assist - Back Office Application for Retail Lending Journey
l Introduction of Credit Packaging Stage
l Introduction of new stage where all the third-party
integrations required for processing the loan can be
triggered under Credit Packaging stage.
l The following stages are applicable for all lending
products:
l Submitted
l Prescreening
l Credit Packaging
l Underwriting
l Closing
l Complete
SME Origination
SME Origination - Onboarding Journey
l Basic Information
l Company Information
l Product Selection
l Related Parties
l Documents
l Summary
l Additional Features
l Submit Application
l Additional Information
l Enhanced Dashboard
l Enhanced dashboards for Relationship Manager to view
queue-wise Applications and Tasks.
l Provision to view to see Recently Viewed applications
(requests).
l Introduction of Queues
l Introduced queue concept for back office staff to handle
applications more effectively.
l Different Queues can be defined based on various
attributes and DMN rules.
l Out-of-the-box, different queues are defined at application
and task levels, and journey wise (onboarding, product
wise, region wise) band separate escalation queue is
defined for tracking tasks pending overdue as per SLA for
each task.
l Application/Tasks are auto assigned to respective
configured queue.
l Users can be granted with required permissions to
various queues and based on the access to the queue,
can claim application, and work on the application.
l Post submission, the application is automatically
assigned to the respective queue based on the queue
criteria.
l Migration of T&C to Consent MS: All T&C, Disclaimer, and
Consents in origination are collected, stored, and managed
(changed/deleted) in Consent MS.
l Document Checklist
l Capability to generate a Dynamic Document Checklist based on
application attributes like product applied, company type and more.
l Creation of DMN rules to generate Dynamic Document Checklist.
l Capability to upload documents based on Document Checklist
defined at product level under separate document section.
l The DMN framework can be configured based on new attributes and
is fully customizable.
l Enhanced Infinity Origination App Roadmap for Lending Journeys
l Basic Information
l Company Information
l Product Selection
l Related Parties
l Documents
l Summary
l Additional Questions
l Submit Application
l Additional Information.
l Infinity Assist - Back Office Application for SME Lending Journey
l Introduction of Credit Packaging Stage
l Introduction of new stage where all the third-party integrations
required for processing the loan can be triggered under Credit
Packaging stage.
l The following stages are applicable for all lending products:
l Submitted
l Prescreening
l Credit Packaging
l Underwriting
l Closing
l Completed
l Introduction of Automated STP Process (Straight-through Process)
for all SME Lending Applications
l Post submission, the application is processed automatically for
lending journeys.
l Mortgage journey
l Enhanced Income and Employment section in Origination and Assist
applications.
l Collateral details
l Mortgage loan calculator
l Funding position in Origination and Assist apps.
l Micro apps conversion for Origination application.
l BSG and US-SaaS feedback enhancements in Origination application.
l Spill over enhancements in Retail journeys such as,
l Supporting update multiple address and narrative via Entity
Overview section of Infinity Assist app.
l Individual PAM services for data migration of origination to
Origination Processing MS.
SME Origination
SME Origination
l Trade Finance: Infinity business users will now be able to access the
Trade Finance (TF) capability. The new TF features that are introduced as
part of the current release will allow the business user to:
l Import Letter of Credit (LC).
l View the list of Import Letters of Credit (LCs) – the issued LC
records and the draft records.
l Select a particular Import LC record and view its details.
l Search for a particular Import LC by using different keywords.
l Filter the list of Import LC records.
l Manage the Import LCs that were saved as drafts, such as edit
and delete a draft.
l Create a new Import LC as a new request or from a previous
record by copying the details.
l Print and download the details for a particular Import LC record.
l View the limit overview for the Import LCs.
l Export Letter of Credit (LC).
l Availability of Export Letter of Credit (LC) in the hamburger
menu based on the user access.
l View the list of Export LC with meta data.
l Select a particular Export LC record and view its details.
l Search for a particular Export LC by using different keywords.
l Filter the list of Export LC records.
l View details to be available under the action of each
transaction.
l Print and download the details for a particular Export LC
record.
l Export Drawings
l Submit documents to an approved Export LC (create a
drawing).
l Save the new Export Drawing request as a draft.
l Edit an Export Drawing draft.
l Delete an Export Drawing draft.
l Submit an Export Drawing for approval.
l View the list of Export Drawings.
l Filter the list of Export Drawings.
l Search for a particular Export Drawing record by using different
keywords.
l Select an Export Drawing record and view its details.
NextGen UI Components
The NextGen UI components are reusable components created using the
Component 2.0 architecture of Quantum Visualizer. These components facilitate
the usage of components across user journeys (features) of a Micro App to
deliver the end-to-end user experience. They are also configurable according to
the context of the consuming functions or features. The NextGen UI components
are available for the Mobile native channel only.
Flow Acknowledgment
Progress Bar QuickLinks SegmentedUI
Charts
Footer
Postal Address Email Address Phone Number
Menu
File
Frequency Picker Data Aggregation Account Selection
Upload
Assist)
Provides banks the ability to onboard corporate lending entities and originate
retail, SME, and corporate credit facilities on a digital-focused platform for the
lending market.
l Overdraft
l Mortgage loan
l Letter of credit
l Letter of guarantee.
l Supporting changes in the pricing screens based on the selected
product.
l Application termination capability
l Capability to withdraw an ongoing application by an authorized user.
l Application termination capability is linked with application stage and
user permissions.
l Search capability in currency drop-down: Search feature added to all
the currency drop-down list.
l Defining user roles and access rights and permissions
l Defining users and the roles along with Line of Business, for
example - Corporate RM, Corporate Underwriters and so on.
l Creation of new role - Supervisor.
l Role-based setting up of permission.
l Permission-based rendering of Infinity Assist screens.
l Role-based dashboards implemented.
l Financial ratio results
l Capability to add and compare all the financial ratio results of the
entity.
l Capability to compare financial ratio results of entities in a request.
l Enhanced collateral features
l Enhanced capability to add collateral to entity.
l Capability to capture specific collateral details based on the
collateral type.
l Capability to add valuation and documents to a collateral.
l Capability to edit and delete collateral.
l Integration with Transact to fetch the existing collateral of an entity.
l Enhanced entity details capture
l Capability to capture more entity specific information like Industry,
sub-industry, sector, MIS code and financial position related
Microservices
Marketing Catalog
Available from: 202107
Marketing Catalog microservice provides an independent cloud-enabled
solution to manage marketing information of the core banking products. It
exposes management APIs to manage marketing information for products
managed in the core banks.
Marketing Catalog
Party Microservice
Available from: 202107
Party microservice is used to store various details about the party (customers in
Transact) such as personal information, identity details, address details, and so
on. A user can create/update/get parties by using the Enterprise APIs of the
party microservice Enterprise APIs.
l DDL data update for MongoDB/DynamoDB and postgres in all the stacks.
l Updated K8-onpremise MongoDB script version.
l Vocabulary Check for events is set to false.
l Euro Bank changes for SRMS.
l Introduced new APIs to create, update, get and Delete for Consent.
l Introduced new APIs to create, update, get and Delete for Payment
Scheduler.
l Introduced new APIs to create, update, get and Delete for Drawing.
l Introduced new APIs to update Collateral Relationship.
l Kafka version upgraded from 2.13 -2.7.2 to 2.13-3.1.0.
l Added new Document Categories and Types in master data.
l Enhancement in the collateral Info and related party Info collection added
the amendRequestTypeStatus and amendRequestType.
l Enhancement in the Feature Details collection added the description.
l Added Mortgage reference data in master data.
l App listener changes for Azure pack.
Receipting Microservice
Available from: 202108
The Receipting microservice is the service that generates a small static PDF
receipt from the provided form definition and data payload.
The following changes are done to the microservice involving client apps:
Arrangement
Available from: 202110
Arrangement Microservice persists all the static information of the arrangements
in the core banking system and provides the same details to the digital front
office during the stand-in processing or a planned outage (For example, online
upgrade of Temenos Transact).
l SSL Disable for DB Servers, Metrics, Error Info Level, Commenting J2EE
Logger Property to ERROR Copyrights headers Logger Property using
TAFJ in K8 AWS Ping and Lambda Standardization Metrics Changes in
K8, AWS Bug Fixing, Removing Unwanted lines, IRF Container
Dependency, getPartyDetailsV2 - Forward Patch in core and all stacks.
l Removed NodePort apply command and Ingress changes in Docker.
l Tag Changes and Logger Level in Docker.
l Updated the MSF artefact name to resolve helm packaging issues in
Docker for sql-helm-pom.xml file.
l Modified Memory limiting changes to 1GB in Docker.
l Updated tag version to 202201.0.0 and added logger changes in Docker.
l Updated the following: CreateArrangementInfoDepositsTest.java,
CreateArrangementInfoDepositsTest.java, Kafka version in AMS,
CreateArrangementInfoDepositsTest.java,
CreateArrangementInfoDepositsTest.java, arrangement-api.yaml,
arrangement-api.yaml, packK8Zip.sh,
l Memory Limit changes for K8 - AMS, Dummy Commit - AMS,
packK8Zip.bat, and Tag Changes in docker.
l AMS Wealth changes in ms-arrangement-test.
l Enabling Health check API for ingester containers for holdings micro
service. Health check APIs help us the get the availability status of
containers.
l Updated the Spring beans version to avoid the build failure.
l Lambda connection syncing with MySQL Scripts-Lambda standardization
changes the lambda function names following the set of rules of naming
convention.
l DDL script execution and script changes in AWS and Azure stacks.
l Defer Date done in getBillDetails in the path: ms-arrangement-
core/src/main/java/com/temenos/microservice/arrangement/ingester/Arran
gementIngester.java.
l Hikkari pool changes increased maximum pool size to 150 and minimum
to 10, in all stacks to accommodate a greater number of DB connections.
l K8 Tag automation changes implemented. From now onwards, setting the
version is automated as we have made changes that take the version from
a version.txt file which is generated during the build.
l Script clean-up for build files and packK8 scripts done in docker stack.
l Helm build scripts updated, gave read access to the build file so that we
can encounter the permission denied error.
l Done vocabulary check in all the pom.xml files in all stacks.
l Corrected scripts for creation of Local Reference Table for Customer,
Account and Company in the path: ms-arrangement-
test/TestWare/Parallel/Thread_1/Testware/Testware.xlsx.
Account Aggregation
Available from: 202110
Account Aggregation is an online service, which allows you to consolidate a
range of accounts and other financial information into one interface to simplify
the management of personal finances. To bring them into the Infinity fold,
Account Aggregation makes use of the Account Aggregation Microservices and
a MarketPlace partner solution.
l Added changes to configure the names of replica set. User can provide the
environment specific name for each deployment through start script “ENV_
NAME” variable. The pod names are prefixed with the ENV_NAME
specified.
l Added the namespace values as variables for service, DB instead of
creating the namespaces directly in docker/k8 stacks.
l Enabling Health check API for ingester containers for holdings micro
service. Health check APIs help us the get the availability status of
containers.
l Updated spring bean version to the latest version to avoid build failure.
l Added escape sequence in azure scripts as some random path is getting
appended to resources. Adding the escape sequence has avoided that
path.
l Hikari pool changes increased maximum pool size to 150 and minimum to
10 in all stacks to accommodate a greater number of connections.
l K8 Tag automation changes, from now on setting the version is automated
as we have made changes that take the version from a version.txt file
which is generated during the build.
l Helm build scripts updated, gave read access.
Consent Management
Available from: 202110
The Consent Management microservice stores the consents received from the
Third-party provider (TPP).
Holdings
Available from: 202110
Holdings is a read-only microservice for providing balances and transactions. It
allows the client applications to view account details along with associated
transactions. It also provides generic data model to manage account balances
and transactions.
l Copyrights and Azure UTP changes, Dummy commit for UTP, and Dummy
commit for job triggers in ms-holdings-core.
l Added changes to configure the names of replica set. You can provide the
environment specific name for each deployment through start script “ENV_
NAME” variable. The pod names are prefixed with the ENV_NAME
specified.
l Data Reconciliation changes. Ensure that no overwriting/ingesting of the
data into MS for the old DES events which hit the MS after the latest DES
events for the same has already been updated.
l Enabling Health check API for ingester containers for holdings micro
service. Health check APIs help us the get the availability status of
containers.
l Modified E2E test cucumber scripts to support latest Transact data.
l Upgraded AWS PostgreSQL version in install-aws-postgresql.sh file.
l K8 Tag automation changes implemented. From now on, setting the
version is automated as we have made changes that take the version from
a version.txt file which is generated during the build.
l Added vocabulary check tag in properties in pom.xml of model, all stacks
folder to avoid build failure.
l Helm build scripts updated, gave read access to the build file so that we
can encounter the error permission denied.
l Updated k8 on-premise MongoDB script version.
Savings Pot
Available from: 202110
Savings Pot microservice lets you to create, fetch, and update the savings pot
details required for both front office and back office.
Campaign
Available from: 202110
Campaign Microservice enables the branch users of banks to define and store
the details of the campaigns created through the front office solution developed
for the campaign management, which is called as Real Time Engagement
(RTE).
Application Framework
223
Temenos Transact
This feature cleans up the footprints for every session that is allocated to the job.
It also facilitates for tidying up anything as part of the job completion.
If the condition defined for the above fields are satisfied, then corresponding field
value of the associated Linked App Fields are considered for performing the
duplicate check. It is then evaluated using the following operations:
This feature improves the runtime capability in Transact for the evaluation and
identification of a duplicate contract, based on the condition field and condition
value available in the EB.DUPLICATE.TYPE record definition.
224
Temenos Transact
225
Temenos Transact
226
Temenos Transact
227
Temenos Transact
228
Temenos Transact
229
Temenos Transact
230
Temenos Transact
papRuntime folder using meta API call. PAP UI now supports system API call if
Transact is selected from the Product drop-down list to fetch data.
231
Temenos Transact
or services, are reported in a log file referred to as COMO. This log file no longer
holds all information by default. It is enhanced to host details only based on the
log level configured in TAFJTrace.properties and classification of log
level for each message.
232
Temenos Transact
233
Temenos Transact
Banking Framework
234
Temenos Transact
235
Temenos Transact
Click here to understand the installation and configuration updates for this
enhancement.
236
Temenos Transact
237
Temenos Transact
l Introduction
l Configuration
l Working with
238
Temenos Transact
239
Temenos Transact
240
Temenos Transact
241
Temenos Transact
Click here to understand the installation and configuration updates for this
enhancement.
242
Temenos Transact
Click here to understand the installation and configuration updates for this
enhancement.
To reduce the time taken to process a debit or credit to an account through the
Generic Accounting Interface and improve performance, the following options
have been added:
Click here to understand the installation and configuration updates for this
243
Temenos Transact
enhancement.
244
Temenos Transact
245
Temenos Transact
Click here to understand the installation and configuration updates for this
enhancement.
246
Temenos Transact
247
Temenos Transact
248
Temenos Transact
Transact is now enhanced to update the internal account block closure file
(accounts that are defined in Temenos Transact and DD Mandate defined for
then) each time a DD Mandate is created, cancelled or matured based on the set
up of the Block Closure field in DD.PARAMETER.
249
Temenos Transact
Click here to understand the installation and configuration updates for this
enhancement.
250
Temenos Transact
Deposit module and allows the Temenos Payment solution to decide the
payment channel and the format of the messages that must be exchanged.
The Transact clients which are in releases prior to R21 AMR can implement a
standalone Temenos Payments platform (R21 or R22 AMR+) to process the
ISO20022 SWIFT payments. Delivery MX Translation module, installed as part
of standalone Temenos Payments platform, receives the MT103/202 generated
by Transact business modules and transforms them to payment orders.
Temenos Payments executes the payment orders and generates the final
ISO20022 message.
The ISO20022 Outward Camt Account Reporting (IZCAMT) module is the
Temenos strategic solution that allows banks to produce customer statements
and account reporting messages in ISO20022 formats. Delivery MX Translation
solution supports the “like for like” transformation of the outward
MT940/950/941/942 to the SWIFT CBPR+ equivalent messages. Transact
clients in prior releases (in which the IZCAMT module is not available) can
implement Delivery MX Translation module as part of the standalone Temenos
Payments platform.
Click here to understand the installation and configuration updates for this
enhancement.
251
Temenos Transact
252
Temenos Transact
define specific set of taxes applicable conditions for them and the bank can
group all their staffs or gold status customers to provide benefits on interest rates
or charges.
PP.GEN.CONDITION provides the parameters to calculate the default groups
for Temenos Payment Hub applications. The priority data items, which are used
in the PP.GEN.CONDITION application are defaulted from the corresponding
CONDITION.PRIORITY record POR.TRANSACTION. This allows banks to
capture and to group the customers and offer different conditions like processing
charges, customer float, spread definitions, payment advice, posting definition
for payments.
253
Temenos Transact
Corporate
Club Loans » Risk Participation
Available from: 202108
Risk Participation allows the lender to reduce their exposure to a particular loan
amount by selling their risk portion (full or partial) to another party. The risk
participants could be an external party or part of the internal consortium of banks
who fund the loan who are responsible for paying back the lending bank whose
risk they have taken over in case there is a default by the borrower.
The Participant Property Class is now enhanced to record the risk participant
(party who have taken over the risk portion) details along with the fund
participants (lenders who provide the funding for the loan).
The user can also add Risk Participant property to the existing Participant
Property Class. A new Participation Type field is introduced in the Product
Condition of Participant Property class to define the type of risk participation.
254
Temenos Transact
255
Temenos Transact
l Banks can now keep a track of those evidence which are due in near
future, already due, overdue and not in compliant through various reports
generated by Temenos Transact.
256
Temenos Transact
257
Temenos Transact
contracts with Risk Participants so that the funding Bank can share the Risk
exposure with other banks (Risk participants) thereby reducing the burden of
entire risk exposure on one bank.
258
Temenos Transact
259
Temenos Transact
260
Temenos Transact
o Introduction
o Configuration
o Working with
261
Temenos Transact
l It takes over a lending or facility arrangement with the risk participants from
a legacy system.
l It adjusts the risk margin accruals, which a Transact pays back to the risk
participants.
l The own bank can charge off the principal outstanding of the loan
arrangement only to the extent of uncovered risk, since the risk participant
covers a certain amount of risk in case of default.
262
Temenos Transact
263
Temenos Transact
Islamic Banking
Direct Purchase of Asset from Seller – Ad hoc
Vendor
Available from: 202112
Currently, an asset can only be purchased from the pre-configured vendor list.
There was no option available to handle the purchase of an existing asset from
the seller and make payment directly to the seller.
To overcome this, the new feature provides an option to the bank for purchasing
the asset directly from an ad hoc vendor. It is not mandatory anymore to create a
Vendor ID to initiate asset purchase using the IS.CONTRACT application.
During an asset purchase, the payment can be made directly to the Seller
Account Number. If the seller is does not have an account with the bank, then it
can be parked in the Seller Wash Account. Later, it can be transferred to the
seller account through other payment modes.
Click here to understand the installation and configuration updates for this
enhancement.
264
Temenos Transact
The user can capture this Special HIBA profit rate agreed with the customer. The
Special HIBA profit amount is paid along with the principal profit amount to the
customer. If the Mudaraba deposit is pre-closed, then the paid Special HIBA
profit amount is adjusted in the principal amount.
Click here to understand the installation and configuration updates for this
enhancement.
265
Temenos Transact
266
Temenos Transact
267
Temenos Transact
268
Temenos Transact
269
Temenos Transact
270
Temenos Transact
Private Wealth
271
Temenos Transact
272
Temenos Transact
273
Temenos Transact
274
Temenos Transact
275
Temenos Transact
276
Temenos Transact
277
Temenos Transact
278
Temenos Transact
279
Temenos Transact
280
Temenos Transact
281
Temenos Transact
282
Temenos Transact
maturity date of the underlying future contract for the options with underlying as
futures. For example, if the option maturity date is Nov 2020, the banks can now
define the underlying future’s maturity date as Nov 2020 or Dec 2020 as per the
contract terms. The maturity date of the underlying futures contract is updated in
the ID of the DX.MARKET.PRICE and DX.REP.POSITION applications of the
option contract to distinguish the price records and positions.
283
Temenos Transact
284
Temenos Transact
285
Temenos Transact
The Securities module is now enhanced with the calculation of penalties for all
transactions that do not pass the matching criteria or settled beyond the intended
settlement date.
286
Temenos Transact
287
Temenos Transact
288
Temenos Transact
289
Temenos Transact
This functionality allows banks to use the BCRA (Central Bank of the Argentina
Republic) service to check the FX (Foreign Exchange) operations executed by a
customer on a particular day. This service is used to query the database in
BCRA and validate the FX operations executed to amend or verify these FX
operations.
290
Temenos Transact
291
Temenos Transact
292
Temenos Transact
293
Temenos Transact
Taxes
294
Temenos Transact
295
Temenos Transact
296
Temenos Transact
297
Temenos Transact
298
Temenos Transact
prohibited.
This functionality allows banks to manage the functional errors that can appear
once the FX blacklist is processed through the Data Formatting Engine (DFE).
The functional error messages will be logged, and the files will be moved to the
archive folder.
Provisioning
Available from: 202202
This functionality uploads the CENDUE and MOROS files into the system and
based on the classification of the customer in the files, the corresponding
customers in the bank will be re-classified.
This functionality provides configurations that allow the system to apply the
Generic VAT, Perception VAT and Turnover Perception when a customer is
charged with the penalty interest.
299
Temenos Transact
300
Temenos Transact
301
Temenos Transact
Accounts
302
Temenos Transact
elsewhere.
This functionality allows banks to calculate the Withholding Tax for the dual
listed security and for stapled securities.
Address Interface
Available from: 202112
There is an existing functionality where the customer’s address is fetched from
the Equifax interface.
This functionality allows banks to capture the collateral address details and get it
validated using the Equifax interface.
Temenos Transact provides home pages based on the user’s role. This allows
the bank users, Call Centre, or Customer Service Agents, to access the data and
functionality they require, investigate and correct payment exceptions, and other
day-to-day functions.
This functionality allows users to access the home pages to view or perform
manual operations on loans and deposits custom-made for Australian banking
303
Temenos Transact
operations.
304
Temenos Transact
displays all the customers' accounts (across different product lines) held with the
bank. It displays a list of all the customer accounts, deposits, loans and
additional information such as the account type, balance, available limit, and
locked amounts.
305
Temenos Transact
movement across the core accounts: client foreign currency account, custodial
foreign currency clearing account, client AUD account, custodial AUD clearing
account.
This functionality allows banks to extract the details around any foreign
exchange transactions undertaken at any foreign currency account linked to the
portfolio. The extract generation is based on the data built in the
CG.FCY.ACC.BASE application.
This functionality covers the structure and hierarchy of the legal entity platforms
of Australia such as super, investor-directed portfolio service, separately
managed accounts, etc., which are at the portfolio level. With this functionality,
banks are able to create, update and retrieve details from the fund structure and
the customer security account (portfolio).
306
Temenos Transact
Using the New Payments Platform (NPP), this functionality allows bank
customers to use two types of Osko payment options given below via online or
mobile banking and also to receive such payments. It applies when the
customer has NPP enabled for an account and both Financial Institutions (FI’s)
involved in a payment are certified and registered for NPP.
307
Temenos Transact
308
Temenos Transact
Lending Insurances
Available from: 202106
This functionality allows Financial Institutions to offer insurance products for
their Line of Credit (LOC) products. The insurance product offering for the LOC
product is based on age-group-wise rate eligibility, gender, and smoking habits
of the customer. The facilitation for the accessed provincial taxes on the
insurance product is also applicable and accounted for the LOC product.
Lending Renewals
Available from: 202106
It is common in the mortgage and commercial term marketplace for a bank to
offer its clients several terms and payment options before renewing a loan.
309
Temenos Transact
Trade Declaration
Available from: 202201
This functionality allows banks to record the trade declarations provided by
customers. This declaration will act as a limit for the trade transactions like
issuance of letter of credits, documentary collections and payments or draft
issues done in Temenos Transact. When the declaration is used during trade
transactions, the available balance in the declaration record will be
automatically updated.
This functionality allows banks to capture or load the deposit balance details in
Temenos Transact. The system will calculate the CRR based on deposit
balances and will update the corresponding CRR in the same record.
310
Temenos Transact
311
Temenos Transact
312
Temenos Transact
Bearer bonds are the type of collaterals that can be created on ships, vehicles,
aircraft, and floating charges.
This functionality allows banks to handle the status of the bearer bonds, capture
the details of the underlying asset, issue a secondary pledge on a bearer bond
and capture the details of the issued or received secondary pledges.
313
Temenos Transact
314
Temenos Transact
customer has some temporal financial difficulties. The European Central Bank
(ECB) requires a report of the loan that has been marked as forbearance by
monitoring the customer's repayment behaviour over a specific period for some
specific amendments.
315
Temenos Transact
paper invoice or pre-notification that is sent to the customer. The penalty interest
(if any) to be part of an invoice will be calculated only until the invoice issued
date. The FILEND.PENALTYINT.CALCULATION routine is introduced to
calculate the penalty interest till the bill issue date.
316
Temenos Transact
317
Temenos Transact
318
Temenos Transact
respective transaction.
319
Temenos Transact
320
Temenos Transact
321
Temenos Transact
options, the respective closeout details will be sent to CPB SECTRAS. In return
CPB SECTRAS responds with the tax amount if applicable and the closeout
transaction is authorised in Temenos Transact.
322
Temenos Transact
supports the processing of entitlements that have both cash and stock
components. For events that have an underline cash and stock component as
part of the entitlement, the Cash or Stock Events field has been added to the
DESCTX.SECTRAS.PARAMETER application, where the bank needs to
configure all the events where there are possibilities of both cash and stock
based processed in the same entitlement.
323
Temenos Transact
Infrastructure
Available from: 202105
This functionality allows users to validate the check digit for the Hong Kong
Identity Card (HKID) captured for a customer at the time of individual customer
creation and customer tracking to determine the availability of CBRED
324
Temenos Transact
(Customer Business Relationship End Date). The system will validate the check
digit of the HKID entered by the user and if it is invalid, an error will be
displayed.
Hong Kong Monetary Authority (HKMA), the regulatory authority in Hong Kong
mandates the maintenance of the customer-business relationship end date
(CBRED) for all customers. The CBRED date has to be updated when the
relationship of a customer with the bank comes to an end.
325
Temenos Transact
326
Temenos Transact
end.
327
Temenos Transact
328
Temenos Transact
329
Temenos Transact
330
Temenos Transact
331
Temenos Transact
Transaction Fees
332
Temenos Transact
333
Temenos Transact
another application, the queuing solution will check if the account against which
a transaction is initiated has a regulatory warrant present or not and whether the
account has available funds other than the allocated funds towards the queuing
solution.
334
Temenos Transact
335
Temenos Transact
336
Temenos Transact
and weaker sections. This is essentially meant for the all-around development of
the economy.
Every bank in India is given targets and sub-targets for lending under the priority
sector. The priority sector lending comprises different categories such as
Agriculture, Micro Enterprises, Education, Housing, Social infrastructure.
This functionality allows banks, in the case of loans to borrowers under the
priority sector, to not charge the penal interest for loans up to Rs. 25,000.
337
Temenos Transact
338
Temenos Transact
339
Temenos Transact
market.
Trading Calendar
Available from: 202108
The system is able to indicate the trading dates of a stock exchange. Further,
there are certain days on which trading in certain securities in Tel Aviv Stock
Exchange (TASE) is not possible. Hence, there is a need to indicate the trading
or non-trading days of a security. The settlement holidays are stored in the core
HOLIDAY application.
This functionality allows banks to setup of trading holidays at the stock
exchange level. There is also a provision to indicate the days of a week when a
particular security doesn’t trade. Any orders being placed on a trading holiday of
the stock exchange or the day of the week when the security doesn’t trade will
result in error.
340
Temenos Transact
341
Temenos Transact
342
Temenos Transact
343
Temenos Transact
344
Temenos Transact
345
Temenos Transact
This functionality allow banks to capture the information related to the deposit
reinvestment instructions and to change a deposit from maturity to rollover and
vice versa. It allows users to define a new term, new rate and new interest
schedule after the rollover.
The system will validate whether the change in the payment frequency and the
payment method (CAPITIALISE (compounding) or PAY (non-compounding)) is
within the period mentioned in the
XNZ.ADDITIONAL.INFO.STAND.DOWN.PERIOD. The system allows the
346
Temenos Transact
This functionality allows banks to calculate the break costs on full and partial
breaks when a customer requests for an early withdrawal in term deposits.
New API’s have been introduced to create or retrieve the information about term
deposit redemptions requested and executed.
347
Temenos Transact
348
Temenos Transact
Customer Compliance
Available from: 202109
This functionality allows banks to store and amend the customer information in
the customer creation process for both individual and corporate customers
during the customer on boarding process.
349
Temenos Transact
Regular reporting provides the financial information required by the SIMAH for
new contracts, closed contracts, daily payment and newly default contracts in
Temenos Transact on a daily basis.
This functionality allows banks to identify if a customer is a salaried person of
the bank and automatically manage the selection of the contracts for regular
reporting containing the financial information required by the Saudi Credit
Bureau (SIMAH).
350
Temenos Transact
Watheeq Services
Available from: 202109
This functionality allows banks to store the UIDN (Unified Identification Number)
for the non–government agencies at the customer level. The UIDN will be
received in the request and it will be validated and the relevant relation code will
be sent in the header of the response. The secondary Id details received in the
request will also be stored in along with the primary Id details. Also, banks are
able to block or garnish the amount from the targeted accounts or target products
and to lift the related restrictions done against the customer.
351
Temenos Transact
Withholding Tax
Available from: 202201
352
Temenos Transact
353
Temenos Transact
the Fund House or All Funds Bank (AFB) the one that, once the backend sends
the transaction, can cancel it.
Non-customers can perform cash transactions like cash deposits and cash
withdrawals (through bearer cheque) to or from the bank customer’s accounts at
the bank’s branches. During the withdrawal with bearer cheque, if the amount
exceeds the threshold, then the non-customer’s Legal Id will be verified and if
the amount is within the threshold, then the Legal Id is non-mandatory.
This functionality allows banks to capture the non-customer information for all
cash transactions and a report will be generated to display the date-wise
transactions performed by the non-customers.
354
Temenos Transact
355
Temenos Transact
356
Temenos Transact
SEPA Iberpay
357
Temenos Transact
358
Temenos Transact
359
Temenos Transact
360
Temenos Transact
361
Temenos Transact
362
Temenos Transact
363
Temenos Transact
364
Temenos Transact
365
Temenos Transact
366
Temenos Transact
367
Temenos Transact
368
Temenos Transact
369
Temenos Transact
370
Temenos Transact
371
Temenos Transact
Retail » Statements
Available from: 202110
This functionality allows banks to generate the statement file with details
captured in the USCORE.COMPANY.DETAILS application, including the
company and branch information. Also, as part of this functionality, the RegE
statement narrative logic has been enhanced to display the ACH return code
description in customer’s statement for incoming ACH returned transactions.
372
Temenos Transact
373
Temenos Transact
This functionality allows banks to exclude linked activity classes and activities
from re-activation of dormant accounts. A new fast path inquiry has been
introduced to allow users to manually re-activate dormant accounts. The inquiry
only lists accounts with activities linked to a new override routine. The tracking
mechanism has been updated to re-reschedule escheatment evaluations based
on related escheatment period changes.
374
Temenos Transact
375
Temenos Transact
Retail
376
Temenos Transact
377
Temenos Transact
378
Temenos Transact
379
Temenos Transact
380
Temenos Transact
l The system settles the accrued interest till date and the remaining interest
component paid by the customer is apportioned towards the principal.
l Thus, the principal is reduced both from the advance payment of principal
and any interest component that is apportioned towards the principal.
l The interest accrual after the advance payment is on the reduced principal
after the advance payment.
381
Temenos Transact
382
Temenos Transact
383
Temenos Transact
performance issues, the interest accruals are archived by moving the entries in
the record in AA.INTEREST.ACCRUALS to the
AA.INTEREST.ACCRUAL.HIST application. The user can archive the interest
accruals using the Archive Period and Retain Period fields in the
AA.PARAMETER application.
l Lending
l Deposits
l Retail Accounts
384
Temenos Transact
l Simulate the combined closure of the MCY arrangement along with its
underlying sub-accounts and execute the simulation.
l Perform direct live closure of the MCY arrangement along with its
underlying sub-accounts.
Banks can now settle the bills in advance for all payment types except the
routine and transaction amount-based payment types. During an advance
payment, the system settles the bill as-is. Therefore, the customer does not
receive any benefit from the principal or interest component paid in advance.
During an advance settlement,
385
Temenos Transact
l The system parks the funds to the new ADV<ACCOUNT> balance type
and triggers the Forward Apply Payment activities with value date as the
actual bill due date . This is achieved by setting the Advance Settle Date
field as Due in the Payment rule type of the advance payment rule
condition.
l The system settles the principal and interest components of the bill as-is
effective on the actual bill due date.
l It settles the bill fully/partially based on the amount paid in advance
and updates the bill status as SETTLED/ADVANCED respectively.
l The system updates the General Ledger (GL) balance only on the actual
bill due date.
386
Temenos Transact
The Generate Charges Activity can be used to collect or pay charges in non-
financial arrangements. The charge information is passed to the settlement
account using Context Name-Value fields and capitalised in the liquidation
account.
387
Temenos Transact
l Null - The interest adjustments for the back value dated transactions are
posted on the next accrual
l Next Cap - The posting of interest adjustments depends on the value set
for Adjust Current Period Interest along with Next Cap?
(FULL.ADJUSTMENT option). That is, when the value is:
l Yes - The interest adjustments for the back value dated transactions
are booked on the next capitalisation date.
l Not Set - The interest adjustments for the back value dated
transactions are posted:
l The current period interest adjustments are posted on the next
accrual
l The previous period interest adjustments are posted on the
next capitalisation date.
388
Temenos Transact
389
Temenos Transact
bank or the channels through which the customers access and transact on their
MCY accounts, Transact is now enhanced to apply preferential pricing to the
MCY accounts through the following pricing strategies, either independently of
each other or in combination:
l Regional Pricing
l Customer Related Arrangements Pricing (CRA)
l Bundle Pricing
l Package Pricing
It is now possible to take over a MCY account from the legacy system. When the
sub-accounts are created, the sub-balance and accruals are captured at the sub-
account level. The sub-account balance automatically flows to the MCY
arrangement as a memo balance and it is displayed as a memo balances at the
top account level.
MCY Card Processing
The user can issue a new card at the top account level and have the card fee
raised and settled from the sub-account linked to card. Besides user
convenience, there is ease of access to MCY account information as the
balances of the customer in Single Customer View (SCV) screen is also made
available.
390
Temenos Transact
391
Temenos Transact
l Capture Historical Bills - Used to take over the settled bills from the legacy
system.
l Capture Historical Transaction Balance - Used to capture the net
movement for a given day from the legacy system. The interest movements
from the historical interest bills adjust the running balance as well.
This feature allows the user to make back value dated changes beyond the
Transact Take Over date and perform bill adjustments.
392
Temenos Transact
393
Temenos Transact
l AA.CALCULATE.RULE78.PRIN.AMOUNT
l AA.CALCULATE.RULE78.INTEREST.AMOUNT
394
Temenos Transact
Rule of 78 in Loans
Retail Securitisation
Available from: 202112
Loan Securitisation helps to create an investor pool and the Loans can be sold
to the investor , partially or fully to the investors to perform loan securitisation.
395
Temenos Transact
allowed product for sub-account creation. The base currency product of the MCY
should be same as the allowed product in the Sub-Arrangement Rules product
condition.
396
Temenos Transact
actual booking and completion dates, retaining the original set of conditions and
parameters regardless of the difference between the dates on which the
simulations are captured and the dates on which they are executed.
To facilitate this, the AA.SIMULATION.RUNNER application (used to turn the
simulation live) is enhanced where the user can modify the simulation execution
date to be the current system date using the Date field (under User Activities
tab of AA.SIMULATION.RUNNER) regardless of the effective date set in
AA.SIMULATION.CAPTURE.
Banks can choose the funds availability date (Available Start Date) to be a
business or a non-business date for notice accounts, based on the value defined
in the new field in the Balance Availability Property Condition namely, Notice
Convention. The allowed values for this field are:
l Forward – The available start date moves forward to the next working day
if the resultant calculated date is a holiday.
l Backward - The available start date moves backward to the previous
working day if the resultant calculated date is a holiday.
l Blank or Calendar – This is the default option, that is, the funds availability
date can be a calendar date.
397
Temenos Transact
398
Temenos Transact
399
Temenos Transact
400
Temenos Transact
Accounts
Notice Request Validations based on Locked Amount -
Deposits
Illustrations For Notice Request Validations - Accounts
Illustrations For Notice Request Validations - Deposits
401
Temenos Transact
402
Temenos Transact
Cycles to define the number of times the review rule has to be evaluated. This
field is a part of the associated multi-value set along with the Frequency
attribute.
The system is enabled to define the rule end for a periodic attribute evaluation in
the AA.PERIODIC.ATTRIBUTE table using the Rule End field. The Cooling-off
option is available to define the Rule End as the cooling period.
l This field can be set only when the Rule Start field is defined as
Agreement/Start/Anniversary.
l The Period Type field should be blank when Rule End is defined.
403
Temenos Transact
404
Temenos Transact
405
Temenos Transact
Early Repayment Charge (ERC) of the individual arrangement and charging the
same at the facility level.
Retail Lending - Role Based Home Page Information on Payoff
The user can now view the number of payoff requests initiated for a customer,
recorded in the new Payoff Request Initiated field in the single customer view
(SCV).
Retail Lending - Mortgage Early Repayment Charge
With Overpayment Limit and Early Repayment Charge ERC, it is now possible
to pre-define a cap amount on the excess repayment associated with a charge
that can be levied only if the repayment exceeds the cap amount. Further, with
ERC, it is now possible to define phases (that can be configured at Product
level) that control how the ERC has to be handled over the loan term. That is,
charges for each year can be different, for one year it can be fixed and for the
next year it can be a variable charge.
406
Temenos Transact
l Forward - The available start date moves forward to the next working day if
the resultant calculated date is a holiday.
l Backward - The available start date moves backward to the previous
working day if the resultant calculated date is a holiday.
l Blank or Calendar - This is the default option, that is, the funds availability
date can be a calendar date.
407
Temenos Transact
Technology
Data Framework
408
Temenos Transact
Design Framework
409
Temenos Transact
410
Temenos Transact
411
Temenos Transact
412
Temenos Transact
413
Temenos Transact
Temenos Data Packager allows the user to import bulk data records from CSV
file with the help of a new wizard Bulk Data Records Import from CSV in IDE
mode.
414
Temenos Transact
Extensibility Framework
415
Temenos Transact
Virtual Table Microservice supports the users to configure and deploy this
service in Elastic Kubernetes Services (EKS) and Azure Serverless
Environment.
416
Temenos Transact
417
Temenos Transact
Temenos Workbench now allows the user to search, create, edit and pack JOLT
mapping used for data extension of Microservices data model. The user can
fetch the list of the Data Extensions that are stored in Generic Configuration
Microservice to edit or add a new JOLT to them.
Data Extension JOLT Mapping allows users to define mapping between
Transact or Generic events and microservices entity to support any new data
field added as part of customization.
418
Temenos Transact
Integration Framework
419
Temenos Transact
l NO.BATCH.SORTED
l NO.BATCH.NO.PRIORITY
l NO.BATCH.SORTED.NO.PRIORITY
l INITIAL.LOAD
420
Temenos Transact
421
Temenos Transact
422
Temenos Transact
Interaction Framework
423
Temenos Transact
424
Temenos Transact
reference fields from LOCAL.TABLE that are enabled for propagation along with
API core fields defined in Version of API.
425
Temenos Transact
In this release, you can map the fields of payload, response and fields of
business error response to any sample data. The solution uses the IRIS
endpoint to load the fields of an artefact to map the field to sample value in
workbench. Once the artefact is added and fields are mapped to the sample
data, workbench should be able to create inventory with sample data and send
the request to IRIS to generate the swagger and service xml. The generated
swagger json will have the sample data as example in definitions.
426
Temenos Transact
427
Temenos Transact
428
Temenos Transact
429
Temenos Transact
error details of the validation failure. IRIS then converts the transaction call into
an Validate call and sends it to Transact, and the result of both the Transact
response and Regex Engine response are sent to the client as a response with
400 status code. The API payload validation performed at the IRIS level is a
benefit.
430
Temenos Transact
Now, the new micro service V2.0.0 functionality supporting the text data string
payload on storing and fetching the data through the API interface, where
explicit encoding and decoding of the data is not required from the application
end.
The uploaded payload against the V1.0.0 API interface can also be retrieved
with the V2.0.0 API interface. Supporting upgraded V2.0.0 micro service API
interface is in IRIS R18.
431
Temenos Transact
Microservice
The Generic Config microservice now allows the user to define and store a
default value for a field. When any of those defined fields have empty values in
the request payload, the system automatically defaults the corresponding
mapped values during runtime before proceeding with the Regex or rules
validation.
This feature helps the user to avoid inputting the same value repeatedly for
every API request.
If the field defined for auto defaulting has a value in the request payload, then
defaulting is avoided.
432
Temenos Transact
433
Temenos Transact
IRIS Tracer
IRIS support banks to extend the interaction framework to customise and script
their own validations and business specific logics separately during runtime
configuration with backward compatibility. It allows defining Python hooks rather
than changing the core framework. It provides flexibility to the banks to define
validation based on domain and operations associated with the API request.
Using Python scripts, both the request and response payload can be extended
for validation.
434
Temenos Transact
Banks can now use Python scripts to extend both request and response to have
customized validations. This allows banks to store it as part of separate Python
hooks rather than changing core framework. The customized Python hooks are
initial configuration process stored separately from core changes. This
functionality is supported in rules engine only for request payloads.
435
Temenos Transact
Click here to understand the installation and configuration updates for this
enhancement.
Platform Framework
Click here to understand the installation and configuration updates for this
enhancement.
436
Temenos Transact
437
Temenos Transact
Transact Email is now enhanced to support the bank to send the alerts and
statements to the customers using plain text password pdf attachments, which
secures the customer account information. The Email sent can be enriched with
enriched attachment using HTML. This feature allows the banks to switch
between Emails with or without attachment based on the requirement and can
customise the Email message sent to the customers.
438
Temenos Transact
Observability » Metrics
Available from: 202112
All kinds of Microservices consist of API, INGESTER, Scheduler & DB services.
Separate metrics are added to each service.
Temenos Transact is now enhanced to provide a support for metrics. This
enhancement enables the metrics in eight infra microservices (adapter,
callbackregister, traceability, serviceorchestrator, metering, eventstore,
genericconfig, entitlement) and sample microservices for verifying the
application in metrics in Grafana IU.
439
Temenos Transact
440
Temenos Transact
441
Temenos Transact
Trade Finance
Miscellaneous Deals » Swift 2021 - Revamp of
Category 7 MTs - Issuance of Guarantees and
Stand By LCs
Available from: 202107
SWIFT has revamped the Category 7 MTs related to guarantees and standby
L/Cs in 2021 for a better straight through process.
442
Temenos Transact
443
Temenos Transact
444
Temenos Transact
The SWIFT 2021 release addresses the changes in MT103 and MT202 COV
messages, which are used in guarantees or standby letter of credit, and their
business flow that generates the message from Temenos Transact.
In this enhancement, fields validations for option of F for tag 59 are introduced in
the MD.DEAL to capture the details for the fields. Similarly in DRAWINGS
wherein the payment message is triggered, the 59F tag is introduced.
445
Temenos Transact
446
Temenos Transact
447
Temenos Transact
448
Temenos Transact
449
Temenos Transact
Treasury
Forex » Extension and Cancellation of Client FX
Forward Contracts
Available from: 202106
The Foreign Exchange (FX) module now supports partial or complete
cancellation and extension of an FX contract and rebooking of a new FX
contract with an extended maturity date.
450
Temenos Transact
451
Temenos Transact
452
Temenos Transact
453
Temenos Transact
454
Installation and
Configuration
Notes
Temenos Transact
Banking Framework
Application Fields
RESERVATION.ID
AC.LOCKED.EVENTS
JOURNAL.ID
JOURNAL.ID
AC.INWARD.ENTRY
UPDATE.MODE
Table Columns
ReservationId
Ms_ac_locked_events
JournalId
JournalId
Ms_ac_pending_request_queue
UpdateMode
JournalId
Ms_ac_request_archive
UpdateMode
456
Temenos Transact
Application Fields
TRANSACTION.CODE
AC.LOCKED.EVENTS
MERCHANT.FLAG
TRANSACTION MERCHANT.FLAG
Table Columns
MerchantFlag
Ms_ac_locked_events
TransactionCode
MerchantFlag
Ms_ac_pending_request_queue
TransactionCode
MerchantFlag
Ms_ac_request_archive
TransactionCode
Ms_transaction MerchantFlag
Table Fields
PRTIAL.BOOKING
AC.ENTRY.PARAM
AMOUNT.TOLERANCE
457
Temenos Transact
Table Columns
AC.ENTRY.PARAM AMOUNT.TOLERANCE
PARTIAL.BOOKING
AC.INWARD.ENTRY MATCH.RES.STATUS
RELEASED.RESERVES
TRANSACTION MERCHANT.FLAG
Table Fields
AC.ENTRY.PARAM Attributes
458
Temenos Transact
Table Record
EB.OBJECT CARD.ISSUE
Table Record
459
Temenos Transact
AC.ENTRY.PARAM SLEEP.TIME.ON.LOCK
AC.ENTRY.PARAM MAX.RETRY.NUMBER
460
Temenos Transact
Corporate
461
Temenos Transact
Islamic Banking
462
Temenos Transact
ID.POOL.PARAMETER
l Configure the Spl Hiba Adj Pl Categ, Spl Hiba Income Categ and Spl Hiba
Expense Categ fields in the ID.POOL.PARAMETER table, to raise profit
adjustment entries for fixed profit deposits. These field values should hold
valid PL categories related to the income/expense/adjustments of Special
Hiba.
463
Temenos Transact
Technology
Interaction Framework
Platform Framework
The following are the sample screen captures of MS SQL database with
metering service.
464
Temenos Transact
465
Technical Notes
Temenos Transact
Application Framework
l DEBUG
l INFO
l WARN
l ERROR
The TAFJTrace.properties file allows to define the default logging level for
COMO. By default, the level will be set to INFO.
467
Temenos Transact
468
Temenos Transact
Banking Framework
469
Temenos Transact
Transaction Code along with the Merchant Flag when the user requests the
details of a reservation to be retrieved.
The getReservations provider API has been changed to return the Transaction
Code and Merchant Flag in the body for each reservation.
holdings-cards-service-v2.0.0
l createCardIssue (POST)
l updateCardIssue (PUT)
l deleteCardIssue (DELETE)
l getCardIssues (GET)
reference-cards-service-v1.0.0
l getCardTypes(GET)
470
Temenos Transact
Corporate
471
Temenos Transact
Islamic Banking
472
Temenos Transact
l Three incoming
l Two outgoing
l One reserved for future use
Arguments Description
473
Temenos Transact
474
Temenos Transact
Retail
l ACCOUNT-CR.MOVEMENT-PAY-INT
l ACCOUNT-DR.MOVEMENT-DUE-INT
475
Temenos Transact
l ACCOUNT-CREDIT-PAY-HIS
l ACCOUNT-DEBIT-DUE-HIS
l INTEREST-CAPTURE.BILL-DUE-HIS
l INTEREST-CAPTURE.BILL-PAY-HIS
l ACCOUNT-DUE.NOTICE-PAY
l ACCOUNT-PAY-PAY-NOTICE
l ACCOUNT-EXPIRE.NOTICE-PAY-NOTICE
l ACCOUNT-CHANGE.NOTICE-PAY
476
Temenos Transact
477
Temenos Transact
Treasury
478
Extensibility APIs
Temenos Transact
Java Extensibility
Hoo-
Package Class Method name Description k*/
API
This hook enables the implementer to update records for any table
atm AtmMessageLifecycle updateRecord Hook
after the ATM request has been processed.
480
Temenos Transact
Hoo-
Package Class Method name Description k*/
API
To convert the given value and return the converted value while
system DataMapper convertFieldValue Hook
mapping data from one record to another.
481
Temenos Transact
Hoo-
Package Class Method name Description k*/
API
atm AtmMessageLifecycle getCharge Enables the implementer to calculate and return the ATM charge. Hook
Enables the developer to get the source from which the payment
payments PaymentLifecycle getSource Hook
message originated and is invoked for channels other than SWIFT.
Enables the developer to get the source from which the payment
payments PaymentLifecycle getSwiftSource Hook
message originated and is invoked for the SWIFT channel.
Provides java hook feature for all the request types from the
payments Message updateFieldValue Hook
external system.
system DataFormattingEngine getHeaderData Enables the implementer to return a string that is used as the Hook
482
Temenos Transact
Hoo-
Package Class Method name Description k*/
API
party Account getContractBalancesRecord Returns the contractBalancesRecord for the account object. API
Gets the narrative which will be updated in the statement lines of HOOK
payments PaymentLifecycle getStatementNarrative
POR.POSTING.AND.CONFIRMATION table.
483
Temenos Transact
Hoo-
Package Class Method name Description k*/
API
PaymentOrderLifecycl Changes a payment order product id for the payment order pro- HOOK
payments setProductId
e cess.
PaymentOrderLifecycl HOOK
payments validatePaymentOrderRecord Validates payment order record.
e
HOOK
payments Message updatePaymentObject Updates the entire payment object.
484
Temenos Transact
Hoo-
Package Class Method name Description k*/
API
instead.
HOOK
contract Calculation calculateTaxAmount Deprecated. Use Calculation.getTaxAmount instead.
Enables the implementer to calculate and return the tax amount to HOOK
contract Calculation getTaxAmount
be applied for the transaction.
485
Temenos Transact
Hoo-
Package Class Method name Description k*/
API
Enables the implementer to filter records from the data extract by HOOK
system DataExporter excludeId
excluding them.
Enables the implementer to transfer the entire data extract from HOOK
system DataExporter transferDataExtract
dataExtractPath to the desired location.
Validates whether the given message type can be sent to the bank.
system Delivery getSwiftRmaStatus API
*Hooks are placeholders in Transact where routines can be attached to an application. For example, version, enquiry, delivery and so on.
486
Wealth Suite
Wealth Suite
Wealth Suite
488
Wealth Suite
This functionality allows the user to view the price history for an instrument as a
table in addition to being able to view the price history for an instrument as a
graph.
489
Wealth Suite
490
Wealth Suite
Click here to understand the installation and configuration updates for this
enhancement.
491
Wealth Suite
492
Installation and
Configuration
Notes
Wealth Suite
Wealth Suite
494
Temenos Banking
Capabilities
Temenos Banking Capabilities
Capability Description
496
Temenos Banking Capabilities
497