> 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

Understand how we bill you as a partner before reviewing 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 remains unpaid. 

Here’s the 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 partner model: even if usage comes from multiple organizations, it is consolidated and billed to you.</td><td><a href="/pages/70072394a1e6c1246ebaab8b0c1ea3932d9c7194">/pages/70072394a1e6c1246ebaab8b0c1ea3932d9c7194</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="/pages/bdd497ce2720a20cb653682abbc97729873191e0">/pages/bdd497ce2720a20cb653682abbc97729873191e0</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 unresolved.</td><td><a href="/pages/c231069dced3d92a3d1868845ba6cd4a1f022b7e">/pages/c231069dced3d92a3d1868845ba6cd4a1f022b7e</a></td></tr><tr><td><strong>Glossary</strong></td><td>The terms that appear in your billing, with a brief definition so you can keep them at hand.</td><td><a href="/pages/afbaff66d6ff22fe1746f9e9e98b8ab28bcf9ce9">/pages/afbaff66d6ff22fe1746f9e9e98b8ab28bcf9ce9</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 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.md?ask=<question>&goal=<endgoal>
```

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