This is most likely due to the fact there are some slight differences between the usage of @OrderBy and @OrderColumn / @IndexedColumn in the boot/run-time models that Envers isn't expecting. Thanks for pointing this out Christian Plätzinger.