> 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/tax-lines.md).

# 税费行

## 场景：

处理发票与采购订单之间的税额差异。

## 操作：

系统根据已批准的税率和金额调整税费行，确保符合适用的税务法规。

## 示例：

* **采购订单 (PO)：**
  * 小计金额：$10,000.00
  * 税率：8%
  * 预期税额：$800.00
  * 含税总额：$10,800.00
* **收到的发票：**
  * 小计金额：$10,000.00
  * 税率：10%（存在差异）
  * 发票税额：$1,000.00
  * 含税总额：$11,000.00

由于发票上的税率（10%）与预期税率（8%）不同，且未获批准，系统将：

1. **拒绝发票税率：** 系统不接受 10% 的税率，因为它与采购订单中已批准的税率不一致。
2. **调整税率：** 系统将税率调整为与采购订单中已批准的税率一致。
   * 调整后的税率 = 8%（来自 PO）
3. **重新计算税额：** 系统根据调整后的税率重新计算税额：
   * **更正后的税额 = 小计金额 × 调整后的税率**
   * **更正后的税额 = $10,000.00 × 8% = $800.00**
4. **重新计算总额：** 系统重新计算含税总额：
   * **更正后的含税总额 = 小计金额 + 更正后的税额**
   * **更正后的含税总额 = $10,000.00 + $800.00 = $10,800.00**
5. **生成贷项通知单：** 系统生成贷项通知单以更正多收的税款：
   * **贷项通知单金额 = 原发票税额 - 更正后的税额**
   * **贷项通知单金额 = $1,000.00 - $800.00 = $200.00**
6. **处理发票：** 系统以更正后的税额 $800.00 和总额 $10,800.00 处理发票，并针对 $200.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/tax-lines.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.