> 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/module/set-negative-sign-for-credit-notes.md).

# 为贷项通知单设置负号

### 概述

**为贷项通知单设置负号**用于确保**贷项通知单**以**负数金额**存储。贷项通知单会冲销或退还部分发票金额，因此在会计处理中，其数值应减少总额，也就是说应为负数。启用此设置后，DocBits 会自动为您添加负号。

此设置**默认启用**。

### 此设置有什么作用？

当文档被识别为**贷项通知单**时，DocBits 会在处理过程中自动将其金额转换为负数。这会影响货币字段，包括净额、税额和总额（例如净额、税额、税额总计、净额总计和总金额）。

* **已启用（默认）** — 贷项通知单的金额会以负数保存（例如，`150.00` 会变为 `-150.00`）。普通发票不受影响。
* **已禁用** — 金额保持从文档中读取的原样，不更改正负号。

{% hint style="info" %}
此设置仅适用于被识别为**贷项通知单**的文档。普通发票始终保持不变。
{% endhint %}

### 优点

* **确保账务正确**：贷项通知单会减少余额，因此负数是会计和 ERP 系统所需的格式。
* **无需手动编辑**：团队无需在每张贷项通知单上手动更改正负号。
* **保持一致**：组织内的每张贷项通知单都会以相同方式处理。

### 使用方法

1. 前往**设置**（**Settings**）。
2. 选择**文档处理**（**Document Processing**）。
3. 选择**模块**（**Module**）。
4. 打开**文档类型**（**Document Type**）部分。
5. 找到**为贷项通知单设置负号**（**Set Negative Sign for Credit Notes**），然后打开或关闭开关。

### 何时使用此功能

* 如果您的会计或 ERP 系统要求贷项通知单以负数金额传入，请**保持启用**（这是最常见的配置）。
* 仅当下游系统已自行处理正负号，或要求贷项通知单金额保持为正数时，才**禁用此设置**。


---

# 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/module/set-negative-sign-for-credit-notes.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.