Issuing a compliant E-invoice in Germany from 2027 requires more than clicking “generate invoice” in your accounting software. Germany e-invoicing requirements 2027 specify the file format, the data fields, the transmission method, and the archiving rules and a gap in any one of these makes the document non-compliant, even if it looks like an invoice and the buyer accepts it. This guide provides a practical Germany e-invoice step-by-step guide: from choosing the right format, through setting up compliant software, to transmitting the invoice, handling errors, and archiving correctly. Follow each step before your applicable deadline January 2027 if your 2025 annual turnover exceeded €800,000, January 2028 if it did not.
The legal standard for an e-invoice in Germany is set in §14 UStG as amended by the Wachstumschancengesetz. An E-Rechnung must be structured, machine-readable, and conform to EN 16931 the European standard for electronic invoices. The standard defines 52 mandatory data fields. All 52 must be present and correctly populated; a missing or incorrectly formatted field causes a validation failure and means the document is not an E-Rechnung under German law, regardless of how it was generated or what file extension it carries. Germany e-invoicing requirements 2027 apply this standard uniformly to XRechnung (pure XML) and ZUGFeRD (hybrid PDF-XML) the two main compliant formats for domestic B2B invoicing. The rest of this guide walks through how to satisfy all requirements from first format choice to final archival.
Key Takeaways
- Germany e-invoice requirements: An e-invoice must be a structured, machine-readable document conforming to EN 16931. A plain PDF generated from standard invoicing software does not qualify as a structured E-Rechnung.
- Germany e-invoice mandatory fields: EN 16931 defines required business terms, including supply date (BT-72) and buyer VAT ID (BT-48 where applicable). Seller bank details are generally recommended for payment processing but are not a universal mandatory field.
- Germany e-invoicing requirements 2027: Businesses should prepare software that generates compliant structured invoices, such as XRechnung or ZUGFeRD using a qualifying EN 16931 profile, subject to applicable transitional provisions.
- Compliant e-invoice software Germany: Software should generate valid EN 16931 output and pass the applicable validation rules. Confirm the precise ZUGFeRD profile or XRechnung specification supported rather than relying only on a general software compatibility claim.
- Transmission of an e-invoice in Germany: Electronic delivery may include sending an XML invoice or a ZUGFeRD PDF containing embedded XML by email. Printing an XRechnung XML document and sending it by post does not preserve its structured electronic form.
What Makes an E-Invoice Compliant in Germany?
A compliant e-invoice in Germany satisfies three requirements simultaneously: format compliance (the document is in an accepted structured format), content compliance (all 52 mandatory EN 16931 data fields are present and correctly populated), and transmission compliance (the invoice was transmitted electronically to the buyer). Missing any one of the three means the invoice is not a compliant E-Rechnung. Format compliance means using XRechnung, ZUGFeRD at EN 16931 or Extended profile, or PEPPOL BIS Billing 3.0 not a plain PDF, not a scanned invoice, not a ZUGFeRD at Basic WL profile. Content compliance means every EN 16931 mandatory field is populated with valid data in the correct format date fields as ISO 8601 dates, VAT IDs in EU format, amounts without currency symbols in the XML (use the currency code field instead).
Germany e-invoicing requirements 2027 also require that the E-Rechnung be transmitted electronically. The transmission method itself is not prescribed: emailing the XML file or ZUGFeRD PDF as an attachment satisfies the requirement; transmitting via PEPPOL satisfies it; submitting via a supplier portal satisfies it. What does not satisfy the requirement is printing the E-Rechnung and delivering it physically, even if the printed version includes a QR code or reference to an online version. The electronic transmission requirement means the buyer must receive the machine-readable file in a digital channel not a printout of the machine-readable file. Most businesses satisfy this automatically by emailing the invoice; the compliance risk is for businesses that currently transmit invoices by post and have not yet updated their delivery workflow.
Step 1: Choose the Right E-Invoice Format (XRechnung or ZUGFeRD)
Choosing the right format is the first step in the Germany e-invoice step-by-step guide. The decision tree is straightforward. Do you invoice German public authorities (federal ministries, federal agencies, state procurement bodies)? If yes, you must use XRechnung the ZRE federal portal and most state OZG-RE portals do not accept ZUGFeRD. Do you invoice primarily B2B customers? If yes, ZUGFeRD at EN 16931 profile is the most common choice it preserves the familiar PDF invoice experience while adding the mandatory XML layer. Do you have large-volume invoice flows to customers with automated AP systems? If yes, consider XRechnung or PEPPOL BIS Billing 3.0, which are pure XML and cleaner for AP automation than ZUGFeRD.
Compliant e-invoice software Germany plays a decisive role in format selection. Your choice of format should align with what your invoicing software can generate natively. Most German SME accounting platforms (DATEV, Lexware, sevDesk, Fastbill) support ZUGFeRD natively from recent versions and XRechnung through additional modules or updated tiers. Enterprise ERP systems (SAP S/4HANA, Microsoft Dynamics 365, Oracle Fusion) support both formats through standard or add-on functionality. Before committing to a format, confirm in writing with your software vendor: (a) which format they generate, (b) which ZUGFeRD profile they use, (c) whether their output passes the KoSIT validator, and (d) when the compliant e-invoice feature was certified or last updated. These four questions distinguish compliant e-invoice software Germany from software that merely claims format support without verified compliance.
Mandatory Fields and Data Required on a German E-Invoice
Germany e-invoice mandatory fields span the full EN 16931 data model. The 52 mandatory Business Terms (BTs) cover: invoice identification (invoice number, invoice date, currency code); seller details (name, address, country code, VAT ID or tax number); buyer details (name, address, country code, VAT ID); supply information (supply date or period BT-72 or BT-73/74, which §14 UStG requires separately from invoice date); line item data (item name, unit price, quantity, net amount per line); VAT data (VAT category code per line, VAT rate per line); document totals (sum of line net amounts, total VAT amount, invoice total with VAT); and payment details (payment due date or payment terms). All 52 fields must be populated; the absence of even one causes EN 16931 schema validation to fail.
Several Germany e-invoice mandatory fields deserve extra attention because they are routinely missing in accounting software templates not originally designed for EN 16931. The supply date (BT-72) is legally required under §14 Abs. 4 Nr. 6 UStG and must reflect the actual date the goods were delivered or the service was performed not the invoice date. Many legacy templates merge these into a single date field. The buyer VAT identification number (BT-48) is an EN 16931 mandatory field for B2B invoices and must be the buyer’s Umsatzsteuer-Identifikationsnummern not their domestic tax number. The seller’s own tax number (Supernumerary) or VAT ID (BT-31) must also be present. Running your first E-Rechnung through the KoSIT validator at xeinkauf.de will identify every field gap before you transmit to a live customer.
| EN 16931 BT Code | Field Name | Example Value | Mandatory? | Common Error |
|---|---|---|---|---|
| BT-1 | Invoice number | RE-2027-00047 | Yes | Non-unique numbering across invoice series |
| BT-2 | Invoice date | 2027-03-15 | Yes | ISO 8601 format required — not DD.MM.YYYY |
| BT-5 | Invoice currency | EUR | Yes | Missing when amount fields already imply EUR |
| BT-31 | Seller VAT ID | DE123456789 | Conditional | Using Steuernummer instead of USt-IdNr format |
| BT-48 | Buyer VAT ID | DE987654321 | Yes (B2B) | Missing when master data not updated; most common validation error |
| BT-72 | Supply date | 2027-03-12 | Yes | Omitted or set equal to invoice date without confirmation of actual supply date |
| BT-112 | Invoice total (gross) | 2,975.00 | Yes | Rounding error in multi-line invoices causing total mismatch |
| BT-119 | VAT rate | 19 | Yes (per VAT breakdown) | Percentage as decimal (0.19) instead of integer (19) |
| BT-131 | Net amount per line | 2,500.00 | Yes (per line) | Gross amount used instead of net; VAT included in line amount |
How to Create and Send an E-Invoice in Germany
Germany e-invoice step-by-step guide for creation and sending: Step 1 — configure your invoicing software to generate XRechnung or ZUGFeRD at EN 16931 profile. In most modern accounting platforms, this is a settings change: navigate to invoice settings, select E-Rechnung format, choose profile (EN 16931 or Extended for ZUGFeRD; UBL or CII for XRechnung), and save. Step 2 — create the invoice as normal in your software, ensuring all mandatory fields are populated. Pay particular attention to supply date (separate from invoice date), buyer VAT ID, and VAT category codes. Step 3 — generate the E-Rechnung file (XML for XRechnung; PDF for ZUGFeRD). Step 4 — validate the file before sending: upload to the KoSIT validator at xeinkauf.de and confirm zero errors. A warning-only result may be acceptable; any error means the invoice fails EN 16931 and must be corrected.
Transmission is Step 5. For most domestic B2B transactions, emailing the XRechnung XML or ZUGFeRD PDF as an attachment to the buyer’s invoicing email address satisfies the Germany e-invoicing requirements 2027 transmission obligation. For B2G transactions, transmission must go via ZRE (federal) or the applicable OZG-RE portal (state), or via PEPPOL if the public authority accepts PEPPOL delivery. Compliant e-invoice software Germany for B2G typically includes PEPPOL or portal integration; standalone XRechnung generators require a separate PEPPOL access point for PEPPOL transmission. Step 6 is archiving: immediately after transmission, archive the original E-Rechnung file in your GoBD-certified archive the same file you transmitted, unmodified, with a timestamp and transmission record. Do not archive a printout. Do not archive a different version.
E-Invoice Archiving and Retention Rules in Germany
E-invoice in Germany archiving is governed by GoBD the German ordinance on electronic bookkeeping and record retention. GoBD requires that every issued and received E-Rechnung be retained for 10 years, counted from the end of the calendar year in which the invoice was issued. The archive must be revision-proof: no modification, deletion, or overwriting is permitted after the document is stored. The document must be retained in its original machine-readable format an XRechnung XML as an XML file, a ZUGFeRD PDF as the full PDF with embedded XML intact. Printing either format to paper and discarding the digital original violates GoBD. Extracting the XML from a ZUGFeRD PDF and discarding the PDF (or vice versa) also violates GoBD.
Germany e-invoicing requirements 2027 for archiving extend to Datenzugriff the German tax authority’s right to access electronic accounting records during a Betriebsprüfung (tax audit). The archive must support three access modes: direct read access (Z1), filtered read access (Z2), and data extract in IDEA-compatible format (Z3). Most GoBD-certified document management systems support all three. When selecting compliant e-invoice software Germany for archiving, ask specifically for the GoBD certification document, the last certification date, and which Datenzugriff access level is supported. Certification by an auditor is not permanent; it applies to the specific software version at the time of certification. Check whether the certification covers the version you are actually running.
Common Errors When Issuing E-Invoices and How to Avoid Them
The five most common errors when issuing an e-invoice in Germany cluster around the same root causes: insufficient pre-go-live testing, incomplete master data, and software that claims compliance without verified profile output. Error one: wrong ZUGFeRD profile. The software generates ZUGFeRD but defaults to Basic WL this is not an E-Rechnung. Fix: validate the first generated invoice through KoSIT before any live transmission; confirm the profile is EN 16931 or Extended. Error two: supply date missing or equal to invoice date without confirmation. §14 UStG requires a supply date separately from invoice date. Fix: update invoice template to include a dedicated supply date field populated from order or delivery records.
Error three: buyer VAT ID missing. This is the most common EN 16931 validation failure for businesses that have not completed master data remediation. Fix: run a master data audit and collect Umsatzsteuer-Identifikationsnummern for all B2B customers before go-live. Error four: archiving a printout instead of the machine-readable file. GoBD requires the original file; printing and filing paper is a GoBD violation. Fix: configure your archive system to automatically save the machine-readable file at the time of transmission not as a manual step. Error five: treating the deadline as a start date rather than a hard deadline. Germany e-invoicing requirements 2027 apply on January 1st not “sometime in Q1 2027.” Businesses that start implementation in November 2026 for a January 2027 deadline consistently encounter go-live issues. Six months of preparation is realistic; three months is tight; one month is high-risk.
For businesses preparing for Greece Advintek offers automated invoice processing, data validation, accounting software integration, and secure digital archiving to help streamline workflows, reduce manual errors, and support compliance readiness for applicable Greek electronic invoicing requirements.
| Implementation Step | Key Actions | Timeline (Before Deadline) | Success Criteria |
|---|---|---|---|
| Format decision | Choose XRechnung, ZUGFeRD or both; confirm B2G requirements | 6+ months | Format decision documented; confirmed with largest 10 customers |
| Software assessment | Verify current software e-invoice capability; identify gaps; get vendor roadmap | 5–6 months | Software confirmed capable or replacement/module identified |
| Master data audit | Collect VAT IDs; verify addresses; obtain Leitweg-IDs for B2G | 4–5 months | 100% of active B2B customers have valid VAT ID in CRM/ERP |
| Validation testing | Generate test invoices; run through KoSIT validator; achieve zero errors | 2–3 months | Zero validation errors on all test invoice types (standard, credit note, multi-line, mixed VAT) |
| Archive setup | Configure GoBD archive; test retention; verify Datenzugriff | 2–3 months | GoBD certification confirmed; test archive and retrieval successful |
| Go-live and monitoring | First live E-Rechnungen issued; monitor transmission confirmations; log all outputs | From deadline | All covered B2B invoices issued as E-Rechnung; zero validation errors reported by customers |
Frequently Asked Questions
1. Can I send an e-invoice in Germany by email as a PDF attachment?
Yes — if the PDF is a ZUGFeRD file at EN 16931 or Extended profile (containing the mandatory XML). A plain PDF email attachment is not a compliant E-Rechnung. An XRechnung XML file attached to an email also satisfies the requirement.
2. What is the Germany e-invoice mandatory fields list in full?
The full list is the 52 mandatory Business Terms of EN 16931, plus German CIUS additions. The KoSIT XRechnung specification document (available at xeinkauf.de) lists all mandatory and conditional fields with German-language descriptions.
3. Do I need Germany e-invoicing requirements 2027 compliance for intercompany invoices?
Yes — if both entities are separate VAT-registered businesses established in Germany and the supply is subject to German VAT, intercompany invoices fall under the mandate. Intra-group does not create an exemption.
4. Which compliant e-invoice software Germany is best for a small business?
For businesses below 100 invoices per month, cloud accounting tools like sevDesk, Lexware Office, or Fastbill offer the simplest path to XRechnung and ZUGFeRD generation. Confirm the specific profile supported and run a test invoice through the KoSIT validator before committing.
5. What if the buyer rejects my e-invoice in Germany as non-compliant?
Identify the specific validation error (request the error message from the buyer’s AP system), correct the invoice data, and reissue as a new E-Rechnung with a new invoice number. If a credit note for the original is needed, issue it as a structured E-Rechnung credit note document.
Source by:
Image by Gemini
