Paying a cloud invoice in euros and reporting cloud cost in euros solve different problems. AWS or Azure may invoice in EUR while list prices or analysis views use another currency. Adding those values without a method creates a misleading total.
Record three currency roles
| Role | Question |
|---|---|
| Pricing | Which currency defines the rate or contract? |
| Billing and payment | Which currency appears on the invoice and bank charge? |
| Reporting | Which currency does management use for budgets? |
AWS payment currency can depend on seller and payment profile, while Cost Explorer displays USD. Under a Microsoft Customer Agreement, Azure pricing is defined in USD and converted for billing. A current retail price conversion should not be used to recreate a past invoice.
For a EUR management view, decide per data source whether to use the invoice's EUR amount or convert a source-currency cost at a documented rate and date. Preserve the original amount and currency; never convert an amount already billed in EUR again. Record rounding and any missing rate as an unresolved item, rather than a zero.
When the monthly trend moves, separate usage, price, contract and FX effects. A UK subsidiary may need a GBP local view and an EUR group view. Both can be valid, but each needs a named conversion rule and a report date. Mixed-currency arithmetic is not a cost metric.
Read next
AWS and Azure invoices: checking EU reverse charge, finance solution and effective cost in the glossary.
Sources and method
Checked on 25 September 2026: AWS Cost Explorer currency, Microsoft billing FAQ. The tables and review steps are Costfluent recommendations.
