Financial Model Scenario Analysis
Compare coherent alternative assumptions and understand why profit, cash and funding change between cases.
Base / Upside / Downside · FY2026
Preview · Illustrative values · EUR thousandsIncome Statement
| Line item | Base | Upside | Downside |
|---|---|---|---|
| Revenue | 12,960.0 | 13,440.0 | 12,240.0 |
| EBITDA | 2,980.8 | 3,091.2 | 2,815.2 |
Balance Sheet
| Line item | Base | Upside | Downside |
|---|---|---|---|
| Accounts receivable | 1,704.3 | 1,472.9 | 2,179.7 |
| Cash & Cash Equivalents | 4,006.8 | 4,292.4 | 3,450.1 |
Cash Flow Statement
| Line item | Base | Upside | Downside |
|---|---|---|---|
| Cash flow from operations | 2,107.7 | 2,409.8 | 1,526.2 |
| Change in cash | 984.0 | 1,269.6 | 427.4 |
Free · No signup
Give each case an economic explanation
Scenario analysis compares persistent alternative assumption sets in the same financial model. Base expresses the central operating plan; Upside and Downside express plausible favorable and adverse conditions. These labels do not assign probabilities. Define the business story, horizon and decision first, then choose assumptions that belong together.
A downside may combine slower demand with delayed collections. An upside may require capacity investment or earlier hiring, so it need not generate the most immediate cash. Keep historical data and opening balances common unless the purpose explicitly requires another starting position. The modeling methods guide explains how the assumptions become calculations.
Define Base, Upside and Downside without changing everything
Document the few drivers that distinguish the cases: sales growth, gross margin, staffing, customer collection time, inventory needs and planned investment. Hold unrelated assumptions constant to make the differences interpretable. Link dependent costs and balances to the same sales case instead of typing independently attractive outputs.
The illustrative preview uses the same industrial company, history and forecast calendar. Base has 8% revenue growth and 48-day DSO; Upside has 12% growth and 40-day DSO; Downside has 2% growth and 65-day DSO. Other operating assumptions are inherited. These values demonstrate comparison and are not estimates for a real business.
Compare outcomes and explain the bridge
Read revenue, gross margin, EBITDA and EBIT alongside operating cash flow, capex, closing cash and debt. Identify which assumptions explain each difference from Base. Growth can raise earnings while absorbing working capital; later collections can reduce cash with unchanged revenue. Compare periods and the lowest cash point as well as the final year.
Review whether every case remains internally consistent: asset investment supports activity, costs match capacity and funding follows cash needs. The financial model analysis workflow provides the broader review sequence. A scenario with a desirable output is only useful when the assumptions that produce it are defensible.
Scenario analysis, sensitivity and What-If answer different questions
A coherent scenario varies a related set of assumptions. A simple sensitivity test varies one assumption while holding others fixed to understand its influence. For example, testing DSO alone explains collection exposure; combining demand, margins and DSO answers how an adverse business case develops. Neither exercise assigns a statistical probability by itself.
What-If analysis isolates discrete temporary changes or transaction effects, such as borrowing or a financed equipment purchase. The product’s identifiable transactions can be disabled or removed; they do not replace persistent scenario assumptions. A manual sensitivity exercise can use controlled case comparisons, but this page does not claim an automated general sensitivity or Tornado feature.
Retain cases in BalanceCheat and verify inheritance
In Advanced, select the intended scenario before editing its forecast. Unchanged inputs inherit Base; targeted overrides retain the alternative method or assumption. Verify the selected case, period and source when changing a driver. Display the relevant scenarios together and compare the same statement basis. The scenario implementation reference explains inheritance, resets and comparison controls.
Keep reported and adjusted results separate; use the adjustment reference when interpreting a normalization or pro-forma bridge. Save the model and export a backup to retain the assumptions behind the comparison. Cases remain persistent model data rather than temporary explanations beside an output.
Use AI assistance for proposals, then review the model
General scenario analysis does not require AI. When you choose to use an external AI, specify the scenario, assumptions, periods and intended result to inspect. The AI-assisted scenario workflow covers that separate task and the review of pending AI changes.
The financial calculations still come from the model. Check the resulting assumptions and linked effects before relying on a proposed case. Continue in the integrated three-statement model to compare profit, balances and cash within one structure.
Frequently asked questions
What is financial model scenario analysis?
Comparing persistent, coherent alternative assumption sets in one model to understand changes in profitability, cash, investment and funding. Base, Upside and Downside are common case labels.
How is scenario analysis different from sensitivity analysis?
A scenario changes a related set of assumptions to describe a business case. A simple sensitivity varies one assumption with others fixed to isolate its influence. Neither automatically provides probabilities.
Does a What-If transaction create a permanent forecasting case?
No. It adds an identifiable, reversible transaction effect within a selected scenario. Persistent scenario assumptions remain a separate part of the model.
Is AI required to compare scenarios in BalanceCheat?
No. You can edit and compare scenarios directly in Advanced. An external AI is optional and follows its own proposed-change review workflow.