> 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-15-header-charge-charge-per-unit-outside-tolerance-rejected.md).

# 案例 15：抬头费用——单位费用超出容差范围（已拒绝）

## 场景：

抬头单位费用超出容差范围，且尚未获得批准。

## 操作：

系统将抬头费用调整为与采购订单一致，并据此处理交易，同时生成任何必要的备注。

## 示例：

* **采购订单（PO）：**
  * 抬头单位费用：$4.00
  * 数量：1,500 个单位
  * 抬头费用总额：$6,000.00
* **收到的发票：**
  * 抬头单位费用：$5.00（高于采购订单价格 25%，超出 ±5% 容差，已拒绝）
  * 数量：1,500 个单位
  * 抬头费用总额：$7,500.00
* **容差级别：**
  * 抬头单位费用容差：±5%

由于抬头单位费用（$5.00）超出 5% 的可接受容差范围，且尚未获得批准，系统将：

1. \*\*拒绝发票中的抬头单位费用：\*\*由于差异超出容差限值，系统不接受发票中的 $5.00 抬头单位费用。
2. \*\*调整抬头单位费用：\*\*系统将单位费用调整为与原始采购订单或已批准的单位费用一致：
   * 调整后的抬头单位费用 = $4.00（来自 PO）
3. \*\*重新计算抬头费用总额：\*\*系统根据调整后的单位费用重新计算费用总额：
   * **更正后的抬头费用总额 = 数量 × 调整后的抬头单位费用**
   * **更正后的抬头费用总额 = 1,500 个单位 × $4.00 = $6,000.00**
4. \*\*生成贷项通知单：\*\*由于原始发票总额高于更正后的总额，系统会针对多收的金额生成贷项通知单：
   * **贷项通知单金额 = 原始发票总额 - 更正后的抬头费用总额**
   * **贷项通知单金额 = $7,500.00 - $6,000.00 = $1,500.00**
5. \*\*处理发票：\*\*系统按更正后的费用总额 $6,000.00 处理发票，并开具金额为 $1,500.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-15-header-charge-charge-per-unit-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.