Agency reporting in multiple currencies: convert before combining spend
Combine agency ad spend across currencies with preserved native amounts, a documented exchange-rate rule, a worked example and human review checks.
To combine advertising spend in different currencies, preserve each source amount and its currency, choose one reporting currency, and convert using a documented rule before adding the results. If a currency or required exchange rate is missing, hold the affected total for review. Changing a currency symbol is not conversion. This guide gives a small agency a reproducible reporting method; it does not select accounting policies or authorize payments.
Keep source currency separate from reporting currency
A client may ask for one spend total even when its advertising accounts use different currencies. Start by identifying the currency of each exported amount and whether the source or connector already converted it. Google Ads exposes an account currency_code and defines it as the immutable currency in which the account operates. That is an account-level fact to retain with the export, rather than infer from the client's location. [1]
Croissant recommends three separate fields: native amount, native currency and reporting amount with reporting currency. Retain the source account reference, reporting period and extraction time beside them. A dollar sign alone is ambiguous; use explicit codes such as USD or CAD. If the export is already converted, record its output currency and conversion basis instead of converting it a second time.
This article covers the money conversion step before an agency rollup. Our weekly reporting guide covers collection and reconciliation, while the campaign ratio guide explains aggregation after compatible inputs exist. Currency conversion does not resolve different attribution rules, overlapping rows or mismatched reporting windows.
Write a rate rule that another colleague can reproduce
Before building the calculation, have the reporting owner and account lead agree the target currency, permitted rate source, rate date convention, conversion direction, missing-rate behavior and rounding rule. Decide whether the report uses daily conversion or an explicitly agreed period rate. These are Croissant's recommended operating decisions, not a universal vendor formula. A weekly export alone cannot reproduce a daily conversion method without the necessary daily amounts.
If considering ECB reference rates for an informational report, check coverage and suitability first. The ECB quotes currencies against the euro and normally publishes updates on working days, with specified closing-day exceptions. It describes these rates as informational and strongly discourages their use for transactions. A reporting reference rate must not be presented as the actual rate charged by a bank or used to settle a client invoice. [2]
Record the rate's effective date separately from the time you downloaded it. For a non-publication day, follow the owner's explicit rule, such as using the most recent available permitted rate and displaying its date. Do not let AI invent a weekend rate, silently substitute a different provider or choose a policy from whichever number looks most convenient. Missing coverage should create an exception.
Worked example: two currencies, one checkable total
Every amount and rate in this example is synthetic. Fictional Client A has USD 1,000 of spend in one account and EUR 800 in another for the same agreed reporting window. Assume these are non-overlapping media-spend rows and the reporting owner has approved USD as the reporting currency with one illustrative period rate: 1 EUR equals 1.10 USD.
Keep the USD row at USD 1,000. Convert the EUR row as 800 EUR multiplied by 1.10 USD per EUR, giving USD 880. The combined reporting total is USD 1,880. Adding 1,000 and 800 first would produce a meaningless mixed-currency 1,800; relabeling it USD would conceal the problem. The converted figure is a reporting calculation, not evidence of cash paid or campaign success.
If the rate were expressed in the opposite direction, as EUR per USD, the formula would divide the EUR amount by that rate. Store the direction in words or units with the value. A positive rate can still be the wrong rate when used backwards. Have the reviewer independently reproduce at least one conversion and check that native and reporting currency match the approved rule.
Now remove the EUR rate from the test. The output should show the verified USD subtotal of 1,000, the unconverted EUR 800 row and a combined total marked unavailable. It should not call USD 1,000 the complete client spend. If an approved daily method is required but only a weekly EUR total exists, route that mismatch for review rather than pretending the period-rate example satisfies the daily policy.
Build calculations first and give AI the checked result
Implement the conversion in a spreadsheet or explicit calculation step. Keep native values unchanged, join each permitted row to the applicable approved rate, and retain the rate reference. Use sufficient calculation precision and round for display under the agreed rule; document whether displayed component rows can differ slightly from a total calculated before rounding.
Give AI the accepted total, currency label, included accounts, reporting window, rate basis and exceptions. A useful synthetic draft is: 'Included media spend totals USD 1,880 using the approved illustrative period rate; native inputs are USD 1,000 and EUR 800.' A person checks that wording before it becomes a client statement. AI should not fetch an arbitrary live rate, select a new reporting policy or infer that exchange-rate movement explains campaign performance.
Keep cost and revenue conversions consistent with their respective approved definitions before calculating a return measure. A dimensionless ratio does not make incompatible money inputs comparable. Also keep media spend distinct from taxes, agency fees and bank charges unless the report explicitly includes those items. An exported media metric is not a reconciled invoice.
Test failure cases and keep business decisions human-owned
Test a missing currency, a reversed pair, a missing rate, an already-converted export and a rate dated outside the agreed policy. Include a same-currency row that needs no conversion. Confirm that an unavailable source remains unavailable rather than becoming zero, and that the workflow cannot mix client accounts when assembling the report.
Have a reporting owner check the arithmetic and an account lead approve the client-facing explanation. Rate-source changes, revised conversion policies and replacement issued reports need explicit review. Keep payment reconciliation, invoicing and accounting judgments with the responsible human. A reporting automation must not change ad budgets or distribute a report solely because the calculation completed.
A protected spreadsheet may be sufficient for a few consistent exports. Consider a connected workflow when collection, currency labeling and exception routing repeatedly consume review effort. Use the reporting demo to frame the conversation, then describe your source tools and a fictional currency example through the Croissant contact form. Leave client exports and credentials out of the initial enquiry.
Implementation checklist
- Record native amounts, explicit currency codes and whether the source already converted them.
- Approve reporting currency, rate source, date rule, direction and rounding before implementation.
- Retain rate references and effective dates with the source snapshot.
- Convert compatible rows before adding; preserve the original native values.
- Hold complete totals when a required source, currency or permitted rate is missing.
- Test reversed rates, prior conversion and non-publication days with synthetic data.
- Require human review of the report; keep payment and accounting decisions separate.
The sources behind the sauce.
Primary research and official documentation behind the cited points. The workflow examples and checklists are Croissant’s own guidance.