> 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/global-settings/document-types.md).

# Document Types

{% embed url="<https://youtu.be/pFz_6tvNlU4>" %}
DocBits Document Types Explained: Create, Configure & Assign Processing Settings
{% endembed %}

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-583a6ea920c8a79e3f8cdb7b7447d32ab88b4eaa%2Fdocument-types-overview-page-en-20261014.png?alt=media" alt="The Document Types page in DocBits settings: default document types (Invoice, Credit Note, Delivery Note, Order Confirmation, Purchase Order, Contract) and custom document types, each card with Activate and Extraction switches, a settings gear, and links to Layouts, Fields, Tables, Validation Rules, Transformation Rules, Scripts, Model Training, E-Doc, Document Sub Types and Logs"><figcaption><p>The Document Types page. Each card carries the Activate and Extraction switches, the settings gear, and the configuration links described below.</p></figcaption></figure>

## Overview

The Document Types page lists all document types recognized and processed by DocBits. It is divided into two sections:

* **Default Document Types**: Pre-configured types provided by DocBits (Invoice, Credit Note, Delivery Note, Order Confirmation, Contract, ZUGFeRD, etc.). These cannot be deleted.
* **Custom Document Types**: Types you create for your specific business needs. These can be edited and deleted.

## Controls per Document Type

Each document type card shows:

| Control                  | Description                                                                                                                                                                                                                                  |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Activate**             | Switch that enables or disables this document type for processing. See [Activate or deactivate a document type](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/activation.md).                    |
| **Extraction**           | Switch that selects the extraction mode, **Flex** or **Fix**. It does not switch extraction on or off.                                                                                                                                       |
| **Settings** (gear icon) | Opens [More Settings](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/more-settings.md) for this document type, for example Custom Validation Rules, Transformation Rules and Duplicate Detection. |

## Configuration Links

Under the Activate and Extraction switches, each card carries links to the configuration areas of that document type. A link appears only when the matching feature is switched on for the type, so a card can show fewer links than the list below.

| Link                     | What you configure                                                                                                | Guide                                                                                                                                           |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| **Layouts**              | Where the fields sit on the document image in the validation view.                                                | [Layout Manager](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager.md)                   |
| **Fields**               | The data fields DocBits extracts from this document type.                                                         | [Fields](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/fields.md)                                   |
| **Tables**               | The columns of the line-item table.                                                                               | [Table Columns](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/table-columns.md)                     |
| **Validation Rules**     | Your own rules for values that must be correct before a document can be exported.                                 | [Custom Validation Rules](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/custom-validation-rules.md) |
| **Transformation Rules** | Steps that correct values after extraction and before validation.                                                 | [Transformation Rules](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/transformation-rules.md)       |
| **Scripts**              | Scripts that run while a document is processed.                                                                   | [Scripts](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/script.md)                                  |
| **Model Training**       | The training data and the model for this document type.                                                           | [Model Training](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/model-training.md)                   |
| **E-Doc**                | Electronic document standards such as XRechnung, ZUGFeRD, EDI and FatturaPA.                                      | [E-Docs](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/edi.md)                                      |
| **Document Sub Types**   | Subcategories of this document type, for example one per supplier template.                                       | [Document Sub Types](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/document-sub-types.md)           |
| **Logs**                 | One entry per evaluation of a validation, transformation or layout selection rule, including the condition trace. | [Logs](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/custom-validation-rules.md#logs)               |

## Custom Validation Rules

Custom validation rules are rules **you** write for a single document type. They check values that the standard field checks cannot cover, for example a supplier tax ID that is only required for German invoices above 250 EUR, or a due date that must not be earlier than the invoice date. Each rule has a condition that decides whether it applies at all, a check that must be true, and a severity that decides whether a violation blocks the document (Error) or only shows a message (Warning).

Before you use them, know two things:

* The rules are switched on **per document type**, not for the whole organisation. Open the card's settings gear, open the **Custom Validation Rules** panel and turn the toggle on. The card then shows the **Validation Rules** link.
* While the toggle is on, the built-in amount checks (total amount = net + tax, and the line amount checks) are replaced by your rules. Recreate the checks you rely on as rules before switching it on.

The link on the card opens the rule list of the document type, where you create, activate, edit, test and delete rules.

{% hint style="info" %}
To copy a rule instead of rebuilding it, follow [Duplicate a Custom Validation Rule](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/duplicate-a-custom-validation-rule.md).
{% endhint %}

[Custom Validation Rules](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/custom-validation-rules.md) explains the whole workflow: enabling, the rule list, the three levels (header field, table line, whole table), the checks (Required, Formula, Pattern, Range, Compare fields, Allowed values, List of Values), the condition step [Rule Conditions (Applies when)](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/rule-conditions-applies-when.md), testing a rule against a document, the execution [Logs](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/custom-validation-rules.md#logs), ready-to-use recipes and troubleshooting.

## Configure fields and required information

{% embed url="<https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/document-types-fields-admin/v1/en.mp4>" %}
Document Types
{% endembed %}

[Watch with subtitles](https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/document-types-fields-admin/v1/en.html)

The recording shows the actual test interface. Configured values and technical labels retain their original meaning.

Configure the reference field in an isolated custom test type, save its label and required-review settings, and verify them after reloading.

The video uses an already-created, isolated custom test type. It changes that type's reference field; it does not change the existing invoice configuration.

1. Open the document type and select its fields.
2. Check the field group and stable technical field name. A readable display label is a separate setting; changing it does not create a new field ID.
3. Make the reference field required while keeping it visible and editable. Required information must be supplied; the setting does not invent a missing value or guarantee correct extraction.
4. Configure explicit field review separately from the required value. Read-only, hidden, OCR thresholds and Match Score thresholds have their own effects; they are not interchangeable switches.
5. Save the configuration, reopen it and verify the stored display label and flags.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-6370f28c1c45c0752279d86056e0f203387ed518%2Fadmin-reload-en-36dbf8128abf.png?alt=media" alt="Saved field settings in an isolated custom test type."><figcaption><p>Saved field settings in an isolated custom test type.</p></figcaption></figure>

The demonstrated result proves that the field configuration was saved and reloaded. It does not constitute model training, invoice approval, export or a downstream validation test. Before using a configuration in production, test representative documents and the intended ordinary-user workflow.

## Creating a Custom Document Type

1. Scroll down to the **Custom Document Types** section.
2. Click **+ New**.
3. Enter a clear name for the new document type.
4. Complete the offered setup steps for the intended extraction mode, fields, groups and any tables.

Model training and extraction configuration are separate from merely saving a required-field flag.

{% hint style="info" %}
See [Setup Document Type](https://docs.docbits.com/administration-and-setup/setup/document-types.md) for detailed setup instructions.
{% endhint %}


---

# 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/global-settings/document-types.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.
