Germany · E-Rechnung
Germany E-Invoicing Integration (XRechnung & ZUGFeRD)
Produce valid XRechnung and ZUGFeRD e-invoices from the ERP you already use, deliver them by Peppol, email or portal, and import inbound e-invoices into accounts payable.
Who must comply with Germany e-invoicing?
The mandate covers domestic B2B transactions between businesses established in Germany. Key points:
- Receiving: every business must be able to receive and process structured e-invoices.
- Issuing: phased in, with transition periods during which other invoice forms are still allowed, depending on prior-year turnover.
- Exclusions: B2C, small-value invoices and certain other cases are excluded.
- B2G: federal and most state public bodies already require XRechnung.
Foreign companies with German establishments and domestic B2B sales are affected too. Confirm your dates with the BMF guidance.
How does German e-invoicing work?
Germany uses a post-audit model. Invoices are exchanged directly between businesses by email, portal, EDI or Peppol. There is no clearance and no real-time reporting to the tax authority today, but invoices must be valid structured documents and stored in line with GoBD retention rules.
- Definition: XRechnung
- Germany's national CIUS of the European e-invoicing standard EN 16931, delivered as UBL or CII XML and maintained by KoSIT.
Which e-invoice formats are valid in Germany?
- XRechnung (UBL or CII), required by most public-sector buyers.
- ZUGFeRD 2.x hybrid PDF/A-3 with embedded XML, in EN 16931-conformant profiles (EN 16931, EXTENDED, XRECHNUNG).
- EDI formats, where both parties agree and the required data can be extracted in line with EN 16931.
- Leitweg-ID routing identifier for public-sector invoices.
How does Co-Mate add XRechnung and ZUGFeRD to your ERP?
We build a module that turns posted ERP invoices into XRechnung or ZUGFeRD per customer, validates them with the official KoSIT rules, and delivers them through your chosen channel or a Peppol Access Point. Inbound e-invoices are validated, shown in readable form and created as draft supplier bills. The original XML is archived. The same platform can also serve France and Spain.
Which ERPs and billing systems do we support for Germany?
- SAP Business One
- SAP (via IDoc/interfaces)
- Microsoft Dynamics 365
- Oracle NetSuite
- Sage
- Odoo
- DATEV (via exports)
- Custom PHP / .NET / Java
- POS systems
Don't see yours? If it stores invoices in a database or exposes an API, export or webhook, we can connect it. See all ERP e-invoicing integrations.
Implementation steps
A predictable path from first call to live, monitored e-invoicing.
- 1
Obligation check
Confirm your receiving obligation now and the date your issuing obligation applies, based on your entities and prior-year turnover.
- 2
Format choice
Decide between XRechnung and EN 16931-conformant ZUGFeRD per customer group, and whether Peppol or email delivery fits.
- 3
Mapping
Map ERP data to EN 16931 fields, German CIUS rules and Leitweg-IDs for public customers.
- 4
Build send & receive
Generate XRechnung/ZUGFeRD, deliver via Peppol, email or portal, and import inbound e-invoices into AP with validation and visualisation.
- 5
Validation & testing
Validate with the official KoSIT validator and Schematron rules, and test with real customers and suppliers.
- 6
Archiving & go-live
GoBD-compliant storage of the original XML and switch-on per entity, with monitoring.
Common Germany e-invoicing challenges and how we handle them
| Challenge | Why it matters | How we handle it |
|---|---|---|
| Receiving obligation already applies | Every business must be able to accept and process e-invoices. | Inbound import with validation, human-readable view and AP draft bills. |
| Choosing XRechnung vs ZUGFeRD | Customers may require different formats. | Per-customer format settings from one canonical model. |
| Leitweg-ID for public customers | B2G invoices are rejected without the correct routing ID. | Leitweg-ID stored on customer records and validated before sending. |
| Validation errors | Invalid XML is not a valid e-invoice. | Official KoSIT validation in the pipeline before delivery. |
| GoBD archiving | The XML original must be stored unaltered and retrievable. | Archive of original files with hashes and search. |
Germany e-invoicing FAQ
Is e-invoicing mandatory in Germany?
What counts as an e-invoice in Germany?
What is the difference between XRechnung and ZUGFeRD?
Do I need Peppol in Germany?
Does Germany clear invoices with the tax authority?
Can our non-German ERP produce XRechnung?
Official sources
Last reviewed:
- E-Rechnung (Federal Government e-invoicing information)
- Federal Ministry of Finance (BMF): e-invoicing guidance
- XRechnung standard (KoSIT)
- European Commission: eInvoicing and EN 16931
E-invoicing rules, timelines and technical specifications change often. This page summarises the official guidance as we understood it on the review date. Always confirm obligations and dates with the tax authority or your tax adviser before acting. Co-Mate provides integration engineering, not tax or legal advice.
Related e-invoicing guides
- E-invoicing integration hubAll countries, models and our approach in one place.
- ERP e-invoicing integrationsSAP Business One, Dynamics, NetSuite, Odoo, Zoho, Tally and more.
- France e-invoicingCertified platforms, Factur-X and e-reporting.
- Europe Peppol integrationBelgium, Poland and other Peppol markets.
- Peppol explainedAccess Points, BIS formats and validation.