A business can be profitable and still fail to pay salaries at the end of the month. That sentence confuses a lot of owners the first time they hear it, but it is one of the most common reasons Kenyan SMEs get into trouble: the income statement says one thing, the bank balance says another, and the bank balance is the one that actually pays people. Profit is an accounting opinion about a period of time. Cash is a fact about what is in your account right now. Forecasting cashflow is simply the discipline of knowing, ahead of time, whether that fact is going to be a problem.
Here is the distinction in practice. Say you land a KES 800,000 contract with a large corporate client, delivered in July, invoiced in July, on their standard 60-day payment terms. Your books will show that sale as July revenue, and if your margins are healthy, July looks like a great month on paper. But the cash from that invoice will not land until September, if it lands on time at all. Meanwhile your July payroll, rent, and supplier bills are due in July, in cash, regardless of what your income statement says. A business can post its best month ever and still bounce a payroll run in the same thirty days. That gap between "profitable" and "liquid" is exactly what a cashflow forecast is built to catch before it catches you.
The 30-60-90 day horizon, and why each window answers a different question
A cashflow forecast is not one number — it is a set of answers at different distances, because the decisions you make at each distance are different.
30 days: can we cover what's already committed
This is the operational window. The questions here are immediate and specific: will we have enough to run payroll on the 28th? Do we need to call a particular debtor this week because their payment is the difference between a comfortable month and a tight one? Should we hold off on paying a supplier three days to let a client's payment clear first? At 30 days you are managing real, dated obligations against real, dated inflows — there is little room for guesswork because most of the numbers are already known.
60 days: near-term planning and financing decisions
At 60 days you're deciding whether to change course. Should you delay a piece of equipment you were planning to buy? Do you need to arrange a short-term overdraft or asset finance now, while you still have time to negotiate terms, rather than scrambling once the gap is already on top of you? This is where a forecast earns its keep — it gives you enough lead time to act like it was planned, not like it was an emergency.
90 days: the strategic calls
Ninety days out, the questions get bigger: can we afford to hire a fourth salesperson? Can we commit to a two-year lease on a bigger space? These are decisions that change your fixed cost base, and they deserve a longer runway of visibility before you commit, because unwinding a hire or a lease is far more painful than unwinding a purchase order.
Building the forecast: what actually goes in it
A forecast is only as good as the honesty of its inputs. Two categories, inflows and outflows, but the detail inside each is where most forecasts either become useful or become fiction.
Inflows
- Confirmed sales already invoiced — money you are owed for work already delivered.
- Likely sales in the pipeline — quotes that are highly likely to close within the forecast window, weighted down if you're not certain.
- Debtor collections, by realistic payment date — not invoice due date. This is the single biggest source of forecast error for Kenyan SMEs. If a client's terms say 30 days but their actual historical payment pattern is 45-50 days, your forecast should say 45-50 days. Look at each major debtor's real payment history over the last two or three invoices and use that, not the polite fiction printed on the invoice.
- Any other cash in — asset sales, loan disbursements, owner injections.
Outflows
- Payroll — including the exact dates it hits the account, not just the monthly total.
- Rent and utilities.
- Statutory deductions — PAYE, NSSF, and SHIF (formerly NHIF), with their specific remittance deadlines. These are non-negotiable and penalised if late, so they belong in the forecast with hard dates, not lumped into "expenses."
- Loan repayments — instalment amount and date, every time.
- Supplier payments — again by when you actually plan to pay, which may be later than the invoice date if you're managing your own payment terms.
- Recurring subscriptions and fixed commitments — software, insurance, security, anything that debits automatically whether or not the month was good.
The template: a weekly rolling forecast
Monthly forecasts hide too much — a business can look fine for the month and still miss payroll in week two. A weekly rolling view, updated every week and always looking about six to twelve weeks ahead, is the practical version of the 30-60-90 idea. Here is the structure:
| Line item | This week | Next week | Week 3 | Week 4 |
|---|---|---|---|---|
| Opening cash balance | 420,000 | 385,000 | 310,000 | 465,000 |
| Inflows | ||||
| Confirmed invoice collections | 150,000 | 90,000 | 320,000 | 60,000 |
| Likely debtor payments (weighted) | 40,000 | 60,000 | 50,000 | 80,000 |
| Cash sales | 65,000 | 65,000 | 65,000 | 65,000 |
| Total inflows | 255,000 | 215,000 | 435,000 | 205,000 |
| Outflows | ||||
| Payroll | 0 | 210,000 | 0 | 0 |
| Rent | 0 | 0 | 80,000 | 0 |
| PAYE / NSSF / SHIF | 0 | 45,000 | 0 | 0 |
| Loan repayment | 35,000 | 35,000 | 35,000 | 35,000 |
| Supplier payments | 180,000 | 0 | 110,000 | 90,000 |
| Subscriptions & recurring | 75,000 | 0 | 55,000 | 0 |
| Total outflows | 290,000 | 290,000 | 280,000 | 125,000 |
| Closing cash balance | 385,000 | 310,000 | 465,000 | 545,000 |
Notice week 2's closing balance: even though inflows for that week are lower than average, payroll plus statutory deductions land in the same seven days, so the buffer drops. That is exactly the kind of squeeze a monthly view would smooth over and hide. Each week's closing balance becomes next week's opening balance, and the whole sheet rolls forward — every Monday you drop the week that just passed, add a new week at the end, and correct the numbers you estimated last time based on what actually happened.
Plan for best case and worst case, not just the expected case
The single forecast above is your base case — your honest best guess. But you should also build two quick variants:
- Worst case: your largest debtor pays two weeks later than expected, and one sale currently in the pipeline falls through entirely. Run the same table with those two changes and see where the closing balance goes negative, if it does. That tells you exactly which week you need a contingency for and how much that contingency needs to be.
- Best case: the pipeline sale closes on time and a slow-paying debtor settles early. This tells you the upside, which matters when you're deciding whether you can afford to say yes to an opportunity that needs cash committed up front.
You don't need to build these every week in full detail — but running them once a month, and re-running the worst case any time one debtor represents a large share of expected inflows, will save you from being blindsided by the single most common cashflow killer: one client not paying when you assumed they would.
Review it weekly, or it's just a document
A forecast built once and filed away is worthless within two weeks, because reality diverges from any prediction almost immediately. The habit that makes this tool work is a short weekly review, ideally the same day and time every week: pull up last week's forecast column, compare it to what actually happened in the bank statement, and note where you were wrong and why. Did a debtor pay on time for once? Did a supplier payment slip? Roll those actuals into the current week's opening balance and adjust your assumptions for the next 30 days — if a debtor has now paid late twice in a row, stop forecasting them at their invoice terms and start forecasting them at their real behaviour. This should take fifteen minutes, not an afternoon. The value isn't a perfect prediction; it's catching the gap between plan and reality every seven days instead of every ninety.
Red flags to watch for
- A shrinking cash buffer over several consecutive weeks — even if each individual week looks explainable, a trend across four or five weeks where the closing balance is steadily lower than the week before is the earliest warning sign you'll get, and it shows up in the forecast long before it shows up as an actual crisis.
- Growing concentration in one or two large debtors. If a single client's payment is now the difference between a comfortable forecast and a negative one, you don't have a cashflow forecast problem, you have a customer concentration problem, and the fix is either diversifying who you sell to or renegotiating that client's terms — not just hoping they pay on time.
- Outflows that consistently outpace inflows while the business "feels busy." Being busy and being cash-generative are not the same thing. If your team is stretched, your calendar is full, and your bank balance is still drifting downward month over month, the forecast is telling you something your workload isn't — usually that your payment terms, pricing, or collections process need to change, not your effort level.
None of this requires accounting software or a finance degree — a spreadsheet, an honest look at how your debtors actually pay versus how their invoices say they should pay, and fifteen minutes every Monday morning is enough to turn cashflow from something that happens to you into something you see coming three weeks out. Build the sheet this week, even roughly, and start the Monday habit before your next payroll run rather than after a close call.
Tagged under
Related Articles
VAT in Kenya for SMEs: Practical Rules You Can Apply This Week
Understand VAT registration, filing cadence, and common mistakes that create penalties for...
NSSF Remittance Best Practices for Growing Kenyan Businesses
Build a repeatable NSSF process that reduces errors and avoids costly compliance gaps.
M-Pesa Charges and Pricing Strategy: Protect Margin Without Losing Customers
Use transaction data to tune prices and decide when to absorb or pass payment costs.