08.12 Reviewing and Auditing All Submitted Planning Data
Why you need this
Once a planning cycle is underway, it is easy to lose track of what has been submitted and at what level. Common problems:
Some contributors submitted at hierarchy node level; others submitted at individual account level for the same accounts — resulting in double-counting when you roll up
Historical submissions remain from an earlier version of the hierarchy, against node names that no longer exist
A contributor submitted a test figure and didn't delete it
FastClose provides a straightforward audit approach for both leaf-level and node-level submissions.
Auditing submissions
Open the solution: Planning Submission Data Audit & Troubleshooter
Set the Planning Scenario variable to select your planning scenario.
Run the report.
You will see every figure submitted against individual account codes. This is the definitive view of what will be aggregated when a hierarchy is applied in reporting.
The _Dummy item at the bottom can be ignored. Its a special node used to ensure that all account nominals and all higher level P&L nodes get displayed regardless of your current P&L and Balance Sheet structures.
Cleaning up
Once you've identified submissions you want to remove, clear them in one of two ways:
One at a time in Designer: Right-click the cell, select Submit Planning Value, do not enter anything, just click OK.
In bulk via Excel (recommended for large volumes): Open the report in the Excel Add-In, clear unwanted cells, then click Submit. This is far faster than clearing values one by one in Designer
End-of-cycle discipline: Run an audit like this both at the midpoint of the planning cycle (to catch problems early) and at the end (before producing board-level reports). A clean data set at this stage means everything in Modules 08.11 and 08.12 will work as expected.
What you've learned
You can produce a complete audit of all submitted planning data — at both account and node level — and efficiently clean up inconsistencies before reporting.
