Reference
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.
This article treats ZUGFeRD EN 16931 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 EN 16931 profile becomes operational. The section focuses on EU compliance-oriented B2B invoices and Customers requiring EN 16931-conform structured data, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- EU compliance-oriented B2B invoices
- Customers requiring EN 16931-conform structured data
What it typically includes
What it typically includes is where the general explanation of ZUGFeRD EN 16931 profile becomes operational. The section focuses on EN 16931-aligned structured invoice data, Line items, taxes, allowances/charges, payment data and Validation-friendly code lists and identifiers, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- EN 16931-aligned structured invoice data
- Line items, taxes, allowances/charges, payment data
- Validation-friendly code lists and identifiers
Limitations
Limitations is where the general explanation of ZUGFeRD EN 16931 profile becomes operational. The section focuses on National CIUS (e.g., XRechnung) may add extra constraints and Some platforms require additional reporting fields beyond 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.
- National CIUS (e.g., XRechnung) may add extra constraints
- Some platforms require additional reporting fields beyond EN 16931
Typical use cases
Typical use cases is where the general explanation of ZUGFeRD EN 16931 profile becomes operational. The section focuses on Large customer onboarding for structured invoicing and Preparing for EU mandate timelines and validations, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Large customer onboarding for structured invoicing
- Preparing for EU mandate timelines and validations
How to choose this profile
How to choose this profile is where the general explanation of ZUGFeRD EN 16931 profile becomes operational. The section focuses on Choose EN 16931 when compliance and interoperability are primary requirements, Prefer BASIC if you only need lightweight commercial automation and the recipient accepts it and Move to EXTENDED only when a specific partner or sector needs extra fields beyond the core…, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- 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.
Frequently asked questions
Frequently asked questions answers the practical questions that usually appear after reading the main explanation of ZUGFeRD EN 16931 profile. The answers focus on Is EN 16931 the same as a national e-invoice standard, Does EN 16931 include line items and taxes and When is EN 16931 the safest default choice and are written to clarify implementation choices quickly.
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. Create a ZUGFeRD file connects ZUGFeRD EN 16931 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.