Month-End Cash Looks Fine. Find the Weekly Shortfall and Close It.

Month-end liquidity can conceal a weekly funding failure

A monthly cash view compresses timing. It can net an early supplier payment against a later customer receipt even though the bank account must fund them on different days. A positive month-end position therefore does not prove that scheduled obligations are executable throughout the month.

The management question is not simply whether the month generates enough cash in aggregate. It is whether the timing, certainty and sequence of receipts and payments preserve usable liquidity on every decision-relevant date.

How do you build a 13-week cash flow forecast?

Build a 13-week cash flow forecast by starting with reconciled available cash, assigning expected receipts and payments to the week in which the bank movement is expected, and calculating closing cash as opening cash plus receipts minus payments. Roll each week’s closing balance into the next week’s opening balance, compare the result with the minimum cash buffer, test timing and uncertainty scenarios, and update the forecast weekly using actual bank movements while adding a new thirteenth week.

This is a direct cash forecast. It models expected bank movements rather than deriving cash from accounting profit. Revenue, purchases and expense recognition remain useful evidence, but their accounting dates do not determine when cash enters or leaves the bank.

Use thirteen connected weekly cash positions

The horizon is long enough to expose near-term funding pressure while remaining close enough to individual invoices, payrolls, taxes, supplier commitments and financing movements. Each week should retain more detail than the executive view: counterparty, amount, contractual date, expected date, confidence, evidence, owner and scenario treatment.

The arithmetic is recursive. Week 1 closes at 120 + 70 − 100 = 90; that EUR 90 thousand becomes week 2 opening cash. Week 2 closes at 90 + 10 − 45 = 55, which becomes week 3 opening cash. No week is calculated independently, because a timing change affects every later opening balance until the displaced cash flow re-enters the forecast.

Weeks 5–13 are illustrative extensions, not additional factual claims. In practice, forecast precision normally declines with distance. Near weeks should be supported by named transactions; later weeks may use controlled recurring schedules, purchase plans, payroll calendars and documented assumptions.

Reconcile the first four weeks before changing the plan

The synthetic base case uses payments as positive amounts that are subtracted from cash. All figures are EUR thousands.

Week 2 is the first breach: 90 + 40 − 85 = 45. The month-end balance of 75 is recovered only because week 3 contributes a net EUR 30 thousand. The forecast therefore identifies a timing problem before management approves the payment run.

The worked example assumes no unmodelled overdraft, restricted cash, foreign-exchange movement or intra-group transfer. If any of those exist, they belong in explicit rows rather than inside a balancing plug.

Trace the EUR 30 thousand receipt to the receivables schedule

One line in the synthetic aged-receivables schedule drives the scenario. The record remains the same economic receivable as its forecast timing changes.

The contractual due date, expected collection date and confirmed receipt date are not interchangeable. The due date states when payment should occur. The expected date represents the current operational forecast and may change with evidence. The confirmed date is historical bank evidence after settlement.

When the expected date moves, the model removes EUR 30 thousand from week 2 receipts and adds exactly EUR 30 thousand to week 3. It does not delete the receipt, count it twice or relabel an expectation as confirmed cash.

Move both sides of each timing decision

The delayed-receipt scenario changes receipts from 40 to 10 in week 2 and from 95 to 125 in week 3. Cash therefore closes week 2 at 90 + 10 − 85 = 15 and week 3 at 15 + 125 − 65 = 75.

The proposed action moves a EUR 40 thousand supplier payment from week 2 to week 4. Payments become 45 in week 2 and 90 in week 4. Cash closes at 55 in week 2, rises to 115 in week 3 when the customer receipt arrives, then returns to 75 after the deferred supplier payment is executed in week 4.

The earlier Monthly Management Reporting Pack explains why historical operating cash missed plan. This forecast takes the next step: it locates the future liquidity breach by week and tests an action before the payment is released.

A safe Friday balance can still hide a Wednesday breach

Closing week-2 cash of EUR 55 thousand gives only EUR 5 thousand of headroom. The CFO must therefore inspect the order of movements within the week before accepting that rescheduling is sufficient.

If the EUR 10 thousand Tuesday receipt moved to Thursday, Wednesday cash would fall to EUR 45 thousand before recovering to 55. The end-of-week result would be unchanged, but the intrawweek control would fail. Management must then advance another receipt, defer an additional payment, draw an authorised facility or accept a formally approved temporary buffer breach.

The weekly model is therefore a screening layer. Weeks with narrow headroom require a daily treasury schedule, value-date confirmation and visibility over bank cut-off times. A payment marked “Wednesday” may leave the account before a receipt expected on the same calendar day becomes available.

Challenge the assumptions that create false liquidity

Assumptions should be explicit enough to challenge: collection timing by customer, supplier payment terms, payroll and tax dates, recurring direct debits, capex commitments, financing flows, minimum liquidity policy and available facility conditions. A 13-week cash flow forecast is not strengthened by adding detail whose timing cannot be evidenced.

The decision closes the week-2 gap and preserves the week-4 obligation

The action is selected because it is sufficient in the model, operationally identifiable and reversible if the counterparty refuses. It does not assume that all suppliers can be delayed or that the customer will pay merely because a message was received. The decision remains conditional on written agreement, refreshed evidence and the intrawweek cash path.

Operate the forecast as a rolling treasury control

Forecast accuracy should be measured at the level that improves decisions: whether named receipts and payments occurred in the predicted week, whether amounts differed, whether a date change was identified before the payment decision and whether the buffer exception was prevented. A small total variance can still conceal offsetting errors that would have produced an unsafe payment sequence.

The operating rule is straightforward: preserve every displaced cash flow, roll every effect through the full horizon and escalate any week whose apparent safety depends on uncertain timing. The forecast earns its value when management can decide not only what to pay, but when the organisation can pay it without losing control of liquidity.