> 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/quickstart.md).
# Quick Start
In a few minutes: set up your payment method and learn where to see your consumption and invoices.
This guide gets your billing in order in just a few minutes: you set up how we charge you and learn where to see your usage and your invoices.
By the end, you'll have your payment method active and know your way around Usage.
> #### 📘 What will you get?
>
> Your payment method set up and clear where to check what you use and what we bill you for.
>
> Remember: this is what you pay Plenit, not what you charge your customers (that lives in [Go to Market).](/docs-en/go-to-market.md)
### Before you start
You need to have logged in and have the **Billing** permission. Have the details of the method you are going to use ready: card details, or the IBAN and your company’s tax details. If you choose direct debit, make sure you have a **valid email and mobile number**, because they are needed to sign the mandate.
### 1. Set up your payment method
Go to **Payment Methods** and choose how we charge you:
* **Credit card** — Visa, Mastercard, or American Express.
* **Direct debit** — SEPA debit from your account, with its mandate.
You have the step-by-step guide, with its fields and the SEPA mandate, in [Add or change your payment method. ](/docs-en/platform/billing/how-to/how-to-add-or-change-payment-method.md)The full reference is in [Payment Methods.](/docs-en/platform/billing/details/payment-methods.md)
### 2. Review your usage
Open **Usage** and stay on the tab **Summary**. There you can see the **monthly usage** (with its total and breakdown by service) and the trend in the **usage history**. It’s your snapshot of the period at a glance.
The details of each tab are in [Usage.](/docs-en/platform/billing/details/usage.md)
### 3. Locate and download your invoices
In **Usage**, go to the tab **Invoices**. There you have the list with its status (**Paid** or **Unpaid**) and the button **Download invoices** to download a batch by date range, in PDF and XML.
You have it step by step in [Download your invoices.](/docs-en/platform/billing/how-to/how-to-download-your-invoices.md)
### Check that everything is in order
Quick review:
* Your payment method appears set up in **Payment Methods**.
* You see your monthly usage in **Usage > Summary**.
* You find your invoices in **Usage > Invoices** and you can open or download them.
> #### 👍 All green
>
> Your billing is ready: we can now charge you and you know where to check your usage and your invoices. From here on, you just need to keep reviewing each period.
### Next steps
* Understand the model in [Concepts.](/docs-en/platform/billing/concepts.md)
* Learn specific tasks in the [How-to guides.](/docs-en/platform/billing/how-to.md)
* Check the reference for each screen in [Details.](/docs-en/platform/billing/details.md)
* Resolve questions in the [FAQ.](/docs-en/platform/billing/faq.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/quickstart.md?ask=&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.
