How to Build a Finance Department Foreign Currency Exposure Log That Keeps Translation Risk Visible

Finance teams at US companies with international operations often discover their currency exposure at the worst possible moment: during close, when a rate move has already hit the income statement and no one can explain exactly where it came from. A foreign currency exposure log does not eliminate that risk, but it does make the risk visible, owned, and reviewable before the damage is done.

Why a Dedicated Log Is Worth the Effort

Many finance departments track currency in passing. Payables knows some invoices are denominated in euros. Treasury knows the company has a GBP-denominated revolver. The subsidiary controllers know their local books are in Canadian dollars. But that knowledge rarely lives in one place, and it rarely gets reviewed on a regular cadence against current exchange rates.

The exposure log creates that single place. It is not a sophisticated hedging model. It is a structured register that forces every relevant position into view on a schedule, so leadership can make deliberate decisions rather than reactive ones.

What the Log Should Capture

The foundation of any useful exposure log is a consistent set of fields applied to every position. Consider including the following for each entry:

Currency and counterparty. Identify the currency code and, where relevant, the counterparty or subsidiary that owns the position. A British pound receivable from a UK customer and a British pound payable to a UK supplier both belong in the log, even though they partially offset each other.

Exposure type. Distinguish between transaction exposure (a specific receivable, payable, or loan denominated in a foreign currency) and translation exposure (the net assets of a foreign subsidiary that must be converted at period-end rates). The two require different thinking and, potentially, different responses.

Notional amount in foreign currency. Record the face amount in the original currency, not a converted figure. Converting at entry locks in a rate that will be stale within weeks.

Expected settlement or measurement date. Transaction exposures have a natural end date, whether it is a payment due date or a contract maturity. Translation exposures are ongoing but should be reviewed at each reporting period. Capturing dates helps the team prioritize which positions need attention soonest.

Functional currency equivalent at last review. Re-translate each position at the current spot rate during every review cycle and record the result. Comparing this figure period-over-period shows how rate movements are affecting the portfolio without requiring a formal mark-to-market process.

Hedge status. If a position is covered by a forward contract, an option, or a natural hedge, note that here. Unhedged positions should be clearly visible so they do not get assumed to be covered by default.

Owner. Every line needs a named owner in the finance department, someone responsible for updating the entry, flagging changes, and escalating if a position grows unexpectedly.

How to Build the Initial Version

Start by gathering input from four sources: accounts receivable aging (look for non-USD invoice currencies), accounts payable aging (same filter), the treasury team's debt and investment schedules, and the consolidation team's list of active foreign subsidiaries.

For a company with limited international activity, this initial population exercise might take a few hours. For a company with ten subsidiaries across seven currencies, it may take a week of coordinated data gathering. Either way, the log starts with what you know and gets refined over time.

For subsidiaries, an important nuance is that translation exposure is roughly equal to the subsidiary's net assets in local currency. A hypothetical example: if a German subsidiary carries 4 million euros of net assets, a one-cent move in the EUR/USD rate produces roughly a 40,000 USD change in the cumulative translation adjustment on the consolidated balance sheet. Capturing that math in the log, even as a rough estimate, helps leadership understand what they are holding.

Review Cadence and Meeting Integration

An exposure log that is updated once a quarter is better than nothing, but it may still leave the team reacting to surprises. A monthly review cadence, timed to align with the close process, tends to work well for most companies. The reviewer re-translates each position, notes any new positions that emerged during the month, flags positions where the exposure has grown beyond a materiality threshold, and confirms that hedges are still in place and current.

Building that review into an existing close meeting, rather than creating a separate meeting, increases the likelihood it actually happens. A standing agenda item titled something like "currency exposure update" keeps the discipline without adding calendar burden.

Setting Materiality Thresholds

Not every position warrants equal attention. Setting a simple materiality threshold helps the team focus energy on positions that can actually move the needle. A suggested approach is to define a threshold in terms of potential income statement impact. If a rate move of five percent on a given position would produce a variance of less than some defined dollar amount (a figure your company would consider immaterial), that position can be reviewed less frequently and documented with less detail.

Positions above the threshold deserve more scrutiny: more frequent re-translation, active consideration of whether a hedge is appropriate, and direct visibility to the CFO or treasurer on a regular basis.

Common Gaps to Watch For

Three gaps tend to surface once a team starts building their first exposure log.

First, intercompany loans in foreign currencies are often overlooked. An intercompany receivable denominated in a foreign currency at the US parent level creates real transaction exposure that shows up in other income or expense when rates move. These are easy to miss because they feel like internal transactions.

Second, multi-currency bank accounts sometimes sit outside the treasury team's normal view, particularly for recently acquired subsidiaries. A quick review of the banking relationships across all entities during the initial build can surface balances that were not on anyone's radar.

Third, long-term purchase agreements with pricing set in a foreign currency create transaction exposure over their entire term, not just for the next payment. Capturing the full notional exposure from a multi-year contract gives a more accurate picture than recording only the near-term obligation.

The Practical Payoff

The exposure log does not need to be sophisticated to be useful. A well-maintained spreadsheet with consistent fields and a reliable monthly review beats an elaborate system that gets ignored. The goal is to make currency risk a visible, recurring topic in the finance team's routine rather than an occasional surprise that requires explanation after the fact.

When an auditor or audit committee asks how the company monitors foreign currency risk, a clean, current exposure log is a direct and credible answer. When leadership asks why translation adjustment moved by a significant amount, the team has the data to explain it. That combination of defensibility and predictability is the practical payoff for the modest effort required to keep the log current.