Advanced liquidity planning: The next step in treasury forecasting

Most treasury teams can tell you where cash is today. That is important, but it is usually not the question that creates pressure.

The pressure starts when the business asks treasury to go one step further, not just to report expected cash, but to show how that forecast is built and what changes when assumptions move.

If you have ever rebuilt the same forecast multiple times in a week because assumptions kept changing, you already know the problem.

Treasury does not struggle because there is no forecast. Treasury struggles because the process behind the forecast is often too manual, too fragmented, and too hard to adapt when the next question comes.

The gap between visibility and decision-making

Treasury teams have made a lot of progress in cash visibility. They have better bank connectivity, stronger control over positions and payments, and more discipline around forecasting than they did a few years ago.

But visibility is not the same thing as decision support.

Today, treasury is being asked to help answer harder questions. If production increases, what does that do to working capital? If payment timing changes across a few large customers, what does that mean for liquidity next quarter? If a refinancing moves out, is there enough headroom?

Those are not simple reporting questions. They are scenario questions. And in a lot of organizations, that is exactly where the process starts to break down.

The issue is not forecasting, it is scenario planning

Most teams already have some kind of forecast in place. The real issue is how hard it is to adjust that forecast when the business changes.

A CFO asks for a downside case. FP&A updates revenue assumptions, and treasury needs to understand the cash impact. In some cases, that starts with the indirect method, using high-level planning inputs like revenue and expense changes to translate P&L assumptions into expected liquidity outcomes. In others, treasury needs the direct method, starting with source transactions like invoices and applying rules for payment terms, tax, business calendars, and payment cycles to model when cash will actually move.

Together, these approaches help treasury answer different versions of the same question. The indirect method helps connect FP&A plans to cash. The direct method adds transaction-level precision, so teams can better understand timing, liquidity risk, and whether funding capacity may need to be part of the answer.

What we wanted to solve

When we built Advanced Liquidity Planning, the goal was not to add another forecasting screen. It was to make liquidity planning more usable when assumptions change.

At the center of it is the Unified Worksheet, which brings together bank actuals, committed transactions, short-term forecasts, long-term planning inputs, invoices, subledger data, open orders, planned capex, and FP&A assumptions in one place.

That matters because treasury should not have to piece the liquidity story together across multiple disconnected files and systems.

From there, teams can start with a base plan and apply scenario overlays by amount, percentage, or period. They can compare outcomes side by side without rebuilding the whole forecast each time. They can also model the drivers that usually matter most, things like revenue changes, payment terms, DSO, DPO, seasonality, tax events, billing cycles, prepayments, and deferrals.

That is the difference.

Cash management helps treasury understand where cash is and manage daily liquidity. Liquidity Planning helps treasury forecast. Advanced Liquidity Planning helps treasury test assumptions and see what those changes mean for the business.

It is about liquidity, not just balances

One of the clearest themes in customer conversations is that cash, debt, and liquidity are not managed as separate ideas in the real world.

One finance leader said it simply: debt management, cash management, and liquidity management are “all kind of one thing.” That is a pretty good way to put it.

If treasury is evaluating a funding decision or a stress case, projected cash alone is not enough. The question is broader. What is total liquidity capacity? How much flexibility is really available? That is why Advanced Liquidity Planning goes beyond projected balances to help treasury look at available credit, debt capacity, and overall liquidity in context.

Where this is headed

I also think treasury planning is about to change again.

The next step is not just faster reporting. It is smarter forecasting.

With Agentic AI forecasting, the opportunity is to reduce the manual work that slows treasury down today. Teams should be able to identify drivers faster, spot unusual movements earlier, and test scenarios without starting from scratch every time.

A simple example is this: imagine asking for the liquidity impact of a 10 percent drop in revenue and a 15-day extension in collections, then getting a scenario model back in seconds instead of spending hours building it. That is the direction this is going.

That does not remove judgment from treasury. If anything, it makes judgment more valuable, because less time is spent assembling the forecast and more time is spent deciding what to do next.

Why this matters now

Treasury is being asked to do more than report numbers. It is being asked to help the business make decisions with confidence.

That is what Advanced Liquidity Planning is for. It builds on the cash management and liquidity planning foundation many teams already have, and it gives them a more practical way to model change, understand liquidity impact, and answer the next question.

That is where treasury becomes even more valuable to the CFO and the business.

See Advanced Liquidity Planning in action at KyribaLive, or contact us to learn how Kyriba can help modernize your liquidity management.