> 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-8a-9a-quantity-outside-tolerance-approved-unit-price-within-tolerance.md).

# 案例 8a、9a：数量超出容差（已批准），单价在容差范围内

## 场景：

发票上的数量超出了可接受的容差范围，但已获批准；单价仍在容差范围内。

## 操作：

系统接受已批准的数量和发票上的单价，并据此处理交易。

## 示例：

* **采购订单 (PO)：**
  * 数量：150 件
  * 单价：每件 $12.00
  * 总金额：$1,800.00
* **收到的发票：**
  * 数量：160 件（超出 6.67% 的容差，但已获批准）
  * 单价：每件 $12.00（在容差范围内）
  * 总金额：$1,920.00
* **容差级别：**
  * 数量容差：±5%
  * 单价容差：±2%

由于数量（160 件）超出了可接受的容差上限，但已获批准；而单价（$12.00）在可接受范围内，系统将：

1. \*\*接受已批准的数量：\*\*系统确认该数量已获批准，尽管它超出了常规容差范围。
2. \*\*接受单价：\*\*每件 $12.00 的单价在可接受的容差范围内，因此按发票所列单价接受。
3. \*\*处理交易：\*\*系统使用已批准的数量和单价计算总金额：
   * **总金额 = 数量 × 单价**
   * **总金额 = 160 件 × 每件 $12.00 = $1,920.00**
4. \*\*完成发票处理：\*\*系统按总金额 $1,920.00 处理发票，该金额反映了已批准的数量和接受的单价。

这种处理方式允许系统接受已批准的数量差异，同时确保单价保持在预期范围内，从而顺利处理交易。


---

# 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-8a-9a-quantity-outside-tolerance-approved-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.