> 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/go-to-market/details/billing-detail.md).

# Billing Details

Reference for customer billing in Plenit: columns in the delivery note list, delivery note content, and download options.

This page shows the structure of customer billing, as it appears in the dashboard.

To understand what it is and where the delivery notes come from, see [Customer invoicing.](https://docs.plenit.com/docs-en/go-to-market/concepts/customer-billing.md)

### Delivery note list

The view **My delivery notes** lists, for each customer, these columns:

| Column         | Description                                      |
| -------------- | ------------------------------------------------ |
| Organization   | The customer to which the delivery note belongs. |
| Billing period | The billing period (for example, June 2026).     |
| Services       | The services consumed in that period.            |
| Costs          | The associated cost.                             |
| To be invoiced | The amount to bill the customer.                 |

You have **Filters** to narrow the search and a button **Export** to extract the information.

### Delivery note content

When you open a delivery note, the document is presented with the partner's branding and includes:

| Block          | Content                                                                                              |
| -------------- | ---------------------------------------------------------------------------------------------------- |
| Header         | Partner logo and details, issuer tax details (VAT ID, address, contact) and the title Delivery Note. |
| Identification | **ID**, **Delivery note number** and **Delivery note date**.                                         |
| Billing period | The billing interval (start and end date).                                                           |
| Summary table  | Lines with **Description** and **Amount**, grouped by service.                                       |
| Totals         | **Taxable base**, **Taxes** (with its percentage) and **Total**.                                     |

### Delivery note details

Below the summary, the section **Delivery note details** breaks down each line in more detail:

| Column      | Description                                                                       |
| ----------- | --------------------------------------------------------------------------------- |
| Description | The specific item (for example, Windows - 2 Cores, Windows Server 2025 Standard). |
| Quantity    | The billed units.                                                                 |
| Unit price  | The unit price applied.                                                           |
| VAT         | The line's tax percentage.                                                        |
| Amount      | The resulting amount.                                                             |

### Download

Each delivery note can be **previewed** and **downloaded in PDF and CSV**, depending on whether you want to send it or process it in a spreadsheet.

> #### 📘 Historical traceability
>
> Delivery notes are retained even if the customer changes status: if you delete a customer, they appear marked as deleted; if a customer migrates to another partner, the delivery notes prior to the migration remain available to you.
>
> It is a view for consultation, not editing.

### Next steps

* Learn how to view and export in [How to invoice your clients.](https://docs.plenit.com/docs-en/go-to-market/how-to/how-to-bill-your-customers.md)
* Understand the concept in [Customer invoicing.](https://docs.plenit.com/docs-en/go-to-market/concepts/customer-billing.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/go-to-market/details/billing-detail.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.
