> For the complete documentation index, see [llms.txt](https://docs.revenium.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revenium.io/track-and-control-costs/data-freshness-and-provisional-figures.md).

# Data Freshness and Provisional Figures

Where Revenium shows when each data source last delivered data, what you see when a feed stops, and which Invoiced figures may still change.

The **Data sources** chip at the top of every page in Revenium shows when every data connection last updated. Also, because many cloud and LLM providers reserve the right to update their billing amounts after they first post them, the Providers pages with invoicing data also name the providers whose invoice figures may still change so you know when numbers are final vs. provisional.

***

## How soon usage appears

Usage appears already priced. Revenium prices each call when it receives it, so a call never shows up first and gets its cost later. How soon it shows up depends on how it reaches Revenium:

* **Revenium SDKs and middleware, and the metering API:** within about a minute of the call finishing, when your code sends the call as it completes. This includes calls metered by the [LiteLLM proxy guardrail](https://docs.revenium.io/integrations/litellm-proxy-setup.md).
* **Codex and Claude Cowork, through OpenTelemetry:** within about a minute.
* **Claude Code, through OpenTelemetry:** within about two minutes.

Cursor and GitHub Copilot usage follows the timing on their own setup pages: [Cursor](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/setup-cursor.md) and [GitHub Copilot](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/setup-copilot.md).

***

## See when each source last delivered data

### Every page: the Data sources chip

The **Data sources** chip in the top bar has one marker for each kind of data:

* **Invoices**: billing data synced from your connected providers.
* **Telemetry**: usage Revenium receives from your SDK, OpenTelemetry agents and coding assistants.
* **Traces**: request-level detail sent through the same SDK connection.

Select the chip to see each one's state, such as **live** or **no data for a few days**, with a link to manage that source.

### Provider billing

On the [Providers pages](https://docs.revenium.io/track-and-control-costs/monitor-infrastructure-costs.md) under **Intelligence > Providers**, **Last checked** under the page title shows when Revenium last checked your providers for new billing data. Provider billing figures refresh every night (UTC) and cover the previous whole day. A second pass a few hours later reads recent days again and replaces the stored figures with the provider's latest, so a recent day can still move until the provider settles it. Hover over **Last checked** to see, for each connected provider, the first day that can still change. Most providers report whole days, so today's spend usually appears first as Metered, then in Invoiced after the nightly refresh or when you use **Sync billing data**. Cursor updates through the day. On **Last 24 hours**, the Providers tabs name the whole days they show, in UTC, and the invoiced total names the same days. Select **Sync billing data** to check again straight away.

Under **Integrations > Providers**, a status row shows the result of the last sync, **Last sync** with its time, any error message, and **View Sync Logs** for the full history.

### GitHub and GitLab

Each GitHub or GitLab card on the **Integrations** tab shows **Last successful sync**, which turns amber when the last success is no longer recent. When the connection's latest completed sync finished with warnings, a **Last completed sync** row appears beneath it in amber, with when that sync ran and **finished with warnings**: some or all of that run's data may be missing, and the sync logs say which part. **Last validated**, on the same card, shows only when the token was last checked. [PR Health](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/pr-health.md) shows **Last synced** under its page controls. When a sync that finished with warnings is newer than that date, the line reads **Last completed sync**, with when it ran, **finished with warnings**, in amber. See [GitHub Integration](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/github-integration.md).

***

## When a feed stops

Revenium shows a stopped feed where you work with its data, and each warning points to the fix.

* **Data sources chip.** A source that has gone quiet turns amber and says how long it has been without data. Follow its link to that source's setup page and check the connection or the agent that sends the data.
* **GitHub and GitLab cards.** The badge changes to **Connected, degraded** or **Sync failing**, and the card explains the cause under **This connection is only partly working** or **This connection is failing**. Select **Reconnect** if the token expired or was revoked, or **Sync now** to try again. **View Sync Logs**, at the top of the Integrations tab, shows what the provider reported.
* **Pull Request (PR) Health.** A banner says GitHub is no longer connected and that the figures stop at the last successful sync, with **Reconnect GitHub** or **Fix it in Integrations**.
* **Provider billing.** When you run **Sync billing data**, the result names the accounts that failed. Open **View Sync Logs** for the provider's message, then check that account's connection under **Integrations > Providers**.

***

## Which figures may still change

Some providers revise recent billing data after they first report it, for example when late usage arrives or a charge is re-rated. Revenium picks up those revisions, so a recent Invoiced figure from those providers can still move before it matches the provider's final invoice.

When the dates you select include days a connected provider may still revise, the **Spend by provider**, **API Keys** and **Models** views show a notice above the figures. It says the provider may still restate billing data, naming the provider or saying **Providers** when more than one is affected. It gives the first day that may still change, or says every day in the range may still change. Treat figures from that day onward as provisional.

Metered figures are priced by Revenium from the usage it records, so a provider's revision changes only the Invoiced side. See [How Revenium Prices a Transaction](https://docs.revenium.io/track-and-control-costs/how-revenium-prices-a-transaction.md) for how the two compare.

***

## When provisional figures settle

Revenium re-reads recent billing days from the providers that revise them:

* **Claude Enterprise**: the current calendar month, and the previous month too until the 10th.
* **Azure**: the current calendar month, and the previous month too until the 5th.
* **AWS Bedrock**: the current calendar month, and the previous month too until the 3rd.
* **GitHub Copilot**: the last 30 days.
* **ChatGPT Enterprise**: the last 30 days.
* **Google Vertex AI**: the last 7 days.

A figure from those providers is final once its day falls outside that window. For other providers, a day's figure does not change once that day has ended and the next daily sync has read it.

The notice covers the days Revenium still re-reads from the provider, and its date moves forward as those days pass. If the range you select for billing data does not include a period in which the provider can still update their charges, the notice no longer appears.

For a provider that issues a monthly invoice, such as Azure, also compare the month's Invoiced total with the final invoice once the provider issues it.

***

## Related

* [How Revenium Prices a Transaction](https://docs.revenium.io/track-and-control-costs/how-revenium-prices-a-transaction.md): where Invoiced and Metered figures come from
* [Provider Integrations](https://docs.revenium.io/integrations/provider-integrations.md): connect each provider's billing data and read the sync logs
* [Monitor Infrastructure Costs](https://docs.revenium.io/track-and-control-costs/monitor-infrastructure-costs.md): the Providers pages


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.revenium.io/track-and-control-costs/data-freshness-and-provisional-figures.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
