Currency & regional settings

AWS bills each account in the local currency configured for it, so an estate that spans regions often has spend recorded in several currencies at once — euros in the EU, rupees in India, pounds in the UK, and so on. CloudQuell consolidates all of it into a single display currency of your choosing, so every dashboard, report, and budget shows one consistent, apples-to-apples number.

Setting your display currency

You choose a display currency when you create your organization, and it stays changeable afterward: an org admin can update it anytime under Settings → Regional Preferences. Organizations that don’t pick one default to USD.

Changing the display currency is an org-wide setting — it applies to everyone in the organization, not just you. Only admins and super_admins can change it; see Roles & permissions. It only changes how amounts are shown — cost data stays stored in the currency it was billed in, so you can switch at any time without losing anything.

Supported currencies

28 currencies are supported:

USD (default), plus EUR, GBP, CAD, AUD, JPY, CNY, INR, BRL, MXN, CHF, KRW, SGD, HKD, NZD, SEK, NOK, DKK, ZAR, PLN, THB, IDR, MYR, PHP, ILS, TRY, SAR, and AED.

How conversion works

Spend is always stored in the currency AWS billed it in, and converted to your display currency when it’s shown. Two things follow from that design:

• Historical reports stay stable. Each charge is converted using the reference rate at the close of the month it was billed, not today’s rate. Anchoring to the end of the billing period keeps a converted total close to the rate your provider uses when it invoices that month, and a report for a past month shows the same totals no matter when you open it — consistent and audit-ready. (The current, still-open month tracks the latest rate and settles to its month-end value once the month closes.)
• No manual maintenance. Exchange rates are sourced from published, ECB-derived reference data and refresh automatically. (The Saudi riyal and UAE dirham are the exception — they track their fixed central-bank USD peg rather than a floating ECB rate.) There’s nothing to upload or maintain.

If your spend is already entirely in USD and your display currency is USD, no conversion happens at all.

Note

Converted amounts use published ECB reference rates, which can differ slightly from the exchange rate your cloud provider applies on its own invoice. For exact reconciliation against a provider invoice, view that account’s costs in the currency it’s billed in.

Where your currency applies

The display currency is used consistently across the product:

• Dashboards and the overview
• Cost reporting, including the report builder and pivot table
• Budgets and budget status
• Commitments — reservations and savings plans
• Savings recommendations
• Anomalies
• AI-spend tracking
• Alert rules and budget alerts — every money threshold you enter (budget targets, spend-threshold amounts, anomaly floors) is interpreted in your display currency, and spend is converted into it before the comparison
• Values returned through the MCP server

Note

The one deliberate exception is the plan-usage spend meter: subscription tiers are defined by USD spend bands, so tracked spend against your plan limit is always measured and shown in USD (and labeled as such), whatever your display currency.

Consolidating multi-region spend

This is the point of the feature. In raw billing data, every line item carries its own currency, so a global total is meaningless until each charge is converted. CloudQuell normalizes each account and region into your display currency before anything is summed, so a single total, budget, or savings figure reflects your whole global estate — no per-region exports, no spreadsheet FX math.

Note

Budgets are always denominated in your organization’s display currency. If you change the display currency, existing budget targets are shown converted into the new currency.