UD or attribute to flag past restatements (Budget pot swaps)
Hello, we are about to start our work on next year budget and we already know that, following a recent restructuration, there will be a lot of pot swaps between departments (e.g. Licence costs used to sit in the department using the software but will now all sit under IT).
Some of the them will be just moving a cost center and its history from one department to the next so that will be easy.
Our issue is when we do a "pot swap" that moves part of a cost center. In this case we will have a disconnect when we compare actual and forecast unless we restate actual (i.e. also move the cost in actual).
My question is on how best to tag/flag the "pot swap" in the actual data so that in reporting we can do like of like comparison (i.e. with past data restated) but also keep the original data.
I have 2 potentials solutions:
- Flag the restatement using an UD: do the restatement of past periods under a specific UD so that we have the ability to see past periods with or without pot swap adjustments
- Use attributes: I think attributes would work but we have not used attributes in the past so not sure whether it is the best way
Does anyone have the same issue and came up with an alternative solution? or has a view on the above options?
Many thanks!
