One of your ideas has been delivered from your suggestion.Collection Strategy Updates for Individual Transactions Using a Rest API

Manage collections strategies for individual transactions using the Collections Strategies REST API. Update strategy status and task status based on triggers from third-party applications. This also helps migrate in-progress strategy assignments and their tasks from another application to Advanced Collections. This feature provides more flexibility in managing collections strategies through extensions.

Use the enhanced Collections Strategies REST API to:

  • Perform operations such as Cancel, Complete, and Skip using the PATCH operation of the strategyExecutionTasks and strategyUserTasks REST APIs.
  • Add new user tasks using the POST operation of the strategyUserTasks REST API
  • Add new strategy tasks using the POST operation of the collectionStrategies REST API
  • Skip a task that is in the To Be Created status using the PATCH operation of the strategyTemplateTasks REST API.

By leveraging REST operations such as PATCH and POST, organizations can dynamically manage user and strategy tasks—cancelling, completing, skipping, or creating them as needed—without manual intervention. This not only accelerates collections cycles and reduces overhead but also enables deeper customization through extensions, ensuring that collections processes align with unique business rules and external system integrations.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

The following features are to be enabled in the Feature Opt-In:

  • Automatically Initiate or Fulfill Collections Tasks in Third Party Systems
  • Collections Strategies for Individual Transactions
  • Collections Scoring and Strategy Assignments by Segments

Tips And Considerations

  1. While migrating strategy assignments that are in progress and their strategy tasks to Fusion Advanced Collections:
  • All the tasks of all the installments have to be migrated at a single go using the POST operation of the collectionStrategies
    • https://<host>:port>/fscmRestApi/resources/11.13.18.05/collectionStrategies/
  • If an installment ID (payment schedule ID) is not provided or missed in the POST Operation, the tasks are assigned as per the strategy template in the To Be Created status.
  1. While assigning a collections strategy using the POST operation of the collectionStrategies REST API:
  • Account-Level Strategy: If a payment schedule ID is provided, it will be ignored, and the strategy will be applied directly at the account level.
  • Transactional-Level Strategy: If a payment schedule ID is not provided, the tasks are assigned as per the strategy template in the To Be Created status.

Key Resources

  • Based on Idea 784339 from the Receivables and Collections Idea Lab on Oracle Cloud Customer Connect.