> 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/cards-overview/and/compare-with-purchase-order/supplier-on-invoice-1.md).
# 发票上的供应商
## **用途**
此 DocBits 卡片可详细比较发票上的供应商与订单确认中的供应商。系统应确保开具发票的供应商与订单确认中的供应商相同。
## **功能：**
* **发票上的供应商与采购订单上的供应商：** 此卡片用于检查发票上的供应商是否与订单确认中的供应商相同。
* **运算符值：** 用户可以设置特定条件，例如：开具发票的供应商是否与采购订单中的供应商相同。可用运算符包括：
* **是 (=)：** 检查发票上的供应商是否与订单确认中的供应商一致。
* **不是 (≠)：** 确保开具发票的供应商与订单确认中的供应商不同。
## **用法：**
此卡片有助于确保整个流程由同一供应商处理，并确保各项内容相互匹配。如果存在差异，系统会提醒用户检查这些差异，避免向与订单及订单确认无关的错误供应商支付发票。
## **示例场景：**
* 下达订单后，会收到订单确认，随后开具发票。整个订购流程都由同一家供应商完成。如果实际情况并非如此，此卡片可以立即发现供应商之间的差异，从而确保不会发生错误付款，并且只向参与整个流程的供应商开具发票。
使用“发票上的供应商 … 采购订单上的供应商”卡片，企业可以自动验证发票开具供应商及其对应的订单确认。
---
# 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/cards-overview/and/compare-with-purchase-order/supplier-on-invoice-1.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.
%20(1).png?alt=media)