A store sells in euros, an ad account bills in US dollars, and a dashboard displays a single revenue-to-spend ratio. If the calculation divides the original amounts without a conversion policy, the result is not a meaningful business ratio.
Currency reconciliation creates a transparent bridge between source amounts and the common reporting view. It should explain differences rather than hide them with a conversion applied somewhere nobody can identify.
Name the currencies at every stage
List the customer's transaction currency, the store's reporting currency, the advertising account currency, the analytics reporting currency, and the currency used for finance's management report. These can differ within one customer journey.
Include currency codes, not only symbols. A dollar sign alone does not distinguish US, Canadian, Australian, or other dollar-denominated amounts.
Google Analytics' currency reference distinguishes event currency from the property's reporting currency and describes its conversion convention. Your payment processor or finance report can use a different convention. Do not assume all displayed amounts are directly comparable because they originated from the same order.
Preserve the original amount
Keep source amount and source currency as immutable inputs to the reporting calculation. Store the normalized amount separately with the applied rate and rate date.
This makes it possible to reproduce an old report, explain a later restatement, and detect double conversion. If an upstream export is already converted to the reporting currency, converting it again produces a plausible-looking but incorrect number.
The metric dictionary should name the source field and whether it is original or normalized. Avoid fields labeled only “amount” in a multi-currency dataset.
Agree on a management-reporting policy
Choose a documented rate source and date convention with the business's finance owner. Possible management views include transaction-date rates or a consistent planning rate for scenario analysis. The right policy depends on the question being answered.
Keep that analytical choice distinct from formal accounting and settlement records. This guide describes advertising reconciliation, not a substitute for the company's accounting policy.
If the team wants to isolate marketing changes from exchange-rate movement, a constant-currency comparison can be useful. Label it clearly and show how it differs from the actual reported-currency result. Do not silently replace realized amounts with a planning assumption.
Build a currency bridge
| Field | Purpose |
|---|---|
| Source record ID | Links the amount to an order, refund, or spend record |
| Source amount and code | Preserves the original monetary value |
| Amount definition | Gross sale, net sale, tax, fee, spend, or settlement |
| Rate and source | Makes normalization reproducible |
| Rate date | Explains the chosen timing convention |
| Reporting amount and code | Supports the common comparison |
| Exceptions | Missing code, unusual rate, or unresolved discrepancy |
Reconcile totals by currency before combining them. This catches a missing currency group that could be hidden inside a single aggregate.
Work through a simple example
Consider an illustrative campaign with $1,000 of advertising spend and €2,000 of sales. If the agreed analytical rate for the relevant records is $1.10 per euro, normalized sales are $2,200 and the revenue-to-spend ratio is 2.2.
Dividing 2,000 by 1,000 without conversion would produce 2.0, but that number mixes units. The arithmetic is easy; the important work is establishing that the sales definition, rate convention, time window, and spend scope are appropriate.
If the €2,000 includes tax or later refunds while the business's target uses retained merchandise revenue, currency conversion alone does not make the comparison valid. Use the refund-adjusted reporting guide to address that separate issue.
Separate exchange rates from payment fees
A payment settlement can be lower than converted order revenue because of fees, timing, refunds, or other adjustments. Do not attribute the entire difference to exchange rates.
Reconcile the components available in the payment and order records. Show conversion effects and fees separately where the data supports it. If an export combines them, label the limitation rather than inventing a precise split.
The advertising report may need revenue, contribution, or cash depending on the decision. Preserve those distinctions so a cash shortfall does not become an unexplained “ROAS discrepancy.”
Handle refunds and corrections consistently
A refund can occur in a different period from its purchase and may settle under a different rate. Decide whether the management view follows the original order cohort, the refund period, or both in separate reports.
Keep the original purchase and refund linked by a stable order reference. Avoid subtracting a refund twice because it appears in both a net-sales export and a separate adjustment feed.
Document how corrected currency codes or values are restated. An unusually large ratio change may be a data correction rather than a sudden improvement in advertising.
Validate before using the ratio for budgets
Check a sample of orders and spend records manually. Include multiple currencies, a refund, and a record near the reporting-period boundary. Confirm that no missing code defaults silently to the main currency.
Then compare platform ROAS with the normalized business view using the MER and platform ROAS guide. Expect differences when attribution and spend scope differ, even after currency is aligned.
The final reconciliation should identify explained conversion effects, definition differences, and unresolved amounts. Once that bridge is stable, budget discussions can focus on customer economics instead of debating numbers that were never expressed in the same units.