> 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/administration-and-setup/settings/document-processing/module/set-negative-sign-for-credit-notes.md).

# Set Negative Sign for Credit Notes

### Overview

The **Set Negative Sign for Credit Notes** setting makes sure that **credit notes** are stored with **negative amounts**. A credit note reverses or refunds part of an invoice, so in accounting its values should reduce the totals — that is, they should be negative. When this setting is on, DocBits applies that negative sign for you automatically.

This setting is **enabled by default**.

### What Does It Do?

When a document is recognized as a **credit note**, DocBits automatically turns its amounts into negative values during processing. This affects the monetary fields, including the net amounts, tax amounts and totals (e.g. net amount, tax amount, total tax amount, total net amount and total amount).

* **Enabled (default)** — Credit note amounts are saved as negative values (for example, `150.00` becomes `-150.00`). Regular invoices are not affected.
* **Disabled** — Amounts are kept exactly as they were read from the document, without any sign change.

{% hint style="info" %}
This only applies to documents identified as **credit notes**. Normal invoices are always left unchanged.
{% endhint %}

### Benefits

* **Correct bookkeeping**: Credit notes reduce balances, so negative values are what your accounting and ERP systems expect.
* **No manual editing**: Your team doesn’t have to flip the sign by hand on every credit note.
* **Consistency**: Every credit note is handled the same way across your organization.

### How to Use

1. Go to **Settings**.
2. Select **Document Processing**.
3. Select **Module**.
4. Open the **Document Type** section.
5. Find **Set Negative Sign for Credit Notes** and switch the toggle on or off.

### When to Use This Feature

* **Keep it enabled** if your accounting or ERP system expects credit notes to arrive with negative amounts (this is the most common setup).
* **Disable it** only if your downstream system already handles the sign itself, or expects credit note amounts to stay positive.

## Wrong document type?

This setting depends on correct credit note classification. If an eDoc is stored as Invoice, first check the transformation, Extraction Paths and later scripts. Follow the [classification troubleshooting guide](/administration-and-setup/settings/global-settings/document-types/edi/credit-note-recognized-as-invoice.md) before changing signs or restarting existing documents.


---

# 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/administration-and-setup/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.