Thirteen Mondays of Cash
A cash forecast nobody trusts is a spreadsheet somebody rebuilt last month. Ours is read off the documents already in the books, week by week for thirteen Mondays, and every figure opens to the invoices and bills behind it.
It is the second Monday of the month at a building-materials distributor on Mombasa Road. The finance manager has KES 2.1 million across two bank accounts and an M-Pesa till float, payroll of KES 1.38 million due at month end, a cement supplier who wants KES 900,000 on the 22nd, and a county contractor who owes KES 1.6 million and has paid every invoice this year about five weeks late. The question from the director is short: do we need the overdraft this month, and if so, which week?
The short version
The 13-week cash forecast under Accounting starts from today’s cash and bank balance in the ledger and places every open invoice, bill, purchase order, payroll run, unpaid expense, VAT and withholding liability and recurring journal in the week it is expected. It shows the running balance, the lowest week, and every week that falls under the threshold you set. A scenario moves receipts later, collects only part of them, delays supplier payments or adds a one-off, and shows the result beside the base forecast, built from the same documents.
Where the numbers come from
Most cash forecasts in East African SMEs are a spreadsheet with a row per supplier and a column per week, rebuilt from the ageing report whenever someone has time. The rebuilding is the problem: by the time the sheet is finished, two invoices have been paid and a purchase order has been raised that it never heard about. Our forecast has no rows of its own. It reads what is already in the books, every time the page opens.
| Line | Read from | Placed in the week of |
|---|---|---|
| Customer invoices | Open invoices with a balance | The due date, or the due date moved by that customer’s own payment history |
| Scheduled invoices | Active recurring invoice schedules | Each run date in the horizon |
| Supplier bills | Payable bills | The due date |
| Open purchase orders | Issued orders not yet fully billed | Expected delivery plus the supplier’s usual terms |
| Payroll | Unpaid runs, then the last regular run repeated | Month end for net pay, the 9th after for deductions |
| Unpaid expenses | Approved expenses not yet paid | Their date |
| VAT and withholding | What the ledger says you owe | The 20th of the month after it arose |
| Recurring journals | Active schedules that touch a cash account | Each run date |
Week 1 starts on this week’s Monday. An invoice that was due three weeks ago is not left in the past: it is still owed, the earliest it can arrive is now, so it lands in week 1. A document expected after week 13 is outside the horizon and is left out rather than piled into the last column. The assumptions are printed under the grid, in plain words, so nobody has to guess why a payroll figure appears on the 30th.
Supplier terms are learned, not typed
An open purchase order has no due date yet. The forecast takes its expected delivery date and adds that supplier’s usual terms, worked out as the median gap between bill date and due date across its bills of the last two years. A supplier you have never been billed by gets thirty days.
The customer who always pays late
The county contractor’s invoices are due in thirty days and arrive in sixty-five. A forecast that trusts the due date tells the finance manager the KES 1.6 million lands in week 2, and it is wrong in the same direction every month. Switch on payment history and each customer’s receipts move by their own average days late, measured between due date and final payment on invoices settled in the last year. It needs two settled invoices before it moves anything, because one is an anecdote. A customer who pays early moves the other way. The forecast measures the lateness; receivables and collections in Kenya covers what usually causes it and how to shorten it.
The Mombasa Road distributor, week by week
The county contractor’s KES 1.6 million, moved by its own payment history, lands in week 6 instead of week 2. Without the history switch the grid shows no low point at all.
Every cell opens. Click week 4’s payroll figure and the run behind it is listed; click week 3’s supplier bills and you see the bill, the supplier and the date it was placed on. A number that cannot be opened is a number somebody has to defend in a meeting; one that opens is a number the meeting can check.
The useful number in a cash forecast is not the closing balance. It is the lowest week, and the date it falls on.
A threshold, and the weeks under it
The forecast settings hold a low-cash threshold. Leave it empty and the line is zero. Set it to the overdraft limit, or to the minimum balance the bank covenant asks for, and every week whose closing balance falls below it is marked. The low point is shown above the grid with its week and amount, so the answer to the director’s question is on the first screen rather than in column eleven.
Scenarios: the same documents, seen two ways
A scenario is a saved list of adjustments, applied to a copy of the forecast’s documents, never to the documents themselves. That is the design choice that matters: the base and the scenario are always the same invoices and bills, so the difference between them is exactly the assumptions you changed.
-
Move receipts by N days
For every customer, or one. An overdue invoice is moved from today, not from a date already past.
-
Collect only part of receipts
A percentage not collected, for every customer or one: the county pays 80% and argues about the rest.
-
Delay supplier payments by N days
For every supplier or one: the cement supplier agrees to fourteen more days.
-
Add a one-off inflow or outflow
A dated amount with a label: the loan drawdown, the generator you have to replace.
Saved scenarios are listed on the page, described in plain sentences such as “Receipts from Coast Works Ltd move 30 days”, and shown as a second set of figures beside the base. The finance manager can carry “County pays 45 days late” and “Cement supplier gives 14 days” into the director’s meeting and show both, with the week 4 hole closing in one and not the other.
One currency at a time
The forecast is shown in the base currency by default. A business with a dollar account picks USD and sees the dollar account’s balance and the dollar invoices and bills, and nothing converted. Adding shillings to dollars at today’s rate produces a number that is true for nobody, so the page does not do it. If you want to know how forecasting fits into wider cash planning, we covered the method in cash flow forecasting for Kenyan SMEs.
Reading the forecast needs the accounting view permission; changing the threshold, the history switch and the scenarios needs its own permission, so a finance assistant can look without rewriting the assumptions. The same forecast, scenarios included, is in the mobile app and the API, and the grid exports to CSV for the board pack. More on the screen itself on the cash flow forecast page.
A forecast shaped to how your treasury works
The thirteen-week grid, payment history, the threshold, scenarios, CSV, app and API are in place. These are the extensions finance teams ask for once they use it every Monday.
A forecast per bank account
Each account’s own running balance, for businesses that pay suppliers from one bank and collect into another.
A daily view of the next two weeks
The same documents by day, for the fortnight when the payroll date and the VAT date sit three days apart.
An alert when a week drops below the line
A note to the finance manager the morning a new bill or a slipped receipt pushes a week under the threshold.
Forecast against actual
Last quarter’s forecast laid beside what the bank actually did, week by week, so the assumptions can be tuned.
What AWRA OpsHub does today
- A rolling 13-week forecast from today’s cash and bank balance, with week 1 on this week’s Monday.
- Inflows and outflows read from the books: open invoices, recurring invoice schedules, supplier bills, open purchase orders, payroll, unpaid expenses, VAT and withholding, recurring journals.
- Customer payment history, moving each customer’s receipts by their own average days late over the last year.
- A low-cash threshold with the lowest week and every week under it marked.
- Saved scenarios that move receipts, collect part of them, delay supplier payments or add one-offs, shown beside the base.
- Every cell opens to its documents, with CSV export, the mobile app and the API reading the same forecast.
More we can add to your workspace
- A forecast per bank account, beside the combined cash position used today. Commission it
- A daily view of the first two weeks. Commission it
- An alert when a week falls under the threshold, sent as the forecast changes. Commission it
- Loan repayment schedules placed in the forecast from the loan terms. Commission it
- A forecast-against-actual report for past quarters. Commission it
- A converted total across currencies, shown beside the per-currency forecasts. Commission it
Where we point you to a specialist
- A forecast is an estimate built from your own documents and your own assumptions. Whether to draw on a facility or delay a supplier is a decision for your finance team and your bank, and the grid is the evidence for it, not the answer.
The per-account forecast is the extension asked for most, because the documents already know which bank they settle through.
Three questions for whoever owns your cash forecast
Which week is our lowest, and by how much?
What you will probably hear
Let me update the sheet first.
How to read it
Then the forecast is a project, not a view. It should be current the moment you open it.
Does it know the county pays five weeks late?
What you will probably hear
We put the due date in.
How to read it
Then the same receipt is forecast wrong every month, in the same direction.
What happens if the cement supplier gives us fourteen days?
What you will probably hear
I would need a copy of the sheet.
How to read it
A scenario should change assumptions, not documents, and sit beside the base.
See the cash flow forecast
Thirteen weeks from today’s cash, built from your invoices, bills, orders and payroll, with scenarios beside it.
Explore the cash forecastFrequently asked questions
Where does the opening balance of the cash forecast come from?
From the ledger balance of your cash and bank accounts today, the same accounts the cash-flow statement treats as cash.
What happens to an invoice that is already overdue?
It is placed in week 1. It is still owed and the earliest it can arrive is now, so it is not left in the past or dropped.
Does a scenario change my invoices or bills?
No. A scenario is applied to a copy of the forecast’s documents and shown beside the base forecast. Nothing in the books is edited.
How are open purchase orders placed?
At the expected delivery date plus the supplier’s usual terms, learned from the median gap between bill date and due date on its bills over the last two years, or thirty days when there is no history.
Can I see the forecast on my phone?
Yes. The mobile app and the API read the same forecast and saved scenarios as the web page.