Reducing Complexities through Smart & Innovative Solutions

Safe Harbor Statement

The data presented in this presentation is intended to be an outline of our general corporate direction. It is intended for
information purpose only and may not be incorporated into any contract. It is not a commitment to deliver any material,
code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing
of any features or functionality described for Profinch products and services remains at the sole discretion of Profinch
solutions Private Limited.

Copyright © 2015: All rights reserved

OBDX - PWT

• Overview
• Architecture
• Admin Module
• Retail Module
• Corporate Module

3
 OBDX: Oracle Banking Digital Experience
• Next-generation digital banking platform for internet and mobile banking
• Omni-channel solution
• Component based architecture with clear separation of tiers and flexibility to deploy
application services tier without presentation tier
• Open and best of industry standards based architecture-SOA based, domain driven
design, REST API’s
• Fintech ready API platform –A platform enabling partner ecosystem
• Resilient and loosely coupled UX architecture based on HTML5, jQuery, Knockout,
Sass-Built for touch points of today & tomorrow, Configurable and customizable
• Enables standards based integration – Well documented host adapters
• Secure by design –Across layer ,pluggable security
• Push notification and authentication through alternative login (otp, biometric, pattern
based)
• Chatbots, social media banking –transfer money to Facebook contacts
• E-Wallets support, Merchant payment, QR Code based payment
4
Architecture Overview

• Best of Breed and Modern Technologies in each of the Layers

Customer Segments

Customer Access Points

Presentation Tier

Framework
Business Services Tier

Integration Tier

ESB
CORE PRODUCT PROCESSORS

5
 Architecture :SOA based Application Platform

Logical Component Diagram

POST/GET/PUT/DELETE
APPLICATION_JSON

• HTML front end application Oracle Digital Platform

using Knockout /submissions /collaborations /content /enumerations /parties REST
• Mobile first, responsive /productgroups
approach
• REST as a first-class citizen Services
Service
Extensions
Service
Constraints
• Focus on resources
• JSON payload Authorization Approval Audit Monitoring Logger

• Oracle REST standards

alignment app

• Publish documentation with domain

Security

sample request and response

OEM
ORM

Repository
• Adapters to host systems obp-adapter external-adapter
SOAP flexcube-adapter
• Pre-built adapter for Oracle
Core Core Banking Platform

Confidential
7
OBDX - Admin Module

OBDX - Administration Module

• Administrator Dashboards
• Admin Maintenance and System Rules and Roles Management
• User Management
• Customer Management(Preferences/Limits/Account
Access/Approvals)
• Audit Log and Reports

8
Administrator Dashboards

OBDX Admin module consist of below Administrator Dashboards.

• System Administrator Dashboard: This dashboard is designed for a user having

system maintenance rights.
• Administrator Maker Dashboard: This dashboard enables bank administrator to
perform maintenance functions for a particular corporate party.
• Administrator Approver Dashboard: Bank administrator dashboard also includes
the Activity Log widget and Pending Approvals widget. Activity Log widget displays
the list of transactions and maintenances done by the user during the day along with
their approval status. Pending Approvals widget (displayed only to the Bank
administrator with Approval rights) displays the list of transactions and maintenances
that are assigned to the user for approval..

9
System Administrator Dashboard – Overview
•System Administrator user can perform below system maintenance
using this dashboard. ➢Maintain System rules and
roles.
➢Define Transaction Limits,
Duration and Cooling Period
Limits.
➢Maintain payee Restrictions.
➢Mapping of Biller Category
and Payment Purposes
➢Onboard Merchants, to
channel banking
➢Maintain Transaction working
windows and blackouts
➢Map User Groups to Subjects
➢Perform Alert Maintenance
➢Audit Log, etc

10
Administrator Maker Dashboard – Overview
Bank administrator Maker’s role involves one time / rarely used and Day 0
maintenances in addition to day to day operations. .
➢Create Users and update user
information such as email
addresses and names.
➢Create new bank
administrators.
➢Change or reset a user’s
password
➢Control user access with
permissions
➢Send alerts to users
➢Set up transaction limits.
➢Generate and download MIS
Reports
➢View audit log
➢User Account Access

11
User Management
User Management function enables bank administrator to onboard and manage users
along with their login credentials for channel banking access. . This module facilitates
channel banking access to the bank’s internal users (administrators) and external users
(customers).

User Types are:

• Corporate User
• Retails User
• Administrator

Pre-Requisites
➢ Application roles and child roles are maintained
➢ Transactions are associated with each child role
➢ Transaction (User Management) access is provided to Bank administrator.
➢ Approval rule set up for Bank administrator to perform the actions.
➢ Party Preference is maintained for corporate user 12
User Management - Create New User
Addition to day to day operations.
Bank administrator logs into the system and navigates to the User
Management screen. This function allows the administrator to
create internal and external users.

To create a new user:

➢Select the User type.

➢Party ID or party name for Retail/Corporate user.
➢In the Personal Information section, enter the required details
or it is fetched from host system..
➢In the Contact Details section, enter the required details.
➢In the Limits and Roles section, select the limit to be mapped
from the Limit list.
➢Select the roles to be mapped from the Roles check box.
➢In the Status field, select the appropriate option.
➢Click Save to save the user details.
➢The success message of user creation appears along with the
transaction reference number.

User Management - Edit User - This function enables the

Administrator to edit the existing user details. 13
System Rules and Roles
Below Application Roles and child exists OBDX system for respective user
types.

Application Role Child Roles

Retail User Customer
Maker
Corporate User Checker
Viewer
Admin Maker
Administrator
Admin Checker

14
 Create Application Role
System Administrator user can create/update/delete using Application Roles menu option.

To create an application role:

➢In the Authorization System - Application Roles screen, click Create. The Create Application
Role screen appears
➢In the Name field, enter the name of the application role.
➢In the Display Name field, enter the display name
of the application role.
➢In the Description field, enter the description of
the application role.
➢In the Map Enterprise Roles section, click Add.
The Search Enterprise Roles And Map Them
With Application Role section appears.
➢The mapped enterprise role appears in Added
Enterprise Roles section.
➢Click Create to create the role.
Update Application Role - This function enables
the Administrator to update the details of an
existing application role
15
Create Rule
• System rules are defined to set different parameters for each enterprise role. Various
parameters can be set for each enterprise role are party mapping required, Limits
Check, Party Preferences Check, Account Transaction Mapping and Approvals
Check. Enabling these parameters at enterprise role, enforces the system to check if
respective maintenances are available for users associated with those enterprise roles.
• E.g. if Approval check flag is enabled for ‘Corporate User’ type of enterprise role;
then transactions initiated by corporate type of users will follow the approval
maintenance for a party mapped to user.
If approval check flag is disabled for ‘Retail User’ type of enterprise role, then
transactions initiated by retail user will not follow the approval maintenance and
will get auto-approved by the system.

• Pre-Requisites
➢Transaction access is provided to System Administrator.
➢Approval rule set up for System Administrator to perform the actions.
➢Enterprise roles are maintained in application.
. 16
System Rules
This screen allows the system administrator to search and view existing
system rules, and create new system rule. To set the system rules:
➢From the Enterprise Role list,
select the appropriate option.
➢In the Party Mapping Required
field, select the appropriate
option.
➢In the Party Preferences Check
field, select the appropriate
option.
➢In the Account Transaction
Mapping, select the appropriate
option.
➢In the Approvals Check field,
select the appropriate option.
➢In the First Time Login Steps
field, select the appropriate
option.
➢In the Limits Check field, select
the appropriate option.
➢Click Submit to save system
rules. The success message
17
appears.
 Role Transaction Mapping /Authorization
• Authorization allows an organization to protect its resources by defining and managing
policies that control access to, and usage of, these resources. Access privileges are
defined in a policy by specifying who can do what to which resource. Current
Authorization supports the creation of Role Based Authorization Policies. This
mapping allows users in external groups to access resources as specified by the
Application Roles.
Authorization consists of multiple policy
domains for logical separation of policies.
Each Policy Domain holds multiple policies
for that policy domain. Policy determines
access permissions on different resources
specific to each entity. The policy consists of
relation between one or more resources/
entitlements and roles.
Below diagram shows the relationship and
hierarchy of Authorization components like
Policy Domain, Policy, Resources, and Roles.
. 18
Policy Domain
Using this option you can create a new policy domain.
Menu Dashboard > Role Transaction Mapping > Policy Domain.

To create a new policy

domain:
➢Navigate to Policy
Domain Menu and
enter below details.
➢In the Name field, enter
the name of the policy
domain.
➢In the Description field,
enter the description of
the policy domain.
➢Click Create.

19
Create New Policy
Using this Option you can create a new policy.
To create a new policy:
➢In the Policy Domain section, click the required policy
link. The Add New Policy section appears.
➢Click Create. The Create New Policy screen appears.
➢In the Effect field, select the appropriate option.
➢In the Name field, enter the name of the policy.
➢In the Description field, enter the description of the
policy.
➢In the Map Resources section, click.
➢The Create New Policy screen with expanded Map
Resources section appears. Click Search.
➢The Create New Policy – Map Resources screen with
search results appears. Select a resource to be mapped and
click.
➢Click Done.
➢The Create New Policy screen with Added Resources
section appears. Repeat the above steps for Map
Entitlements, Map Application Roles and Map Enterprise
Roles section.
➢Click Create. The success message appears.
20
Limits Management

Limits are defined by the bank to set up amount and duration based
restrictions on the transactions that can be carried out by the user.
As part of limits definition maintenance, following limits can be defined:
• Transaction: It is the initiation limit with min and max amount defined
typically for a user with role ‘Maker’
• Cumulative: It is the collective transaction amount limit for all the
transactions that can be performed during a day and maximum number of
transaction in a day
• Cooling Period: It is the time set by the bank during which fund transfer is
not allowed to a newly added payee.

21
Spend Category Maintenance
Spend Category maintenance allows the System Administrator to create, modify or expire
categories. For each of the Spend Category, System Administrator shall be able to map there
corresponding sub categories under which the transactions will be tagged. This maintenance is
done only for retail type of parties and is not applicable for corporate type of parties

22
Spend Category Maintenance
Spend Category maintenance allows the System Administrator to create, modify or expire categories.
For each of the Spend Category, System Administrator shall be able to map there corresponding sub
categories under which the transactions will be tagged. This maintenance is done only for retail type
of parties and is not applicable for corporate type of parties
To create a spend category:

➢Click Spend category

maintenance. Click on create.
➢Enter the relevant information
in Category Code and
Category Name.
➢Enter the Sub Category Code
and Sub Category Name.
➢Click on add if more
categories need to be added.
➢Click Save to save the spend
category.

23
Goal Category Maintenance
Goal Category maintenance allows the System Administrator to create, modify or
expire goal categories. For each of the Goal Category, System Administrator can map
the Product under which the goals will be opened. This maintenance is done only for
retail type of parties and is not applicable for corporate type of parties.

To create a goal category:

➢Click Goal category

maintenance. Click on create.
➢Enter the relevant
information in Category Code
and Category Name.
➢Enter the Expiry Date.
➢Select the Category image by
clicking on choose file.
➢Click Save to save the goal
category.
24
 Manage Brand
Manage Brand is an administrative maintenance that allows the System Administrator to define the theme
using brand logo, colors, fonts and font sizes. System Administrator can configure the style/theme by selecting
brand logo, header colors, background colors, label colors, button colors, font color, header size, font type,
font sizes for header texts, menu, buttons etc. The administrator can define multiple themes with the above
mentioned attributes and once defined, the administrator can activate one of the theme from the available list.

To create a manage brand:

➢Click Manage Brand under User

Experiences. Click on create.
➢Enter the relevant information in Brand
Name and Brand Description.
➢Enter the relevant details in Customize
Brand fields.
➢Click Save to save the manage brand.

25
Limits Management - Transaction - Create
Using this option you can create a new Limits Management for Transaction.

To create a transaction limit:

➢In the Limits Management screen,

click Create. The Limits
Management – Create screen with
Transaction tab appears.
➢In the Transaction tab screen,
enter the code in the Limit Code
field.
➢In the Limit Description field,
enter the description of the limit.
➢Select the Currency from the drop-
down list.
➢In the Minimum Amount and
Maximum Amount field, enter the
minimum and maximum amount
for a transaction in local currency.
➢Click Save to save the created limit.

26
Limits Management - Cumulative - Create
Using this option you can create a new Cumulative limit.

To create a cumulative limit:

➢Click Cumulative tab. The Limits

Management – Create screen with
Cumulative tab appears.
➢Enter the relevant information in
Limit Code and Limit Description
field.
➢In the Frequency field, select the
frequency i.e. Daily or monthly.
➢Select the Currency from the drop-
down list.
➢Enter the Cumulative Transaction
Amount per day in the Cumulative
Transaction Amount field.
➢In the Maximum Transactions
field, enter the value for maximum
number of transactions.
➢Click Save to save the created
27 limit.
Limits Management - Cooling Period - Create
Using this option you can create a new Cooling Period. To set up multiple amount and
time limit slabs:
➢Click the Cooling Period tab. The
Limits Management – Create
screen with Cooling Period tab
appears.
➢Enter the relevant information in
Limit Code and Limit Description
field.
➢Select the Currency from the
drop-down list.
➢From the From Time and To
Time field, select the appropriate
day, hours and minutes.
➢In the Cumulative Transaction
Amount field, enter the collective
amount that is applicable for the
defined cooling period.
➢Click Add Time Period if you
want to create more than one
amount and time limit slabs.
➢Click Save to save the created
28
limit.
Limits Package Maintenance

As part of the limits package definition, the created limits can be mapped to
relevant transactions and/or roles.
The limits packages once created can be associated at User Level, Party Level and
Role Level
Prerequisites:
• Required Limits (i.e. Transaction/ Cumulative/ Cooling period) should be
defined for association to transactions in limits package.

29
Limit Package Management - Create
Using this option, bank
administrator can create a limit package based on
the details given as per the fields.

To create a limit package:

➢ In the Limit Package Management screen, click
Create. The Limit Package Management - Create
screen appears.
➢ In the Limit Package Code field, enter the code
for the limit package.
➢ In the Limit Package Description field, enter the
description of the limit package.
➢ From Available To Role list, select the
appropriate role.
➢ Select the Currency from the drop-down list.
➢ In the Transaction and Limits section, select the
name of the transaction and effective date of the
limit package.
➢ Select the appropriate limit from Cumulative
Limit Daily, Cumulative Limit Monthly,
Transaction Limit and Cooling Limit.
➢ Click Add Transaction and repeat the steps 5 and
6, if you want to assign limits for more
transactions.
➢ Click Save to save the limit package.
30
Transaction Working Window

A transaction working window is the period in a day, when a transaction can

be initiated, approved and processed.
This is essentially like business hours, for a transaction within which
electronic payments, such as domestic transfers, international transfers etc.,
must be submitted for an entry in the system so that the transaction is
processed with same value date.
A working window is maintained by the Bank administrator for each
transaction for which the value date is applicable for processing.

31
Transaction Working Window - Create
Bank administrator can create new transaction working window maintenance for
the selected transaction. Working window can be set as ‘Normal’ working
window (for all days of the week) and ‘Exception Window’.
To create normal window:
➢ Select the working window.
➢ Select Normal Window tab and Click Create.
➢ Select Effective date of working window.
➢ Select the type of user for whom the
transaction working window is being
maintained
➢ Select specific financial transaction, for
which a working window is maintained
➢ Select type of working window for the
transaction. The type can be “Limited
Time”, “Open All Day” or “Closed All
Day”.
➢ If you select the Window Type as Limited
Time, from the From Time / To Time list
select the start and end time of the
transaction working window
➢ In the Other Details section, from the
Treatment Outside Normal Window field,
select the appropriate option.
➢ Click Save to create the transaction working
window. 32
Exception Window - Create
Bank administrator can create new transaction working Exception window
maintenance for the selected transaction.
To create Exception window:
➢ Select the working window.
If you select Exception Window tab and Click
Create.
➢ From the Exception Date list, select the
start date of the working window -
exception
➢ Select the type of user for whom the
transaction working window is being
maintained
➢ Select specific financial transaction, for
which a working window is maintained
➢ Enter Reason for exception for e.g. a
national holiday.
➢ Select type of working window for the
transaction. The type can be “Limited
Time”, “Open All Day” or “Closed All
Day”.
➢ If you select the Window Type as Limited
Time, from the From Time / To Time list
select the start and end time of the
transaction working window
➢ Click Save to create the Exception 33
transaction working window.
Transaction Blackout

• A blackout period is duration of time when access to something usually available is

prohibited.
• When a bank administrator maintains a transaction blackout, for a period,
transaction/s are not accessible to users of the bank’s retail and corporate or even to
the Bank administrator users for a pre-set time period.
• The Bank administrator may use the time, when a transaction is blacked-out, to do
necessary maintenances.

• Administrator can create new transaction blackout maintenance for the selected
transaction. User needs to select the particular transaction and user type for whom
blackout needs to be applied.
• Further user can set up blackout type:
• Full – Black out for the entire period.
• Daily - Blackout between start and end time daily, for the days set.

34
Transaction Blackout - Create
Using this option Bank administrator can create new transaction Blackout.
To create new transaction blackout:
➢ Navigate to Transaction Blackout Menu and
Click Create.
➢ From the Transaction list select the
appropriate option.
➢ From the User Type select the appropriate
option.
➢ From the Blackout Type select the
appropriate option:
➢ If you select Full Day:
➢ a. From the Start On list, select the
start date and time of the transaction
blackout.
➢ b. From the End On list, select the
end date and time of the transaction
blackout.
➢ If you select Daily:
➢ a. From the Date Range list select the
start and end date of the transaction
blackout.
➢ b. From the Time Range list select the
start and end time of the transaction
blackout.
➢ Click Save to create the transaction blackout.
35
Party Preferences

Party Preferences maintenance enables the bank administrator to define certain

parameters values as per the corporate requirements. This maintenance is done only
for corporate type of parties and is not applicable for retail type of parties. Parameter
values maintained against a corporate party defines the system behaviour for the
following:

➢Cumulative daily limits per transaction for the corporate party

➢Transaction limits for the users
➢Type of Approval flow applicable
➢Channel access preferences
➢Availability of Corporate Administrator facility

36
Party Preferences - Create
Using this option, bank administrator can configure party preferences for a
specific party. To create the party preferences :

In the Party Id field, enter the party Id of the

corporate user whose party preferences you want
to view.
➢ Navigate to Party Preferences Menu and
Search for Party ID and Click Create.
➢ From the Cumulative Daily Limits list, select
the appropriate option.
➢ From the User Limit list, select the appropriate
option.
➢ In Grace Period field, enter the appropriate
value.
➢ From the Approval Flow list, select the
appropriate option.
➢ From the Channel Access list, select the
appropriate option.
➢ From the Enable for Corporate Administrator
Facility, select the appropriate option.
➢ Click Save to save party preferences.

37
Party to Party Linkage

Party to Party linkage is required by medium and large corporates if the user(s) of the
parent company needs to access accounts of the subsidiary companies. For e.g. consider
a case wherein say ‘ABC Industries’ is the parent company with a subsidiary company
‘PQR Enterprises’ and the users of ABC Industries needs to access accounts of PQR
Enterprises to carry out transactions and/or inquiries. The corporate will provide a
mandate/ board resolution to the bank for creation of Party to Party linkage. Bank
administrator will setup a Party to Party linkage by selecting the parent party and the
parties to be linked.

Pre-Requisites
• Party preferences should be maintained for the parent as well as the party to be linked
• Channel Access should be enabled for both the parent as well as the party to be linked

38
Party To Party Linkage - Create
The Bank administrator gets a request to create a Party to Party Linkage in the
system with details of the parent party and the party to be linked. As part of
linkage creation, more than one party can be linked to the parent party selected. .
To create a new party to party
linkage:
➢Search the parent party by party ID or
party name as specified in Party to
Party Linkage - Search section.
➢Click Create.
➢There will be a linked party section
with an option to search a party to be
linked.
➢Search a party to be linked by party
ID or party name as specified in ‘Party
Search’ section.
➢Click Add to if the user wishes to
Add more than one linked party to the
selected parent party.
➢Click Save to save the linkage of the
linked parties with the parent party.

39
Account Access

Account access management is a maintenance designed to allow and/or

restrict the corporate accounts for online access.
With this access defined, the corporate can transact on their accounts through
internet banking. They can view accounts, statements, initiate payments,
upload files, and various other transactions available for corporate users.
On the basis of the request/ mandate received from the corporate clients, the
administrator will use this maintenance to enable the corporate accounts to be
accessed online. Further, users working on behalf of the corporate clients will
be mapped to such accounts and their relevant transactions.
Below are the account access components:
• Party Account Access
• User Account Access

40
Party Account Access - Mapping (Create)
The Bank Admin gets a request with the list of account(s) and transactions for
which access needs to be provided to the party.

To provide the party with

account and transaction access:
➢Enter the party ID or party and
Click Search.
➢ For a searched party, Own
Account Mapping Summary
appears which will show all the
account type.
➢Click on the account type. The
Party Account Access Screen -
Create appears

41
Party Account Access - Mapping (Create)

➢ All the accounts held by the selected party as a

relationship with the bank as available in the core
banking system will be fetched and displayed in the
respective categories i.e. CASA, Term Deposits and
Loans.
➢ In case of mapping of linked party accounts to the
parent party, user will select the parent party as part of
party search section and click Map against the linked
party of which account access is to be provided.
➢ Navigate to the specific category tab viz. CASA, Term
Deposits, Loans etc., and select a global check box of
Map all accounts to enable all the existing accounts under
the selected category for channel banking (on screen, it
will serve as a Select All function). OR If specific
accounts are required to be given access then the user
needs to select the respective check boxes preceding the
account number.
➢ To map the new accounts, select appropriate option
from Map Accounts field; Select Auto if you wish to
allow access to all future CASA/ Term Deposit/ Loans
accounts. OR Select Manual if you wish to explicitly map
new accounts and transactions.
➢ Click Next. The Party Account Access - Create
(Transaction Mapping) screen appears.

42
Party Account Access - Mapping (Create)

➢To map the transactions to the

account, click against the particular
account number to view the
transaction mapping.
➢Select the respective check boxes
preceding the transaction to be
mapped. OR Select Map All
Transactions, if you want to map
all the transactions to all accounts.
➢Click Save to save the changes.

43
User Account Access- Mapping (Create)
The Bank administrator gets a request with the list of account(s) and transactions
for which access needs to be provided to the user of a specific party.
To provide the user with account and
transaction access:
➢Enter the party ID or party and
Click Search.
➢ For a searched party, there will be a list of
users displayed with information like user ID,
contact details of the user and an indicator
whether there is an account mapping done for
the user.
➢Click on user ID to navigate to Account
Access summary section with two sections
Own Account Mapping Summary and Linked
Party Account Mapping Summary.
Linked party account mapping will only be
available if the selected party has Party to Party
Linkage maintained.

44
User Account Access- Mapping (Create)
➢ All the accounts held by the selected party as a relationship
with the bank as available in the core banking system will be
fetched and displayed in the respective categories i.e. CASA,
Term Deposits and Loans. In case of mapping of linked
party accounts to the user, bank admin will select the parent
party as part of party search section, select the user of the
parent party and click Map against the linked party of
which account access is to be provided.
➢ Navigate to the specific category tab viz. CASA, Term
Deposits, Loans etc., and select a global check box of Map
all accounts to enable all the existing accounts under the
selected category for channel banking (on screen, it will
serve as a Select All function). OR If specific accounts are
required to be given access to the user, then the bank admin
needs to select the respective check boxes preceding the
account number.
➢ Select Apply Party Level Changes Automatically to
automatically apply the party changes. The cookie message
appears indicating the administrator that account mapping
for other category tabs can be done by visiting the
respective tabs.
➢ Click Next. The User Account Access - Create
(Transaction Mapping) screen appears.

45
User Account Access- Mapping (Create)

➢To map the transactions

to the account, click
against the particular
account number to view
the transaction mapping.
➢Select the respective
check boxes preceding
the transaction to be
mapped. OR Select Map
All Transactions, if you
want to map all the
transactions to all
accounts.
➢Click Save.

46
User Group Management
Using this option Bank administrator can maintain the user groups of Bank
administrator and of corporate users of same party ID.
User groups maintained by administrators for Bank administrator users and
corporate users are used while creating approval workflows and approval rules.

Prerequisites:
• Multiple corporate and admin users are maintained.
• Party preference for which the groups are to be created is maintained and is
active.

User Group Management allows Bank administrator to:

• Admin User Group
• Corporate User Group

47
User Groups - Corporate User – Create
Bank administrator logs into the system and navigates to the User Group
Management screen. To create a user group:
➢ The User Type Selection screen appears. Select
the appropriate option. Click Corporate.
➢ Search the Party Id for corporate and click
Create.
➢ The User selection screen appears. Select the
appropriate option.
➢ In the Group Code field, enter the group code.
➢ In the Group Description field, enter the group
name.
➢ In the User Group section, click Add to add
the selected user in the User Group. Once
added, the user name will be removed from the
user drop-down to avoid duplication of users.
➢ Click Save to create the user groups.

48
Approvals

Approval Management function enables the Bank administrator to configure

approval flows for various financial and non-financial transactions on channel
banking for bank’s customers and for administrators.

Approval flow includes configuration of rules for the users with following access
types:
• Maker/ Initiator – User who is a creator of the transaction.
• Authorizer/ Approver – User who authorizes the transactions created by the
maker. His authorization rights are maintained by an administrator.

Approval management supported for Bank administrator users includes;

• Approval Workflow Maintenance
• Approval Rule Maintenance
49
Approvals

• Business scenario
AES Corporation wants to enable
approval workflow for all financial
transactions.
The requirement is – All the
financial transactions will be initiated
by ‘Officers’ of the corporate.
The transactions initiated by
‘Officers’ should be sent to ‘Assistant
Managers’ for 1st level approval.
After the transaction is approved by
any one user from a group of
‘Assistant Managers’ then the
transaction should be sent to
‘Managers’ for final level of
approval.
The transaction processing should
happen only after final approval.

50
Workflow Management – Create
Bank administrator can create approval workflows for corporate users.
By default, user can specify minimum one and maximum five levels of approvals as a part of
workflow.
Administrator can set either an individual user or user group of a corporate as a part of each level of
approval. Approval type (sequential/non-sequential/no authorization) is defined at the party
preference.
To create an approval workflow:
➢ In the Workflow Management screen,
search for Party Id and Click Create.
The Workflow Management - Create
screen appears.
➢ In the Workflow Code field, enter the
workflow code.
➢ In the Workflow Description field, enter
the name of the workflow.
➢ In the Approval Details section, from
the Level 1 field, click a appropriate user
/ user group.
➢ From the User Name / User Groups
list, select the approver user name.
➢ Click Add to add the selected user/ user
group at specific level of approval. OR
Click delete icon to remove specific
approval level.
➢ Click Save to save Approval Workflow.
51
Approval Rule – Corporate User - Create
Bank administrator can create approval rules for the corporate users.
Administrator is allowed to create an approval rule only if the party preference is
maintained and party is in active status.
To create an approval rule for corporate user:
➢ In the Approval Rules screen, enter the search parameters
and click Search. The Approval Rules screen with both
Party ID and Party Name appears.
➢ Click the Party ID link, to view details. The Approval Rule
- Summary screen appears.
➢ Click Create. The Approval Rules - Create screen appears.
➢ In the Rule Type field, select the appropriate transaction
rule type.
➢ In the Rule Code field, enter the code.
➢ In the Rule Description field, enter the rule name.
➢ From the Initiator Type field, click appropriate user / user
group and select the user/ user group.
➢ From the Transaction list, select the transactions to be
mapped to the rule.
➢ In the Amount Range section, enter the appropriate
amount.
➢ In the Workflow Details section, select whether approval
is required for the mapped transactions.
➢ a. If you select Yes option, select the appropriate
Workflow.
➢ Click Create to save the approval rule.
52
Audit Log
• Audit log has records providing information about who has accessed the
system and what operations he or she has performed during a given period of
time. ➢ Audit logs are useful both for maintaining
security and for recovering lost
transactions. As part of this function, the
bank admin and/or system admin can view
details about the transactions and
maintenances performed by different
user(s) in the system. Bank administrator
can create approval rules for the corporate
users. Administrator is allowed to create an
approval rule only if the party preference is
maintained and party is in active status.
➢ The administrator can search records by
providing specific search parameters and
system will display matching records for
the search criteria.
➢ Maintenances
created/edited/deleted/inquired by bank
administrator can be audited through this
function by the system administrator
➢ Transactions carried out by corporate users
can be audited if required by the bank
administrator and also by system
administrator. 53
Reports
Using this option, administrators can generate various adhoc and scheduled
banking reports. Application provides an option to generate and schedule reports
using Oracle Business Intelligence (BI) Publisher and also by using an internal
application.
Following Reports can be generated from application :
• Date wise User Creation Report
• File Identifiers wise Party User Mapping Report
• Party User wise File Identifiers Mapping Report
• Party wise Approval Rule Report
• Party wise File Identifiers Mapping Report
• Party wise Payee Maintenance Report
• Party wise User Groups Report
• Party wise Workflows Report
• Party wise Pending Approvals list Report
• Resources - Child Role Report
54
Date wise User Creation Report
• Report Generation - Adhoc
• Bank administrator logs into the system and navigates to Report Generation
screen. On accessing ‘Report Generation menu, bank administrator has to
select a type of a report which needs to be generated. Other reports parameters
with respect to each report are displayed on the screen as input fields so that
report can be requested with specific data.

55
Date wise User Creation Report
• Report Generation - Scheduled
Date wise user creation report provides a list of users created with particular
application role within given duration. An administrator can schedule the
generation of report with following additional parameters:
• Report Name
• Party ID
• Frequency
• Date Range
• Further, user has to select a format is which the report needs to be generated.

56
THANK YOU
.

57