France E-Invoicing Readiness: A 6-Step Preparation Plan for Businesses
A practical 6-step plan to get your business ready for France's e-invoicing mandate. Assess, fix data gaps, choose an Approved Platform (PA), test, train, and go live before September 2026 with Complyance.
Table of Contents
The clock on France's e-invoicing reform is no longer a distant abstraction. From 1 September 2026, every VAT-registered business in France must be able to receive electronic invoices, and large and medium companies must start issuing them and reporting transaction data. Small and micro businesses follow on 1 September 2027. The DGFiP has confirmed there will be no further delay.
If that date makes you a little nervous, that is a reasonable place to start. But readiness is not a mystery, and it is not a last-minute scramble if you begin now. The réforme de la facturation électronique touches your invoicing data, your ERP, your teams, and the platform you choose to connect to the network. Each of those is a solvable problem.
This guide breaks the work into a clear 6-step preparation plan. Follow it in order, use the readiness checklist near the end, and you will walk into 2026 knowing exactly where you stand.
Why Readiness Matters Now
The dématérialisation des factures in France is built on a strict 5-corner model from September 2026. The earlier Y-model was dropped at the end of 2024. Invoices no longer travel as PDFs by email. Instead, every B2B e-invoice flows exclusively through a certified Approved Platform (Plateforme Agréée, PA), formerly called a PDP. Your supplier PA validates the invoice and transmits it to the buyer's PA, which reports the required data to the tax administration. The public portal (PPF) is now only a Central Directory and Data Concentrator. It does not route or issue invoices. In practice, that means every business must choose a PA. (Chorus Pro remains the separate platform for B2G invoicing to public bodies.)
Getting there is a project, not a switch you flip. Data has to be clean, formats have to match the standard, teams have to know the new process, and everything has to be tested before real invoices flow. Starting early turns a compliance deadline into a calm, staged rollout.
The 6-Step Preparation Plan
Here is the full arc, from where you are today to a compliant go-live. Work through each step before moving to the next.
Step 1: Assess Your Current Invoicing
Before you change anything, understand what you have. Map how invoices are created, approved, sent, received, and archived today across every entity and system.
- List every system that issues or receives invoices (ERP, billing tools, spreadsheets, third-party portals).
- Identify who touches an invoice at each stage: sales, finance, AP, AR, tax.
- Note your current formats. Are you sending PDFs by email? Paper? EDI? None of these are compliant French e-invoices on their own.
- Separate your flows: domestic B2B (which falls under e-invoicing) from B2C and cross-border transactions (which fall under e-reporting).
The output of this step is a simple inventory. You cannot fix gaps you have not found.
Step 2: Run a Data and Field Gap Analysis
A French e-invoice is structured data, not a picture of an invoice. It must be issued in an approved format (Factur-X, UBL 2.1, or UN/CEFACT CII, all aligned to the EN 16931 European standard). The reform also adds four new mandatory fields that many ERPs do not capture cleanly today.
| New Mandatory Field | What It Means | Common Gap |
|---|---|---|
| Buyer SIREN | The buyer's SIREN number on every domestic B2B invoice | Customer master data often has no SIREN, or it is stored in a free-text note |
| Delivery address | The delivery address when different from the billing address | Ship-to and bill-to are frequently merged or missing |
| Nature of the operation | An indicator for goods, services, or both | Not captured as a structured field at all |
| VAT-on-payments option | A mention of the option for VAT on payments (*TVA sur les débits*) | Sits in tax config, not on the invoice output |
Compare each required field against what your ERP actually produces. Flag every missing, incomplete, or free-text field. This gap list becomes your remediation backlog. Note too that the reform requires four mandatory lifecycle statuses (Déposée, Rejetée, Refusée, Encaissée), so confirm your systems can send and receive them.
Step 3: Choose Your Approved Platform (PA)
Because the PPF does not route or issue invoices, connecting to a certified Approved Platform (PA) is not optional. It is the core of your compliance. Your PA validates invoices, converts them to approved formats, transmits them across the network using the PPF Central Directory (annuaire), exchanges lifecycle statuses, and handles reporting to the DGFiP.
When choosing, look for:
- Support for all three formats (Factur-X, UBL 2.1, CII) and the full lifecycle-status set.
- Pre-built ERP integrations and a clean API, plus a fallback for teams that are not API-ready.
- A working sandbox environment so you can test before go-live.
- Handling for both e-invoicing and e-reporting, since most businesses need both.
- Ongoing updates as the rules evolve toward 2027 and the EU's ViDA reforms.
Complyance is an Approved Platform (PA) built to cover exactly this scope: approved formats, lifecycle statuses, ERP integrations, sandbox testing, and support for both e-invoicing and e-reporting.
Step 4: Test in a Sandbox
Never let your first real invoice be your first test. Use your PA's sandbox to run representative invoices end to end.
- Push a batch of typical invoices from your ERP through the platform.
- Confirm the four new fields populate correctly and validation passes.
- Test the awkward cases: credit notes, self-billing, mixed goods/services, exempt and zero-rated lines.
- Verify that the four lifecycle statuses (Déposée, Rejetée, Refusée, Encaissée) come back and reconcile in your system.
- Run e-reporting scenarios for your B2C and cross-border flows.
Every error you find here is one you do not find in production.
Step 5: Train Your Teams
E-invoicing changes daily habits, not just systems. Finance will see lifecycle statuses instead of chasing PDFs by email. AP will receive structured invoices through the platform. Tax will rely on cleaner, near real-time data.
- Brief finance, tax, AP/AR, and IT on the new flow and their part in it.
- Document how to handle rejections, refusals, corrections, and status follow-ups.
- Assign clear ownership for master-data quality, especially the buyer SIREN.
- Update internal procedures and quick-reference guides before go-live.
Step 6: Go Live and Switch On E-Reporting
With data fixed, a PA connected, tests passed, and teams trained, you are ready to go live. Phase it if you can. Start with a subset of customers or entities, monitor closely, then scale.
- Confirm you can receive e-invoices (mandatory for everyone from September 2026).
- Confirm you can issue and e-report if you are a large or medium company (also from September 2026).
- Activate e-reporting for B2C and cross-border transactions (transaction data roughly every 10 days, payment data monthly).
- Keep monitoring statuses and rejections in the first weeks and tune as needed.
France E-Invoicing Readiness Checklist
Use this table to track where you stand. Aim to move every row to "Done" well before your obligation date.
| Readiness Area | What "Ready" Looks Like | Status |
|---|---|---|
| Invoicing inventory | Every issuing/receiving system mapped, B2B vs B2C/cross-border separated | ☐ |
| Format readiness | Output in Factur-X, UBL 2.1, or CII (EN 16931) confirmed | ☐ |
| Four new fields | Buyer SIREN, delivery address, nature of operation, VAT-on-payments captured | ☐ |
| Lifecycle statuses | Déposée, Rejetée, Refusée, Encaissée sent and received | ☐ |
| Master data | SIREN/SIRET and VAT numbers cleaned and validated | ☐ |
| PA selected | Certified Approved Platform (PA) chosen and contracted | ☐ |
| Sandbox testing | Representative and edge-case invoices passed end to end | ☐ |
| E-reporting | B2C and cross-border reporting configured | ☐ |
| Team training | Finance, tax, AP/AR, IT briefed and procedures updated | ☐ |
| Go-live plan | Phased rollout and monitoring plan in place | ☐ |
Your Timeline at a Glance
| Date | What Applies |
|---|---|
| Now to mid 2026 | Assess, fix data, choose your PA, and test in sandbox |
| 1 September 2026 | All businesses must receive e-invoices; large and medium businesses must issue and handle e-reporting |
| 1 September 2027 | Small and micro businesses must issue e-invoices and e-report |
The reception obligation hits everyone first, so even the smallest business needs a receiving capability by September 2026. That single fact is why "wait for 2027" is the wrong plan for almost every company.
There is one transition allowance to know about. Until December 2027, a business can send a PDF to its PA, which converts it into a structured format. This gives slower-moving suppliers a bridge, but structured output from your own systems is the target state, so treat the PDF route as temporary, not a destination.
What About Penalties?
Under the Loi de Finances 2026, the penalties are specific. Failing to issue an e-invoice costs 50 euros per invoice (capped at 15,000 euros per year). A missed e-reporting submission costs 500 euros (also capped at 15,000 euros per year). The DGFiP has confirmed a grace period from September 2026, so there are no immediate penalties at launch, but that window is for finishing your rollout, not for delaying it.
How Complyance Helps You Get Ready
Complyance is an Approved Platform (PA) built to carry you through all six steps without a long, painful implementation.
1. Gap analysis, done for you. A structured review aligns your ERP output with the required formats and the four new mandatory fields, so you know your remediation list up front.
2. Fast, low-effort go-live. Pre-built ERP integrations and sandbox testing take you from kickoff to e-invoicing ready in days, not months.
3. Developer-friendly, finance-friendly. Clean APIs and real-time validation for your developers; guided uploads for teams that are not ready for APIs yet.
4. Both e-invoicing and e-reporting. One platform covers domestic B2B invoicing and the B2C/cross-border reporting most businesses also need.
5. Continuous updates. As the rules move toward 2027 and ViDA, the platform keeps pace so you do not have to track every change yourself.
Ready to start your readiness plan?
Complyance gives your finance, tax, and IT teams the tools and expert support to move through assessment, testing, and go-live with confidence, well ahead of the 2026 deadline.
Conclusion: Readiness Is a Plan, Not a Panic
France's e-invoicing mandate is firm, and the reception deadline of September 2026 applies to everyone. The good news is that readiness follows a clear path. Here is your starting checklist:
- Inventory every invoicing system and separate B2B from B2C/cross-border
- Run a field-level gap analysis against the four new mandatory fields
- Choose your Approved Platform (PA)
- Test thoroughly in a sandbox, including edge cases
- Train finance, tax, AP/AR, and IT
- Plan a phased go-live and switch on e-reporting
Start now, work the six steps in order, and the deadline stops being a threat and becomes just another date you have already prepared for.
Related posts
Frequently Asked Questions
Reception becomes mandatory for all businesses on 1 September 2026, and large and medium companies must also issue e-invoices and e-report from that date. Small and micro businesses must issue from 1 September 2027. The DGFiP has confirmed no further delay.
Yes. Even though smaller businesses are not required to issue until 2027, every business must be able to receive e-invoices from September 2026. You need a receiving capability, and therefore an Approved Platform, well before that first date.
The reform adds four fields to domestic B2B invoices: the buyer's SIREN, the delivery address (when different from billing), the nature of the operation (goods, services, or both), and the VAT-on-payments option. A gap analysis checks whether your ERP captures each one.
E-invoicing covers domestic B2B transactions between French VAT-registered businesses. E-reporting covers everything else: B2C sales and cross-border trade, with transaction data reported roughly every 10 days and payment data monthly. Most businesses need both, which is why Step 6 includes switching on e-reporting.
No. The PPF is not a free invoicing platform. Its role is now limited to the Central Directory (Annuaire Central) and Data Concentrator (Concentrateur de Données). It does not route or issue invoices. To send, receive, and report, you must connect to a certified Approved Platform (PA) such as Complyance.
Under the Loi de Finances 2026, failing to issue an e-invoice costs 50 euros per invoice (capped at 15,000 euros per year), and a missed e-reporting submission costs 500 euros (also capped at 15,000 euros per year). A DGFiP grace period from September 2026 means no immediate penalties at launch.
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.
