> 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/charge-per-unit-outside-tolerance-approved.md).

# 案例 14：抬头费用 - 单位费用超出容差（已审批）

## 场景：

抬头单位费用超出容差，但已获得审批。

## 操作：

系统处理已审批的单位费用，并将其应用于交易。

## 示例：

* **采购订单 (PO)：**
  * 抬头单位费用：$2.50
  * 数量：2,000 件
  * 抬头费用总额：$5,000.00
* **收到的发票：**
  * 抬头单位费用：$3.00（高于采购订单价格 20%，超出 ±5% 容差，已审批）
  * 数量：2,000 件
  * 抬头费用总额：$6,000.00
* **容差级别：**
  * 抬头单位费用容差：±5%

由于抬头单位费用（$3.00）超出 5% 的可接受容差范围，但已获得审批，系统将：

1. **接受已审批的抬头单位费用：** 尽管超出容差限值，系统仍接受已审批的发票抬头单位费用 $3.00。
2. **处理抬头费用：** 系统使用已审批的单位费用和数量处理发票：
   * **抬头费用总额 = 数量 × 已审批的抬头单位费用**
   * **抬头费用总额 = 2,000 件 × $3.00 = $6,000.00**
3. **完成发票处理：** 系统使用已审批的费用处理交易，反映 $6,000.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/charge-per-unit-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.