Comment 3 for bug 1686194

I would like to supplement this bug report with this:

The logic doesn't seem to take into account that the total fines could be less* than the max_fines value.

extreme scenario:

Item is overdue for 2 days (20 cents per day). The library has a Lost action trigger for 3 days. The item receives overdue fines for 2 days, and on the third day, it's marked lost. The library wants the overdue fines to be removed and the lost fine and lost processing fee to be applied. On day 6, the item is returned which, as per the library settings, should void the lost fee and processing fee. Then reinstate the overdues plus any overdues that would have generated had it never been marked lost. The logic seems to ignore the date on which it was returned, and generate the overdue fines equal max_fines.