1. Oracle Advanced Collections
OVERVIEW AND IMPLEMENTATION
Tips and Tricks Session
Session ID: TIP1153
Mandar P. Kulkarni

2. Oracle EBS R12 Advanced Collections
Benefits
Get More-Accurate View of Customer Information
Increase Collections Effectiveness
Streamline the Collections Process by Managing Claims and Disputes more Efficiently
11/14/2018
© Mandar P. Kulkarni

3. Setup Checklist – Collections Administrator
11/14/2018
© Mandar P. Kulkarni

4. Questionnaire 1 of 3
11/14/2018
© Mandar P. Kulkarni

5. Questionnaire 2 of 3
11/14/2018
© Mandar P. Kulkarni

6. Questionnaire 3 of 3
11/14/2018
© Mandar P. Kulkarni

7. Mandatory Tasks
11/14/2018
© Mandar P. Kulkarni

8. Mandatory Tasks cont.
11/14/2018
© Mandar P. Kulkarni

9. Mandatory Tasks cont.
11/14/2018
© Mandar P. Kulkarni

10. Mandatory Tasks cont.
11/14/2018
© Mandar P. Kulkarni

11. Day in Life
Universal Work Queue UWQ ‘Nerve center’ of Advanced Collections
All Advanced Collections processes and activities are in support of UWQ
UWQ Columns can be arranged by drag-and-drop
How does the UWQ get refreshed?
Delinquency Queue:
Record scored via Scoring Engine Harness (Concurrent Request)
Record added via UWQ populate (Concurrent Request)
Record removed when Delinquency settled and UWQ populate run
Broken Promises:
Record added when Promise Reconciliation run (Concurrent Request)
Tasks:
Record added when Task entered, date arrives, UWQ toolbar refresh
Record removed when Task closed and UWQ toolbar refresh
11/14/2018
© Mandar P. Kulkarni

12. Collections Workbench
Leverage real-time transactional and customer data
Execute proven collections best practices
Treat different customers differently
Automatically identify delinquent/pre-delinquent customers
Streamline collections process
Navigate more easily through collections screens
Automate correspondence notification
Track payments, promises, incomplete work, interactions automatically streamlining interactions between various team members
11/14/2018
© Mandar P. Kulkarni

13. Dispute Process Dispute can be raised by: Advanced Collections
Only AR Collector will be able to enter dispute
Triggers Credit Memo Request workflow
iReceivables
AR Collector enter dispute
AR Transaction form
Does not trigger workflow
11/14/2018
© Mandar P. Kulkarni

14. Demo
Demo of AR Collections and Credit Memo Approval Process

15. Dispute – Issues and Setup
Error ‘A Receivable Role has not been defined or is invalid Receivable Role Name: Please define a Receivable Role.’ Unable To Locate Valid Receivable Role For Credit Memo Request (Doc ID )
Create Responsibility ‘Receivables Role’ Responsibility Key = ‘ROLE’
Open AR Credit Memo Approval Workflow and select File > Load Roles From Database. Select Receivable Role from the list and click on Add and then click on OK.
Update attribute Receivable Role (internal name: RECEIVABLE_ROLE) with value = ‘Receivables Role’ from above
Update attribute Batch Source Name with a valid credit memo batch name
11/14/2018
© Mandar P. Kulkarni

16. Dispute – Issues and Setup cont.
Define Resource - CRM Responsibility > Maintain Resources > Resources and assign Role = Collections Agent
Define Collectors - AR Responsibility > Setup > Collections > Collectors
Define Transaction Approval Limits - AR Responsibility > Setup > Transactions > Approval Limits
11/14/2018
© Mandar P. Kulkarni

17. Dispute – Issues and Setup cont.
Update CM Memo Type for each Invoice Transaction Type - AR Responsibility > Setup > Transactions > Transaction Types
Define Credit Memo Batch Source - AR Responsibility > Setup > Transaction > Sources
11/14/2018
© Mandar P. Kulkarni

18. Dispute – Issues and Setup cont.
Define Transaction Approval Limits AR Responsibility > Setup > Transactions > Approval Limits
11/14/2018
© Mandar P. Kulkarni

19. Thank you!
11/14/2018
© Mandar P. Kulkarni

20. Reference
Migrating to Oracle Advanced Collections: An Overview for Oracle Receivables Users – An Oracle White Paper Winter 2007
Oracle Advanced Collections R12 Implementation Guide
Oracle Advanced Collections R12 User Guide
11/14/2018
© Mandar P. Kulkarni