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

# Wire Requests

Wire Requests is where you send money out of a vehicle. This screen tracks each request from creation through its approvals to the confirmation that the wire was sent.

This screen shows every request across the workspace, whichever deal raised it.

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

1. **Total wire requests** Counts the wire requests raised across every vehicle.
2. **Search** Finds a request by typing any part of its name.
3. **Filter** Opens the filter panel for narrowing the list by deal or status.
4. **Toolbar** Lets you refresh the table, export it, or create a wire request.
5. **Column headers** Label the five columns that trace each request from creation to a sent wire.
6. **Status** Shows how far the request has progressed toward being sent.
7. **Approvals** Shows how many approvals the request has received out of the number it requires.
8. **Confirmation:** Shows whether the bank has confirmed the wire. Select the arrow at the end of the row to open the request.

Two more columns describe the request:

* **Deal:** The vehicle the money is leaving, with the recipient below it.
* **Requested Amount:** The amount the wire will send to the recipient.

### Approvals are shown as a count

Every wire needs more than one approval, so the Approvals column shows how many approvals a request has out of the number it needs, such as 1 / 2 or 2 / 2.

> Sort on Approvals to see every request waiting for a second approval.

### Reading status against approvals

Read Status and Approvals together:

* Pending with 1 / 2 is ready for its second approver.
* Approved with 2 / 2 has every approval it needs.
* Completed with 2 / 2 means the wire has been sent.

> Wait for Completed before telling a recipient the wire has been sent.

### Adding the recipient first

Each request pays a recipient saved in Wire Recipients on the deal, so add the recipient there first.

> Add anyone who receives fees under Fee Recipients, the section beside Wire Recipients. Both are 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/wire-requests.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.