> 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/supported-electronic-documents/facturx-1-09-zugferd-2-5.md).

# FACTURX 1.09 - ZUGFERD 2.5

FACTURX 1.09 - ZUGFERD 2.5 electronic document support in DocBits

{% hint style="info" %}
Check the country guide for version limits, effective configuration and the country explainer. [France](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/france.md). The XML marker 1p0 and Factur-X XMP Version 1.0 do not identify a publication release. Keep the generic label when the release is unknown.
{% endhint %}

| Property             | Value                       |
| -------------------- | --------------------------- |
| **Country / Region** | France / Germany            |
| **Document Types**   | Invoice, Credit Note        |
| **Format**           | CII (PDF/A-3 embedded)      |
| **Standard**         | Factur-X 1.09 / ZUGFeRD 2.5 |
| **Based On**         | EN 16931                    |

Factur-X 1.09 is the French publication equivalent to ZUGFeRD 2.5 (FeRD/FNFE-MPE common publication, June 2026). Its CII XML uses the UN/CEFACT D22B base, which is backwards-compatible with D16B, so the full Factur-X 1.08 / ZUGFeRD 2.4 extraction and transformation contract continues to apply. The EXTENDED profile adds new fields for payment means and BIC, a third-party payee (factor), and the allowance/charge tax-exemption reason.

All five profiles are supported: MINIMUM, BASIC WL, BASIC, EN 16931 (COMFORT) and EXTENDED.

## Support Status

| Component        | Status      |
| ---------------- | ----------- |
| Preview          | ✅ Supported |
| Field Extraction | ✅ Supported |
| Transformation   | ✅ Supported |

## Related

* [ZUGFeRD 2.5](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/zugferd-2-5.md)
* [ZUGFeRD Configuration](/administration-and-setup/settings/global-settings/document-types/edi/zugferd/configuration.md)
* [ZUGFeRD Field Mapping](/administration-and-setup/settings/global-settings/document-types/edi/zugferd.md)
* [Supported Electronic Documents](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents.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/settings/global-settings/document-types/edi/supported-electronic-documents/facturx-1-09-zugferd-2-5.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.