ChargeFrequency
Charge Frequency · Cost and Usage dataset
- Feature level
- Recommended
- Data type
- String
- Allows nulls
- No
- Column type
- Dimension
What it is
Charge Frequency indicates how often a charge will occur. Along with the charge period related columns, the Charge Frequency is commonly used to understand recurrence periods (e.g., monthly, yearly); forecast upcoming charges; and differentiate between one-time and recurring fees for purchases.
Allowed values
| One-Time | Charges that only happen once and will not repeat. One-time charges are typically recorded on the hour or day when the cost was incurred. |
| Recurring | Charges that repeat on a periodic cadence (e.g., weekly, monthly) regardless of whether the product or service was used. Recurring charges typically happen on the same day or point within every period. The charge date does not change based on how or when the service is used. |
| Usage-Based | Charges that repeat every time the service is used. Usage-based charges are typically recorded hourly or daily, based on the granularity of the cost data for the period when the service was used (referred to as charge period). Usage-based charges are not recorded when the service is not used. |
Requirements (4)
Verbatim from the specification. These are the statements the validator checks against.
- ChargeFrequency MUST be of type String.
- ChargeFrequency MUST NOT be null.
- ChargeFrequency MUST be one of the allowed values.
- ChargeFrequency MUST NOT be "Usage-Based" when ChargeCategory is "Purchase".
Check your own export
The FOCUS 1.4 validator checks this column and 122 others against your file, in your browser, with no size cap and nothing uploaded.
Other Cost and Usage columns
BillingCurrencyBillingPeriodEndBillingPeriodStartCapacityReservationIdCapacityReservationStatusChargeCategoryChargeClassChargeDescriptionChargePeriodEndChargePeriodStartCommitmentDiscountCategoryCommitmentDiscountIdCommitmentDiscountNameCommitmentDiscountQuantityCommitmentDiscountStatusCommitmentDiscountType
Definition taken from the FOCUS 1.4 specification. FOCUS is published by the FinOps Foundation under CC BY 4.0.
One column is a definition. A pipeline is a project.
Finitizer ingests FOCUS from every provider you run and reports across all of them.