Free tool · Runs in your browser

Free XRechnung and ZUGFeRD checker
that says what a portal will reject.

E-Rechnung prüfen: XRechnung und ZUGFeRD kostenlos validieren, direkt im Browser.

Drop an XRechnung, an EN 16931 XML or a ZUGFeRD / Factur-X PDF. You get the invoice in readable form and every rule it breaks, in plain English with the German term an accountant or portal would use, and how to fix it at the source. Nothing you check leaves your browser.

Free, no signup. A pre-check, not the official validator: what it checks and what it does not.

Check an e-invoice

Runs entirely in your browser. Your invoice is read by this tab and never uploaded, sent or stored; it is gone when you close the tab. You can load the page, go offline, and it still works.

Drop an e-invoice here

XRechnung or other EN 16931 XML (UBL or CII), or a ZUGFeRD / Factur-X PDF with the XML inside. Up to 20 MB.

Which files count as an e-invoice in Germany

Under § 14 UStG an e-invoice is a structured electronic invoice that follows EN 16931, or an agreed format from which the same data can be extracted, such as EDI. The BMF names XRechnung and ZUGFeRD from version 2.0.1, except the MINIMUM and BASIC-WL profiles (BMF letter of 15 October 2025, Abschnitt 14.1 Abs. 14 UStAE). The checker reads the specification identifier (BT-24) and tells you which of these a file is.

E-invoice formats and whether they count as an e-invoice in Germany
FormatE-invoice?
XRechnung 3.0 (UBL or CII)The German CIUS of EN 16931. Public buyers require it.Yes
ZUGFeRD / Factur-X EN 16931 (COMFORT)PDF/A-3 with the full EN 16931 XML inside. The usual choice for B2B.Yes
ZUGFeRD / Factur-X EXTENDEDEN 16931 plus extra fields for industry use.Yes
ZUGFeRD / Factur-X BASICA compliant subset of EN 16931, with line items.Yes
ZUGFeRD / Factur-X BASIC WLHeader and totals, no line items. A booking aid.No
ZUGFeRD / Factur-X MINIMUMA few header fields and the total. A booking aid.No
ZUGFeRD 1.0Predates EN 16931.No
A PDF without XML, a scan, a Word fileReadable by people only.No, an 'other invoice'

In a hybrid ZUGFeRD invoice the XML is the invoice: if the PDF picture and the data disagree, the data wins. A file the software cannot read at all, because of a format error, is not an e-invoice, whatever it contains.

The German e-invoicing mandate, with dates

The obligation comes from the Growth Opportunities Act (Wachstumschancengesetz), which rewrote § 14 UStG, with the transition in § 27 Abs. 38 UStG. It covers invoices between businesses established in Germany.

  1. Since 1 January 2025Every business in Germany must be able to receive e-invoices from other domestic businesses, small businesses under § 19 UStG included. An email inbox is enough.
  2. 2025 and 2026Issuers may still send paper, or with the buyer's consent another electronic format such as a PDF (§ 27 Abs. 38 Nr. 1 UStG).
  3. 2027Only businesses whose total turnover in the previous year was at most EUR 800,000 may keep sending paper or, with consent, PDFs. Agreed EDI formats remain allowed with consent until the end of 2027 (§ 27 Abs. 38 Nr. 2 and 3 UStG).
  4. From 1 January 2028Every invoice between domestic businesses must be an e-invoice, apart from the exceptions below.

Outside the obligation: invoices up to EUR 250, passenger tickets and invoices from small businesses under § 19 UStG may always be sent as an 'other invoice', and invoices to consumers and to customers abroad are not covered. Invoices to German public buyers follow their own rules: federal authorities have required XRechnung or another EN 16931 format since 27 November 2020 (ERechV). Sources: the BMF letters of 15 October 2024, 15 October 2025 and 15 October 2026 and the BMF's e-invoice FAQ. Not tax advice: ask your tax adviser about your case.

A rule error is not always a VAT error

The BMF separates three kinds of problems. A format error (Formatfehler) means the file does not follow the format at all: it is not an e-invoice. A business rule error (Geschäftsregelfehler) means the data breaks a rule, for example a missing BT-10 in an XRechnung, or a VAT amount that does not match its rate. It only makes the invoice defective for VAT if it touches a mandatory VAT field (Inhaltsfehler).

The BMF letter of 15 October 2026 spells out the consequence: technically, any broken core rule means the file no longer conforms to EN 16931, while for VAT purposes a file with a business rule error but no format error is still an e-invoice. In practice the technical view is the one that bites: the buyer's system or a public portal rejects the file, and you send it again. So every error below is worth fixing, and the ones in mandatory VAT fields (seller VAT ID, amounts, rates) first.

Per the BMF, a business may rely on a suitable validation tool's result with the care of a prudent merchant, and keeping the validation report is a good way to show it. This page is a pre-check; for the report, use the official validator.

What it checks, and what it does not

117 rules, each implemented from the official rule test, not from memory: the EN 16931 business rules from the CEN schematron (release 1.3.17) and the XRechnung 3.0.2 rules from the KoSIT XRechnung schematron (release 2.6.0), with severities as the KoSIT validator configuration sets them. Amounts are compared as exact decimals with the rounding the rules allow.

German VAT rules1 rules
  • BMF-PROFILEThe format is accepted as an e-invoice in Germany (MINIMUM, BASIC WL and ZUGFeRD 1.0 are not).
EN 1693182 rules
  • BR-01An Invoice shall have a Specification identifier (BT-24).
  • BR-02An Invoice shall have an Invoice number (BT-1).
  • BR-03An Invoice shall have an Invoice issue date (BT-2).
  • BR-04An Invoice shall have an Invoice type code (BT-3).
  • BR-05An Invoice shall have an Invoice currency code (BT-5).
  • BR-06An Invoice shall contain the Seller name (BT-27).
  • BR-07An Invoice shall contain the Buyer name (BT-44).
  • BR-08An Invoice shall contain the Seller postal address (BG-5).
  • BR-09The Seller postal address shall contain a Seller country code (BT-40).
  • BR-10An Invoice shall contain the Buyer postal address (BG-8).
  • BR-11The Buyer postal address shall contain a Buyer country code (BT-55).
  • BR-12An Invoice shall have the Sum of Invoice line net amount (BT-106).
  • BR-13An Invoice shall have the Invoice total amount without VAT (BT-109).
  • BR-14An Invoice shall have the Invoice total amount with VAT (BT-112).
  • BR-15An Invoice shall have the Amount due for payment (BT-115).
  • BR-16An Invoice shall have at least one Invoice line (BG-25).
  • BR-CO-18An Invoice shall at least have one VAT breakdown group (BG-23).
  • BR-21Each Invoice line shall have an Invoice line identifier (BT-126).
  • BR-22Each Invoice line shall have an Invoiced quantity (BT-129).
  • BR-23An Invoice line shall have an Invoiced quantity unit of measure code (BT-130).
  • BR-24Each Invoice line shall have an Invoice line net amount (BT-131).
  • BR-25Each Invoice line shall contain the Item name (BT-153).
  • BR-26Each Invoice line shall contain the Item net price (BT-146).
  • BR-27The Item net price (BT-146) shall not be negative.
  • BR-28The Item gross price (BT-148) shall not be negative.
  • BR-CO-04Each Invoice line shall be categorized with an Invoiced item VAT category code (BT-151).
  • BR-29The Invoicing period end date (BT-74) shall be on or after its start date (BT-73).
  • BR-30An Invoice line period end date (BT-135) shall be on or after its start date (BT-134).
  • BR-31Each Document level allowance (BG-20) shall have an amount (BT-92).
  • BR-32Each Document level allowance (BG-20) shall have a VAT category code (BT-95).
  • BR-33Each Document level allowance (BG-20) shall have a reason (BT-97) or reason code (BT-98).
  • BR-36Each Document level charge (BG-21) shall have an amount (BT-99).
  • BR-37Each Document level charge (BG-21) shall have a VAT category code (BT-102).
  • BR-38Each Document level charge (BG-21) shall have a reason (BT-104) or reason code (BT-105).
  • BR-41Each Invoice line allowance (BG-27) shall have an amount (BT-136).
  • BR-42Each Invoice line allowance (BG-27) shall have a reason (BT-139) or reason code (BT-140).
  • BR-43Each Invoice line charge (BG-28) shall have an amount (BT-141).
  • BR-44Each Invoice line charge (BG-28) shall have a reason (BT-144) or reason code (BT-145).
  • BR-45Each VAT breakdown (BG-23) shall have a VAT category taxable amount (BT-116).
  • BR-46Each VAT breakdown (BG-23) shall have a VAT category tax amount (BT-117).
  • BR-47Each VAT breakdown (BG-23) shall be defined through a VAT category code (BT-118).
  • BR-48Each VAT breakdown (BG-23) shall have a VAT category rate (BT-119), except if not subject to VAT.
  • BR-49A Payment instruction (BG-16) shall specify the Payment means type code (BT-81).
  • BR-50A Payment account identifier (BT-84) shall be present if Credit transfer (BG-17) information is provided.
  • BR-61For a credit transfer (BT-81 = 30 or 58) the Payment account identifier (BT-84) shall be present.
  • BR-55Each Preceding Invoice reference (BG-3) shall contain the preceding invoice number (BT-25).
  • BR-17The Payee name (BT-59) shall be provided if the Payee (BG-10) is different from the Seller.
  • BR-18The Seller tax representative name (BT-62) shall be provided if there is a tax representative (BG-11).
  • BR-19The Seller tax representative postal address (BG-12) shall be provided.
  • BR-56Each Seller tax representative party (BG-11) shall have a VAT identifier (BT-63).
  • BR-57Each Deliver to address (BG-15) shall contain a Deliver to country code (BT-80).
  • BR-62The Seller electronic address (BT-34) shall have a Scheme identifier.
  • BR-63The Buyer electronic address (BT-49) shall have a Scheme identifier.
  • BR-53If a VAT accounting currency (BT-6) is given, the VAT total in that currency (BT-111) shall be provided.
  • BR-CO-09VAT identifiers (BT-31, BT-48, BT-63) shall start with an ISO 3166-1 country prefix (EL for Greece).
  • BR-CO-10Sum of Invoice line net amount (BT-106) = sum of Invoice line net amounts (BT-131).
  • BR-CO-11Sum of allowances on document level (BT-107) = sum of document level allowance amounts (BT-92).
  • BR-CO-12Sum of charges on document level (BT-108) = sum of document level charge amounts (BT-99).
  • BR-CO-13Invoice total without VAT (BT-109) = BT-106 - BT-107 + BT-108.
  • BR-CO-14Invoice total VAT amount (BT-110) = sum of VAT category tax amounts (BT-117).
  • BR-CO-15Invoice total with VAT (BT-112) = BT-109 + BT-110, and BT-110 appears once in the invoice currency.
  • BR-CO-16Amount due for payment (BT-115) = BT-112 - paid amount (BT-113) + rounding amount (BT-114).
  • BR-CO-17VAT category tax amount (BT-117) = taxable amount (BT-116) x rate (BT-119) / 100, rounded, within one currency unit.
  • BR-CO-26The seller is identified by a Seller identifier (BT-29), legal registration identifier (BT-30) or VAT identifier (BT-31).
  • BR-CL-01The document type code (BT-3) is from the UNTDID 1001 invoice or credit note list.
  • BR-CL-04The invoice currency (BT-5) is an ISO 4217 alpha-3 code.
  • BR-CL-05The VAT accounting currency (BT-6) is an ISO 4217 alpha-3 code.
  • BR-CL-14Country codes are ISO 3166-1 alpha-2.
  • BR-CL-16Payment means codes (BT-81) are from UNTDID 4461.
  • BR-CL-17VAT category codes are from UNCL 5305 (S, Z, E, AE, K, G, O, L, M, B).
  • BR-CL-23Unit codes (BT-130) are UN/ECE Recommendation 20 or 21 codes, such as H87 or C62 for pieces.
  • BR-CL-25Electronic address schemes (BT-34-1, BT-49-1) are from the CEF EAS list.
  • BR-DEC-09 to 28Document totals, VAT breakdown amounts, line net amounts and allowance or charge amounts have at most two decimals.
  • BR-S-01 and peersEach VAT category used on a line, allowance or charge has its VAT breakdown (one, for every category except S).
  • BR-S-02 and peersLines in categories S, Z, E, AE, K and G need the seller's VAT identifier or tax number as each rule requires; AE and K also need the buyer's.
  • BR-S-05 and peersA standard-rated line has a rate above zero; Z, E, AE, K and G lines have rate 0; O lines have no rate.
  • BR-S-08 and peersEach VAT breakdown's taxable amount equals its lines plus charges minus allowances (S within one currency unit).
  • BR-AE-09 and peersThe VAT amount is 0 for categories Z, E, AE, K, G and O.
  • BR-AE-10 and peersE, AE, K, G and O breakdowns carry an exemption reason; S and Z breakdowns must not.
  • BR-IC-11An intra-community supply has an actual delivery date (BT-72) or an invoicing period (BG-14).
  • BR-IC-12An intra-community supply has a deliver to country code (BT-80).
  • BR-O-11An invoice with a 'not subject to VAT' breakdown has no other VAT breakdown.
XRechnung32 rules
  • XR-VERSIONAn XRechnung identifier names the current version, 3.0, which the KoSIT validator recognises.
  • BR-DE-1An invoice shall contain payment instructions (BG-16).
  • BR-DE-15The Buyer reference (BT-10) shall be provided.
  • BR-DE-2The Seller contact group (BG-6) shall be provided.
  • BR-DE-3The Seller city (BT-37) shall be provided.
  • BR-DE-4The Seller post code (BT-38) shall be provided.
  • BR-DE-5The Seller contact point (BT-41) shall be provided.
  • BR-DE-6The Seller contact telephone number (BT-42) shall be provided.
  • BR-DE-7The Seller contact email address (BT-43) shall be provided.
  • BR-DE-8The Buyer city (BT-52) shall be provided.
  • BR-DE-9The Buyer post code (BT-53) shall be provided.
  • BR-DE-10The Deliver to city (BT-77) shall be provided if a delivery address (BG-15) is given.
  • BR-DE-11The Deliver to post code (BT-78) shall be provided if a delivery address (BG-15) is given.
  • PEPPOL-EN16931-R020The Seller electronic address (BT-34) must be provided (part of XRechnung 3.0).
  • PEPPOL-EN16931-R010The Buyer electronic address (BT-49) must be provided (part of XRechnung 3.0).
  • BR-DE-14The VAT category rate (BT-119) shall be provided in every VAT breakdown.
  • BR-DE-16With VAT categories S, Z, E, AE, K, G, L or M, the seller's VAT ID (BT-31), tax number (BT-32) or tax representative (BG-11) is given.
  • BR-DE-17The invoice type code (BT-3) should be 326, 380, 384, 389, 381, 875, 876 or 877.
  • BR-DE-18Cash discount (Skonto) lines in the payment terms (BT-20) follow the #SKONTO#TAGE=n#PROZENT=n.nn# syntax.
  • BR-DE-19With SEPA credit transfer (58), the account (BT-84) should be a valid IBAN.
  • BR-DE-20With SEPA direct debit (59), the debited account (BT-91) should be a valid IBAN.
  • BR-DE-21The specification identifier (BT-24) should be the XRechnung identifier.
  • BR-DE-23-a/bCredit transfer (30, 58) carries an account (BG-17) and no card or direct debit data.
  • BR-DE-24-a/bCard payment (48, 54, 55) carries card data (BG-18) and no account or direct debit data.
  • BR-DE-25-a/bDirect debit (59) carries the mandate data (BG-19) and no account or card data.
  • BR-DE-26A corrected invoice (384) should name the preceding invoice (BG-3).
  • BR-DE-27The seller's phone number (BT-42) should contain at least three digits.
  • BR-DE-28The seller's email address (BT-43) should be a plausible address.
  • BR-DE-30With a direct debit (BG-19), the creditor identifier (BT-90) shall be given.
  • BR-DE-31With a direct debit (BG-19), the debited account (BT-91) shall be given.
  • BR-DE-TMP-32The invoice should give a delivery date (BT-72), an invoicing period (BG-14) or a period on every line.
  • BR-TMP-6 / BR-TMP-7Dates are written as YYYY-MM-DD (UBL) or YYYYMMDD with format 102 (CII).
Syntax2 rules
  • SYNTAX-AMOUNTEvery amount, quantity and rate is a decimal number.
  • SYNTAX-DATEEvery date is a real calendar date in the syntax's format (UBL YYYY-MM-DD, CII format 102).

Tested on the official samples

Every file in the KoSIT XRechnung test suite, the CEN example invoices and the ZUGFeRD 2.x examples (XML and PDF) passes without a false error, and broken copies of each are caught. MINIMUM and BASIC WL samples are flagged as not being e-invoices.

Not checked here

The XML schema itself, every code list (exemption reasons, identifier schemes), the ZUGFeRD EXTENDED and XRechnung extension fields, the PDF/A-3 conformance of a ZUGFeRD PDF, and whether a Leitweg-ID or VAT ID actually exists. The KoSIT validator covers the first three.

Fix the cause, not the file

Almost every error this page finds comes from the system that issued the invoice: a customer record without a Leitweg-ID, units stored as "Stk", VAT rounded per line, a credit note printed as a negative invoice. Editing the XML by hand fixes one file; the next invoice fails the same way. Two things I build for that:

  • Issuing e-invoices from an old ERP

    A converter layer that reads invoice data from the system you have, maps it to EN 16931, validates every file with KoSIT and sends it once.

  • Receiving e-invoices automatically

    Incoming XRechnung and ZUGFeRD files validated, matched to the order and booked in DATEV or your ERP, with a person on every exception.

FAQ

Is this an official XRechnung validator?

No. It is a free pre-check that runs a scoped set of rules from the official EN 16931 and XRechnung rule sets in your browser, explains each failure in plain English with the German term, and shows the invoice readably. The reference is the KoSIT validator with the XRechnung configuration, which also checks the XML schema and every code list. Use this page to find and understand problems quickly, and the KoSIT validator when you need a formal report.

Is my invoice uploaded anywhere?

No. The file is read by your browser tab and checked by code that runs in that tab. Nothing is sent to a server, nothing is stored, and it is gone when you close the tab. The site's analytics count page visits, never files or their contents. You can load the page, disconnect from the internet and check invoices offline.

Ist ZUGFeRD BASIC WL oder MINIMUM eine E-Rechnung?

Nein. Nach Abschnitt 14.1 Abs. 14 UStAE in der Fassung des BMF-Schreibens vom 15. Oktober 2025 erfüllt ZUGFeRD ab Version 2.0.1 die Anforderungen an eine E-Rechnung, ausgenommen die Profile MINIMUM und BASIC-WL. Sie enthalten keine oder kaum Rechnungspositionen und gelten nur als Buchungshilfe. Ab dem Profil BASIC (empfohlen: EN 16931) ist eine ZUGFeRD-Datei eine E-Rechnung.

Wie prüfe ich eine XRechnung kostenlos?

Ziehen Sie die XML-Datei oder die ZUGFeRD-PDF in das Feld oben. Die Prüfung läuft in Ihrem Browser, nichts wird hochgeladen. Sie sehen die Rechnung lesbar aufbereitet und jede verletzte Regel mit Regel-ID, deutscher Bezeichnung und dem Weg zur Korrektur. Für einen offiziellen Prüfbericht nutzen Sie anschließend den KoSIT-Validator mit der XRechnung-Konfiguration.

What is the Leitweg-ID, and when is it required?

The Leitweg-ID is the routing identifier German public buyers use to direct an invoice to the right office. It goes in the buyer reference, BT-10, and XRechnung requires BT-10 in every invoice (rule BR-DE-15), so a public-sector portal rejects a file without it. Between businesses, BT-10 carries whatever reference the buyer asks for. The BMF letter of 15 October 2025 notes that a missing BT-10 is a business rule error without VAT consequences: the invoice can still be valid for VAT, but the buyer's system or portal may refuse it.

XRechnung or ZUGFeRD: which should we send?

Both meet the German requirement. XRechnung is pure XML and is what federal and state public buyers expect. ZUGFeRD in the EN 16931 profile or higher is a PDF with the XML embedded, which suits business customers whose accounts teams still read invoices on screen; the XML is what counts, and it takes precedence over the picture. Which one to use is agreed between you and the buyer.

Why does my file pass here but fail in a portal or the KoSIT validator?

This page checks a scoped subset of the rules: the mandatory fields, the totals and VAT arithmetic, VAT category consistency, dates, currency, payment means and the XRechnung-specific rules. It does not validate the XML schema, every code list, the ZUGFeRD EXTENDED fields or the PDF/A-3 container, and portals add their own checks, such as whether a Leitweg-ID exists. The reverse should not happen: on the official KoSIT and ZUGFeRD sample files, this page reports no errors.

Is a PDF invoice still allowed after 2027?

Between domestic businesses, only until your deadline. A business whose total turnover in the previous year exceeded EUR 800,000 must issue e-invoices from 1 January 2027, every business from 1 January 2028. Invoices up to EUR 250, passenger tickets, invoices from small businesses under § 19 UStG, invoices to consumers and invoices to customers abroad may stay as PDF or paper.

Does the checker read ZUGFeRD and Factur-X PDFs?

Yes. It finds the embedded XML (factur-x.xml, zugferd-invoice.xml or xrechnung.xml) inside the PDF and checks that. A PDF without embedded XML is reported as not being an e-invoice. The PDF/A-3 format of the container itself is not checked.