2011 Jun 23 6:09 PM
In order to use the new Collections Management functionality, the master data grouping level needs to be configured where it could be at either the contract account level or the contract level.
I wanted to know if anyone has set the grouping to be at the Contract level; if yes, what was the rationale for doing so?
Also, what impact does that have on the collection steps that need to be executed? For a dunning notice as a step for example, considering a Contract Account with 2 contracts, would that mean that 2 notices will issued, one for each contract?
Kind Regards,
Nikhil
2011 Jun 24 8:25 AM
Hi Nikhil,
There can be scenarios, where the dunning treatment path varies based on the type of the contract like Active or Finalised.
So if a customer has two contracts-one active and other finalised and both of them have different treatment path as per the business process, then dunning grouping at the contract level is required.
So, in this case, the customer will receive two different dunning notices for the two types of contracts.
So, in the BRF configuration steps, there will be different treatment path for these type of contracts, based on move out date, final invoice main transaction etc.
Hope it clarifies your doubt.
Thanks,
Amlan
2011 Jun 24 8:25 AM
Hi Nikhil,
There can be scenarios, where the dunning treatment path varies based on the type of the contract like Active or Finalised.
So if a customer has two contracts-one active and other finalised and both of them have different treatment path as per the business process, then dunning grouping at the contract level is required.
So, in this case, the customer will receive two different dunning notices for the two types of contracts.
So, in the BRF configuration steps, there will be different treatment path for these type of contracts, based on move out date, final invoice main transaction etc.
Hope it clarifies your doubt.
Thanks,
Amlan