> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/settings/invoices.md).

# Invoices

Where Admins find and download invoices, what each invoice status means, and how to get a receipt, W-9 or other billing document.

Your organization's invoices are under **Settings → Invoices**. The tab is shown only to [Admins](https://support.sayprimer.com/primer/account-and-security/roles-and-permissions.md). Each invoice lists its number, date, amount, status and recipient, newest first; click a column to sort by it.

## Downloading an invoice

Click the **Download** button on an invoice's row to get it as a PDF. If Primer can't find the file, contact <support@sayprimer.com>.

## Invoice statuses

* **Paid** — the invoice has been paid.
* **Open** — issued and waiting for payment.
* **Draft** — not issued yet.
* **Void** — cancelled; nothing is owed.
* **Uncollectible** — payment couldn't be collected.

Whether your plan itself is active, in trial or past due is shown on [Your plan](https://support.sayprimer.com/primer/settings/your-plan.md#what-happens-to-your-audiences-when-your-plan-lapses), where you also update your card.

## Requesting a receipt, W-9 or other document

For a **receipt**, a **W-9**, a bank or vendor verification letter, or a correction to a charge, contact <support@sayprimer.com> — only invoices are self-serve downloads.


---

# 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://support.sayprimer.com/primer/settings/invoices.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.
