French InvoiceNinja Users Are 6 Months From a Compliance Cliff

InvoiceNinja supports PEPPOL but not France's PA routing requirement. Sept 2026 deadline, zero integration on the roadmap.

Affects: French freelancers and SMEs using InvoiceNinja

Signal

Pain Point Radar detected a signal cluster around InvoiceNinja and French e-invoicing compliance. Multiple GitHub issues, forum threads, and community posts show French users asking about Plateforme Agréée (PA) integration — with no official response from the InvoiceNinja team indicating it's on the roadmap.

Context

France's e-invoicing mandate requires all B2B invoices to route through certified Plateformes Agréées (PAs) starting September 1, 2026. This isn't optional formatting — it's a routing requirement. Every B2B invoice must pass through a government-certified intermediary that validates, transmits, and reports the invoice data to the Direction Générale des Finances Publiques (DGFiP).

InvoiceNinja has built PEPPOL support and can generate Factur-X format invoices. On the surface, that looks like compliance. It isn't.

Gap Analysis

PEPPOL is a delivery network. Factur-X is a format. Neither satisfies the French mandate's core requirement: routing through a certified PA. France's system operates on a fundamentally different architecture than the broader European e-invoicing ecosystem.

The gap is structural, not cosmetic. InvoiceNinja can create the right document — but it can't send it through the right channel. There is no API integration with any certified PA (Chorus Pro, Generix, Comarch, etc.) and no public indication that one is being built.

This means every French freelancer and SME currently using InvoiceNinja for B2B invoicing is operating on a tool that will become non-compliant in approximately six months.

Impact

Every French InvoiceNinja user issuing B2B invoices faces a compliance wall on September 1, 2026. After that date, invoices not routed through a certified PA will be rejected by receiving businesses that have already onboarded to the system.

The practical consequences: delayed payments, rejected invoices, potential tax reporting issues, and the administrative burden of maintaining a parallel invoicing workflow. For freelancers operating on tight margins, even one month of payment disruption can be critical.

The affected population is specific but significant: French-speaking freelancers and small businesses who chose InvoiceNinja specifically for its open-source flexibility and self-hosting capabilities. These users are typically more technically sophisticated but less likely to have dedicated compliance staff monitoring regulatory changes.

Options

1. Pressure InvoiceNinja to build native PA integration before the September deadline. This requires coordinated community advocacy through GitHub issues and forum activity. Realistic timeline: uncertain. InvoiceNinja's development priorities are not publicly roadmapped for French-specific compliance.

2. Build a middleware bridge — export Factur-X invoices from InvoiceNinja and submit them through a PA portal manually or via a separate integration tool. This preserves the InvoiceNinja workflow but adds a manual step and potential point of failure. Tools like Chorus Pro offer free portal access for small volumes.

3. Migrate to an invoicing tool with native French compliance built in. Dolibarr (open-source, French-origin) has active PA integration modules. This is the most disruptive option but eliminates the compliance gap entirely.

We can assess your exposure and map a compliance path before the deadline hits.