Overdue fines not adjusted correctly on backdated lost items

[Jeanette Lundgren]

An item is checked out to a patron long enough for it to go into Lost status. Patron returns the item in such a way that requires staff to back date.

Here are two scenarios:

Item is in lost status. Item's last overdue fine was registered 9/2/17

Example 1: item is backdated to 9/5/17. Lost and processing is reversed as desired. Patron still owes all overdue fines. System working as intended.

Example 2: item is backdated to 8/31/17. Lost and processing is reversed as desired. Patron SHOULD owe fines up to 8/31/17. What happens is the system reverses all overdue fines, so the patron owes nothing on the item.

#2 issue reported two times over the past year. Confirmed behavior in 2.12 and 3.0.

[Steve Callender (stevecallender)]

Just came across this today in 3.0.

Had an item that was lost be checked in and only backdated 1 day, but because the lump of billings had a timestamp of today, they were all removed. (Had a lump payment applied to counter them).

I think that create billing needs to take into account the backdate when it's creating that lump bill.

[Jessica Woolford (jwoolford)]

This appears to still be happening in 3.5.3.