Oracle® Fusion
Applications
Financials Implementation Guide 11g Release 1 (11.1.1.5.0) Part Number E20375-01 |
![]() Contents |
![]() Previous |
![]() Next |
This chapter contains the following:
Setting Up a Collector: Points to Consider
Creating Collectors: Worked Example
A collector is an individual or a group of individuals, assigned to a customer to conduct various collections work. Tasks include sending correspondence, reviewing customer history and collecting payment from customers. Prior to creating a collector, the individual must be set up as an employee in Oracle Fusion Human Resources and as a resource in Oracle Fusion Customer Relationships Management (CRM) applications.
Consider the following when setting up individuals as collectors:
A collector can individually be assigned to one or more customers or can be a group member that collects from one or more customers. Evaluate what are the most appropriate collection needs for your organizations.
Collectors can be assigned at the customer, account or site level. Determine how your organization interacts with customers.
Research how your organization divides the work and tasks among collectors.
Collections organization structures can be created in several ways based on the number of customers. There are many ways in which a collections organization is structured. For example, you can group customers according to size, small to large or divide customers regionally or by the monetary volume you do with a customer.
This example demonstrates creating collectors and assigning them as an employee assignment and a group assignment. Infusion American Division Corporation wants to create five individuals as collectors. The Collections Department collects on a regional basis, north, south, east and west. Acme Corporation is a large customer and they want to assign one collector to this account. All five individuals have been created as a Person Party and Employee, a prerequisite to creating a collector. The regions have also been created as groups.
The following information is required for each individual:
Field |
Action |
---|---|
Name |
Employee Name |
Description |
Optional; detail information |
Correspondence |
Name used on sent correspondence |
Telephone Number |
Contact number |
Employee Name |
Active employee list |
Group |
Uses group from setup feature |
Active or Inactive |
Collector status |
An employee assignment is a collector assigned to one customer. You must create individuals as employees before you can set them up as users, resources or collectors.
A group assignment is created to assign work and customers to a group of collectors. You can have multiple employees or collectors in one group.