Setting up a rolling forecast next to D365: from annual budget to continuous foresight
An annual budget is made once a year and is on average months old by the time you steer on it. A rolling forecast shifts a period forward every quarter or month: you always look twelve to eighteen months ahead, with the latest actuals as the starting point.
Why the annual budget arrives too late
The pattern is the same in most D365 organisations. The budget process starts in September, consolidates in Excel, and is frozen in December. By March reality has diverged; by June nobody steers on the budget anymore but on separately maintained expectations — in Excel again. Forecasts are stale the moment they are finished.
The problem is not Excel. The problem is that input, consolidation and actuals live in three different worlds.
What a rolling forecast does differently
- The starting point is current. Every cycle begins with the actuals from your general ledger — not with the budget from ten months ago.
- The horizon moves along. Always 12–18 months ahead, also in November.
- Drivers instead of a thousand cells. FTEs, volumes and rates drive the outcome; only exceptions require manual work.
- One definition of the truth. Forecast, budget and actuals share the same semantic model — the conversation is about the numbers, not about whose version is right.
The setup on D365 data, step by step
Step 1 — Unlock the actuals. General ledger and subledgers flow from F&O to a lakehouse via Fabric link: no exports, no refresh delay (DirectLake).
Step 2 — Choose the input model. Planning sheets in Plan in Fabric give budget owners an Excel-like environment with versioning, approval and an audit trail underneath. Input at cost centre × ledger account × month, or driver-based where possible.
Step 3 — Consolidate automatically. Departmental forecasts roll up to the total without copy-paste; write-back lands in a governed database in Fabric.
Step 4 — Report the variance. One Power BI report shows forecast versus actuals versus budget, with the same definitions for everyone.
What it costs
No planning suite with its own per-user licences. Plan in Fabric runs on your Fabric capacity; occasional participants (approvers, management) count as a session, not a seat. For the full arithmetic — capacity in euros and the comparison with the Finance Premium route — see What does Microsoft Fabric cost? and the licence calculator on Budgeting & forecasting.
Realistic timeline
With a working lakehouse: a first forecast cycle in weeks. The Planning Readiness Assessment (€ 6,000–9,000, fixed, excluding VAT) settles the route up front — BPP or Plan in Fabric — and the capacity size, so the implementation holds no surprises. The 2027 budget process is the natural deadline for most organisations: to start in September, begin preparing before the summer.