question about dunning. If a client uses a proce...
# general
m
question about dunning. If a client uses a procedure with 3 levels (30-45-90 days after due date). If I later add a rule which therefore becomes level 1, reminder on due date, will an invoice that has exceeded its due date but not yet at the level 30 days after due date, be assigned the level 1 ?
m
Is this a workflow?
m
Yes I have a workflow based on the customer and the execution one time by day (the dunning procedure is assigned at the customer level)
m
Is level 1 , level 2, level 3, etc all their own states in the workflow?
m
No I use the bundle Dunning
this bundle comes with several field and workflows Étc We must create reminder levels, procedures, if we assign at the level of invoices or at the level of customers
the workflow that we configure generate records called dunning evaluation
m
Wow sounds complicated...LOL Either way just evaluate what the conditions are of the transitions between the start state and Level 1 and the start state and Level 2
If a record has already "missed" the condition for Level 1, then just make sure it will be caught by the condition for Level 2. This way any record that has missed Level 1 will at least be caught when they are 30 days past due
s
If it's gone past the due date then it won't be assigned assuming that the dunning level is set as zero days past the due date. The only way to catch the cases you highlight would be to set the dunning level as between 0-29 days past the due date. That would sweep in anything currently in limbo and should trigger on the due date for new records. Then you can run the dunning procedure to get the new level assigned to existing records and then alter the dunning level back to just be 0 days since everything else would have been assigned a level by that point. Recommend a test in the SB first.