The 13-week cash flow forecast, built properly

Why thirteen weeks

Thirteen weeks is one quarter, and the horizon is chosen for a specific reason: it is long enough that you can still act — collect a receivable, delay a capex, renegotiate terms, arrange a facility — and short enough that the underlying detail is knowable rather than estimated.

Beyond thirteen weeks, weekly precision becomes false precision. Inside four weeks, you have visibility but very little room to change the outcome. The quarter is the window where forecasting and action overlap.

Bottom-up, not trend

The most common mistake is building the forecast from historical patterns — last quarter's receipts divided by thirteen, adjusted for growth. That produces a smooth line that has almost nothing to do with what will actually happen, because cash is lumpy and timing is everything.

A bottom-up forecast is built from named items: this customer, this invoice, this expected week. It takes longer to build the first time and it is the only version that is useful.

Building the receipts side

Start from the receivables ledger, invoice by invoice, and place each one in the week you actually expect it — not the week it is contractually due.

The distinction matters enormously. A customer on 30-day terms who has paid at 52 days for the last eight invoices will pay at around 52 days for the next one. Forecasting them at 30 is not optimism, it is an error. Build a payment behaviour profile per significant customer from actual history and apply that.

Then add:

• New sales expected to be invoiced and collected inside the window, at realistic conversion and realistic terms.
• Cash sales, weighted by the day-of-week and seasonal pattern if you are in retail or F&B.
• Any VAT refunds due, financing drawdowns, asset disposals or shareholder injections.

Be conservative on the receipts side. Optimism here is the single most common reason a forecast fails to warn anyone in time.

Building the payments side

Payments are more knowable than receipts, which is why the payments side should be close to exact.

• Payables ledger: every open supplier invoice placed in its scheduled payment run.
• Payroll: known amounts on known dates, including any variable pay and end-of-service settlements you can anticipate.
• Rent and lease payments: the actual cheque dates, which in the UAE are typically annual, quarterly or in a small number of instalments rather than monthly.
• Loan repayments and finance leases: from the amortisation schedule.
• Tax: VAT payment dates and any Corporate Tax liability, discussed below.
• Committed capex: anything already ordered or contracted.
• Recurring overhead: utilities, insurance, subscriptions, licence renewals.

The UAE-specific items that break forecasts

Three items cause more UAE cash surprises than anything else, and all three are entirely predictable.

Annual rent cheques. Most UAE commercial leases are paid annually or in one to four cheques. A business that thinks of rent as a monthly cost in the P&L can be caught by a single payment representing a quarter of its annual occupancy cost. It has a date. Put it in.

Corporate Tax. The liability is payable nine months after the tax period ends. For a business that has never paid it before, it is a new outflow of unfamiliar size. It should be provisioned monthly through the year and modelled as a scheduled payment, not discovered in month nine.

Trade licence and visa renewals. Annual, clustered, and frequently forgotten because they sit outside the normal supplier cycle.

Running it weekly

The forecast is not a document, it is a routine. Every week:

1. Roll the window forward one week and drop the week that has passed.
2. Enter actuals for the completed week and compare them to what you forecast.
3. Explain the variance. This is the step that makes the forecast improve — an unexplained variance repeats.
4. Update expected receipt dates based on what customers actually did.
5. Check the minimum balance across the window against your agreed buffer.
6. If the buffer is breached at any point, decide the action this week rather than in the week it happens.

Fifteen to thirty minutes once the model exists. The discipline is worth more than the sophistication.

Stress testing

Run three scenarios, and take the downside seriously:

• Base: your realistic expectation.
• Downside: your largest customer pays 30 days late, sales fall 15 percent, and one supplier withdraws credit terms. This combination is not implausible — it is a normal bad quarter.
• Severe: whatever the specific existential risk is for your business — losing the anchor customer, a lease renewal at a much higher rate, a licence delay.

Knowing where the breaking point is converts a future crisis into a present plan. Businesses that have modelled the downside act two months earlier than businesses that have not, and two months is usually the difference between renegotiating from strength and renegotiating from desperation.