Consolidation templates

How to create, customize and manage consolidation templates and instances.

Introduction

Consolidation templates are used to create financial plans for different business areas such as departments, entities, and locations.

You can convert any tab into a consolidation template through the Split action. To create a template, navigate to a tab and select Split from the action menu to configure your desired grouping.

When creating a consolidation template, three things happen:

  1. The tab you performed the split on, is converted into a consolidation template.

  2. A number of instances are created in the model overview based on your split configuration.

  3. Consolidation templates automatically consolidate values from associated instances.

Instances are copies of the consolidation template. Instances are linked to the consolidation template and receive any structural updates made to the consolidation template.

Before applying a split, note that specific actions may lead to the deletion of forecasts:

  • When you split a tab, all pre-existing forecasts and manual entries are deleted, as they are now defined bottom-up in the instances.

  • If a new split leads to the deletion of an instance, all forecasts and manual entries in that instance will be deleted.

Managing consolidation templates

Structural elements (top-down)

Consolidation templates define the structure for instances. This includes adding, renaming, rearranging, or removing components. Formulas in calculated rows are considered structural elements and are also defined top-down in the consolidation template. Changes to the consolidation template sync across all instances.

Instances inherit the structure of the template and can't be changed bottom-up.

Actuals and forecasts (bottom-up)

Actuals and forecasts are defined in the instances and are automatically consolidated in the template. This allows you to create and analyze separate forecasts for different parts of your business.

Actuals and forecasts are defined in the instances and cannot be defined top-down.

Last updated