Germany e-Invoicing requires every domestic business to receive structured electronic invoices (e-Rechnung) since 1 January 2025. Issuing becomes mandatory from 1 January 2027 for businesses with prior-year turnover above EUR 800,000, and from 1 January 2028 for all other issuers, subject to statutory exceptions.
Accepted formats include XRechnung and ZUGFeRD 2.0.1 or later (excluding the MINIMUM and BASIC-WL profiles), based on the EN 16931 standard. There is no tax authority clearance and no mandatory portal. Enterprises must automate inbound AP processing, generate valid structured invoices, validate VAT data and archive the structured original for eight years.
Germany e-Invoicing is the mandatory domestic B2B electronic invoicing regime that Germany introduced through amendments to the VAT Act (UStG) and the guidance of the Federal Ministry of Finance (BMF).
This guide explains who Germany B2B e-invoicing covers, which dates apply, which formats qualify, what the compliance model looks like, and how enterprises can prepare ERP, AP, AR, tax and archive processes. It also lists the risks that matter most and a 180-day roadmap you can adapt.
Quick Facts briefly
| Dimension | Current position |
| Authority | Bundesministerium der Finanzen (BMF) and the German tax administration. |
| Core scope | Transactions between domestic entrepreneurs, subject to statutory exceptions. |
| Receive obligation | Active since 1 January 2025. An email inbox can be enough for basic receipt. |
| Issuance transition | Other invoices (paper, PDF) allowed through 31 December 2026 for all issuers. Issuers with prior-year turnover up to EUR 800,000 can continue through 31 December 2027. |
| Valid e-invoice | A structured electronic format that supports electronic processing. A plain PDF is an “other invoice”. |
| Common formats | XRechnung and ZUGFeRD 2.0.1 or later (excluding MINIMUM and BASIC-WL). Other EN 16931 compatible or agreed formats can qualify. |
| Clearance or real-time reporting | None for domestic B2B under the 2025 e-invoice rule. |
| Retention | Eight years. The structured part must stay intact in its original form. |
What Is Germany e-Invoicing and What Changed on 1 January 2025?
Germany redefined the VAT-law concept of an electronic invoice. A compliant e-Rechnung must be structured and must permit electronic processing. A PDF sent by email no longer meets that definition, although it can remain valid as an “other invoice” during the transition periods.
The change already affects operations because every domestic business must be able to receive E-Rechnungen. The BMF states that no special receipt portal is mandatory, so a shared email inbox can technically be sufficient. Enterprise readiness asks for much more than receiving a file. It includes rendering, validation, AP ingestion, approval, tax checks and retention of the structured original.
Germany B2B e-Invoicing Timeline: 2025 to 2028
The rollout runs in phases. The buyer obligation started first, and the issuer obligation follows in two waves based on turnover.
| Period | Issuer position | Buyer position |
| 1 Jan 2025 to 31 Dec 2026 | All issuers may continue with paper or, with recipient agreement, other electronic formats such as PDF. | All domestic businesses must be able to receive e-Rechnung. |
| Calendar 2027 | Issuers with prior-year turnover above EUR 800,000 fall outside the general transition and must issue e-Rechnung. Issuers at or below EUR 800,000 may still use transitional “other invoices”. | Receipt capability continues. |
| From 1 Jan 2028 | The small-issuer transition has ended. Covered domestic B2B transactions require an E-Rechnung, subject to exceptions. | Structured receipt and processing should be fully operational. |
EDI transition
A non-conforming EDI process can continue through 31 December 2027. EDI that already meets the statutory extraction and interoperability conditions may qualify as an e-invoice beyond that date.
Practical tip: the prior-year turnover test decides your wave. For supplies in 2027, your 2026 turnover is the reference figure, so groups near the EUR 800,000 line should plan for 1 January 2027 rather than wait for year-end results.
Who Must Comply? e-Rechnung Germany Applicability and Exceptions
The core rule applies to transactions between domestic entrepreneurs. “Domestic” links to establishment and fixed-establishment concepts, not only to holding a German VAT registration number. Cross-border groups should therefore not use VAT registration alone as the scope test.
| Entity or situation | Status | What to know |
| Domestic B2B between entrepreneurs | In scope | Receipt since 1 Jan 2025. Issuance from 1 Jan 2027 or 1 Jan 2028 depending on turnover. |
| Issuer with prior-year turnover above EUR 800,000 | Phase 1 issuance | Must issue e-Rechnung from 1 Jan 2027. |
| Issuer with prior-year turnover up to EUR 800,000 | Phase 2 issuance | May use other invoices through 31 Dec 2027. Mandatory from 1 Jan 2028. |
| Private consumers (B2C) | Not covered | The domestic B2B mandate does not apply to invoices to consumers. |
| Public sector (B2G) | Separate rules | Federal and state rules apply. XRechnung and a Leitweg-ID can be required. |
| Small-value invoices up to EUR 250, tickets and other listed categories | Statutory exceptions | Check the current UStG and BMF FAQ for each transaction type. |
| Small business (Kleinunternehmer) | Special rules | Assess each entity against the current UStG and BMF FAQ. |
| Cross-border supplies, exports and imports | Requires verification | Not addressed in the source material used for this guide. Confirm with the current BMF FAQ and your tax adviser. |
Because the tests differ by legal entity and transaction, build a scoping register that lists each German entity, its turnover tier, its customer types and any exception it can claim. Review it each year when prior-year turnover is final.
Which Transaction Types Are Affected?
| Transaction type | Coverage | Operational note |
| Domestic B2B sales invoices | Mandatory by phase | Generate XRechnung, ZUGFeRD or another agreed compliant format after your deadline. |
| Domestic B2B purchase invoices | Receipt mandatory now | AP must accept, render, validate, post and archive structured files. |
| Credit notes and invoice corrections | Follow BMF guidance | The BMF has issued guidance on corrections. Confirm treatment against the current BMF letter before finalising templates. |
| Intercompany invoices | In scope when entities are separate domestic businesses | Apply the same entity-level scope test as external invoices. |
| Reverse charge and exempt supplies | Validate wording and tax codes | VAT rule validation should check exemption and reverse-charge wording. |
| B2C invoices | Out of scope | Retail, telecom and utility consumer billing is not covered. Their B2B invoices are. |
| B2G invoices | Separate regime | Maintain a distinct routing profile with Leitweg-ID where required. |
Accepted Formats: XRechnung, ZUGFeRD and EN 16931
The BMF names the XRechnung format and ZUGFeRD from version 2.0.1 (excluding the MINIMUM and BASIC-WL profiles) as common formats that satisfy the VAT requirements. The benchmark underneath is the European standard EN 16931. Other formats, including agreed EDI formats, can also qualify if the VAT information can be extracted correctly and completely and the statutory semantic requirements are met.
| Format | What it is | Key consideration |
| XRechnung | Pure XML invoice based on EN 16931. | It has no conventional visual layer, so users need a viewer. |
| ZUGFeRD (2.0.1 or later) | Hybrid file with a PDF view and embedded XML. | The structured data leads if it conflicts with the visual layer. The MINIMUM and BASIC-WL profiles do not qualify. |
| Other EN 16931 compatible or agreed EDI | Bilateral or industry formats. | Keep evidence that required VAT data is extractable. |
| PDF only | An “other invoice”. | Allowed only during the applicable transition, with recipient agreement. |
This reverses a common habit. For a ZUGFeRD invoice, validation and posting should use the structured content, and the PDF should act only as a presentation layer. Good practice for any format includes:
- Validate mandatory VAT fields and arithmetic before sending.
- Control XML namespace, version and profile handling, and regression-test it.
- Provide viewers so AP users can read XRechnung format files.
- Version your transformation rules so future EN 16931 or profile updates do not force an ERP redesign.
Compliance Model: No Clearance, Open Channels
Germany does not prescribe a single exchange network or tax authority portal for domestic B2B e-Rechnung. The BMF allows flexible channels such as email, portals, APIs or other agreed mechanisms. This differs sharply from clearance regimes. Compliance here depends on invoice format, invoice content and recordkeeping, not on pre-approval of every invoice by the tax authority.
That flexibility moves responsibility to trading partners and to enterprise architecture. Define supported channels, security standards, endpoint ownership, acknowledgments, duplicate handling and fallback processes. Avoid accepting uncontrolled XML through many mailboxes.
Because no government response exists, there is no clearance number or tax authority status to store. Your evidence trail is internal: the validation result, the transmission or receipt record, the approval record and the link to the accounting entry.
Inbound AP Readiness: The Most Urgent Control Area
The receipt duty has been live since 2025, so inbound AP is the most immediate priority. A mailbox satisfies only the minimum ability to receive. AP teams need a Germany e-Invoicing solution for receipt, validation, matching, tax review, approval, posting, payment and archive.
- Rendering: show readable views of XRechnung and XML without changing the structured source.
- Extraction: map supplier, invoice number, dates, lines, tax, bank and payment data, and references into AP.
- Matching: support PO and non-PO invoices, goods receipts and contract references.
- Exception handling: route invalid tax data, missing PO, duplicates and price or quantity variances to named owners.
- Retention: store the structured original for the full statutory period.
Outbound AR Readiness: Plan Against Your Deadline
Schedule outbound work against your own transition deadline, not against year-end. Large issuers should already be testing structured generation and recipient channel requirements. Smaller issuers should use 2027 to remove master data and process dependencies instead of postponing design.
Record customer capability in the customer master or routing layer: preferred format, channel, endpoint, B2G identifiers where relevant, and any bilateral EDI arrangement. If you use an agreed format instead of an XRechnung or a ZUGFeRD invoice, keep evidence that the required VAT information is correctly and completely extractable.
ERP and Integration Architecture for German e-Rechnung
Decouple source ERP logic from invoice format generation and channel delivery. A canonical invoice model can normalise output from SAP, Oracle, Dynamics and local billing tools, apply German VAT and business validations, and then generate XRechnung, ZUGFeRD or another agreed EN 16931 compatible format.
For inbound invoices, the same architecture should parse, validate and render the file, extract fields for AP, match purchase orders and goods receipts, and preserve the original. Central handling is especially valuable for multi-ERP groups, because Germany’s open channel model otherwise encourages many point-to-point integrations.
Tax Validation, Penalties and Non-Compliance Risk
Germany does not require clearance, but validation still matters. Incorrect structured VAT data can disrupt input VAT processing, customer acceptance and audit defensibility. The BMF recommends validation as a practical way to find missing or illogical mandatory data, even though using a specific validator is not itself a condition for tax recognition.
| Control | Purpose | Example |
| Schema and profile validation | Confirm the file conforms to the chosen syntax and profile. | XRechnung or EN 16931 validation. |
| VAT rule validation | Detect tax code and mandatory field errors. | VAT ID, tax amount, exemption or reverse-charge wording. |
| Commercial validation | Prevent operational rejects. | PO reference, payment terms, bank details. |
| Duplicate and idempotency checks | Prevent double posting or sending. | Supplier, invoice number, date and amount checks. |
Non-compliance carries two separate consequences under German law. Administratively, section 26a UStG treats non-issuance or late issuance of a required e-Rechnung, and failure to retain invoices for the statutory period, as an administrative offence with a fine of up to EUR 5,000 per violation. Commercially, and often with greater impact, a recipient who accepts a non-conforming invoice where a structured e-Rechnung was mandatory can lose the input VAT deduction until a compliant version arrives.
| Risk | Consequence | Mitigation |
| Treating PDF as an e-invoice | The PDF is an “other invoice”, not an e-Rechnung. | Generate and receive EN 16931 compatible structured data. |
| Mailbox-only buyer capability | Files arrive but stay manual. | Automate parse, validate, render, match, post and archive. |
| Scope set by VAT registration only | Misapplied domestic establishment test. | Use legal-entity and fixed-establishment rules. |
| Ungoverned channels | Duplicates and lost invoices. | Central intake, channel registry, idempotency controls. |
| Trusting the hybrid visual layer over XML | The structured part is authoritative. | Post and validate from structured content. |
| Missing or late compliant invoice after the transition | Fine up to EUR 5,000 per violation. | Automate format and deadline checks by issuer turnover tier. |
| Structured original not kept for 8 years | Fine up to EUR 5,000 per violation. | Immutable archive. Never overwrite the original during transformation. |
| Accepting a non-conforming inbound invoice | Input VAT deduction denied until corrected. | AP validation gate before posting. Return non-conforming invoices. |
Caution: fines and deduction rules depend on the facts of each case and on current BMF guidance. Confirm the position for technically defective invoices with your tax adviser before you set internal policy.
B2G vs B2B: Leitweg-ID and Public Sector Invoicing
German public sector e-invoicing follows separate federal and state rules. Do not mix it up with the domestic B2B VAT mandate. The BMF FAQ states that it is not the authority for B2G implementation. Public sector scenarios can require XRechnung and a Leitweg-ID or other routing details, depending on the recipient and jurisdiction.
Maintain a distinct B2G routing profile. A customer can sit in Germany and still require a public procurement specific path, with its own endpoint and metadata.
Archival, GoBD and Audit Evidence
Under section 14b UStG, businesses must keep a copy of each incoming and outgoing invoice for eight years. For e-invoices, at least the structured part must stay intact in its original form. The BMF also points businesses to the GoBD for wider electronic recordkeeping and data access principles.
A strong archive keeps the structured original, any readable rendition, the technical validation result, transmission or receipt evidence, the business approval record and the link to accounting entries. If you transform a file for downstream systems, never overwrite the received or sent original.
Related Mandates: VAT Returns, GoBD and ViDA
The invoice is now structured VAT data, so it connects directly to other compliance duties:
- VAT returns and reconciliation: clean structured invoice data supports reconciliation between invoices and returns.
- GoBD and record retention: the archive must meet both UStG and GoBD expectations.
- Audit trails: with no central clearance, your own send and receive evidence settles disputes and period-close questions.
- ViDA: the EU VAT in the Digital Age package points toward digital reporting and e-invoicing across the Union. Track German and EU developments, but do not assume a current German clearance or transaction-level reporting requirement. None exists in the 2025 rule.
Planning for a clean, well-governed invoice data layer now is the most reliable way to stay ready for later reporting changes.
Security and Business Continuity
Because Germany allows many channels, security risk is spread out. Email receipt needs malware and phishing controls, sender verification and safe XML handling. API or portal exchange needs authentication, access control, certificates or keys where applicable, and audit logs.
Business continuity plans should cover endpoint outages, partner channel outages, duplicate and resend behaviour, and late invoice processing. Without central clearance, internal proof of when an invoice was sent or received becomes critical.
e-Rechnung Germany Readiness Roadmap: 90 to 180 Days
| Phase | Priority actions | Exit criteria |
| 0 to 30 days | Classify entities and transactions. Inventory inbound and outbound channels. Confirm your 2027 or 2028 issuer deadline. | Scope and deadlines approved. |
| 31 to 60 days | Choose supported formats. Map ERP fields. Centralise receipt addresses and channels. Design the archive. | Format and channel architecture approved. |
| 61 to 90 days | Build inbound AP automation and outbound generation. Add validation and duplicate controls. | Core flows pass integration testing. |
| 91 to 120 days | Pilot with suppliers and customers across XRechnung, ZUGFeRD and any agreed EDI. | Counterparty UAT and posting evidence. |
| 121 to 180 days | Scale across entities. Monitor exception rates. Document B2G profiles and GoBD evidence. | Dashboards, SLAs and an audit pack. |
Readiness Maturity Model
| Stage | Characteristics | Typical evidence |
| 1. Receive only | A basic mailbox accepts e-invoice files. | No automated AP processing. |
| 2. Controlled | Central intake and archive. | Known channels, owners and retention. |
| 3. Integrated | ERP and AP ingestion plus outbound generation. | Field mappings, validators, interface logs. |
| 4. Operational | Multi-format, multi-channel UAT complete. | Low manual handling and monitored exceptions. |
| 5. Optimised | Continuous tax and reconciliation controls. | Automated validation, analytics, cross-country reuse. |
What Each Team Should Do Next
| Team | Next actions |
| CFO and Finance Controllers | Confirm your issuer wave by legal entity. Fund inbound automation first. Track exception rates and input VAT exposure. |
| Tax Heads and Compliance Officers | Maintain the scoping register and exception list. Confirm treatment of credit notes, cross-border cases and corrections. Align the archive with UStG and GoBD. |
| AP and AR operations | Replace mailbox handling with controlled intake. Record customer format and channel preferences. Define owners for each exception type. |
| ERP and IT leaders | Build a canonical invoice model, version transformation rules, secure every channel and set up monitoring and logging. |
How Cygnet.One Supports Germany e-Invoicing Readiness
Cygnet.One’s public Germany and global e-invoicing pages describe ERP integration, multi-format conversion, secure exchange, dashboards and multi-country support. The global platform supports 250+ ERP and accounting systems and connects through APIs, SFTP, files and pre-built connectors. It offers on-premises, private SaaS and cloud deployment options.
| Readiness layer | How Cygnet.One can contribute |
| ERP and source connectivity | Connect SAP, Oracle, Microsoft Dynamics and other ERP and accounting landscapes through APIs, SFTP, files and configurable connectors. |
| Data transformation | Normalise multiple source formats into a governed canonical invoice model, then map to jurisdiction-specific structured formats. |
| Validation and controls | Apply configurable schema, mandatory field and business rule validations before transmission or downstream posting. |
| Inbound and outbound operations | Support both AR and AP flows, with status visibility, exception handling and controlled reprocessing. |
| VAT and tax convergence | Use invoice data as a controlled base for VAT compliance, reconciliation and audit readiness where the local regime supports it. |
| Deployment and scale | Support on-premises, private SaaS and cloud patterns, designed for multi-entity and multi-country operations. |
Conclusion
The German rules reward early, structured preparation. Receipt capability is already required, issuance deadlines arrive on 1 January 2027 and 1 January 2028, and the absence of clearance puts the burden of control on your own ERP, AP, AR and archive processes. Enterprises that centralise intake, validate VAT data before posting and preserve the structured original will be ready for the deadline and for whatever reporting changes follow.
FAQ's
Partly. Since 1 January 2025, all domestic businesses must be able to receive E-Rechnungen. The obligation to issue them starts on 1 January 2027 for larger issuers and on 1 January 2028 for the rest.
A plain PDF is an “other invoice”. It can still be used with recipient agreement during the transition, which ends on 31 December 2026 for most issuers and on 31 December 2027 for issuers with prior-year turnover up to EUR 800,000.
It refers to prior-year turnover. Issuers above it must issue E-Rechnungen from 1 January 2027. Issuers at or below it have until 31 December 2027.
XRechnung and ZUGFeRD 2.0.1 or later (excluding MINIMUM and BASIC-WL) are the common choices. Other EN 16931 compatible or agreed formats can qualify if VAT data can be extracted correctly and completely.
No. The BMF states that no special receipt portal is mandatory, and an email inbox can be sufficient for basic receipt. Enterprise processing still needs far more than a mailbox.
No. Private consumers are outside the domestic B2B mandate.
Section 26a UStG allows fines of up to EUR 5,000 per violation for non-issuance, late issuance or failed retention. A recipient who accepts a non-conforming invoice can also lose the input VAT deduction until a compliant invoice arrives.
B2G follows separate federal and state rules. XRechnung and a Leitweg-ID can be required, depending on the recipient. x
Author
Kesha Shah
General Manager - Products Marketing
Kesha Kumar leads the global products marketing team at Cygnet.One, where she turns the complexity of tax and finance transformation into stories that resonate with the people who matter most. She’s the strategic force behind the brand’s presence across India, the GCC, Southeast Asia, and Europe, translating dense subjects like e-Invoicing mandates, digital engineering, and enterprise AI into narratives that inform and drive action. With expertise spanning tax and finance transformation, quality, enterprise applications, and data and AI, Kesha blends sharp strategic thinking with a marketer’s instinct for what truly connects. At Cygnet.One, she does more than build campaigns and content; she shapes the conversations that help enterprises navigate compliance with clarity and confidence, propelling the brand to the forefront of the industry along the way.