A low risk in each week can still mean a material chance of a cash shortfall

A forecast may show a small chance of cash falling below its floor in every individual week. Management still needs a different measure: the chance that at least one shortfall occurs anywhere during the planning horizon. Meeting obligations requires usable cash when payments are due, not merely favorable odds in a selected column.

OpenStax's probability rules distinguish individual events from their union and explain why overlapping events cannot simply be added. Applied here, the events are cash-floor breaches in different weeks. Their overlap depends on how the business's cash path evolves.

Define the floor and the observation schedule. Zero cash, a management liquidity reserve and a contractual minimum balance are different thresholds. A model checked only at Friday close may miss a Wednesday payment problem, so the time resolution should match the decision.

Imagine 100 equally weighted, invented three-week cash paths. In one arrangement, the same five paths fall below the cash floor in every week. Each weekly breach rate is 5%, and the proportion of paths with any breach is also 5%.

In a second arrangement, five paths breach only in week one, a different five only in week two and another five only in week three. Each weekly breach rate is still 5%, but 15 separate paths breach somewhere. The horizon-wide breach rate is now 15%.

The weekly summaries are identical in the two arrangements. They cannot tell management which horizon-wide risk applies because they have discarded the identity of the paths. Keep each path intact long enough to identify whether, when and by how much it crosses the floor.

If 13 weekly breach events each had probability 5% and were independent, the chance of at least one breach would be one minus 0.95 raised to the thirteenth power, about 48.7%. This is an illustration of the independence formula, not a suitable default model of business cash.

Cash balances carry forward. A delayed receipt can reduce several consecutive weekly balances, while a later collection can reverse the effect. Payroll schedules, customer behavior and funding conditions can connect multiple periods. Those mechanisms usually need to be represented in dated cash paths.

Adding the weekly probabilities would count a path several times if it breaches in several weeks. Multiplying weekly non-breach probabilities would impose independence if no conditional relationships are modeled. Neither shortcut is justified merely because the spreadsheet presents separate weekly columns.

For each simulated path, calculate the lowest available-cash balance over the defined dates. Compare that minimum with the floor and mark the path once if a breach occurs. The proportion of marked paths estimates the model's horizon-wide breach probability when the paths have equal weights.

For explicitly weighted scenarios, sum the weights of the scenarios that breach rather than dividing their count by the number of scenarios. A small set of management cases may have no defensible probability weights. In that situation, report the cases and consequences without relabeling their frequency as a statistical probability.

Use the same available-cash definition throughout the path. Exclude inaccessible funds where appropriate and reflect transfers only when they can occur. A group-wide balance that becomes available only after a delayed transfer should not prevent the operating entity from registering an earlier funding gap.

Retain a stable path identifier while calculating those measures. Sorting each weekly column separately would break the economic sequence and make the resulting minimum or breach count describe combinations that the model never generated.

A 10% chance of a brief $2,000 shortfall creates a different planning problem from a 10% chance of a $200,000 gap lasting a month. Retain the minimum balance, first breach date and duration for each affected path. The single probability does not describe the cash required to respond.

Separate the unconditional distribution of minimum cash from summaries calculated only among paths that breach. An average shortfall among adverse paths is conditional on the event. Labeling it simply as expected shortfall can confuse readers unless the calculation and conditioning are explained.

Use the first-breach dates to examine lead time. A facility that can be arranged after six weeks cannot solve a week-two problem without another bridge. Match response options to the dates and conditions in the affected paths, including any costs or commitments they create.

A cash model may automatically draw a credit line whenever the balance falls below the floor. If the line is assumed unlimited and immediately available, the displayed breach rate may be zero by construction. That result does not establish that the business can obtain the modeled funding.

Show the unfunded path, the proposed response and the remaining path after feasible actions. Apply actual facility limits, draw conditions and timing. Where management can defer discretionary spending, represent the decision rule and the notice needed to avoid the payment.

Distinguish an approved action from a possible one. An uncommitted lender conversation can be tested as a scenario, but it should not silently turn into guaranteed cash in every simulation. The risk report should expose the commitment needed to make the proposed response real.

The calculated rate depends on receipt assumptions, payment coverage, dependencies and the simulation design. More paths can improve numerical precision without fixing omitted obligations or an unrealistic collection model. Explain the main assumptions that drive the chance and size of a breach.

Present weekly risk, whole-horizon risk and the response schedule together when they inform different decisions. Preserve the model version and evaluate emerging actual cash against its paths. Management then has a direct answer to whether the business can remain funded across the period, with the conditions behind that answer visible.