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

# Closing

The Closing tab is where you follow a close after you request it. It shows the closing summary, the figures for each investor, and what the close means for distributions.

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

1. **Section list** Lists the two sections, Closing and Distributions, each with its own tracker.
2. **Closing Tracker** Shows the closing summary and the figures for each investor once a close is created.
3. **Closing notice** Reminds you to check the closing figures against Banking and the Investors tab before you use them.
4. **Empty state** Appears until the first close is created.
5. **Distribution Tracker** Shows what the close implies for payouts to investors.
6. **Distribution notice** Reminds you to check the distribution figures against Banking before you share them with investors.

### Requesting a close

Create a close in the Closes section of the Investors tab, described in **The Investors tab**, and then follow it here.

### What appears once a close exists

A close produces a closing summary and the figures for each investor, covering units, fees, and carried interest.

> Check the figures line by line the first time you close.

### The Distribution Tracker

The Distribution Tracker sits below the Closing Tracker and shows what the close means for payouts. The Distributions screen in the Funds sidebar, described in **Distributions**, lists the payouts themselves.

### Before you request a close

Before you request a close, check the following:

1. Complete deal basics shows every item complete, as described in **Deal Setup**.
2. Every investor's KYC has cleared.
3. Every amount change request has been answered.
4. Banking has been refreshed and the wired total matches what you expect.

> Refresh Banking just before you request the close, so the close uses the latest balance.


---

# 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/closing.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.