France E-Invoicing for SAP: DRC, PA and Integration Options
How should SAP teams prepare for France e-invoicing?
SAP teams preparing for France e-invoicing should confirm legal-entity scope, inbound and outbound flows, e-reporting, PA responsibilities, source-data gaps, lifecycle statuses and exception handling. The choice between SAP DRC, SAP’s PA service, third-party PA integration and any confirmed extension requirement should follow an evidence-based fit-gap review of the actual SAP landscape.
Determine the right France e-invoicing path for your actual SAP landscape. We assess standard SAP DRC, SAP’s PA service, third-party plateforme agréée (PA) integration and any confirmed extension requirements against your FI and SD processes.
- SAP ECC / S/4HANA release & edition check
- FI & SD document-flow review
- PA connectivity, PA-to-PA routing, statuses & e-reporting
Book a 20-minute France SAP readiness call
We review your SAP release and current architecture, then identify the next technical decision for your France scope.
Key date
1 Sep 2026
All in-scope businesses must receive. Large enterprises and French intermediate-sized enterprises (ETIs) must also issue electronic invoices and submit required e-reporting data.
Key date
1 Sep 2027
The issuing and e-reporting obligations extend to SMEs and micro-enterprises.
At a glance
- Mandate: B2B e-invoicing + e-reporting
- Scope: In-scope domestic B2B transactions between France-established VAT-taxable persons; transaction e-reporting for B2C and transactions with foreign operators; payment / collection e-reporting where required
- Core formats: UBL, CII and Factur-X; supported issuance and receipt formats must be confirmed against the selected PA and SAP scenario
- Platform / channel: plateforme agréée (PA), formerly / commonly referred to as PDP
- Authority: DGFiP
- SAP scope: SD billing, FI invoices, tax codes, customer/vendor or business partner master data, SIREN/SIRET and VAT IDs
2-minute SAP readiness check
How prepared is your SAP landscape for France e-invoicing?
Answer seven questions to identify the next decision your France programme should make. You will receive the result immediately.
No email required. Individual answers are not sent to analytics.Your directional result
Items to confirm before commitment
This self-check is directional. It does not confirm legal scope, SAP compatibility, PA availability or production readiness. Those require current official specifications and customer-system evidence.
Which SAP architecture path fits?
| Your situation | Likely path | Why it matters |
|---|---|---|
| Standard S/4HANA, supported process, SAP route acceptable | SAP DRC review | Fastest standardization path; use the standard where it fits |
| SAP ECC or older enhancement package | Technical fit-gap required | Compatibility and extraction can block a clean rollout |
| Custom SD billing / feeder systems | Extension assessment | Confirm whether standard extraction covers the actual document flow |
| Multi-country SAP compliance roadmap | DRC architecture review | Avoid duplicated, country-by-country builds |
| Provider choice / existing PA partner | Connector assessment | Routing, statuses and ownership must be clear |
| Inbound AP + outbound AR + e-reporting | End-to-end process design | France is not only invoice XML generation |
Not sure which path fits your SAP landscape? Get a fit-gap recommendation →
France mandate impact
The Compliance Challenge in France
France is not introducing a simple invoice-format change. From 1 September 2026, the reform changes how B2B invoices are issued, received, routed, reported and monitored.
1 Sep 2026
All in-scope businesses must be able to receive electronic invoices. Large enterprises and French intermediate-sized enterprises (ETIs) must also issue electronic invoices and submit required e-reporting data from the first wave.
1 Sep 2027
The issuing and e-reporting obligations extend to SMEs and micro-enterprises.
Approved platform route
In-scope domestic B2B invoices flow through a plateforme agréée (PA; formerly PDP).
Structured formats
France’s core semantic formats include UBL, CII and Factur-X. The formats supported for issuance and receipt must be confirmed against the current specifications, the selected PA and the supported SAP scenario.
What changes for SAP teams?
- Master data quality becomes critical: SIREN/SIRET, VAT IDs, buyer and supplier details.
- SD billing and FI invoice flows need mandate-ready mapping.
- Tax codes, invoice type codes and VAT categories must be aligned with the approved platform requirements.
- Inbound supplier invoices and returned lifecycle statuses must be processed inside the operating model.
- Audit evidence, payload history and monitoring need to be traceable from the SAP source document.
Why it matters
A compliant France flow is not “generate XML and send”. It must handle platform routing, transaction and payment e-reporting, validation errors, inbound invoices, lifecycle statuses and audit evidence.
How the France model works
In practice, the supplier sends an in-scope domestic B2B invoice to its chosen plateforme agréée (PA). The supplier’s PA validates and routes the invoice to the buyer’s PA using the central directory. The buyer’s PA then makes the invoice available to the recipient. The Portail Public de Facturation (PPF) provides the central directory and concentrates the regulatory data transmitted by PAs to the tax administration; it is not the business-to-business invoice exchange channel.
Alongside e-invoicing, France also requires e-reporting. Transaction e-reporting covers operations outside domestic B2B e-invoicing, such as B2C sales and transactions with foreign operators. Payment / collection e-reporting may also apply where VAT becomes due on collection, especially for service-related flows. Our companion readiness guide to B2B e-invoicing in France and the country mandates overview cover the phased deadlines and the other jurisdictions we track.
SAP implementation approach
How S4FN Supports This in SAP
We assess the standard path first. Where SAP DRC and SAP’s PA service support the customer scenario, we use that route. Where a confirmed gap remains, we define the required third-party PA integration, SAP-native extension or SAP Business Technology Platform integration.
DRC fit-gap review
We check SAP release, edition, SD/FI document flows, e-reporting scope, inbound requirements and the selected PA route. This is our SAP DRC Architecture & Readiness Assessment.
SAP-native extension
Where a confirmed gap requires an SAP-native extension, its scope and deployment model are defined against the customer’s release, document flows and change-control requirements. Modifications to SAP standard objects are avoided wherever possible.
Mapping and validation
The implementation scope can include mapping SAP billing and accounting documents to invoice type codes, VAT categories, units of measure, tax codes and France-specific master-data requirements.
PA connectivity
PA connectivity is configured for the selected provider and confirmed SAP architecture. Additional provider routes are assessed where required.
Monitoring and errors
Validation can check SIREN/SIRET, VAT IDs, tax-code mappings, invoice type codes and required master data before transmission. Platform rejections remain visible in the agreed monitoring flow.
Inbound and audit trail
Depending on the confirmed scope, inbound invoices, returned lifecycle statuses, generated payloads, status history and applicable Factur-X documents can be linked to the originating SAP process.
The target operating model gives finance and IT visibility into document generation, transmission, rejection and processing, with evidence traceable to the relevant SAP source document. This follows the in-system pattern described in our SAP integration architecture.
Technical scope
SAP Compatibility & Technical Scope
The technical review covers SAP source documents, PA connectivity, lifecycle status handling and operational monitoring. It confirms whether the landscape should use standard SAP DRC and SAP’s PA service, a third-party PA connector, an SAP-native extension or SAP Business Technology Platform integration.
Deployment model
Where an ABAP extension is required, it can run inside the customer’s SAP landscape. Repository, retention and archiving requirements are confirmed during technical design.
SAP releases
Targeted for SAP S/4HANA landscapes. SAP ECC compatibility is assessed separately against the customer’s enhancement package, support package level, installed components and document-flow scope.
Source documents
Outbound invoices can be built from SD billing documents and FI invoices, depending on the customer’s process design and posting model.
DRC alignment
SAP DRC is used where standard coverage fits. An SAP-native add-on, connector or BTP extension is added only where custom flows, ECC constraints, provider choice or e-reporting scope require it.
Outbound formats
France’s core formats include UBL, CII and Factur-X. The supported outbound and inbound formats are confirmed against the current specifications, selected PA and SAP delivery scope.
PA connectivity
The selected PA connector, authentication method and routing model are confirmed during technical design. Additional provider routes are assessed where required.
Direction
Supports outbound issuance and inbound receipt scenarios, including supplier invoices and platform notifications where included in scope.
Status handling
Where included in scope, platform lifecycle statuses are written back or linked to the relevant SAP source document for operational monitoring.
Validation & errors
The validation and monitoring design defines how missing master data, unmapped tax codes, invoice type issues and platform rejections are surfaced.
E-reporting scope
Transaction e-reporting and payment / collection e-reporting are checked against the customer’s VAT, SD and FI processes during technical review.
Deployment topology
Integration can run in-system, through SAP Integration Suite on SAP Business Technology Platform, or through a selected PA connector, depending on the landscape.
Fit-gap output
The review produces a clear recommendation: use standard DRC, extend with an SAP-native add-on, connect to a selected PA, or combine the standard path with BTP-based integration.
What we confirm before implementation
- SAP release, edition, enhancement package and support package level
- SD billing, FI invoice and feeder-system document flows
- Inbound invoice scope and lifecycle status requirements
- Selected plateforme agréée (PA) and connectivity route
- Transaction and payment e-reporting obligations
- Monitoring, audit evidence and operational ownership model
Security and control
Security & Data Handling
The target architecture keeps SAP as the system of record and exchanges only the invoice, reporting and lifecycle-status data required by the selected PA and confirmed process scope.
SAP remains the control point
The implementation is designed to link source invoices, relevant master-data references, generated payloads and status history to the originating SAP process. The exact storage and monitoring model is confirmed during technical design.
Authorization follows SAP roles
Access to monitoring, configuration and processing follows the customer’s SAP authorization model. Compliance configuration remains under the customer’s change-control and transport-management process.
Secure outbound connectivity
Connectivity to the approved platform uses SAP-supported secure communication patterns, with encrypted transport and token- or certificate-based authentication depending on the customer landscape and provider requirements.
Credentials are not hard-coded
Provider credentials, certificates and technical connection settings are handled as configuration and protected through the customer’s SAP security setup, rather than being embedded in application code.
Audit evidence is traceable
The audit design defines how generated payloads, returned lifecycle statuses, error messages and applicable Factur-X documents are retained or linked so evidence can be traced from SAP.
Retention and data residency are confirmed
Retention periods, archiving approach, data-residency requirements and detailed authorization design are confirmed during the technical review, together with the selected PA provider.
Clear responsibility boundary
S4FN builds and integrates the technical channel between SAP and the approved platform. The customer’s finance and tax teams remain responsible for tax determination, invoice content, reporting scope and final compliance with the French mandate.
France SAP e-invoicing FAQ
Is SAP DRC enough for France e-invoicing?
Often yes for supported S/4HANA scenarios. SAP is a validated plateforme agréée in France, and SAP DRC connects supported SAP processes to SAP’s compliance and PA services. The required components, licensing and integration path depend on the SAP release, edition, document flows, e-reporting scope and provider choice.
Do we need a PA if we use SAP?
Yes. France’s model requires in-scope domestic B2B invoices to pass through a plateforme agréée (PA; formerly PDP). SAP is a validated PA in France. SAP DRC connects supported SAP processes to SAP’s compliance and PA services, while the exact components and integration path depend on the customer scenario.
Can this work with SAP ECC?
Yes, but ECC should not be treated as a standard assumption. SAP ECC compatibility depends on the customer’s enhancement package, support package level, installed components, document types and custom billing/accounting flows. We confirm the path during technical review and recommend standard DRC, an add-on, a connector or a BTP extension accordingly.
Does the solution cover inbound supplier invoices?
France requires receiving as well as issuing. Depending on the confirmed implementation scope, the SAP-native extension can support inbound invoice handling, PA notifications and lifecycle-status linkage to the relevant SAP process.
Does France require Factur-X, UBL or CII?
France’s core semantic formats include UBL, CII and Factur-X. Factur-X is a hybrid PDF with embedded XML, while UBL and CII are XML formats. The formats available for issuance and receipt must be confirmed against the current specifications, selected PA and supported SAP scenario.
What is the difference between e-invoicing and e-reporting in France?
E-invoicing covers in-scope domestic B2B invoices exchanged through approved platforms. Transaction e-reporting covers operations outside domestic B2B e-invoicing, such as B2C sales and transactions with foreign operators. Payment / collection e-reporting may also apply where VAT becomes due on collection, especially for service-related flows.
Can S4FN work with our chosen approved platform?
Yes, subject to technical fit. If you have selected a third-party PA, or plan to use SAP’s PA service through SAP DRC, we confirm the provider interface, authentication, routing, status handling and supported document flows before implementation.
How long does a France SAP readiness review take?
The readiness review is a focused engagement. The implementation timeline is estimated after confirming the SAP release, document flows, e-reporting scope, PA route, integrations and testing requirements.
What information do you need before a technical demo?
Your SAP release and edition, whether billing is standard SD/FI or customized, your e-reporting scope (B2C and transactions with foreign operators), and whether you have chosen a PA provider. The readiness checklist walks through each item.
DRC Sprint Country Compliance Pack
France: turn mandate scope into SAP delivery
The France pack connects B2B e-invoicing and e-reporting requirements to system evidence, architecture decisions, implementation work and operational controls.
What the pack connects
- 01Mandate controlsScope, scenarios, deadlines and exceptions
- 02SAP evidence checksRelease, component, configuration, data and process evidence
- 03Delivery assetsDecision records, test scenarios, work packages and operating controls
France focus: PA connectivity, invoice and e-reporting scenarios, partner routing, status handling and phased rollout controls.
Get your France SAP e-invoicing path before the 2026 deadline
Send your SAP release and current setup. We reply with a practical next step for your landscape: standard SAP DRC and SAP’s PA service where supported, integration with a selected third-party plateforme agréée (PA), or a supplemental S4FN extension or SAP BTP integration where a confirmed gap remains.
Primary Sources and Verification
Verified on: 10 July 2026. Scope, exclusions, platform status and the SAP-supported scenario must be reconfirmed before implementation.