Transaction vs translation exposure
Both are called “FX exposure” and they behave almost nothing alike. Confusing them is how a treasury team ends up hedging the risk it does not have.
Transaction exposure
This is the risk attached to a specific cash flow denominated in a currency other than the entity’s functional currency. A euro invoice owed by a dollar-functional entity, a yen-denominated loan, a signed purchase commitment settling in six months. The rate moves between the date the obligation arises and the date it settles, and the difference is a real gain or loss. It hits profit, and it hits cash.
Translation exposure
This is the risk attached to consolidating a foreign subsidiary. The subsidiary is not doing anything in a foreign currency — from where it sits, everything is local. The exposure exists only because the parent has to restate those books into a different reporting currency. It moves reported equity through the cumulative translation adjustment, and it never moves cash.
Why the distinction matters
They call for different instruments and different justifications. Hedging transaction exposure protects cash and earnings, and the case for it is usually straightforward. Hedging translation exposure protects a reported figure and consumes real cash to do it — which is a harder argument to make, and one reason the share of companies that hedge translation is far smaller than the share exposed to it.
Where teams get it wrong
The common failure is not misunderstanding the definitions. It is that a single consolidated FX line contains both, undifferentiated, so nobody can say how much of a quarter’s currency effect was cash and how much was consolidation arithmetic. The definitions are easy. Separating them in your actual numbers is the work.
See this on your own numbers.
The attribution map is free and built from public filings — the drivers that move the number in your industry, and where peers took the hit. No data required, nothing to sign.