How to build an annual budget and rolling forecast in SAP Analytics Cloud

The annual budget and the rolling forecast are not the same exercise, and treating them as one is the most common planning design error in SAP Analytics Cloud. The budget is a fixed commitment — approved once, locked, and used as the reference point for the year. The rolling forecast is a regularly updated view of where the business now expects to land, blending year-to-date actuals with a re-planned remainder. Both live in the same SAC model, on the same dimensions, but in different versions — and getting that structure right from the start saves months of rework later.

Budget versus rolling forecast: the structural difference

A budget covers the full fiscal year, is built once (typically in Q4 for the following year), goes through an approval workflow, and is then locked. It answers the question: what did we commit to at the start of the year? A rolling forecast is updated regularly — monthly or quarterly — and always looks a fixed number of periods forward (12 months, 18 months, 6 quarters). It answers the question: where do we now expect to land, given what we know today? The rolling forecast replaces the stale budget as the operational planning tool while the budget remains the accountability baseline.

How to structure both in the same SAC model

The right approach is a single model with a well-designed Version dimension: one version for Actual (read-only, loaded from the ERP), one for Budget (locked after approval), and one or more for Forecast (editable, updated each cycle). This way, a single Story can show Actual vs Budget vs Forecast on the same chart without any data movement. The Version dimension is the backbone — see how to structure Actual, Budget and Forecast in SAC for the full explanation.

The budget build process in SAC

A typical annual budget build in SAC follows a top-down / bottom-up cycle. Finance sets targets at the entity level (top-down); department planners enter their line-item plans (bottom-up); Finance consolidates and reconciles. SAC supports this with private versions (each planner works in their own copy, invisible to others until published) and data locking (Finance locks approved sections to prevent drift). Driver-based planning — entering headcount and salary assumptions, letting SAC calculate the cost — is more reliable than entering every line directly and reduces the number of cells planners touch.

The rolling forecast update cycle

The rolling forecast update is simpler than the budget build: actuals for the closed periods load automatically from the ERP, and planners re-enter or adjust assumptions for the open periods. In SAC, a common pattern is to copy the previous forecast into a new version, update the assumptions that have changed, and publish. The comparison between the new forecast and the previous one (forecast vs forecast) is often as valuable as the comparison to the budget — it shows whether the outlook is improving or deteriorating.

Key KPIs for a budget and forecast model

The essential measures are: revenue and cost by category (SUM-aggregated flows), operating margin (a calculated measure — never store a ratio directly), budget vs actual variance (absolute and percentage), forecast accuracy (how close the previous forecast was to actual), and forecast vs budget (the gap between current expectation and original commitment). These five give a finance team the full picture of where they are, where they are going, and how reliable their planning process is.

Where to start

Our annual budget template and rolling forecast template come with the version structure, dimensions and KPIs already in place. Import, map your chart of accounts, and start planning. Not sure which fits your process? Let the assistant recommend one.