> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/platform/billing/concepts/statuses-and-unpaid.md).
# Statuses and Unpaid Invoices
### Invoice statuses
In the invoice list, each invoice shows its status. The ones you will usually see are:
* **Paid** — the invoice has been successfully paid.
* **Unpaid** — the invoice has not been paid and is pending resolution.
> #### 🚧 Other statuses
>
> The system can handle additional statuses in the billing cycle. We are confirming which ones are visible to you before documenting them.
### What happens if an invoice remains unpaid
An unpaid invoice is not just informational: if it is not resolved, it can lead to the **suspension** of the service and, if it remains unpaid, to its **cancellation**.
> #### 🚧 Deadlines and notices to be confirmed
>
> The exact timelines of the process (when it is suspended and when it is canceled) and the notices you receive are pending validation with the billing team.
>
> We will add them here as soon as they are confirmed.
Even with a pending invoice, you keep the necessary access to **resolve**: you can go to your profile and your payment methods to resolve the charge.
### Next steps
* Learn how to download your invoices in [How-to](https://gitlab.com/plenit-group/plenit-docs-es-es/-/blob/v1.0/docs/Plataforma/facturacion/facturacion-conceptos/facturacion-how-to/README.md).
* Review how we bill you in [How we bill you](https://gitlab.com/plenit-group/plenit-docs-es-es/-/blob/v1.0/docs/Plataforma/facturacion/facturacion-conceptos/facturacion-conceptos-como-te-facturamos/README.md).
---
# 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, and the optional `goal` query parameter:
```
GET https://docs.plenit.com/docs-en/platform/billing/concepts/statuses-and-unpaid.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.