How to set preferences for Oracle Fusion Advanced Collections

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.

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.

Field	Value
Select the default Transaction Type for the Transactions tab	Select Invoice, other transaction choices are all, credit, or debit memos.
Automatically display closed transactions on Transaction tab	Yes is selected to view closed transactions as part of the customers history.
Automatically display current transactions on Transaction tab	Yes is selected to view current or open transaction the customer has pending.
Enter the number of days before the current date the transaction date range should start	1 to 9999 is the range that can be used.
Enter the number of days after the current date the transaction date range should end	1-9999 is the range that can be used.
Enter the maximum number of days work can be rescheduled on the dashboard	1-9999 is the range that can be used.
Enter the number of days after submitting an adjustment or dispute that an activity is generated	1-9999 is the range that can be used.
Select the default Aging Method	Example, 5 Bucket Aging. Several aging buckets can be defined and may be available.
Enter the delimiter used to separate customer, account and site on the Collections Dashboard	Select the pipe symbol, greater than, dash, or colon symbols.
Enter the minimum number of characters required to perform a search	Three characters is the Oracle recommended number for a search. 1-9999 is the range that can be used.
Enter the sender or return E-mail for dunning correspondence	The default return E-mail for customers to respond
Allow collector to update transaction attributes	Yes is selected to allow updating the below fields on the Collections page: PO Number Bill to Contact Comments Translated Description Field PO Revision PO Date
Default Receipt Method from Transaction	Enable to determine the receipt method based on a transaction.
Email open transaction copy	Select the appropriate option to resend, or resend and regenerate.
Send or return email address for dunning correspondence	Allows you to specify the email address that will be used as the return address for dunning letters sent to customers.
Maximum number of transactions to send with dunning letters	Controls the maximum number of individual transactions that will be included and printed on a single dunning letter.
Number of grace days before a promise is broken	Defines the number of extra days allowed after the promised payment date before the system considers a promise to pay as broken.
Maximum number of days to make a promise	Controls the latest possible date that a collector can set as the due date for a promise to pay.
Common currency for metric calculations	Specifies the base currency used to standardize all financial metrics.
Past date to be used for metric calculations	Determines the effective date the system uses to calculate collection metrics such as total overdue amount, delinquency status, and aging buckets.
Enable bankruptcy	Allows to record bankruptcy details so that system disables dunning for that customer and collection actions are stalled.
Number of parallel processors	Controls how many parallel Dunning Letter processing threads or jobs can run simultaneously for background processing tasks. Typically set to 1 to indicate that the processes run sequentially.
Batch size	Specifies how many customer records (or related entities) are grouped and processed at a time within each thread when executing background collection processes. This setting helps manage memory and processing efficiency by controlling the size of data chunks handled in each processing cycle.

Preferences

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

Preferences Table Column Name	Field Value
Collections Preference Set	Example, Common Set.
Select the Collections Business Level	Select Account, Customer, or Site.
Select whether open credits should be aged or summarized by default	Select Summarized or Aged.
Select the conversion rate type for converting multicurrency transactions	Example, Corporate.
Select the default method to send collections notifications	Select E-mail, fax, or print.
Enter the default contact for unknown dunning recipients	Accounts Payable Manager. User defined if no contact is listed.

Correspondence

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

Correspondence Table Column Name	Field Value
Collections Preference Set	Example, Common Set.
Send Adjustment Notice	Select yes to notify the customer of adjustments made to their account.
Adjustment Template	Select the delivered template.
Send Dispute Notice	Select yes to notify the customer of disputes made to their account.
Dispute Template	Select the delivered template.
Send Payment Notice	Select yes to notify the customer of payments made to their account.
Payment Template	Select the delivered template.
Send Promise Notice	Select yes to notify the customer of promises to pay on their account.
Promise Template	Select the delivered 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.