Simultaneous consolidation causing balance sheet mismatch

Summary:

Simultaneous consolidations caused balance sheet mismatch on base entity level.

Content (please ensure you mask any confidential information):

We have a client where they managed to run two simultaneous consolidations. This caused an issue with the default movement calculation and resulted in the balance sheet being out of balance (Closing balance did not equal Closing balance input on the data source).

As the entities had status "OK", a following consolidation did not solve the issue. We had to impact the entities and run the consolidation.

I suspect the Impact status of the first consolidation was only changed after the second calculation of the node was started.