Every group with subsidiaries reporting in more than one currency runs into the same question sooner or later: how do you turn a set of financial statements prepared in Swedish kronor, US dollars, or Kenyan shillings into one consolidated set of numbers the group can actually report on? IAS 21, The Effects of Changes in Foreign Exchange Rates, is the standard that answers that question, and it’s one that trips up even experienced group accountants when the details get technical.
This guide walks through the practical mechanics of currency translation under IAS 21, where the currency translation adjustment comes from, and where groups most often get it wrong. It’s written as a working reference for people who actually run a consolidation, not a substitute for the standard itself or for advice on a specific fact pattern from your auditor.
What IAS 21 Actually Covers
IAS 21 does two distinct jobs, and it helps to keep them separate in your head. First, it sets out how to account for individual foreign currency transactions, things like a sale invoiced in a currency other than your functional currency. Second, and this is where most consolidation headaches live, it sets out how to translate the entire financial statements of a foreign operation into the currency the group uses for its consolidated reporting.
This guide focuses mainly on the second one. If your group runs consolidation through a dedicated CPM system, this is the part of the standard your software needs to get right on your behalf, period after period, across every entity in the structure.
Functional Currency vs. Presentation Currency: Get This Right First
Before any translation can happen, you need to be clear on two separate concepts that get confused constantly.
Functional currency is the currency of the primary economic environment in which an entity actually operates. This is not necessarily the currency an entity happens to invoice in. A subsidiary based in Poland that sells mainly into the Eurozone, prices its contracts in euros, and settles most of its costs in euros may well have the euro as its functional currency, even though it’s legally incorporated in Poland and files its statutory accounts in zloty.
IAS 21 points to a handful of indicators to help determine this: the currency that mainly influences sales prices, the currency of the country whose competitive forces and regulations mainly determine sales prices, and the currency that mainly influences labor, material, and other costs. Where these indicators don’t point clearly in one direction, the standard also looks at financing currency and the currency in which receipts from operating activities are usually retained.
Presentation currency is a separate decision entirely: it’s whatever currency the group chooses to present its consolidated financial statements in. A UK-headquartered group might present in sterling even though several subsidiaries have the US dollar or the euro as their functional currency.
Getting functional currency wrong at the entity level is the single most common root cause of translation problems that surface later in consolidation. If an entity’s functional currency is misidentified, everything built on top of it, the exchange rates applied, the treatment of monetary items, the resulting translation adjustment, will be wrong too, and it usually won’t be obvious until someone is trying to explain a strange movement in equity months later.
The Closing Rate Method, Step by Step
Once functional currency is settled, translating a foreign operation’s financial statements into the presentation currency follows what’s commonly called the closing rate method. It works like this:
- Assets and liabilities are translated at the closing rate, meaning the exchange rate at the balance sheet date.
- Income and expenses are translated at the exchange rate at the date of each transaction, though in practice groups almost always use an average rate for the period as a reasonable approximation, unless exchange rates have fluctuated significantly.
- Equity items, including share capital and pre-acquisition reserves, are translated at historical rates, meaning the rate in effect when that equity was originally recognized.
Here’s the part that catches people out: the resulting difference between these translations doesn’t go through profit or loss. It’s recognised in other comprehensive income and accumulated as a separate component of equity. Treating it as a P&L item is one of the more common errors we see, and it can materially distort reported earnings if it slips through.
A simplified example makes this concrete. Say a UK parent has a subsidiary in Kenya with a total balance sheet of KES 500 million and net income for the year of KES 40 million. If the closing rate is 165 KES to 1 GBP but the average rate for the year was 158 KES to 1 GBP, the balance sheet translates at roughly £3.03 million using the closing rate, while the income statement translates at roughly £253,000 using the average rate. Because two different rates were used for two different parts of the same set of financial statements, a difference falls out of the arithmetic. That difference is the currency translation adjustment, and it sits in equity rather than distorting the income statement.
Monetary vs. Non-Monetary Items: Why It Still Matters
The closing rate method above applies once you’re translating an entire set of financial statements into the presentation currency. But there’s a separate distinction that matters earlier in the process, particularly at the individual entity level before consolidation even begins.
Monetary items, cash, receivables, payables, loans, are translated at the closing rate, and any resulting exchange differences are recognized in profit or loss for that entity, since they represent a genuine economic gain or loss on holding those balances.
Non-monetary items, such as property, plant and equipment, or inventory carried at cost, are generally translated at the historical rate in effect when the item was originally recognised, and are not retranslated at each period end.
This distinction is easy to lose sight of once you’re focused on the group-level closing rate translation, but it’s still doing real work underneath. A subsidiary holding a large foreign-currency loan, for instance, will show genuine monetary exchange gains or losses in its own profit or loss well before that subsidiary’s financial statements ever reach group-level translation.
The Currency Translation Adjustment: What It Is and Where It Lives
The currency translation adjustment, often shortened to CTA, is the cumulative effect described above: the difference that arises from translating a foreign operation’s net assets using a rate different from the rate that applied historically.
It’s recognised in other comprehensive income and accumulated in its own separate component of equity, sitting alongside items like actuarial gains and losses or revaluation surpluses. It does not flow through profit or loss in the period it arises.
One detail that trips people up: on disposal of a foreign operation, the cumulative CTA relating to that entity is reclassified, or recycled, from equity into profit or loss as part of the gain or loss on disposal. This is why a group can sell a foreign subsidiary at what looks like a modest operating profit and still see a large gain or loss appear on disposal, driven almost entirely by years of accumulated currency movement finally being recognised.
This is also why a genuinely profitable subsidiary can show a large negative CTA balance in the group’s equity. It’s not a sign the subsidiary is performing badly. It simply reflects sustained depreciation of that entity’s functional currency against the group’s presentation currency over time, arithmetic, not performance.
Common Mistakes Groups Make When Translating Foreign Subsidiaries
A handful of errors show up repeatedly in group consolidations, even at well-run organizations:
- Applying the closing rate to equity items. Share capital and pre-acquisition reserves should be translated at historical rates, not the current closing rate. Getting this wrong throws off the calculated CTA and can misstate opening equity balances going forward.
- Confusing entity-level functional currency with the group’s presentation currency. These are two different questions answered at two different levels, and treating them as the same thing leads to the wrong rate being applied from the start.
- Using the spot rate instead of an appropriate average for income statement items, particularly where a subsidiary’s activity isn’t evenly spread across the period, a seasonal business, for instance, or one with a large one-off transaction late in the year.
- Manual, spreadsheet-based rate application drifting out of sync across entities and reporting periods, so one entity’s translation is quietly using a different rate source or a different cut-off date than another’s, without anyone noticing until the numbers don’t tie out.
That last one tends to be the most damaging in practice, simply because it’s invisible until someone goes looking for it. Getting entity data in through a consistent, automated import process removes a lot of the risk of rates drifting apart between entities in the first place.
Where This Gets Harder at Scale
The mechanics above are manageable for a handful of entities. They get genuinely difficult once a group is running dozens of subsidiaries across multiple functional currencies, all needing to be translated consistently, at the same cut-off, using the same rate sources, every single period.
On top of the translation itself, there’s a reporting obligation sitting right behind it. IAS 21 requires disclosure of the amount of exchange differences recognised in profit or loss, and a reconciliation of the CTA balance at the beginning and end of the period. Producing that reconciliation cleanly, and getting it into the annual report in a form auditors and readers can actually follow, is its own piece of work layered on top of getting the translation right in the first place.
How AARO Supports Currency Translation in Consolidation
This is exactly the kind of process AARO is built around. The AARO Base Package applies closing rate and average rate translation consistently across every entity in the group, at the same cut-off, so one subsidiary’s numbers can’t quietly drift out of step with another’s. The CTA is tracked as its own equity component throughout, rather than something reconstructed manually at period end, and AARO’s acquisition register keeps historical rate treatment intact for equity items as new entities are added to the group over time.
Duni Group, a multinational packaging and table-setting business operating across more than 20 countries, moved to AARO after its previous consolidation system was discontinued. Their group accountant has specifically pointed to the currency translation functionality as one of the improvements that made the biggest difference for their controllers, alongside intercompany matching, particularly when managing reporting across a genuinely multinational structure.
Once the translated figures and the CTA reconciliation are ready, AARO Disclosure exports the relevant reports and note tables directly into MS Word and PowerPoint, with a single-click refresh whenever the underlying numbers change, so the annual report always reflects the current translated figures rather than a stale export from weeks earlier.
Book a demo to see how AARO handles multi-currency consolidation across a real group structure.
FAQs
What’s the difference between functional currency and presentation currency?
Functional currency is the currency of the primary economic environment an entity actually operates in, determined by factors like sales pricing and cost structure. Presentation currency is simply the currency the group chooses to present its consolidated financial statements in, and the two can be different for any given entity in the group.
Why does the currency translation adjustment go through OCI instead of profit or loss?
The CTA reflects a translation effect rather than a realized gain or loss from the group’s actual trading activity. IAS 21 requires it to be recognized in other comprehensive income and accumulated in equity, where it stays until the related foreign operation is disposed of, at which point it’s recycled into profit or loss.
What exchange rate should be used for income statement items under IAS 21?
Technically, the rate at the date of each transaction. In practice, most groups use an average rate for the period as a reasonable approximation, unless exchange rates have moved significantly during that period, in which case using an average can distort the results and a more precise approach is needed.
What happens to the CTA when a foreign subsidiary is sold?
The cumulative CTA relating to that subsidiary is reclassified from equity into profit or loss as part of calculating the gain or loss on disposal. This is why disposals of long-held foreign subsidiaries can produce a much larger reported gain or loss than the operating performance alone would suggest.
Can a subsidiary’s functional currency differ from the currency it invoices in?
Yes, and this is more common than people expect. Functional currency is determined by the underlying economic environment, pricing influence, cost structure, financing, not simply by which currency appears on an entity’s invoices. A subsidiary can invoice customers in one currency while its functional currency, based on the indicators in IAS 21, is actually different.