The September 2026 E-Invoicing Deadline Is an ERP Problem, Not a Tax Problem

Three Months Until France Goes Live — And Most SAP Shops Are Not Ready

On 1 September 2026, every company operating in France must be able to receive electronic invoices through the state's Y-model architecture. On 1 January 2027, Germany's domestic B2B mandate follows. These are hard regulatory deadlines — and they are not, despite how most coverage frames them, primarily a tax compliance project. They are an ERP-readiness program that requires structural changes to master data, document flows, output management, and fiscal calendar configuration inside SAP S/4HANA.

The finance leaders I speak with — CFOs and Finance Directors running SAP at mid-to-large companies with French or German operations — consistently describe the same situation: IT has been assigned the mandate project, and Finance has been asked to "provide requirements." This is backwards.

Why the E-Invoicing Mandate Is an ERP Problem

France's architecture (the "Y-model") separates invoice data exchange from tax reporting. Certified Private Dematerialisation Platforms (PDPs) — of which SAP Document and Reporting Compliance Cloud is one — exchange invoices between businesses and transmit structured data to the public PPF portal (Chorus Pro). Germany uses a simpler model based on ZUGFeRD 2.1+ or XRechnung, with PEPPOL as the dominant transport layer.

From an SAP perspective, both mandates demand the same fundamental capabilities: an output management pipeline that can generate structured XML payloads for every invoice document type; correctly configured master data with SIRET, VAT IDs, and Leitweg-IDs; and a fiscal calendar synchronised with the company's declared VAT filing frequency. None of these are "tax configuration" in the sense of SAP FI-FC or VAT reporting. They are core ERP process configuration — document routing, output control, and data quality across all financial objects.

The distinction matters because of how organisations staff and budget these projects. A compliance project gets a tax manager and a two-week assessment. An ERP-readiness program needs an SAP architect, a finance process owner, and a three-to-nine-month implementation window with a dedicated budget line.

The Trap of Deadline Softening

May 2026 brought fresh activity around the French mandate. Tax authorities softened the language around immediate penalty enforcement, and the ASP/service-provider appointment deadline shifted to October 2026. This has been widely interpreted as another delay in the making — following the pattern of 2022-to-2024 and 2024-to-2026 postponements.

That reading is dangerously wrong. The previous delays were caused by PPF infrastructure unreadiness and PDP certification backlogs — government-side bottlenecks. Those specific causes are resolved. The PPF pilot has been running live transactions since February 2024, and approximately 75 PDPs were certified as of Q1 2026. The bottleneck today is not government infrastructure; it is enterprise readiness.

Three months is a very short window for an SAP DRC implementation, which typically runs four to nine months including testing. Any company that has not scoped this project by June 2026 is structurally late for a September go-live. The softening is a perception trap: finance teams cite the delay history to justify waiting, but the conditions that caused those delays no longer exist. The window is compressing, not expanding.

Where These Projects Actually Stall

Five failure points appear consistently when companies approach this as an activation task rather than a structural overhaul.

1. SAP Release Incompatibility

SAP Document and Reporting Compliance requires S/4HANA 2021 or later with specific Support Package levels. ECC 6.0 and early S/4HANA releases (1709, 1809) are not directly compatible. Companies still on these releases face a choice: upgrade their core ERP, or deploy a hybrid DRC cloud deployment that bridges the gap. Either option adds months to the timeline. The most common response from IT — "DRC is not compatible with our current release" — is a genuine technical constraint, not foot-dragging. Finance leaders hearing this need to escalate to the CIO immediately for a go/no-go decision on the upgrade path.

2. Legacy Output Management Not Decommissioned

This is the most insidious gap. Post-migration S/4HANA systems often still route some invoices through legacy SAPScript or SmartForms for specific document types. These outputs look correct as PDFs but generate no XML payload for the PDP. The invoice goes to the customer as an email attachment — compliant to human eyes, non-compliant to the mandate. Finding and remediating these hidden flows requires a systematic audit of condition records and output type configurations, typically done with SAP Signavio or equivalent process mining. It is not a task that can be discovered during a two-week gap assessment.

3. Credit Notes, Reversals, and Corrections

Most test teams validate new outbound invoices only. Storno documents, reversal postings, and credit memos frequently fail on XML mapping in parallel runs. The e-reporting schema requires specific handling for negative amounts, correction indicators, and reference to the original invoice. If these scenarios are not tested before go-live, the first correction cycle creates a compliance exception that triggers manual remediation.

4. Inter-Company Invoice Coverage

Sister entities that bill the French entity must also be PDP-connected under the Y-model. For multinational groups, inter-company invoices can account for 20 to 40 per cent of total invoice volume. Companies that configure only their external customer flows discover this gap during user acceptance testing, when internal billing documents begin arriving as non-compliant PDFs from entities that were never included in the project scope.

5. Master Data Coverage Gaps

France requires the 14-digit SIRET identifier in the customer or vendor master for every French trading partner. Companies with more than 100,000 records typically show 15 to 30 per cent SIRET coverage gaps. Similar gaps exist for German VAT IDs and Leitweg-IDs. Master data enrichment at this scale is a multi-month data stewardship exercise that cannot be compressed into the final weeks before go-live. SAP Note 3345614 (2024) provides the field mapping, but it cannot fix missing data.

What Finance Leaders Should Own Today

These are the decisions that belong to Finance, not IT, and that cannot be delegated safely:

• Invoice scope declaration: Which legal entities, document types, and transaction flows are in scope? IT cannot determine VAT-relevant flows — this requires a finance process owner who knows the chart of accounts and transaction tax treatment.
• VAT filing frequency alignment: Confirm the declared VAT cadence (monthly, quarterly, or annual) per legal entity. This drives e-reporting cycles under the French model and must match the S/4HANA company code fiscal variant exactly.
• Master data audit: Commission a SIRET coverage check on all French trading partner masters. Target 100 per cent before September 2026. This is a data quality exercise, not a technical one — it needs commercial teams to source missing identifiers.
• PDP selection and contracting: Finance selects the PDP (or confirms SAP DRC Cloud as PDP). This involves procurement, legal review, and budget allocation. PDP fees range from approximately 15,000 to 100,000 EUR or more per year depending on invoice volume.
• E-reporting content review: The 24-field dataset transmitted to DGFiP includes payment terms, amounts, VAT breakdowns, and customer references. Finance approves what is transmitted — this is a tax exposure decision, not an IT configuration parameter.

For companies without a contracted PDP by July 2026, the Chorus Pro portal is available as a free fallback for receiving mandated inbound invoices. Outbound transmission will still require a PDP-connected flow or manual portal upload — neither is scalable at volume. It is a compliance floor, not a solution.

The Real Deadline Is Organisational, Not Technical

The September 2026 e-invoicing mandate is a test of organisational readiness, not technical capability. The SAP DRC configuration is well-documented. The PDP integrations are proven. The challenge is scope ownership: who in the organisation is accountable for determining what needs to be e-invoiced, ensuring the master data supports it, and validating that the transmitted dataset is correct.

Finance leaders who treat this as an ERP-readiness program — and assert ownership of the non-delegatable decisions — will be compliant by September. Those who treat it as an IT-led tax project will discover the gaps in August, when there is no time left to fix them. The deadline is real, the window is closing, and the work is fundamentally about how finance operates inside SAP, not about configuring a new tax code.