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

# Authoritative approval

**For:** Risk, Finance, and Treasury owners evaluating a client withdrawal where no live applicable withdrawal workflow exists. This route is an exceptional configuration state.

## When this route starts

The client requests a withdrawal, funds are reserved, and **no live applicable workflow** owns the request. A live workflow with no matching rule uses its fallback chain instead.

## Decision and payment sequence

1. Risk reviews first.
2. Finance reviews after Risk. The two approvers must be distinct and neither may be the requester.
3. Finance approval moves the withdrawal toward payment processing. It does **not** mean the client has been paid.
4. Treasury settlement or an eligible brand-configured automatic send follows as a separate control. Check the payment status and reconciliation outcome.

If the intended policy uses different approvers or levels, design and QA-test a [withdrawal workflow](/crm-admin/platform-configuration/configure-financial-approval-flows/withdrawals/withdrawals-workflow.md) rather than assuming authoritative Risk/Finance clicks are added later. Return to the [withdrawal overview](/crm-admin/platform-configuration/configure-financial-approval-flows/withdrawals.md) for route selection.


---

# 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/withdrawals-authoritative.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.