> 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-8b-9b-quantity-outside-tolerance-approved-unit-price-outside-tolerance-approved.md).

# 案例 8b、9b：数量超出容差（已审批），单价超出容差（已审批）

## 场景：

数量和单价均超出容差范围，但都已获审批。

## 操作：

系统使用发票中的数量和单价处理交易，并应用任何必要的调整或行项目费用。

## 示例：

* **采购订单 (PO)：**
  * 数量：200 件
  * 单价：每件 $25.00
  * 总金额：$5,000.00
* **收到的发票：**
  * 数量：220 件（超出 10% 的容差，已审批）
  * 单价：每件 $27.00（超出 8% 的容差，已审批）
  * 总金额：$5,940.00
* **容差级别：**
  * 数量容差：±5%
  * 单价容差：±2%

由于数量（220 件）和单价（$27.00）均超出可接受的容差范围，但已获审批，系统将：

1. **接受已审批的数量：** 尽管发票数量超出容差范围，系统仍会接受 220 件这一数量，因为该数量已获审批。
2. **接受已审批的单价：** 尽管发票单价超出容差范围，系统仍会接受每件 $27.00 的单价，因为该单价已获审批。
3. **计算总金额：** 系统根据已审批的发票值计算总金额：
   * **总金额 = 数量 × 单价**
   * **总金额 = 220 件 × 每件 $27.00 = $5,940.00**
4. **应用必要的调整或行项目费用：** 如适用，系统可能会根据组织处理已审批差异的政策，应用任何额外的行项目费用或调整。
5. **处理发票：** 系统使用已审批的数量和单价处理发票，并以 $5,940.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-8b-9b-quantity-outside-tolerance-approved-unit-price-outside-tolerance-approved.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.