> 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-11b-quantity-outside-tolerance-positive-rejected-unit-price-outside-tolerance-rejected.md).

# 案例 11b：数量超出容差（超出部分拒收），单价超出容差（拒收）

## 场景：

数量超过可接受范围（正向超出）并被拒收，单价也超出容差并被拒收。

## 操作：

系统将数量和单价调整为采购订单中已批准的数值，拒收超出部分，并处理该交易。

## 示例：

* **采购订单 (PO)：**
  * 数量：200 件
  * 单价：每件 $50.00
  * 总金额：$10,000.00
* **收到的发票：**
  * 数量：220 件（超出 10% 的容差，被拒收）
  * 单价：每件 $55.00（超出 10% 的容差，被拒收）
  * 总金额：$12,100.00
* **容差级别：**
  * 数量容差：±5%
  * 单价容差：±2%

由于数量（220 件）和单价（$55.00）均超出可接受的容差限值，且都未获批准，系统将：

1. \*\*拒收超出部分的数量：\*\*系统不接受发票上的 220 件数量，而是将其调整为与原采购订单一致。
   * 调整后的数量 = 200 件（来自 PO）
2. \*\*拒收发票单价：\*\*系统不接受发票上的 $55.00 单价，而是将其调整为与原采购订单一致。
   * 调整后的单价 = 每件 $50.00（来自 PO）
3. \*\*重新计算总金额：\*\*系统使用调整后的数量和单价计算总金额：
   * **更正后的总金额 = 调整后的数量 × 调整后的单价**
   * **更正后的总金额 = 200 件 × 每件 $50.00 = $10,000.00**
4. \*\*处理发票：\*\*系统以更正后的总金额 $10,000.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-11b-quantity-outside-tolerance-positive-rejected-unit-price-outside-tolerance-rejected.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.