Overview

The Arrangement Microservice functionality is the solution for holding the basic information of arrangements and services bothTemenos Digital and also other systems that need customer arrangements information.

In Temenos Digital, there is a concept called Account Aggregation which is to aggregate account information from other bank’s held by the same customer and provide a seamless experience in the current digital channel (like initiating funds transfers, ability to view all balances in a single place and so on). In order to bring these details into the Temenos Digital fold, external aggregators were used (for example Salt Edge).

In R19 release, these external accounts are held as external arrangements in Temenos Digital and their balances are held in ECB of Temenos Digital. With the release of the Arrangement Microservice functionality the details of the arrangement are moved into a new Arrangement details Microservice.

The Customer Arrangement Microservice functionality allows to hold the contract or account information (the basic information of the arrangement) in a Microservice data store (core model), which is easily updated through ingestion techniques and serviced through APIs so that multiple systems will use this information.

Arrangement MS has the capability to store the Portfolios of the Customer.

Background

In terms of any new contract created by banks, entries should get created at core (Backend) system. Contracts can be Loan account, Deposit account, Current account, saving account and Portfolio for a Wealth customer. If any of the account opened, it have the impacts with customer account entries.

From Temenos Digital UI, new account details should get displayed in the customer dashboard. So that user (End user) can view the account details and avail the account services.

Functionality Overview

The objective of the Arrangement Microservices is to store the new same bank accounts and external accounts in a designated Microservices architecture. Any new account opened in Temenos Digital sends a request to Core banking system and creates an entry for it. As soon as the new account entry created in the core banking system, there is an impact in the customer account details. Customer account details integrated with the Arrangement Microservices using a sophisticated Integration framework. Whenever there is an entries and new contract created in the core banking system, an event which is configured passes the details to the Arrangement Microservices on an asynchronous manner. This also holds the Portfolio Id for a Wealth customer along with the Portfolio indicator. Investment strategy and Service Type of the Portfolio along with Portfolio specific information is also held for a Wealth customer.

To list a few features (included but not limited to) that are used in Arrangement Microservices are:

• Capture the contract details created by Customer.
• Capture the payment schedule details for the contract.
• Support both Real Time and Near time processing style.
• Integrate with multiple systems for processing.
• Capture Portfolio related information for a Wealth customer.

Data Model

This section explains the various entities of Arrangement Microservice and their respective roles.