How to Choose the Right France E-Invoicing Solution for Your Business
A practical buyer's guide to choosing a France e-invoicing solution and certified Approved Platform (PA) before the 2026 mandate. Compare must-have criteria, avoid common mistakes, and score vendors with a clear framework.
Table of Contents
Picking an e-invoicing platform in France used to be a "nice to have" project that finance could push to next quarter. That window has closed. From 1 September 2026, every French VAT-registered business must be able to receive electronic invoices, and large and medium-sized companies must issue them. From 1 September 2027, the obligation to issue reaches small and micro businesses too. The DGFiP has confirmed there is no further delay.
So the real question is no longer whether you need a logiciel de facturation électronique, it is which one, and how to choose without regretting it eighteen months later.
The problem is that "France e-invoicing solution" covers everything from a lightweight portal to a full integration engine wired into your ERP. They are not interchangeable. Choose the wrong tier and you either overpay for capability you will never use, or you hit a wall the week before go-live. This guide gives you a buyer's framework: the first filter that disqualifies most tools instantly, the must-have criteria, a scoring table you can copy, the mistakes that trip up most teams, and a clean set of decision steps.
Start With the Non-Negotiable: A Certified Approved Platform
Before you compare features, understand how invoices actually move in France. At the end of 2024 the government confirmed a strict five-corner model, effective 1 September 2026. Under it, every domestic B2B e-invoice flows exclusively through a certified Approved Platform (Plateforme Agréée, or PA, formerly PDP). There is no free public issuing and receiving service. The public portal (PPF) has been narrowed to two jobs only: the Annuaire Central (the central directory) and the Concentrateur de Données (the data concentrator) that forwards data to the DGFiP. It does not send or receive your invoices.
That single fact makes your first buying filter obvious.
1. The vendor must be a certified Approved Platform, or partner with one. Using a certified PA is mandatory. The DGFiP publishes the official list of Approved Platforms, so you can verify a vendor's status directly. Some tools are marketed as Solutions Compatibles (OD/SC). Those are not PAs and must connect through a certified Approved Platform to transmit and report your invoices. That can work, but you need to know exactly which certified PA sits behind the tool, because that platform is where your compliance actually lives.
2. It must cover your real transaction mix. E-invoicing in France applies to domestic B2B. Separately, e-reporting applies to B2C sales, cross-border transactions, and other non-B2B flows (imports, exports, intra-EU). Most businesses need both. A tool that handles domestic B2B beautifully but ignores e-reporting leaves half your obligation uncovered. Note that e-reporting also has its own rhythm: transaction data is typically submitted every 10 days under the monthly VAT regime, and payment data monthly.
If a solution fails either of these, stop. It does not matter how good the dashboard looks.
The Must-Have Criteria for a France E-Invoicing Solution
Once a vendor clears the two filters above, evaluate it on the criteria below. These are the dimensions that separate a platform you will grow into from one you will rip out.
1. PA Certification and Regulatory Standing
Is the platform itself a certified Approved Platform, or does it route through one? Ask for the certification status in writing, check it against the DGFiP's published list, and ask how the vendor keeps pace as specifications evolve toward 2027 and the EU's VAT in the Digital Age (ViDA) reforms. France became a Peppol Authority on 8 July 2025, so ask about Peppol interoperability too.
2. Format Support
France's mandate is built on the EN 16931 European standard. A compliant platform must handle Factur-X (the hybrid PDF/A-3 and XML format popular with French SMEs), UBL 2.1, and UN/CEFACT CII. Note that Peppol BIS is a profile of UBL 2.1 (France has been a Peppol Authority since 8 July 2025), while EDIFACT is not among the authorized formats. Confirm the platform can both generate and ingest all three authorized formats, because receiving matters as much as issuing.
3. E-Reporting Coverage
Can the platform submit transaction and payment data for B2C and cross-border flows, not just domestic B2B invoices? This is where many "invoicing" tools quietly fall short.
4. ERP and System Connectors
Your invoices live in SAP, Oracle, Sage, Microsoft Dynamics, NetSuite, or a homegrown system. Look for pre-built connectors, a documented API, and support for batch and real-time flows. The fewer custom bridges you build, the faster and cheaper your go-live.
5. Lifecycle Status Handling
The French model exchanges lifecycle statuses between platforms. Under the AFNOR XP Z12-012 specification there are four mandatory statuses: Déposée (Submitted), Rejetée (Rejected, a technical rejection), Refusée (Refused, a commercial rejection by the buyer), and Encaissée (Cashed, payment received). Your solution should capture, expose, and route these statuses back into your systems so finance can see where every invoice stands.
6. Security and Data Governance
Ask about encryption, access controls, audit trails, data residency, and independent certifications such as ISO 27001. You are moving your entire billing flow through this platform, so its security posture is your security posture.
7. Support and Onboarding
Who helps you when a batch rejects at 5 p.m. before a deadline? Evaluate support hours, response times, onboarding assistance, gap analysis, and whether you get real specialists or a ticket queue.
8. Pricing Model
Understand how you are billed (per invoice, per volume tier, per connector, or flat platform fee) and what triggers overage. A model that looks cheap at pilot volume can become the most expensive line item at scale. Ask for the all-in cost including onboarding and support, and verify the specifics directly.
9. Deployment Speed
How long from kickoff to live invoicing? With a hard 2026 deadline, a platform that goes live in weeks beats one that needs a six-month implementation, all else equal.
A Scoring Framework You Can Copy
Turn the criteria into numbers. Score each vendor 1-5 on every row, weight the rows by what matters most to your business, and let the total do the arguing. Here is a starting template:
| Criterion | Weight | What a 5 Looks Like | What a 1 Looks Like |
|---|---|---|---|
| Certified Approved Platform / routing | High | Certified PA on the DGFiP list, confirmed in writing | Unclear which certified PA is behind the tool |
| Format support (Factur-X, UBL 2.1, CII) | High | Generates and ingests all three, EN 16931 aligned | Supports one format, issue-only |
| E-reporting (B2C + cross-border) | High | Full e-reporting alongside e-invoicing | E-invoicing only, no e-reporting |
| ERP / system connectors | High | Pre-built connectors plus documented API | Manual upload only |
| Lifecycle status handling | Medium | Captures and routes all four statuses to your ERP | Statuses not surfaced |
| Security & certifications | High | ISO 27001, clear data residency, audit trails | No certifications, vague on data |
| Support & onboarding | Medium | Specialists, gap analysis, fast response | Ticket-only, slow |
| Pricing transparency | Medium | Clear all-in model, no surprise overage | Opaque, per-item fees add up |
| Deployment speed | Medium | Live in days to weeks | Multi-month implementation |
Multiply each score by its weight, sum the columns, and you have a defensible shortlist you can take to your CFO, not a gut feeling.
Common Mistakes to Avoid
Even careful teams stumble on the same few things. Watch for these:
- Assuming any "compatible" tool is enough. Only a certified Approved Platform can transmit and report your invoices. A Solution Compatible must connect through a PA, so always confirm which certified PA sits behind it.
- Treating a PDF-by-email tool as compliant. A PDF is not a structured e-invoice. If the platform cannot produce Factur-X, UBL 2.1, or CII, it does not meet the mandate. A transition allowing PDF sent through a PA runs only until December 2027.
- Forgetting e-reporting. Buying purely for domestic B2B and discovering your B2C and cross-border flows are still uncovered is a costly surprise.
- Ignoring the receiving side. From September 2026 everyone must receive e-invoices. A tool that only issues leaves you unable to accept invoices from compliant partners.
- Choosing on price alone. The cheapest per-invoice rate is meaningless if onboarding drags for months or support disappears after signature.
- Underestimating ERP integration. The invoice data has to leave your system cleanly. Skipping a gap analysis on your ERP fields is the most common cause of failed go-lives.
- Assuming the deadline will slip again. It will not. Planning for a delay is planning to be late.
Decision Steps: From Longlist to Signature
A simple sequence keeps the project on track:
- Map your transaction mix. Domestic B2B, B2C, cross-border. Quantify each so you know exactly what you need to cover.
- Run an ERP gap analysis. Check your current invoice data against the mandatory fields and formats. This tells you how much integration work is real.
- Filter on the non-negotiable. Drop any vendor that is not a certified Approved Platform (or clearly routing through one on the DGFiP list) and any that cannot cover your full scope.
- Score the shortlist. Use the table above with your own weights.
- Test in a sandbox. Insist on a sandbox environment. Send real invoice shapes (credit notes, mixed goods and services, self-billing) and watch how the platform behaves.
- Pressure-test support and pricing. Ask hard questions about onboarding timelines, overage, and who picks up the phone during a deadline crunch.
- Plan go-live and e-reporting together. Do not treat them as separate projects.
Where Complyance Fits
Complyance is a certified Approved Platform (PA), so it clears the very first filter that disqualifies most tools. It supports Factur-X, UBL 2.1, and CII, handles both e-invoicing and e-reporting, and surfaces the four lifecycle statuses (Déposée, Rejetée, Refusée, Encaissée) back into your systems. Pre-built ERP connectors and a documented API mean integration is measured in days rather than months, and sandbox testing lets your developers validate edge cases before go-live. For teams that are not ready to integrate by API on day one, guided uploads keep you compliant while the deeper integration lands. Add an ERP gap analysis and specialist support for tricky cases (credit notes, self-billing, mixed invoices) and you have a platform that scores well on every row of the table, not just the flashy ones. As always, compare it fairly against the criteria alongside the other names on the market.
Ready to score your options?
Use the framework above, then talk to Complyance about a gap analysis and a sandbox trial to see how a certified Approved Platform performs against your real invoice flows.
Conclusion: Choose Deliberately, Not at the Last Minute
The France mandate is fixed, but your choice of partner is not. The businesses that come out ahead are the ones that treat vendor selection as a structured decision, not a scramble. Before you sign, run this checklist:
- Confirm the platform is a certified Approved Platform (on the DGFiP list) or clearly routes through one
- Verify support for Factur-X, UBL 2.1, and CII, both issuing and receiving
- Confirm e-reporting coverage for B2C and cross-border flows
- Check ERP connectors and API against your actual systems
- Score every vendor on weighted criteria, not gut feel
- Run a sandbox test with your real invoice shapes
- Nail down pricing, onboarding timeline, and support before signature
Get these right and the 2026 mandate stops being a threat and becomes an upgrade: cleaner data, faster payments, and less manual work.
Related posts
Frequently Asked Questions
An Approved Platform (Plateforme Agréée, or PA, formerly PDP) is a platform certified by the DGFiP to send, receive, and transmit e-invoices and report data to the tax authority. The official list is published on impots.gouv.fr. From September 2026 France runs a strict five-corner model, so every domestic B2B e-invoice must flow through a certified PA. The public portal (PPF) is now only the Annuaire Central (directory) and Concentrateur de Données (data concentrator), so using a certified PA (or a tool that routes through one) is mandatory.
It must handle the EN 16931-aligned formats: Factur-X, UBL 2.1, and UN/CEFACT CII. Confirm the platform can both generate and receive them, since reception becomes mandatory for everyone from September 2026.
E-invoicing covers domestic B2B transactions. E-reporting covers B2C sales and cross-border transactions. Most businesses need both, so a solution that only handles domestic B2B leaves part of your obligation uncovered.
Very. Your invoice data lives in your ERP, and getting it out cleanly is the most common source of delayed go-lives. Prioritise platforms with pre-built connectors, a documented API, and an ERP gap analysis so you know the integration effort before you commit.
No. Per-invoice price is only one part of the total. Slow onboarding, missing e-reporting, weak support, or surprise overage can make a "cheap" tool the most expensive choice over time. Compare all-in cost and capability, not headline rate, and verify pricing directly.
More than you think. Between ERP gap analysis, integration, sandbox testing, and team training, a proper rollout takes months. Starting your evaluation now, well ahead of September 2026, gives you room to test properly instead of rushing.






















