> For the complete documentation index, see [llms.txt](https://docs.payrexx.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payrexx.com/platform/english/backoffice/payouts.md).

# Payouts

This article explains where to find an overview of all transaction commissions paid out to you, how to download payout reports, and how to export payout data.

Navigate to **Payouts** in your Payrexx account to view the payout overview:

<div align="left"><figure><img src="https://13947520-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McKWr2N1ZENCggMlAH5%2Fuploads%2FWRAMyBnGyJJiLnDVpFTl%2Fimage.png?alt=media&amp;token=867a96f8-8057-4494-98c2-c0ab8178b826" alt=""><figcaption><p>Overview of payouts made to the platform</p></figcaption></figure></div>

### 1. Search for payouts

Use the serch field to find a specific payout. It is possible to search by the account holder name and by the IBAN.

### 2. Download payout data

Click on the download icon and choose whether you want to download the payout data in a summarized or detailed format:

* **Summary:** A CSV file will be downloaded containing summarized payout data.
* **Details:** A CSV file will be downloaded containing detailed payout data.

### 3. Download payout report

Click on the PDF icon to download the report of the respective payout.


---

# 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.payrexx.com/platform/english/backoffice/payouts.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.
