[BRIEF] The European E-Invoicing Avalanche: France is Live, Spain is Next

This is an Architecture Brief—a high-level overview of market changes and system requirements. For step-by-step system configurations and SPRO guides, explore our Deep Dives.

If your SAP SD architecture relies on generating PDF invoices via standard email output (NAST or BRF+), you are already falling behind. The pan-European rollout of Continuous Transaction Controls (CTC) is aggressively expanding, forcing companies to implement SAP Document and Reporting Compliance (DRC) to survive.

Here is the current architectural reality across Europe:

• France (Live Now): As of September 1, 2026, e-invoicing (and e-reporting for B2C/cross-border) is strictly mandatory for all large and intermediate-sized enterprises. Small businesses follow in September 2027.
• Spain (Timelines Locked): The long-delayed Ley Crea y Crece has finally received its implementing Royal Decree (238/2026). Mandatory B2B e-invoicing kicks off in October 2027 for large companies, with the rest following in October 2028. Additionally, the VeriFactu (invoice verification) system mandates start on January 1, 2027.
• Germany (Sending Mandate Approaching): While receiving e-invoices has been mandatory since January 2025, the strict mandate to send structured formats (ZUGFeRD/XRechnung) for companies over €800k turnover hits in January 2027.
• Poland (Live): The KSeF system became mandatory for all VAT-registered businesses in April 2026.

Applicable Systems: SAP S/4HANA Cloud, SAP S/4HANA On-Premise, SAP ECC (via DRC add-on).

[SCOPE BOUNDARY: WHO ACTUALLY NEEDS THIS?] Do not assume this is a localized finance problem. If your sales organization creates Outbound Deliveries and subsequent Billing Documents (VF01/VF04) for B2B customers in any of these jurisdictions, your Output Management architecture must be fundamentally redesigned.

[THE ARCHITECTURE] The era of point-to-point EDI connections for each country is over. The only scalable architecture for multinational rollouts is:

1. The Core: EDOC_COCKPIT (eDocument Cockpit) becomes the central hub, replacing the traditional VFX3 transaction for invoice monitoring.
2. The Mapping: Application Interface Framework (AIF) maps the core billing index (VBRK/VBRP) to the local XML requirements (e.g., Factur-X for France, UBL, or local formats).
3. The Transmission: SAP Integration Suite (via Peppol Exchange or local direct APIs) handles the handshake with national platforms (like the French PPF/PDPs).

[TRENCH NOTE] The biggest architectural mistake SD consultants make is treating e-invoicing as just an "XML export." It is a two-way street. Your SAP system must be able to ingest tax authority responses (e.g., "Invoice Rejected") and update the billing document status in real-time. Do not decouple this logic to a third-party black-box provider, or your SD flow will lose synchronization with reality.

Want the full picture? This update is just one piece of our massive 2026 SAP Architecture Radar. We’ve compiled 17 critical changes across FI, SD, EWM, and TM that every Solution Architect must know this year. Drop your email below to unlock the full 2026 Radar report.