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

# Workflow approval

**For:** Brand administrators configuring approval of PSP-confirmed deposits held by automatic-credit or brand daily limits. Finance and Risk owners must approve the intended chain.

## When this route starts

A PSP-confirmed deposit is held above an applicable auto-credit ceiling or daily amount/count limit, and a live **Overlimit Deposits** workflow covers the system-initiated request. Its first matching rule or, if none matches, fallback chain owns the decision. There is no additional authoritative approval after workflow completion.

Use [Set up approvers and advice collaborators](/crm-admin/platform-configuration/configure-financial-approval-flows/approver-and-advice-eligibility.md) before naming a level's approvers. The operator's assignment and the workflow's **Permission to decide**, when configured, are both needed for a decision; advice eligibility does not replace either.

## Build the PSP-hold route

1. Confirm the PSP really reported a successful payment and the amount/count limit **held credit**. A PSP decline is not an overlimit deposit approval.
2. In **Tenants & Brands → Approval Workflows**, select the intended tenant and brand and inspect any live **Overlimit Deposits** coverage. Publishing an overlap can replace existing routing.
3. In a draft choose **Overlimit Deposits** and **Applies to: Both**. The hold is system-initiated; client-only coverage will miss it.
4. Set the fallback chain required by the approved policy: one authorized level if one decision is sufficient, or explicit Risk and Finance levels if both must approve. Set active approvers, quorum, permission, SLA, escalation, and four-eyes controls. The chain does **not** inherit Risk and Finance from the no-workflow route.
5. Decide whether direct approval is allowed. If every held amount must pass the configured levels, turn it off. Add effective, prioritized rules only for deliberate exceptions; no match uses the fallback chain.
6. Select [outcome, assignment, and reminder templates](/crm-admin/platform-configuration/configure-financial-approval-flows/approval-email-templates.md) whose brand mapping and wording have been checked. In QA, test a below-limit deposit (no approval), an overlimit matching rule, an overlimit fallback, rejection, and the actual credit/reconciliation result.

![Unsaved QA overlimit workflow editor with Overlimit Deposits trigger, Both initiator coverage and four-eyes controls](https://1730587053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpafqqfmUanubolAQzn0g%2Fuploads%2Fgit-blob-0c159fe2415407f653474f9f000d499691fb53c7%2Fqa-trigger-and-controls.jpg?alt=media)

*QA editor illustration only: **Both** is essential for the system-created PSP hold. The example name/code and controls were not saved or published.*

![Unsaved QA overlimit workflow editor showing a one-level fallback and assignment/reminder email selectors](https://1730587053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpafqqfmUanubolAQzn0g%2Fuploads%2Fgit-blob-78939e5dbdea06a4772dabedeeb85efc3d0c7173%2Fqa-level-and-emails.jpg?alt=media)

*QA editor illustration only: the single Finance level demonstrates where to set a fallback, quorum, SLA, escalation, and email events. Its approvers are **incomplete**; add active authorized people. Use two explicit levels instead if the brand policy requires Risk then Finance.*

Rejection is not automatically a PSP refund. Follow the transaction's refund or settlement instructions and reconcile the provider separately. The [transaction-to-decision map](/crm-admin/platform-configuration/configure-financial-approval-flows/from-transaction-to-decision.md) distinguishes an automatic-credit deposit from a held one; the [overlimit overview](/crm-admin/platform-configuration/configure-financial-approval-flows/overlimit-deposits.md) compares the authoritative single-decision route.


---

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