France’s e-reporting mandate requires VAT-registered businesses to electronically transmit transaction and payment data for operations outside mandatory domestic B2B e-invoicing, using approved platforms, with phased rollout from September 2026 and September 2027 based on size.
Key Takeaways
All VAT-registered businesses in France are required to comply with the e-invoicing and e-reporting mandate from 1 September 2026 for large businesses and ETIs, and from 1 September 2027 for SMEs and micro-enterprises, with all businesses required to be able to receive electronic invoices from 1 September 2026.
Under this mandate, in-scope domestic B2B invoices must be issued in a structured electronic format through a Approved platform (platform), while reportable transaction and payment data must also be transmitted electronically to the tax administration.
The French model operates through two connected channels:
E-reporting in France is the electronic transmission of transaction and payment data to the tax administration for operations that fall outside mandatory domestic B2B e-invoicing. It forms part of the same reform as French e-invoicing, but it serves a different purpose.
While e-invoicing applies to domestic B2B transactions between VAT-taxable businesses established in France, e-reporting captures other reportable flows, especially those involving non-taxable persons, foreign operators, and payments on transactions where VAT becomes due on collection.
Transaction e-reporting applies to:
France uses a platform-based transmission model. Businesses do not send e-reporting data directly by ordinary email or manual filing. Instead, the approved platform receives and transmits invoice, transaction, and payment data to the administration based on the information provided by the business. Depending on the type of flow and system environment, transmission may be supported by invoice uploads, ERP outputs, point-of-sale data, or periodic summary files.
Business Category | e-Reporting Start Date |
|---|---|
Large enterprises and intermediate-sized enterprises | 1 September 2026 |
SMEs and micro-enterprises | 1 September 2027 |
Non-established large or intermediate-sized sellers or service providers | 1 September 2026 |
Non-established micro, small, and medium-sized sellers or service providers | 1 September 2027 |
Non-established acquirers or customers liable for VAT in specific cases | 1 September 2027 |
Transaction e-reporting applies to operations that do not fall within mandatory domestic B2B e-invoicing but must still be transmitted to the French tax administration.
Transaction e-reporting mainly covers transactions within the French VAT scope that are outside domestic French B2B e-invoicing, including:
Transactions exempt from VAT under Articles 261 to 261 E of the French General Tax Code, and not subject to invoicing, are excluded from transaction e-reporting.
Common examples include:
For transaction e-reporting in France, the core data to be transmitted is relatively limited in principle: the administration expects the transaction amount and the corresponding VAT. The reporting method then depends on the type of transaction and source system used. For consumer flows, businesses can report using structured data extracted from POS systems or invoice uploads, while some international B2B transactions are handled at invoice level rather than as daily aggregates.
VAT Regime | Frequency | Transaction Data Submission Deadline |
Monthly VAT regime | Per 10-day period: Three submissions for one month:
| 10 days after the end of the period, that is:
|
Quarterly VAT regime | Monthly | Before the 10th of the following month |
Simplified VAT regime | Monthly | No later than between the 25th and 30th of the following month |
VAT exemption regime | Every two months (bimonthly) | No later than between the 25th and 30th of the month following the end of the period |
Payment e-reporting applies only to operations for which VAT becomes due on collection. In the French reform, it is a separate e-reporting stream from transaction data and is limited to payments received on in-scope operations, mainly services and other flows taxed on an encaissement basis. It does not apply simply because a transaction exists. It applies when the payment event itself becomes reportable.
Payments Which Must Be e-Reported?
Payment e-reporting mainly covers payments received for transactions within the French VAT scope where VAT is due on collection, including:
Payment e-reporting does not apply to all collections. It is excluded where the law removes the need to report payment data as a separate stream.
Common exclusions include:
For payment e-reporting in France, the core data to be transmitted is the actual collection date and the amount collected, broken down by VAT rate. The reporting method then depends on how the underlying transaction was handled.
Payment Scenario | How the Payment Data Is Reported | Data to Be Reported |
Payment linked to an e-invoice deposited on an approved platform | Reported by updating the invoice status to “encaissée” | Invoice number, payment date, amount collected by VAT rate |
Payment linked to an international B2B transaction not deposited as an e-invoice | Reported per invoice in a global payment e-reporting flow | SIREN of the collecting business, reporting period, invoice number, reporting date, amount collected by VAT rate |
Payment linked to B2C flows already reported through daily aggregated transaction data | Reported as daily aggregated payment data | SIREN of the collecting business, reporting period, collection date, total amount collected by VAT rate |
VAT Regime | Frequency | Deadline |
Monthly VAT regime | Monthly | Before the 10th of the following month |
Quarterly VAT regime | Monthly | Before the 10th of the following month |
Simplified VAT regime | Monthly | No later than between the 25th and 30th of the following month |
VAT exemption regime | Every two months (bimonthly) | No later than between the 25th and 30th of the month following the end of the period |
A workable implementation starts with scope design, then platform selection, then system integration. Treating e-reporting as only a file-submission exercise usually leads to classification errors and broken reconciliations.
Step 1: Map the Transaction Population
Separate domestic B2B France-established flows from all other taxable and reportable operations. Identify which transactions are with non-taxable customers, which are cross-border, which are services taxed on collection, and which are reverse-charge or VAT-on-debits cases. This mapping should happen at transaction-family level and then be tested at document and master-data level.
Step 2: Select a PA (State-Registered Approved Platform)
Businesses must use a state-registered PA (like ClearTax) for e-invoicing and for transmitting transaction and payment data. The platform is not a passive relay. It receives, transmits, and processes invoice-related information and sends e-reporting data to the administration based on information provided by the client.
Step 3: Prepare Source Data
The following data domains usually decide whether implementation succeeds or fails:
Step 4: Build the Right Reporting Logic
A compliant design must support more than one reporting method. International taxable-person transactions may need invoice-level extraction, while B2C or other non-assujetti flows may need daily aggregated totals. Payment reporting may also require invoice-level or aggregated payment handling depending on the underlying flow. A single flat export usually cannot cover all scenarios without transformation rules.
Step 5: Reconcile With VAT and Cash Data
The reform does not replace VAT accounting logic. It adds a structured data-transmission layer that must remain consistent with the VAT position and, for payment reporting, with actual collections. Reconciliation should therefore cover source invoice data, reporting-period allocation, platform submissions, cash application events, and the resulting VAT reporting posture. This is one of the most important internal controls in the French model.
The special cases often matter more than the headline rule because they are where classification mistakes happen.
A foreign company without a permanent establishment in France is generally outside the domestic e-invoicing scope, but may still be subject to e-reporting where the operation is located in France and French VAT is due. This is one of the clearest examples of why e-invoicing scope and e-reporting scope should never be treated as identical.
Being under the VAT exemption scheme does not automatically remove a business from the reform. The official guidance explains that businesses benefiting from the small business VAT exemption scheme can still fall within the overall reform, at least for receipt of e-invoices and, depending on their operations, for transmission obligations. “No VAT shown” is not the same as “out of scope.”
Customer classification can change the reporting path. The FAQ highlighted in the research document explains that certain associations may be treated as non-taxable persons. In those cases, the association itself may not have e-invoicing or e-reporting obligations, but transactions carried out to its benefit can still fall into the supplier’s e-reporting scope. That makes customer-status governance a master-data issue, not only a tax-technical issue.
The French overseas position is not uniform. Some territories are outside VAT for local operations, which can place local entities outside e-invoicing for those operations. However, e-reporting may still apply where transactions are deemed located in mainland France and subject to French VAT. Businesses operating across mainland France and overseas territories should therefore avoid one blanket territorial rule.
Using an e-commerce interface does not, by itself, shift compliance ownership away from the company carrying out the transaction. The research source notes that the platform user remains responsible for e-invoicing and e-reporting obligations, even where VAT facilitator rules affect tax liability. That means marketplace sellers still need their own scope and timing analysis.
Although both obligations are part of the same French reform, they do not apply to the same transactions or serve the same purpose.
Aspect | E-Invoicing | E-Reporting |
Scope | Applies to domestic B2B sales and services between businesses established in France and subject to French VAT. | Applies to transactions outside that domestic B2B scope, mainly B2C transactions and transactions with operators established abroad. |
What is sent | The electronic invoice itself is issued and exchanged in a structured format, and invoice data is transmitted from it to the tax administration. | Structured transaction data or payment data is sent to the tax administration, even when the underlying transaction is not covered by mandatory domestic B2B e-invoicing. |
Main purpose | To digitize invoice issuance and receipt for in-scope domestic B2B flows. | To give the administration visibility over non-e-invoiced transactions and certain payment events. |
Typical examples | A French VAT-registered business invoicing another France-established VAT-registered business. | A sale to a private individual, an export, an intra-EU supply, or payment data for services taxed on collection. |
Payment data | Not the core trigger. | Includes payment e-reporting for certain services where VAT is due on collection. |
France’s e-reporting reform includes a specific sanctions framework for both taxable persons and approved platforms, with separate penalty amounts and annual caps depending on who failed to meet the reporting obligation.
Entity | Type of Failure | Penalty per Transmission | Annual Cap |
|---|---|---|---|
Taxable person | Failure to comply with transaction e-reporting or payment e-reporting obligations | €500 | €15,000 |
Approved platform | Failure to comply with its own e-reporting transmission obligations | €750 | €100,000 |
Why ClearTax for France E-Invoicing and E-Reporting
ClearTax is a compliance first e-invoicing and e-reporting pre-approved platform built to manage France’s digital tax reporting requirements through one connected workflow. It supports the full compliance journey, from invoice creation and data mapping to reporting, validations, and ongoing monitoring, so businesses can reduce manual work and stay aligned with reporting rules as they scale.
Key capabilities:
French e-reporting is best understood as a data-governance obligation built on VAT logic, not as a narrow filing requirement. Businesses that classify customers correctly, distinguish invoice reporting from payment reporting, and align their platform, ERP, and cash data early will be far better prepared than businesses that wait to solve the issue at submission stage. In practice, the strongest compliance position comes from treating scope, data quality, and reconciliation as one integrated process.
Resource | Description |
Official overview of the reform, including the distinction between e-invoicing, transaction e-reporting, and payment e-reporting. | |
Official timing note covering the 1 September 2026 and 1 September 2027 rollout dates. | |
Official explanation of which transactions fall into transaction e-reporting. | |
Official guidance on when payment data must be transmitted and what data points are required. | |
Official frequency and deadline table by VAT regime. | |
DGFiP: E-Reporting for Foreign Companies Without a Permanent Establishment in France | Official English-language guidance for non-established businesses. |
Official explanation of the role of approved platforms in France’s model. | |
Official directory of state-registered platforms. | |
Official public-service summary of the reform calendar and business obligations. | |
Legal text governing payment-data reporting. |