Behind the Treasury Headlines: A Journalist’s View of 20 Years in Treasury  

💲 We simplify Corporate Treasury Concepts - 🎙️ From the podcast Corporate Treasury 101

Behind the Treasury Headlines: A Journalist’s View of 20 Years in Treasury  

Treasury teams face pressure to respond to disruption while maintaining a dependable view of cash, liquidity and risk. AI in treasury can appear to offer instant answers, yet faster information is of little value if it is incomplete or difficult to trust.

The challenge persists because the information treasury needs is often scattered across systems and business units. Commercial decisions may also be made before they reach the people responsible for forecasting and liquidity planning.

Ben Poole is a journalist, editor and interviewer specialising in corporate treasury and finance. He has covered the industry from a journalist’s perspective for 20 years, including 15 years as a freelance journalist.

The sections below break down how treasury teams can assess AI realistically, improve the information behind their decisions and communicate their contribution more clearly across the business.

AI in treasury starts with dependable information

Interest in AI is strong, particularly where it could improve cash flow forecasting. But the practical constraint is rarely the algorithm alone: reliable source data, connected systems and consistent operating inputs determine whether a forecast can support a decision.

Forecasting remains a live operational problem

The EACT annual survey referenced in the discussion found that cash flow forecasting was the first or second biggest concern for 52% of respondents. That persistence matters because forecasting remains an important treasury challenge, and teams need reliable information to plan around cash and liquidity.

Manual workarounds expose the underlying gap

The same survey found that 46% of treasurers still needed manual workarounds for areas such as long-term forecasting. Manual intervention may be necessary in some circumstances, but it also signals that data, systems or submissions have not yet formed a dependable end-to-end process.

Adoption is not the same as maturity

A PwC survey cited in the discussion found that 74% of treasurers were using or expanding AI, while only 26% considered their capabilities moderately or very mature. The gap suggests that teams should judge progress by the quality of their decision support, not by whether a tool has been introduced.

  • Check whether source data is complete before automating it.
  • Map where forecasting inputs enter from across the business.
  • Identify manual workarounds and the reason each one remains.
  • Assess whether existing systems can exchange the required data.

This checklist keeps the first conversation grounded in operating reality. It also helps distinguish a solvable data issue from a technology purchase that would merely automate an existing weakness.

The immediate priority is not to make every process more advanced. It is to establish a coherent information base that treasury can use with confidence when cash, liquidity or risk requires attention.

Use current data when decisions need it

Real-time reporting attracts substantial interest, but its purpose should be clearer decisions rather than permanent reaction. A treasury team needs a complete and reliable position at the point a decision is required, not an instruction to respond to every changing data point.

Demand for timely visibility is clear

The EACT survey identified real-time reporting and dashboards as highly important for 63% of respondents. Interest also extended to real-time liquidity, cited by 49%, and real-time payments and collections, cited by 41%.

Speed has a specific role in liquidity management

Timely information is especially useful when an unexpected payment creates an intraday liquidity shortfall. In that situation, the ability to see the position quickly can support a prompt response and reduce reliance on a stale view of available cash.

Some choices still require judgement

A funding or hedging decision may require discussion even when the data is current. Treating every update as a trigger for action can create noise; the more useful aim is information on demand that is current enough to act on and coherent enough to trust.

  • Define the decisions that genuinely need intraday information.
  • Test whether all relevant accounts update on a comparable basis.
  • Separate operational alerts from decisions requiring discussion.
  • Review whether a dashboard presents a complete position or a partial view.

The questions focus investment on moments where timeliness changes the outcome. They also guard against a misleading picture in which one data source is current while another remains out of date.

Real-time capability is valuable when it improves the quality and timing of a specific response. It should not displace the professional judgement needed for decisions with wider funding or risk implications.

Connect treasury to the business decisions it must support

Technology cannot compensate for information that never reaches treasury. The practical reader problem is often organisational: forecasting inputs sit across business units, and unrecorded commercial decisions can undermine a carefully built plan.

Business-unit consistency matters

Consistency in submissions from different business units is a key implementation challenge. If comparable inputs are supplied in different ways, treasury must spend time interpreting them before it can establish a usable view of cash flow.

Translate the purpose of treasury work

Technical language can obscure a straightforward business outcome. Colleagues outside the function are more likely to engage when a request is linked to available cash, better-managed risk or more confident decisions rather than specialist terminology alone.

Build relationships beyond finance

Treasury needs information from elsewhere in the organisation, so communication is an operating control as well as a visibility exercise. Clear relationships make it easier to surface changes early and clarify why a particular input matters to planning.

  • Agree which commercial events should be reported to treasury.
  • Use plain language to explain the effect on cash or risk.
  • Set consistent expectations for business-unit submissions.
  • Escalate material changes before they distort a forecast.

A simple shared routine can reduce avoidable surprises without adding unnecessary process. It gives operational colleagues a practical route to provide information before treasury has to discover it after the fact.

Treasury’s strategic role depends partly on how well it connects the organisation’s activity with its financial consequences. Better communication makes that connection visible and makes the resulting analysis more useful.

Pair experience, curiosity and clear communication

Treasury has become closer to strategic decision-making as liquidity, funding, currency risk and financial resilience have moved up the business agenda. That broader role requires technical capability, but it also requires people who can question established processes and explain their judgement clearly.

Experience supplies context under pressure

Professionals who have worked through periods when liquidity was under pressure or markets behaved unexpectedly bring judgement that cannot be replicated quickly. They can test whether an apparently efficient new approach accounts for the practical risks that emerge in a crisis.

New entrants can challenge routine

People entering treasury may be more comfortable with newer technology and more willing to ask why a process depends on a spreadsheet or takes several days. That questioning is useful when the culture allows a reasoned answer rather than treating routine as sufficient justification.

Capability includes the ability to explain

Projects are easier to evaluate when the original problem and the change achieved can be stated plainly. Clear communication also helps treasury demonstrate value to the CFO and the wider business after a successful project.

  • Learn the fundamentals of liquidity, funding and risk.
  • Ask how the organisation makes and spends money.
  • Question established processes without dismissing experience.
  • Test technology claims against a defined operational problem.

These habits bring technical learning, commercial awareness and constructive scepticism together. They also create a common language between experienced practitioners and colleagues who see the process with fresh eyes.

The strongest teams make room for both perspectives. Experience can sharpen new ideas, while curiosity can expose workarounds and assumptions that no longer serve the organisation.

Conclusion

AI in treasury is most useful when it strengthens a team’s ability to understand and act on its financial position. The technology should be assessed as part of the information, processes and judgement that support treasury decisions.

First, reliable inputs are essential. Incomplete data, disconnected systems and manual workarounds limit the value of even well-designed forecasting tools.

Second, timely reporting should serve a defined decision. Current data has particular value in an intraday liquidity event, while funding and hedging choices may still need discussion and professional judgement.

Third, treasury needs a stronger link with the rest of the organisation. Consistent business-unit inputs and plain-language communication improve forecasts while making treasury’s contribution easier to understand.

Start with the problem that needs solving, identify the information required and test whether a proposed tool changes the result. That disciplined approach gives AI in treasury a practical purpose rather than allowing innovation claims to set the agenda.

FAQs

Why is cash flow forecasting still difficult?

Forecasting depends on complete, timely and consistent inputs from systems and business units. The EACT annual survey found that manual workarounds remain common for long-term forecasting.

What is the first step for AI in treasury?

Start with a clearly defined operational problem and assess the source data behind it. A tool cannot create a dependable forecast from incomplete or disconnected inputs.

Does real-time data require real-time decisions?

No. Current information can be critical during an intraday liquidity shortfall, but funding and hedging decisions may still require discussion and judgement.

How can treasury improve information from business units?

Agree which commercial events need to be shared, set consistent submission expectations and explain the impact in plain business terms such as cash availability or risk.

What skills matter in a modern treasury team?

Useful capabilities include technical literacy, curiosity about established processes, commercial awareness, experience and the ability to communicate clearly with colleagues outside finance.

If you liked the article, why not spreading the Treasury word? :)

Leave a Reply

Your email address will not be published. Required fields are marked *

Receive your Free copy of "The Corporate Treasury eBook" :)