> For the complete documentation index, see [llms.txt](https://gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/help-center/account-management/pricing-plans-and-billing/where-can-i-find-my-invoices-and-update-billing-details.md).

# Where can I find my invoices, and update billing details?

GitBook uses Stripe for billing. To access your invoices:

1. Click **Settings** at the bottom of your sidebar
2. Click **Organization Settings**
3. Click **Billing** → **Manage Billing** (redirects you to Stripe)
4. Navigate to **Invoice History** and click the arrow (↗️) next to any payment to download

#### To update billing information:

In the billing portal, click **Update Information** in the information section.&#x20;

You can add additional email addresses, for example, your finance department details here. This address will receive invoices but won't have GitBook access.&#x20;

{% hint style="info" %}
**Important:** Please update billing details *before* making a payment.&#x20;

We cannot change company information on invoices that already have been paid.
{% 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 dynamically by asking a question.

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

```
GET https://gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/help-center/account-management/pricing-plans-and-billing/where-can-i-find-my-invoices-and-update-billing-details.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
