08.08 Planning with Multiple Segments or Full GL Accounts

When to use this approach

Use this when you need:

• Plan data recorded against individual GL account codes (not aggregated hierarchy nodes)

• Plan data combining more than one cost centre — for example Division, or Division & Department

• A bottom-up budget where each account is planned independently

This approach produces the most granular plan and gives maximum reporting flexibility, at the cost of greater data-entry effort and more complex template management.

Step 1 - Setup the data-entry report

1. In Designer, open or create a report based on the GL Balances template such as

   GL 06 Planning / Replanning This Year — for planning the current financial year

   GL 06 Planning for Next Year — for planning the year ahead

2. Select your planning scenario in the "Planning Scenario" filter.

3. In the Rows / Columns dialog (Layout tab), set up the down axis to include each dimension you want to plan against in the down axis. Examples in Epicor:

   • Division + Account: Add Segment2 and Account

   • Division + Department + Account: Add Segment2, Segment3, and Account

   • Division + Project + Account: Add Segment1, a project dynamic segment, and Account

   or alternatively use the GL Account dimension which is a prebuilt Epicor dimension combining Segment1, Segment2 and Segment3.

4. Run the report. Confirm Segment code combinations appear in rows, periods across the top, and that actuals are populating where expected.

   

5. Verify submission cells are yellow (see 08.05 if they are not).

6. Save the report with a clear name — for example: Budget FY2026 — Detailed Input.

Step 2 - Entering data in Excel

1. Open the saved report in the Excel Add-In.

2. Type budget figures directly into the editable cells. You can use Excel formulas — for example =B5/12 to spread an annual total equally across twelve periods. Formulas are preserved when the report is re-run, as long as the same row is still present in the results.

3. Use the Preview button in the FastClose ribbon to review unsaved changes before submitting.

4. Click Submit.

Using a hierarchy alongside account-level detail

You can still apply a hierarchy to the report for display purposes — grouping accounts under P&L sections — while submitting at individual account level. This gives contributors context (which section of the P&L they're working in) while ensuring granular data is stored.

To do this: in the hierarchy, ensure the Submit checkbox is not ticked on any aggregated node. All submission will then happen at the individual account level, and the hierarchy is used for grouping and subtotalling only.

Accounts with no actuals

When planning at account level, you will almost certainly encounter accounts that have never had a transaction — so no row appears for them in the report. Module 08.11 covers how to add these missing rows.

Multiple scenarios on one template

If your process requires contributors to submit to more than one scenario simultaneously — for example a Base Case and a Stretch scenario — add both to the Scenario filter on the across axis. Submission cells will appear for each scenario in separate columns.

What you've learned

You can configure planning templates for complex multi-segment planning. The submission and reporting mechanics are identical to the other approaches — just with more dimensions in play.