Cloud spend KPIs relate a period's cloud cost to something finance and management judge: revenue, the budget, the forecast, the owners, the discounts and the product's output. Such a measure is comparable only once four things are fixed: formula, scope, period and cost basis. Leave one open and two reports show two values for the same month, both correctly calculated. How a measure becomes a team's target is covered in cloud cost targets.
How it works
Each measure combines billing data with a second quantity. The symbols: K cloud cost of the scope in the period, U revenue, B budget, P forecast, Z allocated cost, L cost of the same usage at list or contracted prices, E effective cost, Q business volume.
| Measure | Formula | Data from outside billing | Cost basis |
|---|---|---|---|
| Cloud cost as a share of revenue | K / U | revenue for the same period from the accounts | effective cost excluding tax |
| Budget variance | (K − B) / B, plus K − B as an amount | budget per scope | the basis the budget was set on |
| Forecast accuracy | error e = (K − P) / P per month; accuracy 1 − mean of abs(e) over several months | stored forecast with its creation date | the basis of the forecast |
| Allocation coverage | Z / K | tags and rules that define what counts as allocated | effective cost |
| Effective savings rate | (L − E) / L | none | a stated price basis: list or contracted |
| Unit cost | K of a product / Q | volume from product or sales | effective cost |
Written this way, a positive budget variance means an overrun. Forecast accuracy uses the forecast from a fixed point, such as the first day of the month for month end, because a forecast is recomputed with every data refresh; it averages the absolute errors so that over- and underestimates do not cancel. Splitting a budget variance by cause is covered in variance analysis, the savings rate per price basis in effective savings rate: formula and price basis, the denominator of unit cost in unit economics and unit costs.
The cost basis
The same measure changes value with the cost basis. In FOCUS, BilledCost follows the invoice: a prepayment sits in the billing period in which it is invoiced, and the usage it covers shows as zero. EffectiveCost spreads the prepayment or commitment across the usage it covers in each period and sets the purchase itself to zero. The specification assigns BilledCost to invoice reconciliation and to cash-based forecasts and budgets, EffectiveCost to accrual-based reporting and forecasts. Both columns are in the billing currency and include negotiated and commitment discounts; tax lines carry the ChargeCategory Tax. Which basis gives which figure is covered in list, billed, effective and amortized cost, the providers' columns in FOCUS columns and the providers' mapping.
Measures are calculated on closed months, because the current month's data still changes (freshness, restatements and finalisation). Where reporting and billing currencies differ, budget variance compares at the budget exchange rate; otherwise the currency effect sits inside the variance.
Shared definitions
The FinOps Foundation covers measures in the KPIs & Benchmarking capability of its Quantify Business Value domain and keeps, with its community, a KPI library with a definition, formula, examples and data sources per entry (CC BY 4.0). Closest to the six measures are Cloud Spend Percentage of Recurring Revenue, Percentage Variance of Budgeted vs. Actual CSP Cloud Spend, Forecast Accuracy Rate (Spend), Percentage of Costs Associated with Unallocated CSP Cloud Resources as the complement of allocation coverage, Effective Savings Rate Percentage and, for unit cost, entries such as Cost per API Call. Each entry sets its own denominator and sign, not always as the table above does: budget variance there is (B − K) / B, with the opposite sign, and the share of revenue divides the cloud invoice amount by recurring revenue, so it uses the invoice rather than effective cost. Name a measure after the library and you either adopt its definition or state where yours differs.
What it means for your cost
A KPI does not change the invoice; it decides which question gets asked. The six are read together, because each on its own allows a wrong story. The share of revenue is unit cost times volume per unit of revenue: K / U = (K / Q) × (Q / U). If it rises while unit cost stays flat, revenue per unit is falling, which is a pricing or mix question rather than an engineering one. Low allocation coverage makes unit costs too small, because shared and unallocated cost sits in no product. A rising savings rate lowers the price per unit, not the quantity.
So that two readers mean the same number, each measure has a definition record: formula, scope, period, cost basis, currency and rate, data source, owner and the date of the definition. When one of them changes, a new time series starts. In the monthly cloud cost review the measures belong in the pre-read pack, and only a few reach management (cloud cost reporting for management and the board).
For the share of revenue, finance decides which revenue counts, recurring or total, and which cloud costs belong in cost of sales (cloud cost in the P&L, COGS and gross margin). That classification follows the company's accounting policy; where in doubt, the auditor or tax adviser decides.
Where it goes wrong
- Variances that cancel out. Symptom: total variance is near zero although single scopes are far off. Cause: measured on the total only, overruns and underruns offset each other.
- The last forecast compared. Symptom: the forecast looks almost perfect. Cause: the month-end forecast, almost all actuals, was compared instead of one stored at a fixed point.
- Allocation coverage moves with purchases. Symptom: coverage drops in the month of a commitment purchase and recovers afterwards. Cause: on billed cost the purchase sits in the denominator as a central item; effective cost assigns it to the usage.
- A savings rate on two bases. Symptom: two reports give different rates for the same commitments. Cause: one divides by list cost and counts the negotiated discount, the other by contracted cost.
- Unit cost without shared cost. Symptom: unit cost falls while total cost grows faster than volume. Cause: the numerator holds only directly allocated cost, and the share of shared and unallocated cost is growing.
Example
A company buys a commitment at the start of the year with a full prepayment V for twelve months. Other usage costs N per month and revenue is U per month, both constant. On billed cost the share of revenue is (N + V) / U in the purchase month and N / U in the eleven months after. If effective cost spreads the prepayment evenly over the term, the share is (N + V / 12) / U every month. Over the year both bases give the same value, (12 × N + V) / (12 × U). A month-on-month comparison on billed cost, however, shows the purchase month V / U above the months after it, with no change in usage or revenue.
Sources
Read on 2026-10-16. FinOps Foundation KPIs & Benchmarking, FinOps KPIs library with the six entries named above (CC BY 4.0); FOCUS 1.4 Billed Cost and Effective Cost.