Bug 24763 - Backdating check-ins creating fine issues that can't be resolved
Summary: Backdating check-ins creating fine issues that can't be resolved
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Fines and fees (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-28 17:43 UTC by Christopher Brannon
Modified: 2020-05-11 18:35 UTC (History)
1 user (show)

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 Christopher Brannon 2020-02-28 17:43:29 UTC
From ByWater:
When libraries accept payment on accruing fines and then backdate the checkin of the item, the final amount due can end up less than the amount paid. (There are other ways for this to happen, but backdated checkin is the most common.) It's not a fine that can be paid off (because it's negative), but it's not truly a credit either so it cannot be reconciled or voided.

We would like to see this addressed so we can continue to backdate our overnight bookdrop items without these issues, and without having to constantly ask our support vendor to remove them for us.
Comment 1 Andrew Fuerste-Henry 2020-02-28 19:54:59 UTC
This should be resolved as of bug 21747. The excess payment amount is moved into a credit. Do you have examples generated after you moved to 19.05?
Comment 2 Christopher Brannon 2020-02-28 23:21:06 UTC
(In reply to Andrew Fuerste-Henry from comment #1)
> This should be resolved as of bug 21747. The excess payment amount is moved
> into a credit. Do you have examples generated after you moved to 19.05?

Check our support tickets.  They have all been handled through Bywater because we couldn't do anything with them.  I would think if it were fixed, our backdating wouldn't be touching it at this point.
Comment 3 Katrin Fischer 2020-05-05 22:39:52 UTC
I wonder if this is related to bug 22539?