NewLoadYTDClosingBalanceInput not working as expected with prior period movements
Summary:
For a customer we are encountering issues with balance sheet accounts in combination with the NewLoadYTDClosingBalanceInput substitution variable (YTD Reversal - Closing Balance Input in consolidation settings).
When there is an entry on a movement (other than the default movement), FCC reverses that movement (as expected), but is not taking into account that reversal when calculating the default movement. This results in a closingbalance other than zero, while it should be zero.
- We are loading data using data exchange (replace/replace, closingbalance_Input as only movement member)
- All balance sheet accounts contain default movements
- I have enabled/disabled the setting NewLoadYTDClosingBalanceInput to see whether it makes a difference
Tagged:
0