01
Treasury transformation has become a buzzword
A Treasury Management System replacement is called a transformation. Automation becomes transformation. A new forecasting tool, payment platform or organisational structure can all acquire the label.
These may be important changes. They are not necessarily transformation. The term is often used without a clear account of what is being transformed, why the change is needed or what outcome matters. Calling every significant Treasury project a transformation strips the word of meaning.
Organisational-change research has long made a similar distinction. Bartunek and Moch distinguish first-order change, which improves within an existing frame, from second-order change, which changes the frame itself. Levy and Merry likewise treat organisational transformation as second-order change. Applied to Treasury, improving a process or replacing a system may be significant change; transformation requires a material change in Treasury capability or in the way the operating model works.
The distinction does not depend simply on investment, duration or the number of projects. It depends on whether the changes form a deliberate response to a material change in what the organisation requires from Treasury and produce a different Treasury capability. That relationship is line of sight.
There is already a lot of research and commentary on transformation. This paper draws that work together with practical Treasury experience and sets out TRC's distilled view of what Treasury transformation is — and what it is not.
Some organisations describe any major technical or operational programme as transformation. TRC uses the term more narrowly. A technology programme, however large, is not a transformation in its own right. It becomes part of a transformation only when it contributes to the connected set of initiatives required to meet the original business ask and deliver the Treasury capability the organisation now needs. More recent digital-transformation research points in the same direction: technology impact or adaptation in one part of an organisation is distinct from a systemic organisational shift.[1][2][18][19][21]
02
The reason begins above Treasury
Before asking what Treasury needs to change, ask why the organisation needs Treasury to be different. The answer might be growth, acquisition, international expansion, refinancing, increased financial risk, resilience, cost pressure, regulation or a different business model.
The original objective may have little to do with Treasury, but it can create significant Treasury consequences. International expansion may introduce currencies, entities, banking relationships, liquidity requirements and financial risks. An acquisition may create additional systems, bank accounts and funding requirements.
Treasury may own the transformation. It does not necessarily originate the reason for it. The important principle is not a particular hierarchy; it is that the Treasury response remains traceable to what the organisation is trying to achieve.[3][4]
03
The Treasury requirement is the source
Consider an organisation planning significant international growth. Treasury may need stronger cash visibility, scalable funding, consistent banking structures, controlled foreign-exchange risk and resilient payments.
The growth objective is not the transformation. It is the reason Treasury needs to become different. The transformation is the coordinated redesign undertaken in response.
A material regulatory change may create a different but equally valid requirement. Treasury may need new reporting, controls, liquidity buffers or risk-management capability even when the organisation's commercial strategy has not changed.
Visible problems often create urgency: a Treasury system that is no longer supported, a manual process or unreliable forecasting. These are triggers. They explain why action is required now, but they do not define the outcome. Moving directly from the immediate problem to a preferred solution breaks line of sight before the programme has properly begun.[5][10]
04
Required capability comes before the solution
The Treasury requirement explains why Treasury needs to change. Required Treasury capability describes what it must become able to do.
For international growth, that may include producing reliable group-wide cash visibility, forecasting liquidity across additional entities and currencies, funding expansion, controlling foreign-exchange risk and processing payments safely at greater scale.
A new Treasury Management System is not the objective and it is not the capability. It may become part of the response once the capability, current limitations and required operating model are understood. Technology expands what is possible; organisational purpose determines what is relevant.[5]
05
The transformation gap makes the change explicit
Required capability describes the destination. The current state establishes the starting point. The transformation gap is the material difference between them.
That gap may sit in skills, responsibilities, processes, information, controls, technology or the way Treasury connects to other functions. A system may be inadequate, but the deeper constraint may be late source data, unclear ownership or decisions made outside Treasury.
For international growth, the gap might include incomplete cash visibility, limited multi-currency forecasting, fragmented banking structures or funding processes that cannot scale across additional entities.
Without a clear difference between current and required capability, there is no basis for calling the response a transformation. There may still be a platform replacement or process improvement, but the nature of the transformation has not been established.[6][7]
06
Business As Usual (BAU) change can contribute without defining the whole
Treasury changes continuously. Processes improve, controls strengthen, technology is updated and operating problems are resolved. This is BAU change.
In organisational-change terms, this is broadly first-order change: improvement within the existing model. Transformation begins when Treasury's capability or the model itself must materially change.
The boundary is not determined by the size of an individual project. Several connected changes may collectively alter Treasury's capabilities or how they are produced. A BAU change can therefore form part of a transformation when it closes part of the agreed gap and retains line of sight to the organisational driver and Treasury requirement.
Without that connection, even a large programme may remain a collection of improvements rather than a coherent transformation.
Several improvements may be connected and may produce useful process benefits. If they are not a response to a material change in what the organisation requires from Treasury and do not change the capability Treasury must provide, TRC treats them as an improvement programme, not a Treasury transformation.[1][9][18][19]
07
Treasury does not operate in isolation
Treasury capability is produced through an operating model and a set of organisational interfaces. Cash forecasting may depend on Accounts Payable, Accounts Receivable, Financial Planning and Analysis, payroll and operating businesses. Payments may involve Procurement, master data, Accounts Payable, Treasury, Information Technology and banks.
The object of transformation is therefore not simply the Treasury department. It is Treasury's capabilities, operating model and the interfaces through which information, responsibilities, controls and decisions pass.
In the international-growth example, the transformation may extend across entity data, bank connectivity, foreign-exchange processes, funding responsibilities, liquidity information and the interfaces between Treasury, Finance and operating businesses.
A forecasting platform may improve Treasury's analytical tools. If source information remains late or unreliable, the organisation may still lack an effective forecasting capability. The platform changed. The outcome did not.[2][3]
08
Transformation changes relationships as well as components
When Treasury changes, responsibilities may move, information may be required earlier, data ownership may alter and controls may shift upstream or downstream.
If Treasury automates a payment process, Accounts Payable may need to provide more accurate data or apply different approvals. Accounting may receive information differently. Controls once performed in Treasury may move elsewhere.
A function can become more efficient locally while making the wider organisation less effective. Local optimisation is not necessarily organisational optimisation. The transformation therefore extends across the relevant interfaces; its object is not confined to Treasury.[6][7][8]
09
Line of sight gives separate changes coherence
A transformation may contain legitimate changes to technology, process, data, controls, skills and responsibilities. Their presence does not, by itself, make them a transformation.
Connectedness is part of the definition. The individual initiatives are not separate transformations; together, they form the connected body of change through which Treasury responds to the organisational shift.
As work is divided across functions, workstreams and suppliers, each group interprets success through its own responsibilities. The platform is implemented. Processes are documented. Data is migrated. Projects are completed. Yet Treasury may still not possess the capability the organisation required.
Line of sight connects the organisational driver, Treasury requirement, required capability, transformation gap, connected changes and measurable Treasury outcome. It is not administrative traceability. It is what prevents the programme from becoming a set of locally successful but collectively incoherent projects.[10][11][20]
10
When has Treasury been transformed?
Delivery measures establish that change occurred. They do not establish that Treasury was transformed. The final test is whether Treasury acquired the required capability and can demonstrate its contribution to the original objective.
That does not mean attributing the organisation's entire result to Treasury. International growth, resilience or better decisions depend on many functions. The evidence should distinguish three things: the organisational outcome sought, Treasury's contribution to it and the measurable Treasury capability created.
If the objective was scalability, can Treasury absorb more volume and complexity without simply adding people? If it was resilience, are recovery, liquidity and payment capabilities demonstrably stronger? If it was better decision-making, is Treasury producing more reliable information at the point decisions are made?
For international growth, the test is not whether separate projects were completed. It is whether Treasury can now provide the visibility, funding, risk control and payment capability the expanded organisation requires.
Transformation is demonstrated by a different capability and operating outcome, not merely by completion of the projects intended to create it.[2][20][21]
11
Conclusion
A material change in the organisation's business environment may create a transformational requirement for Treasury.
Treasury transformation is the connected set of change initiatives required to respond to that ask. The requirement may arise from a change in strategy or regulatory environment, or from changes to the organisation's business model, ownership, scale, funding, capital structure, risk exposure or resilience requirements.
Those changes may sit inside Treasury or in the functions, systems and processes it depends on. Technology, processes, data, controls and people all matter. None independently defines the transformation.
Line of sight keeps every material change connected to the organisational driver and Treasury requirement that made the transformation necessary. It is what turns separate projects into a coherent response and allows the resulting Treasury capability to be tested.
How line of sight should be preserved through design, governance and delivery is the subject of the next TRC paper.[18][19][20][21]