08.13 Reviewing and Auditing Submitted Data
Once a planning cycle is underway, it is easy to lose track of what has been submitted and at what level. Common problems include:
submissions at hierarchy node level alongside submissions at individual account level for the same accounts (causing double-counting)
submissions referencing old hierarchy nodes that no longer exist
test figures not deleted
FastClose provides a straightforward audit approach for both leaf-level and node-level submissions.
Here is a video, or read below.
Auditing submissions
Open the solution: Planning Submission Data Audit & Troubleshooter
Set the Planning Scenario variable to select your planning scenario.
Run the report.
Every figure submitted against individual account codes is shown for that scenario — this is the definitive view of what will be aggregated when a hierarchy is applied in any reporting template.
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 submissions to be removed have been identified, 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.
Move on to Appendix - A - Planning Process Owner Checklist or back to 0800 Planning Contents
