> 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/cycle-and-modes.md).

# Billing Cycle and Modes

Billing is monthly, based on the period's usage, and can be grouped in several ways.

### When it is issued

Billing is **monthly**: it is generated from the **accumulated consumption** during the billing period. Consumption is measured throughout the month, so additions, removals, or changes halfway through the period are reflected in the amount according to what was actually consumed.

### How it is grouped: billing modes

The **billing mode** defines how your billable consumption is grouped and displayed. It does not change the consumption calculation, only its presentation:

* **Unified billing** — a consolidated invoice with all your consumption.
* **By organization** — the result is separated by each customer organization.
* **By subscription** — the result is broken down by subscription.

This way you can tailor how you read your billing to how you operate with your customers.

> #### 📘 Where it is set
>
> The billing mode is an organization setting, in its Profile. You can see it in [Profile.](https://docs.plenit.com/docs-en/platform/organizations/detalles/profile.md)

### Taxes and currency

The **taxes** applied on the invoice are calculated according to your country and your tax configuration, so the percentage is not universal. The **currency** also depends on the applicable business and tax environment.

### Next steps

* Learn about invoice statuses and unpaid invoices in[ Statuses and unpaid invoices](https://docs.plenit.com/docs-en/platform/billing/concepts/statuses-and-unpaid.md).
* See how usage looks in [Usage.](https://docs.plenit.com/docs-en/platform/billing/details/usage.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/cycle-and-modes.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.
