This takes some really specific setup and processing to duplicate. To do so: - Set up an item type with a processing fee but no default replacement cost - create an item with no replacement cost in the 952$v - Check that item out with a due date several days in the past - run longoverdue.pl --lost 1=1 --confirm - run longoverdue.pl --lost 2=2 --confirm --charge 2 - note the item is at lost status 2, patron has been charged the processing fee but no lost fee - run longoverdue.pl --lost 1=1 --confirm (again) - note the item changes back to lost status 1 - run longoverdue.pl --lost 2=2 --confirm --charge 2 (again) - note the item changes back to lost status 2 and the processing fee is charged a second time This does not occur if the item has a replacement cost and a Lost fee is created on the account. In that case, the processing fee is only charged once. This can be avoided by using the --maxdays option in the longoverdue cron.