You are on page 1of 7

Setting Up Advanced Collections

1. Oracle Advanced Collections provides a user interface to guide you through
the implementation process. As you answer questions and make decisions about how you will use the application, Advanced Collections sets system profile options in the background at the site level. It also performs setup tasks, such as displaying tabs and creating scoring engines. After completing your implementation, you can continue to use the Checklist to manage and update key features such as scoring and strategies.

2. If you are upgrading from a previous version, Oracle Advanced Collections will
populate the Questionnaire and Checklist to reflect your earlier product configuration. You must review the Questionnaire and Checklist to verify that the settings correctly migrated and support your business practices. Make changes if necessary. If you use dunning plans, you must change the default collections method in the Questionnaire from strategies to dunning plans. The Questionnaire and Checklist set profile options at the site level and will not affect existing profile options set at the user, application, or responsibility level. Your responses to the Questionnaire and Checklist will not override any profile options previously set at any level other than the site level.

3.

Process Flow for Advanced Collections
1. Concurrent program extracts raw data on transactions from Oracle Receivables; scores these objects; identifies the objects as delinquent, predelinquent or current; adds customer data; and stores the records in Oracle Advanced Collections tables. 2. User logs in and navigates to Collector’s work Queue to see the assigned work. 3. User views information on delinquent customers and collections work assignments displayed in Collector's Work Queue and selects a work item to launch Advanced Collections. 4. User reviews customer collections profile; delinquency information; histories; strategies and work assignments; aging; and notes. 5. User processes work assignments and records information on payments, promises to pay, or disputes. New payment information is sent via Oracle Receivables to Oracle Payments for authorization. 6. Upon authorization, payment information is sent to Oracle Receivables for processing and updating of customer's receivables records. 7. Upon authorization, payment information is sent to Oracle Receivables for processing and updating of customer's receivables records. 8. Collections correspondence is sent using Oracle XML Publisher. Correspondence event is recorded in customer history. 9. Agents can view information about collections activities, customer payments, disputes, and promises on the History tab and by running reports.

Process Flow for Advanced Collections

Payment. promise to pay and disputes Agent views Collections Activities. Disputes and promises on the history Tab and by running reports Collections correspondence is sent using Oracle XML publisher. Process Flow for Strategies .Run Concurrent programs User Logins to see assigned work User selects a work item to launch IEX New payment info sent to IBY via AR for authorisation Upon authorisation. payment info sent back to AR User processes work items and records info on payments.

Concurrent programs are run according to an established schedule and scoring occurs. Strategies are executed based on scores. 5. Process Flow for Strategies . 4. Managers and agents can override the established collections work items by removing or adding work items to the strategy for the object. If the first work item is manual. it is posted in Collector's Work Queue to the collector who owns the customer. Strategy engine keeps track of when a work item is completed and initiates the next item. Managers create scoring engines and relate the score ranges to strategies. required and optional work items. 3.1. the system performs the work and creates a history record. Managers define collections strategy templates. Work items are initiated. If the work item is automated (such as send a letter). Strategies can contain 2.

Customer (or . fax or e-mail) to send for each score range.Managers Define Collection Strategy template Programs run to generate scores Work Item posted on collector’s work queue No Strategies are initiated and work items created based on scores Is the work item automated? Yes System performs the work and creates a history record Strategy keeps a track of when the work is completed and initiates next item Process Flow for Dunning Plans 1. Managers determine dunning score ranges and associated dunning letters and send method (print.

or delinquency) can be rescored and. Dunning letters are automatically sent to customer via the Oracle XML Publisher. The system tracks payments made by customers. 6. the customer (account. The Dunning Plan concurrent program is run. a new and more aggressive dunning letter is sent. Optional dunning callbacks are defined. or delinquency) scores determine which dunning letter to send. bill to. If no payment is made. 5. at the next bill cycle. If payment is still not made. account. the Dunning Callback concurrent program can be run to create callbacks. bill to. . Dunning history is recorded. 4. which are automatically posted to an agent's Collector's Work Queue Task node. 3.2.

the customer is rescored and more aggressive dunning letter is sent during next billing cycle .Managers determine the scoring ranges. Callbacks are posted the agent’s work queue If the payment is still not made. Dunning call backs are defined (Optional) Dunning Plan Concurrent Program Is run System Tracks the payment Yes Dunning Letters are automatically sent to the customers (Oracle XML Publisher) Is Payment made by customer? No Dunning call back program is run. associated dunning letters and the method of sending them.