> 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-4-5-quantity-within-tolerance-unit-price-outside-tolerance-approved.md).
# 情况 4、5：数量在容差范围内，单价超出容差（已审批）
## 场景：
发票上的数量在容差范围内，但单价超出可接受的容差范围。不过，相关主管部门已经审核并批准了这项单价差异。
## 操作：
系统会将单价调整为与采购订单一致，并应用必要的行费用来补足差额。
## 示例：
**采购订单 (PO)：**
数量：100 件
单价：每件 $10.00
总金额：$1,000.00
**收到的发票：**
数量：100 件（在容差范围内）
单价：每件 $11.00（超出 ±5% 的容差范围）
总金额：$1,100.00
**容差级别：**
数量容差：±2%
单价容差：±5%（预期范围：$9.50 至 $10.50）
**审批：**
• $11.00 的单价超出容差范围，但已由相关部门手动审批。
由于数量在容差范围内，但单价超出容差范围（且已获批准），系统将：
1\. **调整单价**：由于差异已获批准，系统会将单价调整回采购订单中的单价：
• **调整后的单价 = 每件 $10.00**
• **调整后的总金额 = 100 件 × 每件 $10.00 = $1,000.00**
2\. **应用差额行费用**：由于已批准的 $11.00 发票单价高于采购订单中的 $10.00 单价，系统会应用一笔行费用来补足差额：
• **行费用金额 =（已批准的发票单价 - 采购订单单价）× 数量**
• **行费用金额 =（$11.00 - $10.00）× 100 件 = $100.00**
3\. **处理发票**：系统按以下金额处理发票：
• **基础金额：** $1,000.00
• **行费用：** $100.00
• **处理后的总金额：** $1,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-4-5-quantity-within-tolerance-unit-price-outside-tolerance-approved.md?ask=&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.