E-Invoice Finder
Menu
Countries Compare software Deadlines Guides Checker Check obligation
ENFRDEPLNL
Independent buyer’s guide for French businesses

France e-invoicing software comparison for 2026

Compare Sage, Cegid, Pennylane, Qonto and Sellsy for French e-invoicing in 2026, using workflow fit, PA checks, costs and clear demo evidence.

Quick verdict:
  • Score mandatory capabilities before viewing polished extras.
  • Give the owner of exception queues a formal vote in selection.
  • Pause procurement until finance signs off one repaired rejection.
Check your French e-invoicing readinessOfficial sources
Last checked: 23 July 2026Based on official sourcesClear summaryBusiness guidance, not legal advice
Official sources prioritized
Last-checked dates visible
Free checker, no signup required

What you need to know

Guide

No universal best: start with a profile-based shortlist

There is no responsible universal winner in a Sage vs Cegid vs Pennylane vs Qonto vs Sellsy comparison. Begin with the workflow you already operate and treat supplier positioning as a hypothesis to test. Sage and Cegid merit investigation where an existing accounting or ERP ecosystem, multi-entity controls and established finance processes matter. Pennylane may suit businesses prioritising accountant collaboration and a shared finance workflow. Qonto may warrant attention where invoicing, expenses and banking sit together and a small business wants a simpler path. Sellsy may fit organisations seeking continuity across CRM, quotations, sales and invoicing. These are starting points, not feature verdicts. Reduce the field to two or three candidates, document your legal entities, transaction types, invoice volumes, user roles and integrations, then ask each supplier to demonstrate the exact edition and modules it proposes—not a generic flagship environment.

Guide

The official 2026 and 2027 timetable

Service-Public states that every business within scope must be able to receive electronic invoices from 1 September 2026. Large companies and mid-sized enterprises (ETIs) must also issue from that date; SMEs and micro-enterprises begin mandatory issuance on 1 September 2027. Receiving readiness therefore cannot wait merely because your own issuing deadline is later. The reform covers a structured exchange and reporting model: an ordinary PDF attached to an email is not the mandated flow. Map the timetable by legal entity rather than relying on group-level assumptions, and include B2B domestic invoices, B2C transactions, exports, intra-EU activity and payment data where relevant. Official dates and scope rules should prevail over marketing countdowns. Confirm any special case with the current official guidance and your adviser, particularly where entity size, transaction location or VAT treatment is unclear.

Guide

Official PA status is not the same as your subscribed scope

DGFiP describes a plateforme agréée (PA, previously commonly called PDP) as able to emit, transmit and receive electronic invoices, extract useful data, and receive or transmit transaction and payment information. Its official list page, modified on 21 July 2026, also explains that definitive registration follows interoperability tests under real conditions; candidate assessment covers tax compliance, infrastructure and data security, and interoperability. Re-check that official list immediately before signing, using the precise legal entity providing the service. Even confirmed PA status does not prove that your chosen Sage, Cegid, Pennylane, Qonto or Sellsy subscription includes every required connector, entity, volume tier, e-reporting function, support level or archive option. Ask the seller to identify the PA operator, registration state, contracted module and responsibilities in writing, including any subcontracted or partner route.

Guide

A neutral comparison of the five options by operating profile

For an initial France e-invoicing software comparison, match each candidate to the change you are willing to make. Existing Sage users can investigate whether their current product, version and ledger workflow can be extended without disruptive re-entry. Cegid deserves the same examination for businesses already using its accounting or ERP environment, especially where entity-level governance matters. Pennylane should demonstrate how business users and the external accountant share validation, records and exceptions. Qonto should show whether its combined banking, expense and invoicing route covers the complexity of your sales and finance controls. Sellsy should prove the hand-off from CRM and quotations through invoicing, credit notes and accounting export. None of these propositions guarantees fit. Exact editions, integrations, entity coverage, transaction volumes, e-reporting, support and migration arrangements must be confirmed in a written response tied to your requirements.

Guide

Build a weighted requirements matrix

Use a 100-point matrix before commercial demonstrations: legal and PA route 20%, transaction and e-reporting coverage 15%, accounting/ERP/CRM integration 15%, operational workflow and controls 15%, data security and auditability 10%, implementation and support 10%, three-year cost 10%, and portability and exit 5%. Set non-negotiable gates separately: correct entity coverage, required structured formats, receiving by the statutory date, required e-reporting, credit-note handling and an acceptable security review. Score each criterion from zero to five only when evidence exists, multiply by its weight, and record the evidence link, product edition and date. A high aggregate score must not rescue failure on a mandatory gate. Invite finance, sales operations, IT, the external accountant and a real invoice-processing user to score independently; discuss large differences rather than averaging them away. This turns an approved platform comparison in France into an auditable decision rather than a feature-count contest.

Guide

Test formats, reporting and integrations with representative cases

Require the same scripted demonstration from every finalist. Case one: receive a supplier invoice, match SIREN/SIRET and TVA data through the annuaire, route approval and export the posting. Case two: issue a domestic B2B Factur-X, UBL or CII invoice aligned with EN 16931, then show lifecycle statuses and a credit note. Case three: process B2C and export or intra-EU activity and show the associated e-reporting and payment-data treatment. Case four: send an invoice involving Chorus Pro or a relevant Peppol/API route and recover cleanly from rejection. Case five: move a quotation from CRM or ERP to invoice, payment reconciliation, archive and audit trail without duplicate entry. Inspect the structured data, not just the readable PDF. Ask how accounting export, user permissions, multiple entities, API failures, corrections, attachments and portability work in the exact contracted configuration.

Guide

Compare three-year total cost, contract and exit terms

Do not compare headline monthly prices alone, and do not assume a free tier will remain adequate. Model three years using realistic growth in entities, users, outgoing and incoming invoices, API calls, storage and support demand. Add implementation, configuration, data cleansing, connectors, accountant access, training, custom fields, archive retrieval, premium support, overage charges, annual indexation and VAT where applicable. Separate one-off migration costs from recurring charges and request a priced scenario for peak volume. Contract checks should cover minimum term, renewal notice, service levels, incident escalation, data location, subprocessors, liability, format or regulatory updates and what happens if the PA route changes. For exit, require structured export of invoices, statuses, attachments, audit logs and master data, plus deletion confirmation and migration assistance. Compare like-for-like editions in writing; a low entry price can conceal costly dependencies or restricted portability.

Guide

Risks and common comparison mistakes

The most common mistake is equating a familiar brand, a vendor’s dated claim or candidate status with current official PA registration and complete contractual coverage. Other risks include testing only a simple sales invoice, ignoring receiving readiness, confusing a visual Factur-X PDF with validated structured data, overlooking B2C/export e-reporting, and assuming an accounting connector is real-time and bidirectional. Buyers also understate exception volumes, credit notes, multi-entity permissions, duplicate prevention, rejected invoices, payment-status reporting and archive access. Avoid copying feature tables whose editions or publication dates differ. Vendor pages are useful for identifying claims to investigate, but DGFiP and Service-Public are the authority for official rules and timetable. Record every answer with a date, named product, module and legal entity; label unproven claims as open. Security, business continuity, support response and exit capability deserve the same attention as the attractive front-end workflow.

Guide

Run a concrete go/no-go decision process

Start by completing one requirements sheet for each legal entity and marking statutory, operational and desirable needs. Check the current DGFiP list, then issue the same written questionnaire and five-case demo script to two or three shortlisted providers. Reject any option that fails a mandatory gate or will not identify its PA route and contracted scope. For the remaining candidates, validate references or documentation, security and data-processing terms, integration ownership, implementation resources and a three-year cost model. Run a limited pilot with representative users and reconciled outputs where practical; log defects, workarounds and unresolved dependencies. The final go decision should name an accountable owner, implementation milestones, receiving-readiness date, fallback procedure, acceptance tests and exit plan. Choose the candidate with the strongest evidenced fit for your weighted needs—not the longest feature list—and obtain all critical commitments in the order form or contract before signature.

Checklist

List every French legal entity, SIREN/SIRET, VAT position and statutory deadline.

Count incoming and outgoing invoices, users, peaks and expected three-year growth.

Map domestic B2B, B2C, export, intra-EU, payment-data and credit-note scenarios.

Verify the exact PA legal entity and current registration on the DGFiP list.

Record the proposed edition, modules, volume limits, connectors and support tier.

Run all five representative cases and retain screenshots, exports and error results.

Calculate three-year cost including implementation, overages, archive and migration.

Secure written acceptance criteria, service commitments, structured export and exit terms.

FAQ

Which option is best for an SME in France?

There is no single best option for every SME. A small firm wanting a straightforward invoicing, expense and banking workflow might investigate Qonto; a business working closely with its accountant might examine Pennylane. Existing Sage or Cegid customers should test whether extending their present ecosystem reduces migration and control risk, while a sales-led firm may examine Sellsy’s CRM-to-invoice continuity. Treat these as shortlist hypotheses only. The right choice depends on entities, transaction types, integrations, controls, support and total cost, all verified for the exact contracted edition.

Are Sage, Cegid, Pennylane, Qonto and Sellsy all officially approved?

Do not infer approval from a brand name or this comparison. Check DGFiP’s live official PA list immediately before contracting and match the listed legal entity to the operator named in your proposal. The list page was modified on 21 July 2026, and status can be more nuanced than a marketing badge because definitive registration follows real-condition interoperability tests. Also distinguish the PA operator from the software interface or partner selling the service. Ask each supplier to state its current registration status, legal entity, PA route and the functions included in your specific subscription in writing.

Is a free plan enough for French e-invoicing?

A free plan may cover a narrow workflow, but price alone cannot establish readiness. Check whether it includes statutory receiving, your issuing timetable, the necessary structured formats, e-reporting and payment-data cases, credit notes, lifecycle statuses, archive, accountant access and required integrations. Examine volume, user, entity, API, storage and support limits, plus whether essential functions require a paid module. Ask for the current terms and a three-year growth scenario. A no-cost entry tier can be useful for evaluation, but only written scope and successful tests can show whether it is sufficient for your business.

Do I need to replace my accounting or ERP software?

Not necessarily. Your existing accounting, ERP or CRM may connect to a PA, include a suitable module, or exchange data through an API or accounting export. First map where invoices originate, where approvals occur, which system holds master data and how postings and statuses return. Then ask the current supplier and shortlisted PA to demonstrate the complete round trip without duplicate entry. Replacement may be justified if the existing stack cannot meet mandatory flows or creates excessive manual control, but integration costs and process risk should be compared with migration costs before deciding.

What should an e-invoicing software demo prove?

The demo should use your representative data and prove outcomes, not tour menus. Require receipt and approval of a supplier invoice; domestic B2B issuance in a valid structured format; lifecycle statuses and a credit note; B2C, export or intra-EU e-reporting; and a CRM or ERP route through reconciliation, archive and export. Include a rejection or API failure and observe recovery. Confirm SIREN/SIRET, VAT data, permissions, multiple entities, attachments and audit logs. Save the outputs and tie every result to the proposed edition, modules and integration design so the demonstration becomes usable acceptance evidence.

How should I compare total cost?

Build a three-year model with the same assumptions for every supplier. Include licence tiers, legal entities, users, incoming and outgoing volumes, storage, API usage, implementation, connectors, migration, configuration, training, accountant access, premium support, overages and annual increases. Add internal effort for exception handling and reconciliation where one workflow needs more manual work. Request prices for the base case, a peak month and a growth case, and identify non-cancellable commitments. Keep tax treatment consistent. The result should show cash cost, internal workload and contractual exposure rather than a misleading comparison of advertised monthly fees.

Can I change approved platform later?

A later change should be possible in principle, but the practical difficulty depends on your contract, data portability, integrations and operating history. Before signing, require export of structured invoices, statuses, attachments, audit logs and master data in documented formats. Check termination notice, renewal, extraction charges, deletion timing, archive access, migration support and responsibility for in-flight invoices. Ask how directory information and routing are changed and test an export during the pilot. This page provides practical information, not legal or tax advice; obtain professional advice where contractual, retention or statutory responsibilities are material.

Is Factur-X or a PDF enough?

A normal PDF sent by email is not the mandated structured flow. Factur-X can combine a readable PDF with embedded structured data, but displaying a Factur-X label does not prove that the data is valid, complete, routed correctly or sufficient for all your transactions and reporting duties. Ask the supplier to validate the embedded data, show UBL or CII support where needed, demonstrate EN 16931 alignment, and prove receipt, lifecycle statuses, credit notes and e-reporting. The correct answer depends on the transaction and official rules, so test actual cases rather than accepting a sample PDF.

Key regulations, formats and terms

FranceFrench tax administrationDGFiPimpots.gouv.frapproved platformplateforme agrééePDPFactur-XUBLCIISIRENVATe-reportingSMEmicro-enterpriseaccounting softwareEuropean CommissioneInvoicingEN 16931Directive 2014/55/EUstructured electronic invoiceVAT automationcross-border tradePractical 2026 France e-invoicing software comparison and requirements matrix for Sage, Cegid, Pennylane, Qonto and Sellsy

France — Country hub

France

Open country hub →

Use the country hub to see every related deadline, checklist, format guide and software comparison for this market.

Continue reading

Official sources

We prioritize official government and EU sources where available and keep last-checked dates visible for mandate-sensitive pages.