Keep currencies separate in multi-cloud cost reports
On this page
This check is due for a source refresh. Confirm the current documentation before you rely on provider-specific details.
Mixed currencies can misstate a total, so keep each amount with its currency and document conversion before adding costs. Use BilledCost or EffectiveCost with BillingCurrency, or PricingCurrencyEffectiveCost with PricingCurrency. Skipping this can hide currency effects and make the report untraceable.
What you need first
- Tool
- Use the checklist below beside an existing cost export in a file viewer. Start with its column names and currency values, then record the scope and period. No command-line tool is needed.
- Access
- Ask an authorized billing-data colleague for a read-only export covering the providers, billing accounts, and period you need, plus corresponding issued invoices if reconciling.
- If you do not use that tool
- Send the checklist to your billing-data colleague with the account scope and period. Request the cost and currency field pairs, missing fields, and BilledCost totals grouped by InvoiceId and InvoiceIssuerName.
Why this is worth a look
A combined total can hide which currency each amount represents. FOCUS requires BilledCost and EffectiveCost to use BillingCurrency, while PricingCurrencyEffectiveCost uses PricingCurrency and follows EffectiveCost's pricing adjustments, amortization, and exclusions. Choosing billed or effective cost also changes how commitment purchases are recognized, so use one basis for the report.
Run this check
CHECKLISTComplete this read-only review beside an existing export. Use an authorized colleague's results if you cannot view it. Record scope, period, currency units, and policy decisions without changing source data.
SCOPE
Providers and billing accounts: __________________________
Billing-period or charge-period start and end: ___________
Export version for each provider: ________________________
Report purpose: __________________________________________
Chosen cost basis (BilledCost or EffectiveCost): __________
Required reporting currency: _____________________________
SOURCE REVIEW
[ ] Record each distinct BillingCurrency: ________________
[ ] Keep BilledCost and EffectiveCost in BillingCurrency units.
[ ] Check whether PricingCurrencyEffectiveCost is provided.
[ ] If used, record its PricingCurrency values: __________
[ ] Do not assume PricingCurrency is the same across exports.
[ ] Keep different currency totals separate until a conversion policy is approved.
REPORTING POLICY, RECOMMENDED NOT REQUIRED FOCUS FIELDS
Policy owner and version: ________________________________
Rate source: _____________________________________________
Source currency -> reporting currency: ____________________
Rate and multiply/divide direction: _______________________
Rate date and effective-date rule: ________________________
Rounding precision and stage: _____________________________
[ ] Keep original amounts and currencies beside separately labelled reporting amounts.
[ ] For Microsoft exports, retain x_BillingExchangeRate and its determination date when supplied. It multiplies pricing currency into billing currency.
[ ] Do not assume a provider rate converts to the report's required currency.
INVOICE VALIDATION, WHEN NEEDED
[ ] Use complete issued-invoice data, not only a department or service slice.
[ ] Sum source BilledCost for each InvoiceId and InvoiceIssuerName.
[ ] Compare with the corresponding invoice payable amount using the FOCUS Rounding Variance Tolerance.
Unresolved differences or missing fields: _________________
Review owner: ____________________________________________How to confirm it
- 01
Choose the report's cost basis
Use BilledCost for invoiced cost, budgeting, or cash-based forecasting. Use EffectiveCost for costs recognized in the charge period, including recognized portions of related purchases. Record the accounts and period before comparing exports.
- 02
Check currency pairs in each export
Match each cost field to its currency using the checklist. Check the actual export version rather than assuming providers expose identical columns. Treat PricingCurrencyEffectiveCost as conditional, not as a field every export must contain.
- 03
Approve the reporting conversion
Ask the finance owner to approve the reporting currency, rate source, direction, date rule, and rounding policy before combining currencies. Keep these reporting controls separate from FOCUS source fields. Do not label a currency-driven difference as a usage change without further analysis.
- 04
Validate invoices in source currency
Compare BilledCost totals by InvoiceId and InvoiceIssuerName with each issued invoice, within the FOCUS Rounding Variance Tolerance. Use the whole invoice for this comparison, not a converted reporting total. Request complete invoice data when the report includes only part of an invoice.
Before making changes
Assume this review starts with an existing FOCUS export and a defined account scope and period. Field availability varies by export version, so do not invent missing columns. Conversion and retention rules are recommended reporting policies, not FOCUS requirements. Microsoft's x_BillingExchangeRate converts pricing currency to billing currency, not necessarily to the reporting currency. Preliminary invoice amounts can differ before an invoice is issued.