Germany E-Invoice Format and Technical Specifications

Germany does not prescribe a single universal e-invoice format for domestic B2B transactions. Businesses can use compliant formats such as XRechnung, ZUGFeRD, or other structured formats that comply with EN 16931 and German VAT requirements.

What Are Germany’s E-Invoice Format Requirements?

Under German VAT law, an e-invoice must be issued, transmitted, and received in a structured electronic format that enables automated processing. The format must comply with the applicable European standard and syntax requirements or, under defined conditions, use an agreed format that enables the required invoice data to be extracted into an EN 16931-compliant or interoperable format.

Electronic transmission alone does not make an invoice an e-invoice. A PDF sent by email, for example, is an electronic document but does not meet the structured-format requirement.

How Does EN 16931 Shape German E-Invoice Formats?

EN 16931 defines the business information an invoice must contain and its meaning, but not a single file format or transmission network. For implementation, businesses should distinguish three separate layers:

• Invoice data: The business and tax information the invoice must contain, such as the supplier, buyer, invoice number, tax information, amounts, and payment details.
• Syntax: How that information is structured electronically so that systems can read and process it, such as UBL or UN/CEFACT CII.
• Transmission: How the invoice is exchanged between the supplier and buyer, such as through Peppol, email, a portal, EDI, or an API.

What Germany E-invoice Formats and Technical Specifications are Accepted?

Accepted E-Invoice Formats in Germany

Some of the common e-invoicing options in Germany include XRechnung, qualifying ZUGFeRD profiles, and other structured formats that comply with EN 16931 and the requirements of §14 UStG.

Structured Invoice Syntaxes and Exchange Specifications

The underlying technical syntax or exchange specification is different from the invoice format itself.

Does a PDF with Embedded XML Qualify as an E-Invoice?

A hybrid invoice can qualify as an e-invoice when it meets the applicable requirements. ZUGFeRD is the principal example, combining a human-readable PDF representation with structured XML invoice data.

The structured component is legally significant. For a qualifying ZUGFeRD hybrid invoice, the structured XML component is the authoritative invoice data. The PDF provides the human-readable representation. 

Note: For hybrid invoices, validate that the structured XML contains all required invoice data and remains consistent with the visual representation. 

Does Germany’s E-Invoicing Mandate Require EDI Replacement?

Germany does not require businesses to replace EDI solely because of the e-invoicing mandate. Under §14 UStG, the invoice format can be agreed between the issuer and recipient and may differ from EN 16931 if the format allows the required VAT information to be correctly and completely extracted into a subsequent format that complies with or is interoperable with EN 16931. EDI procedures such as EDIFACT can therefore remain relevant where these conditions are met. 

For enterprises, this means the focus should be on reviewing existing EDI mappings, data fields, and validation rules rather than replacing the entire infrastructure. Where changes are needed, businesses can adapt the data or integration layer while retaining established EDI connections.

How Are German E-Invoices Technically Validated?

A German e-invoice must meet specific structural, data, and processing requirements. The main technical requirements are:

• Structured format: The invoice must use structured electronic data that can be processed automatically. A standard PDF alone does not meet this requirement.
• EN 16931 alignment: The format must comply with EN 16931 and its applicable syntax, or meet the requirements for an agreed format that can be correctly mapped to an EN 16931-compliant or interoperable format.
• Required invoice data: The structured invoice must contain the required business and VAT information. Important data must not exist only in an attached or unstructured document.
• Correct data structure: Invoice information must be placed in the appropriate fields and follow the rules of the selected format. This allows different systems to interpret the data consistently.
• Accurate calculations: Taxable amounts, VAT rates, VAT amounts, totals, and other related values must be logically consistent.
• Correct system mapping: ERP and billing systems must map their invoice data correctly to the selected e-invoice format. Incorrect mapping can create missing or inconsistent information even when the file is technically valid.
• Validation: Businesses should validate invoices against the applicable technical and business rules before issuing or processing them. This helps identify structural errors and inconsistent data early.
• Interoperability: Where an agreed format is used, the invoice data must be capable of being correctly extracted into an EN 16931-compliant or interoperable format.

These requirements mean that e-invoicing compliance depends on more than selecting an accepted format. The underlying data, structure, calculations, and system mapping must also work correctly.

How Enterprises Manage Multiple E-Invoice Formats?

Large enterprises may need to handle several invoice formats across ERP systems, legal entities, customers and trading partners. The challenge is therefore not choosing one German format, but maintaining consistent validation, transformation, routing and monitoring across different invoice flows.

A central e-invoicing layer can help standardize these controls while allowing individual ERP and billing systems to retain their existing configurations. This can reduce the need to redesign every source system whenever a customer, country or regulatory requirement changes.

Flick can support this type of centralized e-invoicing architecture by connecting enterprise systems with the required e-invoicing workflows and providing a consistent layer for processing and compliance.

Conclusion

Germany’s e-invoicing framework allows businesses to use different compliant formats, including XRechnung, ZUGFeRD, and qualifying EDI solutions. The key requirement is that invoice data is structured, complete, correctly mapped, and machine-processable.

For enterprises, the focus should therefore be on reliable data mapping, validation, ERP integration, and interoperability across invoice formats and transmission channels. A strong e-invoicing architecture can meet Germany’s requirements without forcing businesses to replace every existing system or EDI connection.

Frequently Asked Questions

Can businesses use their existing invoice format for German e-invoicing?

Yes, provided the format meets the applicable German requirements and supports the required invoice data in a structured, compliant form.

Does choosing an EN 16931-compliant format guarantee e-invoice compliance?

No, compliance also depends on complete invoice data, correct mapping, calculations, validation, and the applicable German VAT requirements.

Can businesses use different e-invoice formats across their ERP systems?

Yes, businesses can operate multiple compliant formats, but they need consistent validation and data mapping across systems to maintain compliance.

Do the buyer and seller have to use the same e-invoice format?

No, different systems can exchange invoices through interoperable formats as long as the invoice data can be correctly processed and meets the applicable requirements.

What is the biggest technical risk when implementing German e-invoicing?

The main risk is not choosing the wrong format but having incomplete or incorrectly mapped invoice data that fails validation or cannot be processed reliably.