Enforce valid intersection while selecting members in consolidation journals

Summary:

We have enabled valid intersections on "account / movement" combinations. This works fine in forms.

We are now getting questions from the customer if it is somehow possible to only see the "valid" movements when you have already selected a specific account when working with consolidation journals.

This isn't the case and makes the creation of "consolidation journals" a bit "hit or miss", because you cannot easily check if a movement is valid when selecting it. (users can try 10 different movements, while still failing the scan, just because you cannot filter the valid movements)

So my question: is it in some way possible to only see valid options when picking members in a consolidation journal? (standard license, so no groovy)