> 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-10a-quantity-outside-tolerance-negative-rejected-unit-price-within-tolerance.md).

# 案例 10a：数量超出容差（负向偏差不予接受），单价在容差范围内

## 场景：

数量低于可接受范围（负向容差），因此未获批准；单价则在容差范围内。

## 操作：

系统将数量调整为已批准的数量，同时保持单价不变。随后按调整结果处理交易。

## 示例：

* **采购订单（PO）：**
  * 数量：150 件
  * 单价：每件 $20.00
  * 总金额：$3,000.00
* **收到的发票：**
  * 数量：140 件（超出 -6.67% 的容差范围，未获接受）
  * 单价：每件 $20.00（在容差范围内）
  * 总金额：$2,800.00
* **容差级别：**
  * 数量容差：±5%
  * 单价容差：±2%

由于数量（140 件）低于可接受的容差下限（负向偏差为 -6.67%），因此未获批准；但单价（$20.00）在容差范围内，系统将执行以下操作：

1. \*\*拒绝较低的数量：\*\*数量超出已批准的容差范围，因此系统不接受较低的数量。
2. \*\*调整数量：\*\*系统将数量调整为采购订单中指定的已批准数量。
   * 已批准数量 = 150 件（来自 PO）
3. \*\*保持单价不变：\*\*每件 $20.00 的单价在容差范围内，因此保持不变。
4. \*\*重新计算总金额：\*\*系统使用已批准的数量和接受的单价计算总金额：
   * **总金额 = 已批准数量 × 单价**
   * **总金额 = 150 件 × 每件 $20.00 = $3,000.00**
5. \*\*处理发票：\*\*系统按调整后的总金额 $3,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-10a-quantity-outside-tolerance-negative-rejected-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.