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

# Manual bank deposits

**For:** Brand administrators and Finance/Risk owners configuring review of **client-submitted bank deposits**. Operator-created deposits and other manual payment methods are outside this guide.

A client bank deposit enters review when the client submits the request and payment evidence. The evidence is stored with the transaction. Approval credits the deposit once; rejection does not credit it.

## Choose the route

| Configuration at creation                                                                  | Route to read                                                                                                                                                                                                                                                                                                |
| ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| A live **Manual / bank deposit created** workflow applies to the client-initiated request. | [Workflow-based manual bank deposit approvals](/crm-admin/platform-configuration/configure-financial-approval-flows/manual-deposits/manual-deposits-workflow.md). The first matching rule decides the outcome or the workflow fallback chain runs.                                                           |
| No live workflow applies.                                                                  | [Authoritative manual bank deposit approvals](/crm-admin/platform-configuration/configure-financial-approval-flows/manual-deposits/manual-deposits-authoritative.md). The backend starts Risk → Finance review, but the current Admin decision path does not provide a complete enforced two-person process. |

**No matching rule does not mean no workflow.** A live workflow keeps the request and uses its fallback chain. It does not hand the request to authoritative review.

Before using either route, verify the transaction, uploaded evidence, approver access, decision history, and resulting credit in QA. Do not treat a queue label alone as proof of approval or credit.


---

# 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/manual-deposits.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.