http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8770 --- Comment #6 from Melia Meggs <melia@bywatersolutions.com> --- I can't check that particular one because I can't make their silly VPN work, but I have another example from a different library of the same thing. This one is also related to a lost item that was later returned (I think?). The one with the wrong amountoutstanding is accounttype F. It looks like this: mysql> SELECT * FROM accountlines WHERE borrowernumber = 323737\G; *************************** 1. row *************************** borrowernumber: 323737 accountno: 2 itemnumber: 700451 date: 2012-08-22 amount: 3.950000 description: Froggy goes to Hawaii / 05/22/2012 23:59 dispute: NULL accounttype: F amountoutstanding: 2.950000 lastincrement: 0.050000 timestamp: 2012-08-22 16:42:19 notify_id: 0 notify_level: 0 note: NULL manager_id: NULL *************************** 2. row *************************** borrowernumber: 323737 accountno: 3 itemnumber: 700451 date: 2012-07-30 amount: 15.990000 description: Lost Item Froggy goes to Hawaii / 31319001350302 dispute: NULL accounttype: LR amountoutstanding: 0.000000 lastincrement: NULL timestamp: 2012-08-22 16:42:19 notify_id: 0 notify_level: 0 note: NULL manager_id: NULL *************************** 3. row *************************** borrowernumber: 323737 accountno: 4 itemnumber: NULL date: 2012-08-22 amount: -15.990000 description: Item Returned 31319001350302 dispute: NULL accounttype: CR amountoutstanding: 0.000000 lastincrement: NULL timestamp: 2012-08-22 16:42:19 notify_id: 0 notify_level: 0 note: NULL manager_id: NULL 3 rows in set (0.00 sec) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.