> 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 to find your invoices, what each billing status means, and which ones count as an active, paid account. Your invoices and billing status live under **Settings → Invoices**, which is visible to organization admins. ## Subscription statuses Your subscription can be in one of these billing states: * `active` * `trialing` * `past_due` * `paused` * `incomplete` * `incomplete_expired` * `canceled` * `unpaid` ## Which count as paid and active An account is treated as **paid and active** when its status is **`active`** or **`trialing`**. In those states you have full access to your plan's features. The other states mean access is limited or ended — for example `past_due` or `unpaid` signal a payment problem, and `canceled` means the subscription has ended. If billing features are missing when you expect them, check that your subscription is `active` or `trialing`; if a payment failed, resolve it on the billing screen or contact . ## Requesting a receipt, W-9 or other document The billing screen shows your invoices. For a **receipt**, a **W-9**, a bank or vendor verification letter, or a correction to a charge, contact — those aren't 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=&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.