French B2B e-invoicing stops being optional in 2026. From September 2026 every established company must be able to receive structured electronic invoices, and issuance plus e-reporting obligations phase in behind it, all routed through a Plateforme Agréée (PA) now that the state PPF has pivoted to a directory-and-concentrator role. ERPNext ships a solid Sales Invoice and Purchase Invoice, but it has no concept of a Factur-X hybrid PDF, no lifecycle statuses tied to a PA, no e-reporting extract for B2C and cross-border transactions, and no inbound channel for supplier invoices arriving as structured data. Teams end up bridging that gap with spreadsheets and a portal login, which does not scale and does not survive an audit.

This app closes that gap inside ERPNext itself. We build a proper Frappe app (france_einvoicing) with its own module, so nothing is patched into erpnext core and upgrades stay clean. On submit of a Sales Invoice, a hooks.py on_submit doc event calls a whitelisted server-side method that assembles a Factur-X / EN 16931 compliant document: a human-readable PDF/A-3 with the structured CII XML embedded, mapped from your ERPNext party, tax, and item data. A new E-Invoice Transmission DocType tracks each document's lifecycle (generated, submitted, accepted, rejected, paid-status-reported), stores the PA message id, and links back to the source invoice so your finance team never leaves ERPNext.

Transmission is handled by a pluggable connector layer. Rather than hard-wire one vendor, we implement a PA Connector DocType plus a Python transport class per provider, so the same routing logic serves whichever Plateforme Agréée or PDP you select during scoping. Outbound invoices are pushed and their acknowledgements polled back via a scheduler_events cron; inbound supplier invoices are pulled and parsed into draft Purchase Invoices with the embedded XML mapped to ERPNext fields for your AP team to review. E-reporting flows (payment status, B2C and international transactions that are reported but not invoiced through a PA) are aggregated on schedule and submitted in the required cadence. Everything is exposed over the Frappe REST API and guarded by dedicated role profiles and permission rules, with client scripts adding the status badges and action buttons your users see on the invoice form.

Because this is build-to-order, we start from your actual chart of accounts, tax templates, party masters and chosen PA, not a generic template. After a scoping call we confirm the exact CII field mapping, the connector, and your v15 or v16 target, then deliver working software, a UAT pass on a staging bench, and a supported go-live. Typical delivery is one working week from confirmed scope. You receive the full source and the git repository, so the app is yours to run and extend.