> For the complete documentation index, see [llms.txt](https://docs.violet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violet.io/prism/reporting.md).

# Reporting

Violet provides comprehensive reporting capabilities that allow you to export detailed financial and operational data for analysis, reconciliation, and record-keeping purposes. You can export data in CSV format for use in Excel or other spreadsheet applications.

## Available Reports

Violet offers four main reporting categories, each designed to provide specific insights into your business operations.

### [Commission Rate Change Log](/prism/reporting/commission-rate-change-log.md)

Track historical changes to commission rates across your merchant network with detailed audit trails and effective dates.

### [Connected Merchants](/prism/reporting/connected-merchants.md)

Export data about your connected merchants, including their platform information, connection dates, and commission rate history.

### [Payouts](/prism/reporting/payouts.md)

Export detailed payout information including settlement dates, amounts, and associated distributions for bank account reconciliation.

### [Distributions](/prism/reporting/distributions.md)

Access granular transaction data with detailed breakdowns of fees, commissions, and other financial metrics for individual orders.


---

# 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.violet.io/prism/reporting.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.