> 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/how-we-bill-you.md).

# How We Bill You

In Plenit, the billing relationship is **with the partner**.

Although your usage originates in several customer organizations, what is billed is consolidated in your account: **we bill you** what you have consumed.

### What we bill you for

The amount is based on **actual usage** of your subscriptions and services during the period. We apply the relevant taxes and billing rules to that usage. In short: you pay for what your services consume in each period.

### The two layers: what you pay and what you charge

You work with two financial layers, and it's best not to mix them:

* **Plenit bills you** — your **cost**. It’s what you see in this section, in Usage, and on your invoices.
* **You bill your customers** — what **you charge**, with your margin. That is managed in [Go to Market,](/docs-en/go-to-market.md) in Customer Billing, and it is reflected in delivery notes.

> #### 📘 The difference in one sentence
>
> Here you see what Plenit costs you. In Go to Market, you prepare and review what you charge your customers. The difference between the two is your margin.

### Where you see it

Your billing with Plenit lives in your own area, split across two places:

* **Usage** — your usage, your subscriptions, and your invoices (with their Overview, Subscriptions, and Invoices tabs).
* **Payment Methods** — the card or direct debit we use to charge you.

### Next steps

* Understand when and how it is grouped in [Billing cycle and modes.](/docs-en/platform/billing/concepts/cycle-and-modes.md)
* See the screens at [Details.](/docs-en/platform/billing/details.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/how-we-bill-you.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.