Germany should be approached differently from countries with a single tax-clearance platform. For B2B, the customer question is broader: can the organization receive, understand, process, archive, and later audit structured invoice data in a reliable way?
German e-invoicing discussions often involve EN 16931, XRechnung, and ZUGFeRD. These terms are important, but for SAP customers the bigger change is operational. Supplier invoices may arrive as structured data, finance users still need a readable view, and purchasing, invoice verification, posting, and archive processes must remain consistent.
B2B transmission: email and Peppol are channel choices
For German B2B e-invoicing, the key distinction is between the invoice format and the transmission channel. A compliant e-invoice needs structured data that can be electronically processed. The channel can be agreed between business partners. In practice, this can include email, ERP-to-ERP interfaces, portals, EDI-style paths, or Peppol.
Email can be a pragmatic starting point for receiving B2B e-invoices, as long as the attached invoice is structured, such as XRechnung XML or a compliant ZUGFeRD file. A plain PDF sent by email should not be treated as a compliant German e-invoice for post-2025 B2B readiness; it belongs to the category of other invoices during applicable transition periods.
Peppol is useful when a company wants a more standardized and automated exchange model, especially for recurring partners, cross-border rollout, or higher invoice volume. It should be positioned as an optional network channel for B2B automation, not as the only German B2B route.
Why receiving matters as much as issuing
Many projects first focus on outbound invoice generation. In Germany, readiness to receive and process structured invoices is just as important. If the organization can receive a file but cannot route it to the right process, interpret the data, visualize it for finance users, or connect it to invoice verification, the business benefit is limited.
A practical SAP roadmap
A practical roadmap starts with B2B scope, format scope, partner channel preferences, inbound mailbox or interface design, readable visualization, FI invoice verification, posting, and archive rules. Outbound generation can then be designed on the same foundation. This keeps the work business-led rather than turning it into a format conversion exercise.
Specific tax interpretation should be confirmed with local advisors. JRS focuses on SAP process readiness, B2B channel design, and integration governance.