The standards already say how.
Under US GAAP, ASC 830-30-45-3 translates revenues and expenses at the rate on the date each one is recognized. Because that is impractical, ASC 830-10-55-10 allows an average. The next paragraph, as reproduced in Deloitte’s foreign currency roadmap, adds the condition that matters: the average has to be weighted by the volume of transactions, and the example it gives is to translate each month or quarter at its own average and combine the results for the year.
IFRS lands in the same place. HMRC’s Corporate Finance Manual restates IAS 21 as an average rate where it is a good approximation, and a weighted average or transaction rates where results are seasonal. Its Business Income Manual adds that an average only works if rates do not fluctuate significantly in the period.
Current answers, such as ScaleXP’s help article, explain the mechanics with a profit earned evenly through the year. Even is the one case where the choice of average makes no difference. Here is a year that is not even.
One seasonal year, translated two ways.
The example subsidiary
Group reports in US dollars
Subsidiary keeps its books in euros
Figures in thousands. Every rate and amount
is an example.
Revenue 400 a month January to September,
then 900, 1,400 and 1,900 in Q4
Expenses 450 every month
Profit 2,400 for the year
Monthly average EUR to USD rate
1.04 in January, up 0.01 a month,
1.15 in December
simple average of the twelve: 1.095
Closing rate at 31 December: 1.16| Month | Revenue, EUR | Expenses, EUR | Average rate | Revenue, USD |
|---|---|---|---|---|
| January to September, each month | 400 | 450 | 1.04 rising to 1.12 | 3,888 in total |
| October | 900 | 450 | 1.13 | 1,017 |
| November | 1,400 | 450 | 1.14 | 1,596 |
| December | 1,900 | 450 | 1.15 | 2,185 |
| Year | 7,800 | 5,400 | simple average 1.095 | 8,686 |
Translated month by month, revenue comes to 8,686. That is an effective rate of 1.1136, because most of the euros arrived in the fourth quarter when the rate was highest. Translate the year’s 7,800 at the simple average of 1.095 instead and revenue is 8,541. Expenses fell evenly, so they come to 5,913 either way.
| Line | Each month at its own rate | One average for the year | Difference |
|---|---|---|---|
| Revenue | 8,686 | 8,541 | 145 lower |
| Expenses | 5,913 | 5,913 | the same |
| Profit | 2,773 | 2,628 | 145 lower |
| Profit at the 31 Dec closing rate of 1.16 | 2,784 | 2,784 | the same |
| Translation adjustment on the year’s profit | 11 | 156 | 145 higher |
The 145 does not disappear. The balance sheet is translated at the closing rate whichever average you pick, so the subsidiary’s equity is the same. What changes is the split: one annual average moves 145 thousand dollars out of net income and into the currency translation adjustment in other comprehensive income. That is about 5 percent of the subsidiary’s profit, landing in a line most readers of the accounts skip.
When one average is fine, and when it is not.
Two things have to move together for the shortcut to go wrong: uneven activity and a moving rate. Expenses in the example were flat, so their translation matched to the dollar. If the rate had held at 1.10 all year, revenue would have matched too. Subscription businesses with steady monthly billing can usually use an annual average. Retail, events, agriculture, and anything with a big fourth quarter usually do not.
Some items should skip the average entirely. Deloitte’s roadmap names impairments and certain write-offs: they belong to one day, so they take that day’s rate. Dividends and capital contributions do the same. A large one-off in a month is worth checking by hand.
The practical setup is a table of twelve monthly average rates, each with the date it was taken and its source, kept beside the consolidation. It costs very little to maintain, it answers the auditor’s first question about rates, and it makes a quarter or a year the sum of months you have already closed.
How Rivane picks the rate today.
Rivane runs the consolidated income statement one month at a time, and translates each company at that month’s average rate, so a year built from it follows the month by month method above. Under Close Management, the Exchange Rates screen lists each subsidiary with its closing rate for the balance sheet, its average rate for income and expenses, and a status of Translated or Rate missing.
Rivane consolidation rates, as built
# Rivane consolidation rates, as built.
statement the consolidated income statement is
run for one month at a time, and each
company is translated at that month's
average rate
average rate 1. the approved average rate for the
month, if one has been entered
2. otherwise the mean of the month's
approved daily rates, if there are
at least five dates covering both
halves of the month
3. otherwise the latest rate on or
before the 15th, labelled as a
mid-period approximation
closing rate the latest rate on or before month end
missing rate the group figure is blocked and the
screen shows "Rate missing"; nothing
is ever translated at 1.0
stale rate by default, a rate more than 35
days old is refused rather than used
receipt for each company: the amount in its
own currency, the rate, the rate's
date and source, and which of the
three methods chose it
The rule we would point to first: when a rate is missing, Rivane blocks the group figure instead of adding the subsidiary’s euros to the dollars untranslated. A wrong total that looks finished is harder to catch than a total that refuses to appear.
The limits worth knowing. When Rivane derives an average from daily rates, it is a simple mean of the rates, not weighted by the subsidiary’s own volumes within the month. And every line in a month uses that month’s average, so an impairment or other one-day item is not translated at its own date’s rate automatically. For a seasonal business, the first gap rarely matters at monthly level; the second is worth a manual check in the month it happens.
Twelve rates, added up.
Keep one approved average rate per month for each currency, translate each month at its own rate, and build the year from the months. Check one-day items separately. Then the translation reserve holds only what it should: the gap between average and closing rates, not profit that belonged in the income statement.
To see how Rivane handles groups with more than one company and currency, read the Rivane multi-entity overview.
Frequently asked questions.
Can we translate a foreign subsidiary’s whole year at one average exchange rate?
Only if it gives about the same answer as translating each month at its own rate. ASC 830-10-55-11 says averages must be weighted by the volume of transactions, and gives translating each month or quarter at its own average and adding the results as the example. IAS 21 allows an average only when rates do not fluctuate significantly. With seasonal revenue and a moving rate, one annual average can be materially off.
Where does the difference go if we use the wrong average rate?
The balance sheet is translated at the closing rate either way, so total equity does not change. The difference moves between net income and the currency translation adjustment in other comprehensive income. In the example, one annual average put 145,000 dollars less in net income and 145,000 more in the translation reserve.
Which items should not use the average rate at all?
Items tied to a single date. Deloitte’s roadmap gives impairments and certain write-offs as examples: they should be translated at the rate on the day they are recognized. Dividends and capital contributions also use the rate on their own date.
Sources
- Deloitte, Roadmap: Foreign Currency Matters, section 3.2 Selecting Exchange Rates. Reproduces ASC 830-30-45-3 and ASC 830-10-55-10 and 55-11, including the instruction to translate each month or quarter at its own average rate and combine the results for the year.
- Deloitte, Roadmap: Foreign Currency Matters, section 5.2 Translation Process. Assets and liabilities at the balance sheet rate, income statement items at an appropriate weighted average, and the difference to the currency translation adjustment in OCI.
- HMRC Corporate Finance Manual, CFM64170. Restates the IAS 21 position for tax purposes: an average rate where it is a good approximation, and a weighted average or transaction rates where results are seasonal.
- HMRC Business Income Manual, BIM39510. An average rate is acceptable provided exchange rates do not fluctuate significantly in the period.
- ScaleXP help centre, Why year to date earnings on the consolidated P&L can differ from current year earnings on the balance sheet. Read as a current answer: it explains monthly averages against a closing rate, with an example where profit is earned evenly through the year.
A note on how this was researched. ASC 830-30-45-3 and ASC 830-10-55-10 and 55-11 were read as reproduced on Deloitte’s DART site, and the IAS 21 position as restated in two HMRC manuals; all are HTML pages read directly. The subsidiary, the rates and every amount are examples. The Rivane section describes the product as built today, checked against the consolidation code rather than marketing copy. This is not accounting advice for your specific case.
On embedded social posts: we looked for public posts from standard setters or practitioners on choosing average rates for translation and found none we could verify as current and relevant, so this article uses ordinary citations instead.