Voiding Bill Removes from Patron's History

[Robert J Jackson]

Evergreen 2.7.2
OpenSRF 2.3
PostgreSQL 9.1.14
Ubuntu 12.04.5

Patron from library A checked out item belonging to library B. Item was returned to library A and transited back to B. B indicates item was damaged and placed billing on patron's account. Library A says that patron would not knowingly return a damaged item without notifying and that staff would also report damages if they existed. So library A voided billing. As a result the billing does not show on the billing history for the patron.

Setting the voided voider void_time in money.billing and the xact_finish in action.circulation was required to reinstate bills:

update money.billing set voided = 'f', voider = null, void_time = null where id in (36444985,36444986);

update action.circulation set xact_finish = null where id = 48221486;

[Jason Boyer (jboyer)]

Judging from the API called in bill_history.js I guess this is intentional, but I can't understand why you would avoid showing transactions where all billings were voided with no payments. Those tend to be the most "interesting" ones (so to speak).

[Terran McCanna (tmccanna)]

I agree with Jason on this. I can understand if a bill was legitimately added accidentally that hiding it from view after voiding it reduces clutter, but we end up having to rely on reports and logs to help library managers track down information about bills that shouldn't have been voided. We'd save a significant amount of time if that information was readily available on that screen.

[Diane Disbro (ddisbro)]

This is still an issue in 3.6.3. When voiding a bill in Full Details, the NO in the Voided? column changes to YES. But after you refresh or navigate away from the page then return to it, all information about the bill has disappeared.