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)Since 2025
Every business must be able to receive e-invoices — no consent required
1 Jan 2027
Issuing mandatory for companies with turnover above €800,000
1 Jan 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.
What the Tax Administration Has Clarified
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.
What the Law Leaves Open
The transport channel, the format you agree with each partner, and whether you use a service provider at all.
What Good Looks Like
One outbound channel with delivery confirmation, one inbound channel that feeds invoice verification automatically, and validation on both.
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.
Which Channel for Which Partner
| Partner | Usual channel | Why |
|---|---|---|
| Public-sector customers | Peppol or the federal invoice portals | XRechnung is required, with the routing identifier they give you |
| Large corporate customers | Peppol, EDI or their portal | They dictate the channel; most are already automated |
| Mid-sized and small customers | ZUGFeRD by e-mail, or Peppol if reachable | Readable for their people, structured for their system |
| Suppliers (inbound) | One address per channel, feeding one queue | Several doors is what makes accounts payable manual |
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 — especially where the recipient is not yet automated and still wants to look at an invoice.
Pure XML, the German public-sector specification of EN 16931. No visual layer. Mandatory for invoices to federal public bodies; also used B2B by automated recipients.
The EN 16931-compliant format used on the Peppol network (pure XML). A channel-native format: what travels when you send through Peppol, at home and cross-border.
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.
Versions: Current, and What Is Coming
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.
How to Choose, in One Line Each
- Public-sector customers: XRechnung, with the routing identifier (Leitweg-ID) they give you.
- Automated B2B customers: the format their channel expects — usually Peppol BIS over Peppol, or XRechnung.
- Everyone else: ZUGFeRD in an EN 16931-compliant profile: compliant data for their system, a readable PDF for their people.
What to Ask Your Software and Service Providers
On Output
Which format and which profile do we actually produce, and can we set it per customer? Can we switch to newer versions without a project?
On Input
Do we read the embedded XML or the PDF? What happens to a file in a non-compliant profile? Is the validation result stored?
On Evidence
Where is the structured original archived, unchanged, and how quickly can we retrieve one invoice from 2025?
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.
How a Peppol Delivery Travels
- Your SAP: one outbound channel for all e-invoices.
- Your access point: format conversion, validation, delivery.
- The Peppol network: addressed routing, confirmations, a directory of participants.
- Your partner's access point: delivers into their ERP or portal.
Peppol Compared with the Alternatives
Why Groups Choose Peppol Anyway
- One connection covers Germany, public-sector customers and other countries' mandates.
- France's approved platforms use Peppol as their interoperability layer — the same channel serves both countries.
- ViDA's cross-border reporting from 2030 is expected to ride on the same standards.
- Deliveries are confirmed, addressed and traceable, which removes an entire class of disputes.
What to Clarify with a Provider
- Are you an access point, and which German and EU scenarios do you cover?
- Can you send ZUGFeRD to partners who are not on Peppol, from the same channel?
- How do you handle inbound invoices — delivery into SAP, or a portal we have to check?
- Which validations run before an invoice leaves, and what do we get as evidence?
Peppol in Four Words You Will Hear
| Term | What it means |
|---|---|
| Access point | Your connection to the network, usually provided by a service provider or by SAP. |
| Participant ID | The address of a company on the network — typically built from its VAT or company identifier. |
| Directory | Where you check whether a partner is reachable, and for which document types. |
| BIS document | The agreed document specification — the invoice format that travels on the network. |
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.
Outbound in Five Steps
This is the obligation with the deadline. From 1 January 2027 every domestic B2B invoice you issue must be a compliant e-invoice — which means your customer master data, your formats and your channels all have to be ready before the first invoice run of the year.
- Bill: invoice or credit note posted in SAP.
- Format: ZUGFeRD, XRechnung or Peppol BIS, per customer.
- Validate: structure and VAT content checked before sending.
- Send: Peppol, EDI, portal or e-mail — from one channel.
- Keep: structured file archived unchanged, with the validation result.
The Decisions Behind Those Steps
| Decision | What to settle | Why it matters |
|---|---|---|
| Format per customer | A default (usually ZUGFeRD in a compliant profile) plus exceptions for public-sector and automated customers | Sending a format the customer cannot process creates disputes, not compliance |
| Channel per customer | Peppol ID, EDI connection, portal or e-mail address, held in the customer master | This is master data now, not a note in someone's mailbox |
| Completeness of data | All mandatory VAT information inside the XML — including references, discounts and payment terms | Information only visible in the PDF layout does not count |
| Credit notes and corrections | Same format, same channel, referencing the original | A correction to an e-invoice must itself be electronic |
| Self-billing | Where your customer issues on your behalf, agree format and validation | The obligation still attaches to the supply, not to who types it |
| Archiving | The structured file, unchanged, for the statutory retention period, retrievable | A PDF copy is not the invoice; the data is |
Getting Customer Master Data Ready
Who Is in Scope
German-established business customers — the test is establishment, not just a VAT number.
Routing Data
Peppol IDs, EDI partner profiles, portal references, and the Leitweg-ID for public bodies.
Contacts
One invoice-receipt address per customer, owned by the master data team, not by sales.
Exceptions
Invoices under €250, exempt supplies and B2C — keep the rules in the system, not in people's heads.
A Migration Plan that Fits the Time Left
Public-sector customers and the largest automated customers
What to prove: format, routing identifiers and channel work end to end.
Top customers by volume and by revenue
What to prove: real files accepted and posted on their side, not just validated on yours.
The long tail, by default format
What to prove: master data complete; exceptions documented.
First invoice run under the obligation
What to prove: monitoring, rejection handling and a named owner in place.
A practical sequence for the last months of 2026: pick the default format, clean the customer master, switch your largest customers first (they are the most likely to reject non-compliant files), then move the long tail before the year-end close.
Inbound in Five Steps
Receiving has been mandatory since 2025, so this side is usually 'done' on paper and unfinished in practice. As suppliers switch during 2027, the volume of structured invoices arriving at your accounts payable team goes from a trickle to the default — and input VAT deduction depends on handling them properly.
- Arrive: Peppol, EDI, portal or e-mail — several doors today.
- Capture: read the XML, not the PDF; no re-keying, no OCR.
- Validate: format and mandatory VAT content checked and logged.
- Process: matched, approved and posted in invoice verification.
- Keep: structured original archived unchanged and retrievable.
What to Get Right — and What Goes Wrong
| Topic | What good looks like | Typical failure |
|---|---|---|
| One front door | A single inbound channel per format, feeding one queue in SAP | Invoices in three mailboxes, a portal and a supplier's e-mail to a buyer |
| The XML is the source | Postings are built from the structured data | The PDF is scanned while the XML sits unused in the attachment |
| Hybrid mismatches | PDF and XML compared; differences stopped and queried | Paying what the PDF says while the XML says something else |
| Incomplete profiles | Supplier invoices checked for a compliant profile on arrival | MINIMUM or BASIC WL files accepted as if they were invoices |
| Validation evidence | Validation result stored with the document | No record of what was checked when a question arrives years later |
| Archiving | The structured file kept unchanged for the statutory period | Only a print or a PDF rendering is kept |
| Duplicates | Duplicate detection on invoice number and supplier, across channels | The same invoice paid twice because it arrived twice, differently |
Questions Worth Asking Your AP Team This Quarter
- How many structured invoices did we receive last month, and what happened to the XML?
- If a supplier sends a compliant invoice today, does anyone have to touch it?
- Who checks that an incoming file is a valid e-invoice at all?
- What do we do when the PDF and the XML disagree?
- Can we produce the original structured file for any invoice from 2025 onwards?
- What is our plan for the wave of suppliers switching in January 2027?
What to Measure Once It Runs
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
Why This Side Carries the Money
Issuing badly is a compliance risk. Receiving badly is a cash and cost risk: blocked postings, missed discounts, duplicate payments and — once the transition ends — input VAT deduction resting on invoices your systems never properly captured.
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 and the Manage Electronic Documents app.
Format determination per customer: ZUGFeRD, XRechnung or Peppol BIS. Watch out: the ZUGFeRD profile your system actually produces.
Peppol through SAP BTP; e-mail, EDI or portal for the rest. Watch out: fallbacks that quietly bypass the monitor.
Incoming e-invoices into the cockpit, then invoice verification (MM, VIM or Ariba). Watch out: parallel PDF and OCR routes left running in production.
Peppol IDs, Leitweg-ID, VAT IDs, bank data, invoice-receipt addresses. Watch out: missing identifiers are the top cause of rejected files.
References, payment terms, discounts and delivery dates carried into the structured data. Watch out: information that exists only in the print layout.
Structured originals and validation results kept and retrievable. Watch out: archiving the rendering instead of the data.
Daily review of errors and rejections, with an owner. Watch out: a cockpit nobody opens after go-live.
SAP notes and the regulatory change tracker for new format versions. Watch out: treating the project as finished at go-live.
What Changes, by Role
A deadline with VAT consequences, and a cost question on both sides of the ledger. Decisions: channel strategy for the group, budget, sponsor, target automation rate.
Format compliance, corrections, archiving and input VAT evidence. Decisions: default format, validation policy, retention approach.
Customer master data becomes routing data; rejected files come back to billing. Decisions: migration sequence for customers before 1 Jan 2027.
Structured invoices replace PDFs; the XML drives the posting. Decisions: one inbound channel, duplicate control, exception handling.
DRC set-up, BTP connectivity, roles, testing and monitoring. Decisions: sequence — outbound for 2027, then inbound automation.
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, with SAP DRC delivery experience in France and Germany.
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 — with the group and other mandates in view.
Fit-gap against EN 16931 and the German rules
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. Validation, duplicate control, monitoring and exception handling built in from the start.
Partner testing before the 2027 cut-off
With real customers and suppliers, in migration waves. 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. Roadmap to the 2028 wave, other country mandates and ViDA reporting.
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.
Typical Deliverables
Gap & Risk List
Per entity and per process, with effort and owner.
Format & Channel Decision
Documented, with the group and other mandates in view.
SAP Design
Outbound, inbound, master data, validation, archiving.
Migration & Test Plan
Waves, partner tests and the evidence pack.
Founder-led
Finance + SAP DRC depth
SAP DRC delivery: France and Germany
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; process documentation. Independent review — whoever builds the solution should not certify it.
Design, build and run the SAP and channel solution for both sides. Produce the evidence auditors ask for: logs, validations, test results.
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.
What a First Conversation Needs from You
Entities
German entities, turnover and who is above the threshold.
Volumes
Customer and supplier invoices per month, and public-sector share.
Systems
SAP release, DRC status, current channels and any provider.
Pain Points
Where issuing or receiving is manual or failing today.
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. The 2026 revision of EN 16931 introduced ZUGFeRD 2.5 and XRechnung 4.0; earlier versions remain valid for domestic invoicing. SAP: SAP Document and Reporting Compliance documentation and community material on XRechnung, ZUGFeRD and Peppol. Scope, licensing and release details must be confirmed with SAP for your landscape.
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. 30 Advisory accepts no liability for decisions taken on the basis of this document.
Not Sure What This Means for Your SAP Landscape?
We'll map your issuing, receiving and channel strategy against the German mandate in our free 60-minute diagnostic.
Three things to check first
- Which entities cross €800,000 in prior-year turnover.
- Customer and supplier master data, including routing identifiers.
- That you can retrieve the originals of five recent invoices from the archive.
Want the full picture? Score your DRC readiness →