- Issue created by @loze
I had the exact same problem. I agree that the module itself should be able to do this, but since that's not the case I just built a custom module with a transactions table that implements hook_ENTITY_TYPE_update() for the userpoints entity type and updates the custom table accordingly by taking the difference of the original and the new entity. Maybe that approach would also work for you.