Token Controller Docs
Docs / Account / Bills

Bills

A bill is a provider's figure for one period: gross, discount, credit and net. Token entries must add up to it.

Browse the docs

Where bills come from

ProviderHow
Anthropic, Enterprise planEnterprise Analytics API
Anthropic ConsoleUsage and Cost Admin API
OpenAICosts API
Bedrock, Vertex, FoundryThe cloud's export as CSV, or a connector on an Enterprise plan contract
Anything elseCSV upload, typed in by hand, or the bills endpoint of the HTTP API

A provider can restate a bill. Each bill keeps its revisions.

Reconciliation

For each period: postings plus unattributed plus residual equal the bill. Residual is the part no token entry explains, such as seats, chat usage or a restated bill. It is always shown.

What the close reconciles against

Cost sourceReconciles againstList value is
Enterprise plan, usage at API ratesThe Enterprise Analytics cost report at list price; the discount is its own lineMoney, before discount
Console or API keyThe Usage and Cost report, per workspace and dayMoney
Team plan or seat-based plansUsage credits only; usage inside the seat is not metered in dollarsA share of the seat cost, and the cost sheet says so
Bedrock, Vertex, FoundryThe cloud's exportApproximate

The web app says which applies to your organization.

List value and billed value

Every token entry has a list value: the agent's reported cost where it has one (Claude Code does), otherwise its token counts times the price table for the model. A billed value exists where a bill or billed telemetry says what was actually charged. Every figure is labelled billed, list-price estimate, or unknown model.

Last updated 8 October 2026 · Edit this page © 2026 Jan Beck · Privacy · Imprint