Oracle® Fusion
Applications
Financials Implementation Guide 11g Release 1 (11.1.2) Part Number E20375-02 |
![]() Contents |
![]() Previous |
![]() Next |
This chapter contains the following:
Setting Up Collection Preferences: Points to Consider
Defining Collection Preferences: Worked Example
FAQs for Manage 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 behaves, such as date ranges and defaults. Consider the following decisions before defining preferences:
Decision |
Is This 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 is Receivables being set up and what is 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 needs to be verified that Business Intelligence Publisher is working to run collection reports. |
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
Default aging method
Delimiter used to separate data and the number of characters required to do a search
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 exchange rate
Send method of dunning
Default contact for unknown dunning recipients
This example demonstrates how to set preferences for collections. You have been tasked to set up the two regions of preferences: Global and Preferences
Your company requires collectors to review transaction that are 90 days past due and current ones 30 days into the future. Collectors review customers by account and send out past due notices by E-Mail. Notices are sent to the accounts payable manager if no contact information is available. Reviewing a customer's history requires viewing current and closed transactions. Your company allows up to two days for rescheduling work on the dashboard. Adjustments and disputes are handled within 1 business day of being recorded. Credits on an account are summarized. Aging is displayed by a 5 bucket aging method. The conversion rate is based on a rate set by the corporation. The delimiter symbol used to separate data is a pipe. A three-character minimum is required and recommended to perform a search on customer accounts. Create the preferences based on this information.
Define preferences based on the following table:
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 select 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 |
In this example, 90 days gives the collector 3 months of history. 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 |
30 days of current or open transactions are displayed. 1-9999 is the range that can be used. |
Enter the maximum number of days work can be rescheduled on the dashboard |
Two days is the allowable change in schedule for work. 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 |
One day generates the disputes and adjustments. 1-9999 is the range that can be used. |
Select the default Aging Method |
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 |
The pipe symbol, other available choices are the greater than, dash, and 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. |
Field |
Value |
---|---|
Collections Preference Set |
Choose the value; Common Set |
Select the Collections Business Level |
Account, other choices are customer and site. |
Select whether open credits should be aged or summarized by default |
Summarized, credits can be displayed as aged. |
Select the exchange rate type for converting multi-currency transactions |
Corporate, several choices can be defined and are displayed. |
Select the default method to send collections notifications |
E-Mail, other methods are fax or print. |
Enter the default contact for unknown dunning recipients |
Accounts Payable Manager. User defined if no contact is listed. |
Global preferences affect the Collections Customer Work Area, such as display of closed or open transactions and setting date range parameters.
Preferences can be set uniquely for a specific business unit. Preferences impact the default settings, such as preference set and default method to send notifications.
Transactions set at the customer level to view or modify, encompasses all of the transaction activity associated with the customer. For example, a dunning letter at the customer level is inclusive of transactions at the customer and account level.
Transactions set at the account level to view or modify, are for a particular account and include transactions for all the bill-to sites under that account.
Transactions set at the site level to view or modify, are specific to the bill-to location.
Minimum dunning amount is the total amount set for all overdue transactions to have correspondence generated. For example, if your minimum dunning amount is set to $100 and you have three overdue transactions of $25, $35, and $55 totaling $105, a dunning letter is generated listing the three invoices as overdue.
Minimum dunning invoice amount is the amount set for an overdue transaction to generate correspondence. For example, if your minimum dunning invoice amount is set to $25 and you have three overdue transactions of $15, $50, and $75, a dunning letter is generated for the $50 and $75 transactions.