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

# 案例 10b：数量超出容差（拒绝），单价超出容差（拒绝）

## 场景：

数量和单价均超出容差，且两者都未获审批。

## 操作：

系统拒绝发票数据，将数值调整为与采购订单一致，并生成所需的借项或贷项通知单。

## 示例：

* **采购订单（PO）：**
  * 数量：150 件
  * 单价：每件 $30.00
  * 总金额：$4,500.00
* **收到的发票：**
  * 数量：140 件（超出 -6.67% 的容差，已拒绝）
  * 单价：每件 $33.00（超出 10% 的容差，已拒绝）
  * 总金额：$4,620.00
* **容差级别：**
  * 数量容差：±5%
  * 单价容差：±2%

由于数量（140 件）和单价（$33.00）均超出可接受的容差范围，且两者都未获审批，系统将：

1. \*\*拒绝发票数据：\*\*由于开票数量和单价偏离容差范围，系统不予接受。
2. \*\*调整数量：\*\*系统将数量调整为与原采购订单数量一致。
   * 调整后数量 = 150 件（来自 PO）
3. \*\*调整单价：\*\*系统将单价调整为与原采购订单单价一致。
   * 调整后单价 = 每件 $30.00（来自 PO）
4. \*\*重新计算总金额：\*\*系统使用调整后的数量和单价重新计算总金额：
   * **更正后总金额 = 调整后数量 × 调整后单价**
   * **更正后总金额 = 150 件 × 每件 $30.00 = $4,500.00**
5. \*\*生成借项通知单：\*\*由于原发票总金额高于更正后的总金额，系统会针对多收金额生成借项通知单。
   * **借项通知单金额 = 原发票总金额 - 更正后总金额**
   * **借项通知单金额 = $4,620.00 - $4,500.00 = $120.00**
6. \*\*处理发票：\*\*系统以更正后的总金额 $4,500.00 处理发票，并开具金额为 $120.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-10b-quantity-outside-tolerance-negative-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.