> 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/platform-configuration/configure-financial-approval-flows/withdrawals.md).

# Withdrawals

**For:** Brand administrators, Finance, Risk, and Treasury process owners. A client withdrawal reserves funds when requested. **Approval and payment release are separate events.**

## Choose the route

| Configuration when the client requests a withdrawal                                           | Route to read                                                                                                                                                                                                                                                                                   |
| --------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A live applicable **Withdrawal requested** workflow, including a published built-in workflow. | [Workflow-based withdrawal approvals](/crm-admin/platform-configuration/configure-financial-approval-flows/withdrawals/withdrawals-workflow.md). The first matching rule or fallback chain decides. The chain may differ from Risk → Finance if configured and approved.                        |
| No live applicable workflow.                                                                  | [Authoritative withdrawal approvals](/crm-admin/platform-configuration/configure-financial-approval-flows/withdrawals/withdrawals-authoritative.md). Risk reviews first, Finance second; settlement remains separate. This is an exceptional configuration state, not the usual starting point. |

A no-match rule in a live workflow uses its fallback chain, **not** authoritative review. A custom chain that omits Risk or Finance does not acquire those sign-offs automatically. The built-in withdrawal workflow's fallback has Risk → Finance and distinct approvers; a rule-selected chain can differ.

After final approval, check whether the request enters Treasury processing or an eligible automatic-send route under the published brand settings. Verify payment status and reconciliation before saying funds were sent. See [withdrawal configuration and QA screenshots](/crm-admin/platform-configuration/configure-financial-approval-flows/withdrawals/withdrawals-workflow.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/platform-configuration/configure-financial-approval-flows/withdrawals.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.