> 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/purchase-invoice-2nd-approval-quantity.md).
# 采购发票 - 第二次审批数量
此标题表示该规则专门用于处理处于第二次审批阶段的采购发票，重点是验证所列数量是否准确。
#### 规则配置：
1. **当……**
* **文档类型为发票**：此条件确保规则仅对归类为发票的文档触发。这对于保持工作流的针对性和相关性至关重要。
2. **并且……**
* **文档状态为待第二次审批**：这表示该发票当前正在等待第二次审批。此阶段通常用于在最终确定发票前进行额外审核。
* **文档字段 Invoice Sub Type 等于 Purchase Invoice**：此条件进一步限定规则仅适用于标记为“Purchase Invoices”的发票。此分类有助于将其与其他发票类型区分开来。
* **订单确认中的 Logic Quantity 不等于采购订单中的数量**：此关键条件用于检查订单确认中注明的数量是否与原始采购订单中的数量一致。如果存在差异，则触发操作，表明可能有错误或问题需要解决。
#### 操作（那么……）：
* **从字段 Buyer Name 分配用户，并使用用户 User 作为备用用户**：如果满足规则条件（即数量不一致），系统会自动将发票分配给 Buyer Name 字段中列出的人，以便进一步审核。如果该字段为空或指定人员无法处理，则由默认用户（可能是管理员或其他指定员工）接手，以确保及时审核并解决问题。
#### 此规则的用途：
* **准确性与合规性**：此规则对于确保开票流程准确并符合采购订单中约定的条款至关重要。它有助于防止财务差异和潜在的库存错误。
* **简化审批流程**：针对特定差异自动执行审核流程，有助于简化审批，并确保相关人员迅速处理问题。
* **加强财务监督**：要求对数量进行第二次审批，可以加强组织内的财务控制和责任落实。
此设置展示了如何利用工作流自动化提升运营效率并确保财务诚信，尤其是在管理公司内部复杂采购流程时。
---
# 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/purchase-invoice-2nd-approval-quantity.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.
