> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/help-and-support/faqs/why-isnt-my-azure-billing-data-up-to-date.md).

# Why isn't my Azure billing data up to date?

The platform uses several Microsoft APIs to pull data that allows you to create Spend reports, [Budgets](/extensions/cloud-tools/budgets.md), and [Chargebacks](/extensions/cloud-tools/chargebacks.md). In some cases, it can take up to 24 hours for the resource cost to be accessed through the interface.

As the platform synchronizes your Azure billing data only once a day, sometimes, it might take 48 hours for the data to refresh.

Additionally, the reconciliation files are available no later than the 8th day of every month. Microsoft invoices partners based on this file. Therefore, we recommend that you send chargebacks after the 8th day of the month. 

For more information, see [Reconciliation file availability](https://docs.microsoft.com/en-us/partner-center/billing-basics) and [Microsoft Partner Center data delay](https://docs.microsoft.com/en-us/partner-center/daily-rated-usage-recon-files).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.platform.softwareone.com/help-and-support/faqs/why-isnt-my-azure-billing-data-up-to-date.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.