> 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-unit-price-export.md).
# 采购发票 - 第二次审批单价导出
此标题表示，该规则用于管理采购发票的第二阶段审批，重点关注单价，确保其符合约定条款。
#### 规则配置：
1. **当……**
* **文档类型为发票**：此条件确保规则仅对标识为发票的文档触发，这对于准确指引工作流至关重要。
2. **并且……**
* **文档状态为待第二次审批**：此条件表示发票正在等待第二次审批。此阶段通常会增加一道检查，确保交易最终确认前的准确性。
* **文档字段“发票子类型”等于“采购发票”**：此条件进一步限定，规则仅适用于归类为“采购发票”的发票，以区别于其他类型的发票。
* **逻辑单元：订单确认中的单价等于采购订单中的单价**：此条件检查订单确认中列出的单价是否与采购订单中的单价一致。只有价格一致时，发票处理才会继续，这对预算管理和财务报告至关重要。
#### 操作（然后……）：
* **开始导出**：发票满足指定条件后（即订单确认与采购订单中的单价一致），系统会触发“开始导出”操作。这通常会将发票数据导出以供进一步处理，例如发送到其他财务系统或用于报告。
#### 此规则的目的：
* **确保准确性和一致性**：通过验证订单确认与采购订单中的单价是否一致，系统有助于保持财务数据准确，并防止多收或少收款项。
* **简化财务处理**：确认价格后自动导出数据，可减少人工操作并加快财务处理周期。
* **加强合规与监督**：要求对价格进行第二次审批，增加了一层监督，这对于遵守财务政策和控制要求至关重要。
此规则展示了如何有效利用工作流自动化，在组织内精确、高效地处理财务文档，尤其适用于需要细致验证的大量交易。
---
# 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-unit-price-export.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.
