> 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/setup/testing/auto-accounting.md).

# Auto Accounting

Auto Accounting needs an enabled module, accounting master data and an invoice with usable amounts or line items. This guide separates the settings you can check before opening an invoice from the checks that require a configured LN or M3 connection.

## Check the module settings

1. Open **Settings → Module → Order & Finance** and expand **Auto accounting**. The older **Document Processing → Module → Purchase Order / Auto Accounting** path is no longer the route shown in the current application.
2. Choose the **Type** for your connected system (**LN** or **M3**). Turn on **Auto accounting** only when the required master data and connection are ready.
3. When enabled, select the **Accounts** list and the dimension lists appropriate to your system. For LN, the visible fields include **Dimension Range Dropdown** and **Dimension List Name**. M3 has different fields. Use **Reset accounting data on element change** only if recalculation after a changed element is intended.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-26d6ff64f7949387fde30a08b1f00e0c4e2cb154%2Fdbdc-174-auto-accounting-off-en.png?alt=media" alt="English Order and Finance module settings with Auto accounting switched off and Type set to LN"><figcaption><p>Auto accounting is off in the English Sandbox test organisation.</p></figcaption></figure>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-75e5a3aa3b363e0ab7c0613eaf855b9114398f89%2Fdbdc-174-auto-accounting-on-en.png?alt=media" alt="English Order and Finance module settings temporarily enabled, revealing account and dimension selectors"><figcaption><p>The fields shown when the setting is enabled. It was switched off again after this capture; no accounts or dimensions were configured.</p></figcaption></figure>

## Test with a configured invoice

Use an invoice whose line items and accounting master data are available. Open it in the validation screen and select **Auto Accounting**. If the action is missing, check the module setting and whether this invoice is eligible. Validate the invoice before navigating; the application saves and validates when the action is selected.

On the accounting screen, verify the following with your own LN or M3 data:

1. Run **Validate Setup** where available and resolve missing account or dimension configuration before proceeding. A green result only describes the checks in your environment.
2. Check whether the invoice should be assigned by its **total** or by **individual line items**. Compare the accounting amounts with the original invoice.
3. If you split an amount, select the intended account for each split row. Enter amounts or percentages and check that the allocated values add up to the parent amount. Add or remove a row only when needed.
4. Review any **Unsettled amount** or validation warning and correct it before saving or exporting. Confirm the result in the connected system separately.

The Sandbox test organisation used for the screenshots above has no configured account and dimension lists or invoice line items for this flow. The accounting screen, splitting and export were therefore **not tested or pictured here**. Do not use the settings screenshots as proof that accounting or export succeeded.

For system-specific setup, continue with the [LN guide](/administration-and-setup/setup/testing/auto-accounting/ln.md) or [M3 guide](/administration-and-setup/setup/testing/auto-accounting/m3.md).


---

# 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/setup/testing/auto-accounting.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.