> 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.md).
# 发票上的供应商
## **用途：**
此工作流卡片用于将发票上的供应商信息与相关采购订单上的供应商信息进行比较。该卡片可确保发票上的供应商与采购订单上的供应商一致。此比较有助于验证开具该订单发票的供应商是否正确，并可根据差异触发相应操作。
## **卡片组件：**
1. **运算符：**
* **说明**：定义用于比较发票上的供应商与采购订单上的供应商的条件。
* **选项**：
* **是**：检查发票上的供应商是否与采购订单上的供应商一致。
* **不是**：确保发票上的供应商与采购订单上的供应商不一致。
## **功能：**
* \*\*条件评估：\*\*系统根据所选运算符，将发票上的供应商与采购订单上的供应商进行比较。如果比较条件为真（例如，供应商按要求相同或不同），工作流将相应地继续执行。
* **执行操作：**
* **条件为真**：如果条件评估结果为真（例如，发票上的供应商与采购订单上的供应商一致），工作流将继续执行，且不会触发任何错误。
* **条件为假**：如果条件评估结果为假（例如，发票上的供应商与采购订单上的供应商不一致），工作流将不会继续执行。
## **设置和配置：**
* 用户选择合适的运算符（“是”或“不是”），以定义如何比较供应商。
## **示例场景：**
* 一张发票列出的供应商 ID 为“SUP123”，相关采购订单也将“SUP123”列为供应商。使用“是”运算符时，卡片会比较这两个供应商并确认其相同，因此工作流会顺利继续执行。
## **结论：**
“供应商比较”工作流卡片可确保为采购订单开具发票的供应商正确无误，有助于防止采购流程中出现差异和错误。通过自动验证供应商信息，组织可以简化发票审批流程，并降低供应商账单中出现欺诈或错误的风险。
---
# 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.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.
.png?alt=media)