Introduction to Australia Base

Temenos Transact provides the functionality for 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 payments exceptions, and other day to day functions.

This functionality allows the bank to comply with the Australian Banking Code of Practice, which requires the banks to be able to assist the vulnerable customers.

The benefits of this functionality are:

• Ability to login to the Home Page of the Call Centre or Customer Service Agent and view the available features
• Ability to service a customer via the Single Customer View which has the AUMB features.
• Ability on Arrangement Overview to view the AUMB features and make amendments to the account.
• Ability to login to the Home Page – Administrator and view the AUMB features.

Alternate Account No Generation and User Transaction Restriction

The Alternate Account Number Generation functionality allows banks to automatically generate an alternate account number for each account as per the bank configuration.

Temenos Transact facilitates the automatic generation of alternate account numbers in numeric number format where the starting number is defined by the bank and the system keeps incrementing this number by one for every other alternate account number that is generated.

The CMBASE.ALTERNATE.ID.PARAM parameter application is used to configure the way the alternate accounts numbers are generated during the arrangement creation.

In the User Transaction Restriction functionality, if a bank user is also a customer of the bank and has a Temenos Transact account, then the system will not allow the user to credit or debit that account based on user login.

The User Customer Number field is added to the CUSTOMER application and it is used to manually capture the Customer Number of the bank user.

The system will check whether the customer of the account (arrangement) is the same as the User’s Customer Number stored in the USER application. If it is the same, then the system will not allow the user to commit the credit or debit activity.