> 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/setup/testing/po-matching.md).

# PO 匹配

测试 PO 匹配配置时，需要在 LN/M3 中创建一张采购订单，以检查 INFOR 是否已与 DocBits 同步。

## 在 INFOR 中创建采购订单

* LN: <https://docs.infor.com/ln/10.4/en-us/lnolh/docs/ln\\_10.4\\_procpoug\\_\\_en-us.pdf>
* M3: <https://docs.infor.com/m3udi/16.x/en-us/m3beud/default.html?helpcontent=ois610.html>

创建采购订单后，前往 Settings → Master Data Lookup，搜索刚创建的采购订单编号。此时，该订单应已显示在 DocBits 的采购订单主数据中。

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-5718caef68d471ac4861f805e677af8d9d885dea%2Fdbdc206-purchase-order-bod-input-en.png?alt=media" alt="主数据查找页面，显示已导入采购订单的 Purchase Order 表格。"><figcaption><p>采购订单显示在主数据查找中。</p></figcaption></figure>

您应能在此处看到唯一的 PO 编号，这表示 DocBits 与 INFOR 已正确同步。

现在上传一张发票，其数量和单价与您创建的采购订单相符。验证文档，并在验证界面选择 PO Matching。

PO 和发票的行项目应自动匹配。然后选择导出选项，并检查文档能否无误导出。如果遇到导出错误，请创建工单联系 DocBits 支持团队寻求帮助。如果您不确定如何在 DocBits 中创建工单，请参阅 DocBits Overview 文档以获取帮助。

\\


---

# 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/setup/testing/po-matching.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.