Cube ☰
AI

Product

menu arrow

Core Platform

Platform Overview

Workflow-native FP&A, powered by AI

Cube Workspace

Your command center for financial intelligence

Data Engine

Powering structured, real-time planning

AI for FP&A

AI that does real work across your workflow

Integrations

Integrations

Data you need, where you need it

MCP Server

Enterprise-grade, secure LLM integration

Payments & Banking

Accounting

HRIS

CRM

ATS

Business Intelligence

Solutions

menu arrow

Use Cases

Data Management

Executive Reporting

Reporting & Analysis

Planning & Modeling

Cash Management

Ad-Hoc Reporting

Annual Planning

Forecasting

Scenario Analysis

Variance Analysis

Financial Close

Financial Planning and Modeling

Vendor Expense Planning

Capex Planning

Driver Based Planning

Data Consolidation

Headcount Planning

Roles

Cube for CFOs

Cube for FP&A

Cube for Controllers

Cube for CEOs

Industries

Business Services

Financial Services

Healthcare

Manufacturing

Nonprofits

Real Estate

Retail

SaaS / Software

Multi-Location

Resources

menu arrow

Get Started

Strategic Finance Assessment

Benchmark your finance maturity

Spreadsheet Templates

Ready-to-use models and tools

Developer Center

Build and extend with Cube’s API

Learn

Blog

Insights and tips for modern FP&A

The Finance Fix Newsletter

Weekly finance news and strategies

eBooks & Guides

Deep dives on strategic finance levels

FP&A Glossary

Key terms every finance pro needs

Webinars & Videos

Expert talks and product demos

Community and Support

Customer Stories

Real results from real teams

Help Center

Answers, docs, and how-tos

Workshops

Live sessions to level up

Company

menu arrow

About Cube

Explore our vision and team

Careers

Help shape the future of FP&A

In the News

Cube featured in top publications

Security

Enterprise-grade, cloud security

Partnership

Join the Cube ecosystem
Pricing
FREE DEMO
Rolling Forecast & Annual Budgeting Software | Cube

Use case · Annual budget & rolling forecast

The budget holds. The forecast keeps moving.

Cube runs budget season as one shared workflow: owners plan in their own views, approvals land in one model, and actuals then roll the budget into a living forecast.

Book a demo See it in action

Planning season

The board approved a budget in January. The business changed by February.

The template collection

Forty templates go out, thirty come back changed, and the master file breaks the night before the review.

Version chaos

Finance, department heads, and the CFO each hold a different final file, and nobody can say which one the board saw.

A plan frozen in time

The numbers lock in December, revenue moves in January, and every variance meeting argues with a figure that no longer describes the business.

Budget season, together

One budget, built by forty owners.

Budgeting is a company-wide workflow, and Cube runs it end to end: finance sets the frame, owners plan their part, and one version carries to sign-off.

01

Templates go out

Every owner opens a template pre-filled with their own actuals, scoped to their departments.

02

Owners plan in place

Department heads work in Excel, Sheets, or Cube, and every input publishes back to one model.

03

Finance reviews live

Submissions land as they happen, with no collection emails and no master-file merges.

04

Approve and lock

Sign-off locks the version, and the approved budget becomes the baseline for the year.

Sign-off is where the budget stops aging: from the first close, the same model rolls it into a current forecast.

One governed model

Then the budget rolls into one live forecast.

There is no reforecast workbook and no v7_FINAL. Each close, actuals land in the model the board approved, the horizon rolls forward, and everyone opens the one current version, and the same numbers feed your executive reporting.

What flows in NetSuite · GL actualsHRIS · headcount & compDepartment inputspublished back

Cube

One governed model holds the budget, the actuals, and every reforecast, with each figure traceable to the source.

Where it shows up Excel & Google SheetsBudget vs actualslive all yearBoard & exec viewsalways current
GL actuals syncedBudget FY26 lockedRolling FC current

The monthly rhythm

A reforecast workflow that runs itself.

Cube Workflows turns the reforecast into a cadence: everyone knows what they owe, and finance sees status at a glance.

01 · Close lands

Actuals sync in, and reforecast tasks go out to every owner automatically.

02 · Owners update

Each owner revises their drivers and inputs in their own view, on live numbers.

03 · Finance tracks status

Submissions, stragglers, and approvals in one view, with nudges built in.

04 · The version locks

Sign-off stamps the reforecast of record, and the audit trail keeps the history.

Live data

Budget, actuals, and the reforecast in one grid.

Fetch actuals as they land, compare them to budget, and publish the rolling forecast back to the model without leaving your spreadsheet.

fetched live from Cube forecast inputs, published back to Cube bi-directional: fetch actuals in, publish the reforecast back
Watch June actuals land in the grid.On the demo we fetch live actuals next to budget and publish a reforecast back to the model while you watch.
Book a demo

Charted

Actuals hand off to the forecast.

The month closes, the bar turns navy, and the forecast rolls one further. One model draws both.

728 May 748 Jun 745 Jul · FC 745 Aug · FC 745 Sep · FC $K · total opex · navy = actuals, gray = rolling forecast · ties to the grid above

Why Cube

One budget season, then a forecast that stays current.

Does it solve my problem?

One version, finally

Budget, actuals, and every reforecast live in one model, so the file wars end and reviews start from agreement.

How is it different?

Reforecast without rebuilding

Roll the horizon forward and revise your drivers. The model you built in budget season carries every forecast after it.

Can I trust it?

Trace to the source

Any figure opens to the transactions behind it, so a variance is a conversation about the business rather than the data.

Adoption

Built for finance to run.

Cube deploys alongside the spreadsheets and systems you already use, designed for finance to run without waiting on outside consultants.

No code

Finance-led setup

Configured by your team, guided by ours.

100s

of sources

Cube connects to hundreds of source systems, with pre-built connectors for major platforms.

0

Rip-and-replace

Your ERP, HRIS, and spreadsheets stay exactly where they are.

1:1

Onboarding

Hands-on setup and a named contact through budget season.

Cube in action

Budget season with agents on your team.

FP&Agents work inside the same governed model as your budget, so everything they draft is traceable and finance approves before anything changes.

Variance explanations

Ask why cloud spend ran $42K over budget in Q2 and get the drivers, the transactions, and draft commentary for the review.

Reforecast prep

Smart Forecasting rolls the horizon forward, refreshes driver assumptions, and flags the lines that moved from budget.

Department follow-ups

Owners ask about their own budget vs actual in plain language and get governed answers without waiting on finance.

Book a demo

Where you work

One model, on every surface.

Cube delivers the same governed numbers wherever the work happens. Explore the full story on Where You Work.

Cube Workspace

The browser app where finance builds the model, sets permissions, and publishes.

Excel & Google Sheets

Bi-directional sync: fetch live actuals into the sheet, publish plans back.

AI assistants via MCP

Claude, ChatGPT, and Gemini answer from your governed numbers.

Slack & Teams

Ask a question in chat and get the governed figure back, with the trace.

PowerPoint & Google Slides

Decks with figures bound to Cube that refresh to the current numbers.

BI tools

Tableau, Looker, and Power BI read from the same model as the plan.

Workflows

Where the budget and forecast meet the business.

Annual planning cycle

Build the budget from templates that read and write to one model instead of forty diverging files.

Monthly reforecast

Actuals land, the horizon rolls forward, and the forecast updates on a cadence the business can feel.

Department budget vs actual

Every owner sees their own lines, live, without asking finance for an export.

Headcount & comp

Hiring plans feed the budget directly through headcount planning in Cube.

Vendor & software spend

Contract renewals and tooling costs stay budgeted and tracked with vendor and expense planning.

Top-line assumptions

Bookings and pipeline flow from revenue planning into the same forecast the board sees.

See your budget season in Cube.Bring your current template. We will run the same cycle on one governed model, live.
Book a demo

Controls

Governed enough for the board pack.

Budgets carry commitments, so the controls matter. The full posture lives on our security page.

SOC 2 Type II SSO & SAML GDPR Audit trail

Role-based access

Department heads see their own lines and nothing else.

Version control

The approved budget, each reforecast, and every scenario is a named, locked snapshot.

Full audit trail

Every change to a plan carries who, what, and when.

Read-only by default

Cube reads from your source systems and never writes back to them.

Trace to the transaction

Every variance line opens.

Every finance leader knows the feeling of defending a number they cannot fully explain. Here, the June cloud overage opens to its accounts and the invoices behind them.

Already convinced?

Book a demo and watch the whole cycle run on your own workflows. Still researching? The sections below cover what a rolling forecast is, why it is hard, and what to look for in the software.

Book a demo

The definition

What is a rolling forecast?

Rolling forecast

A rolling forecast is a financial forecast that always extends a fixed horizon into the future, such as 12 or 18 months, and is updated as each period's actuals land. Where an annual budget is set once and ages as the year unfolds, a rolling forecast drops the period that just closed, adds a new period at the far end, and revises the periods in between, so the business always plans against a current view.

In Cube, the rolling forecast starts from the governed model the budget was built in, so actuals flow in automatically and each update is a revision instead of a rebuild.

Side by side

Rolling forecast vs annual budget: what changes?

Most teams keep both. The budget sets the commitment; the rolling forecast tracks reality against it.

Static annual budget

  • •Set once, before the year starts, and locked as the commitment.
  • •Ages as the business moves; by mid-year it describes a different company.
  • •Variance analysis explains the past.
  • •A reforecast means rebuilding the workbook, so it rarely happens.

Rolling forecast

  • •Updated as actuals land, month after month.
  • •Always looks a fixed horizon forward, so planning never stops at December.
  • •Variance analysis changes the plan ahead.
  • •A reforecast is a revision of one model, so it happens on cadence.

The honest part

Why is rolling forecasting difficult?

The concept is simple. The workflow is what breaks, in six familiar ways.

Version control

Every reforecast spawns new files. Cube snapshots each version in one model, so Budget, June FC, and July FC stay comparable.

The template collection

Chasing department templates eats the calendar. In Cube, departments enter numbers that write straight to the model.

Actuals land late

A forecast is only as fresh as its actuals. Cube syncs the GL, so every reforecast starts from actuals as they land.

Department sandbagging

Padded numbers hide in opaque files. One transparent model shows assumptions next to actuals, line by line.

The cost of reforecasting

When each update means rebuilding the workbook, teams stop updating. Cube rolls the horizon forward on the model you already have.

Calendar-driven updates

Most teams reforecast when the calendar says so. With live actuals, you can also reforecast when the business says so.

Six problems, one model.On the demo, pick the one that hurts most and we will show how Cube removes it.
Book a demo

The workflow gap

Manual vs automated budgeting and forecasting.

Manual (spreadsheets and email)With Cube
Collecting inputs✗Templates emailed out and pasted back by hand✓Departments enter numbers that write to one model
Loading actuals✗Exports downloaded and re-keyed every close✓GL actuals sync automatically as they land
Version control✗v14_FINAL_final and a diverging master file✓Named, locked snapshots of one governed model
Reforecasting✗A rebuild big enough that it happens once a year✓Roll the horizon forward and revise the drivers
Variance review✗Arguing about whose number is right✓One number, traced to the transaction behind it

Four maturities

Which type of forecasting process fits your team?

Static annual budget

One plan set before the year starts and reviewed against actuals. It works while the business holds still.

Budget plus quarterly reforecast

The budget stays as the commitment and the forecast refreshes each quarter. The most common first step up.

True rolling forecast

A 12 or 18 month horizon that rolls forward every month, so planning never restarts from zero.

Driver-based rolling forecast

The forecast recalculates from business drivers such as pipeline and headcount. See our guide to driver-based planning.

Best practices

How do you run a rolling forecast well?

Keep budget and forecast in one model

Comparisons only work when both read the same structure and the same actuals.

Forecast fewer lines than you budget

Reforecast the twenty or so lines that actually move and hold the rest at budget.

Anchor volatile lines to drivers

Tie revenue and headcount-driven costs to their drivers, so an update is assumptions work rather than data entry.

Snapshot every version

Lock each forecast before revising it, so accuracy is measurable over time.

Reforecast on events, with month-end as the floor

A missed quarter or a major deal should trigger an update ahead of the calendar.

Buying guide

What to look for in budgeting and forecasting software.

A direct GL connection

Actuals should land in the model without exports, from hundreds of source systems.

A governed, versioned model

Named snapshots, a locked budget, and one structure every report reads from.

Spreadsheet-native planning

If the team plans in Excel or Google Sheets, the software should work there rather than replace it.

Traceability

Any figure should trace to the transaction behind it, or variance meetings stay arguments.

Department self-serve with permissions

Owners should see their own lines and submit inputs without touching anyone else's.

AI that respects governance

Agents should draft commentary and reforecasts from the governed model, with finance approving every change.

Run the checklist against Cube.Bring this list to the demo and score us on every line, on your own use case.
Book a demo

Run budget season once. Stay current all year.

Book a demo and watch budget, actuals, and a rolling reforecast run in one governed model, on your own workflows.

Book a demo

You will see the live grid, the variance drilldown, and FP&Agents at work.

FAQ

Questions buyers ask.

Implementation is finance-led and requires no code. Your team connects source systems through pre-built connectors, maps the chart of accounts into the model once, and builds budget and forecast templates with guided onboarding and a named contact. Cube deploys alongside the tools you already run, so there is no rip-and-replace.

Cube connects to hundreds of source systems, with pre-built connectors for major platforms such as NetSuite, Sage Intacct, and QuickBooks, plus flexible connection methods for the rest. GL actuals, headcount data, and pipeline data flow into one governed model automatically.

No. Cube is built to run inside the spreadsheets your team already uses. You fetch governed actuals into Excel or Google Sheets, build the budget and the rolling forecast there, and publish inputs back to the model. The workflow stays familiar while the data underneath becomes governed and traceable.
Every version is a named, locked snapshot of the same model: the approved budget, each monthly reforecast, and any scenario. Because all versions share one structure and one set of actuals, any two are directly comparable, and forecast accuracy can be measured over time.
Yes. Role-based permissions scope every user to their own departments and accounts. Owners can check budget vs actual, drill into their variances, and submit forecast inputs while payroll and other sensitive lines stay restricted to the people who should see them.
Cube is SOC 2 Type II audited, supports SSO and SAML, connects to source systems read-only by default, and keeps a full audit trail of every change. Access is role-based, so each user sees only the departments and accounts they are permissioned to see.
logo-cube-image.svg logo-cube-image.svg

Schedule a Demo.

Please provide your details, and a member of our sales team will personally coordinate a time that works best for you.