> 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-rejected-1.md).

# 超出容差的单位费用（已拒绝）

## 场景：

单位费用超出容差，且尚未获得审批。

## 操作：

系统会调整单位费用，使其与采购订单或已批准的金额一致，并按需生成借项通知单或贷项通知单。

## 示例：

* **采购订单 (PO)：**
  * 单位费用：$6.00
  * 数量：800 件
  * 费用总额：$4,800.00
* **收到的发票：**
  * 单位费用：$7.00（超出 16.67% 的容差，已拒绝）
  * 数量：800 件
  * 费用总额：$5,600.00
* **容差级别：**
  * 单位费用容差：±5%

由于单位费用（$7.00）超出 5% 的可接受容差范围，且尚未获得审批，系统将执行以下操作：

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