> 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/configure-subtypes.md).

# Configure subtypes

Use a document subtype when invoices of the same document type need different fields, a different validation layout, or their own processing scripts. First [create a subtype](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/creating-a-new-sub-type.md), then open **Settings → Document Types**, choose the document type, and open **Document Sub Types**. In the subtype row, open **Actions** (the three dots). The menu offers **Fields**, **Layout Builder**, and **Scripts**; it also contains [Copy, Edit, and Delete](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/using-actions.md).

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-5c9602bb3ef7850571bb2edd4b66c0784eaffa85%2Fsubtype-actions-menu-en.png?alt=media" alt="Actions menu for a document subtype showing Fields, Layout Builder, Scripts, Copy, Edit, and Delete"><figcaption><p>Choose the part of the subtype that you want to configure.</p></figcaption></figure>

## Fields

Select **Fields** to decide what information users see and enter for this subtype. You can create a field in a group, mark an existing field as required, read only, or hidden, and adjust recognition options. Select **Save Settings** after making changes. Use [Adding and Editing Fields](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/fields/adding-and-editing-fields.md) for the steps, [Configuring Field Properties](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/fields/configuring-field-properties-1.md) for the column options, and [Master Data Settings](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/fields/master-data-settings.md) when a field should use lookup data.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-0ee50c7a6d2fb296cc6d1d563494f397604fc8e7%2Fsubtype-fields-en.png?alt=media" alt="English field settings for a synthetic invoice subtype, including field groups, property columns, and Save Settings"><figcaption><p>Field settings in the documentation test organization. No customer data is shown.</p></figcaption></figure>

## Layout Builder

Select **Layout Builder** to arrange groups and fields on the document validation screen. The left side lists elements; the right side accepts a sample document for preview. Review the result and select **Save** when the layout is ready. The [Layout Builder guide](https://docs.docbits.com/administration-and-setup/setup/document-types/layout-builder.md) explains elements, the document preview, and saving a layout.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-acd08484c6d3da10758015b732d55404b192fcc6%2Fsubtype-layout-en.png?alt=media" alt="English Layout Builder for a synthetic invoice subtype, showing groups, preview upload, and Save"><figcaption><p>Subtype layout before adding a sample document.</p></figcaption></figure>

## Scripts

Select **Scripts** to view scripts for this subtype. In an empty list, select **Create Script** or **New** to start. The search and **All**, **Active**, and **Inactive** filters help find existing scripts. Follow [Creating and Editing Scripts](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/script/creating-and-editing-scripts.md) to create one, and [Script Activation and Management](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/script/script-activation-and-management.md) before enabling it for processing.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-5caf76b7af793804c5e86ce03bfef125dc5c874f%2Fsubtype-scripts-en.png?alt=media" alt="English empty script list for a synthetic invoice subtype, with Create Script and status filters"><figcaption><p>No scripts have been created in the documentation test subtype.</p></figcaption></figure>


---

# 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/configure-subtypes.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.
