> 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/edi/zugferd/configuration.md).

# ZUGFeRD Configuration

{% embed url="<https://youtu.be/AxrHNEmmXtg>" %}
DocBits E-Invoice Tutorial: Process XRechnung / ZUGFeRD (Factur-X), Validate Data & Automate Workflows
{% endembed %}

## **Supported Versions of ZUGFeRD**

DocBits supports all major versions of ZUGFeRD, including:

* **1.0**
* **2.0**
* **2.1** (compliant with FACTUR-X 1.0.05)
* **2.2**
* **2.3** (compliant with FACTUR-X 1.07.2)
* **2.3.2**

#### Standard Activation and Modification

The ZUGFeRD standard is always active by default, but you can make modifications to it if needed.

### **Steps to Modify ZUGFeRD Settings:**

1. Navigate to **Settings → Global Settings → Document Types → Invoice**.
2. Click on **E-Doc**.\\
3. A list of all available e-docs will appear.
4. Locate the **ZUGFeRD** version you want to modify.\\

## **Transformation and XML Path Configuration:**

In the **transformation settings**, you can define the path to locate specific information within the XML file and save it in a new structure, making it easier to access the data.\ <mark style="color:red;">**Note**</mark>: If you use this functionality, you must use the newly created XML paths, not the original XML paths, in the **Preview** and **Extraction Path**.

### **Steps to Modify Transformation File:**

1. Open the **Transformation**.
2. Create a new draft by clicking the **pencil icon**.
3. Select the newly created draft.
4. Either create a new field or modify an existing one.
5. Set the desired path for data extraction.
6. Click **Save**.

### Important Notes:

* The **preview file** is used only for **FACTUR-X** and not for **ZUGFeRD**. ZUGFeRD will use the original **PDF**.

## Preview PDF Configuration

The **Preview PDF Configuration** is used to generate a user-readable version of the document. You can customize it with HTML to match your needs.

### **Steps to Modify Preview File:**

1. Open the **Preview**.
2. Create a new draft by clicking the **pencil icon**.
3. Select the newly created draft.
4. Either create a new field or modify an existing one.
5. Set the desired path for data extraction.
6. Click **Save**.

## Extraction Paths Configuration

The **Extraction Paths Configuration** is used to extract data and populate fields in the **validation screen**, such as the invoice table or fields configured in the invoice layout.

### **Steps to Modify** **Extraction Paths**:

1. Open the **Extraction Paths**.
2. Create a new draft by clicking the **pencil icon**.
3. Select the newly created draft.
4. Create a new field or modify an existing one.
5. The left side represents the **DocBits field ID**, which can be found in the **Settings → Global Settings → Document Types → Invoice → Fields**.\\
6. The right side represents the **path to the field** created in the Transformation.
7. Click **Save**.

By following these steps, you can ensure accurate data extraction and validation for ZUGFeRD invoices.

## Effective rules and activation

Organization-specific rules take precedence over defaults for the detected eDoc format. Check the active TRANSFORMATION and check which node supplies invoice\_type in the transformed XML; the path depends on the format. Save stores a draft; use the checkmark to activate it after testing. A rendered Preview does not prove the stored document type. See the [classification troubleshooting guide](/administration-and-setup/settings/global-settings/document-types/edi/credit-note-recognized-as-invoice.md) for codes 381/261, later scripts and reprocessing safeguards.


---

# 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/edi/zugferd/configuration.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.