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

# Authoritative approval

**For:** Finance and Risk owners evaluating the no-workflow path for client-submitted bank deposits. This page describes the current backend behavior and an important Admin limitation; it is **not** an instruction to approve live requests through an unverified screen.

## When this route starts

The client creates a bank deposit request, and **no live workflow** applies. If a live workflow owns the request but none of its rules match, its fallback chain runs instead; that is not this route.

## Current decision sequence

1. The backend opens the deposit at **Risk pending**.
2. A Risk approver acts before Finance. Risk and Finance must be different people, and the requester cannot approve.
3. Final Finance approval credits the deposit once. Rejection does not credit it.

The client's payment screenshot or other evidence is available with the transaction and must be inspected before a decision.

> **Current Admin limitation:** The audited Admin decision path does not yet expose this bank-deposit review as a complete enforced Risk-decision then Finance-decision path. Do **not** represent it as a working two-person Admin control or use it for live bank-deposit approval until that decision path is corrected and tested.

For a staged operator process today, configure and QA-test an approved [manual bank deposit workflow](/crm-admin/platform-configuration/configure-financial-approval-flows/manual-deposits/manual-deposits-workflow.md). Confirm that its decision gate really prevents credit until the required levels approve. Return to the [manual bank deposit overview](/crm-admin/platform-configuration/configure-financial-approval-flows/manual-deposits.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/manual-deposits/manual-deposits-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.