We've found that following check-in message appears for all lost statuses regardless of if a patron has been billed or not. A good way to test this is to find a book that is not checked out and mark it missing. When you check it in, you'll get the following message: "Item was lost, now found. A refund has been applied to the borrowing patron's account." It seems like the second half of the message should only apply if a patron was actually refunded.
This is not a bug. Functionality works as it should. This message appears depending on how 'RefundLostItemFeeOnReturn' is set in your system.
(In reply to Jesse Maseto from comment #1) > This is not a bug. Functionality works as it should. This message appears > depending on how 'RefundLostItemFeeOnReturn' is set in your system. The message appears depending on the fact of whether there was a refund or not. It would be cool to carry the borrowernumer/name to display a link to the actual patron just in case the librarian wants to check.
(In reply to Tomás Cohen Arazi from comment #2) > (In reply to Jesse Maseto from comment #1) > > This is not a bug. Functionality works as it should. This message appears > > depending on how 'RefundLostItemFeeOnReturn' is set in your system. > > The message appears depending on the fact of whether there was a refund or > not. I don't find this to be the case. If I mark an item missing when it is not checked out, checking it in will not trigger any refund because a charge was never put on anyone's account. The message should not display every times something with a lost status is checked in.
Realistically the message shouldn't display unless a refund has actually taken place. Unfortunately this is not the case. This has annoyed many staff. If the refund took place before the message was displayed, it would be great if it actually looked at the patron's account and confirmed that a refund was actually given, and if so, THEN display the message.
*** Bug 19508 has been marked as a duplicate of this bug. ***
+1 on this, it's a source of confusion
This is still an issue, and with the changes to refund options, it is even more confusing.