Skip to main content

ZUGFeRD BASIC profile

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

Profile overview

ZUGFeRD BASIC is the next step after BASIC WL when you need machine-readable line items for goods or services. BASIC invoices are EN 16931-compliant, but the profile leaves out a number of optional business terms.

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

With line itemsAdds: Line items

urn:cen.eu:en16931:2017#compliant#urn:factur-x.eu:1p0:basic

What it contains
Adds structured line items with quantities, unit codes and prices. EN 16931-compliant, but leaves out a number of optional business terms.
Typical use
Simple goods or service invoices that are matched line by line.
Germany
E-invoiceCounts as an e-invoice under § 14 UStG.
France
CheckNot named among the reform profiles (EN 16931, EXTENDED-CTC-FR). Confirm with your platform.
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

  • Structured line items (quantity, unit codes, prices)
  • Totals and taxes
  • Basic references (order/contract) where applicable

Limitations

  • Omits optional EN 16931 business terms that some recipients expect
  • Some advanced tax and reference scenarios may require higher profiles

Typical use cases

  • Automated AP posting with line-level matching
  • Simple goods invoicing with quantities and unit codes

Specification references

  • GuidelineID: urn:cen.eu:en16931:2017#compliant#urn:factur-x.eu:1p0:basic
  • PDF/A-3 conformance: PDF/A-3 (ISO 19005-3:2012)
  • Embedded XML filename: factur-x.xml
  • AFRelationship attribute: Alternative (DE) · Data / Source / Alternative (FR)
  • 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 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 recipient needs optional business terms that BASIC does not carry.

Implementation fit

Use the BASIC 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

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. BASIC is EN 16931-compliant but omits optional business terms. If the recipient needs those terms, choose EN 16931.

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

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