Skip to main content

Reference

Markdown export

ZUGFeRD Profiles

Understand what each ZUGFeRD/Factur-X profile contains and which compliance requirements it best fits.

When to use the profile overview

Use the profile overview when you already know you need ZUGFeRD or Factur-X, but still have to choose how much structured detail the recipient process requires. The main decision is not “PDF or XML”; it is which profile keeps the workflow interoperable.

Choose a profile

Start from recipient requirements: do they need full line detail, EN 16931 semantics only, or a lightweight PDF/A payload? When in doubt, prefer EN 16931 or EXTENDED for audited B2B flows.

Minimal structured data

MINIMUM or BASIC WL when only header-level totals or lightweight metadata is required.

Standard B2B invoices

BASIC or EN 16931 when line items, taxes, and parties must validate end-to-end.

Sector-specific or rich data

EXTENDED when you must carry extra identifiers, allowances, or process fields beyond core EN 16931.

Quick actions

Convert invoiceValidate XMLDeveloper API

Open profile

MINIMUM

Updated

The MINIMUM profile is a lightweight ZUGFeRD profile with a reduced set of structured invoice data embedded in a PDF.

BASIC WL

Updated

BASIC WL (“without lines”) focuses on header-level totals and parties, without structured line item details.

BASIC

Updated

The BASIC profile provides structured line items and totals for simple automation scenarios.

EN 16931

Updated

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

EXTENDED

Updated

The EXTENDED profile provides additional data elements for sector-specific or advanced processes beyond the core EN 16931 model.

Related articles

Convert PDF to ZUGFeRD: when a hybrid invoice workflow fits

Learn when PDF to ZUGFeRD is the right bridge for B2B workflows, what a valid hybrid invoice must contain, and how to review the XML before sending.