In your scenario, you can employ an event-driven architecture and avoid storing data locally. In order to suspend overdue accounts, you can have the Invoicing BC publish an event indicating that an invoice is past due. The Collections and Subscriptions BC would subscribe to that event and invoke the required behaviors. From the perspective of the Invoicing BC, you'd have a domain event called something like InvoiceBecamePastDue and it would be published externally via message bus.
In this case, it doesn't seem like you need a local copy. There are instances however where a local copy of data is required in which case you would maintain the local copy using published events.