Currency and FX Rate Selection in Cross-Border M&A Precedent Analysis
A cross-border deal adds a currency layer to every multiple. Which exchange rate to use, and where to find it, for deal price and financial metric alike.
A domestic precedent set carries one currency throughout — the deal price, the enterprise value, and the financial metric all denominate in the same unit, so the multiple is internally consistent. A cross-border set does not come with that guarantee. The deal price may be stated in US dollars. The target’s EBITDA is disclosed in euros. The analyst’s workbook is in sterling. Each combination requires an explicit currency choice, and each undocumented choice is a potential source of silent inconsistency in the final multiple.
This guide sets out the two FX problems that arise in a cross-border precedent set, the exchange rate conventions practitioners use to resolve them, how accounting standards affect the financial metric before the analyst opens a spreadsheet, and what to record for each transaction.
Why the currencies do not automatically cancel
A multiple such as EV/EBITDA is dimensionally consistent only when numerator and denominator share a currency. When both the EV and the EBITDA denominate in euros, the unit cancels and the multiple is a pure number. The problem arises in two scenarios.
Scenario 1: deal price and financial metric are in different currencies. A US acquirer announces a $2.4 billion offer for a French target. The target’s most recent annual report discloses LTM EBITDA of €180 million. To form EV/EBITDA, the analyst must either convert enterprise value to euros or convert EBITDA to dollars using a specific exchange rate.
Scenario 2: the analyst is normalizing a mixed-currency set. A practitioner building a precedent set for a UK target draws transactions from North America, Europe, and Asia. Without a common currency, the multiples are individually valid but not comparable on a single scale. Converting all deals to a base currency requires an explicit rate for each.
Neither problem has a single universally correct answer. What matters is consistency: the same rate convention applied uniformly across the set, with the rate source and date recorded for every transaction.
The four exchange rate conventions
Four conventions are in common use for cross-border deal work. Each has a rationale and a natural use case.
Spot rate at announcement. The market rate on the day the transaction is publicly announced is the most widely used convention for converting the deal enterprise value. The rationale is that the announcement is the economic event: the deal price represents the agreed value as of that date, and the FX rate in effect that day reflects the market’s contemporaneous view. The Federal Reserve H.10 release publishes daily historical spot rates against the US dollar. Central bank equivalents publish rates for other base currencies.
Using the announcement date is straightforward when the deal closes quickly. For transactions that take nine to eighteen months to complete with material rate movement between announcement and close, some analysts note the closing-date rate alongside the announcement-date rate and document the sensitivity.
Spot rate at close. When a deal’s economic substance is tied to the closing event — particularly when cash consideration was settled at close using a currency-conversion mechanism specified in the merger agreement — the closing-date spot rate may be the more accurate figure. The merger agreement filed as an exhibit to Form 8-K sometimes specifies the FX rate or the rate-setting date. If the agreement fixes a rate, use it and cite the filing.
Average rate over the financial period. When the purpose is to convert the financial metric rather than the deal price, the period average is more appropriate than a single-day spot rate. Under both IAS 21 and ASC 830, income statement items in foreign-currency financial statements are translated into the presentation currency using the average rate for the reporting period. Applying the same period-average rate to re-express an EBITDA figure into a different currency is internally consistent with how the target originally reported it. Companies disclose the average rate used for translation in their financial statement notes, and that disclosed rate is the most defensible source.
Balance sheet closing rate. Under IAS 21 and ASC 830 (current-rate method), balance sheet items are translated at the period-end closing rate. If an analyst needs to re-express a target’s balance sheet items — including the cash and debt that feed into the net debt bridge — to a common currency, using the closing rate stated in the filing produces results consistent with how the company presented those figures.
How accounting standards affect the EBITDA before you begin
When a target’s functional currency differs from its presentation currency, the translation has already occurred by the time the annual report is published. The EBITDA the analyst reads in the filing is already a translated figure. No further rate sourcing is needed unless the analyst wants to re-express it in a different base currency.
Under IAS 21, the current-rate method applies when the functional currency differs from the presentation currency. Income statement items are translated at the average rate for the period; balance sheet items at the closing rate. Exchange differences are recognised in other comprehensive income, not in profit or loss. The result is an EBITDA figure that embeds a blended rate across the year — consistent within that filing, but potentially not directly comparable to another filing covering the same period at a different average rate.
Under ASC 830 (FASB), the same principle applies when a foreign subsidiary’s functional currency is not the US dollar (the current-rate method). Where the foreign entity’s functional currency is the US dollar — because it operates primarily in USD even while located in a foreign jurisdiction — the temporal method applies instead. The temporal method translates monetary items at current rates and non-monetary items at historical rates, which can produce a materially different EBITDA in the presentation currency.
The practical implication for a precedent analyst: the EBITDA disclosed in a public filing is already a translated figure. Knowing which method was applied, and at what average rate, determines whether two EBITDA figures from different jurisdictions are directly comparable.
Where to find exchange rates
For spot and average rates, primary sources include:
- Federal Reserve H.10 release. Daily noon buying rates against the US dollar, with data from 1971. This is the standard US-government source for historical FX data and the most commonly cited source for cross-border M&A analysis involving dollar-denominated deal prices.
- Company financial statement disclosures. The notes to any foreign-currency financial statement will state the average rate and closing rate applied. For the period-matched average rate on a target’s income statement, this is the authoritative source because it is the exact rate the company used.
- Merger agreement exhibit to Form 8-K. Where the deal specifies an FX mechanism, the agreement sets the rate or the rate-setting date. Use it and cite the accession number.
For analysts building a precedent set across many currencies, the company’s own disclosed rate for each filing period is the most defensible single source for the income statement metric. Spot rates from a named central bank source are appropriate for deal-price conversion.
Constructing a multiple across currencies: worked example
A US acquirer announces the acquisition of a German target. The Form 8-K discloses an offer implying an enterprise value of $4.2 billion. The target’s Form 20-F discloses LTM EBITDA of €280 million and states an average EUR/USD translation rate of 1.095 for the period.
Step 1 — convert EV to the target’s currency. Find the EUR/USD spot rate on the announcement date from the Federal Reserve H.10. Suppose it is 1.082. Enterprise value = $4,200M ÷ 1.082 = €3,882M.
Step 2 — apply the company-disclosed average rate to express EBITDA in dollars (optional cross- check). €280M × 1.095 = $306.6M. EV/EBITDA in dollars = $4,200M ÷ $306.6M = 13.7×.
Step 3 — verify consistency. EV in euros ÷ EBITDA in euros = €3,882M ÷ €280M = 13.9×. The 0.2-turn difference reflects the rate spread between the announcement-date spot (1.082) and the period-average (1.095). Both are valid computations but they are not the same multiple; the analyst must document which one was used and why.
Step 4 — record the rates. Footnote: “EV converted at EUR/USD 1.082 (announcement date, Federal Reserve H.10). EBITDA expressed in euros as reported (Form 20-F LTM period). Period-average rate disclosed in Form 20-F notes: 1.095. Multiple computed on euro-denominated inputs.”
A 5% rate difference between the spot conversion and the period average translates to a 5% difference in the expressed multiple. In a fairness analysis, that gap is material and must be explained, not glossed over with a single undocumented number.
Currency and AI-assisted valuation
For a language model querying a deal database, currency is a field that must be tagged on every value, not inferred from context. An EV of 3,882 and an EBITDA of 280 produce a multiple of 13.9 if both are in euros — or a nonsensical 0.07 if the model treats one as millions and the other as billions because no unit was recorded. More subtly, a model comparing a 13.9× euro-denominated multiple to a 12.4× dollar-denominated multiple without knowing the exchange rates and their as-of dates cannot determine whether the difference is real or artefactual.
The AI-ready precedent transaction data schema sets out how to tag currency at the field level: the currency of each consideration component, each financial metric, and the exchange rate and source used for any conversion should be explicit record fields, not spreadsheet assumptions. The reported vs. calculated multiples guide covers the related provenance requirement — a multiple calculated using an undocumented FX rate is no more reproducible than a multiple with an undocumented EBITDA period.
Common errors
Applying a deal-date spot rate to the income statement metric. The announcement-date spot rate is the right choice for converting the deal price; it is not appropriate for converting LTM EBITDA, which represents a twelve-month average of income. Use the period average — preferably the company’s own disclosed rate — for income statement items.
Converting in only one direction. Converting the deal price to the analyst’s base currency while leaving the financial metric in the target’s reporting currency produces a multi-currency numerator and denominator. Every value in a given multiple must be in the same currency before the division is performed.
Ignoring translation effects on the net debt bridge. Under IAS 21, net debt items are translated at the balance sheet closing rate, not the income statement average. Applying the same average rate to the entire EV bridge mixes rate conventions and produces a bridge that does not foot.
Failing to record the source. An exchange rate without a named source and a date is not reproducible. A different analyst, or an automated system, cannot verify or reconstruct the multiple.
Treating the reported multiple as currency-neutral. A reported multiple from a fairness opinion is stated in a specific currency and embeds the adviser’s own FX convention. If the adviser converted from a foreign currency, the proxy may not disclose the rate used. Treating the stated figure as directly comparable to a calculated multiple built in a different currency or with a different FX method introduces hidden inconsistency.
Documentation checklist
For each cross-border transaction in a precedent set, record:
| Item | What to record |
|---|---|
| Deal price currency | As stated in the Form 8-K or announcement |
| EV conversion | Rate used, named source (H.10, central bank, merger agreement), as-of date |
| Financial metric currency | As disclosed in the annual report or proxy |
| Financial metric conversion | Period-average rate; prefer company-disclosed rate from the filing notes |
| Net debt currency | Balance sheet closing rate and source |
| Base currency for the multiple | The single currency in which EV and EBITDA are both expressed |
| Rate spread noted | Whether announcement-date spot and period-average differ materially |
Applying this checklist consistently eliminates the most common source of multiple inconsistency that does not arise from EBITDA definition or financial period differences — currency choice that is present but unrecorded.
Related articles: Equity Value vs Enterprise Value in an Acquisition, Net Debt in M&A: What to Include, Exclude, and Where to Find Each Component, LTM vs NTM Multiples in Precedent Transactions, Reported vs. Calculated Multiples in Precedent Transactions, AI-Ready Precedent Transaction Data Schema, Where to Find M&A Deal Terms in Non-US Jurisdictions.
PrivyLogic stores deal values with currency-tagged fields and disclosed exchange rates where available in the underlying filings. Review access options or contact the team for an enterprise query.
Sources
- IAS 21 The Effects of Changes in Foreign Exchange Rates — IFRS Foundation; accessed September 22, 2026
- Accounting Standards Codification — ASC 830 Foreign Currency Matters — Financial Accounting Standards Board (FASB); accessed September 22, 2026
- Foreign Exchange Rates (H.10) Statistical Release — Board of Governors of the Federal Reserve System; accessed September 22, 2026