> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/workflow/standard-workflow-builder/standard-workflow/above-max-amount.md).
# 超出最大金额
此标题表示，该规则用于处理发票总金额超过审批人有权处理的最高金额的情况。
#### 规则配置：
1. **当……**
* **文档类型为 Invoice**：此条件确保规则仅适用于发票，这对于正确引导工作流至关重要。
2. **并且……**
* **文档状态为 Pending Approval**：发票必须处于“Pending Approval”（待审批）状态。此状态至关重要，可确保规则应用于仍在处理中且尚未最终确定的发票。
* **比较两个字段：Total Amount 大于 Approver Max Amount**：此条件用于检查发票总金额是否超过审批人获准处理的最高金额。此比较还可以包含容差设置，以便根据预定义标准允许小幅差异。
#### 操作（则……）：
* **从字段 Next Level Approver 指定用户；使用用户 User 作为后备用户**：如果发票超过指定的最高金额，系统会自动将其分配给更高级别的审批人，即“Next Level Approver”字段中指定的人员。如果此字段未填写，或指定用户不可用，系统会使用默认用户（可能是管理员或其他指定员工）作为后备，以确保发票得到及时审核。
#### 界面元素：
* **Add Card**：此选项允许向规则中添加其他条件或操作，从而灵活处理复杂场景。
* **Save**：此按钮将规则配置保存到系统中。
#### 此规则的用途：
此规则旨在确保超过特定财务阈值的发票由具有相应授权级别的审批人审核。这有助于维持财务控制与监督，确保支出由具备相应审批限额的人员审核，从而保护组织免受未经授权或不当支出的影响。
与前一条规则一样，此规则有助于自动化工作流，减少人工操作并提高对组织财务政策的遵循程度。这是一个示例，说明如何有效运用工作流自动化来管理公司内部复杂的财务流程。
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.docbits.com/chinese/guan-li-yu-she-zhi/workflow/standard-workflow-builder/standard-workflow/above-max-amount.md?ask=&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 `automate deployments from our CI pipeline` 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.
