The Problem With Decentralized FX
In a multi-entity corporate group, FX exposures are rarely managed centrally by default. Each subsidiary handles its own currency needs through its local bank, often at whatever rate the relationship manager quotes that day. The result is a structure where the group as a whole carries more FX cost and more risk than it needs to.
The pattern is familiar to any group treasurer who has tried to get a consolidated picture of FX exposure: each entity reports in a different format, hedges at different times and rates, and maintains separate banking relationships that cannot be netted against each other. Two subsidiaries in the same group might simultaneously be long EUR and short EUR, each paying a spread to convert, when they could simply transfer between themselves.
What Visibility Gaps Cost
The first problem with decentralized FX is visibility. If the treasury team cannot see the consolidated FX position of the group in real time, they cannot make informed hedging decisions. They are managing a portfolio of individual exposures rather than a net position.
This matters because hedging a net position is always cheaper than hedging a collection of gross positions. A group with a EUR 5 million long position in Germany and a EUR 3 million short position in Spain has a net EUR 2 million long. Hedging EUR 2 million costs roughly 40% of what it costs to hedge EUR 5 million and EUR 3 million separately. The difference is the cost of poor visibility.
The second problem is timing. When each entity hedges independently, they hedge at different times in response to their own operational cycle. The group ends up with a portfolio of hedges at different rates, maturity dates, and counterparties. Unwinding or rolling these efficiently requires a level of coordination that most decentralized structures do not have.
The Role of Intercompany Transfers
Many multi-entity groups have entities in multiple currency zones. A parent in the US may have subsidiaries in the UK, Brazil, and Singapore. Each entity has its own operating currency, and the group regularly needs to move funds between them — dividend upstream, funding pushdown, or operational cost recharges.
Each intercompany transfer involves an FX conversion. If each entity handles this independently through its local bank, the group is paying multiple retail FX spreads on transfers that are, from the group's perspective, internal. Centralizing these through a single FX execution function means converting at institutional rates, netting offsetting flows where possible, and maintaining visibility over the timing and cost of every transfer.
What Centralized Execution Looks Like
Centralized FX execution does not require a treasury management system that costs seven figures. At its core, it requires three things: a single point of execution where all group FX trades are booked, institutional pricing that reflects the group's aggregate volume, and a visibility layer that shows the consolidated position.
In practice, this means the treasury team (or a centralized treasury entity within the group) executes all FX on behalf of subsidiaries through a single provider relationship. Subsidiaries submit their hedging requirements — currency, amount, tenor — to the central treasury function, which aggregates and executes. The execution rate is better than what any individual subsidiary would achieve locally. The administrative overhead is lower because there is one counterpart, one documentation set, and one reconciliation process.
The Intragroup Pricing Question
When a group centralizes FX, the question arises of how to price the service to subsidiaries. Transfer pricing rules require that intragroup transactions be priced at arm's length — a subsidiary receiving an FX conversion from the treasury function should pay a rate that is comparable to what they would receive from a third party.
This is straightforward to document when the treasury function is using an external provider at institutional rates. The subsidiary pays a small spread above the interbank rate, and the documentation demonstrates that the rate is competitive with what any external bank would offer. The group captures the benefit of institutional pricing while subsidiaries pay a rate that is still better than what they would achieve alone.
Multi-Currency Accounts as the Operating Layer
Centralized FX execution works most cleanly when the group's entities can hold balances in multiple currencies from a single account structure. Rather than converting immediately upon receipt, the treasury function holds currencies until it is optimal to convert — allowing it to take advantage of favourable rate windows rather than converting at whatever the market is doing on the day the subsidiary needs the funds.
Multi-currency virtual accounts, where each currency has its own balance but all accounts are visible and manageable from a single relationship, are the operational infrastructure that makes this possible. The treasury function sees EUR, USD, GBP, and BRL balances in one place, can transfer between them at will, and can time conversions around operational requirements and rate movements.
Getting Started
For a group that is currently managing FX on a decentralized basis, the starting point is a consolidated picture of current FX exposure and cost. What is the group converting per year, across which currency pairs, at what average spreads? The answer frequently reveals that a simple change in execution infrastructure reduces FX costs by 30 to 50 basis points on aggregate volume — which, at any meaningful scale, justifies the exercise entirely.
