Skip to main content
Sign in

Search

DOKA-SaaS

How can we help?

Branch and HUB/HUB and Spoke

Manikandan Narayanan
  • Updated

The banking customers are getting accustomed more to online banking, automation and self-kiosk options, the nature of branch banking is getting diminished.

Due to the expansion of the scope of banking services, banks started to setup “Centralized Operations” or “Processing Centers” that cater to multiple processes with specialized focus and reduced Turn-around-Time (TAT), resulting in improved customer experience.

Processing centers help banks to carry out all processing activities at one particular place while only front ending activities are carried out at the different branches of the bank.

This results in better customer service and happy customers, and also provides the branch banking staff with a better chance for cross selling and up selling bank products. This Branch and HUB (also known as Branch & Spoke) functionality could be used for this particular setup.

 

Configuration Settings

  • Activation from Entity Group

To activate the “Hub and Spoke” functionality, a new checkbox “Activate Hub-spoke Functionality” has been introduced in the maintenance transaction for Entity Groups (DBxETG) transaction.

Also, another new checkbox “Attach documents via external system in Registration (SPTDOC)” has been introduced.
This option is placed to enable accessing/using external document management system to attach and maintain documents in the new Registration transaction (SPTDOC). If DOKA system should integrate with an external system via API or Webservice to fetch the files from that system, it can be customized at project level. This checkbox is a placeholder or kind of prototype for future use in product/project.

 

Maintaining Entity Groups (DBxETG):

  • Definition and Routing from Entity

An entity can be defined as a Hub or Branch based on the selection in the checkbox “Hub” in the Entity maintenance transaction (DBxETY).

If the flag is set, that entity is defined as a 'Hub' and if the flag is empty, it is a 'branch'

Maintaining Entities (DBxETY):

Routing definitions for an entity/branch can be defined from the respective entity transaction. Routing is possible to a particular entity hub, or a particular user group or even a particular user.

Routing can be defined per Business sector, Medium and Currency/Amount. Also, within the same Business sector and Medium, different routing can be defined for different Amount.


Example: Import LC opening via Document registered up to EUR 100,000.00 to be routed to a particular hub and above to be routed to a different hub.

Routing in Entity Settings (DBxETY) : 

  • Routing from Party : 
Further to Entity, routing logic can also be defined per party in the Party transaction (DBxPTY). The logic defined here will override the routing logic of Entity.
 
Routing Settings in Parties (DBxPTY) :
 
  • Registration : 
A new transaction “Registration” (SPTDOC) has been introduced for the branch user (front office user) to register the applications/requests received in the branch and route the same to respective hubs, or user groups or even to specific users.
 
Registration screen (SPTDOC): 
 
The branch user can select the respective business modules to which the received application/requests pertain to, update basic details such as customer and amount, scan & attach the application and/or any other documents received, and system will recognize the routing for the input.
In case there is no routing logic defined; branch users can manually route the application/request.
 
Registration attachments:
 
Registration Overview
 
A new transaction Registration Overview (ORTHUB) has been introduced to provide an overview of items/contracts initialized from the Registration (SPTDOC) transaction. Branch users can track the status of the transaction initiated by the branch.
 
Registration Overview (ORTHUB) :
 
 
A new communication box “Message Hub” has been introduced in this transaction (ORTHUB) for branch user to message the Hub user for any query/follow-up.
 
 
Message to Hub user:
 
Update in OFFICE transaction for Hub user
The contracts initiated from Branch user from Registration (SPTDOC) transaction will be available for the Hub user in his OFFICE transaction (landing page) for the option “Incoming Message” with the description in the result as “Registration”.
The new communication box “Message Hub” will also be available in the OFFICE page for communicating with the branch user.
 
 
 
 

Comments

0 comments

Please sign in to leave a comment.