Investigate a cloud bill increase systematically
On this page
Use this recommended worksheet method: choose one cost basis, compare two periods, and document currency, scope, and filters before reviewing provider-native cost drivers. Rank dimensions within each provider, then map their meanings before making a cross-cloud summary.
Why this is worth a look
This is an investigation method and set of worksheet assumptions, not a claim that providers expose identical fields. FOCUS identifies Service Name as a Cost and Usage dimension commonly used for aggregate trends and anomaly investigation. FOCUS describes SKU Price ID as a provider price-list reference consistent across periods and billing accounts within a provider, which can help track price fluctuations. AWS Cost Comparison covers top changes across services, accounts, and Regions, including usage and discount changes. Google documents separate reports for billing trends, invoice details, charges and credits, and SKU prices. Azure documents anomaly details, removed costs, changed costs, and replacement meters after resource changes.
Run this check
CHECKLISTA manual, read-only worksheet for comparing two periods. It has no cloud execution surface and requires no permissions. Record units and currency for every amount, and map provider fields before any cross-cloud summary.
Question: Why did cost change from __________ to __________?
Current period: __________ to __________ Complete: [ ]
Comparison period: __________ to __________ Complete: [ ]
Provider and native scope for each period: __________
Recommended cost basis selected: __________
Currency and conversion method, if any: __________
Current total and unit: __________ Prior total and unit: __________ Delta: __________
1. Record the comparison inputs
- Period completeness or corrections noted: __________
- Report or export and filters used: __________
- Scope and charge inclusion used: __________
2. Rank dimensions within each provider
- Service Name or provider service: __________
- Provider-native account, project, subscription, or region: __________
- Mapping used before a cross-cloud summary: __________
3. Inspect leading movements
- SKU ID and SKU Price ID, where available: __________
- Charge category and class, where defined: __________
- Resource or meter change documented: __________
4. Separate possible causes
- Usage quantity and unit: __________
- List or contracted unit price and pricing tier: __________
- Discounts, credits, purchases, taxes, or adjustments: __________
- Supporting provider report or invoice detail: __________
5. Confirm ownership and explanation
- Resource or workload owner: __________
- Confirmed cause and evidence reference: __________How to confirm it
- 01
Set the comparison basis
As a worksheet recommendation, select one basis, such as billed cost or effective cost, and record it. Write down the two periods, provider-native scope, report or export, filters, units, currency, and any conversion method. Mark incomplete or corrected periods instead of treating their totals as final.
- 02
Rank each provider separately
Use each provider's native views before combining results. FOCUS Service Name is a Cost and Usage dimension commonly used for aggregate trends and anomaly investigation. AWS Cost Comparison covers services, accounts, and Regions. Google billing reports separately show service, project, and region views. Treat the cross-cloud mapping of labels as an explicit worksheet assumption, not as a provider-defined equivalence.
- 03
Review SKU and price evidence
For leading movements, record provider-native SKU and charge fields. Where FOCUS data is available, SKU Price ID references a provider price-list entry and remains consistent across periods and billing accounts within that provider. Google cost tables list service IDs, SKU IDs, and project numbers. Google pricing reports show list and contract prices and separate tier rows when applicable.
- 04
Separate usage from bill items
As a safety recommendation, compare quantity and unit price only when the source defines compatible units and the applicable tier or negotiated treatment. Otherwise, record the fields without multiplying them. Use Google's cost breakdown report to record contract pricing, usage-based credits, taxes, and adjustments. For Azure, drill into anomaly details and check whether a stopped or changed resource produced a removed cost or a replacement meter, then confirm the explanation with the responsible team.
Before making changes
Assumptions: both periods are available; their scope, report or export, filters, units, and currency can be recorded; and any conversion method is applied consistently. These are worksheet controls, not rules established by the supplied provider documentation. Provider-native dimensions are not automatically equivalent across clouds. FOCUS SKU Price ID is conditional and may be null for some charge cases. Google has separate report types, and Azure anomaly alerts are unavailable in Azure Government and other sovereign clouds. The worksheet does not establish invoice completeness or root cause.