Group consolidation
Multi-entity FX consolidation for group finance teams
Updated
A group with subsidiaries in different base currencies cannot read its real FX position one entity at a time. Each subsidiary measures exposure in its own functional currency, and the group needs those positions translated into one presentation currency without double-counting intercompany invoices.
For group finance teams and CFOs searching how to consolidate FX exposure and P&L across subsidiaries with different base currencies.
The short answer
Measure each subsidiary in its functional currency, translate every position into the group presentation currency with a consistent rate, eliminate intercompany invoices once, and keep transaction-level FX (functional-currency P&L) separate from the translation difference that arises on consolidation (IAS 21).
Source records
| Record | Used for | Watch out |
|---|---|---|
| Per-entity invoices and bills | Functional-currency exposure for each subsidiary before any group roll-up. | Each entity has its own base currency; never sum them before translating. |
| Per-entity bank balances | Foreign cash held inside each subsidiary, revalued in its functional currency. | Held foreign cash shows as translation exposure at group level, not parent P&L. |
| Intercompany invoices | Trades between group entities that are eliminated once in consolidation. | Counting an intercompany receivable and its matching payable twice overstates group exposure. |
| Closing and average rates | Translating each subsidiary position into the group presentation currency. | Use one consistent rate source and reject placeholder 1.0 rates between two real currencies. |
What finance teams run into
| Problem | What it means | Response |
|---|---|---|
| Subsidiary P&L is summed in mixed currencies | The consolidated FX number is dimensionally wrong and can overstate or hide group risk. | Translate each entity into the group base currency before adding anything together. |
| An intercompany invoice is counted on both sides | The group double-counts an exposure it holds against itself. | Identify trades between group entities and eliminate them once before netting. |
| Held foreign cash is read as a parent cash loss | A subsidiary translation movement is mistaken for a realised hit at the parent. | Keep functional-currency P&L separate from the group translation lens. |
Checks before relying on the numbers
- Every subsidiary is translated with a sourced, non-1.0 rate. A placeholder 1.0 rate between two real currencies silently corrupts the consolidated total.
- Intercompany invoices are flagged and removed exactly once. It stops the same exposure appearing in two entities and inflating the group figure.
- Functional-currency P&L is reported separately from the translation difference. IAS 21 keeps transaction gains in P&L and the consolidation movement in a translation reserve, not P&L.
A GBP group with ZAR and USD subsidiaries
Illustrative figures, not customer data.
| Item | Value | Note |
|---|---|---|
| GBP parent | EUR and USD receivables | Functional currency GBP; exposure measured directly in GBP. |
| ZAR subsidiary | USD supplier bills | Functional currency ZAR; measure in ZAR, then translate to GBP. |
| USD subsidiary | Held USD cash all year | No parent P&L hit, but the group still carries the translation exposure. |
| Group view | One net position in GBP | Currencies netted across entities after intercompany elimination. |
Multi-entity consolidation review
| Stage | Finance question | What to check |
|---|---|---|
| Per entity | What is each subsidiary exposed to? | Functional-currency receivables, payables, and cash for that entity only. |
| Translate | How does it roll up to the group? | A consistent closing or average rate from one source into the presentation currency. |
| Eliminate | Are any trades intercompany? | Invoices between group entities removed once so exposure is not double-counted. |
| Two lenses | P&L or translation? | Transaction FX hits functional-currency P&L; the consolidation movement is a translation difference (IAS 21). |
Common mistake
Adding up each subsidiary P&L in mixed currencies, or netting an intercompany receivable against its matching payable twice, makes the consolidated FX number look tidy and wrong.
Where Hedgr fits
Hedgr Pro tags every invoice, bill, and balance by entity, translates each subsidiary into the group base currency, eliminates intercompany invoices, and shows functional-currency P&L next to the group translation lens.
Related guides
- Realised vs Unrealised FX
- FX Exposure: Gross, Net, and Cash Timing
- What FX Risk Management Software Should Do
Hedgr is read-only. It does not execute trades, move funds or give investment advice.
Guides
- FX exposure basics
- SME FX policy template
- Unrealised FX gains and losses
- Realised vs unrealised FX
- Multi-currency invoice cashflow risk
- Xero FX exposure workflow
- QuickBooks Online FX exposure workflow
- Exporter month-end FX reporting
- Multi-entity FX consolidation
- SARB BoP categories after the August 2026 change
- Sage One South Africa FX exposure workflow
- Rand exposure for SA importers and exporters
- IAS 21 and the margin basis: does your FX impact double-count?
- FX risk management software for SMEs
- What FX hedging software does
- Hedge accounting software vs FX exposure software
- FX risk for e-commerce and DTC exporters