> 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/cost-invoice-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/cost-invoice-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.
