# ZUGFeRD EN 16931 profile

The EN 16931 profile is designed to be compatible with the European semantic model for e-invoices and is commonly required for compliance.

## Profile overview

ZUGFeRD EN 16931 is the profile most teams compare when they need an invoice format that is structured enough for validation, interoperable enough for trading partners, and aligned with European e-invoicing expectations.

## Recommended for

- EU compliance-oriented B2B invoices
- Customers requiring EN 16931-conform structured data

## What it typically includes

- EN 16931-aligned structured invoice data
- Line items, taxes, allowances/charges, payment data
- Validation-friendly code lists and identifiers

## Limitations

- National CIUS (e.g., XRechnung) may add extra constraints
- Some platforms require additional reporting fields beyond EN 16931

## Typical use cases

- Large customer onboarding for structured invoicing
- Preparing for EU mandate timelines and validations

## Specification references

- GuidelineID: urn:cen.eu:en16931:2017
- 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 EN 16931 when compliance and interoperability are primary requirements.
- Prefer BASIC if you only need lightweight commercial automation and the recipient accepts it.
- Move to EXTENDED only when a specific partner or sector needs extra fields beyond the core profile.

## Implementation fit

Use the EN 16931 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

### Is EN 16931 the same as a national e-invoice standard?
No. EN 16931 is the European semantic model. National specifications such as XRechnung can add extra rules on top of it.

### Does EN 16931 include line items and taxes?
Yes. It covers structured line data, tax information, allowances and charges, and other invoice details needed for validation and exchange.

### When is EN 16931 the safest default choice?
It is the safest default when you are unsure what the recipient expects, or when you need a broadly interoperable profile for EU-oriented invoice exchange.

## Create a ZUGFeRD file

Convert a PDF invoice to ZUGFeRD and choose the best matching profile.

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