A company can spend hours building a cash flow forecast, carefully checking its formulas and pulling together information from several areas. And a few days later, actual liquidity can look very different from what was expected.
Why does that happen? Rarely because of a calculation error. Deviations usually stem from the information that was used, the assumptions about how the business behaves, or events that weren't factored in on time.
Understanding those causes matters, because a cash flow forecast shouldn't just be a report: it has to help anticipate funding needs and support decisions. This article goes deeper into what's covered in Liquidity forecasting.
1. A forecast with correct math can give the wrong answer
Picture a company that starts the month with 4,000 million available. Its treasury expects collections of 8,000 million and payments of 9,000 million, so it forecasts ending the period with 3,000 million.
During the month, however, it only collects 5,000 million and has to pay 10,000 million.
| Item (millions) | Forecast | Actual |
|---|---|---|
| Opening balance | 4,000 | 4,000 |
| Collections | 8,000 | 5,000 |
| Payments | 9,000 | 10,000 |
| Closing position, before additional financing | 3,000 | −1,000 |
The gap is 4,000 million. Instead of ending with a surplus, the company needs 1,000 million of financing to meet its commitments.
The math in the original forecast was right. What failed were the estimates of collections and payments. It's a fundamental distinction: arithmetic accuracy doesn't make a forecast reliable.
2. First cause: incomplete or outdated information
A forecast draws on many areas. Sales provides expected collections, purchasing the commitments to suppliers, treasury the debt obligations, and other areas project investments, taxes and expenses.
The problem appears when that information arrives incomplete, stale or built on different criteria. One area may report a payment as scheduled for next month when the contract requires it this week. Another may project collections from invoices issued, without considering how its customers actually pay.
When those differences pile up, the result can look reasonable and still fail to reflect real liquidity needs. That's why a good forecast requires consistent criteria for dates, amounts and conditions, and owners who keep each figure up to date, which is what collaborative cash planning addresses.
3. Second cause: mistaking what's expected for what's available
A sale made isn't a collection received, and an invoice issued doesn't guarantee the money will arrive on the expected date. Commercial terms set deadlines, but customers behave their own way: some pay early, some on time and some are late again and again.
If a company forecasts collections using only contract dates, it may overestimate liquidity in certain periods. The same goes for payments: the accounting date, the contractual date and the actual payment date don't always match.
To forecast liquidity, what matters is when the money is actually expected to move. And that requires understanding how the company operates, not just its accounting records.
4. Third cause: assumptions that no longer reflect reality
Every forecast carries assumptions: that sales will grow at a certain pace, that customers will keep their payment habits, that disbursements will follow past patterns. They may be reasonable when the forecast is made, but conditions change. A drop in sales, a new contract, an unexpected cost increase or a change in loan terms can significantly alter the expected flows.
Using assumptions isn't the problem, since every forecast needs them. The problem is keeping them unreviewed when the information already shows they no longer hold. A forecast has to evolve with the business.
5. Fourth cause: ignoring restrictions on funds
Not all the money sitting in accounts and investments can be used for any payment. Some funds are pledged as collateral, earmarked for a specific purpose or subject to redemption conditions.
There can also be restrictions on moving cash between several companies in the same organization, especially when they operate in different countries or under different rules. A forecast that adds up every balance without considering these conditions shows more availability than can actually be used.
That's why liquidity management has to tell apart funds that exist from funds that can be used: the available, restricted and invested parts of the cash position. The difference matters even more when managing several companies, currencies, accounts and portfolios, as in multi-entity treasury.
6. Fifth cause: not systematically comparing forecast with actual
A key practice for improving forecasts is comparing past forecasts with what actually happened, starting with reconciling the statement against the forecast. That exercise reveals deviations and helps explain their causes. But knowing the total difference isn't enough.
Suppose a treasury forecasts collections of 20,000 million and collects exactly that. At first glance, the forecast was perfect. Looking at the detail, however, it finds that some customers paid 5,000 million less than expected and others 5,000 million more. The total matches, but the individual estimates had significant errors that offset each other, and those errors will repeat in future forecasts.
That's why assessing a forecast means looking at both the overall result and its components, dates and main sources of uncertainty: separating collections from payments and breaking it down by category, as measuring forecast accuracy does. Getting the total right doesn't always mean the estimates were reliable.
7. Sixth cause: treating the forecast as a static document
In many organizations, the forecast is built every so often and stays unchanged until the next cycle. Liquidity, however, changes every day: actual collections, investment decisions, maturities and new commitments all shift what was expected. A forecast from two weeks ago may have lost much of its usefulness, even if it was reasonable when it was made.
How often to update depends on each company, the volatility of its flows and the horizon it looks at. A useful practice is the rolling forecast, which takes in actual results and extends the horizon as time passes. That keeps the organization's view of its needs current, which is how a day-by-day cash flow forecast works.
8. Seventh cause: relying on a single scenario
A forecast represents what the company expects to happen under certain assumptions. What if they don't hold? A treasury might anticipate a sizable surplus and invest funds it will later need to make payments.
The risk grows when scenarios aren't assessed. Besides the central forecast, it pays to look at adverse and favorable situations:
- What happens if collections drop?
- How does liquidity change if certain payments come forward?
- What financing would be needed if an investment can't be liquidated on the expected date?
Scenarios don't remove uncertainty, but they make its consequences clear and let you prepare decisions before the problem shows up, which is the work of liquidity risk.
9. The cost of spotting a deviation too late
When a company discovers a shortfall shortly before it has to pay, it has fewer options left: emergency financing, investments sold on poor terms or higher financing costs. When it spots it early, it can weigh its options and choose the best one.
The difference doesn't depend only on getting the initial forecast right, but on detecting changes in time, understanding their causes and responding.
A deviation spotted in time becomes a decision. A deviation discovered too late becomes an emergency.
10. How to make forecasts more reliable
Improving a cash flow forecast doesn't necessarily require more complex mathematical models. The biggest gains usually come from getting the information in order and bringing discipline to the process:
- Define who owns each piece of data.
- Use consistent criteria to estimate dates and amounts.
- Revisit assumptions when conditions change.
- Identify restrictions on funds.
- Regularly compare estimates with actual results.
It also helps to keep the history of your forecasts. If every update fully replaces the previous one, it's hard to know what changed and to judge how good the forecasts were. That's why it makes sense to keep a snapshot of each version and measure against it.
Technology can make all of this easier by integrating information, automating tasks and analyzing deviations. No tool, however, replaces knowledge of the business or the judgment of the people who decide.
11. The real goal: forecasting to decide
A cash flow forecast is useful when it lets you understand the likely path of liquidity and act on it. It shouldn't be judged only by its ability to hit future numbers, but also by the timeliness and quality of the decisions it enables.
Treasury needs to know how much money it expects to have, but also which movements explain that result, how much uncertainty there is and what alternatives it has if conditions change. That means moving from building periodic forecasts to keeping a continuous understanding of funds and how they may move.
The biggest risk isn't always that the forecast is wrong, but that the organization keeps making decisions as if it were still right.
FLIQO: intelligence to anticipate and understand liquidity
Treasury decisions need information that is reliable, current and understandable.
FLIQO is an operational liquidity intelligence platform: it anticipates the path of cash with figures that are explainable and auditable, and strengthens treasury professionals' analysis by helping them understand the information behind their decisions.
Because anticipating liquidity isn't just looking at future numbers. It's understanding what could change them and being ready to act.
Anticipate liquidity. Understand the figures. Decide with confidence.
