> 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.md).

# Concepts

The key ideas in your billing: how we bill you as a partner, the billing cycle and modes, and invoice statuses and unpaid invoices.

Understand how we bill you as a partner before checking your invoices: what is billed and how it differs from what you charge your customers, when it is issued and how usage is grouped, and what happens if an invoice goes unpaid.

Here's why, without steps.

{% hint style="info" %}
Looking for the step-by-step guide? You have it in How-to. Here we explain what each thing is and how it fits together.
{% endhint %}

### Explore the concepts

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>How We Bill You</strong></td><td>The Plenit-to-partner model: although usage comes from multiple organizations, it is consolidated and billed to you.</td><td><a href="https://docs.plenit.com/docs-en/platform/billing/concepts/how-we-bill-you.md">How We Bill You</a></td></tr><tr><td><strong>Billing Cycle and Modes</strong></td><td>When the invoice is issued, how usage is grouped, and how taxes are applied.</td><td><a href="https://docs.plenit.com/docs-en/platform/billing/concepts/cycle-and-modes.md">Billing Cycle and Modes</a></td></tr><tr><td><strong>Statuses and unpaid invoices</strong></td><td>What statuses an invoice can have (Paid, Unpaid) and what happens if one remains unsettled.</td><td><a href="https://docs.plenit.com/docs-en/platform/billing/concepts/statuses-and-unpaid.md">Statuses and Unpaid Invoices</a></td></tr><tr><td><strong>Glossary</strong></td><td>The terms that appear in your billing, with a brief definition for quick reference.</td><td><a href="https://docs.plenit.com/docs-en/platform/billing/concepts/glossary.md">Glossary</a></td></tr></tbody></table>


---

# 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.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.
