The accounting treatment for multi-currency consolidation — how IAS 21 requires different rates for balance sheet and P&L items, how the currency translation adjustment is calculated and allocated to equity — is a technical problem with a defined solution. The harder challenge is operational: how do you manage a multi-currency entity group in practice, period after period, in a way that produces accurate consolidated figures without the close being derailed by rate inconsistencies, intercompany mismatches, and FX noise that makes it impossible to read actual business performance?
This post covers the operational best practices — the decisions and processes that determine whether multi-currency reporting works smoothly or becomes a recurring source of delays and errors.
Best Practice 1
Establish and Publish a Formal Group Exchange Rate Policy
Most multi-currency problems trace back to one root cause: different entities applying different rates to the same currency pair on the same date. Without a formal rate policy, entities source rates wherever is convenient — their own bank’s feed, an online currency converter, yesterday’s rate because the system was down — and the intercompany positions that should eliminate to zero instead produce residual mismatches.
A group exchange rate policy should specify: the source for each rate type (a named central bank or data provider), the date on which rates are set for each period, and who is responsible for publishing the rate table to all entities. For most groups, the relevant rates are the closing rate (spot rate at the last business day of the period) and the average rate (typically the arithmetic mean of daily closing rates, or in practice the mid-month rate). Both should be published from a single authoritative source.
Rate policy example — what to specifyClosing rate: ECB reference rate (for EUR pairs) / MAS published rate (for SGD pairs) on the last business day of the reporting period.
Average rate: Average of daily ECB/MAS reference rates for the calendar month.
Publication: Group finance publishes the rate table by the 2nd business day of the following month. All entities must use these rates for both their entity submission and any intercompany invoicing for the period.
Source documentation: Rate table archived with source data for each period as part of the consolidation working papers.
Best Practice 2
Lock Rates Before the Close Starts, Not After
The sequence matters. Rates should be published and locked before entities submit their trial balances — not derived from what entities submitted. If Group Finance publishes the rate table on day two of the close cycle and entities have already submitted data using their own rates, the consolidation either uses inconsistent rates or requires re-submissions — both of which add time and risk.
Rate locking before submission serves a second purpose: it prevents the intercompany mismatch caused by rate timing. If Entity A records a $50,000 intercompany receivable and translates it at Monday’s rate while Entity B records the corresponding payable and translates at Wednesday’s rate, the two sides don’t match after translation. A single published rate, applied by all entities to the same transactions, eliminates this class of mismatch entirely.
🚩 The most common rate locking failure: The rate table is published on time, but one entity has already submitted using its accounting software’s automatic rate — which pulled a live feed rate on a different day. The result is a small intercompany difference that requires manual adjustment to clear. Multiplied across multiple entities and multiple currency pairs, these small differences consume hours of close time every month. The fix is requiring entities to confirm which rates they applied before the submission is accepted.
Best Practice 3
Report in Constant Currency to Separate FX from Operations
When a foreign subsidiary’s results are translated into the group presentation currency, two things change simultaneously: the operational performance of the business and the exchange rate used to express it. A subsidiary that grew revenue by 8% in local currency terms may show 2% growth or 12% growth in group currency depending on whether the rate moved against or in favour of the group. The board is looking at one number that contains two stories.
Constant currency reporting separates them. In a constant currency report, the prior period figures are restated at the current period’s exchange rate before the comparison is made. This removes the rate movement as a variable — the only remaining difference between periods is operational performance.
Constant currency worked example UK subsidiary revenue: GBP 500,000 in prior period, GBP 540,000 in current period (8% growth in local currency).
Prior period GBP/SGD rate: 1.70 → SGD 850,000
Current period GBP/SGD rate: 1.55 → SGD 837,000
Reported growth in group currency: −1.5% (GBP weakened against SGD).
Constant currency growth: Restate prior period at current rate: GBP 500,000 × 1.55 = SGD 775,000. Growth = (SGD 837,000 − SGD 775,000) / SGD 775,000 = +8% (operational growth, FX removed).
The board narrative: “Revenue grew 8% in local currency; reported in SGD the growth was −1.5% due to GBP/SGD movement. On a constant currency basis, the UK business is performing on plan.”
For groups with material foreign currency exposure, constant currency commentary in management reporting is not optional — it’s the difference between the board understanding operating performance and the board making decisions based on FX noise.
Best Practice 4
Decide Intercompany Invoice Currency Deliberately
When a parent company invoices a subsidiary for management fees, goods, or services, the choice of invoice currency determines where the FX risk sits. This decision is often made by default — whoever raises the invoice uses their own currency — rather than deliberately. The consequences are material.
| Invoice currency | FX risk sits with | Entity-level P&L impact |
|---|---|---|
| Parent’s functional currency | Subsidiary | Subsidiary records a foreign-currency payable, retranslated at each period end, with FX gains/losses in subsidiary P&L |
| Subsidiary’s functional currency | Parent | Parent records a foreign-currency receivable, retranslated at each period end, with FX gains/losses in parent P&L |
| Third currency (e.g. USD) | Both entities | Both entities carry retranslation exposure against their respective functional currencies |
For groups where entity-level profitability is tracked and reported, this decision affects which entity shows FX volatility in its P&L. For groups where transfer pricing policy specifies intercompany pricing in a particular currency, the choice may be constrained. The point is that it should be a deliberate policy decision, documented and consistently applied — not a default based on whoever creates the invoice.
Best Practice 5
Distinguish Natural Hedges from Genuine FX Exposure
Not all foreign currency exposure is a risk that needs managing. A natural hedge exists when a foreign currency entity has both revenue and costs denominated in the same foreign currency — the exposures offset each other, and the net exposure is much smaller than the gross revenue or cost figures suggest.
A UK subsidiary that earns in GBP and pays its UK staff, suppliers, and rent in GBP has very little genuine GBP/SGD translation exposure at the operating level — its GBP operating costs naturally offset its GBP revenues. The only real group-level FX exposure is the translation of net GBP assets (equity position) at each period end, which creates CTA movements but not cash flow exposure.
The genuine FX exposures to track are those where revenue and costs are in different currencies — a Singapore entity that earns USD from US clients but pays its staff in SGD, for example. That entity’s USD/SGD rate movement directly affects its SGD operating margin. Understanding which entities have natural hedges and which have genuine net exposures is the starting point for any rational FX risk management conversation.
💡 The practical implication for reporting: Entities with natural hedges don’t need constant currency commentary — their local currency performance is already the relevant story. Entities with genuine net currency exposures need constant currency reporting and, where material, explicit FX sensitivity disclosure (e.g. “a 5% movement in USD/SGD would impact group EBITDA by SGD X”).
Best Practice 6
Build Specific Protocols for High-Volatility and Restricted Currencies
The standard IAS 21 translation approach works well for freely traded currencies with liquid markets. It works less well — and in some cases produces legally questionable results — for currencies subject to exchange controls, official rates that diverge significantly from market rates, or hyperinflationary conditions.
For entities in markets where the official rate and the freely available market rate diverge materially (Argentina is the most prominent current example), IAS 21’s requirement to translate at the closing rate raises the question of which rate to use. Using the official rate may not faithfully represent the economic reality if the official rate is not accessible for actual transactions. Disclosure of the rate used, the alternative rate available, and the financial statement impact of the divergence is increasingly expected by auditors and investors.
For entities in hyperinflationary economies, IAS 29 (Financial Reporting in Hyperinflationary Economies) applies — which requires restating non-monetary items for inflation before translation, rather than applying the standard IAS 21 approach. Groups with subsidiaries in countries currently classified as hyperinflationary (typically those with cumulative inflation exceeding 100% over three years) need specific protocols for these entities that sit outside the standard multi-currency consolidation workflow.
BrizoConsol supports multi-currency consolidation with configurable rate tables — closing and average rates set and applied centrally, with drill-down showing which rate was applied to each entity’s figures. Currency translation adjustments are calculated automatically and allocated to equity as a separate component. Learn more or see it in action →