Your checkout works. But is your invoicing flow ready for France’s reform?
An order arrives from a consumer in Lyon. The next one comes from a German shopper. Then a French retailer places a wholesale order, and yesterday’s customer asks for a partial refund.
To your storefront, these can look like four normal orders. To your invoicing system, they are four different compliance and data scenarios.
Since 1 September 2026, every French business subject to VAT must be able to receive electronic invoices. Large companies and ETIs must already issue domestic B2B e-invoices and transmit e-reporting data; SMEs, VSEs and micro-enterprises follow on 1 September 2027. The official timetable is available from the French tax administration.
For an e-commerce business, the reform is not simply about replacing one PDF generator. It changes how customer data, VAT, orders, refunds, invoice statuses and accounting systems work together.
The first mistake: treating every order the same
Your commerce stack now needs to distinguish three flows.
1. French domestic B2B
An invoice between businesses established in France and subject to French VAT must be created as structured data and routed through a Plateforme Agréée (PA). A normal PDF attached to an email is no longer enough.
Your PA exchanges the invoice with the customer’s PA and returns lifecycle information. At minimum, your systems should be able to reconcile statuses such as deposited, rejected, refused and collected/paid with the original order and accounting entry.
2. B2C
Consumer sales do not enter the domestic B2B e-invoicing circuit. Ordinary consumer and distance-selling document rules still apply, but e-reporting is added.
This distinction matters technically: you should not turn every consumer order into a B2B e-invoice. Instead, e-reporting is generally based on cumulative daily sales data—notably turnover excluding VAT by VAT rate—and does not include the consumer’s personal data. The submission cadence depends on your VAT regime.
For a merchant processing thousands of orders, that means building a reliable aggregation and reconciliation flow, not firing one compliance request per checkout.
3. Cross-border
International transactions are also included in e-reporting where the French rules apply. Your stack still needs the correct VAT logic and evidence: destination VAT and OSS for eligible EU B2C sales, VIES validation and reverse charge where relevant for intra-EU B2B, and export evidence outside the EU.
Even if you sell only to consumers, you still need a PA to receive electronic invoices from French suppliers.
The reform starts at checkout, not in accounting
An invoice cannot be compliant if the order does not contain reliable data.
For a French professional buyer, can your checkout or sales team capture the correct legal entity, SIREN, VAT number, billing address and delivery address? Can it distinguish goods, services or a mixed operation?
At line level, the invoice flow may also need:
- Product name, variant, SKU, quantity and unit
- Unit price excluding VAT, discounts and totals excluding/including VAT
- Several VAT rates in the same basket
- Shipping allocation and promotional adjustments
- Currency, language and exchange-rate policy
- Deposit invoices, partial shipments, cancellations, refunds and credit notes
- Marketplace, merchant-of-record or multi-entity ownership
This is why invoicing becomes an integration project. Your storefront, OMS, ERP, payment provider, tax engine, PA and accounting system must agree on the same order—and on every later change to that order.
The three formats you will keep hearing about
The French system’s minimum interoperability set is:
- Factur-X: a human-readable PDF/A-3 with structured XML inside
- UBL: a structured XML format
- CII: another structured XML syntax
All align with the European semantic standard EN16931. A PA can accept another input format and convert it, so the useful buying question is not just “does it generate Factur-X?” but “which formats can the API accept and return, and who is responsible for conversion errors?”
The official PA register contained 150 entries on 17 September 2026 and continues to evolve.
What else changes on the invoice
The reform adds four data points to French invoices: customer SIREN, delivery address when different, nature of the operation, and the VAT-on-debits option where applicable. The usual requirements—continuous numbering, dates, VAT breakdown, totals, payment terms and late-payment information—remain.
Accounting documents and invoices are generally retained for 10 years. For an electronic invoice, preserve the original structured format and a reliable audit trail.
Penalties can reach €50 per missing electronic invoice and €500 per missing e-reporting transmission, each capped at €15,000 per year. The law provides correction relief for a qualifying first offence, but that is not an operating model.
The e-commerce platform checklist
Before comparing logos, test each candidate against your actual order flow.
- Compliance route: is it a PA, or which PA does it use?
- API access: which paid plan unlocks it? Are there rate limits, invoice quotas or extra fees?
- Webhooks and recovery: can you replay failures, use idempotency keys and reconcile statuses?
- Commerce data model: variants, SKUs, bundles, discounts, shipping, deposits and credit notes.
- B2C e-reporting: can it aggregate daily sales by VAT rate without exporting personal data?
- VAT: OSS, VIES, reverse charge, mixed rates and evidence management.
- Scale: peak order throughput, annual invoice allowance and multi-store/multi-entity support.
- Integrations: storefront, marketplace, ERP, accounting, bank and payment provider.
- Security and reversibility: GDPR, hosting, retention, permissions and complete export.
- Testing and support: sandbox quality, migration tools, incident handling and contractual responsibility.
Platform comparison for an automated French e-commerce flow
Prices below are excluding VAT and were checked on 18 September 2026. They show the public plan needed for API use—not simply the cheapest headline plan. Promotions and commitments change, so confirm a quote and expected invoice volume.
| Solution | Website | API documentation | France compliance route | API-ready public price | Best e-commerce fit | Watch-out | Rating |
|---|---|---|---|---|---|---|---|
| Odoo | odoo.com | Documentation | Direct PA | Custom: €37.40/user/month on regular annual pricing or €46.80 monthly; €29.90 first-year annual promotion displayed | Native eCommerce + inventory + accounting + PA | Strong implementation commitment; external API is not on the free plan | ★★★★½ |
| Pennylane | pennylane.com | Documentation | Direct PA | Essentiel: €24/month independent; €49/month small company | Finance/accounting hub with commerce data connections | Free e-invoicing is not the API plan; check invoice allowances | ★★★★ |
| Qonto | qonto.com | Documentation | Direct PA | Qonto Facturation: €0/month | Low-cost PA entry, invoice API and Factur-X import | Bank-centric; validate the complete B2C e-reporting and accounting chain | ★★★★ |
| Evoliz | evoliz.com | Documentation | Through Chaintrust by Visma PA | Advanced: €49/month or €490/year | API, pre-accounting and white-label possibilities | Evoliz is not listed as a PA under its own name | ★★★★ |
| Axonaut | axonaut.com | Documentation | Direct PA | €97/month for one user month-to-month; commitment discounts displayed | Public API and native Shopify, WooCommerce and PrestaShop connectors | Compare total commitment and volume economics | ★★★★ |
| Sellsy | sellsy.com | Documentation | Direct PA via TeamSystem Sellsy | Standard list: €39/user/month billed annually, minimum two users | CRM + invoicing + cash-management suite | Standard is capped at 100 invoices/month | ★★★½ |
| Abby | abby.fr | Documentation | Direct PA | Pro list: €15/month | Affordable public API for an independent or small shop | Validate throughput, multi-entity and complex commerce needs | ★★★½ |
| Dolibarr / DoliCloud | dolibarr.org · dolicloud.com | Documentation | Connect to a PA | Self-hosted software free; DoliCloud from €14/user/month | Open-source flexibility and reversibility | More integration ownership; DoliCloud publishes API and e-invoice volume limits | ★★★½ |
The score is editorial: it ranks fit for an automated e-commerce scenario, not legal status. Always verify the chosen product and legal entity on the live PA register.
Three useful tools that are not substitutes for a PA
- Quaderno is an international tax and invoicing layer. It can help calculate VAT and validate VAT numbers, but in France it still needs a PA connection. Its entry plan is $29/month for only 25 transactions, so compare by order volume.
- Stripe Tax can calculate tax and Stripe Invoicing can create billing documents. Neither alone routes a compliant French domestic B2B e-invoice. Stripe documents Marketplace integrations with PA-connected providers.
- Invoice Ninja offers a REST API and PEPPOL functions, but it is not a French PA. Do not select it as your only France-compliance layer without a verified PA route.
Tiime and Indy are direct PAs with attractive free offers, but we did not verify an open, self-service public invoicing API for a custom commerce integration. They can still make sense for a manual workflow or through an approved partner integration.
A safer implementation plan
1. Map the flows
Separate French B2B, B2C and cross-border orders. Identify the system of record for customer identity, tax, payment, fulfilment and refunds.
2. Fix data before connecting an API
Define required checkout fields, professional-account validation and a clean mapping for products, shipping, discounts and tax.
3. Select the platform with real volumes
Price the API plan, users, annual documents, calls, e-reporting, archiving and implementation—not the homepage’s lowest price.
4. Test the difficult cases
Do not stop at a happy-path invoice. Test mixed VAT, partial refunds, cancellations, credit notes, duplicate webhook delivery, PA rejection and customer refusal.
5. Run reconciliation before full cutover
For a representative period, reconcile orders, payments, invoices, e-reporting totals and accounting entries. Create alerts for missing documents and status mismatches.
6. Monitor the live flow
Track rejection rates, processing delays, webhook failures, unmatched refunds and monthly e-reporting totals. Compliance should become observable operations, not a manual year-end check.
Is the investment worth it?
The French tax administration cites 50–75% savings compared with paper processing and estimates around €4.5 billion in annual gains for businesses at economy level. Your own ROI will depend on volume, current manual work and integration quality.
For an e-commerce merchant, the operational upside is often more immediate: fewer manual entries, quicker reconciliation, cleaner refunds, fewer customer-service disputes and a finance team that sees the same data as operations.
What comes next
- 1 September 2027: SMEs, VSEs and micro-enterprises enter the issue and e-reporting phase.
- 1 July 2028: ViDA’s single-VAT-registration measures start.
- 1 July 2030: EU digital reporting requirements for cross-border B2B transactions apply, based on e-invoicing; the amended rules include a 10-day invoice deadline for relevant transactions.
Choosing an EN16931-ready platform now reduces—but does not eliminate—the work required for 2030.
Frequently asked questions
Does the French e-invoicing reform apply to my online store?
If your business is subject to French VAT, yes. Since 1 September 2026 every French business subject to VAT must be able to receive electronic invoices, and large companies and ETIs must already issue domestic B2B e-invoices and transmit e-reporting data. SMEs, VSEs and micro-enterprises follow on 1 September 2027.
Do I need a Plateforme Agréée if I only sell to consumers?
Yes. Consumer sales do not enter the domestic B2B e-invoicing circuit, but even if you sell only to consumers you still need a PA to receive electronic invoices from your French suppliers. B2C sales add e-reporting on top of the usual consumer document rules.
What is the difference between e-invoicing and e-reporting?
E-invoicing is the structured, PA-routed invoice exchanged between French businesses subject to French VAT. E-reporting covers transactions outside that circuit, such as B2C and relevant cross-border sales, and is generally based on cumulative daily sales data, notably turnover excluding VAT by VAT rate, without the consumer’s personal data.
Which invoice formats does the French system require?
The minimum interoperability set is Factur-X (a human-readable PDF/A-3 with structured XML inside), UBL and CII, all aligned with the European semantic standard EN16931. A PA can accept another input format and convert it, so ask which formats its API can accept and return, and who is responsible for conversion errors.
Can my current invoicing tool handle the reform, or do I need a new platform?
A normal PDF attached to an email is no longer enough for French domestic B2B. Your systems must create structured data, route it through a PA and reconcile lifecycle statuses such as deposited, rejected, refused and collected/paid with the original order and accounting entry. If your tool cannot do that, it becomes an integration project.
What data does my checkout need to capture for B2B invoices?
For a French professional buyer, your checkout or sales team must capture the correct legal entity, SIREN, VAT number, billing address and delivery address, and distinguish goods, services or a mixed operation. At line level you also need product name, variant, SKU, quantity, unit price excluding VAT, discounts, totals, VAT rates, shipping allocation and promotional adjustments.
What happens if I send a non-compliant invoice?
Penalties can reach €50 per missing electronic invoice and €500 per missing e-reporting transmission, each capped at €15,000 per year. The law provides correction relief for a qualifying first offence, but that is not an operating model.
How should I handle refunds, credit notes and partial shipments?
They are part of the same order lifecycle and must reconcile with the original invoice. Your data model needs to cover deposit invoices, partial shipments, cancellations, refunds and credit notes, and you should test mixed VAT, partial refunds, cancellations, credit notes and PA rejection before full cutover.
When do SMEs, VSEs and micro-enterprises have to comply?
Large companies and ETIs are already in the issue and e-reporting phase. SMEs, VSEs and micro-enterprises enter that phase on 1 September 2027. Further milestones follow: ViDA’s single-VAT-registration measures start on 1 July 2028, and EU digital reporting for cross-border B2B applies from 1 July 2030.
How do I choose between the invoicing platforms in the comparison?
Do not pick the lowest “from” price. Price the API plan, users, annual documents, calls, e-reporting, archiving and implementation against your real volumes, then test the difficult cases and reconcile orders, payments, invoices, e-reporting totals and accounting entries before full cutover. Always verify the chosen product and legal entity on the live PA register.
The bottom line
For e-commerce, France’s reform creates two distinct operating pipelines: structured PA-routed invoices for French B2B, and cumulative e-reporting for B2C and relevant cross-border sales. Both must reconcile with the same orders, payments, refunds and accounting records.
The right platform is therefore not the one with the lowest “from” price. It is the one whose API, volume model, PA route and data model survive your real checkout.
Saphes IT-Systems helps e-commerce businesses map these flows, select the right architecture and automate the connection between the store, ERP, invoicing platform and accounting. If your process still depends on exports and manual corrections, let’s talk.
This article provides operational information, not individualized tax or legal advice. Confirm your specific scope with your accountant, tax adviser and chosen PA.