> 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-12-13-header-charge-charge-per-unit-within-tolerance.md).

# 单位抬头费用在容差范围内

## 场景：

与采购订单相比，单位抬头费用在可接受的容差范围内。

## 操作：

系统按发票所列金额处理抬头费用，不作调整。

## 示例：

* **采购订单 (PO)：**
  * 单位抬头费用：$3.50
  * 数量：1,200 件
  * 抬头费用总额：$4,200.00
* **收到的发票：**
  * 单位抬头费用：$3.55（在 1.43% 的容差范围内）
  * 数量：1,200 件
  * 抬头费用总额：$4,260.00
* **容差级别：**
  * 单位抬头费用容差：±2%

由于单位抬头费用（$3.55）与采购订单相比处于 2% 的可接受容差范围内，系统将：

1. \*\*接受单位抬头费用：\*\*系统接受发票所列的单位抬头费用 $3.55，因为该金额在规定的容差限值内。
2. \*\*处理抬头费用：\*\*系统根据发票所列的单位费用和数量，按抬头费用总额处理发票：
   * **抬头费用总额 = 数量 × 单位抬头费用**
   * **抬头费用总额 = 1,200 件 × $3.55 = $4,260.00**
3. \*\*完成发票处理：\*\*系统无需进行任何调整即可处理该交易，并按原样接受发票。

这种方法可确保在抬头费用处于可接受的容差范围内时，交易得到顺畅、高效的处理，避免不必要的拒收或延误。


---

# 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-12-13-header-charge-charge-per-unit-within-tolerance.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.