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
Getting started
Attribute
Account
Reference
Where bills come from
| Provider | How |
|---|---|
| Anthropic, Enterprise plan | Enterprise Analytics API |
| Anthropic Console | Usage and Cost Admin API |
| OpenAI | Costs API |
| Bedrock, Vertex, Foundry | The cloud's export as CSV, or a connector on an Enterprise plan contract |
| Anything else | CSV 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 source | Reconciles against | List value is |
|---|---|---|
| Enterprise plan, usage at API rates | The Enterprise Analytics cost report at list price; the discount is its own line | Money, before discount |
| Console or API key | The Usage and Cost report, per workspace and day | Money |
| Team plan or seat-based plans | Usage credits only; usage inside the seat is not metered in dollars | A share of the seat cost, and the cost sheet says so |
| Bedrock, Vertex, Foundry | The cloud's export | Approximate |
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