08.10 Planning using a P&L Structure
What we have done in the previous modules, using account nominal planning gives contributors a list of account codes to fill in. That works well for finance teams, however, many other budget holders tend to think more in management reporting terms — Revenue, Salaries, Travel etc... not account numbers. Planning using a P&L hierarchy gives contributors a familiar view while FastClose maps their entries to the underlying accounts.
This module assumes a FastClose account hierarchy describing the P&L has already been built. If not, the P&L / Income Statement Quick Start guide covers hierarchy construction and is a prerequisite for this module.
Here is a video, or read below.
How it works
A FastClose hierarchy defines how account nominals are grouped into named nodes. Those node names become the rows of the planning template. When a planner submits a number against a node like Travel & Entertaining, FastClose stores it at that node level. When you report, the node figure is used directly. Individual account codes do not appear — contributors work entirely in business language.
Step 1 — Build the input template
Open GL 06 Planning / Replanning This Year.
In Rows / Columns, set the down axis to Account only (exactly as we did in 08.05 — no cost centre dimensions).
Go to Insert → Hierarchies and bring in your P&L hierarchy. The account codes in the down axis will be replaced by the hierarchy’s node names.
Confirm it covers the P&L lines to be planned against, with the correct account ranges at the leaf level. Any node used as a submission point must have the underlying accounts mapped correctly, even though contributors wont be using them.
Select the planning scenario in the Planning Scenario filter.
Step 2 — Set the Submit checkbox on hierarchy nodes
This is the key decision in hierarchy planning. Each node in the P&L can work in one of two ways:
Submit checked: the node itself appears as an editable cell in the planning report. Its child nodes and underlying accounts are not submittable. Planners enter a total at this level.
Submit not checked: the node rolls up from whatever is submitted beneath it, exactly as previously. It appears as a calculated subtotal, not an editable cell.
To set this: double-click a node in the hierarchy editor to open it, then tick or untick the Submit checkbox. You can mix this across nodes — some can be submission nodes while others roll up from account nominals.
Step 3 — Save and test
Run the report in Designer
Nodes with Submit checked will appear with a yellow background whilst their children will have a white background indicating unsubmitable.
Right-click on a yellow cell and choose Submit Planning Value. Type a test number and click OK.
Re-run the report. Confirm the submitted value now appears in the results.
If cells you expect to be yellow are not, right-click and choose Why Can’t I Submit? FastClose will explain the reason. Common causes: the scenario is not in the column, the period is outside the allowed range, or a mandatory filter has not been set.
Step 4 — Save the report
Save the report with a name that makes its purpose clear to anyone who opens it — for example Budget FY2026 — Contributor Input. A well-named template prevents contributors from opening the wrong version.
Step 5 - Entering data in Excel
Follow the same process as described in 08.07
Now try the downloadable exercises below:
LINK HERE
Your feedback helps us do better, to fill in a short survey on this tutorial, click here.
Move on to the second variation 0811 - Planning on Account Nominal by Cost Center or skip to 0812 - Balance Sheet Planning (Advanced) or 0813 - Reviewing and Auditing Submitted Data
