Why a balanced multi-currency consolidation still might be wrong

I've seen consolidated financial statements that look perfectly fine at first glance. The balance sheet balances, the P&L looks reasonable, and nothing immediately stands out. Then an auditor asks a simple question: Why doesn't the P&L's net income line up with the movement in retained earnings?

If you've been there, you know the feeling. The number balanced, so you assumed it was right, and now you're tracing a discrepancy backwards through three entities and two currencies as your eyes glaze over. Nine times out of ten, in a multinational, the thread leads back to multi-currency consolidation.

Consider a US-based company with subsidiaries in India. The US entity keeps its books in dollars and the Indian entity in rupees. Each set of books may be correct on its own. But the parent company still needs to combine them into one accurate view of the entire business.

Doing that involves more than converting rupees and pounds into dollars and adding up the results. Currency consolidation has two key parts:

• Foreign currency translation: Translate each entity's financial statements into the company's reporting currency.
• Intercompany eliminations: Remove intercompany transactions such as revenue, expenses, loans, receivables and payables between entities so internal activity doesn't inflate the consolidated numbers.

Get either part wrong, and the problem can surface in retained earnings, the cumulative translation adjustment (CTA), or elsewhere in the consolidated statements.

That's what makes multi-currency consolidation challenging. The numbers don't just need to balance; they need to reflect what actually happened across the company.

Multi-currency consolidation, explained with an example

Let me make multi-currency consolidation concrete with a simple example.

Say a US parent company sells to customers and records its financials in US dollars (USD). It also has an Indian subsidiary that employs a local team and pays salaries and operating expenses in Indian rupees (INR).

Three currency terms help explain what happens next:

• Functional currency: The currency an entity primarily operates in. In this example, the US parent's functional currency is USD, while the Indian subsidiary's is INR.
• Reporting currency: The currency used to present the company's consolidated financial statements. If the US parent reports the group in USD, the Indian subsidiary's INR financials must be translated into USD before consolidation.
• Transaction currency: The currency used for a specific transaction. For example, the Indian subsidiary could buy software from a US vendor and receive a $10,000 invoice. The transaction currency is USD, even though the subsidiary's functional currency is INR.

Now suppose the US parent transfers $100,000 to India. At an exchange rate of INR 80 per USD, the Indian subsidiary receives ₹8 million and uses that money to pay salaries and other operating costs.

This is where currency consolidation becomes important. If the US parent records an internal charge, its Indian subsidiary may record the corresponding amount as intercompany income. Simply adding the two sets of books would then include activity that happened within the company, not with an external customer or supplier.

The company needs to do two things: translate India's INR financials into USD and remove the relevant intercompany transactions. The result should show the economic activity of the US parent and Indian subsidiary as one business, rather than two companies doing business with each other.

The FX rules: Which rate goes where?

Once every entity's financials need to be presented in one reporting currency, the next question is: Which exchange rate should you use?

The most common mistake I see, and the one that distorts equity, is grabbing a single month-end rate and applying it to the entire balance sheet. It feels efficient, but it's wrong, and you won't notice that distortion until something downstream won't tie.

There isn't one rate for the whole statement. The right rate depends on what you're translating and when the activity happened. The three rates you'll see most often are the average rate, closing rate, and historical rate.

Average rate

The average rate is the average exchange rate over a reporting period, such as a month, quarter, or year. It is commonly used to translate P&L items because revenue and expenses occur throughout the period rather than on one specific day.

For example, suppose the Indian subsidiary incurs ₹8 million in salary expenses throughout the year. If the average exchange rate for the year is INR 80 per USD:

₹8 million ÷ 80 = $100,000

Using an average rate gives a reasonable representation of the exchange rates in effect while those expenses were incurred.

Closing rate

The closing rate is the exchange rate on the last day of the reporting period. It is generally used for monetary balance sheet items such as cash, accounts receivable, and accounts payable because these balances represent what the company owns or owes at that date.

Suppose the Indian subsidiary has ₹8 million in cash on Dec. 31, when the exchange rate is INR 100 per USD.

That cash translates to: ₹8 million ÷ 100 = $80,000

Notice that the same ₹8 million translates to $100,000 using the average rate but $80,000 using the closing rate. That's not an error. The two rates answer different questions.

Historical rate

The historical rate is the exchange rate that applied when the original transaction occurred. It is relevant for certain equity items, such as contributed capital, because those amounts may have entered the business years earlier.

Suppose the US parent invests $100,000 in its Indian subsidiary when the exchange rate is INR 80 per USD.

The Indian subsidiary receives and records:

$100,000 × 80 = ₹8 million

Now assume the closing rate has moved to INR 100 per USD. Translating that same contributed capital at today's rate would produce $80,000, even though the original investment was $100,000. Using the historical rate preserves the value associated with the original transaction.

Certain assets may also require historical-rate treatment depending on the applicable accounting policy.

Here are the questions each rate answers:

‍

Where does constant currency fit into this picture?

Constant currency is different from all three. It isn't an exchange rate used to perform foreign currency translation for consolidation. It's a management view used to understand business performance without the effect of changing exchange rates.

For example, suppose the Indian subsidiary's revenue increases from ₹80 million to ₹88 million, a 10% increase. But INR weakens against USD during the year. After translation, USD revenue might appear to have grown only 4%.

Management now has two effects mixed together: the business grew, but the currency weakened. Constant-currency analysis applies a consistent exchange rate across the periods to answer a simpler question:

How much would revenue have grown if exchange rates had stayed the same?

That distinction matters in multi-currency consolidation. Average, closing, and historical rates help translate the financial statements correctly. Constant currency helps management understand the business performance behind the translated numbers.

Intercompany transactions and eliminations: The heart of consolidation

Translating every entity into the same reporting currency solves only half the problem. The next step is dealing with intercompany transactions — transactions between different entities in the same company.

Why? Because from the company's perspective, you can't generate revenue by selling something to yourself, and you can't owe money to yourself.

Building on my earlier example, suppose the Indian subsidiary provides support services to the US parent and invoices ₹8 million. Let's assume that at the transaction date, assume INR 80 per USD, making the invoice worth $100,000.

The two entities may record:

‍

Both sets of books can be correct individually. But if we simply add them together, the consolidated P&L would include $100,000 of revenue and $100,000 of expense from a transaction that happened entirely within the company. The problem is, moving money around within a company isn't revenue or an expense, so this distorts the numbers.

Intercompany eliminations address this problem. During consolidation, finance removes the following transactions from both sets of books:

• Intercompany revenue against the corresponding expense.
• Intercompany receivables against the corresponding payables.
• Intercompany loans against the corresponding obligations.
• Other internal transfers and balances between group entities.

The goal is for the consolidated financial statements to show the company as one business dealing with external customers, suppliers and lenders, rather than a parent company and its subsidiaries doing business with each other.

What happens when exchange rates change?

Multi-currency consolidation makes these eliminations harder because the two entities may record the same transaction in different currencies, but exchange rates change continuously.

So, in the previous example, India initially would record a receivable of ₹8 million when the exchange rate is INR 80 per USD, or $100,000. Now, let's assume the invoice remains unpaid until period-end, and by that time, the exchange rate has moved to INR 100 per USD.

Because the receivable is still outstanding, its value has to be remeasured at the period-end exchange rate. The ₹8 million receivable is now worth $80,000, compared with $100,000 when the invoice was first recorded. This change in value is an example of how FX gains and losses can arise when exchange rates move. Finance still needs to reconcile the receivable in India's books with the corresponding payable in the US books and calculate any FX-related difference before performing the elimination.

This is why foreign currency translation and intercompany eliminations have to work together. When the balances don't match, it's tempting to book a plug, a journal entry for whatever amount makes the elimination net to zero and charge it to FX gain/loss or CTA. Finance needs to determine whether the difference comes from exchange rates, timing, the underlying transaction or an accounting error.

A good intercompany elimination answers two questions: Does this transaction belong in the company's financials, and if not, can we correctly reconcile both sides before removing it?

CTA, retained earnings, and the tricky parts of FX translation

At this point, I have explained how to translate the P&L and balance sheet using different exchange rates. That creates another question: What happens to the differences caused by those rates?

This is where the CTA becomes important. CTA captures the cumulative effect of translating a foreign subsidiary's financial statements into the group's reporting currency as exchange rates change over time. It is typically recorded within equity, separate from net income, rather than flowing through the P&L.

Let's continue with my US and India example.

Suppose the Indian subsidiary has:

• Assets and liabilities translated at the closing rate.
• Current-period income translated using an average rate.
• Contributed capital translated at the historical rate.

Because these rates are different, the translated pieces may not naturally produce the same balance sheet relationship they had in INR. CTA captures the translation difference created by bringing those amounts into USD.

Why retained earnings can get tricky

Retained earnings represent profits accumulated over multiple periods. The challenge is that those profits may have been earned when exchange rates were very different.

For a simplified example, suppose the Indian subsidiary earns:

‍

Ignoring dividends and other adjustments, the two years contribute $200,000 of translated profit to retained earnings.

Now suppose the closing rate at the end of Year 2 is INR 100 per USD. If you simply take the accumulated ₹17 million and translate the entire balance using that closing rate, you get:

₹17 million ÷ 100 = $170,000

That's $30,000 less than the $200,000 of profit translated over the two periods.

The example is simplified, but it illustrates an important point: retained earnings carry history with them. You can't assume that all accumulated profits arose at today's exchange rate. Retained earnings is a figure you build up, not one you translate. You take each period's net income, convert it at that period's average rate, and accumulate: $100,000 from Year 1 plus $100,000 from Year 2. You never translate the ending ₹17 million balance at one rate, because that balance was never earned at one rate.

CTA shouldn't become a plug

This, in my experience, is the easiest trap to fall into. The balance sheet is off by $30,000. It's late, the close is due, and there's a line called CTA sitting right there that's supposed to absorb translation differences. So you drop the $30,000 into it. The balance sheet balances. You move on.

Six months later, an auditor pulls that thread, and it turns out that the $30,000 wasn't a translation adjustment at all. It was a missed intercompany elimination hiding inside the plug. Now it's not a close adjustment; it's a restatement conversation. Balancing the balance sheet never proved the $30,000 was real. The CTA should capture legitimate translation differences, not become a catch-all for anything finance can't immediately explain.

A useful rule of thumb I’d recommend: Don't just ask whether the balance sheet balances. Ask whether you can explain why CTA has the value it does.

If you want to go deeper into the accounting mechanics and calculations, I’d recommend this detailed guide to cumulative translation adjustments.

Different ownership structures, ERPs, and real-world scenarios

So far, I’ve used a simple example: a US parent with an Indian subsidiary. In practice, multi-currency consolidation gets harder as companies add entities, investors, currencies and financial systems.

Three factors create much of that complexity: ownership, currency volatility and data structure.

Ownership determines how an entity enters the consolidated financials

Not every company in a group is 100% owned.

Suppose the US parent owns 100% of its Indian subsidiary. This is the simplest scenario because there are no outside shareholders whose share of the subsidiary needs to be presented separately.

Now suppose the parent owns 80% and outside investors own the remaining 20%. If the parent controls the subsidiary, the company may consolidate the subsidiary's financials and separately recognize the portion attributable to other shareholders as non-controlling interest (NCI). The accounting standards that govern this treatment aren't limited to publicly traded companies. Private companies also follow applicable accounting standards when determining how subsidiaries and other investments should be accounted for. The existing draft introduces this distinction as part of the ownership challenge.

Note: The rules for multi-currency consolidation depend on the accounting framework a company follows.

1. Under IFRS, IAS 21 (The Effects of Changes in Foreign Exchange Rates) governs foreign currency translation, while IFRS 10 (Consolidated Financial Statements) covers consolidation requirements.
2. Under US GAAP, ASC 830 (Foreign Currency Matters) addresses foreign currency translation and remeasurement, while ASC 810 (Consolidation) governs consolidation.

For example, if the subsidiary earns $100,000 in translated net income, some of that income belongs economically to the outside shareholders. The consolidation process needs to reflect that ownership split rather than treating the entire amount as belonging to the parent.

When the parent doesn't have the same level of control, a different accounting approach, such as the equity method, may apply. The key point is that ownership affects how an investment is accounted for, so finance teams need to establish the relationship with each entity before consolidation.

Volatile currencies can make performance harder to interpret

Exchange rates also don't move in neat, predictable increments. In 2025 alone, EUR/USD moved from just above 1.02 in January to close to 1.16 by the end of October—a 14% increase in less than a year.

Suppose the Indian subsidiary generates ₹100 million in revenue in both Year 1 and Year 2. Its local-currency revenue hasn't changed. But imagine the relevant exchange rate moves from INR 80 per USD to INR 100 per USD.

• At INR 80 per USD: ₹100 million ÷ 80 = $1.25 million
• At INR 100 per USD: ₹100 million ÷ 100 = $1 million

The business generated the same ₹100 million, but its translated USD revenue fell by $250,000.

Sharp currency movements can therefore create significant changes in consolidated results even when the underlying business is relatively stable. Finance teams need to distinguish operating performance from the effects of foreign currency translation. The original draft also highlights currency volatility as a real-world complication.

Different ERPs create a different kind of consolidation problem

Then there's the data itself.

Imagine the US and Indian entities use different enterprise resource planning (ERP) systems. Even something as basic as payroll might appear differently:

‍

The company can't reliably consolidate these accounts until it knows they represent the same type of expense.

That's why finance teams typically need to map local charts of accounts into a "global"  chart of accounts for the company. This kind of ERP data consolidation helps bring data from different systems into a consistent structure before it flows into the consolidated financials. Otherwise, similar transactions may end up in different consolidated accounts simply because the subsidiaries use different systems or naming conventions.

These challenges also tend to compound. A finance team may need to consolidate an 80%-owned subsidiary that operates in a volatile currency, uses a different ERP, and has intercompany transactions with several other entities.

At that point, reliable currency consolidation depends on more than FX calculations. Finance needs consistent accounting rules, ownership data, and account mappings before it can create an accurate company view.

How to build and validate a multi-currency consolidation process

I've learned to do almost nothing in the reporting currency until the local books are clean. Every time I've seen someone trying to shortcut that—translate first, fix later—they’ve just ended up with a wrong balance sheet in a different currency. A reliable process starts before you translate a single number: clean local books, consistent mappings, clear FX rules. If you get those wrong, the errors just get harder to see in consolidation.

I recommend working through it in this order:

1. Collect and validate each entity's trial balance

Start by collecting the trial balance from every entity you plan to consolidate. Then confirm that each entity's local books are complete and balanced.

For example, if the Indian subsidiary's balance sheet doesn't balance in INR, converting it to USD won't solve the problem. It will only give you an incorrect balance sheet in a different currency.

2. Map local accounts to a common chart of accounts

Different entities may use different ERPs and account names. Map these local accounts to a common company structure before combining them.

For example:

‍

This ensures that economically similar transactions end up in the same place in the consolidated financials.

3. Identify the currencies involved

Next, determine each entity's functional currency and the group's reporting currency.

For our US and India example:

• US parent: USD functional currency.
• Indian subsidiary: INR functional currency.
• Consolidated group: USD reporting currency.

Also, identify transactions denominated in currencies other than an entity's functional currency. This helps finance understand where additional FX-related differences may arise.

4. Apply the appropriate FX rates

Define which rates apply before performing foreign currency translation. As we covered earlier, that could mean an average rate for P&L activity, a closing rate for monetary balance sheet items and historical rates for relevant equity balances.

The important control here is consistency. Finance should be able to answer: Which rate did we use for this account, and why?

5. Translate and consolidate the financials

Translate each foreign entity's financial statements into the company's reporting currency and bring the results together.

At this stage, however, you're not finished. The combined numbers can still contain transactions between different entities in the company.

6. Reconcile and eliminate intercompany transactions

Match intercompany transactions before eliminating them. This includes revenue and expenses, receivables and payables, loans, and other internal balances.

For example, if the US parent shows a $100,000 payable to India, finance should be able to trace it to the corresponding receivable in India's books. If the translated amounts don't match, investigate whether the difference comes from timing, exchange rates or an accounting error before making the intercompany elimination.

7. Validate CTA and retained earnings

Next, review the CTA. It should reflect genuine differences created by translating financial statements at different exchange rates, not serve as a plug for unexplained discrepancies. When CTA doesn't tie, don’t start by adjusting CTA. Instead, work backwards through the things that masquerade as translation differences.

First, does net income on the P&L match the movement in retained earnings? Second, does the closing cash balance on the cash flow statement match the bank balance on the balance sheet? Third, does the balance sheet still refuse to balance even after a correctly calculated CTA? The issue could be a missed elimination, a timing difference, or an incorrect exchange rate. The important thing is to identify the cause before making any adjustment to CTA.

Retained earnings also deserve a separate check because they contain profits accumulated across periods with different historical exchange rates.

8. Check the consolidated financial statements

Finally, review the P&L, balance sheet, and cash flow statement together. Don't stop at "Does the balance sheet balance?" Ask:

• Do changes in retained earnings make sense relative to net income?
• Have all material intercompany balances been eliminated?
• Can we explain the CTA?
• Were the correct FX rates applied consistently?
• Can we trace consolidated numbers back to the underlying entities?

These checks create an audit trail from the local trial balances to the final group financials.

That's ultimately what makes a currency consolidation process reliable: finance can explain not only what the consolidated number is, but also where it came from and why it is correct.

What good multi-currency consolidation looks like

Good multi-currency consolidation goes beyond converting every subsidiary's numbers into one currency and checking whether the balance sheet balances. It creates one accurate and explainable view of the entire company.

If the consolidated P&L changes, finance should also be able to distinguish a change in the underlying business from one caused by foreign currency translation or exchange-rate movements.

This brings us back to the discrepancy I mentioned earlier: the P&L's net income doesn't line up with the movement in retained earnings. When net income and the movement in retained earnings don't reconcile, finance needs to trace the difference to its source.

That's the real test of a strong currency consolidation process: The numbers balance, but more importantly, finance knows why they balance.