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

# 案例 6：数量在容差范围内，单价超出负向容差（拒绝）

## 场景：

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

## 操作：

系统拒绝该单价，将其调整为与采购订单一致，并针对差额生成贷项通知单。必要时还可应用额外的抬头费用。

## 示例：

* **采购订单（PO）：**
  * 数量：100 件
  * 单价：每件 $10.00
  * 总金额：$1,000.00
* **收到的发票：**
  * 数量：100 件（在 0% 容差范围内）
  * 单价：每件 $9.00（超出 -10% 的负向容差）
  * 总金额：$900.00
* **容差级别：**
  * 数量容差：±2%
  * 单价容差：±1%

由于数量（100 件）在可接受的容差范围内，但单价（$9.00）低于可接受范围且未获批准，系统将：

1. \*\*拒绝单价：\*\*系统不接受发票中的 $9.00 单价。
2. \*\*调整单价：\*\*系统将单价调整为与原采购订单中的单价一致。
   * 调整后的单价 = $10.00（来自 PO）
3. \*\*计算更正后的总金额：\*\*系统使用调整后的单价重新计算总金额。
   * **更正后的总金额 = 数量 × 调整后的单价**
   * **更正后的总金额 = 100 件 × 每件 $10.00 = $1,000.00**
4. \*\*生成贷项通知单：\*\*系统针对发票错误总金额与更正后总金额之间的差额生成贷项通知单。
   * **贷项通知单金额 = 原发票总金额 - 更正后的总金额**
   * **贷项通知单金额 = $900.00 - $1,000.00 = -$100.00**
   * 贷项通知单将有效冲销少收的金额。
5. \*\*处理发票：\*\*系统以调整后的总金额 $1,000.00 处理发票，并应用金额为 $100.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-6-quantity-within-tolerance-unit-price-outside-negative-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.