How to Create a Compliant E-Invoice in 2026: Step-by-Step Guide for Businesses Still Using PDF Invoices

The End of the PDF Invoice: What Has Changed Since January 2025

Until the end of 2024, a PDF invoice sent by email officially qualified as an electronic invoice in Germany. Since January 1, 2025, that is no longer the case. The law now defines an e-invoice exclusively as a structured, machine-readable document; a standard PDF does not meet this requirement.

That sounds technical. But it has concrete implications for every business in Germany that invoices other businesses (B2B): if you are still sending PDF invoices today, you are operating within a legal transitional window and that window is closing. Businesses that prepare now avoid last-minute scrambles, questions from their tax advisors, and the risk of being non-compliant during a tax audit.

📋  Key fact: Since January 1, 2025, ALL domestic B2B businesses must be capable of receiving e-invoices. The obligation to issue e-invoices follows in phases  from 2027, with full mandatory compliance from 2028.

This guide walks you through the complete process of creating a compliant e-invoice in 2026  step by step, from format selection to archiving  regardless of the size of your business or your current software.

What Is an E-Invoice  and What Is It Not?

A legally compliant e-invoice in Germany from 2025 is a structured, machine-readable document that conforms to the European standard EN 16931 and enables automatic electronic processing. There are three things that are explicitly no longer considered e-invoices:

•        A PDF file sent by email  regardless of how professional it looks.

•        A scanned paper invoice transmitted as an image or PDF file.

•        A Word document or Excel spreadsheet  even if all required invoice fields are correctly filled in.

What an e-invoice must be instead: a structured XML format, or a hybrid document that contains both machine-readable XML and a visual representation  conforming to the XRechnung standard which is called ZUGFeRD (from version 2.0.1 onwards). Both formats meet the requirements of § 14 UStG (German VAT Act) and the European standard EN 16931.

📎 Related reading: Creating XRechnung and ZUGFeRD from PDF  format comparison and technology  how the two formats differ and when each one should be used.

XRechnung or ZUGFeRD? Choosing the Right Format for Your Business

XRechnung  the format for the public sector

XRechnung is a pure XML format developed and maintained by KoSIT (Germany's IT standards coordination body). It contains only structured data and no visual representation. Opening an XRechnung file directly shows machine-readable XML code. Free viewer tools exist to make it human-readable, including the official e-invoice viewer from the German tax authority at www.e-rechnung.elster.de.

XRechnung is mandatory for invoices to federal authorities (B2G) and is increasingly requested in B2B transactions as well. One field many businesses overlook: the Leitweg-ID (routing ID) of the recipient. Without it, an XRechnung submitted to a public sector client will be automatically rejected.

ZUGFeRD  the hybrid format for everyday B2B invoicing

ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland) is a hybrid format: it combines a human-readable PDF/A-3 document with embedded structured XML data. The recipient sees a normal invoice and their ERP or accounting software automatically extracts the underlying structured data. ZUGFeRD is more user-friendly for day-to-day B2B invoicing because it does not require the recipient to have separate viewer software.

Important: not all ZUGFeRD versions are legally compliant. ZUGFeRD is only accepted as a valid e-invoice from version 2.0.1 onwards. The profiles MINIMUM and BASIC-WL are explicitly excluded and do not meet the legal requirements.

💡  Quick rule: Invoices to government bodies → XRechnung (with Leitweg-ID). Invoices to businesses → ZUGFeRD 2.1+ (easier to handle, fully compliant, no viewer required by recipient).

Step-by-Step: How to Create a Compliant E-Invoice in 2026

Here is the complete process, broken down into six concrete steps:

Step 1: Review and complete your master data

A compliant e-invoice requires complete and accurate master data. Ensure your system contains: full company name and address, tax number or VAT identification number, IBAN for payment details, service descriptions that comply with § 14 UStG requirements. Incorrect master data leads to validation errors that can render an e-invoice legally invalid.

Step 2: Populate all mandatory fields under EN 16931

The European standard EN 16931 defines more than 50 mandatory fields for a compliant e-invoice. The most critical are: invoice number (unique and sequential), invoice date and supply date, full supplier and recipient details, tax number or VAT ID of both parties, net amount, tax amount, and gross amount per line item, payment due date and IBAN. For XRechnung invoices to public sector clients, the recipient's Leitweg-ID is an additional mandatory field (BT-10 "Buyer reference") without which the invoice will be rejected.

Step 3: Select your format and generate the e-invoice

Select the appropriate format: XRechnung for government clients, ZUGFeRD 2.1+ for B2B. Enter your invoice data into your ERP system, accounting software, or an e-invoice generator. The software automatically produces the compliant XML file or the hybrid ZUGFeRD PDF. Verify that your software is explicitly certified as "EN 16931 compliant", "XRechnung-capable", or "ZUGFeRD 2.1+". Free online viewers such as the official ELSTER e-invoice viewer allow you to visually check the generated file before sending.

Step 4: Validate your e-invoice before sending

The German Federal Ministry of Finance explicitly recommends validating e-invoices before dispatch. Validation checks that all mandatory fields are present, that totals are mathematically correct, and that the document meets the EN 16931 business rules. Validation errors fall into three categories: format errors (structural problems), business rule errors (logical inconsistencies such as mismatched tax amounts), and content errors (missing or incorrect invoice information). The official KoSIT validator and the ELSTER viewer both offer free validation.

Step 5: Send the e-invoice via the correct channel

The law does not prescribe a specific transmission channel. Permitted delivery methods include: email with the e-invoice as an attachment (ZIP for XRechnung, PDF for ZUGFeRD), the PEPPOL network for cross-border and public sector invoices, a customer or supplier portal operated by the recipient, direct ERP-to-ERP connection. Tip: set up a dedicated email address for invoices  for example, invoice@yourcompany.com. This simplifies both sending and tracking.

Step 6: Archive the e-invoice in GoBD-compliant format

Archiving is the step most frequently overlooked  and the one with the most common errors. The GoBD requires: e-invoices must be stored in their original format (as an XML or ZUGFeRD file, not as a printout), in an immutable and audit-proof form, for a minimum of eight years. The Federal Ministry of Finance clarifies: for a ZUGFeRD invoice, at least the structured XML part must be archived unchanged. Simply printing an e-invoice and filing it in a folder is explicitly not sufficient.

📎 Related reading: E-Invoicing Obligation for Small Businesses in Germany 2026  specific rules and exemptions for Kleinunternehmer and small business owners.

What If You Are Already Creating PDF Invoices From Your Existing System?

Many businesses face the same situation: their existing ERP or accounting software generates invoices as PDFs  and replacing or significantly upgrading that system is not immediately practical or desirable. The question is valid: can an existing PDF workflow be converted into compliant e-invoices without changing the underlying system?

The answer is yes, with the right approach. AI-powered fingerprinting solutions can bridge existing PDF invoice workflows and compliant e-invoice formats seamlessly  without modifying the existing system. The PDF is generated as usual; a conversion layer automatically transforms it into a validated XRechnung or ZUGFeRD document.

This is precisely the approach PEDIF takes. Businesses that have already established their invoicing workflow within an ERP or accounting system can keep their existing processes entirely unchanged. PEDIF handles the automatic conversion of outbound PDF invoices into validated XRechnung or ZUGFeRD documents, no IT project, no system replacement, no disruption to live workflows. The same applies in reverse: incoming e-invoices from suppliers are automatically recognised, processed, and transferred into the ERP.

📎 Learn more about the technology: Why OCR fails and AI fingerprinting is the solution, the technical foundation behind automatic PDF-to-e-invoice conversion.

The Most Common Mistakes When Creating E-Invoices  and How to Avoid Them

•        Wrong ZUGFeRD version: ZUGFeRD MINIMUM and BASIC-WL profiles are not legally compliant. Use only ZUGFeRD 2.1 or higher in the EN 16931 or XRECHNUNG profile.

•        Missing Leitweg-ID for XRechnung: Without the recipient's routing ID, an XRechnung submitted to a public sector body will be automatically rejected. Request the Leitweg-ID from the client before creating the invoice.

•        Incorrect tax rate or mathematically inconsistent amounts: Business rule errors of this type make an e-invoice formally invalid. Validation before sending reliably catches them.

•        Archiving the printout instead of the original file: A printed copy of an e-invoice is not audit-proof archiving. The original XML or ZUGFeRD file must be stored electronically and immutably.

•        Software without EN 16931 certification: Not every accounting tool that claims to create e-invoices actually produces compliant documents. Verify the vendor's conformity statements explicitly before relying on the output.

Frequently Asked Questions (FAQ): Creating E-Invoices in Germany 2026

❓  Is a PDF invoice still permitted in 2026 in Germany?

Yes, but with restrictions. According to the German Federal Ministry of Finance, until December 31, 2026, all businesses may still issue so-called "other invoices" (i.e. PDFs or paper)  with the recipient's consent for PDFs. Businesses with prior-year revenue below €800,000 may continue using PDFs until the end of 2027. From January 1, 2028, structured e-invoices are mandatory for all B2B transactions  without exception.

❓  Which format should I choose: XRechnung or ZUGFeRD?

For invoices to federal authorities and public sector clients, XRechnung is mandatory  including the recipient's Leitweg-ID. For B2B invoices between private businesses, ZUGFeRD from version 2.1 is the more practical choice: the hybrid PDF-plus-XML format is readable by both humans and systems, and requires no separate viewer software on the recipient's side.

❓  How do I create an XRechnung or ZUGFeRD invoice if my ERP does not support it yet?

If your ERP or accounting software cannot yet generate XRechnung or ZUGFeRD, there are two practical approaches: first, use a standalone e-invoice generator (online or as software) that produces compliant files; second, use a conversion solution that automatically transforms your existing PDF invoices into XRechnung or ZUGFeRD. PEDIF takes the second approach: your existing invoicing workflow remains entirely unchanged, and the conversion happens automatically. Learn more at pedif.digital/en.

❓  Do I need to validate an e-invoice before sending it?

The Federal Ministry of Finance explicitly recommends it. While validation is not a statutory requirement, it ensures that the invoice will not be rejected by the recipient due to format errors. Validation errors can jeopardise the recipient's VAT input deduction rights and lead to disputes and delays. The free ELSTER e-invoice viewer and the KoSIT validator both offer fast, reliable validation.

❓  How long must e-invoices be retained and in what format?

E-invoices must be retained for a minimum of eight years under § 14b UStG and the GoBD requirements. Importantly, archiving must be in the original format as an XML file for XRechnung, or as the ZUGFeRD PDF (with embedded XML) for ZUGFeRD. Printing and filing in a physical folder is not an acceptable archiving method for electronic invoices.

❓  Does the e-invoicing obligation apply to small-value invoices?

No. Small-value invoices with a gross amount below €250 are exempt from the e-invoicing obligation  even after 2028. Also exempt are transport tickets and invoices issued to private individuals (B2C transactions). The e-invoicing obligation applies exclusively to domestic B2B transactions between VAT-registered businesses.

❓  What happens if I fail to issue a compliant e-invoice  are there penalties?

The law does not prescribe a direct financial penalty for issuing a non-compliant invoice. However, the practical consequences are significant: the recipient may reject a non-compliant e-invoice, their VAT input tax deduction may be denied, and during a tax audit, non-compliant invoice records can be treated as a tax risk. From 2028, when the obligation applies in full, non-compliant invoicing increasingly becomes a concrete commercial and tax liability.

Conclusion: Acting Now Is Worth It  2028 Is Closer Than It Looks

The transition to e-invoicing is not something to defer to "some point in the future." The obligation to receive e-invoices is already in force. The obligation to issue them is arriving in phases. And the technology that makes the transition straightforward is available right now without major IT projects, without replacing existing systems.

Businesses that want to maintain their existing PDF invoicing workflow while becoming compliant have better options today than at any previous point: AI-powered conversion solutions handle the transformation automatically, validate against EN 16931, and deliver dispatch-ready XRechnung or ZUGFeRD files without any modification to the underlying software.

→ Still using PDF invoices? PEDIF automatically converts your existing invoices into compliant XRechnung or ZUGFeRD  validated, dispatch-ready, without any IT overhead. Learn more at www.pedif.digital/en.