ARCS Transaction Matching - Effective Date Filter Dependency Across Entities

We use ARCS Transaction Matching across multiple APAC and EMEA entities and control matching periods through Effective Date Filters.

Our challenge is that a few entities occasionally delay closing their reconciliations. Since Effective Date Filters cannot be updated until all related reconciliations are closed, those delays prevent us from starting Transaction Matching for the next period for entities that are already closed.

We are looking for a way to make entities operate more independently, so that once an entity's reconciliation is closed, we can begin Transaction Matching for the next period without waiting for all other entities.

Has anyone faced a similar issue? Are there recommended approaches or best practices (e.g., match type design, profile setup, or other configurations) that reduce these inter-entity dependencies while still controlling matching periods effectively?