Read FOCUS billed cost versus effective cost for GPU spend

Why this is worth a look

FOCUS defines BilledCost as the cost of a charge invoiced by the invoice issuer in a billing period. EffectiveCost applies pricing adjustments and moves the cost of covering charges, including one-time or recurring purchases, to the covered charges they offset. BilledCost is commonly used for invoice reconciliation, while EffectiveCost is commonly used for accrual-based reporting, allocation, chargeback, and spending trends. ServiceCategory is a highest-level service classification, so it supports broad analysis but does not identify GPU usage by itself.

Review the documented FOCUS columns and scope before comparing BilledCost with EffectiveCost. The checklist avoids assuming a warehouse dialect or treating ServiceCategory as a GPU identifier.

READ-ONLY FOCUS REVIEW

1. Confirm the export contains BilledCost, EffectiveCost, BillingCurrency, ServiceProviderName, ServiceCategory, ChargeCategory, BillingPeriodStart, BillingPeriodEnd, ChargePeriodStart, ChargePeriodEnd, and InvoiceIssuerName.
2. Choose one bounded window. Use BillingPeriodStart and BillingPeriodEnd for invoice-cycle reporting, or ChargePeriodStart and ChargePeriodEnd for consumption and commitment-recognition analysis.
3. For BilledCost, verify BillingCurrency before summing. For EffectiveCost, first verify the currency denomination documented for your conformant export. Do not combine unlike currencies.
4. Record ServiceProviderName, ServiceCategory, ServiceName, and any export-specific mapping used to identify the intended workload. ServiceCategory values such as Compute or AI and Machine Learning are not GPU identifiers.
5. If investigating commitments, inspect CommitmentDiscountId and CommitmentDiscountStatus. For unit cost, use a documented quantity and unit only when their meaning is established as consistent across the selected rows; otherwise report monetary totals without dividing by quantity.

How to confirm it

1. 01

   Set the reporting question

   Choose BillingPeriodStart and BillingPeriodEnd for invoice-cycle reporting. Choose ChargePeriodStart and ChargePeriodEnd when studying when resources were consumed or commitments were recognized. Use a bounded window that covers the relevant periods.

2. 02

   Verify monetary comparability

   BilledCost must be denominated in BillingCurrency. Before summing EffectiveCost with it, verify the currency denomination documented for EffectiveCost in your conformant export. Keep unlike currencies separate, and include ServiceProviderName in the reporting scope.

3. 03

   Identify the intended workload

   ServiceCategory supports broad provider and architecture analysis, with allowed values including Compute and AI and Machine Learning. It is a highest-level service classification, not a GPU identifier. Review ServiceName and any export-specific documented mapping, but do not claim a GPU total unless that mapping identifies the workload.

4. 04

   Investigate cost differences

   Compare BilledCost and EffectiveCost only after the provider, currency treatment, category, and selected period are aligned. Differences can reflect covering charges such as commitment discount purchases, prepayments, or marketplace purchases. Use CommitmentDiscountId and CommitmentDiscountStatus where available.

5. 05

   Treat units as documented

   The FOCUS evidence lists PricingQuantity with PricingUnit and ConsumedQuantity with ConsumedUnit, and demonstrates PricingQuantity with PricingUnit in an EffectiveCost query. Calculate a unit cost only when your documentation establishes that the selected quantity and unit have the same meaning across the included rows. Otherwise keep the comparison to monetary totals.

Primary sources