Germany E-Invoicing Requirements and Mandatory Invoice Fields

Germany is implementing e-invoicing in phases from 2025 to 2028, with mandatory receiving from 2025 and phased issuance requirements thereafter. Businesses need to understand the mandatory invoice fields and ensure their finance and ERP systems can generate, receive, validate, and process structured invoice data accurately. 

What Is the Scope and Timeline of Germany’s E-Invoicing Framework? 

Germany’s mandatory e-invoicing regime primarily applies to domestic B2B transactions where German VAT law requires an invoice. B2C transactions are generally outside the domestic B2B mandate. B2G invoicing follows a separate public-sector framework and should be assessed independently of the B2B mandate.

Whether an invoice is in scope depends on the parties, transaction, VAT treatment, place of supply, applicable exceptions, and the transition framework for issuance.

• Domestic B2B: Transactions between businesses established in Germany are generally in scope, subject to applicable exceptions and the transition framework.
• Cross-border: Cross-border transactions require separate assessment under the applicable German VAT regulations. The domestic B2B mandate does not apply uniformly to these transactions.
• VAT treatment: Reverse charge and other special VAT treatments can change the applicable invoice and data requirements.
• Exceptions: Small-value invoices up to €250 gross, passenger transport tickets, qualifying small-business invoices, and certain transactions involving non-business recipients can fall outside the mandate. Where German VAT law does not require an invoice, mandatory e-invoicing may also not apply.
• Transition: Receipt of e-invoices has been mandatory since 1 January 2025. For issuance, the applicable transition framework and the issuer’s previous-calendar-year turnover determine the deadline.

Note: For 2027, the €800,000 previous-year turnover threshold is decisive. Businesses above €800,000 must issue e-invoices from 1 January 2027, while those at or below €800,000 can continue under the transition through 31 December 2027.

What Information Must an E-Invoice Contain in Germany?

E-invoices in Germany must contain the information prescribed under German VAT law in a structured electronic format. The important distinction is that these data elements must be available as structured invoice information, not merely displayed visually on a PDF.

For enterprise implementations, mandatory fields should therefore be mapped to ERP master data, transactional data and the selected e-invoice syntax.

How Are Mandatory Invoice Fields Structured in Germany?

German VAT law defines the required invoice information, while EN 16931 provides the semantic model for representing it in a structured E-Rechnung. The selected syntax, such as XML, determines how these business terms are technically encoded. Flick helps connect these requirements to the operational invoice flow, supporting the structured data, validation and transmission processes needed for compliant e-invoicing.

• ERP and master data: Provide supplier, customer, tax, payment and transaction data required for invoice generation.
• Invoice business information: Determines invoice and line-level details, including quantities, prices, dates, references and amounts.
• EN 16931 business terms: Maps each data element to the corresponding semantic business term and applies mandatory or conditional requirements.
• Technical syntax: Encodes the mapped business terms in the selected structured format, for machine processing and transmission.

Which E-Invoice Formats Are Accepted in Germany?

E-Invoicing in Germany does not require a universal B2B e-invoice format. The format should also be distinguished from the transmission channel. Email, Peppol, APIs, portals and system-to-system connections are transmission mechanisms; they do not themselves define the invoice format. Qualifying formats include:

• XRechnung: Structured XML based on EN 16931, widely used for public-sector invoicing.
• ZUGFeRD 2.0.1+: Hybrid XML/PDF format; MINIMUM and BASIC-WL profiles do not qualify.
• Other EN 16931-compliant formats: Permitted if they meet the required semantic and technical requirements.
• EDI: Can continue where statutory requirements are met and required VAT data can be correctly and completely extracted. Non-qualifying EDI arrangements benefit from the transition through 2027.

Note: For hybrid invoices, the structured component takes precedence if it conflicts with the visual representation.

Is a PDF Invoice Compliant With Germany’s E-Invoicing Requirements?

A conventional PDF is not an E-Rechnung because it does not provide invoice information in the required structured form. PDF invoices may remain permissible during applicable transition periods, subject to the relevant conditions and, for electronic non-e-invoices, recipient consent. 

After the applicable transition, a conventional PDF cannot satisfy the e-invoicing requirement for in-scope transactions. 

How Do E-Invoice Fields Affect ERP and Finance Operations?

Mandatory fields create a data-architecture requirement across the invoice lifecycle, affecting both invoice generation and receipt.

What Should Multinational Enterprises Consider for Germany?

Multinational enterprises should assess Germany’s e-invoicing requirements across legal entities, ERP environments, and transaction flows. A centralised compliance layer can standardise core controls while accommodating entity-specific deadlines, VAT treatments, systems, and invoice processes.

• Entity scope: Determine the applicable requirements for each legal entity in Germany and invoice flow.
  Different entities may have different turnover levels, systems, and applicable transition periods.
• Transaction scope: Assess domestic B2B transactions based on VAT treatment, transaction type, and applicable exceptions.
  Cross-border invoice flows require separate assessment under the relevant German VAT requirements.
• Transition frameworks: Apply the €800,000 previous-year turnover threshold when determining the 2027 issuing requirement.
  The applicable deadline should be established for each issuing entity.
• ERP integration: Map structured invoice, tax, customer, and supplier data across ERP and accounting systems.
  Shared-service environments should support consistent data processing across multiple entities and invoice flows.
• Formats and transmission: Support qualifying EN 16931-compliant formats and appropriate transmission channels.
  Existing EDI, Peppol, or service-provider infrastructure should be assessed against the applicable requirements.
• Controls: Implement validation, exception handling, correction, retransmission, and retention controls. Controls should operate consistently across invoice generation, receipt, processing, and accounting.

How Should Businesses Validate E-Invoices in Germany? 

A structured e-invoice can still be rejected if its data is incomplete, inconsistent, or mathematically incorrect. Applying a few pre-transmission validations can reduce avoidable corrections, processing issues, and payment delays.

• Invoice and reference checks: Use a unique invoice number for each invoice and make sure credit notes or corrections point to the correct original invoice.
• Date checks: Verify that the invoice date, supply date, and service period accurately reflect the transaction and are appropriate for the invoice type. Dates should also follow the required structured format.
• Amount and VAT checks: Check that line-item amounts reconcile with the document totals. The net amount, VAT amount, and gross total should be calculated correctly, with VAT amounts matching the applicable rates and taxable bases.
• Profile-specific requirements: For XRechnung invoices, check that the fields required by the applicable profile are present. For example, BT-23 (business process type), BT-34 (seller electronic address), and BT-49 (buyer electronic address) must be populated where required. For federal B2G invoices, the Leitweg-ID is provided in BT-10.
• Integrity and readability: Controls should preserve the invoice's authenticity, integrity, and readability throughout its lifecycle, from creation and transmission through to storage and retrieval.

Conclusion

Germany’s e-invoicing requirements are not just a format change. Businesses must ensure accurate invoice data, compliant structured formats, and ERP processes for generation, receipt, validation, exchange, and retention.

Preparing these controls at the entity and transaction level helps businesses meet the mandate while keeping finance operations ready for future digital reporting requirements. 

FAQs

What are the mandatory fields on an e-invoice in Germany?

Core fields include supplier/customer IDs, invoice number/date, supply details, amounts, VAT data, totals, and transaction references.

Is a digital signature required?

No. A digital signature is not generally required for a compliant e-invoice in Germany.

Does Germany’s e-invoice have to comply with EN 16931?

Germany's e-invoicing framework uses EN 16931 as the basis for structured invoice data, and qualifying formats must meet the applicable semantic and technical requirements 

Are intra-group invoices automatically exempt?

No. Their treatment depends on the transaction and applicable VAT circumstances.

Do cross-border invoices fall under Germany’s e-invoice requirements?

Not automatically. Cross-border flows require separate assessment based on the parties, transaction, place of supply and applicable VAT requirements.

Does the buyer need a Peppol Access Point? 
No. A buyer does not need its own Peppol Access Point to receive e-invoices. Peppol is a transmission channel, not a mandatory e-invoice format or receiving requirement.