> 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/deal-brokerage-accountcc.md).

# Deal Brokerage Accountcc

The Brokerage Account tab shows the securities a vehicle holds, with their value and the cash available. Open it before you report holdings to investors.

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

1. **Account name** Identifies the brokerage account on statements and exports.
2. **Toolbar** Lets you generate a statement or export the positions.
3. **Account line** Names the entity that holds the account, with its identifier and whether it is active.
4. **Account Value** Shows the combined value of cash and positions, with today's movement and the number of positions held.
5. **Buying Power** Shows the settled funds available for new purchases.
6. **Cash** Shows the cash held in the brokerage account.
7. **Unrealized P/L** Shows the gain or loss on open positions, with its percentage.
8. **Positions** Lists each holding with its price, quantity, market value, and gain or loss, sorted by market value.

### **Accounts**

A brokerage account holds securities and a bank account holds cash, so a vehicle that buys public shares uses both. Bank accounts are described in **Banking**.

### **Figures**

> **Plan wires from Cash.** Account Value includes positions, while Cash is what you can spend now. Sale proceeds become cash once the trade settles.

### Positions

The positions table lists each holding with its ticker and company, price, quantity, market value, and total gain or loss, largest first.


---

# 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/deal-brokerage-accountcc.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.