FOCUS column
ChargeFrequency
How often a charge recurs: One-Time for a single purchase, Recurring for a fixed periodic fee such as a support plan or a monthly reservation payment, and Usage-Based for charges that scale with consumption. It separates the predictable part of a bill from the part that responds to behavior.
Example
A monthly reservation installment is Recurring; the compute hours it discounts are Usage-Based; the upfront portion paid at purchase is One-Time.
Where it comes from, per export
The export column that feeds ChargeFrequency in each format the platform ingests, and the transform applied. A format with no row does not carry the column; the value is then absent rather than guessed.
| Export | Source column | Transform |
|---|---|---|
| AWS Data Exports, FOCUS | ChargeFrequency | as is |
| Azure Cost Management, FOCUS export | ChargeFrequency | as is |
| Azure Cost Details (actual cost) | Frequency | values mapped: UsageBased → Usage-Based, OneTime → One-Time, Recurring → Recurring |
| Azure Cost Details (amortized cost) | Frequency | values mapped: UsageBased → Usage-Based, OneTime → One-Time, Recurring → Recurring |
| Google Cloud detailed billing export | Not carried | — |
How Runcost uses it
Runcost forecasts Recurring and One-Time charges from their schedule and Usage-Based charges from trend, which is why the two are forecast separately.
Related columns
About this reference
Generated from the column contract and provider rules that Runcost runs, and written by Faisal Saleem, Founder. The normative definitions are in the FinOps Foundation’s FOCUS specification at focus.finops.org.