Treasury centralisation is often associated with better cash visibility, stronger financial control and more efficient funding. Yet for multinational groups, there is an important trade-off: if every treasury decision must be escalated to headquarters, local teams can lose the responsiveness they need to manage daily operations.
The objective is not to choose between a fully centralised and a fully decentralised model. It is to determine what should be managed at group level, what should remain local, and how a Treasury Management System (TMS) can connect both.
The central principle
Centralising governance does not mean centralising every transaction or decision.
Group-wide oversight and locally delegated execution can coexist when responsibilities, controls and information flows are clearly defined.
Why centralise treasury in a multi-entity group?
As organisations expand across countries, business units and banking partners, treasury information becomes fragmented. Account balances sit with different banks; forecasts are prepared in separate systems; financing decisions may be made without a complete picture of the group’s resources and needs.
Centralisation addresses this fragmentation. When designed appropriately, it strengthens the group’s ability to anticipate cash requirements, coordinate financial decisions and apply consistent controls without necessarily taking over every local process.
Consolidated cash visibility
Bring bank balances, cash positions and forecasts together across entities, banks and currencies, based on available reporting data.
More coordinated funding
Identify surpluses and financing requirements across the group, helping to reduce unnecessary external borrowing where feasible.
Consistent risk management
Apply a common approach to FX exposures, financing risks, limits and hedging policies while taking local constraints into account.
Stronger controls and banking coordination
Harmonise approval principles, access rights and strategic banking relationships, with local arrangements where needed.
These benefits are significant, but they do not require identical operating procedures in every subsidiary. A consolidated view of cash is not the same thing as physically concentrating all cash in one location. The distinction matters when selecting a treasury organisation.
When centralisation becomes a constraint
Each subsidiary operates in a specific environment. Local currencies, exchange controls, tax rules, banking cut-off times, market practices and business cycles can all affect how treasury activities should be organised. A process that works efficiently at headquarters may not be appropriate in every country.
Excessive centralisation can also create operational bottlenecks. Consider a subsidiary that needs to release a time-sensitive supplier payment. If every approval must pass through a small central team in another time zone, a control designed to improve security may also create delays.
Slower decisions
Routine payments or cash decisions depend on approvals that do not always require group-level intervention.
Complex approval chains
Multiple hand-offs can obscure accountability instead of making controls clearer.
Reduced local responsiveness
Local treasury and finance teams may lack the authority to react quickly to operational needs or banking requirements.
The challenge is therefore not simply to maximise centralisation. It is to centralise where doing so improves decision-making and risk control, while retaining local flexibility where it adds operational value.
Centralise governance, not necessarily every operation
A practical way to approach treasury centralisation is to separate governance from execution. Headquarters sets the policies, information standards and limits that apply across the group. Subsidiaries can then perform authorised activities within that framework, with exceptions escalated when necessary.
At headquarters: group oversight
- Consolidated cash and forecast visibility
- Funding and investment policies
- Group FX and financial risk policy
- Access rights, approval rules and limits
- Strategic banking relationships
At subsidiary level: local operations
- Day-to-day payments and collections, as authorised
- Local cash forecasts and funding needs
- Operational decisions within group limits
- Country-specific banking and regulatory requirements
- Escalation of exceptions and material exposures
For example, a subsidiary may be authorised to approve payments below a defined threshold, while higher-value or higher-risk transactions require additional group-level validation. The same principle can apply to cash transfers, FX transactions or financing requests. A consistent policy does not have to mean the same approval route for every operation.
The most useful question is not “Who performs every transaction?” but “Who decides, who executes, who controls, and who has visibility?”
Cash pooling, Payment Factory, In-House Bank: choosing the right model
Different treasury arrangements help groups coordinate cash and financial processes. They solve related but distinct problems, and they do not represent mandatory stages in a single maturity model. A group may combine several approaches depending on its countries, legal entities, banks and operational requirements.
| Arrangement | Main purpose | Governance consideration |
|---|---|---|
| Group reporting and cash visibility | Consolidate information without necessarily moving funds. | Define reporting responsibilities and data-refresh frequency. |
| Cash pooling | Coordinate cash balances through physical concentration or notional offsetting. | Assess banking, legal, tax and country-specific feasibility. |
| Intercompany financing | Arrange lending and borrowing between eligible group entities. | Define pricing, credit limits, documentation and tax treatment. |
| Payment Factory | Standardise and control payment processes and bank connectivity. | Define who initiates, validates, signs and monitors payments. |
| In-House Bank | Organise intra-group accounts, funding and financial flows. | Define internal limits, pricing, responsibilities and local treatment. |
For instance, a group could centralise banking communication and payment controls through a Payment Factory while keeping the initiation of operational payments with its subsidiaries. Another organisation may use cash pooling for selected entities and manage other countries through reporting and local bank accounts.
There is no universally optimal structure. Physical and notional cash pooling arrangements, in particular, have different legal and financial implications; their applicability depends on the countries and banks involved. The preferred model should follow the operating needs and constraints of the group, rather than dictate them.
How a TMS makes the balance possible
A Treasury Management System provides the common information and control framework that supports a hybrid operating model. Its contribution is not simply to bring all transactions into one application. It is to connect group-level oversight with the operational processes carried out by individual entities.
Depending on the solution and configuration, a TMS can help the treasury team:
Consolidate information
Collect account balances, forecasts, positions and transaction information across banks, ERPs and entities.
Apply consistent controls
Configure role-based access, approval thresholds, segregation of duties and audit trails.
Delegate authorised actions
Give subsidiaries clearly defined rights to initiate or approve operations within group policies.
Manage exceptions and exposures
Escalate transactions outside predefined limits and provide the group with the reporting needed to act.
This is particularly relevant for treasury organisations with diverse banking environments, currencies and operational models. A common platform can support local execution without sacrificing consolidated reporting, traceability and group-wide policies.
For example, Datalog TMS combines cash management, payments, banking connectivity, financial risk management and in-house banking capabilities in a modular platform. Its configurable workflows help groups adapt controls and responsibilities to their treasury organisation, rather than imposing a single degree of centralisation.
Six questions to define the right level of centralisation
Before changing a treasury operating model, it is useful to assess where group oversight delivers the most value and where local discretion remains necessary.
- What does the group need to see? Identify the cash positions, forecasts, bank accounts and exposures that require consolidated reporting.
- Which decisions have group-wide financial implications? Define central policies for funding, investments, hedging and material cash transfers.
- Which operations require local responsiveness? Identify time-sensitive payments, collections and country-specific banking processes.
- Where are the legal and regulatory boundaries? Review exchange controls, banking rules, tax implications and restrictions on cash movements.
- Who should authorise exceptions? Set clear approval thresholds, responsibilities, escalation routes and audit requirements.
- Can the technology support different levels of autonomy? Check whether workflows, reporting and access rights can be adapted by entity, country or transaction type.
The result is not necessarily one uniform model for the entire organisation. Many multinational groups need a common governance framework with differentiated operational arrangements across countries and subsidiaries.
Key takeaway
Effective treasury centralisation is not about routing every decision through headquarters. It is about combining group-wide visibility and control with the right level of local autonomy.
Frequently asked questions about treasury centralisation
What is treasury centralisation?
Treasury centralisation is the organisation of selected cash management, funding, financial risk and banking activities at group level. It can involve centralised policies, reporting, control or execution, depending on the group’s operating model.
Does centralising treasury mean moving all cash to headquarters?
No. A group can consolidate cash visibility, forecasts and control rules without physically moving all subsidiary funds. Cash pooling or other concentration mechanisms may be used where appropriate, but they are not prerequisites for centralised treasury governance.
Can subsidiaries remain autonomous when using a central TMS?
Yes. A TMS can support different access rights, validation thresholds and workflows by entity, allowing local teams to carry out authorised operations while the group maintains visibility and consistent controls.
Is a Payment Factory the same as an In-House Bank?
No. A Payment Factory mainly standardises payment processing, controls and banking communication. An In-House Bank is a broader intra-group treasury arrangement that can manage internal accounts, funding and financial flows. The two approaches can complement each other.
Explore related Datalog solutions
Build a treasury organisation that fits your group
Combine group-wide control with local agility
Discover how Datalog TMS can help structure cash visibility, financial controls and treasury workflows across your subsidiaries.
