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

# Document Sub Types

Document sub types are specialized versions of a document type. Under the main document type **Invoice**, for example, there might be sub types such as *Standard Invoice*, *Pro-forma Invoice* and *Credit Invoice*, each with slightly different data requirements or processing rules.

## Why sub types are useful

* **Specific processing requirements** — different variations of the same document type often need different fields, approval workflows or validation rules.
* **Organizational customization** — sub types let you tailor document processing to your own processes instead of relying on a generic setup.
* **Clear structuring** — users can move between the variations of a document type and only see the information that belongs to the one they are working on.
* **Consistency and accuracy** — standardised sub types capture the same information in the same structure for every document of that variation.
* **Efficient processing** — pre-built templates and workflows for a sub type reduce manual effort and errors.

## Open the sub types of a document type

1. Go to **Settings → Document Types**.
2. On the card of the document type, select **Document Sub Types**.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-23ceaf1f912c4dc284b316d8bd263fdb7ef70d70%2Fdocument-types-list-en.png?alt=media" alt="Document Types settings page with the Invoice card and its action row containing Layouts, Fields, Tables, Validation Rules, Transformation Rules, Scripts, Model Training, E-Doc, Document Sub Types and Logs"><figcaption><p>**Document Sub Types** is one of the actions on each document type card.</p></figcaption></figure>

The page lists the sub types of that document type with their **Name** and the **Actions** available for each one.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-b8076bc4a86d439fb340a6cd32910e757a8b19ce%2Fdocument-sub-types-list-en.png?alt=media" alt="Document Sub Types page with the New button, the columns Name and Actions and the empty state No Record Found"><figcaption><p>The sub types of the selected document type.</p></figcaption></figure>

## Actions on a sub type

Each row offers the following actions:

* **Fields** — configure which data fields belong to the sub type and how they are managed.
* **Layout Builder** — open the layout of this sub type and change how the fields are arranged.
* **Scripts** — attach or edit the scripts that run when a document of this sub type is processed.
* **Copy** — duplicate the sub type as the starting point for a new one.
* **Edit** — change the name or title of the sub type.
* **Delete** — remove the sub type when it is no longer needed.

## Add a sub type

1. Select **New** above the table.
2. Enter a **Name**. It may contain letters and underscores only.
3. Enter a **Title** for the sub type.
4. Select **Save**.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-bb5579d19b9b86b513ac22d0d20f3ec0675d4b95%2Fdocument-sub-types-create-dialog-en.png?alt=media" alt="Create New Sub Document Type dialog with the fields Name and Title and the buttons Cancel and Save"><figcaption><p>A new sub type is created in the **Create New Sub Document Type** dialog.</p></figcaption></figure>

After a sub type exists, it is available wherever a document of that type is processed, for example in the fields and layouts of the document type.


---

# 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/document-sub-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.
