> 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.md).
# 工作流示例
#### 工作流组件概览：
* **应付账款发票电子邮件**：流程可能从通过电子邮件收到发票开始。
* **DocBits**：此工具可能用于初步文档管理任务，例如采集和数字化发票。
* **财务审核**：发票会经过财务审核，以判断其有效性和准确性。
#### 工作流步骤：
1. **初步审核**：
* 使用 DocBits 接收并初步处理发票。
* 随后由财务团队审核，确保已完成的发票从工作流中移除，或将其推进至后续处理环节。
2. **采购订单发票与非采购订单发票**：
* 工作流会区分与采购订单相关的发票和非采购订单发票。
* 非采购订单发票会根据供应商 ID、数量、单价和项目编号等预定义条件，路由至后续审批或拒绝环节。
3. **匹配与不匹配**：
* 系统会将发票与收货记录进行核对，以确保详细信息（如供应商 ID 和数量）一致。
* 如果出现不匹配，发票将进入进一步审核，并可能被拒绝。
4. **财务与采购员审核**：
* 对于与采购订单相关的发票，会进行详细的匹配流程，其中包括采购员审核。
* 可能需要调整采购订单或收货记录。
5. **最终决定**：
* 通过所有检查的发票将获批并集成到财务系统中，以便记录留存。
* 被拒绝的发票会触发通知，采购员可能会要求提供新发票。
6. **与 Infor IDM 和 LN+M3 集成**：
* 获批的发票可能会发送至 Infor 的 IDM 进行文档管理，并发送至 LN 进行账簿记录。
* 此集成可确保所有财务记录保持最新，并让工作流顺畅接入更广泛的 ERP 系统。
#### 决策点：
* 在整个工作流中设有多个决策点，可决定发票获批、被拒绝或退回以补充信息。延迟后会发送通知，以确保处理及时。
这些工作流将纳入标准工作流
---
# 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.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.
.svg?alt=media)