Germany's B2B e-Invoicing Mandate: ZUGFeRD, Peppol and the 2027 Deadline
Receiving has been mandatory since January 2025. Issuing becomes mandatory on 1 January 2027 for most companies. What that means for the invoices you send, the invoices you receive, and your SAP landscape.
Client briefing · September 2026 · CFOs, Finance, PMs
Download Full Briefing (PDF, EN)Since 2025
Every business must be able to receive e-invoices — no consent required
1 ene 2027
Issuing mandatory for companies with turnover above €800,000
1 ene 2028
All remaining businesses; the EDI transition ends
2 formats
ZUGFeRD and XRechnung — plus Peppol BIS as a channel format
Key takeaway for finance leaders: the freedom is the trap. Because Germany mandates no platform, most companies did the minimum in 2025 — an inbox that accepts XML — and left the rest. With 1 January 2027 just over three months away, the open questions are which format you send to which customer, how supplier invoices get into the system without manual re-keying, and whether the structured file you archive is the one that counts.
What the Law Changed
The Growth Opportunities Act (Wachstumschancengesetz) rewrote the invoice definition in German VAT law. From 2025 there are two categories: the e-invoice (structured, EN 16931-compliant, machine-readable) and the 'other invoice' — paper, PDF, image, anything else. For domestic B2B supplies between German-established businesses, only the first category will satisfy the law once the transition ends.
What has not changed: there is no state platform, no registration, no approval of service providers and no obligation to report invoice data to the tax administration. Germany deliberately separated the format reform (now) from a reporting system (expected with the EU's ViDA package, around 2030 and later).
E-invoice definition applies; receiving is mandatory for everyone
Transition: paper and PDF still allowed for issuing, with the customer's agreement
Issuing mandatory where prior-year turnover exceeds €800,000
All remaining businesses; EDI arrangements must also meet the standard
EU-wide digital reporting under ViDA; a national reporting system is expected to follow
Obligations
All domestic businesses — including small ones and landlords with VAT-taxable supplies — must be able to receive e-invoices today. Turnover above €800,000 in the prior year: must issue from 1 Jan 2027. Everyone else: from 1 Jan 2028. Small businesses under the VAT small-business scheme are exempt from issuing — but must still receive them.
Out of Scope
Invoices up to €250 (small-amount invoices) and travel tickets. Certain VAT-exempt supplies (financial services, insurance, health, education, property). B2C invoices, and supplies where the customer is not established in Germany — these follow the other country's rules.
In a hybrid file the XML is decisive. If the PDF and the XML disagree, the XML is the invoice — and the difference is a compliance problem.
All mandatory VAT information must be inside the structured data, not only in an attached delivery note, contract or PDF layout.
A correction to an e-invoice must itself be electronic and structured.
Both outgoing and incoming invoices should be validated, and the result documented — it is the evidence that you exercised due care.
Once the transition ends, deduction rests on receiving a proper e-invoice with complete information in the structured data.
How a German e-Invoice Travels
There is no prescribed route. The law governs the content and format, not the channel — so the decision you actually have to make is which channel gives you control, proof of delivery and automation on both sides.
Addressed delivery between access points, with confirmations.
Established partners; must meet the standard from 2028.
Upload or download, often imposed by large customers.
Legally sufficient — operationally the weakest option.
What the Law Requires
A structured invoice meeting EN 16931, complete VAT information in the data, and an unchanged structured file kept for the statutory retention period.
Why 'E-mail Is Enough' Is Expensive
An e-mail inbox satisfies the letter of the law, and the tax administration has said so. It gives you no delivery confirmation, no addressing standard, no duplicate control and no straight-through processing — so the cost moves from the project budget to the accounts payable team, every day, invoice by invoice.
Germany in Context
ZUGFeRD, XRechnung and Peppol BIS
Three names, one European standard underneath. They differ in what a human can see, who mandates them, and how they travel.
= Factur-X in France. A hybrid file: a PDF a person can read, with the structured XML embedded inside it. One file, two audiences. For B2B customers of every size.
Pure XML, the German public-sector specification of EN 16931. No visual layer. Mandatory for invoices to federal public bodies.
The EN 16931-compliant format used on the Peppol network (pure XML). A channel-native format: what travels when you send through Peppol.
ZUGFeRD Profiles: the Detail that Decides Compliance
Only booking-level data — not a complete invoice.
Header data without invoice lines.
Simple invoices with lines, a subset of the standard. Valid for simple cases.
The full European standard — the usual target.
Adds industry and cross-border detail beyond the standard.
The XRechnung specification inside a ZUGFeRD container.
Many accounting tools still default to MINIMUM or BASIC WL because it is enough to book an invoice. Check what your systems actually produce — and what your suppliers send you.
Still Valid
XRechnung 3.x and ZUGFeRD 2.3 / 2.4 remain valid for domestic invoicing. Nothing you send today becomes invalid on 1 January 2027.
The 2026 Revision
EN 16931 received its largest update since 2017 — more business terms, designed to be ready for ViDA reporting.
New Releases
ZUGFeRD 2.5 (mid-2026) implements the new standard; XRechnung 4.0 follows for the public sector. Plan an upgrade path, not a rush.
Peppol: the Channel Germany Did Not Mandate
Peppol is an international network for exchanging business documents. You connect once to an access point, your partners connect to theirs, and documents travel between them using agreed formats and addresses — like e-mail, but with identity, structure and delivery confirmation. Germany uses it for public-sector invoicing and it is spreading through B2B.
A Common Trap
The realistic German set-up: most companies end up with a channel mix — Peppol for partners who are reachable there and for the public sector, EDI where it already runs, and ZUGFeRD by e-mail as the fallback for the long tail of smaller customers and suppliers. The goal is not one channel — it is one place in SAP where all of them are visible.
Invoices You Issue, Invoices You Receive
Issuing and receiving have different deadlines, owners and failure modes. From 1 January 2027 every domestic B2B invoice you issue must be a compliant e-invoice; receiving has been mandatory since 2025, and volume will jump sharply as your suppliers make the transition.
Format and channel per customer, held in the customer master. Completeness of VAT data inside the XML. Corrections and credit notes in the same format and channel. Archiving of the structured file, unchanged, for the statutory period.
Read the XML, not the PDF, to post. Compare PDF and XML in hybrid files and stop discrepancies. Check the ZUGFeRD profile on arrival. Duplicate control across channels.
A Migration Plan that Fits the Time Left
Public-sector customers and the largest automated customers
Top customers by volume and by revenue
The long tail, by default format
First invoice run under the obligation
Structured Share
Percentage of supplier invoices arriving as valid e-invoices
Touchless Rate
Invoices posted without anyone opening them
Exception Ageing
How long blocked or invalid invoices sit before resolution
Days to Post
From arrival to posting — protects early-payment discounts
Impact on SAP
SAP Document and Reporting Compliance (DRC) covers Germany: it creates the electronic invoice from the billing document, produces XRechnung or ZUGFeRD, connects to Peppol through SAP Business Technology Platform, and shows every document and its status in one monitor — the eDocument Cockpit.
Format determination per customer: ZUGFeRD, XRechnung or Peppol BIS.
Peppol through SAP BTP; e-mail, EDI or portal for the rest.
Incoming e-invoices into the cockpit, then invoice verification (MM, VIM or Ariba).
Peppol IDs, Leitweg-ID, VAT IDs, bank data, invoice-receipt addresses.
Structured originals and validation results kept and retrievable.
Daily review of errors and rejections, with an owner.
What Changes, by Role
A deadline with VAT consequences, and a cost question on both sides of the ledger.
Format compliance, corrections, archiving and input VAT evidence.
Customer master data becomes routing data; rejected files come back to billing.
Structured invoices replace PDFs; the XML drives the posting.
DRC set-up, BTP connectivity, roles, testing and monitoring.
Lessons from SAP e-Invoicing Projects
Master data first. Most rejected invoices trace back to a missing identifier or address. Stay on standard. Custom conversions age badly — new format versions arrive regularly. Plan roles and connectivity early; they delay more projects than mapping does. Test with real partners, not only with sample files. Close the side doors — every bypass channel becomes an audit finding. One design, several countries. Germany, France and Spain share the same building blocks.
How 30 Advisory Can Help
A founder-led boutique specialised in SAP DRC & e-invoicing compliance, S/4HANA Finance optimisation and CFO/CIO strategic advisory, delivering across European mandates.
Readiness assessment for both sides
What you issue today, what you receive, and where each stands against 2027. Format and channel strategy: ZUGFeRD as default, XRechnung where required, Peppol where it pays.
Fit-gap against EN 16931
Customer and supplier segmentation by channel. Finance design: billing content, master data, corrections, validation and archiving.
SAP DRC implementation and Peppol connectivity
SAP DRC implementation and configuration, Peppol connectivity through SAP BTP, inbound automation into invoice verification.
Partner testing before the 2027 cut-off
Training for AR and AP teams, operating procedures and an evidence pack for auditors.
Ongoing monitoring and roadmap to 2028
SAP notes, new format versions (ZUGFeRD 2.5, XRechnung 4.0), KPIs and hypercare.
Short on Time Before 2027?
A focused four-week assessment gives you the gap list, the format and channel decision, and a migration plan for your largest customers — enough to protect the January invoice run.
Founder-led
Finance + SAP DRC depth
Multi-country: Italy, Turkey, Spain
Boutique agility
Roles, Key Dates and Next Steps
The State does not certify your software or your processes. Proving that your invoicing, reporting and archiving are compliant remains your responsibility.
Scope and exemptions, VAT treatment, input VAT and correction rules.
Retention requirements and the audit-proof archive. Controls over validation, completeness and archiving.
Design, build and run the SAP and channel solution for both sides. Produce the evidence auditors ask for.
Key Dates
Receiving mandatory for every domestic business
Issuing mandatory where prior-year turnover exceeds €800,000
All remaining businesses; EDI must meet the standard
France: SMEs must issue (relevant for groups with French entities)
Spain: B2B mandate starts for companies above €8M turnover
EU ViDA digital reporting; a German reporting system is expected to follow
Next Steps
1. Confirm which entities cross the €800,000 threshold — the test is prior-year turnover, per entity. 2. Decide the default format and channel, and where Peppol earns its place. 3. Clean customer and supplier master data, including routing identifiers. 4. Automate the inbound side so 2027 volumes do not land on the AP team. 5. Prove archiving and validation — pick five invoices and try to produce the originals. 6. Plan the 2028 wave and the new format versions as a recurring cycle, not a project.
Three Questions We Get Asked Most
Only where the customer is out of scope, the invoice is exempt or under €250, or your entity is still in the 2028 group.
Not legally. In practice, one is what gives you Peppol reach, delivery evidence and one channel instead of four.
Yes, in a compliant profile — provided the structured data is complete and matches the PDF a customer reads.
Mandate: German VAT law as amended by the Growth Opportunities Act; Federal Ministry of Finance guidance and FAQ on the e-invoice (including the October 2025 letter on hybrid formats, validation and input VAT); IHK and practitioner summaries of the transition periods and exemptions. Formats: FeRD/FNFE specifications for ZUGFeRD and Factur-X; KoSIT XRechnung specification; Peppol BIS Billing. SAP: SAP Document and Reporting Compliance documentation and community material on XRechnung, ZUGFeRD and Peppol.
Prepared by 30 Advisory, September 2026. Information only — not legal or tax advice. Thresholds, exemptions and retention periods depend on your circumstances; confirm them with your tax advisor.
Not Sure What This Means for Your SAP Landscape?
We'll map your issuing, receiving and channel strategy against the German mandate in a 1-hour diagnostic session.
Schedule Assessment (1 hour)