Reference
ZUGFeRD MINIMUM profile
The MINIMUM profile is a lightweight ZUGFeRD profile with a reduced set of structured invoice data embedded in a PDF.
Profile overview
ZUGFeRD MINIMUM is the smallest practical profile for teams that want a PDF invoice with just enough structured data for basic downstream processing, archiving, and simple invoice exchange.
This article treats ZUGFeRD MINIMUM 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 MINIMUM profile becomes operational. The section focuses on Simple B2B invoices where only basic automation is needed and Archive-friendly workflows that prioritize the PDF, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Simple B2B invoices where only basic automation is needed
- Archive-friendly workflows that prioritize the PDF
What it typically includes
What it typically includes is where the general explanation of ZUGFeRD MINIMUM profile becomes operational. The section focuses on Core header data (invoice number, dates), Basic parties (seller/buyer) and Totals and tax summary (limited), so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Core header data (invoice number, dates)
- Basic parties (seller/buyer)
- Totals and tax summary (limited)
Limitations
Limitations is where the general explanation of ZUGFeRD MINIMUM profile becomes operational. The section focuses on Not ideal for strict EN 16931 compliance requirements and May be insufficient for public sector or platform mandates, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Not ideal for strict EN 16931 compliance requirements
- May be insufficient for public sector or platform mandates
Typical use cases
Typical use cases is where the general explanation of ZUGFeRD MINIMUM profile becomes operational. The section focuses on Small supplier invoices with PDF-first processes and Early adoption before moving to EN16931 profile, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Small supplier invoices with PDF-first processes
- Early adoption before moving to EN16931 profile
How to choose this profile
How to choose this profile is where the general explanation of ZUGFeRD MINIMUM profile becomes operational. The section focuses on Choose MINIMUM when the PDF is the main deliverable and only a minimal structured dataset is…, Move to BASIC WL if your process needs totals and parties but not line-item detail and Use BASIC or higher when automation, validation, or compliance checks depend on structured line…, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Choose MINIMUM when the PDF is the main deliverable and only a minimal structured dataset is needed.
- Move to BASIC WL if your process needs totals and parties but not line-item detail.
- Use BASIC or higher when automation, validation, or compliance checks depend on structured line data.
Frequently asked questions
Frequently asked questions answers the practical questions that usually appear after reading the main explanation of ZUGFeRD MINIMUM profile. The answers focus on Does ZUGFeRD MINIMUM support structured invoice exchange, Is MINIMUM enough for EN 16931 compliance and When should I avoid MINIMUM and are written to clarify implementation choices quickly.
Does ZUGFeRD MINIMUM support structured invoice exchange?
Yes, but only in a reduced form. It is suitable for basic exchange and archiving, not for demanding automation or strict compliance cases.
Is MINIMUM enough for EN 16931 compliance?
No. If the recipient or workflow requires EN 16931-conform data, choose EN 16931 or a profile that explicitly covers that requirement.
When should I avoid MINIMUM?
Avoid it when you need line items, tax detail, validation-heavy workflows, or broad interoperability with larger customers and platforms.
Create a ZUGFeRD file
Convert a PDF invoice to ZUGFeRD and choose the best matching profile. Create a ZUGFeRD file connects ZUGFeRD MINIMUM 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.