Bug 22916 - Processing Fee charged multiple times
Summary: Processing Fee charged multiple times
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Fines and fees (show other bugs)
Version: 18.11
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-15 21:16 UTC by Andrew Fuerste-Henry
Modified: 2019-05-15 21:16 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Fuerste-Henry 2019-05-15 21:16:10 UTC
This takes some really specific setup and processing to duplicate. To do so:

- Set up an item type with a processing fee but no default replacement cost
- create an item with no replacement cost in the 952$v
- Check that item out with a due date several days in the past
- run longoverdue.pl --lost 1=1 --confirm
- run longoverdue.pl --lost 2=2 --confirm --charge 2
- note the item is at lost status 2, patron has been charged the processing fee but no lost fee
- run longoverdue.pl --lost 1=1 --confirm (again)
- note the item changes back to lost status 1
- run longoverdue.pl --lost 2=2 --confirm --charge 2 (again)
- note the item changes back to lost status 2 and the processing fee is charged a second time


This does not occur if the item has a replacement cost and a Lost fee is created on the account. In that case, the processing fee is only charged once.

This can be avoided by using the --maxdays option in the longoverdue cron.