Receivables & Collections

Get Involved. Join the Conversation.


    Sara Munaretto
    Custom Data Point for Collections Scoring
    Topic posted October 28, 2019 by Sara MunarettoBlue Ribbon: 750+ Points, tagged Collections, Configuration, Financials, Help Center, Receivables, Setup / Administration 
    14 Views, 1 Comment
    Custom Data Point for Collections Scoring
    It should be possible to define Custom Data points for Collections Scoring in Advanced Collections

    We are implementing collections at a client that has continuous business with its customers. This means that within the duration of one strategy, invoices become overdue. For example, the strategy starts with 2 overdue invoices, which are included in a soft dunning letter. These two invoices get paid, but another invoice becomes overdue before the strategy is closed.

    The way strategies are set up now, the initial strategy will continue and hence a moderate dunning letter is sent with that one invoice. This is not ideal from a customer communication perspective. The strategy should change to either the same strategy (automatically start again) or to a softer one for example, but not continue.

    A way to achieve this is to use Collections Scoring, however the available data points are not sufficient. There is a need for smaller aging buckets (1-7, 8-14. etc.) and a data point looking at how many days overdue is the oldest transaction. This way if a customer has one transaction 14 days overdue and one 1 day overdue, the original strategy (moderate strategy) continuous. However, if the first transaction is paid (14 days overdue), a softer strategy is applied to the customer. 

    Oracle Fusion Advanced Collections 19C



    • Ben Verheij

      We actually have the same requirement. With the current data points it can happen that a final demand dunning letter is send to a customer for transactions which are only overdue for 2 days. It would be great if there is a data point which assesses the days late of the oldest transaction, so a strategy could re-start based on the oldest transaction outstanding. If I remember correctly, a similar data point is available in EBS.