What it means
A company expects $100,000 of opening cash and $60,000 net inflow over a quarter. In a downside case, a large customer pays $40,000 late and urgent costs rise by $15,000, so ending cash falls to $105,000 instead of $160,000, before any response.
Start with a reliable base cash forecast listing opening cash, dated customer receipts, supplier payments, payroll, tax, debt service and other known flows, because a scenario cannot repair an inaccurate opening balance. Choose a horizon that matches the decision.
A 13-week view may help with near-term payroll and supplier commitments, while a longer view helps with expansion or financing, and detailed near-term dates should be grounded in invoices and payment schedules. A cash-management guide from Float describes scenario planning as running a forecast under multiple assumptions to see a range of cash positions, and distinguishes a scenario, which changes related inputs together, from a sensitivity that moves one input at a time.
Build coherent cases. If sales fall, variable purchasing may also fall, though perhaps later, and if a customer pays late, collection work and supplier terms may change.
Avoid stacking every bad outcome unless the stress case intentionally tests an extreme, and keep assumptions explicit by naming which customer payments shift, which expenses change and which contracts or dates support each input. Model timing, not only the ending total, because a company can end the quarter with positive cash yet fall below zero in week six.
The lowest projected balance and the date it occurs matter for funding decisions. CFA Institute's company-forecasting guidance recognises scenario analysis for considering multiple outcomes and notes that forecast drivers should match the company's model and available evidence.
Test operational triggers, since a customer missing an agreed payment date or a pipeline shortfall may signal the downside case is emerging, and decide in advance who reviews spending and when. Separate controllable levers from hopes: delaying a discretionary hire might be an option, but assuming a supplier will accept late payment without agreement is not an action plan.
Include financing terms carefully, because a credit line may have limits, interest and covenants, and unused borrowing capacity should not be assumed available until its current terms and draw conditions are checked. Refresh the model as actual cash moves by reconciling bank balances and receipts, removing forecasts that have become actuals and updating later periods, while keeping prior versions to see why expectations changed.
Use sensitivity tests as a companion, since moving collections by seven days or revenue by 10% can show which input matters most. Scenarios are structured possibilities, not probability-weighted promises unless a justified probability model is built, so label judgment calls and data gaps, check that cash held by one entity or in a restricted account is actually available, and protect essential suppliers, employee pay and legal obligations while reviewing optional outflows.
In practice
Real-world examples.
Example
A customer payment shifts four weeks later in a downside case. The forecast shows that the cash dip falls in the same week as payroll, so the owner arranges a bridging option in advance.
Example
A hiring decision is tested against a lower sales and slower collections case. The owner decides to start the hire a month later, which keeps the weakest week above the minimum buffer.
Example
A weekly forecast shows a cash dip despite a positive quarter-end total. The finance team sets a review trigger tied to the date the payment is due, so spending is checked before the dip arrives.
Formula
Calculation
Illustrative ending cash = Opening cash + Scenario receipts - Scenario payments
Worked example. A fictional business opens the quarter with $100,000 and expects $60,000 of net inflow in the base case, which gives $160,000. In the downside case a $40,000 receipt is delayed and $15,000 of urgent cost is added.
- Downside ending cash = $100,000 + $60,000 - $40,000 - $15,000 = $105,000.
- The difference from the base case is $160,000 - $105,000 = $55,000.
- If the delayed $40,000 arrives early in the next quarter, it must be counted there once, not in both periods.
Verify that late receipts are moved, not counted twice.Case study
Seen in the real world.
In this entirely fictional example, Birch Services expects 160,000 at quarter-end. Its downside case moves one 40,000 receipt later and adds 15,000 of urgent cost. The weekly model shows an earlier low point than the quarter-end number suggests. The owner reviews optional spending and confirms available financing terms. The scenario is a planning exercise, not a prediction.
Watch out
Common mistakes.
- Showing only quarter-end cash and missing an earlier shortfall.
- Assuming suppliers will extend payment dates without agreement.
- Double-counting a delayed receipt in both its old and new periods.
Questions
People also ask.
How does a scenario differ from sensitivity analysis?
A scenario changes a coherent set of assumptions; a sensitivity often changes one input.
How many scenarios are needed?
Enough to inform the decision; base and plausible downside are often useful.
Is a downside case a prediction?
No. It tests resilience if stated conditions occur.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%