Reference
Markdown exportZUGFeRD BASIC WL profile
BASIC WL (“without lines”) focuses on header-level totals and parties, without structured line item details.
Profile overview
ZUGFeRD BASIC WL is the profile to read when you need a practical invoice PDF with structured header data, totals, and payment context, but no individual line items.
Recommended for
Use these points as the practical checks for this section.
- Invoices where line item automation is not required
- Legacy workflows that still need some structured data
What it typically includes
Use these points as the practical checks for this section.
- Invoice header and parties
- Totals and tax information
- Payment information (basic)
Limitations
Use these points as the practical checks for this section.
- No structured line item data
- Not a substitute for EN 16931 profile requirements
Typical use cases
Use these points as the practical checks for this section.
- Summary invoices where details stay in attachments
- Simple service invoices billed as a total
Specification references
Use these points as the practical checks for this section.
- GuidelineID: urn:factur-x.eu:1p0:basicwl
- PDF/A-3 conformance: PDF/A-3 (ISO 19005-3:2012)
- Embedded XML filename: factur-x.xml
- AFRelationship attribute: Data
- XMP metadata: fx:DocumentType, fx:DocumentFileName, fx:Version, fx:ConformanceLevel
- FNFE-MPE reference: https://fnfe-mpe.org/factur-x/
How to choose this profile
Use these points as the practical checks for this section.
- Choose BASIC WL if your downstream system only needs invoice-level totals and party data.
- Use BASIC when line items, quantities, and prices must be machine-readable.
- Upgrade to EN 16931 when the recipient expects compliance-oriented structured data.
Implementation fit
Use the BASIC WL profile only after you confirm how much structured detail the recipient, archive, and validation process expects. If line-level automation, tax review, or downstream matching is important, choose the richer profile before you start converting production invoices.
Frequently asked questions
Why does BASIC WL have no line items?
It is designed for workflows where the invoice summary is enough and detailed rows stay in the source system, attachment, or separate document.
Is BASIC WL a good choice for simple AP automation?
Yes, when your automation only needs header data, totals, and payment information. If you need matching by quantity or item, BASIC is the better fit.
Can I use BASIC WL for compliance-heavy customers?
Only if the customer accepts that profile. Many compliance-oriented workflows expect line-level detail or EN 16931-conform data instead.
Create a ZUGFeRD file
Convert a PDF invoice to ZUGFeRD and choose the best matching profile.