Well, the audit entity's id is composed of the revision number + primary key for the audited entity. So if the entity contains the company id in its primary key, it should work.
Thanks for answering my question but the way we would like it to function is the following:
The revision number should increase per company like that:
companyId revision number
That way we could easily copy company data (also the company audit data itself) from one server to another without having conflicting keys.
Maybe this would be possible with a custom revision entity and a custom id generation strategy?