Cost of a charge as invoiced by the invoice issuer in a given billing period.

Identifier for the owner of the datacenter estate. Should be used as an index to identify the P&L organization owning a Data Center or set of Data Centers. In small environments will likely match HostProviderName, larger environments may map to different subsidiaries “Acme Asia-Pacific Infrastructure Pty Ltd”, “Acme North America Technology Operations Inc”.

A Billing Account Name is a display name assigned to a billing account. Billing accounts are commonly used for scenarios like grouping based on organizational constructs, invoice reconciliation and cost allocation strategies.

Represents the currency that a charge was billed in (“USD”, “CAD”, “EUR”, …etc).

Billing interval (monthly or quarterly); Should be considered in the amortization period of the Data Center itself.

Billing interval (monthly or quarterly); Should be considered in the amortization period of the Data Center itself.

Classification of charge (“Usage”, “Purchase”); Primarily usage category, as taxes, corrections, credits are less likely in the Data Center.

A Charge Description provides a high-level context of a row without requiring additional discovery. This column is a self-contained summary of the charge’s purpose and price. It typically covers a select group of corresponding details across a billing dataset or provides information not otherwise available.

Indicates how often a charge will occur. The Charge Frequency is commonly used to understand recurrence periods (e.g., monthly, yearly), and differentiate between one-time and recurring fees for purchases.

The start/end time period for when the usage occurs (hourly or daily). Likely artificially batched for capital depreciated asset usage.

The start/end time period for when the usage occurs (hourly or daily). Likely artificially batched for capital depreciated asset usage.

Contracted Cost represents the cost calculated by multiplying contracted unit price and the corresponding Pricing Quantity. Contracted Cost is denominated in the Billing Currency and is commonly used for calculating savings based on negotiation activities, by comparing it with List Cost. If negotiated discounts are not applicable, the Contracted Cost defaults to the List Cost.

Effective Cost represents the amortized cost of the charge after applying all reduced rates, discounts, and the applicable portion of relevant, prepaid purchases (one-time or recurring) that covered this charge. The amortized portion included should be proportional to the Pricing Quantity and the time granularity of the data. Since amortization breaks down and spreads the cost of a prepaid purchase, to subsequent eligible charges, the Effective Cost of the original prepaid charge is set to 0. Effective Cost does not mix or “blend” costs across multiple charges of the same service. This cost is denominated in the Billing Currency. The Effective Cost is commonly utilized to track and analyze spending trends.

This column resolves two challenges that are faced by practitioners:

1. Practitioners need to amortize relevant purchases, such as upfront fees, throughout the commitment and distribute them to the appropriate reporting groups (e.g., tags, resources).

2. Many commitment discount constructs include a recurring expense for the commitment for every billing period and must distribute this cost to the resources using the commitment. This forces reconciliation between the initial commitment row per period and the actual usage rows.

An Invoice Issuer is an entity responsible for issuing payable invoices for the resources or services consumed. It is commonly used for cost analysis and reporting scenarios.

Cost calculated by multiplying List Unit Price and the corresponding Pricing Quantity. Generally zero for usage lines, can be retail price for purchase lines.

The volume of a given SKU associated with a resource or service used or purchased (vCPU-hours, GB-months, GB transfer), based on the PricingUnit.

SKU level specified measurement unit (GB) for determining unit prices, indicating how the provider rates measured usage and purchase quantities.

The physical data center ID (internal).

Identifier assigned to a resource by the service provider.

The name identifier within the physical data center.

Category of the resource (VM, Volume) or SKU representation level (Cluster).

Linked to layer (“Compute”, “Databases”, “Networking”). Broad classification, derived from the rate card.

Internal name of the offering or tier. Linked to layer (“Compute”, “Databases”, “Networking”).

A SKU ID is a provider-specified unique identifier that represents a specific SKU. SKUs are quantifiable goods or service offerings in a FOCUS dataset that represent specific functionality and technical specifications.

Each SKU ID represents a unique set of features that can be sold at different price points or SKU Prices. SKU ID is consistent across all pricing variations, which may differ based on multiple factors beyond the common functionality and technical specifications.

SKU ID should be consistent across pricing variations of a good or service to facilitate price comparisons for the same functionality, like where the functionality is provided or how it’s paid for. SKU ID can be referenced on a catalog or price list published by a provider to look up detailed information about the SKU. The composition of the properties associated with the SKU ID may differ across providers. SKU ID is commonly used for analyzing and comparing costs for the same SKU across different price details (e.g., term, tier, location).

Ownership or metadata for allocation/reporting/invoicing/chargeback.