Guidelines for Setting Up Collections Preferences

Oracle Fusion Advanced Collections provides a user interface to guide you through the collection preferences. The two required setup regions are: Global Preferences and Preferences.

You answer questions and make decisions about how the application functions, such as date ranges and defaults. Consider the following decisions before defining preferences:

Decision	Is This Oracle Fusion Applicable?
How many employees, locations and organizations to create?	Yes, depends on the setup of the enterprise structure. Review and verify before setting up Advanced Collections.
Which employees to create?	Yes, determine the number of employees who are involved with the collection process.
Assign collectors?	Yes, how are the collectors going to be assigned; by customer account, account, site or other criteria?
Set up Oracle Fusion Accounts Receivables?	Yes, how's Receivables being set up and what's the impact on Advanced Collections.
Enable AR Transactions Summary Tables?	Yes, a profile option set in Receivables to update activities applied to transactions.
Set up Oracle Fusion Payments?	Yes, set up to use credit cards and automatic fund transfers to apply to transactions.
Set up Units of Measure?	Yes, a Receivables set up needed for transactions.
Set up Security and Users?	Yes, set up through Oracle Fusion Identity Management to grant access to collections.
Set up Notes?	Yes, is an Oracle Fusion Common Application Components (CAC) feature allowing collectors to comment on interactions with customers.
Set up Tasks?	Yes, is a CAC feature allowing collectors or managers to assign follow-up tasks.
Set up Oracle Business Intelligence Publisher?	Yes, but must be verified that Business Intelligence Publisher is working to run collection reports.

Global Preferences

Selections made in the Global Preference region impact the view the collectors see from the Collections Customer Work Area and Collections Dashboard. Global Preferences define the following:

• Default transaction class that appears

• Display of open transactions

• Display of closed transactions

• Number of days for prior and future transactions to be displayed

• Number of days to reschedule work on the dashboard

• Default aging method

• Delimiter used to separate data and the number of characters required to do a search

• Sender or return E-mail address for dunning correspondence

• Maximum grace days before a promise is broken

• Maximum number of days for a promise due date

• Enable bankruptcy

• Allow collector to update transaction attributes

Preferences

Selections made in the Preference region impact the defaults the collector encounters when going through the collection process. Preferences define the following

• Preference set

• Collections business level

• Summarize or age credits

• default conversion rate

• Send method of dunning

• Default contact for unknown dunning recipients

Correspondence

Selections made in the Correspondence table impact the defaults the collector encounters when sending correspondence during the collection process. Correspondence defines the following:

• Preference Set

• Send Dispute Notice

• Dispute Template

• Send Payment Notice

• Payment Template

• Send Promise to Pay Notice

• Promise to Pay Template

Dunning Delivery Using Email

Use the Dunning Delivery Using Email section to configure the email body content of a dunning email. You can configure the email body content in the Email Body field by selecting the Dunning Letter Templates from the Dunning Letter Template drop-down list.

You can create the message with enhanced rich text content in the email body. You can choose various fonts, modify font size and style, and insert logos and links using HTML. The enhanced content improves the user experience for customers who receive dunning letters as an email attachment.

Note: If you've a custom data model, then replace it with the predefined Collections Send Dunning Letters data model to use this feature.