How a DTC Brand Reconciles Multi-Currency ROAS for a Board Meeting
Alessandro Conti
Senior Performance Marketer
A direct-to-consumer brand selling into the US, UK and EU has a deceptively hard reporting problem: the board wants one return-on-ad-spend number, but the spend happens in dollars, pounds and euros, and the obvious way to combine them is quietly wrong. This is the story of one finance-minded marketer's dtc multi-currency roas reconciliation workflow — normalizing three currencies at the day-of-transaction rate so the board sees a single ROAS that ties to revenue instead of approximating it.
Quick answer: A DTC marketer reconciles multi-currency ROAS by normalizing each channel's spend at the day-of-transaction rate — valuing each day at that day's rate — into one reporting currency, then reading a blended ROAS that ties to the books. Delivered as a scheduled export, the board gets a single number that reconciles to revenue, with the per-market breakdown underneath it.
The brand here is a composite drawn from common DTC patterns, but the currency failure and its fix are exactly what real finance-minded marketers hit.
The number that would not tie out
The marketer's job before each quarterly board meeting was simple to state and miserable to do: produce one ROAS figure for the quarter across every channel and every market. The brand ran Meta, Google and TikTok in three currencies. Revenue came back in the same three currencies through the store. The board reported in euros.
The manual method was to pull spend per platform, pull revenue, pick an exchange rate, convert everything to euros, and divide. And every quarter the same thing happened: finance compared the marketer's blended ROAS against the company's actual revenue and spend in the ledger, and the numbers did not match. Not wildly — a few percent — but enough that the board's first question was always "why doesn't this tie to the accounts?" instead of "what does this tell us?"
The most damaging gap in a board deck is not a big error — it is a small one finance can see. When the marketing ROAS misses the ledger by a few percent every quarter, the board stops asking what the number means and starts asking why it is wrong. Once one figure is in doubt, the whole deck is.
That gap between a reported number and a reconciled one is the exact problem dissected in why multi-currency ROAS doesn't add up: the issue is rarely the data and almost always the conversion method sitting on top of it.
The real failure: one rate cannot represent a quarter
The marketer was not careless. The method was wrong. Converting a quarter of multi-currency spend with a single exchange rate — a quarter-end spot rate or a rough average — assumes every transaction happened at that one rate. But spend in dollars on the 3rd of October and spend in dollars on the 28th of December occurred at two different rates, and the ledger booked each at the rate of its own day.
So a single-rate conversion values the whole quarter as if it were one moment in time. The total drifts from the books, and the drift is not random — it tracks however much the currency moved over the period. In a volatile quarter, that is the difference between a ROAS the CFO signs off on and one they flag. The denominator of the ROAS — total spend in euros — was simply computed by a method the accounts did not use.
A single exchange rate cannot represent a quarter of spend that happened across ninety days at ninety rates. Currency drift is a method error, not an effort error — no amount of recomputing fixes a conversion that approximates what the ledger records exactly. The fix is valuing each day's spend at that day's rate, the way the books already do.
This is the same denominator problem that distorts the headline metric in the reported-versus-true-ROAS framework: when the spend figure underneath ROAS is computed wrong, every ratio built on it is slightly fictional, and the board is reading fiction.
The switch: normalize per day, in one cross-channel view
The brand moved reporting onto Wevion and the conversion method changed at the foundation. Spend now converts at the day-of-transaction rate: each day's spend in each currency is valued at that day's rate, across every connected channel, automatically. The euro total for the quarter is the sum of correctly-valued days, not one rate stretched over ninety.
With the denominator fixed, the ROAS came together in a single cross-channel view. The view blended Meta, Google and TikTok across all three markets into one normalized currency, divided reconciled revenue by reconciled spend, and produced one blended ROAS — with the per-channel and per-market breakdown sitting underneath it for any board member who wanted to see where the number came from.
Day-of-transaction normalization was the whole unlock. The board ROAS stopped being a negotiation with finance and became a figure they trusted on sight, because each day's spend was valued exactly the way the ledger valued it. The number tied out by construction, not by the marketer reworking the conversion until it happened to match the accounts.
The mechanics of doing this correctly — per-day rates, closed-period stability, audit traceability — are walked step by step in how to reconcile ad spend across currencies, and they are the reason the quarterly review stopped opening with a challenge to the math.
The stability the CFO actually wanted
There was a second benefit the finance team cared about as much as accuracy: a closed period that stays closed. Under the old spot-rate method, re-pulling last quarter's ROAS in a later month returned a different total, because the single rate used had changed. A number that moves when you re-read it is, to a CFO, a number you cannot audit.
With day-of-transaction normalization, a closed quarter is valued at the rates from the days it occurred — and those days are in the past, so the total is fixed. Re-pull Q3 in any later month and it returns the same euros. The marketer stopped getting questions about why last quarter's figure had drifted, because it no longer did.
A closed period that never moves is the difference between a metric finance tolerates and one they reconcile against. When last quarter's ROAS returns the same total every time it is re-read, the board can tie it to a settled ledger — and the quarterly review turns from an audit of the arithmetic into a conversation about the budget.
The cadence: schedule it, then interpret it
The final change removed the manual assembly entirely. The currency-normalized cross-channel view is delivered as a scheduled export on the board's cadence, so the report builds itself and arrives reconciled. The days the marketer used to lose pulling platforms, converting currencies, and rebuilding the deck came back.
What did not get automated — deliberately — is the interpretation. The board does not want a normalized data dump; it wants to know what the blended ROAS means for next quarter's budget allocation across markets and channels. The marketer's hour now goes there, to the analysis, instead of to assembly and currency math. The same scheduling pattern, applied to the full monthly pack, is the subject of the DTC board-report scramble case study, which traces how automating assembly raises report quality rather than lowering it.
One honest note the marketer accepted easily: Wevion syncs platform data on a roughly 15-minute cadence rather than instantly. For a quarterly board ROAS covering a settled period, that window is invisible — a board figure reflects closed months, not the last minute.
What other DTC teams can take from this
The brand's problem is the default for any e-commerce operation selling across borders. The lessons generalize cleanly:
- The drift is in the method, not the data. A single exchange rate over a multi-day, multi-currency period will not tie to the books. Day-of-transaction normalization is what makes ROAS reconcile.
- Fix the denominator first. ROAS is only as trustworthy as the spend figure beneath it. Normalize spend per day before you compute a single ratio.
- Demand closed-period stability. A figure that changes when re-read cannot be audited. Per-day rates keep a closed quarter fixed.
- Schedule the assembly, keep the human on the meaning. Let the report build and reconcile itself; spend the recovered hour explaining what the blended ROAS implies for the budget.
The stakes scale with how much of the business sells across borders. Statista reported in 2024 that cross-border e-commerce continues to grow as a share of global online retail, so more DTC brands are booking spend and revenue in several currencies at once. And a 2024 Gartner finance survey found that manual, spreadsheet-driven reporting remains one of the most error-prone steps in the monthly close — exactly the step day-of-transaction normalization removes from the board ROAS.
For the alternatives side by side, reconcile ad spend across currencies lays out the methods, and scheduled ad reports that stop manual exports covers the cadence side. To weigh a dedicated DTC analytics tool against this approach, the Triple Whale comparison sets the options out — including the question most analytics tools never answer: once you see the ROAS, can you act on the campaigns in the same place, or only watch them?
Wevion's plans start at a permanent free tier (€0), then Starter at €99/mo, Pro at €499/mo, and Plus at €1,499/mo (€1,199 annual, billed yearly at -20%), with Enterprise as a custom plan, and every paid tier includes a 14-day trial that coexists with the free plan. For the broader picture of how reporting overhead caps DTC growth, the campaign-scaling cluster connects the reporting layer to the operations around it.
The board does not need a more confident marketer defending the math. It needs one ROAS that ties to the books. Value each day at its real rate, normalize across every channel, schedule the delivery, and walk into the meeting with a number nobody questions — so the conversation can finally be about strategy instead of arithmetic.
Najczęściej zadawane pytania
The Ad Signal
Cotygodniowe spostrzeżenia dla media buyerów, którzy odmawiają zgadywania. Jeden e-mail. Tylko konkrety.
Powiązane artykuły
Why Your Multi-Currency ROAS Never Adds Up Across Markets
When clients and markets bill in different currencies, your blended ROAS stops being a number and becomes an argument. Spend in dollars, euros and pounds refuses to sum, FX timing quietly shifts last month's "final" figures, and the number your finance team trusts never matches the one your ad dashboards show. This is why multi-currency reconciliation breaks — and what actually fixes it.
How to Reconcile Ad Spend Across Currencies (Step by Step)
When accounts bill in different currencies, your blended ROAS only matches finance if you fix two things: one conversion rule for everyone, and a closed period that never re-prices itself. This is the step-by-step method — pick the day-of-transaction rate, normalize every account into one view, and run a weekly habit that keeps marketing and finance reading the same number.
How a DTC Brand Killed Its Monthly Board-Report Scramble
Every month, this DTC brand lost three days to building one board-ready ad report — pulling five platforms, reconciling three currencies by hand, and rebuilding the deck the finance team kept rejecting. This is how scheduled, currency-correct exports turned that scramble into a one-hour analytical review.