Skip to main content

ZUGFeRD 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.

Interactive profile ladder

Each step adds data to the embedded XML. Select a profile to see what it contains and whether it counts as an e-invoice.

Germany: e-invoice from here

German reference profile

Without linesAdds: VAT, payment

urn:factur-x.eu:1p0:basicwl

What it contains
Everything in MINIMUM plus the VAT breakdown, addresses and payment details. Still no line items.
Typical use
Bookkeeping imports that do not process individual lines.
Germany
Processing aidNot an e-invoice. Treated like a plain PDF (“other invoice”).
France
Not a reform profileToo little structured line data to serve as a complete invoice profile.
ZUGFeRD / Factur-X profiles from least to most data: MINIMUM (header and totals only), BASIC WL (adds the VAT breakdown, addresses and payment details, still no line items), BASIC (adds line items; an EN 16931-compliant subset), EN 16931, also called COMFORT (the full EN 16931 data set), and EXTENDED (adds data beyond EN 16931). ZUGFeRD also defines XRECHNUNG: EN 16931 data under the German XRechnung rules, embedded as xrechnung.xml. In Germany, BASIC and above count as e-invoices; MINIMUM and BASIC WL do not. The French reform profiles are EN 16931 and EXTENDED-CTC-FR. Sources: FeRD / FNFE-MPE ZUGFeRD and Factur-X specifications, BMF e-invoice FAQ, French e-invoicing reform. Status: October 2026. Not legal advice.

What it typically includes

  • Invoice header and parties
  • Totals and tax information
  • Payment information (basic)

Limitations

  • No structured line item data
  • Not a German structured e-invoice; it does not replace the EN 16931 profile

Typical use cases

  • Internal summary records where details stay in attachments
  • Controlled bookkeeping imports without line processing

Specification references

  • 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

  • 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. In Germany BASIC WL does not meet the e-invoice requirement, and many compliance-oriented workflows expect line items or EN 16931 data.

Create a ZUGFeRD file

Our converter creates hybrid ZUGFeRD/Factur-X invoices in the EN 16931 or EXTENDED profile from your PDF.