> 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/payouts/columns.md).

# Available Columns

Violet allows you to export financial transactions, from the point of order through payment processing, to eventual payout, with a detailed breakdown of fees, commissions, and other financial metrics related to orders and their components. This page provides details on the columns you are able to export.

**Payouts** are the top level funds receieved in your bank account via Stripe, for a collection of Orders. Key information such as the payout ID, date, and amount are initially null until the transfer initiates.

## Payouts

A payout is generated when money begins to transfer to your bank account. Before that happens the id, date, and amount fields on a distribution record will be null. These fields will always be present as part of a payouts report. They are not customizable.

| Field Name             | Export Name      | API Name         | Definition                                                                                                                                                                        |
| ---------------------- | ---------------- | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Payout ID              | id               | id               | The ID of the Payout that the distribution is associated with.                                                                                                                    |
| Payout Amount          | payout\_amount   | payout\_amount   | The amount of the payout. This is the amount that will be seen transferred into your bank account. In the export, this amount will be duplicated on each associated distribution. |
| Payout Currency        | currency         | currency         | The currency of the payout.                                                                                                                                                       |
| Payout Status          | status           | status           | One of `PAID`, `PENDING`, `IN_TRANSIT`, `CANCELED`, `FAILED`.                                                                                                                     |
| Payment Service        | payment\_service | payment\_service | The payment gateway provider (e.g. Stripe, Moov…).                                                                                                                                |
| Payout External ID     | external\_id     | external\_id     | The id of the payout in the external payment gateway.                                                                                                                             |
| Payout Date Created    | date\_created    | date\_created    | The date the Payout record was created.                                                                                                                                           |
| Payout Settlement Date | date\_settled    | date\_settled    | The date the Payout record was settled.                                                                                                                                           |


---

# 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/payouts/columns.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.
