Currently Envers relies on a predefined, hard-coded set of so-called PropertyMappers. They're responsible of various aspects of handling audited entity properties:

• mapping values from map to actual object
• mapping values from object to map,
• checking collection changes
• checking modified flags
  Unfortunately it seems like there's no way to customize the behavior of these classes from outside of envers code-base.
  It would be great to have a custom strategy that allows (say PropertyMapperResolver or CollectionMapperResolver) people to inject their own behavior for mappers - I needed it when working on eager collection retrievals.