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

# Distributions

Distributions is where you track proceeds returned to investors. Each row shows the vehicle, the status, and the date the money is due to arrive.

This screen lists distributions across every vehicle. Each deal also has a Distributions section in its Investors tab, and investors see their own Distributions screen in Portfolio.

![](https://content.gitbook.com/content/9IirLidzibYpEfSBave3/blobs/LaME4o4eykDDuHJepHSX/Unknown%20image)

1. **Total distributions** Counts the distributions recorded across every vehicle in the workspace.
2. **Search** Finds distributions by typing the deal's name.
3. **Refresh and Export** Let you refresh the table or export it.
4. **Column headers** Label the five columns, with one row for each distribution.
5. **Status** Shows whether the distribution is pending or has been completed.
6. **Requested Receiving Date** Shows the date investors were told to expect the money.
7. **Note** Holds a short description written when the distribution was created.

The table also shows the deal each distribution is paid from and the date it was created.

> **Follow up on Pending rows whose date has passed.** A row stays Pending until the distribution is completed.

### Creating a distribution

To create a distribution, open the deal's Investors tab and use its Distributions section, described in **The Investors tab**.


---

# 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.allocations.com/why-allocations/distributions.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.