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

# Banking

The Banking screen lists every bank account across the vehicles you manage. Open it to check balances and find where money has arrived without opening each deal.

Banking appears in four places on the platform. Banking Setup in a deal's Setup tab opens an account. This screen reports across every account you manage. Each deal also shows its own accounts on its Banking tab and in its Investors tab.

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

1. **Account list** Lists every account across the workspace, and selecting one opens its detail on the right.
2. **Hide $0 accounts** Removes unfunded accounts from the list when switched on, and is off by default.
3. **Account card** Shows each account's name, provider, last four digits, deal, entity, balance, and status.
4. **Last synced** Shows when the balance was last fetched from the bank, with Refresh beside it.
5. **Account Balance** Shows the balance as of the last sync, with the available amount below it.
6. **Account Details** Shows the account and routing numbers you give to a payer.
7. **Reveal control** Shows the full account number when you need to share it with a payee.
8. **Transactions** Lists every transaction on the account with a running total.
9. **Download Statement** Produces a downloadable statement for the selected account.

### Every account names its deal and entity

Each card names the deal the account serves and the entity that holds it, so this screen shows every account, deal, and entity together.

> **Hide $0 accounts** is off by default, so new escrow accounts appear at zero until their first deposit. Turn it on to see only funded accounts. Balances are accurate as of the last sync. Select **Refresh** before quoting a balance, and give the sync time with it.

### Transactions

The transaction table has five columns: Date, Category, Amount, Status, and Description, with a total at the foot.

Category shows two tags, such as TRANSFER and WIRE. Incoming amounts are positive and outgoing amounts are negative, and Status shows whether a transaction has posted.

> The Description column names the investor behind each incoming wire, so check it first when you match a wire to the Investors tab.

### Account details

Account and routing numbers show their last four digits, with a reveal control on the account number.

> Keep account numbers masked while sharing your screen. To pay someone from the account, add them in Wire Recipients on the deal, as described in **Wire Requests**.


---

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