Talk:Dunning Setup
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
Some notes on the code:
- The determination of previous dunning levels uses a query that picks the previous levels based on DaysAfterDue+DaysBetweenDunning being less than the same calculation for the current level. Not sure why the DaysBetweenDunning is considered. Seems to be an odd constraint.
- The query to determine sequential dunning does not consider if a higher dunning level has been triggered, so the lower levels repeat.
- Definitions of Days Between Dunning are confused when looking at different dunning levels. I think the Days Between Dunning should only apply to repeat notifications of a single level.
- Payments repeat on multiple dunning levels if one of the levels has invoices. They should only repeat on dunning levels that have invoices.
I'd like to propose the following changes:
- Dunning levels progress in order of the Days After Due date - one level is active until the next is triggered by the invoice passing the due date limit.
- The days between dunning only apply to repeats of the same level
Example 1: Level 1: DaysAfterDue = 30, DaysBetweenDunning = 10 Level 2: DaysAfterDue = 60, DaysBetweenDunning = 10
Dunning performed daily. Results:
- From DaysDue = 0 to 30 - no impact;
- Level 1 notice sent on day 30, 40 and 50
- Level 2 notice sent on day 60, 70, 80 ....
Example 2: Level 1: DaysAfterDue = 0, DaysBetweenDunning = 999,999 Level 2: DaysAfterDue = 7, DaysBetweenDunning = 999,999 Level 3: DaysAfterDue = 30, DaysBetweenDunning = 15 Level 4: DaysAfterDue = 90, DaysBetweenDunning = 30
Dunning performed daily. Results:
- Level 1 notice triggered on day 0. No repeats
- Level 2 notice triggered on day 7. No repeats
- Level 3 notice triggered on day 30. Repeats on day 45, 60 and 75
- Level 4 notice triggered on day 90. Repeats every 30 days thereafter - or until the invoice is written off.