For years we've assumed that Treasury is the natural home of organisational liquidity.
After all, Treasury manages cash, funding, foreign exchange exposure and financial risk.
So, if anyone should understand the organisation's future cash position, surely it's Treasury.
But I don't think that's actually true.
I think the organisation already knows far more about its future than Treasury can currently see.
Consider a typical business.
A salesperson closes a significant deal.
The contract moves to Legal.
- Legal negotiates payment terms, milestones and completion dates.
- Operations begin planning delivery.
- Procurement starts ordering materials.
- Human Resources recruit additional staff.
- Project managers allocate resources.
Long before a single invoice is raised, dozens of people are already making decisions that will eventually affect the organisation's cash position. But none of those decisions happened in Treasury.
Now consider the same process from Treasury's perspective.
Treasury sees today's bank balances.
Treasury sees today's incomings.
Treasury sees today's outgoings.
Treasury may also see today's outstanding receivables and payables.
But much of the information that will determine cash over the coming weeks and months still exists elsewhere.
The organisation already knows about future financial commitments.
Treasury often doesn't. Not because anybody is withholding information, simply because the information was never intended to flow that way.
This isn't a technology problem, it's an architectural one.
Enterprise software has traditionally been organised around business functions.
Sales owns Sales.
Finance owns Finance.
Procurement owns Procurement.
HR owns HR.
Treasury owns Treasury.
Each department has software optimised for its own responsibilities.
Each system performs its own job exceptionally well, but future cash doesn't belong to a single department.
It emerges from the combined activities of all of them.
Take something as simple as a new customer contract.
The contract is signed today.
Treasury may not become aware of its financial implications until weeks later, when invoices begin to appear.
Yet the organisation already knew:
- how much the customer intended to buy;
- when delivery was expected;
- the agreed payment terms;
- the contract value;
- whether payments would be made in Sterling, Euros or Dollars;
- whether milestone payments had been agreed.
Those are all financially significant facts, yet they exist outside Treasury.
The same applies on the expenditure side.
A purchase order may be approved.
A supplier contract may be signed.
A major recruitment campaign may begin.
A property lease may be agreed.
Each creates future financial commitments, influences future liquidity, may create foreign exchange exposure. Each is known somewhere within the organisation.
Treasury often discovers them only when they become invoices or payment requests.
This raises the question.
Perhaps Treasury's challenge has never been forecasting, but visibility.
Most forecasting processes attempt to estimate future cash movements.
But many future cash movements are already known. The difficulty is that they're distributed across operational systems that were designed for entirely different purposes.
Imagine if Treasury could see those business events much earlier and understand their future financial consequences.
That changes the conversation. Treasury is no longer reacting to invoices. It is understanding business activity.
This distinction becomes even more important in multinational organisations.
One business unit signs a contract. Another delivers the service. A third issues the invoice.
Treasury manages the resulting cash.
Each department performs its own role.
Yet no single system naturally joins those events together into a single financial story.
The information already exists. The understanding often does not.
This isn't a criticism of ERP systems, Treasury Management Systems or accounting platforms. They were designed to execute business processes. The challenge we're now trying to solve is different.
It's about connecting financially significant events, regardless of which department created them.
When those events are viewed together, something interesting happens.
Sales activity becomes future revenue.
Contracts become future obligations.
Purchase orders become future expenditure.
Payroll changes become future cash requirements.
Business activity becomes financial understanding.
I suspect this is why liquidity forecasting remains difficult in so many organisations.
The challenge isn't that Treasury lacks expertise. Nor is it that organisations lack information.
The challenge is that the information which determines tomorrow's liquidity is created throughout the organisation, while Treasury is often only exposed to the financial consequences much later.
Perhaps the future of Treasury isn't seeing more reports, it's seeing more of the organisation.
The organisation already knows more about its financial future than Treasury can currently see.
The next generation of enterprise software will connect those insights before they become cash movements.
