France e-Reporting for Odoo
Prepare and transmit the French reform's e-reporting de transaction and e-reporting de paiement feeds — the B2C, cross-border and encaissement flows that e-invoicing leaves out.
What It Does
The French e-invoicing reform pairs mandatory B2B e-invoicing with two mandatory e-reporting flows that the e-invoice itself does not carry. From 1 September 2026 large and mid-size companies in France (and 1 September 2027 for SMEs) must transmit, alongside their e-invoices, the e-reporting de transaction (sales not covered by e-invoicing: B2C and cross-border B2B — exports, intra-community supplies and imports) and the e-reporting de paiement (the encaissement / payment status of services invoices that drives VAT on collection).
This module is the data-preparation and submission layer for those two flows. It scans your posted customer documents, classifies and aggregates the qualifying transactions per VAT rate, normalises the services-invoice payments, validates everything against the French business rules, and submits the feeds to your certified Plateforme Agréée using your own API credentials.
Key Features
Transaction feed (B2C & international)
Automatically collects posted customer invoices and refunds that are B2C or cross-border (and therefore not individually e-invoiced) and aggregates them per frame, VAT category, rate and counterparty country into transmission-ready transaction entries.
Payment feed (encaissement)
Collects the cash-collection status of services invoices in the period — collected, partial or pending — to feed VAT-on-collection (TVA sur les encaissements), reported per invoice.
Real SIREN validation
The reporter SIREN is derived from your company SIRET and validated with the published Luhn algorithm; per-entry VAT categories are mapped to EN 16931 codes (S, Z, E, AE, export G, intra-community K).
Per-month periods & audit trail
Each period is a reviewable, editable working set: draft → collected → submitted → accepted, with both canonical feeds and the full transport log stored for audit.
BYOK transmission
Feeds are posted to the e-reporting endpoints of the Plateforme Agréée you already configured for PDP routing. Your API token lives only on your database and is transmitted only to the platform you set.
Validation before transmission
A dedicated fr_ereporting rule set checks the reporter SIREN, the YYYY-MM period, VAT categories, currency, frame codes and payment statuses, blocking any feed that would be rejected.
Optional monthly automation
An opt-in monthly cron collects and submits the previous period automatically for high-volume B2C and cross-border sellers. Disabled by default.
Guided setup wizard
A one-screen wizard validates the SIRET, turns on the flows you need and creates the current month's period so you land ready to collect.
Built on the e-Invoice Core Engine
This connector reuses the shared e-Invoice Core Engine (canonical JSON, validation framework, BYOK REST transport) and the France PDP Routing module (SIREN/SIRET validation and the Plateforme Agréée connection). It does not duplicate invoice routing — it captures the flows that B2B e-invoicing leaves out and ships them to the same platform.
Compatible with Odoo 18 & 19
Disclosure: this module transmits aggregated e-reporting data only to the Plateforme Agréée endpoint you configure on the PDP connection. Your API token is stored solely on your own database and is never sent anywhere else.
Screenshots
E Reporting Period B2C Cross
Classified Transaction Lines
Update date: 2026-07-02