One of the most confusing parts of cloud billing is knowing which cost number to look at. Cloud providers offer multiple cost figures for the same line item, and choosing the wrong one leads to incorrect budgets, misleading dashboards, and bad architectural decisions. FOCUS standardizes these into three critical metrics with precise definitions.
1. ListCost — The Sticker Price
Definition: What you would have paid if you had no discounts, no Enterprise Agreement, no Savings Plans, and no negotiated rates. This is the public on-demand price multiplied by usage quantity.
Formula: ListUnitPrice × UsageQuantity
Use Case: Benchmarking the "market value" of your infrastructure. If your ListCost is $100,000 and your BilledCost is $60,000, your effective discount rate is 40%. This is how you measure the value of your commitment programs.
2. BilledCost — The Invoice Number
Definition: What actually appears on your invoice. This is the cash that leaves your account. It includes discounts applied at billing time (like Enterprise Agreement discounts or on-demand discounts) but does not amortize upfront payments.
Use Case: Finance reconciliation. When your CFO asks "how much did we pay AWS in October?", BilledCost is the answer. It matches the invoice line by line.
The critical limitation: If you purchased a 1-year Reserved Instance for $8,760 upfront in January, your BilledCost for that instance in February through December is $0.00. The cash already left. This makes usage look free when it is not.
3. EffectiveCost — The Amortized Reality
Definition: The most important metric for engineers and FinOps practitioners. It takes upfront and recurring commitment-based payments and distributes them evenly across the usage period they cover.
Formula (conceptual): (Upfront Payment / Coverage Hours) + Recurring Hourly Rate
Use Case: True cost allocation and unit economics. If you want to know "what does it actually cost to run this Kubernetes cluster per hour?", EffectiveCost gives you the honest answer — even if the cash was paid months ago.
Example: You pay $8,760 upfront for a 1-year Reserved Instance on January 1st.
- BilledCost in January: $8,760. BilledCost in February: $0.
- EffectiveCost every month: $730 ($8,760 ÷ 12 months).
Using EffectiveCost for showback and chargeback prevents the perverse incentive where teams fight to avoid being the "owner" of a reservation in the month it was purchased, and then treat the resource as free for the rest of the year.
Choosing the Right Metric
| Question | Use This Metric |
|---|---|
| "How much is on the invoice?" | BilledCost |
| "What is the true cost of this service this month?" | EffectiveCost |
| "How much did our discounts save us?" | ListCost − BilledCost |
| "What would this cost at public rates?" | ListCost |
A common FinOps interview question is: "Your team's Kubernetes nodes show $0 cost in the billing dashboard. The engineering manager thinks the cluster is free. What's happening and how do you fix it?" The answer: the nodes are covered by an upfront Reserved Instance or Savings Plan purchase. The BilledCost is $0 because the cash was paid at purchase time. The fix is to switch your dashboard to use EffectiveCost, which amortizes the upfront payment across the coverage period and shows the true hourly cost of running those nodes.