E-Reporting: send your B2C and international sales data to your accredited platform

Electronic invoicing covers only half of the French reform. The other half is e-reporting: sales to consumers, operations with foreign businesses, and the payments collected on your services. These operations have no electronic invoice, so they never travel through the Factur-X circuit, and nobody files them for you.

From 1 September 2027, every French small or medium business registered for VAT must report them to its accredited platform. The fine is 500 € per missing transmission, capped at 15,000 € a year.

The module produces the official message, and proves it

The flow 10 XSD schemas published by the French tax authority in external specifications version 3.2 dated 30 April 2026 are embedded in the module. Every message is validated against them before being sent: a non-conforming message is neither written nor transmitted. You do not discover the problem when the platform rejects it, two days after the deadline.

All four flows are covered: international invoices (10.1), payments linked to an invoice (10.2), aggregated consumer transactions (10.3), aggregated payments (10.4).

Two calendars, because the law imposes two

This is the trap of the reform. Under the monthly standard regime, transactions are filed every ten days, three times a month, while payments are filed once a month. The module keeps both rhythms apart, with their own periods, deadlines and overdue states, and shows them side by side. All four regimes are handled.

A period with no operation produces no message at all and can never fall overdue: the 2026 specifications removed the obligation to file an empty e-reporting.

Every operation is classified, and the rule is shown

Domestic B2B, consumer, international sale, international purchase, out of scope. Classification follows the country, the company registration number and the third party type, and shows the rule that produced it so you can challenge it. A per-third-party override forces a category.

Consumer sales are reported aggregated by day, currency and category, never invoice by invoice, as flow 10.3 requires. International operations are reported invoice by invoice with the counterparty identification. Sales and purchases form two separate transmissions.

Payments split to the cent

For each payment, the service share is split by VAT rate in whole cents, using the largest remainder method. Partial and multi-invoice payments included. Under the debits option, no payment data is produced, as the law provides.

All your sources, including the till

• Validated customer invoices, credit notes and down payments included.
• International supplier invoices.
• Point of sale sales, aggregated per day.
• Daily takings from a till outside Dolibarr, typed in or imported from CSV.
• Payments.

Nothing leaves with a blocking anomaly

Missing filer registration number, missing counterparty country on an international operation, inconsistent amount, payment with no invoice: sending is refused and the screen says what to fix. Warnings let the filing through and stay visible.

Send, trace, replay

• Sandbox to walk through the whole journey before you have even chosen your platform. It sends nothing and says so.
• Manual upload: the module produces the file, you upload it to your platform portal. It never claims to have sent anything.
• Generic REST API with a configurable authentication header. A plain HTTP endpoint is refused.
• Connectors from the Transmission PA module if installed, with nothing to reconfigure.

Every attempt, response and rejection is journalled. Re-sending an already accepted period produces a corrective transmission with a distinct identifier, a duplicate identifier being a firm ground for rejection.

What the module is not

Dolibarr with this module is a compatible solution in the sense of the external specifications, not an accredited platform: it never talks to the public invoicing portal directly, it hands its flow to your platform. It does not issue B2B electronic invoices, and it does not replace your VAT return.

Compatibility

• Dolibarr 20 to 24, both bounds actually tested. PHP 7.4 to 8.3.
• Interface in French and English. No external dependency: plain cURL, no Composer, no SDK.
• Generated files are written outside the web root.

Other Arcchester modules

Factur-X, Transmission PA, Reception PA, PeppolConnect, DoliTax, Pennylane Sync, DoliBank Match, Qonto & Open Banking Sync, Shopify Sync, LogiCockpit, PDF Annexes, Stripe Payment Links, WhatsApp Notify. Support: support@arcchester.com