Bug 39645 - Prevent duplicate overdue fines if an item is renewed and new due date is overdue
Summary: Prevent duplicate overdue fines if an item is renewed and new due date is ove...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Fines and fees (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-15 18:40 UTC by Alyssa
Modified: 2025-05-07 19:42 UTC (History)
1 user (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alyssa 2025-04-15 18:40:51 UTC
If an item is overdue when it is renewed, and the new due date is also overdue, Koha should take into account the period of time in which overdue fines were already charged and not assess duplicate fines. 

This happens in libraries that charge overdue fines, renews items based on original check out date, and allows auto renewing on overdue items.
Comment 1 mteal 2025-04-15 19:32:17 UTC
We had this happen for an item that took a long time to renew because the popularity of the book finally faded enough to no longer have holds. By the time the item renewed, it was already overdue for the next loan period. It doesn't look good to fine a patron twice for the same overdue days.
Comment 2 Katrin Fischer 2025-05-07 19:18:08 UTC
Could you add a step by step with your configuraiton on how to reproduce this?
Comment 3 mteal 2025-05-07 19:22:02 UTC
Item X auto-renewed to be due 1/28/25 once okay. For some reason (probably a hold or something), the auto-renewal was not successful the second time by 1/28/25. At that point, it was overdue, fines began to accrue. Eventually, on 2/25/25, the auto-renewal was successful and assessed the $5.20 for overdue days of 1/18-2/25. Then the new due date was calculated from the previous checkout (as per our syspref) and it set the new due date as 2/15/25, which meant the item was already 8 days overdue. So the overdue charges began again, this time from 2/15/25, the new due date. When the item was eventually marked LOST on 3/18, another fine was assessed for 2/15-2/25 + 2/26 - 3/18 = $5.00. So the time period of 2/15 - 2/25, was accounted for in both the first $5.20 fine and the second 3/18 $5.00 fine.
Comment 4 Katrin Fischer 2025-05-07 19:29:45 UTC
This is really hard to follow without knowing how your fines are set to charge (begin of interval, end of interval, interval, fine amount, holidays etc.)
Comment 5 mteal 2025-05-07 19:42:45 UTC
Our fines are $0.20/day. This item checked out for 3 weeks. There were no holidays during the overdue time. Fines begin to accumulate the day after the item is overdue. OverduesBlockRenewing - don't block. Our circ rules are set to autorenew 3 days prior to the due date. New due date is from the previous checkout date. I believe the problem came in either with the renewal occurring after the due date or when the item went to LOST status and was later returned after then second renewal. Are there any  other syspref settings that would help?