Peppol Country Guide · Germany
Build for Germany’s structured invoice mandate before 1 January 2027
Reception has been required since 2025. Issuing moves in phases, with larger businesses first and all covered domestic businesses following in 2028. Peppol can prove to be a key delivery option, but it is not the only one.
Overview
Who and what Germany’s mandate covers
Germany's e-invoicing mandate generally applies to invoices issued between domestic businesses, subject to specific statutory exclusions. The public sector already runs its own track, and consumers are largely outside scope.
| B2B · In scope | B2G · Separate track | B2C · Out of scope |
|---|---|---|
| The mandate generally applies where an invoice must be issued for a transaction between domestic businesses, subject to specific statutory exclusions. Businesses only registered for VAT without a German establishment are not automatically domestic. The €800,000 threshold delays issuing for smaller suppliers by one year; it does not remove receiving capability. | Federal suppliers have generally issued structured invoices since 27 November 2020. Federal exceptions include direct orders up to €1,000 and defined confidential or foreign service cases. Germany's regional governments run public invoicing through their own rules and channels. | Private consumers are outside the domestic business mandate. Invoices for tax exempt supplies under section 4 numbers 8 to 29 UStG and low value invoices up to €250 are excluded from the mandatory electronic form. Tickets treated as invoices are also excluded. Kleinunternehmer need not issue the structured form, but must still be able to receive it. |
Implementation Timeline
Germany e-Invoicing rollout, 2025 to 2030
Every domestic business must be able to receive a structured electronic invoice.
Businesses above 800,000 euros previous calendar year turnover must issue compliant electronic invoices for covered domestic transactions.
The issuing obligation reaches the remaining covered domestic businesses. Transitional relief for legacy EDI ends, while EDI that meets the statutory interoperability requirements may continue.
ViDA digital reporting for covered cross border transactions applies across the European Union. Germany plans a separate domestic reporting system, but details are not yet enacted.
Architecture
A decentralised four corner option
As one permitted route, Peppol moves the invoice between certified service providers. Participant discovery and service metadata tell the sender's Access Point where the receiver can accept the document.
Germany also permits other transmission methods including portals and even email. Federal public buyers use portals such as OZG-RE or ZRE and require routing data such as the Leitweg-ID. Regional government requirements vary.
Invoice Formats
The semantic standard and the formats that implement it
A compliant invoice for Germany carries the tax data required by section 14 UStG in a structured electronic format that enables automated processing. German law does not fix one file format by name. It accepts any format that conforms to, or is interoperable with, the European standard EN 16931, or another format bilaterally agreed between sender and receiver that fully extracts the legally required information and processes it electronically.
For most vendors, the practical path runs through EN 16931 and recognised German e-invoicing formats such as XRechnung and qualifying ZUGFeRD profiles. XRechnung is one recognised implementation, not a mandatory layer for every German B2B invoice.
EN 16931 explained
EN 16931 is the European standard for electronic invoicing. It is a semantic data model: it defines what information an invoice must contain, what each field means (the business terms, such as BT-31 for the seller VAT identifier), and the rules those values must obey. It does not by itself produce a file. A valid German invoice is built by combining three layers:
| 1. Semantic model | 2. Syntax | 3. National CIUS |
|---|---|---|
| EN 16931 defines the core invoice business terms and validation rules. It is the legal baseline that every compliant invoice must satisfy. | Two mandatory XML syntaxes carry the model: UBL 2.1 (Universal Business Language) and UN/CEFACT CII (Cross Industry Invoice). Both are equally valid; either can express the same business terms. | Each country adapts the model to local law. XRechnung is Germany’s EN 16931-based CIUS and is widely used, particularly for public-sector invoicing. For German B2B e-invoicing, it is one recognised implementation rather than a mandatory national layer for every invoice. Peppol BIS Billing 3.0 is another EN 16931-based profile used for network exchange. |
What this means for your business: German B2B e-invoicing does not require XRechnung for every invoice. Support the invoice formats relevant to your customers and validate each against its applicable syntax, semantic and business rules. XRechnung and qualifying ZUGFeRD profiles are recognised options under the German framework.
A selection of the formats
| XRechnung | ZUGFeRD | Factur X |
|---|---|---|
| Germany’s national profile of EN 16931, maintained by KoSIT on behalf of the IT Planning Council. XRechnung 3.0 is the current major specification line; implementations should use the current KoSIT release and validation artefacts. The current published release is 3.0.2. A pure structured XML document delivered in UBL or CII syntax. XRechnung is required in many public-sector invoicing scenarios and is a recognised option for domestic B2B, but it is not the mandatory default format for every German B2B invoice. Extension XRechnung supports additional sector-specific requirements. | ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland) is a hybrid format: structured CII XML is embedded inside a PDF/A 3 file, so the same document is both machine readable and human readable. Qualifying ZUGFeRD profiles can satisfy the German E-Rechnung requirements. BASIC is accepted under §14 UStG but represents a reduced subset. EN 16931 (formerly COMFORT) fully implements EN 16931. EXTENDED is accepted and adds data beyond the EN 16931 core. MINIMUM and BASIC WL are excluded. | ZUGFeRD and Factur-X share a technically aligned core. This can reduce format-conversion work for solutions supporting Germany and France, although country-specific profiles, compliance rules and exchange requirements remain separate. Same EN 16931 conformance rule and same excluded profiles apply. |
ZUGFeRD profiles at a glance
In a hybrid ZUGFeRD document, the structured XML layer takes precedence over the visible PDF whenever the two conflict. Your parsing system should always read the embedded XML, never the rendered text.
| Profile | EN 16931 conformant | Intended use |
|---|---|---|
| MINIMUM | No | Basic reference data only, no line items or VAT breakdown. |
| BASIC WL | No | Wrapped logical data only; excluded from the mandate. |
| BASIC | Yes under German §14 UStG | Reduced subset; accepted as a German E-Rechnung but does not implement the full EN 16931 model. |
| EN 16931 (formerly COMFORT) | Yes | Full EN 16931 profile; accepted for German E-Rechnung. |
| EXTENDED | Yes | EN 16931 plus additional supply-chain and order data; accepted for German E-Rechnung. |
| XRECHNUNG | Yes | Aligns with the XRechnung standard, accepted by federal channels and the Peppol XRechnung extension. Useful when one ZUGFeRD-based system needs to also produce pure XRechnung for public-sector recipients, without a separate toolchain. |
What is not accepted
- A plain PDF is a sonstige Rechnung, not an electronic invoice, after the applicable transition ends.
- Paper invoices do not qualify for covered domestic B2B after the transition.
- Unstructured XML does not qualify merely because the file extension is .xml.
- Legacy EDI that does not allow the legally required invoice data to be extracted correctly and completely.
- A standalone visual representation without the embedded structured data is not compliant.
Reporting Obligations
Invoice exchange now, transaction reporting later
Section 14 UStG generally requires a covered invoice between domestic businesses to be issued within six months after the supply. Germany does not currently operate a general domestic, invoice by invoice reporting platform alongside the B2B exchange mandate. The Finance Ministry states that the electronic invoice foundation is intended to prepare for a later transaction based reporting system, for which legislation is still to be proposed.
Existing VAT returns and relevant recapitulative statements continue independently. Under ViDA, covered cross border transactions move to harmonised digital reporting from 1 July 2030. The directive sets a ten day invoice deadline for those cross border transactions and replaces the present recapitulative statement mechanism for data inside the new system.
Penalties
General invoice offences apply
| Fine | Violation |
|---|---|
| Up to 5,000 euros under section 26a UStG | Intentionally or recklessly failing to issue a required invoice, or failing to issue it within the statutory period |
| Up to 5,000 euros under section 26a UStG may apply to intentional or reckless failures concerning required invoice retention obligations. | Failure to preserve invoices under section 14b UStG |
| No separate repeated violation ceiling is stated in section 26a. Each case is assessed under general offence rules. | Repeated invoice failures |
No automatic technical safe harbour in the statute: Section 26a requires intent or recklessness. That fault standard matters, but it is not a blanket exemption for outages. Preserve validation results, attempted transmission timestamps, delivery responses and incident records to support the facts of any technical failure.
Germany at a glance
The build facts your product team needs
Use these as routing and policy inputs, not as one fixed national workflow.
Businesses with turnover above €800,000 must start issuing e-invoices.
A proven four corner exchange route, especially useful for automated and high volume delivery.
XRechnung and qualifying ZUGFeRD profiles build on the European semantic model.
Section 14 UStG generally sets this period for covered supplies between domestic businesses.
The structured invoice data must be retained for eight years in its original, intact form. For hybrid invoices, additional visual content must also be retained where it contains tax-relevant information not present in the structured data.
Section 26a UStG sets the ceiling for intentionally or recklessly failing to issue a required invoice on time.
KoSIT operates the German Peppol Authority and maintains the XRechnung standard on behalf of the IT Planning Council.
Federal public invoices use the buyer reference to route documents to the correct authority.
The mandate generally applies where an invoice must be issued for a transaction between domestic businesses, subject to specific statutory exclusions.
Frequently Asked Questions
What vendors ask before implementation
No. A software vendor connects to a certified Peppol Access Point rather than seeking certification for every product. Arratech operates the network connection, participant discovery, secure transport and delivery evidence, while your product uses one unified interface.
The four corner transport pattern and EN 16931 data model are familiar. Germany adds German invoice requirements, support for commonly used formats such as XRechnung and ZUGFeRD, Leitweg ID routing for public buyers, federal and state channel differences, and domestic transition logic. Unlike Belgium, Germany does not currently require Peppol as the exclusive route for ordinary business invoices.
For transactions covered by the transition, another electronic format such as a PDF may still be used with recipient consent through 2026. Smaller issuers with prior year turnover no more than 800,000 euros receive one further year. Your receiving flow cannot wait: every domestic business has needed the ability to receive structured invoices since 2025.
Arratech provides one EU hosted connection for Peppol transport, format validation, delivery status and white label embedding. Your team still owns correct source tax data and product decisions, while Arratech removes network certification and country transport plumbing from the build.
Ready for a simple connection to the future of e-Invoicing?
Join the next generation of e-Invoicing infrastructure from Arratech.
Cut costs, stay compliant, and integrate effortlessly.