What's new in Customer Journeys?

Connect and learn more! ×
Advanced Collections - how come Disputed transactions still get scored following collection refresh — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Advanced Collections - how come Disputed transactions still get scored following collection refresh

Received Response
32
Views
3
Comments

Summary:

Why are Disputed transactions still scored following collection refresh activities. Surely any disputed transaction should be omitted from scoring and strategy assignment.

Content (please ensure you mask any confidential information):

We have set up scoring at Account Level for Account Age of Oldest Overdue Transaction.

We have a simple Scoring formula based on days and a Strategy Group with strategy methods and strategy tasks based on the score value.

If for a customer the oldest invoice transactions are put in dispute, when the collection refresh jobs run the strategy assigned is still considering the disputed transactions and creating a task. Surely if invoice transactions are in dispute, then the collections engine should exclude them from scoring until any disputed transaction is withdrawn by the collector?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!