Handling feature modules with duplicated state in NgRx

I got an NgRx question I would like your 2 cents on.

We are building a banking application, containing a feature team per feature module monorepo setup.
Each feature module contains its own sub store.

Problem: We are duplicating accounts info around the feature stores and it is hard to keep them in sync via actions because then new events are updating accounts in the different feature stores you need to hook it into the other feature modules to keep them in sync.

Proposed solution: What do you think about creating a shared eager-loaded accounts NgRx entity map, containing the aggregated model for all the properties used by the feature teams working with accounts so we get a single source of truth in the store we can select on?