# 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.

## Recommended for

- Organizations with advanced integration requirements
- Sector-specific data needs (where supported by recipients)

## What it typically includes

- Extra reference data and additional business information
- More granular line-level and tax details (where applicable)
- Extensions that some systems can process

## Limitations

- Not every recipient supports EXTENDED fields
- May reduce interoperability if recipients expect strict EN 16931

## Typical use cases

- Sector projects with agreed extensions
- Complex enterprise invoice integrations where both parties align on the data set

## Specification references

- GuidelineID: urn:cen.eu:en16931:2017#conformant#urn:factur-x.eu:1p0:extended
- PDF/A-3 conformance: PDF/A-3 (ISO 19005-3:2012)
- Embedded XML filename: factur-x.xml
- AFRelationship attribute: Data
- XMP metadata: fx:DocumentType, fx:DocumentFileName, fx:Version, fx:ConformanceLevel
- FNFE-MPE reference: https://fnfe-mpe.org/factur-x/

## How to choose this profile

- 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.

## Implementation fit

Use the EXTENDED profile only after you confirm how much structured detail the recipient, archive, and validation process expects. If line-level automation, tax review, or downstream matching is important, choose the richer profile before you start converting production invoices.

## Frequently asked questions

### 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.

- [Convert to ZUGFeRD](/pdf-to-zugferd)