8 Scenario Planning Examples That Protect Cash
A cash forecast that assumes every customer pays on time, every settlement arrives as expected, and payroll never changes is not a forecast. It is a best-case narrative. Useful scenario planning examples start with a reconciled cash position, then change one operational fact at a time: a hiring date, an invoice collection date, a processor reserve, or a vendor payment term.
For CFOs and operators, the objective is not to produce more versions of a spreadsheet. It is to establish the decision boundary before cash reaches it. Can the company hire now? Which invoices must be collected this week? How much room exists to accept a slower-paying enterprise contract? Those answers must trace to actual bank activity, open receivables, scheduled obligations, and explicit assumptions.
What Makes a Cash Scenario Decision-Ready
A scenario is only as credible as its starting point. If the opening cash balance does not reconcile to the bank, or forecasted collections are disconnected from the invoices and settlements that support them, a polished chart can still produce the wrong operational decision.
Start with a baseline forecast that reflects the direct timing of cash. This means modeling when an ACH payment is expected to land, when a card processor releases a settlement, when payroll clears, and when a loan debit hits the account. Revenue on the income statement matters, but it does not tell you whether Friday's payroll can be funded.
A decision-ready scenario has four properties. Its baseline is reconciled to $0.00. Its changed assumption is explicit and limited. Its effects flow through daily cash, not only monthly P&L. And every output can be traced back to the transaction, rule, invoice, bill, or planned event that created it.
This discipline also prevents a common failure mode: changing five assumptions at once, seeing a lower cash balance, and having no way to identify the actual driver. Run scenarios as controlled tests. Keep the base case intact, apply a named change, and compare the result.
8 Scenario Planning Examples for Operating Cash
The following examples use the questions finance teams confront in real operating cycles. The right answer depends on the company's margins, payment terms, concentration risk, available credit, and minimum cash policy. The method remains consistent: model timing, preserve evidence, and inspect the lowest daily cash point.
1. Hire Before Revenue Arrives
A services firm is considering a $120,000 annual hire, beginning May 15. The P&L may show sufficient annualized revenue to support the role. The cash question is narrower: can the business fund the first partial payroll, employer taxes, benefits, equipment, and the following two full payroll cycles before the related customer work is invoiced and collected?
Create a scenario that inserts the employee's start date and all associated cash outflows on their actual payment dates. Then compare the cash floor and runway with the baseline. If the floor drops below the operating reserve for ten days, the decision may be to delay the start date, stage the hire as a contractor, or accelerate specific collections. The model should show which choice changes the result and by how much.
2. A Major Customer Pays 30 Days Late
An overdue invoice is not merely an accounts receivable problem. It is a cash-timing event. Assume a $75,000 invoice expected on June 10 instead lands on July 10. Move only that collection date and observe every day between the two dates.
This is especially material when payroll, rent, debt service, and vendor payments are clustered near the original collection date. The scenario should not reduce revenue or write off the invoice unless that is the actual assumption. It should shift the cash receipt. That distinction preserves the relationship between the forecast, the ledger, and the underlying receivable.
3. Processor Settlements Slow Down
Subscription and commerce businesses often see sales activity before cash becomes available. A processor may settle on a two-day schedule, hold weekend activity until Monday, net out refunds and fees, or impose a reserve after a spike in volume.
Model a scenario where settlements extend by three business days and a 10% reserve is withheld temporarily. Use expected gross processing volume, fee rules, refund behavior, and the actual settlement calendar. A monthly revenue forecast can miss this completely because the economic sale still occurred. Direct-method cash forecasting reveals whether the delay creates a short-lived but operationally serious trough.
4. Renew a Vendor Contract at a Higher Price
A software, freight, or materials vendor proposes a 12% increase at renewal. The annual impact is easy to calculate. The harder question is how the new billing cadence changes liquidity. An annual prepayment may improve the unit price while creating a large near-term draw on cash.
Run at least two controlled versions: monthly billing at the new price and annual prepayment with the offered discount. Include implementation fees, taxes, and renewal timing. The scenario may show that the annual option is economically better but violates the company's minimum cash threshold during its seasonal low point. Lower cost is not automatically lower risk.
5. Change Customer Payment Terms
Moving standard terms from net 30 to net 15 can improve working capital, but only if customers follow the policy and billing operations can enforce it. Model new invoices under the proposed terms while leaving existing receivables on their original expected collection dates.
For a more conservative case, assume only a portion of customers pay earlier during the first two billing cycles. This prevents the forecast from treating a policy announcement as immediate cash. Finance can then quantify the value of adoption: for example, whether improved collections fund a planned hire or simply rebuild a depleted reserve.
6. Offer a Discount to Collect Earlier
Suppose a customer will pay a $50,000 invoice ten days early in exchange for a 2% discount. The visible trade-off is $1,000 of revenue or margin against earlier cash. The operating trade-off may be more consequential if the early receipt avoids drawing on a line of credit, missing payroll buffer, or delaying a high-return purchase.
Model the discounted receipt at the proposed date and the full receipt at the normal date. Then compare interest expense, borrowing availability, and the lowest cash point. This turns a negotiation into a measurable financing decision rather than a judgment call based only on gross margin.
7. Prepare for Seasonal Demand Before Cash Arrives
A seasonal business may need inventory, temporary labor, marketing spend, or production capacity weeks before its busiest selling period. Revenue projections can make the season look attractive while hiding the funding gap created by upfront payments.
Build the scenario from purchase orders, payroll schedules, deposit terms, expected sales, refund assumptions, and settlement lag. Test a modest demand case alongside the planned case. If demand comes in 20% below plan, identify whether inventory can be deferred, paid in installments, or reduced without damaging service levels. Scenario planning is most valuable before the commitment becomes noncancelable.
8. Refinance Debt or Draw on a Credit Line
A term loan refinance may lower the interest rate but introduce fees, a payoff date, collateral requirements, or a period when both old and new obligations overlap. Similarly, a line-of-credit draw solves a short-term gap but adds principal and interest payments later.
Model the exact cash events: proceeds, origination fees, payoff amounts, recurring debits, and any covenant-driven minimum balance. Compare the scenario against the baseline through the full repayment period, not only the month of funding. A financing decision that improves next week's cash but creates pressure during a known seasonal low requires a different operating plan.
How to Run Scenarios Without Breaking the Forecast
The control point is versioning. Preserve a locked baseline that reflects approved assumptions and reconciled actuals. Create a separate scenario with a clear name such as “July collection delay” or “Q3 hire on May 15.” State the changed input in plain language, including the amount, date, and confidence level.
Then inspect three outputs together: daily available cash, the minimum cash date and amount, and the changes in key obligations. A scenario that appears safe at month-end may still fall below payroll requirements mid-month. Monthly totals are useful for planning, but daily timing is where many cash failures occur.
The calculation path should be replayable. If someone asks why projected cash fell by $42,300 on June 21, the system should identify the moved collection, added payroll run, vendor debit, or settlement rule behind the number. Shekl applies this principle by keeping scenario changes connected to transaction-level evidence and deterministic financial rules, rather than allowing an opaque model to invent the forecast.
Finally, assign an owner and a trigger. A late-payment scenario may require the collections lead to act when an invoice reaches seven days past due. A hiring scenario may require cash to remain above a defined floor for two consecutive forecast cycles. A scenario without an owner or trigger is analysis, not control.
The most useful forecast is not the one with the cleanest chart. It is the one that tells your team, early enough to act, which cash commitment must change and exactly what evidence supports that decision.