E-Invoicing in Germany
B2B e-invoicing under the Growth Opportunities Act, EN 16931, ZUGFeRD and XRechnung
The mandate at a glance
Germany runs the largest e-invoicing transition in Europe by business count. The Growth Opportunities Act (Wachstumschancengesetz) made structured e-invoice reception mandatory for every VAT-registered business in January 2025, and phases in the issuing obligation through 2027 and 2028. A PDF sent by email stopped being a legally privileged invoice format the moment the reception rule took effect: the structured XML is now the legally decisive layer.
The mandate is format-open but standard-strict: any format compliant with EN 16931 is acceptable. In practice the German market has settled on two: ZUGFeRD, a hybrid PDF/A-3 with embedded CII XML that keeps invoices human-readable, and XRechnung, the pure-XML national CIUS required in the public sector.
| Date | Obligation | Scope |
|---|---|---|
| January 2025 | Must be able to receive structured e-invoices | All VAT-registered businesses |
| January 2027 | Must issue structured e-invoices | Businesses with turnover above EUR 800,000 |
| January 2028 | Must issue structured e-invoices | All VAT-registered businesses |
Required formats and network
Accepted formats: any EN 16931-compliant syntax. ZUGFeRD (profiles EN 16931 and EXTENDED are the safe B2B choices) dominates because accounts-payable teams can still open the PDF, while DATEV, SAP, and Lexware import the embedded XML. XRechnung, in either CII or UBL syntax, is equally valid for B2B and mandatory for B2G.
There is no clearance platform: invoices travel directly between trading partners (by email, portal, or Peppol), which keeps integration simpler than in Italy or Poland but puts the full validation burden on the sender and receiver.
Public sector (B2G)
XRechnung has been mandatory for invoices to German federal authorities since November 2020, submitted via Peppol, ZRE, or OZG-RE portals. Every B2G invoice must carry a Leitweg-ID, the buyer routing identifier, in the BuyerReference field; a missing or malformed Leitweg-ID is the single most common rejection cause.
How to comply
- Confirm your systems can ingest structured e-invoices (ZUGFeRD and XRechnung) today: the reception duty already applies.
- Pick your issuing format: ZUGFeRD where humans still read invoices, XRechnung for public-sector buyers.
- Validate every outgoing invoice against the EN 16931 rule set plus the German CIUS rules before sending.
- Capture the Leitweg-ID for public-sector buyers and map it to BuyerReference.
- Plan for the January 2027 issuing deadline now if your turnover exceeds EUR 800,000.
Integrate from your system
Each guide shows the full integration for one platform, with code: map the invoice to JSON, call the API, store the returned file. The API validates every invoice before it returns it, and keeps up with the rule sets, so the integration does not change when the formats do.
- Dynamics NAV 2018: C/AL codeunits: ZUGFeRD and XRechnung from posted invoices, supplier invoice import
- Business Central: AL extension: ZUGFeRD, XRechnung and incoming e-invoices
- SAP ECC and S/4HANA on-premise: ABAP classes: ZUGFeRD and XRechnung from billing documents, email delivery by the API, supplier invoice import
- SAP Business One: Service Layer and C#: ZUGFeRD and XRechnung from A/R invoices, email delivery, A/P drafts from supplier e-invoices
- Dynamics AX 2012 and Dynamics 365 Finance (X++): CustInvoiceJour to ZUGFeRD or XRechnung with one API call, attachment or email delivery, supplier invoices as pending vendor invoices
- Odoo: Custom module for Odoo 12 to 17, with vendor bill import and an XML-RPC script for Odoo Online
- Shopware 6: Self-hosted PHP plugin: scheduled task or Flow Builder action, hybrid PDF as the invoice document, supplier invoices stored in a custom entity
- Make (formerly Integromat): Create ZUGFeRD and XRechnung in a scenario with the HTTP module; validate and import supplier invoices with Router and Iterator
- Excel and Access VBA: ZUGFeRD and XRechnung from a VBA macro, plus a button that checks and imports supplier invoices
- Power Automate custom connector: SharePoint lists, Outlook import and XRechnung with a Leitweg-ID column
- Sage 100: C# service reading the Sage 100 database, Leitweg-ID from the customer master
- Oracle NetSuite: SuiteScript 2.1: e-invoices per OneWorld subsidiary, vendor bill import
- abas ERP: ESDK app in Java: ZUGFeRD after saving a sales invoice, XRechnung, supplier invoice checks
- SelectLine: C# service with the SelectLine API, supplier invoices as Eingangsrechnungen
- Shopify: Node.js custom app with the Admin GraphQL API
- WooCommerce: WordPress plugin with HPOS and Action Scheduler
- microtech büro+: C# service with the büro+ GraphQL API
- plentymarkets / PlentyONE: Node.js service on the REST API, PDF uploaded to the order
- DATEV e-invoice import: Incoming ZUGFeRD and XRechnung into DATEV, step by step
- xentral: Node.js service, webhook trigger, supplier invoices as liabilities
- weclapp: Node.js service on the weclapp REST API v2
- IBM i (AS/400): RPG and Db2 SQL with the QSYS2 HTTP functions
- Airtable: Automation script, email delivery and supplier import
- Retool: Internal tool app and Retool Workflow on your own SQL tables
- SAP BTP: CAP service: ZUGFeRD and XRechnung from S/4HANA billing documents
- Dynamics 365 and Power Automate: Flow: hybrid invoices from Dataverse records, no code
- Salesforce: Apex callout: e-invoices from opportunities and orders
- Zapier: Zap: ZUGFeRD from any trigger app
- n8n: HTTP node: self-hosted workflow for creating and validating invoices
- Google Sheets: Apps Script: ZUGFeRD from a spreadsheet row
- Bubble: API Connector: ZUGFeRD and Factur-X from a Bubble app
- ZUGFeRD API toolkit: Code guides for C#, Java, Python, Node.js, PHP, Ruby and Go
- XRechnung API toolkit: Leitweg-ID, KoSIT validation and PDF preview for public-sector invoices
- Incoming e-invoices: Extraction API: read ZUGFeRD, XRechnung and plain PDF invoices into your system
More platforms and languages in the integrations hub.
Complete ZUGFeRD Toolkit
Everything you need to create, convert, embed, validate, and extract ZUGFeRD invoices, via REST API or online.
Frequently Asked Questions
Who must issue e-invoices from January 2027?
Businesses whose turnover in the previous calendar year was above EUR 800,000 must issue structured e-invoices from 1 January 2027. All other VAT-registered businesses follow on 1 January 2028. Receiving e-invoices has been mandatory for every business since January 2025.
Is a PDF invoice still legal in Germany?
A plain PDF no longer counts as an e-invoice under German VAT law. Since January 2025 the structured XML data is the legally decisive invoice. During the transition, senders may still issue paper or plain PDF with the recipient's consent, but that option ends with the issuing phases in 2027 and 2028.
ZUGFeRD or XRechnung: which one do I need?
For B2B either works, and ZUGFeRD is usually preferred because the PDF layer stays human-readable. For invoices to German public-sector buyers, XRechnung is mandatory. Both satisfy EN 16931, and the embedded ZUGFeRD XML at the EN 16931 profile is technically an XRechnung-compatible CII document.
Does Germany require a government clearance platform?
No. Unlike Italy's SDI or Poland's KSeF, Germany has no central clearance. Invoices are exchanged directly between the parties, and each side is responsible for validating conformance.
What is a Leitweg-ID and when do I need one?
The Leitweg-ID is the routing identifier German public-sector buyers assign for B2G invoices. It goes in the BuyerReference field of an XRechnung. It is required for every invoice to a federal, state, or municipal authority, and is not used in B2B.
Ready to automate your invoices?
Validate, convert and embed compliant e-invoices through one API. Start your 30-day free trial. No credit card required.