> For the complete documentation index, see [llms.txt](https://docs.rekor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rekor.ai/scout/scout-dashboard/billing-and-subscriptions/review-billing-history.md).

# Review Billing History

To review your Billing History, start by clicking the **`Billing and Subscriptions`** link located on the left side navigation of your dashboard.

In the popup window, choose **`Billing History`**.

Here you can view PDFs of all previous invoices by clicking **`Download`** on the respective invoice. Invoices are available either monthly or yearly depending on your subscription billing frequency.

<div align="left"><figure><img src="https://1741267365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Vw5WlNC3SZYgYghV1xw%2Fuploads%2FWorL8k7ZSHOnZud8dyM3%2Fbilling-history.jpg?alt=media&amp;token=f729e105-961c-43d3-9cd7-063b23484a9d" alt="" width="375"><figcaption><p>Screenshot showing the Billing History window</p></figcaption></figure></div>

{% hint style="info" %}
**Note:** Scout invoices are only available from July 2022 to the Present. If you need access to an invoice older than July 2022, please contact our Finance team at <billing@rekor.ai>.
{% endhint %}


---

# 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.rekor.ai/scout/scout-dashboard/billing-and-subscriptions/review-billing-history.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.
