Reference
ZUGFeRD EXTENDED profile
The EXTENDED profile provides additional data elements for sector-specific or advanced processes beyond the core EN 16931 model.
Profile overview
ZUGFeRD EXTENDED is the profile to study when the standard EN 16931 payload is not enough and your partner agreement, industry process, or internal workflow needs additional business context.
This article treats ZUGFeRD EXTENDED profile as a practical reference, not just a navigation page. It explains the term or workflow in context, shows why it matters for European e-invoicing, and connects the topic to invoice creation, validation, routing, archiving, and ERP implementation decisions.
Recommended for
Recommended for is where the general explanation of ZUGFeRD EXTENDED profile becomes operational. The section focuses on Organizations with advanced integration requirements and Sector-specific data needs (where supported by recipients), so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Organizations with advanced integration requirements
- Sector-specific data needs (where supported by recipients)
What it typically includes
What it typically includes is where the general explanation of ZUGFeRD EXTENDED profile becomes operational. The section focuses on Extra reference data and additional business information, More granular line-level and tax details (where applicable) and Extensions that some systems can process, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Extra reference data and additional business information
- More granular line-level and tax details (where applicable)
- Extensions that some systems can process
Limitations
Limitations is where the general explanation of ZUGFeRD EXTENDED profile becomes operational. The section focuses on Not every recipient supports EXTENDED fields and May reduce interoperability if recipients expect strict EN 16931, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Not every recipient supports EXTENDED fields
- May reduce interoperability if recipients expect strict EN 16931
Typical use cases
Typical use cases is where the general explanation of ZUGFeRD EXTENDED profile becomes operational. The section focuses on Sector projects with agreed extensions and Complex enterprise invoice integrations where both parties align on the data set, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Sector projects with agreed extensions
- Complex enterprise invoice integrations where both parties align on the data set
How to choose this profile
How to choose this profile is where the general explanation of ZUGFeRD EXTENDED profile becomes operational. The section focuses on Choose EXTENDED only when a recipient or sector specifically asks for fields beyond EN 16931, Use EN 16931 by default if you want stronger interoperability and fewer partner-specific… and Keep EXTENDED out of generic invoice exchange unless the receiving process has been agreed in…, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Choose EXTENDED only when a recipient or sector specifically asks for fields beyond EN 16931.
- Use EN 16931 by default if you want stronger interoperability and fewer partner-specific variations.
- Keep EXTENDED out of generic invoice exchange unless the receiving process has been agreed in advance.
Frequently asked questions
Frequently asked questions answers the practical questions that usually appear after reading the main explanation of ZUGFeRD EXTENDED profile. The answers focus on When should I choose EXTENDED instead of EN 16931, Is EXTENDED a better default for every invoice and Can EXTENDED cause validation or exchange issues and are written to clarify implementation choices quickly.
When should I choose EXTENDED instead of EN 16931?
Choose EXTENDED when a specific partner, sector, or internal process explicitly needs extra business fields that are not part of the core EN 16931 model.
Is EXTENDED a better default for every invoice?
No. It increases specificity, but that can reduce interoperability. For most invoice exchange scenarios, EN 16931 is the safer default.
Can EXTENDED cause validation or exchange issues?
Yes, if the receiving system does not support the extra fields or expects a stricter EN 16931 payload. Always confirm the target process first.
Create a ZUGFeRD file
Convert a PDF invoice to ZUGFeRD and choose the best matching profile. Create a ZUGFeRD file connects ZUGFeRD EXTENDED profile with the next useful reference pages and tools. These links are included to support a complete workflow, from understanding Convert to ZUGFeRD to validating or converting the invoice file.