ZUGFeRD BASIC WL: Six Myths About the Profile Without Line Items
ZUGFeRD BASIC WL is not an e-invoice in Germany. Six common myths checked against the law, the BMF and FeRD, plus how to spot the profile in a file.
Key takeaways
- ZUGFeRD BASIC WL carries no invoice lines; FeRD calls it a booking aid, not a complete invoice under the German VAT Act.
- The BMF letter of 15 October 2024 (paras. 25 and 30) excludes the MINIMUM and BASIC WL profiles from valid e-invoice formats.
- For VAT purposes a BASIC WL file is an 'other invoice', allowed until the end of 2026, and in 2027 only for issuers with up to EUR 800,000 prior-year turnover.
- You can spot the profile by the BT-24 value urn:factur-x.eu:1p0:basicwl and by XML that has no IncludedSupplyChainTradeLineItem element.
On this page
ZUGFeRD BASIC WL is not an e-invoice under German law. The profile carries no invoice lines, and FeRD treats it only as a booking aid. The German Federal Ministry of Finance (BMF) excludes MINIMUM and BASIC WL explicitly in its letter of 15 October 2024 (paras. 25 and 30), so a BASIC WL file is merely an "other invoice" (sonstige Rechnung).
This matters to finance teams that receive ZUGFeRD or Factur-X files from German suppliers, and to companies whose invoicing software exports a hybrid PDF without saying which profile it writes. Below, six common assumptions are checked against the German VAT Act, the BMF and the Forum elektronische Rechnung Deutschland (FeRD), followed by a way to find the profile in any file.
The myths at a glance
| Myth | Fact | Source |
|---|---|---|
| BASIC WL is a lean but valid e-invoice | Not an e-invoice; it counts as an "other invoice" | BMF letter 15 Oct 2024, paras. 25, 30; FeRD FAQ |
| BASIC and BASIC WL are almost the same | BASIC has lines and is an e-invoice; BASIC WL is not | FeRD FAQ |
| The PDF shows every line, so that is enough | In an e-invoice, the XML part prevails | BMF letter 15 Oct 2024, para. 31 |
| With the buyer's consent, BASIC WL becomes an agreed format | An agreed format must allow full extraction of all mandatory data | § 14(1) sentence 6 no. 2 UStG |
| No validator error means everything is fine | The schema allows invoices without lines; the standard does not | CII XSD, rule BR-16 |
| Buyers must reject BASIC WL right away | Allowed as an "other invoice" until the end of 2026 | § 27(38) UStG |
Myth 1: "BASIC WL is a lean but valid e-invoice"
Under Section 14 of the German VAT Act (§ 14 UStG (opens in a new tab)), an e-invoice is an invoice in a structured electronic format that follows the European standard EN 16931 or that the two parties have agreed on. Whether a ZUGFeRD file meets this test depends on its profile, not on its file name or version number.
The BMF letter of 15 October 2024 is clear. Para. 25 lists ZUGFeRD from version 2.0.1 as an example of a valid format, "ausgenommen die Profile MINIMUM und BASIC-WL" (excluding the MINIMUM and BASIC WL profiles). Para. 30 repeats this for hybrid formats: ZUGFeRD is based on the EN 16931 series only from version 2.0.1 and only without these two profiles. In its ZUGFeRD FAQ (opens in a new tab), FeRD states for BASIC WL that it is not recognised in Germany as a complete invoice under the VAT Act.
Para. 7 of the same letter defines every invoice in an electronic format that does not meet § 14(1) sentence 6 UStG as an "other invoice". For VAT purposes, a BASIC WL file is therefore in the same category as a plain PDF.
Myth 2: "BASIC and BASIC WL are almost the same"
The names are similar; the legal status is not. FeRD describes BASIC as a subset of EN 16931-1 that can be used for simple invoices that meet the VAT Act. BASIC WL, by contrast, contains no invoice lines and holds only the document-level data needed to post the invoice.
MINIMUM is even smaller. According to FeRD it contains the key buyer and seller data, the invoice total and the total VAT, but no VAT breakdown. At line level it can only carry the buyer's reference. MINIMUM is a booking aid as well.
The difference is visible in the profile identifier in BT-24 (specification identifier) of the XML:
| Profile | Identifier in BT-24 | Invoice lines | E-invoice per BMF |
|---|---|---|---|
| MINIMUM | urn:factur-x.eu:1p0:minimum | no | no |
| BASIC WL | urn:factur-x.eu:1p0:basicwl | no | no |
| BASIC | urn:cen.eu:en16931:2017#compliant#urn:factur-x.eu:1p0:basic | yes | yes |
| EN 16931 | urn:cen.eu:en16931:2017 | yes | yes |
| EXTENDED | urn:cen.eu:en16931:2017#conformant#urn:factur-x.eu:1p0:extended | yes | yes |
Every profile that counts as an e-invoice starts with urn:cen.eu:en16931:2017. MINIMUM and BASIC WL lack this reference to the standard. The identifiers match those in the open-source reference library Mustang. Since ZUGFeRD 2.x and Factur-X are identical in content according to FeRD, the same values appear in French Factur-X files. The full profile and version overview is in our guide to ZUGFeRD profiles.
Myth 3: "The PDF shows every line, so that is enough"
In a BASIC WL invoice, a person reading the PDF often sees a complete invoice with lines, quantities and unit prices. A machine reading the XML sees only totals. For an e-invoice, the machine-readable part is what counts.
Para. 31 of the BMF letter of 15 October 2024 says that this reverses the earlier rule: in a hybrid format the XML data is the leading part, and if the structured data and the image differ, the structured data prevails. Among the mandatory invoice details, § 14(4) sentence 1 no. 5 UStG requires the quantity and type of goods supplied, or the scope and type of the service. A data set without lines cannot deliver this detail in structured form.
The PDF still has a role. While "other invoices" are allowed, the file can carry all mandatory details in its visual part and work as such an invoice. It does not become an e-invoice that way.
Myth 4: "With the buyer's consent, BASIC WL becomes an agreed format"
§ 14(1) sentence 6 no. 2 UStG allows formats agreed between issuer and recipient, in addition to EN 16931 formats. The condition is that the format allows the "correct and complete extraction" of the details required by the Act into a format that meets the standard.
In our assessment, a profile without line data cannot meet this condition, because type and quantity of the supply are missing from the data set (see myth 3). An agreement does not add data that the format does not carry. Consent matters for something else: until the end of 2026, every "other invoice" sent electronically needs the recipient's consent. According to para. 63 of the BMF letter, this consent needs no specific form and can be given in general terms and conditions or implied by conduct.
Myth 5: "No validator error means everything is fine"
A BASIC WL file can be technically flawless and still not be an e-invoice. Two levels of checking explain why:
- Schema (XSD). In the CII D16B schema used by ZUGFeRD 2.x, the element
ram:IncludedSupplyChainTradeLineItemis defined withminOccurs="0". An invoice without lines is schema-valid. - Business rules (Schematron). Only rule BR-16 of EN 16931 requires: "An Invoice shall have at least one Invoice line (BG-25)." This rule runs only when a tool validates the file as an EN 16931 invoice.
The KoSIT validator, maintained by the German Coordination Office for IT Standards (KoSIT), picks its rules by BT-24. The current XRechnung configuration of 31 August 2026 has scenarios for XRechnung 3.0 and for plain EN 16931 (urn:cen.eu:en16931:2017), but none for urn:factur-x.eu:1p0:basicwl. A BASIC WL file is therefore not accepted there, and no business rule runs. How technical errors and content errors relate is explained in our article on the e-invoice format error.
This excerpt shows where the identifier sits in a CII file (fictitious example, context block only):
<rsm:ExchangedDocumentContext>
<ram:GuidelineSpecifiedDocumentContextParameter>
<ram:ID>urn:factur-x.eu:1p0:basicwl</ram:ID>
</ram:GuidelineSpecifiedDocumentContextParameter>
</rsm:ExchangedDocumentContext>
Myth 6: "Buyers must reject BASIC WL right away"
No. Since 1 January 2025, businesses established in Germany must be able to receive e-invoices (BMF letter of 15 October 2024, para. 62). That does not stop suppliers from sending "other invoices" during the transition. Under § 27(38) UStG (opens in a new tab):
| Supply made in | BASIC WL allowed as "other invoice"? | Condition |
|---|---|---|
| 2025 and 2026 | yes, sent by 31 Dec 2026 | buyer's consent |
| 2027 | yes, sent by 31 Dec 2027 | issuer's 2026 total turnover at most EUR 800,000, buyer's consent |
| 2027 | no | issuer's 2026 total turnover above EUR 800,000 |
| from 2028 | no | applies to all domestic B2B invoices |
A buyer rarely knows a supplier's prior-year turnover. For 2027 it is simpler to ask suppliers with a BASIC WL export to change the profile now than to assess each invoice later. Who must issue e-invoices from January is covered in Germany e-invoicing 2027.
What to do instead
If you issue invoices:
- Open a recent outgoing invoice and read BT-24 (steps in the next section).
- If it says
basicwlorminimum, switch your software export to EN 16931. BASIC is legally sufficient too but covers fewer fields. - Check that every line arrives in the XML with description, quantity, unit and net amount.
- Finish the switch before your issuing obligation starts: 1 January 2027 with more than EUR 800,000 prior-year turnover, otherwise 1 January 2028.
If you receive invoices:
- Until the end of 2026, post a BASIC WL invoice like any "other invoice" and check the mandatory details in the PDF part.
- Ask the supplier in writing for the EN 16931 or XRECHNUNG profile.
- Keep a list of suppliers that still need to switch, so that 2027 holds no surprises.
For the format basics, read what is ZUGFeRD; more articles are collected under ZUGFeRD and Factur-X guides.
How to spot BASIC WL with docutools.pro
- Open the ZUGFeRD extractor and click "Choose PDF". The tool runs in your browser, so the file never leaves your computer. One PDF at a time is free.
- In the "Invoice summary" tab, a file without lines shows "No line items found in the XML." under "Line items". That strongly suggests MINIMUM or BASIC WL. The extractor does not display the profile as a separate field.
- Switch to the "XML source" tab and search for
GuidelineSpecifiedDocumentContextParameter. The value inram:IDis the profile identifier. Save the file with "Download XML". - Load that XML into the ZUGFeRD validator (it accepts XML only, not PDFs). The file is sent to our server for the check. For BASIC WL it shows "No official validation scenario matches this file" with the identifier it found. The free plan allows 2 uploads a day up to 500 KB; the Pro plan removes the limit.
- If you need a compliant file and have no suitable software, the XRechnung generator creates ZUGFeRD files. It writes the identifier of the XRECHNUNG reference profile into BT-24, never MINIMUM or BASIC WL.
Sources
- BMF letter of 15 October 2024, BStBl I p. 1320, paras. 7, 25, 30, 31, 62–65 (IHK copy of the original, German) (opens in a new tab)
- ZUGFeRD FAQ with profile descriptions, FeRD (German) (opens in a new tab)
- § 14 UStG on gesetze-im-internet.de (German) (opens in a new tab)
- § 27 UStG (para. 38) on gesetze-im-internet.de (German) (opens in a new tab)
- Profile identifiers in the Mustang library (Profiles.java) (opens in a new tab)
The BMF letters of 15 October 2025 and 15 October 2026 supplement the 2024 letter. The paragraph numbers 7, 25, 30, 31 and 62 to 65 cited here are from the letter of 15 October 2024.
Last reviewed: November 2026
This article is general information, not tax or legal advice.
Tools for this article
- ZUGFeRD / Factur-X XML ExtractorExtract, view and download the embedded e-invoice XML from ZUGFeRD and Factur-X PDFs.Open tool →
- XRechnung ViewerParse, validate & repair German e-invoices with GoBD-compliant audit trail.Open tool →
- E-Invoice GeneratorCreate compliant XRechnung XML and ZUGFeRD hybrid PDF invoices instantly.Open tool →
Frequently asked questions
What does BASIC WL mean in ZUGFeRD and Factur-X?
BASIC WL is the second-smallest of the five ZUGFeRD and Factur-X data profiles. It carries header and total data but no individual invoice lines. The German e-invoicing forum FeRD describes it as a booking aid: the buyer can post the invoice with it, but it does not represent a complete invoice under the German VAT Act. The same profile identifier is used in Factur-X.
Is a ZUGFeRD BASIC WL invoice accepted in Germany?
Only as an 'other invoice', not as an e-invoice. Under § 27(38) UStG, invoices in a non-compliant electronic format may be sent until 31 December 2026 with the buyer's consent. For supplies made in 2027 this still works only if the issuer's total turnover in 2026 was at most EUR 800,000. From 1 January 2028 every domestic B2B invoice needs a valid e-invoice format.
Which ZUGFeRD profile should I use instead of BASIC WL?
Use EN 16931 for most B2B invoices. BASIC is legally sufficient too, but it covers fewer fields. Both contain invoice lines and are based on the EN 16931 standard. FeRD explicitly recommends the EN 16931 profile for EU-compliant invoices. Ask your software vendor which profile the export setting produces, and test one invoice before you switch.
Can a foreign supplier keep sending BASIC WL to German customers?
The German issuing obligation applies to supplies between businesses established in Germany, so a supplier without a German establishment is usually outside it. A German customer may still ask for EN 16931 because its accounts payable process reads the XML. Check with your tax adviser if you have a fixed establishment in Germany.