> For the complete documentation index, see [llms.txt](https://docs.brokvix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brokvix.com/crm-admin/broker-teams/finance-withdrawal-queue.md).

# Use the Finance withdrawal queue

**For:** Finance users with withdrawal approval access.

The queue helps you identify requests awaiting a Finance decision and payment attention.

1. Open **Finance → Withdrawal Approvals**.
2. Read **Awaiting your action** and **Finance pending**. These are queue summaries; open a request to inspect its details.
3. Check **Recent required actions** and select **Review** for the relevant request.
4. Watch **Payment attention** for requests that need follow-up. Use **Refresh** if the list appears stale.

The Finance workspace is intended for reviewing Risk-approved withdrawals and settlement handling. A Finance decision is not, by itself, proof that payment has completed. Follow your organization's approved settlement and reconciliation process; this guide does not instruct you to release funds.

For a missing menu or denied action, see [Access and permissions](/crm-admin/getting-started/access-and-permissions.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.brokvix.com/crm-admin/broker-teams/finance-withdrawal-queue.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 `build a script that syncs our docs to a CMS` 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.