> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/docs/web-app/billing-and-job-history.md).

# Billing history and job history export

Find credit purchases and invoices, or export job details to a CSV file.

## Find a purchase or invoice

Click your name or account icon at the bottom of the sidebar, then open **Billing**.

Click **Payment Processor**, **Invoice Number**, **Amount**, or **Purchase Date** to sort the purchase list.

When an invoice is available, click **Download** in its **Invoice** column. It opens in another browser tab. An empty invoice cell means the purchase has no invoice link available in the app.

For payment options and invoice restrictions, see [Buy Render Credits](/docs/web-app/render-credits.md).

## Export job history

1. In the account menu, open **Account Settings** and click **Download Job History** below the account summary.
2. Use **date range** to choose the jobs' creation dates. Leave it empty to include all dates.
3. Open **Fields** above the preview and choose the columns to export. For example, include **Name**, **Date created**, **Frame range**, and **Job cost**.
4. Check the preview and click **Download CSV**.

The CSV contains the selected columns and jobs from the displayed page. You can open it in a spreadsheet application.

{% hint style="info" %}
Each export contains up to 50 jobs. If a page selector appears below the preview, select and download each page you need, or narrow the date range.
{% endhint %}

**Download CSV** is unavailable while the preview is loading, when no jobs match, or when no columns are selected.


---

# 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://know.rendernetwork.com/docs/web-app/billing-and-job-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.