How ASC 830 Governs Foreign Currency Gains and Losses

A subsidiary's functional currency is the currency of the primary economic environment it operates in, usually the local currency if it's a self-contained operation, but sometimes the parent's currency if the subsidiary is really just an extension of the parent's operations with limited local autonomy. This isn't a free choice; ASC 830 lays out specific indicators, such as cash flow, sales market, financing source, and intercompany transaction volume, that point toward one answer or the other.

Document the functional currency determination and the indicators that support it when the subsidiary is set up, not retroactively when an auditor asks, since the reasoning needs to reflect the actual facts at the time, not a justification constructed after the fact.

Once functional currency is determined, translating the subsidiary's financials into the reporting currency for consolidation produces a translation adjustment, and that adjustment goes into accumulated other comprehensive income on the balance sheet, not through the income statement. This is the detail that surprises people building their first international consolidation: a large currency swing can move equity significantly without touching reported net income at all.

This is different from remeasurement, which applies when the functional currency isn't the local currency, and does flow through the income statement, so getting the functional currency call right upfront determines which treatment applies.

When a subsidiary's functional currency is the parent's currency rather than the local currency, its local-currency transactions get remeasured into the functional currency, and the resulting gain or loss does hit the income statement, unlike a translation adjustment. This typically applies to a subsidiary that's more of an operational extension than an independent business, holding mostly monetary assets and liabilities in a currency that isn't its functional one.

This distinction is exactly why the functional currency call matters so much: the same underlying currency movement produces a very different financial statement impact depending on which mechanism applies.

A few recurring issues in practice:

• Never formally documenting the functional currency determination, leaving it implicit in how the books happen to be kept
• Changing functional currency informally when a subsidiary's business model shifts, without the specific justification and disclosure ASC 830 requires for a change
• Confusing translation adjustments and remeasurement gains or losses when explaining FX-related equity or income statement movement to leadership
• Not revisiting the functional currency determination when a subsidiary's actual operations change significantly from what it looked like at setup

Most of these surface for the first time during an audit, which is a more expensive place to discover them than during a quarterly close review.

A clean quarterly close process reviews both translation adjustments in equity and any remeasurement gains or losses in the income statement, with a clear explanation for leadership of what's driving each one, currency movement, not operational performance. Payroll and expense platforms like Deel and Navan generally aren't where ASC 830 accounting happens, but the cross-border payroll and travel and expense spend they process feeds into these calculations, so clean data from both helps a clean close.

Check with your accountant or auditor on the specific functional currency and remeasurement treatment for each subsidiary, since getting it right depends on facts specific to how each entity actually operates.