Facturation électronique

Transmission conforme de tes factures Counsel via une Plateforme Agréée, prête pour la réforme française.

The layer that makes your invoices compliant with the French e-invoicing reform. A finalized Counsel invoice is sent to an accredited platform (Qonto first), which generates the Factur-X and routes it over the network. You track the regulatory status right from the invoice page.

What it does for you

The French reform makes e-invoicing mandatory for domestic B2B. Receiving becomes mandatory on September 1st, 2026, issuing for small and mid businesses on September 1st, 2027. In practice, an invoice between two French companies can no longer travel as a plain PDF by email: it has to go through an accredited platform that puts it in the right format and sends it over the official network.

This module plugs Counsel into that network. When you finalize an invoice, it is sent to an accredited platform as structured data: client, lines, VAT, payment details. The platform recreates the invoice, produces the Factur-X and routes it to the recipient. You never touch the XML or the PDF/A-3, the platform handles it.

The module is provider-agnostic. Qonto is the first provider wired and tested in real conditions. Iopole and B2Brouter are planned behind the same interface: switching platform is a config change, not a code change. Until a workspace connects a platform, transmission is simply skipped and the invoice stays a regular one.

A subjection rule decides, invoice by invoice, whether transmission happens. It only applies to French B2B: issuer registered in France with a SIRET, recipient a French company with a SIRET. Outside that scope (individual client, foreign client) the invoice stays a classic send and falls under a separate e-reporting flow.

How it works

Transmission via an accredited platform

The invoice is not submitted as a PDF. It goes out as structured data to the platform, which recreates the invoice, generates the Factur-X and sends it to the recipient. The Qonto path follows a clear sequence: create or reuse the client by email, create the invoice, send by e-invoicing, then read the status.

The recipient is identified by their SIRET, checked in the platform directory
An unreachable recipient returns an explicit error, the invoice stays ready to retransmit
On the Qonto path, the issuer must hold a Qonto account for settlement

Regulatory status tracking

Every finalized invoice shows an "Accredited platform transmission" card on its page. You see the platform used, the lifecycle status, the transmission identifier, the send date and the last error if there is one. A button lets you retransmit after a failure.

Statuses tracked: pending, submitted, received, made available, approved, in dispute, rejected, payment sent, failed
Status events are logged as they come, not just the latest state
Updates arrive via a signed webhook from the platform

/counsel/invoices

Invoice 2026-014 Submitted

Factur-X, accredited platform Qonto

Submitted Mar 12, 09:41
Received by the platform pending
Accepted pending
Settled pending

Sent as structured data, not an attached PDF.

Factur-X format, sent through an accredited platform (PDP).

Click a lifecycle step to see the timestamp land.

Automatic subjection

Before any transmission, a pure rule decides whether the invoice falls in the French B2B scope. Issuer outside France, issuer without a SIRET, individual or foreign recipient: in those cases transmission does not happen and the reason is logged. A French recipient with a SIRET triggers the e-invoice, otherwise the module identifies the e-reporting case.

Inbound supplier invoices

The network works both ways. Invoices received through the platform are synced and listed in Counsel, on the received invoices page. You find the supplier, their SIRET, the number, the amount, the dates and the status. A periodic sync pulls in new incoming invoices.

Supplier, SIRET, invoice number, amount, currency, issue and due dates
Distinction between invoice and credit note
Manual sync from a button, plus a scheduled sync

Two issuing flows

The same engine serves two origins. Counsel invoices issued by a freelancer to their clients. And Freelance OS platform subscription invoices to its own subscribers, when it bills its clients. The second flow applies the same French B2B rule and the same status tracking.