Mid-period, the forecast stops answering the question. A number moves and someone asks what it does to the rest of the quarter. Excel forecast models get built to answer that. The balances in Business Central show where things stand, and finance works through the impact in Excel before anything changes in the system.
Excel forecast models in practice
Finance builds forecast models in Excel because the structure needs to change as assumptions change. The initial forecast may come from Business Central, but once the team starts adjusting timing, volumes, or cost behavior, the model has to support multiple versions at once.
That structure usually includes a base case, one or more alternative scenarios, and a set of assumptions that drive each version. Changes to revenue timing, headcount, or project delivery flow through the model and update the forecast outputs. The workbook becomes the place where those relationships are defined and tested before anything is reflected in the system.
Over time, those models accumulate additional layers. New assumptions are added. Existing drivers are refined. Additional outputs are built to support leadership questions. The model continues to produce the right answers, but the structure becomes more dependent on how the workbook is organized and maintained.
Where forecast models break under change
Finance updates forecast models throughout the reporting cycle. Revenue timing shifts, cost structures adjust, and project timelines move. Each update flows through the formulas and changes multiple outputs across the model.
The break becomes clear when finance cannot explain a result without stepping through the model. A number moves, and the team has to trace it across multiple tabs, formulas, and assumptions to understand what changed. The model still calculates, but the relationship between inputs and outputs is no longer clear at a glance.
That condition develops as updates accumulate. Finance adds new inputs alongside earlier assumptions. The team extends existing formulas and links new calculations to prior versions of the model. This is the natural result of working through multiple scenarios inside the same file as conditions change.
At that point, the model requires validation before it can be used. Finance reviews the calculations, checks how changes flow through the workbook, and confirms that the outputs align with the intended assumptions.
Excel forecast models and model structure
Excel forecast models rely on structure to keep inputs, calculations, and outputs connected. Finance defines where assumptions live, how those assumptions flow through the model, and where results are presented for review.
In a Business Central environment, that structure determines how easily finance can align the model with the underlying ledger. The forecast often starts from actual balances in the system and then extends forward based on updated assumptions. The model needs to reflect those starting points clearly so changes in the forecast can be understood in relation to current results.
A model that supports ongoing updates keeps those elements separated. Assumptions sit in one place. Calculations reference those assumptions consistently. Outputs pull from defined calculation layers instead of embedding logic directly in presentation schedules.
Finance maintains that structure as the model evolves. New scenarios follow the same pattern as existing ones. Additional drivers extend the model without changing how earlier calculations work. The workbook grows, but the relationships between inputs and outputs remain visible.
That structure allows finance to update assumptions, tie those changes back to Business Central balances, and understand the impact without reworking the model each time a question comes up.
How finance leaders use forecast outputs
Finance leaders use forecast models to answer questions that do not wait for the next reporting cycle. A number moves, and leadership wants to understand the impact on the rest of the period, the quarter, or the year.
The model supports that discussion by showing how changes in assumptions flow through to expected results. Finance adjusts inputs, reviews the updated outputs, and explains how the forecast shifts under each scenario.
Those conversations move quickly. Leadership asks follow-up questions. Assumptions change during the discussion. Finance updates the model and walks through the impact in real time.
That interaction depends on the model holding together under pressure. The team needs to understand how each change flows through the workbook so they can explain the result without stopping to reconstruct the logic.
Maintaining forecast integrity with live Business Central data
Excel forecast models sit on top of a starting point. That starting point comes from the . As finance updates assumptions and builds scenarios, the connection between the model and those balances needs to stay intact.
Export-based workflows place that responsibility on the reporting cycle. Finance refreshes data, confirms that the model reflects the latest balances, and checks that the outputs still align with the underlying ledger.
A live connection changes that structure. The model continues to live in Excel, but the balances feeding it come directly from Business Central whenever the file refreshes. Assumptions, calculations, and scenarios remain flexible, while the starting point stays aligned with the current state of the business.
That is where tools such as Velixo fit into the workflow. Finance keeps building and adjusting models in Excel, and the data underneath those models stays connected to Business Central. The model reflects current balances without requiring a separate step to reconnect the workbook to the system.
That structure supports the way forecast models are actually used. Finance can update assumptions, run scenarios, and explain the impact without stopping to verify whether the model still ties back to the ledger.
Learn more about what a budgeting/forecast process could look like with Velixo in the below video, and feel free to any time with questions.
