Configuring SAP for France E-Invoicing: SAP DRC and PDP Integration Guide
A practical guide to configuring SAP for France's e-invoicing mandate. SAP Document and Reporting Compliance (DRC), the eDocument framework and cockpit, mapping to French formats, and why SAP still needs a certified Approved Platform (PA, formerly PDP) like Complyance.
Table of Contents
If your business runs on SAP, France's e-invoicing mandate raises a very specific question: what do you configure in SAP, and what has to happen outside it? The honest answer is that SAP does a lot of the heavy lifting on document generation and monitoring, but it does not, on its own, connect you to the French network. For that, SAP still needs an Approved Platform. You may see this called a PDP (Plateforme de Dématérialisation Partenaire); the current official term is Plateforme Agréée (PA), and the two refer to the same certified platform.
This guide clears up that split. It covers what SAP Document and Reporting Compliance (DRC) does, how the eDocument framework and cockpit fit in, how SAP maps invoices to French formats, and where a PA takes over so your invoices reach the buyer and the DGFiP. If you own SAP for a French entity ahead of the September 2026 deadline, this is your orientation map.
SAP Document and Reporting Compliance (DRC): The Overview
SAP's compliance solution is SAP Document and Reporting Compliance (DRC). It is SAP's global framework for handling statutory electronic documents and periodic reporting across many countries, France included. For France, DRC is where invoice documents are generated from your SAP transactions, mapped to the required structure, and monitored through their lifecycle.
The important nuance: DRC handles generation, mapping, and monitoring inside SAP. It still needs to connect to a certified Approved Platform (PA) for transmission to the French network and the DGFiP. Under France's strict 5-corner model (in force from September 2026, after the earlier Y-model was dropped at the end of 2024), every B2B e-invoice must travel through an Approved Platform. The public portal (PPF) is now only a Central Directory and Data Concentrator, not a transmission service, and it does not route or issue invoices. SAP DRC prepares the document; the PA moves it and reports it. (Chorus Pro remains the separate platform for B2G invoicing.)
The eDocument Framework and Cockpit
Inside SAP, France e-invoicing is built on the eDocument framework, the mechanism DRC uses to create and manage electronic documents from your source transactions (billing documents, journal entries, and so on).
Your day-to-day control point is the eDocument Cockpit (transaction /EDOC_COCKPIT). From the cockpit, teams can:
- View eDocuments generated from SAP source documents.
- Trigger submission, resubmission, and cancellation.
- Track status and see error messages when a document fails validation.
- Monitor the lifecycle of documents as statuses come back.
DRC is available across deployment models: SAP S/4HANA (on-premise and Private Cloud) and SAP S/4HANA Cloud, with cloud and integration components (often via SAP's cloud/integration layer) used to connect outward. Exact building blocks depend on your SAP release and deployment, so confirm the current setup for your landscape against SAP documentation.
How SAP Maps Invoices to the French Formats
France requires structured invoices in Factur-X, UBL 2.1, or UN/CEFACT CII, aligned to the EN 16931 standard. SAP DRC's job is to turn your SAP billing data into that structure.
- The eDocument framework extracts data from the SAP source document.
- DRC maps SAP fields to the target French format's elements.
- Validations run so incomplete or malformed documents are caught before they leave.
This is also where France's four new mandatory fields must be accounted for. SAP has to supply, from its own data:
| New Mandatory Field | What SAP Must Provide | Where It Typically Lives in SAP |
|---|---|---|
| Buyer SIREN | The buyer's SIREN on domestic B2B invoices | Customer master (business partner) identification |
| Delivery address | Delivery address when different from billing | Ship-to partner / delivery data |
| Nature of the operation | Goods, services, or both indicator | Derived from material/service or document configuration |
| VAT-on-payments option | Option for VAT to be due on payment | Tax configuration flowing to the output |
If these are not populated cleanly in your SAP master and configuration, DRC cannot map them, so master-data readiness in SAP is a prerequisite, not an afterthought. The same applies to the four mandatory lifecycle statuses (Déposée, Rejetée, Refusée, Encaissée), which SAP must be able to send and receive through the cockpit.
Why SAP Still Needs a PA
This is the point that trips up many SAP teams: DRC generating a compliant document is not the same as delivering it. France's model requires transmission through a certified Approved Platform (PA) and reporting to the DGFiP. SAP DRC handles the document; the PA handles the network.
A PA:
- Receives the compliant document from SAP.
- Validates it against French rules and transmits it across the network.
- Uses the PPF Central Directory (annuaire) to locate the buyer's platform.
- Exchanges lifecycle statuses back to SAP.
- Reports the required data to the DGFiP, and handles e-reporting for B2C and cross-border flows.
Because the PPF does not route or issue invoices, a certified PA is mandatory. SAP DRC connects to it. It does not replace it.
Integration Architecture at a Glance
Here is how the pieces fit, from SAP transaction to the tax administration:
| Layer | Component | Responsibility |
|---|---|---|
| Source | SAP billing / financial documents | Business transactions that trigger invoices |
| Generation | eDocument framework (DRC) | Create the eDocument from the source |
| Mapping | SAP DRC | Map SAP fields to Factur-X / UBL / CII, run validations |
| Monitoring | eDocument Cockpit (/EDOC_COCKPIT) | View, submit, resubmit, track status |
| Connectivity | SAP cloud / integration layer | Route the document outward to the PA |
| Transmission | Approved Platform (PA) | Validate, transmit to buyer's platform, report to DGFiP, handle e-reporting |
| Authority | DGFiP (via PPF concentrator) | Receive reported invoice and transaction data |
A simplified flow:
SAP (billing) to eDocument framework to DRC mapping and validation to eDocument Cockpit to SAP integration layer to PA (Complyance) to buyer's platform plus DGFiP.
SAP France E-Invoicing Configuration Checklist
Work through this list as you configure your SAP landscape for France:
- Confirm your SAP release and deployment support DRC for France.
- Activate the eDocument framework and the relevant France-specific content.
- Verify access to the eDocument Cockpit (/EDOC_COCKPIT) for your operations team.
- Clean SAP master data, validating buyer SIREN/SIRET and VAT numbers on business partners.
- Ensure ship-to (delivery) data is captured separately from bill-to.
- Configure the nature-of-operation indicator and the VAT-on-payments option so they flow to the output.
- Confirm mapping to Factur-X, UBL 2.1, or CII produces valid EN 16931 documents.
- Set up connectivity from SAP to your chosen PA.
- Test end to end in a sandbox, including credit notes and mixed goods/services.
- Verify the four lifecycle statuses (Déposée, Rejetée, Refusée, Encaissée) return to the cockpit and reconcile in SAP.
- Configure e-reporting for B2C and cross-border transactions via the PA.
Complyance and SAP: A Clean Division of Labour
Complyance is an Approved Platform (PA) built to sit at the end of your SAP DRC flow, so you keep SAP as your system of record and add compliant transmission around it.
1. A certified Approved Platform. Complyance handles validation, transmission across the network, lifecycle statuses, and reporting to the DGFiP that DRC alone cannot do.
2. Clean connectivity from SAP. Documents generated and mapped in DRC route out to Complyance, which takes them the rest of the way to the buyer and the tax authority.
3. Both e-invoicing and e-reporting. Domestic B2B invoicing and the B2C/cross-border e-reporting most SAP-run businesses also need are covered in one place.
4. Format and validation support. Support for Factur-X, UBL 2.1, and CII with real-time validation, complementing DRC's mapping.
5. Expert support for edge cases. Credit notes, self-billing, and mixed goods/services invoices handled with guidance, not guesswork.
Ready to connect SAP DRC to a French Approved Platform?
Complyance works alongside SAP Document and Reporting Compliance to complete your French e-invoicing chain, from the eDocument Cockpit to the DGFiP, with expert support for your SAP and finance teams.
Conclusion: Configure SAP, Connect a PA
For France, SAP DRC and an Approved Platform are partners, not competitors. DRC generates, maps, and monitors your invoices inside SAP; a PA transmits them and reports to the DGFiP. Here is your SAP configuration checklist in short:
- Confirm DRC support for France on your SAP release
- Activate the eDocument framework and use /EDOC_COCKPIT to monitor
- Clean SAP master data and populate the four new mandatory fields
- Validate mapping to Factur-X, UBL 2.1, or CII
- Connect SAP to a certified Approved Platform (PA)
- Test end to end and switch on e-reporting
Get that division of labour right, and your SAP landscape is ready for September 2026 without drama.
Related posts
Frequently Asked Questions
SAP DRC is SAP's global solution for generating statutory electronic documents and handling periodic reporting across countries. For France, it generates invoice documents from your SAP transactions, maps them to the required formats, and lets you monitor them, but it still needs an Approved Platform to transmit them to the network. Exact building blocks depend on your SAP release and deployment.
No. DRC handles document generation, mapping, and monitoring inside SAP. Transmission to the buyer's platform and reporting to the DGFiP must go through a certified PA (formerly called a PDP). Since the PPF does not route or issue invoices, a PA such as Complyance is mandatory.
The eDocument Cockpit is SAP's monitoring screen for electronic documents, reached via transaction /EDOC_COCKPIT. From there your team can view generated eDocuments, submit or resubmit them, track statuses, and troubleshoot validation errors.
SAP DRC maps your billing data to Factur-X, UBL 2.1, or UN/CEFACT CII, all aligned to the EN 16931 standard. The four new mandatory fields (buyer SIREN, delivery address, nature of operation, and the VAT-on-payments option) must be present in your SAP data for the mapping to succeed.
Yes. DRC can only map data that exists and is structured. Validate buyer SIREN/SIRET and VAT numbers on your business partners, keep ship-to and bill-to separate, and configure the nature-of-operation and VAT-on-payments indicators so they reach the output.
Complyance is a certified Approved Platform (PA) at the end of your DRC flow. Documents generated and mapped in SAP route out to Complyance, which validates, transmits across the network, exchanges lifecycle statuses back to SAP, reports to the DGFiP, and handles e-reporting for B2C and cross-border transactions.
About the Author
Swathy
Content Marketer
I’m a Content Marketer at Complyance, focused on e-invoicing. Over the years, I’ve created a wide range of content, including blog posts, whitepapers, and product guides, which have supported Complyance’s growth across markets such as the UAE and EU regions. My goal is to deliver content that is comprehensive, clear, accurate, and easy to understand, no matter how complex the topic.
