> 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

What statuses an invoice can have and what happens if one is left unpaid.

### Invoice statuses

In the invoice list, each invoice shows its status. The ones you will usually see are:

* **Paid** — the invoice has been successfully charged.
* **Unpaid** — the invoice has not been charged 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 goes unpaid

An unpaid invoice is not just informative: if it is not resolved, it can lead to **suspension** service suspension and, if it remains outstanding, to its **cancellation**.

> #### 🚧 Deadlines and notices to be confirmed
>
> The exact process deadlines (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.<br>

Even with a pending invoice, you keep the necessary access to **resolve it**: you can go into 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plenit.com/docs-en/platform/billing/concepts/statuses-and-unpaid.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.
