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

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

## 场景：

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

## 操作：

系统拒绝发票单价，将其调整为与采购订单一致，并可能生成借项通知单，以处理多收的金额。

## 示例：

* **采购订单（PO）：**
  * 数量：200 件
  * 单价：每件 $15.00
  * 总金额：$3,000.00
* **收到的发票：**
  * 数量：198 件（在 1% 的容差范围内）
  * 单价：每件 $17.00（超出正向容差 13.33%）
  * 总金额：$3,366.00
* **容差级别：**
  * 数量容差：±2%
  * 单价容差：±1%

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

1. \*\*拒绝发票单价：\*\*系统不接受发票中的单价 $17.00。
2. \*\*调整单价：\*\*系统将单价调整为与原采购订单单价一致。
   * 调整后的单价 = $15.00（取自 PO）
3. \*\*计算更正后的总金额：\*\*系统使用调整后的单价重新计算总金额。
   * **更正后的总金额 = 数量 × 调整后的单价**
   * **更正后的总金额 = 198 件 × 每件 $15.00 = $2,970.00**
4. \*\*生成借项通知单：\*\*系统生成借项通知单，以处理多收金额造成的差额。
   * **借项通知单金额 = 原发票总金额 - 更正后的总金额**
   * **借项通知单金额 = $3,366.00 - $2,970.00 = $396.00**
   * 该借项通知单表示供应商多收的金额。
5. \*\*处理发票：\*\*系统按更正后的总金额 $2,970.00 处理发票，并签发金额为 $396.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-7-quantity-within-tolerance-unit-price-outside-tolerance-positive-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.