German e-invoice guide: mandate, KoSIT, ZUGFeRD, validation and automation
38English companion guides for German B2B and B2G e-invoices: what is a German e-invoice (basics), what is XRechnung (format), what is ZUGFeRD (format), what is EN 16931 (norm), mandate 2025/2027, transition periods to 2028, ZUGFeRD/Factur-X vs. XRechnung/EN 16931, e-invoice example (XML), validation errors (BR-DE), DATEV & tax advisors, Python/Node SDK, Peppol, email delivery, tradespeople, opening & reading an e-invoice, Leitweg-ID (B2G routing), free vs paid, KoSIT validation, GoBD, VAT, PDF myths and automation with n8n, Make, Zapier, API, MCP, agents and small-business workflows. German remains the primary catalog.
Software choice
German e-invoice software: which solution you actually need
Accounting suite or focused engine/API? When your existing software is enough for EN 16931 e-invoices — and when an API/MCP solution with a KoSIT accept gate and a free validator fits better.
Automation
Automate German e-invoicing: from trigger to a validated EN 16931 file
Generate EN 16931-compliant ZUGFeRD/Factur-X or XRechnung files from your shop, CRM, ERP or workflow via API, MCP server or no-code (n8n, Make, Zapier) — each through the same KoSIT-aligned accept gate as the free validator.
Comparison
German e-invoice software comparison: four approaches, one compliance gate
Accounting/ERP suite, online portal, focused engine with API/MCP, or build it yourself — compared across format coverage, technical validation, integration and pricing, with a KoSIT-aligned accept gate and a free validator.
n8n workflow
Generate EN 16931 e-invoices from n8n
Webhook, HTTP Request, and response-node setup for German ZUGFeRD / Factur-X invoices.
Make scenario
Generate German e-invoices from Make
A Make scenario for CRM, form, or shop data using the fakturai API and technical validation.
Zapier workflow
Generate ZUGFeRD invoices with Zapier and an API
How Zapier can request a German B2B e-invoice from deals, forms, or spreadsheets.
API and agents
German e-invoicing API for agents, backends, and MCP clients
Why agents need a narrow validating e-invoice tool instead of a full accounting suite.
Mandate 2025/2027
German e-invoicing mandate for B2B teams 2025/2027
Receive obligation since 2025, issuing phased 2027/28. Why a PDF is not an e-invoice and the KoSIT gate helps.
Format choice
ZUGFeRD, Factur-X, XRechnung and EN 16931: which format fits?
Comparison for B2B vs B2G. Only COMFORT/EN 16931/EXTENDED profiles (not MIN/BASIC-WL) meet the requirements.
Technical validation
Technical validation for German e-invoices — KoSIT, EN 16931 and sum validation
The 4 validation layers at fakturai. What the KoSIT-Accept-Gate actually checks (and what it does not replace per GHOA-1671).
PDF vs e-invoice
Why a PDF is not an e-invoice (and what counts instead)
Myth-busting: PDF-only counts as 'other invoice' in transition. Structured EN 16931 (hybrid/XML) is required. Validator first.
API & Agents
Create e-invoices: ZUGFeRD / Factur-X with fakturai (API & MCP)
Practical steps and JSON example to generate compliant German B2B e-invoices via API or MCP. KoSIT gate before delivery. Free validator first.
GoBD compliance
E-Invoice GoBD-compliant: archiving, creation and verification in Germany
GoBD rules for structured e-invoices (8y retention, original format, integrity). KoSIT-Accept-Gate supports GoBD archiving of the XML part. Full GHOA-1671. Free validator first.
API & MCP
Create e-invoices per API & MCP: ZUGFeRD / Factur-X with fakturai
6 steps with JSON payload, curl example, MCP agent prompt. KoSIT gate before delivery. Free validator first.
VAT / Vorsteuer
German e-invoice & VAT: input VAT deduction only with correct structured data
Only EN 16931-compliant structured e-invoice (ZUGFeRD/Factur-X) with all VAT mandatory elements in the XML part entitles to input VAT deduction. KoSIT gate. Free validator first.
KoSIT & compliance
KoSIT validator for German e-invoices: what the official ACCEPT gate actually checks
The official KoSIT ACCEPT result is the decisive technical bar for EN 16931 e-invoices. How fakturai's 4-layer gate works and what it deliberately does not replace.
Validation checklist
German e-invoice validation checklist before sending or booking
Practical checks for ZUGFeRD/Factur-X, XRechnung, EN 16931, mandatory structured data, PDF/A, VAT coding and KoSIT acceptance.
Receiving / Inbound
Receiving German e-invoices: obligations, validation and GoBD archiving for B2B recipients
B2B receipt obligation since 1.1.2025. Validate received structured e-invoices with KoSIT gate, archive GoBD-compliant, protect input VAT. Free validator first.
Small business
German e-invoicing for small businesses and freelancers
A practical guide for small B2B businesses, freelancers and agencies: formats, validation, PDF pitfalls, API/MCP generation and what remains your responsibility.
Leitweg-ID & B2G
Leitweg-ID in German B2G e-invoices (XRechnung): structure, example and where to find it
The Leitweg-ID routes an XRechnung to the correct public-administration recipient (EN 16931 field BT-10). Structure, example, where to find it and B2B vs B2G. Free validator first.
Open & view
How to open and read a German e-invoice (XRechnung & ZUGFeRD)
Open a German e-invoice: ZUGFeRD/Factur-X in any PDF reader, XRechnung XML made readable (visualisation/validator). Plus check for free whether the file meets EN 16931.
Free & freemium
Free German e-invoice: what is actually free (validate and create)
Validate ZUGFeRD/Factur-X/XRechnung for free with no account, and start creating for free. Honest breakdown of what is free vs paid — and why a plain PDF is not an e-invoice. KoSIT accept gate.
Example & sample
E-invoice example (XML): what a German e-invoice looks like
An annotated XRechnung XML sample with all EN 16931 mandatory fields (BT/BG codes), XRechnung vs ZUGFeRD, and how to turn the sample into a valid file. Free validator first.
Format decision
XRechnung or ZUGFeRD: the difference and which one you need
Pure XML vs PDF with embedded XML, B2G vs B2B, which profiles meet the mandate and which format you need. Free validator first.
Validation errors
XRechnung validation errors (BR-DE): how to fix them
The 5 most common XRechnung validation errors: BR-DE-1 (missing seller endpoint), sum mismatches, wrong profile, wrong VAT category code. Free BR-DE validator first.
DATEV & accounting
E-invoices and DATEV: import and post structured invoices cleanly
How ZUGFeRD/Factur-X and XRechnung are processed in DATEV Unternehmen online and the firm, why imports fail, and how to validate files against EN 16931 before handover. Free validator first.
Tax advisors & firms
German e-invoices for tax advisors: clients, validation and a clean booking workflow
How the B2B mandate changes document intake for tax firms: receive XRechnung/ZUGFeRD, validate before posting, protect input VAT and archive GoBD-compliant. Free validator first.
Transition periods 2025–2028
German e-invoice transition periods 2025–2028: what applies when
Receipt obligation since 2025, paper/PDF with consent through 2026 (smaller businesses through 2027, €800k threshold), full issuing obligation from 2028. Orientation + free validator.
Python & Node SDK
Generate German e-invoices with Python and Node.js (API integration)
Send a JSON payload to the fakturai REST API from Python or Node.js, get back an EN 16931-compliant ZUGFeRD/Factur-X or XRechnung file. No XML knowledge needed. KoSIT accept gate before delivery.
Peppol & B2G
Peppol and German e-invoices: what you need to know
Peppol explained: a transmission network (not a format), B2G vs B2B, XRechnung vs Peppol BIS Billing 3.0, and why fakturai is not an access point. Free validator first.
E-invoice by email
Sending a German e-invoice by email: what is allowed and what matters
Sending a ZUGFeRD/Factur-X PDF or XRechnung XML by email is allowed — no transmission channel is prescribed. What matters: the file must contain an EN 16931 data set. Free validator first.
Trades & crafts
E-invoicing for tradespeople and craft businesses in Germany
Receipt obligation since 2025, transition until 2027 (€800k threshold), full obligation from 2028. B2B vs B2C, ZUGFeRD as the easiest entry, Kleinunternehmer rules. Free validator first.
Basics
What is a German e-invoice? Definition, formats and the mandate
A structured invoice per EN 16931 — not a PDF. XRechnung vs ZUGFeRD/Factur-X, the phased mandate 2025/2028, and how to check any file for free. The starting point for the whole topic.
Format
What is XRechnung? Germany's XML e-invoice format explained
Germany's pure-XML e-invoice standard — a CIUS of EN 16931, maintained by KoSIT, the B2G standard. XRechnung vs ZUGFeRD, UBL vs CII, the Leitweg-ID and the mandate explained. Free validator first.
Format
What is ZUGFeRD? The hybrid PDF/XML e-invoice format explained
Germany's hybrid e-invoice format — a PDF/A-3 carrying embedded EN 16931 CII XML. Factur-X as the identical French profile, the ZUGFeRD profiles (MINIMUM to EXTENDED), and ZUGFeRD vs XRechnung explained. Free validator first.
Norm
What is EN 16931? The European e-invoice norm explained
The European norm defining the semantic core invoice model — business terms (BT), business groups (BG) and two XML syntaxes (UBL 2.1, UN/CEFACT CII). The basis for XRechnung (a CIUS) and ZUGFeRD/Factur-X (profiles). Free validator first.
Mandatory fields
German e-invoice mandatory fields: which fields must an e-invoice contain?
Mandatory fields of a German e-invoice on two layers: § 14 UStG details plus the structured EN 16931 fields (business terms BT/BG), Leitweg-ID (BT-10) for B2G, VAT breakdown, totals and the KoSIT acceptance gate. Free validator first.
Correct & cancel
Correcting and cancelling a German e-invoice: corrections, cancellations and credit notes
You don't overwrite a sent e-invoice — you issue a correction document: a cancellation/credit note (type 381) or corrected invoice (type 384) with the preceding-invoice reference (BG-3, BT-25/26) and the KoSIT accept gate. Free validator first.