> 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/less-than-max-amount.md).

# 低于最高金额

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-777c87e6f820689f1d8a120826d8c3bf4a4ced87%2FBildschirmfoto%202024-05-03%20um%2014.48.55.png?alt=media" alt=""><figcaption></figcaption></figure>

此标题表明，所设置的规则或条件用于处理总金额小于或等于指定最高金额的发票。

#### 规则配置：

1. **当……**
   * **文档类型为发票**：此条件用于检查正在处理的文档是否为发票。这对于确保规则仅适用于发票，而不适用于其他类型的文档，至关重要。
2. **并且……**
   * **文档状态为待审批**：这指定发票必须处于“待审批”（"Pending Approval"）状态。此状态检查可确保规则仅适用于等待审批的发票。
   * **比较两个字段：总金额小于或等于审批人最高金额**：此条件将发票的总金额与审批人获授权的最高金额进行比较。如果发票总金额小于或等于该最高金额，规则将继续执行下一步。这可能包含一个容差范围，允许在指定限度内存在细微偏差。

#### 操作（那么……）：

* **从字段审批人姓名分配用户，用户作为备用用户**：如果满足指定条件，系统会自动将发票分配给姓名由某个字段指定的审批人。如果此字段为空或不可用，则会分配默认用户（可能是管理员或其他指定员工）作为备用用户来处理审批。

#### 界面元素：

* **添加卡片**：此按钮可能允许用户为规则添加更多条件或操作，从而提高工作流的灵活性和针对性。
* **保存**：将配置好的规则保存到系统中。

#### 此规则的用途：

此设置旨在简化发票审批流程，根据金额自动将发票转给相应的审批人，并确保只有金额处于特定限额内的发票才会按此方式自动处理。它有助于管理财务控制，并通过减少对每张发票的人工检查来加快工作流。

\\


---

# 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/less-than-max-amount.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 `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.
