Planning Overview

Planning in Datarails is designed to offer a streamlined and systematic approach to financial management. By enabling seamless integration and management of Actuals, Forecast, and Budget, the platform ensures clarity, precision, and efficiency at every stage of the planning process. Below is an overview of the planning data hierarchy within your database:

Scenario: This column distinguishes between Actuals, Forecast, and Budget. Each scenario represents a unique stage in your financial planning and reporting.

Reporting Year: Indicates the year for which the scenario data applies, ensuring efficient management of data across multiple fiscal years.

Scenario Cycle: Defines the specific time frame and version of your financial plans. For Forecast, cycles include combinations like "1+11" (1 month of actuals and 11 months of forecast) or "0+12" (12 months of forecast). For Budget, scenario cycles align with organizational planning structures such as "Top-Down" or "V1".

Planning Scenario: Available in Forecast, this feature allows users to analyze different business assumptions (e.g., "Low", "Mid", "Best").

Scenario Details: Provides a detailed breakdown of each scenario and its related assumptions for clarity and traceability. For example, a value in the Scenario Details field could be "Budget V1" to represent a specific budget version, or "Forecast 4+8 Mid" to denote a forecast cycle with a mid-case planning scenario covering 8 months of forecast data.  

Planning Diagram 

The following diagram illustrates the data structure in Datarails, showing the relationships between Scenarios, Scenario Cycles, Planning Scenarios, Scenario Details, and Named Ranges:

Legend

Blue: Represents Actuals

Red: Represents Forecast

• "1+11" and "0+12" indicate forecast scenario cycles with varying actual-to-forecast months.
• "Best" and "Worst" represent different Planning Scenarios those values can be set by the users.

Green: Represents Budget

• "Top-Down" and "Bottom-Up" are examples of budget cycle types. Those values can be defined by the users.

This structure supports efficient scenario management, enabling users to navigate complex financial data with ease.

Best Practices for Planning

1. Start with One Scenario Cycle: Begin by creating one scenario cycle that you are satisfied with, then use the clone or roll-forward options to create new cycles. The clone option copies all your models and files, requiring only adjustments to assumptions to align with the new scenario.
2. Separate Files for Planning Scenarios: Use different files for different Planning Scenarios. The differences between these files should be in the assumptions while maintaining a consistent file structure. This recommendation applies exclusively to Forecast and is not intended for Budget scenarios. Begin by creating one Planning Scenario that meets your requirements. Once satisfied, use the clone option to create a new scenario. This allows you to retain the file structure while adjusting assumptions to reflect the new scenario. 
3. Ensure Successful File Mapping: Always ensure your files are mapped successfully into your database. Look for the green "Included in Database" badge to confirm that the mapping is complete and accurate.

Updated February 09, 2025 13:01