How to Stress-Test a 13-Week Cash Flow Forecast for Late Customer Payments

Your cash forecast says you’ll finish the quarter with $420,000 in the bank.

Wonderful.

Unfortunately, payroll is due in three weeks, your largest customer has stopped answering emails, and the $420,000 doesn’t arrive until week twelve.

This is how companies end up profitable, growing, and having uncomfortable conversations with their lenders.

A 13-week cash flow forecast should show whether the business can meet its obligations throughout the quarter, including when expected customer payments arrive late.

The most useful stress test is straightforward: delay a material customer receipt, leave committed payments on their actual dates, and calculate the lowest cash balance before the money arrives.

That tells management how much liquidity is at risk, when the problem emerges, and how much time remains to respond.

Start With the Cash Balance That Actually Matters

Most cash forecasts show beginning cash, expected collections, disbursements, and ending cash.

That’s a reasonable starting point. It also leaves out a question CFOs should be asking:

How much cash can we afford to lose before something important becomes a problem?

The answer requires a minimum operating cash reserve.

That reserve might reflect upcoming payroll, unavoidable supplier payments, debt obligations, lender requirements, or the amount of liquidity management considers necessary to operate safely.

It shouldn’t be a number someone picked because it looked conservative in a board presentation.

For each week, calculate:

Ending cash = Beginning cash + Cash receipts − Cash disbursements

Then calculate:

Cash headroom = Ending cash − Minimum operating cash reserve

Headroom tells management how much room remains before the business falls below its chosen operating threshold.

A company with $150,000 in the bank and a $125,000 minimum reserve has $25,000 of headroom.

That’s a considerably different position from a company with $150,000 and a $40,000 reserve.

Same bank balance. Different decisions.

What Happens When a $100,000 Customer Payment Arrives Three Weeks Late?

Consider a hypothetical company with $200,000 in opening cash and a minimum operating reserve of $75,000.

Management expects a $100,000 customer payment in week two.

The customer has historically paid on time, but its latest invoice is awaiting approval. Finance wants to understand what happens if payment moves to week five.

Here’s the original forecast and the delayed-payment scenario.

All amounts below are illustrative and shown in thousands of dollars.

The delayed scenario removes $100,000 from week two and adds it to week five. All other assumptions remain unchanged.

Notice what happens.

The base forecast never falls below the $75,000 reserve.

Under the delayed-payment scenario, cash falls to $70,000 in week three and $50,000 in week four.

The maximum shortfall against the reserve is $25,000.

The business doesn’t necessarily run out of cash. But it breaches management’s minimum liquidity threshold for two consecutive weeks.

That’s the distinction the CFO needs.

The eventual customer payment restores the projected cash balance in week five. It doesn’t solve the week-four funding problem.

Cash arriving later is surprisingly unhelpful when payroll arrives first.

Calculate the Funding Gap, Not Just the Delayed Revenue

A common mistake in liquidity analysis is treating the entire delayed invoice as the funding requirement.

In our example, the delayed collection is $100,000.

The maximum reserve shortfall is only $25,000.

Those figures answer different questions.

The $100,000 represents the temporary reduction in expected receipts. The $25,000 represents the additional liquidity needed to maintain the company’s chosen minimum reserve, assuming the rest of the forecast holds.

The calculation is:

Required liquidity support = MAX(0, Minimum reserve − Lowest projected cash balance)

For this example:

$75,000 − $50,000 = $25,000

That doesn’t automatically mean the company should borrow $25,000.

Management might accelerate another collection, defer an optional purchase, negotiate a payment date, or draw against an existing credit facility.

It also doesn’t mean $25,000 is sufficient under every outcome. A second delayed payment, an unexpected expense, or an inaccurate opening balance could increase the requirement.

The forecast identifies the problem. The scenario analysis helps management decide how to address it.

Stress-Test More Than One Collection Date

A single downside case is useful, but customer payment uncertainty rarely comes with a precise calendar invitation.

Instead, test a few plausible dates.

For the same $100,000 receipt, management could examine:

• Base case: Payment arrives in week two.
• Moderate delay: Payment arrives in week four.
• Severe delay: Payment arrives in week five.
• Noncollection within the forecast: No payment arrives during the modeled period.

Keep other assumptions unchanged initially. This isolates the effect of the customer’s payment timing.

Then calculate the lowest weekly cash balance and maximum reserve shortfall for each scenario.

For the first five weeks of our example:

These results cover the five illustrated weeks, not the entire 13-week forecast. A full analysis must check all thirteen weeks and identify the actual lowest balance.

The differences matter.

If the customer pays in week four, management faces a relatively small temporary reserve breach.

If payment moves to week five, the shortfall increases.

If the money doesn’t arrive at all during the illustrated period, the company needs a much more serious liquidity response.

And if the customer represents a meaningful concentration of revenue, the CFO should probably be discussing credit exposure alongside cash forecasting.

A late payment can be a timing issue. Repeated late payments may be telling you something about the customer’s financial condition.

Don’t Confuse Probability With Available Cash

Finance teams sometimes handle uncertain collections by applying a probability to the invoice.

A $100,000 receipt with an estimated 70% collection probability becomes $70,000 in the forecast.

That can be useful when calculating an expected value across many uncertain receipts.

It can also create a dangerous illusion when evaluating a single large invoice.

Your customer generally doesn’t pay 70% of an invoice because your spreadsheet assigned it a 70% probability.

The cash may arrive in full, arrive late, arrive partially, or fail to arrive.

For material collections, discrete scenarios often provide a clearer picture of liquidity risk than a probability-weighted average.

Probabilities can still inform the likelihood of each scenario. They shouldn’t hide the amount of cash the business needs if the unfavorable outcome occurs.

Decide What Management Will Do Before the Shortfall

A stress test earns its place in the finance process when it changes a decision.

For a projected $25,000 reserve shortfall, the CFO should establish a response before week four.

That could mean asking the collections team to confirm the customer’s approval and payment status, identifying other invoices that can realistically be collected sooner, reviewing discretionary payments, or confirming available borrowing capacity.

Each action needs a cash impact, timing assumption, and owner.

For example, management might consider postponing a $30,000 equipment purchase originally scheduled for week four.

If the purchase is genuinely discretionary and can be moved to week six without operational or contractual consequences, the week-four projected balance improves from $50,000 to $80,000.

That keeps the business above its $75,000 reserve in week four, although the $5,000 reserve breach in week three remains unresolved.

And the equipment payment still needs to appear in week six.

Deferring spending isn’t a permanent cash improvement. It’s a timing decision, and the model should show where the obligation moves.

The same discipline applies to credit facilities. Confirm actual availability, borrowing conditions, interest costs, and repayment assumptions before treating financing as accessible cash.

Build a Weekly Review Around Exceptions

Once the forecast is operating, the finance team should update it weekly.

Start by replacing the completed week’s estimates with actual receipts and disbursements. Reconcile the cash position, investigate meaningful differences, and add another week to maintain the 13-week horizon.

Pay particular attention to collection timing.

If a customer expected to pay in week two hasn’t paid, the next forecast shouldn’t quietly assume the money will arrive in week three without new evidence.

That’s how a forecast becomes a rolling collection of optimism.

The review should answer four questions:

1. Which expected receipts failed to arrive, and why?
2. What changed in the timing or amount of committed payments?
3. When does projected cash reach its lowest point?
4. Which management action is required, by whom, and by what date?

For major customers, the forecast should distinguish between an invoice’s contractual due date and the date finance reasonably expects to receive the cash.

Payment history, unresolved disputes, customer approvals, and direct collection updates can all affect that assumption.

Keep the original forecast version as well. Comparing what finance expected with what actually happened helps identify whether errors come from customer behavior, missing obligations, or assumptions that nobody challenged.

When Should the CFO Escalate a Cash Forecast Warning?

A reserve breach shouldn’t be the first time management hears about a liquidity problem.

Set escalation rules based on projected headroom and the time available to respond.

For example, a company might require a formal liquidity review whenever a downside scenario falls below its minimum reserve, even if the base case remains healthy.

It might require the CFO to approve discretionary payments when projected headroom drops below a defined amount.

And it might require a documented funding plan before a projected shortfall reaches a point where ordinary collections activity can no longer resolve it.

These are management policy decisions, not universal financial thresholds.

The correct limits depend on the company’s cash volatility, payment obligations, access to financing, and tolerance for disruption.

One additional caution: weekly ending balances can conceal a shortage that occurs earlier in the week.

If payroll clears Tuesday and a major customer payment arrives Friday, the company could face a temporary liquidity problem even when Friday’s ending balance looks acceptable.

For tight liquidity situations, supplement the weekly forecast with daily cash timing around critical payment dates.

Put the Forecast to Work

A 13-week cash flow forecast becomes considerably more useful when it shows what happens if management’s assumptions are wrong.

Late customer payments are a sensible place to start because they expose the difference between reported revenue and usable cash.

The objective is to identify the lowest cash balance, quantify the exposure, and give management enough time to choose a response.

A forecast that predicts a shortfall after the company has already missed payroll is technically a forecast.

It’s just a rather expensive one.

To test your own assumptions, use The Schlott Company’s free Finance Decision Lab, which includes a 13-week cash flow forecasting tool with weekly collections, payments, financing inputs, and a minimum cash reserve.

For businesses that need a maintained forecast, scenario analysis, and regular liquidity reviews, explore our Cash Flow Forecasting Services.