1.10 Business Configurations

Oracle Banking Collections and Recovery provides maintenance screens that facilitate to setup and maintain day zero configurations required to perform various transactions efficiently.

The maintenance screens facilitate in following essential configurations:
  • Lookups: Lookups help to configure predefined values for drop down lists that are used for processing various information in the system.
  • Product Processor: Product Processors facilitate to receive details of the delinquent accounts from various host systems.
  • Auto Number Generation: Definitions for auto number generation facilitates to generate case numbers automatically by the system with a predefined logic.
  • Workflow: Workflows help to create predefined life cycle for tasks that are performed by the system or collector. It consists of statuses through which a task moves based on certain predefined rules and conditions.
  • Task: Tasks help to define type of activities to be performed for collection of amount due from the customer. The tasks are either executed automatically by the system, or the tasks need to be performed manually by the collector.
  • Call Action: Call Action helps to configure actions types and their corresponding results for the tasks. It also helps to configure the collection statuses applicable on an account based on action and results captured for the task performed.
  • Strategy: Strategy helps to group tasks that are applicable on the accounts associated to various segments.
  • Segment: Segment facilitates to group accounts for applying various strategies to collect the amount due on the accounts.
  • User Group: User Group facilitates to manage the collectors who perform various tasks. It helps to assign collectors to the relevant user groups, and also assign supervisor for each user groups to manage the team of collectors.
  • User Assignment: User Assignment facilitates to assign accounts, customers, and tasks to the collectors based on rules.
  • Promise Type: Promise Type facilitates to define promises types that are used to create promise to pay which is used to track the promise of payment made by the customer.
  • Seed Data: Seed Data facilitates to create seed data codes for various seed data types for which inbound data is received from the product processor.
  • Communication: Communication helps to define template and other parameters for generating various types of communication that are sent to customers.