A company operating subsidiaries across several EU countries, even within the eurozone, runs into budgeting complications that a single-currency, single-country operation never has to deal with. And for companies with operations spanning both eurozone and non-eurozone EU countries, Poland, Sweden, or Denmark, for example, alongside eurozone entities, the complications compound further. A few structural practices consistently separate finance teams that handle this smoothly from those that spend a disproportionate amount of time reconciling avoidable discrepancies.
Budget-setting currency versus reporting currency need to be explicitly separated
A common source of confusion is not clearly distinguishing between the currency a subsidiary's budget is actually set and managed in day-to-day versus the group reporting currency used for consolidated financial statements. When these aren't explicitly separated in the budgeting process, local finance teams sometimes end up managing to a budget number that was silently converted at a stale exchange rate, without realizing the number they're tracking against has already drifted from what group finance actually intended.
Explicitly stating both the local operating currency budget and the reporting currency equivalent, along with the specific exchange rate and date used for that conversion, in every budget document removes this ambiguity and gives local teams a clear, stable number to manage against regardless of subsequent currency movements.
Exchange rate volatility needs a defined treatment, not an implicit assumption
Currency movements over the course of a budget year can meaningfully affect how a subsidiary's actual performance compares to its budget, even when the subsidiary's local-currency performance is exactly on plan. Without an explicit policy on how this is handled, budget variance reviews can end up attributing exchange-rate-driven variance to operational performance, which produces a distorted picture of how a subsidiary is actually doing and can lead to unwarranted pressure on a local team for a variance that has nothing to do with their operational decisions.
A clear policy, commonly either locking the budget at a fixed exchange rate set at the start of the year and tracking variance against that fixed rate regardless of actual currency movement, or explicitly separating reported variance into an operational component and a currency component, prevents this conflation and lets performance conversations focus on what a local team actually controls.
Intercompany transactions create currency exposure that's easy to overlook
Subsidiaries that transact with each other, one entity providing services or goods to another within the group, create currency exposure at the point of intercompany settlement that's separate from each entity's external revenue and costs. This exposure is often under-modeled in budgeting processes that focus primarily on each subsidiary's external-facing financials, since intercompany flows can feel like an internal accounting detail rather than a genuine currency risk.
In practice, meaningful intercompany transaction volume across currency pairs represents real exposure to exchange rate movement, and modeling this exposure explicitly, rather than assuming it nets out or is immaterial, avoids surprises when intercompany settlement amounts diverge from what was budgeted due to currency movement between the budget-setting date and the actual settlement date.
Hedging decisions need to be made deliberately, not by default
Companies vary considerably in how much currency risk they choose to hedge, and there's no universally correct answer, it depends on risk tolerance, the materiality of the exposure, and the cost of hedging relative to the exposure being managed. What matters more than which specific approach a company takes is that the decision is made deliberately, with an explicit view of the actual exposure across all subsidiaries and currency pairs, rather than defaulting to no hedging simply because nobody explicitly evaluated the exposure and made a conscious choice about it.
A periodic review, even quarterly, of aggregate currency exposure across the full group, not just exposure visible within any single subsidiary's own books, gives finance leadership the information needed to make this decision deliberately rather than by omission.
Local finance teams need budgeting autonomy within a consistent group framework
A tension that shows up repeatedly in multi-subsidiary budgeting is between standardizing the budgeting process enough to allow meaningful group-level consolidation and comparison, and giving local finance teams enough autonomy to budget in a way that reflects genuine local market conditions, local currency dynamics, and local competitive context that a rigid, centrally imposed template may not capture well.
Companies that handle this well tend to standardize the structural elements, currency treatment, reporting timeline, variance methodology, while leaving genuine room for local judgment within that structure, rather than either imposing a fully centralized template that ignores local nuance or allowing fully independent local processes that make group-level consolidation and comparison unreliable.
The underlying discipline
None of these practices require sophisticated treasury infrastructure to implement, most are achievable through disciplined process design and clear documentation rather than specialized tooling. What separates companies that manage multi-currency budgeting smoothly from those that don't is less about resources and more about whether these currency-related decisions were made explicitly, upfront, and consistently, rather than left as implicit assumptions that different people across different subsidiaries end up interpreting differently, which is where most of the actual reconciliation pain in multi-currency budgeting tends to originate.
Top comments (0)