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.
3. 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.

Process Flow for Advanced Collections

1. Concurrent program extracts raw data on transactions from Oracle
Receivables; scores these objects; identifies the objects as delinquent, pre-
delinquent 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

 Run Concurrent
programs

User Logins to
see assigned
work

User selects a
work item to
launch IEX

New payment
User processes info sent to
work items and IBY via AR for
records info on authorisation
payments,
promise to pay
and disputes Upon
authorisation,
payment info
sent back to AR

Agent views Collections

Collections correspondence
Activities, is sent using
Payment, Oracle XML
Disputes and publisher.
promises on
the history Tab
and by running
reports

Process Flow for Strategies

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

Process Flow for Strategies

 Managers
Define
Collection
Work Item
Strategy
posted on
template
collector’s
work queue
Programs run to
generate scores

No

Strategies are
initiated and Is the work
work items item
created based automated?
on scores

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, fax or e-mail) to send for each score range. Customer (or
 account, bill to, or delinquency) scores determine which dunning letter to
send.
2. Optional dunning callbacks are defined.
3. The Dunning Plan concurrent program is run.
4. Dunning letters are automatically sent to customer via the Oracle XML
Publisher. Dunning history is recorded.
5. The system tracks payments made by customers. If no payment is made, the
Dunning Callback concurrent program can be run to create callbacks, which
are automatically posted to an agent's Collector's Work Queue Task node.
6. If payment is still not made, the customer (account, bill to, or delinquency)
can be rescored and, at the next bill cycle, a new and more aggressive
dunning letter is sent.
Managers
determine the
scoring ranges,
associated
dunning letters
and the method Dunning call
of sending backs are
them. defined
(Optional)

Dunning Plan System Tracks

Concurrent the payment
Program Is run

Yes

Dunning
Letters are
automatically Is Payment
sent to the made by
customers customer?
(Oracle XML
Publisher)
No

Dunning call
If the payment back program
is still not is run.
made, the Callbacks are
customer is re- posted the
scored and agent’s work
more queue
aggressive
dunning letter
is sent during
next billing
cycle