> 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/settings/document-processing/module/auto-export-if-po-matched-100.md).

# PO 匹配度为 100% 时自动导出

### 概述

**PO 匹配度为 100% 时自动导出**设置是采购订单（PO）模块中的一项功能。当采购订单完全符合预期条件时，该功能会自动执行导出流程。它旨在通过减少导出过程中的人工干预来简化工作流，确保完全匹配的采购订单得到高效处理。

### 它的作用

启用此设置后，系统会在采购订单与预期数据达到 100% 匹配时立即自动导出采购订单。也就是说，如果采购订单中的所有物料、数量、价格及其他相关详情都符合预定义条件，系统便会立即处理并导出订单，无需用户执行其他步骤。

### 优势

* **效率**：自动导出完全匹配的采购订单，节省时间并减轻管理员和用户的工作负担。
* **准确性**：确保只有经验证、与预期条件达到 100% 匹配的采购订单才会被导出，从而降低出错风险。
* **速度**：立即处理匹配的采购订单，加快订单处理速度并减少供应链延迟。

### 使用方法

1. **启用此功能**：
   * 前往 Settings
   * 选择 **Document Processing**。
   * 选择 **Module**。
   * 前往 **Purchase Order**。
   * 启用对应的滑块，激活 **Auto Export if PO matched 100%**。
2. **监控**：
   * 启用后，系统会自动导出与预期条件达到 100% 匹配的采购订单。
   * 您可以通过 PO 仪表板或其他相关监控工具查看导出活动。
3. **注意事项**：
   * 请确保采购订单条件定义正确且准确，以避免意外导出。
   * 定期检查通过此功能处理的采购订单，确保自动化功能按预期运行。

### 何时使用此功能

* **大批量处理**：适用于定期处理大量采购订单且对数据匹配有较高信心的场景。
* **常规订单**：适用于差异较少且准确性稳定的标准或常规订单。
* **时效性强的订单**：当时间紧迫且需要加快匹配订单的处理速度时，此功能会很有帮助。


---

# 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/settings/document-processing/module/auto-export-if-po-matched-100.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.