Back to blog
Reporting

Multi-Currency Consolidation Challenges for EU Finance Teams

Grove FP Team2 April 20267 min read

The multi-currency reality of European FP&A

Operating across the European Union means dealing with multiple currencies as a matter of course. While the eurozone covers 20 member states, significant EU economies like Poland (PLN), Sweden (SEK), Czech Republic (CZK), Denmark (DKK), Hungary (HUF), and Romania (RON) maintain their own currencies. Add in the UK post-Brexit (GBP) and Switzerland (CHF) for pan-European operations, and a typical mid-market European group may be consolidating five to ten currencies into a single reporting currency.

The consolidation challenge is not simply one of translation. It involves choosing the right exchange rates for different line items, handling intercompany transactions that cross currency boundaries, and presenting a consolidated view that management can actually use for decision-making.

Translation method under IAS 21

Under IAS 21, foreign operations are translated using the closing rate method. Assets and liabilities translate at the closing rate, income and expenses translate at the average rate for the period (or transaction date rates if rates fluctuate significantly), and equity translates at historical rates. The resulting translation difference goes to other comprehensive income, not the P&L.

For FP&A, this means your budget and forecast must model three different rate assumptions: closing rates for the balance sheet, average rates for the P&L, and historical rates for equity. Using a single rate across all statements is a common shortcut that produces misleading consolidated numbers.

Intercompany eliminations

Intercompany transactions are where multi-currency consolidation gets genuinely complex. When a German parent invoices a Polish subsidiary in EUR, the subsidiary records a PLN payable at the transaction date rate. By month-end, the PLN equivalent may have changed, creating an FX gain or loss on the subsidiary's books. At consolidation, the intercompany balance must eliminate -- but it only eliminates cleanly if both entities are using the same rate.

The practical solution is to designate a single intercompany rate (typically the month-end closing rate or a fixed monthly rate published by group treasury) and require all entities to revalue their intercompany balances to this rate before consolidation. Any FX difference goes to a designated FX line item that is visible in reporting.

Building a multi-currency budget model

Start with local currency budgets. Each entity should budget in its functional currency. This is where the operational detail lives, and it avoids introducing FX noise into departmental variance analysis. A Polish subsidiary's marketing team should see their budget and actuals in PLN, not EUR.

Centralise rate assumptions. Group finance should publish a single set of budget rates for the year -- typically based on forward rates or bank consensus forecasts at the time of budget preparation. All entities use these rates for consolidation, ensuring comparability.

Model FX sensitivity. Include at least two scenarios in your consolidated forecast: the base case using budget rates, and a sensitivity case using current spot rates. The difference tells leadership how much of the consolidated variance is operational versus currency-driven.

Separate transactional and translational FX. Transactional FX (gains and losses on foreign-currency-denominated receivables and payables) hits the P&L. Translational FX (the effect of converting foreign subsidiary results into group currency) hits OCI. Your forecast model should separate these because they behave differently and require different management responses.

Practical tooling considerations

Spreadsheet-based consolidation breaks down quickly with multiple currencies. The rate lookup tables, the intercompany matching, and the elimination entries create a web of VLOOKUP and SUMIF formulas that are fragile and opaque. A dedicated FP&A platform with native multi-currency support handles rate management, automatic translation, and intercompany elimination as core functionality.

For a structured starting point, see the multi-currency budget model template and the multi-currency planning guide.

Ready to get started?

See Grove FP in action

Start building smarter budgets today. No credit card required.