Runcost

Periods

Type
timestamp (UTC)
Required
Yes, on every row
Added in
FOCUS 1.0
Contract name
billing_period_end
Updated

FOCUS column

BillingPeriodEnd

The exclusive end of the billing period: the first instant that belongs to the next period. Together with BillingPeriodStart it defines the invoice interval precisely, so that a charge on the boundary lands in exactly one period and totals never double-count.

Example

For the September 2026 invoice the value is 2026-10-01T00:00:00Z, the first moment of October.

Where it comes from, per export

The export column that feeds BillingPeriodEnd 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
BillingPeriodEnd
as is
Azure Cost Management, FOCUS export
BillingPeriodEnd
as is
Azure Cost Details (actual cost)
BillingPeriodEndDate
parsed as a date (MM/dd/yyyy)
Azure Cost Details (amortized cost)
BillingPeriodEndDate
parsed as a date (MM/dd/yyyy)
Google Cloud detailed billing exportNot carried

How Runcost uses it

Runcost uses the pair to validate that an export covers a whole period before reconciling it to the invoice.

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