Runcost

Periods

Type
timestamp (UTC)
Required
No; absent when the export does not state it
Added in
FOCUS 1.0
Contract name
charge_period_end
Updated

FOCUS column

ChargePeriodEnd

The exclusive end of the charge period. Some exports do not state it, in which case the value is absent rather than assumed, because only the granularity of the source knows where a charge period ends and a guessed end would misplace usage that spans a boundary.

Example

The same hourly charge carries 2026-09-12T15:00:00Z; a daily Azure Cost Details row leaves it empty because the export gives only a date.

Where it comes from, per export

The export column that feeds ChargePeriodEnd 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.

ExportSource columnTransform
AWS Data Exports, FOCUS
ChargePeriodEnd
as is
Azure Cost Management, FOCUS export
ChargePeriodEnd
as is
Azure Cost Details (actual cost)Not carried
Azure Cost Details (amortized cost)Not carried
Google Cloud detailed billing export
usage_end_time
cast to datetime

How Runcost uses it

Runcost keeps the value nullable on purpose and infers the granularity per export, so a missing end never reads as the epoch.

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.

Your bills, in FOCUS, allocated to owners.

Runcost ingests AWS, Azure and Google Cloud exports into this contract and produces statements, forecasts and alerts from it.

Book a call to discuss