> 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/rule-manager/transactionconfig-pro-template/case-1-2-3-quantity-and-unit-price-within-tolerance.md).

# 案例 1、2、3：数量和单价在容差范围内

## 场景：

与采购订单相比，发票上的数量和单价都在可接受的容差范围内。

## 操作：

系统接受发票上的数值，并根据提供的数量和单价计算总金额。

## 示例：

**采购订单 (PO)：**

数量：100 件

单价：每件 $10.00

总金额：$1,000.00

**收到的发票：**

数量：101 件（在 1% 的容差范围内）

单价：每件 $10.05（在 0.5% 的容差范围内）

总金额：$1,015.05

**容差级别：**

数量容差：±2%

单价容差：±1%\\

由于数量（101 件）和单价（$10.05）都在与采购订单相比可接受的容差范围内，系统将：\\

1\. \*\*接受发票数值：\*\*由于发票上的数量和单价处于定义的容差范围内，因此将其视为有效值并予以接受。

2\. \*\*计算总金额：\*\*使用接受的数值计算总金额：

• 总金额 = 数量 × 单价

• 总金额 = 101 件 × 每件 $10.05 = $1,015.05

3\. \*\*处理发票：\*\*系统将按总金额 $1,015.05 处理发票，并相应更新财务记录。

这种做法可确保在可接受容差范围内的轻微差异不会导致发票被拒或付款延迟，从而简化财务流程。


---

# 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/rule-manager/transactionconfig-pro-template/case-1-2-3-quantity-and-unit-price-within-tolerance.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.