Reference
ZUGFeRD BASIC profile
The BASIC profile provides structured line items and totals for simple automation scenarios.
Profile overview
ZUGFeRD BASIC is the practical next step after BASIC WL when you need machine-readable line items for goods or services, but do not yet need the full EN 16931 compliance scope.
This article treats ZUGFeRD BASIC 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 BASIC profile becomes operational. The section focuses on B2B invoices needing line-level automation and Systems that reconcile quantities and prices automatically, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- B2B invoices needing line-level automation
- Systems that reconcile quantities and prices automatically
What it typically includes
What it typically includes is where the general explanation of ZUGFeRD BASIC profile becomes operational. The section focuses on Structured line items (quantity, unit codes, prices), Totals and taxes and Basic references (order/contract) where applicable, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Structured line items (quantity, unit codes, prices)
- Totals and taxes
- Basic references (order/contract) where applicable
Limitations
Limitations is where the general explanation of ZUGFeRD BASIC profile becomes operational. The section focuses on May not satisfy EN 16931 mandates for specific recipients and Some advanced tax and reference scenarios may require higher profiles, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- May not satisfy EN 16931 mandates for specific recipients
- Some advanced tax and reference scenarios may require higher profiles
Typical use cases
Typical use cases is where the general explanation of ZUGFeRD BASIC profile becomes operational. The section focuses on Automated AP posting with line-level matching and Simple goods invoicing with quantities and unit codes, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Automated AP posting with line-level matching
- Simple goods invoicing with quantities and unit codes
How to choose this profile
How to choose this profile is where the general explanation of ZUGFeRD BASIC profile becomes operational. The section focuses on Choose BASIC if your process depends on quantities, prices, and item-level matching, Stay on BASIC WL only when line details are intentionally kept outside the invoice payload and Use EN 16931 if the receiving side needs the compliance profile instead of a lighter commercial…, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Choose BASIC if your process depends on quantities, prices, and item-level matching.
- Stay on BASIC WL only when line details are intentionally kept outside the invoice payload.
- Use EN 16931 if the receiving side needs the compliance profile instead of a lighter commercial profile.
Frequently asked questions
Frequently asked questions answers the practical questions that usually appear after reading the main explanation of ZUGFeRD BASIC profile. The answers focus on What makes BASIC different from BASIC WL, Is BASIC enough for invoice automation and Can BASIC be used for service invoices as well as goods and are written to clarify implementation choices quickly.
What makes BASIC different from BASIC WL?
BASIC includes structured line items, which makes it better for quantity matching, item-level validation, and simple automation based on rows.
Is BASIC enough for invoice automation?
Yes for many commercial workflows. If your workflow needs detailed tax rules, public-sector requirements, or strict semantic compliance, EN 16931 is the safer choice.
Can BASIC be used for service invoices as well as goods?
Yes. It works for both, as long as the sender can express the relevant line details, totals, and references in structured form.
Create a ZUGFeRD file
Convert a PDF invoice to ZUGFeRD and choose the best matching profile. Create a ZUGFeRD file connects ZUGFeRD BASIC 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.