Most CFOs can tell you what their TMS costs. Licence fees, implementation, annual support, it is all on an invoice somewhere. What they cannot tell you is what their fragmented treasury infrastructure is actually costing them. Not because the number is small. Because it never appears anywhere that anyone is looking.
Fragmentation in treasury is not a technology problem. It is a financial problem hiding inside an operational one. When cash positioning lives in the TMS, FX exposure in a spreadsheet, bank data across five separate portals, and intercompany positions in a model someone built three years ago, the cost is real, it is just distributed across a hundred small inefficiencies that nobody ever adds up.
The cost you see is the smallest part of it
The visible cost is the time it takes. An analyst spending two hours a day reconciling data between systems that should already talk to each other is a cost you can calculate. Two hours a day across a treasury team of five is the equivalent of a full-time headcount doing work that should not exist.
But that is the cheap version of the problem. The expensive version is the decisions that get made on incomplete or delayed information. When the cash position is assembled manually, each morning, from four sources, it is always a few hours behind reality. When a CFO asks for an accurate group liquidity position and the answer takes until Thursday, the decisions that needed to be made on Monday got made without the right information. Those decisions have consequences that never show up in the technology budget. They show up in the P&L.
The risk dimension is the one that should concern people most. Fragmented systems mean fragmented controls. When data moves between systems manually, audit trails break. When positions live in spreadsheets, version control is a best-efforts exercise. A treasury function that cannot answer “what is our actual FX exposure right now” without a two-day process does not have an information problem. It has a governance problem.
The real cost is what treasury cannot do
A treasury function spending 60% of its time assembling information is not spending that time analysing it. It is not stress-testing liquidity scenarios, identifying cash optimisation opportunities, or giving the CFO the forward-looking insight needed to make better capital allocation decisions. Fragmented systems do not just make the treasury team slower — they make the whole function smaller than it should be.
What the solution actually looks like
The answer is not always buying new technology. Often, the TMS already in place is capable of far more than it is being used for. The problem is the integration gaps: the bank feeds that were never fully connected, the ERP linkage that was scoped out during implementation to hit a go-live deadline, the subsidiary entities that were added to the business and bolted onto the system landscape rather than properly integrated.
The starting point is an honest audit: map every source of data that feeds the treasury function and identify where manual intervention is filling the gaps between them. That audit almost always reveals that the cost of fixing the integration is a fraction of the cost of not fixing it.
From there, the priorities are clear. Consolidate bank connectivity so positions update automatically rather than manually. Complete the ERP integration, so cash flows are captured at source rather than reconciled after the fact. Retire the spreadsheets not by mandate but by making the system reliable enough that the team stops needing them.
None of this is complicated in principle. What it requires is treating the existing technology investment as unfinished rather than complete and allocating the time and resources to finish it properly.
