Factur-X Profiles Explained — From MINIMUM to EXTENDED
Understanding the 6 Factur-X/ZUGFeRD profiles: what data each contains, when to use them, and how they map to EN 16931 compliance.
What are Factur-X profiles?
Factur-X (France) and ZUGFeRD (Germany) use a system of profiles that define how much structured data is embedded in the CII XML attached to the PDF invoice. Each profile adds more fields — from a minimal reference identifier up to a fully detailed EN 16931-compliant invoice.
The profile choice affects automation capabilities: higher profiles enable full automated processing, while lower profiles are suitable for archiving or basic reference purposes. Since ZUGFeRD 2.0, Factur-X and ZUGFeRD share the same profile hierarchy and are technically identical.
ValidateFin extracts the XML from your Factur-X/ZUGFeRD PDF and identifies the declared profile automatically.
The 6 profiles at a glance
Factur-X defines six profiles, from least to most detailed:
| Profile | Fields | EN 16931 | Use case |
|---|---|---|---|
| MINIMUM | ~10 fields | No | Reference only: invoice number, date, total, buyer/seller name, currency |
| BASIC WL | ~30 fields | No | Without lines: header + tax summary, no individual line items |
| BASIC | ~50 fields | No | Full header + line items with basic details (description, quantity, price) |
| EN 16931 (COMFORT) | ~100 fields | Yes | Full EN 16931 compliance: all mandatory and common optional fields |
| EXTENDED | ~150 fields | Superset | EN 16931 + additional fields for complex scenarios (delivery, logistics) |
| XRECHNUNG | ~100 fields | Yes (CIUS) | German B2G variant: EN 16931 with XRechnung-specific requirements |
Choosing the right profile
Which profile fits your needs:
Use MINIMUM if you only need a digital invoice archive with basic reference data. The PDF carries all visual detail; the XML is just for identification.
Use BASIC or BASIC WL if your recipients need structured data for semi-automated processing but don't require full EN 16931 compliance. This is common for SMEs sending invoices to larger companies.
Use EN 16931 (COMFORT) for full regulatory compliance with the European e-invoicing standard. This is required for French B2G via Chorus Pro and recommended for B2B under the 2026 reform.
EN 16931 compliance
The EN 16931 profile is the most important for regulatory compliance:
This profile includes all mandatory fields defined by the European standard: seller/buyer identification (VAT, SIRET, etc.), full tax breakdown by category, payment terms, line items with prices and quantities, and monetary totals.
For the French e-invoicing reform starting September 2026, invoices must be in at least the EN 16931 profile (or equivalent UBL/CII) to be accepted by Chorus Pro and ODP platforms.
The EXTENDED profile adds fields beyond EN 16931 (delivery details, logistics information) but remains backward-compatible. Recipients that only support EN 16931 can still process EXTENDED invoices by ignoring the extra fields.
Validate your Factur-X invoice
Upload your Factur-X or ZUGFeRD PDF to ValidateFin. We extract the embedded XML, identify the profile, and validate the data against the declared profile rules — all in your browser.
Open Factur-X ValidatorFrequently Asked Questions
Which profile does Chorus Pro require?
Chorus Pro accepts Factur-X invoices at the EN 16931 (COMFORT) profile or higher. MINIMUM and BASIC profiles are not sufficient for French B2G compliance.
Can I upgrade a MINIMUM invoice to EN 16931?
Not automatically — you need the missing data. A MINIMUM invoice only contains ~10 fields. EN 16931 requires ~100 fields including line items, tax breakdown, and payment details. You must add this data from your source system.
Are ZUGFeRD and Factur-X profiles identical?
Yes, since ZUGFeRD 2.0/Factur-X 1.0. The profiles (MINIMUM through EXTENDED) are technically the same specification, jointly maintained by FNFE-MPE and FeRD.
Does ValidateFin detect the profile automatically?
Yes. ValidateFin reads the GuidelineSpecifiedDocumentContextParameter in the CII XML to identify the declared profile, then validates accordingly.
Can a BASIC invoice pass EN 16931 validation?
No. BASIC profiles lack mandatory EN 16931 fields (like detailed tax breakdown per category). They will fail EN 16931 validation rules.
What is the difference between BASIC and BASIC WL?
BASIC includes individual line items (InvoiceLine). BASIC WL (Without Lines) only has header-level data and tax summary — no line item detail. Use BASIC WL when line items are only in the PDF.
Is EXTENDED backward-compatible with EN 16931?
Yes. EXTENDED is a superset of EN 16931. All EN 16931 mandatory fields are present. Recipients that only support EN 16931 can process EXTENDED invoices by ignoring extra fields.
Which profile do German companies use most?
For B2G (XRechnung), the XRECHNUNG profile is mandatory. For B2B, most German companies use EN 16931 (COMFORT) or EXTENDED, though BASIC is common among SMEs.
How do I specify the profile in my Factur-X XML?
The profile is declared in rsm:ExchangedDocumentContext/ram:GuidelineSpecifiedDocumentContextParameter/ram:ID. Each profile has a specific URN identifier.
Will there be new profiles in the future?
The current 6 profiles cover the full range from minimal to extended. New versions may add fields to existing profiles, but the profile hierarchy is expected to remain stable.