E-Reporting in France: Obligations, Scope, Transaction Coverage, and How It Operates Alongside the E-Invoicing Mandate

Updated On : Oct 15th, 2025 | 25 min read

France`s mandatory e-invoicing framework for domestic B2B transactions addresses only one dimension of the tax authority`s ambition to achieve comprehensive visibility over commercial activity. The transactions that fall outside the B2B e-invoicing scope, sales to consumers, cross-border supplies, exports, imports, and intra-community transactions, represent a substantial portion of the commercial activity of many French businesses and generate VAT obligations that require equally rigorous reporting. E-reporting is the mechanism France has established to capture this data, transmitting structured transaction information to the Direction Générale des Finances Publiques for the same categories of transaction that e-invoicing does not cover.

Understanding e-reporting as a parallel and complementary obligation rather than a subset of e-invoicing is the conceptual foundation on which compliant implementation must be built. The two obligations share infrastructure, apply to overlapping sets of businesses, and operate through the same certified platform network, but they address different transaction types, carry different data requirements, and follow different reporting rhythms. A business that implements e-invoicing without also configuring its e-reporting obligations is only partially compliant with France`s mandate.

The Policy Logic Behind E-Reporting

The Direction Générale des Finances Publiques designed the e-reporting obligation to close the visibility gap that would otherwise exist if structured electronic reporting applied only to domestic B2B transactions. Consider the range of transactions that domestic B2B e-invoicing does not cover: a French retailer`s daily sales to individual consumers, a French manufacturer`s exports to customers in the United States or Japan, a French service provider`s cross-border B2B billing to a German client, a French importer`s purchases from a Chinese supplier. None of these transactions generate a domestic B2B e-invoice. Without a separate reporting mechanism, the tax authority would have no structured data on these flows despite their collective significance to France`s VAT base.

E-reporting fills this gap by requiring businesses to transmit the key transactional and payment data associated with these out-of-scope transactions to the tax authority through the same certified platform infrastructure used for e-invoicing. The data transmitted is not always at the individual invoice level. For B2C transactions, aggregate daily summaries are used rather than line-by-line invoice data, reflecting the volume of consumer transactions and the impracticality of individual invoice reporting at scale. For international B2B transactions, the reporting is more granular, aligning more closely with the data carried in a structured invoice.

Who Bears the E-Reporting Obligation

The e-reporting obligation applies to all French-established businesses that make transactions outside the scope of domestic B2B e-invoicing. This encompasses the full range of transaction types described below, but the obligation is not limited to large or complex businesses. Any VAT-registered French business that makes B2C sales, exports goods outside the EU, receives goods from EU suppliers, or makes cross-border B2B supplies will have e-reporting obligations that must be fulfilled through its certified platform.

Foreign companies that are not established in France but whose activities fall within the scope of French VAT also bear e-reporting obligations for their relevant transactions. A non-French business that is VAT-registered in France due to its commercial activities there cannot limit its compliance to domestic invoicing alone where it also conducts transaction types that fall within the e-reporting scope.

The implementation timeline for e-reporting mirrors the phased schedule for e-invoicing, differentiated by business size. Large companies became subject to e-reporting obligations first, followed by medium-sized companies, and finally small, medium, and micro-enterprises in the final phase.

The Transactions Covered by E-Reporting

France`s e-reporting obligation under Article 290 of the General Tax Code covers four principal categories of transaction that fall outside domestic B2B e-invoicing scope.

Business-to-Consumer Transactions

All sales of goods and services by French businesses directly to end consumers are subject to e-reporting. This category covers the broadest set of transactions in terms of volume, given that many French businesses serve both professional and consumer customers simultaneously. The reporting methodology for B2C transactions varies based on the business`s IT infrastructure and how it processes consumer sales, a distinction that reflects the practical reality that consumer transaction volumes are frequently too high to report at the individual invoice level.

Businesses operating point-of-sale systems report B2C transactions through a daily summary derived from the end-of-day Z ticket, which captures the aggregate value of sales processed through the POS system for that day. Businesses that issue electronic invoices to their consumers report that data through the same channel and method used for their B2B e-invoicing. Businesses without any IT transaction system are required to submit weekly or monthly operational summaries. This three-tier approach ensures that businesses at every level of digital infrastructure can fulfil the B2C e-reporting obligation without being required to implement point-of-sale technology they do not currently use.

International B2B Transactions

Cross-border B2B transactions between a French business and a business established outside France fall within the e-reporting scope rather than the domestic B2B e-invoicing scope, because both parties to the transaction are not French-established VAT-registered entities. Two subcategories apply distinct treatment.

For intra-community transactions within the EU, the e-reporting data must include the buyer`s VAT identification number, reflecting the intra-community supply framework under which the buyer accounts for VAT in their home member state. For transactions with businesses outside the EU, a different code is used in place of the EU VAT identifier. This distinction ensures that the Direction Générale des Finances Publiques can differentiate between intra-EU and extra-EU international flows in its analysis of the reported data.

Exports to Non-EU Countries

Exports of goods from France to countries outside the European Union are zero-rated for VAT purposes but remain subject to e-reporting. The reporting obligation ensures that the tax authority holds structured data on export activity that can be reconciled against customs declarations and used in VAT compliance verification. The data transmitted mirrors the information that would appear in an invoice for the export transaction.

Intra-Community EU Transactions

Both intra-community dispatches, meaning sales of goods and services from France to other EU member states, and intra-community acquisitions, meaning purchases by French businesses from suppliers in other EU member states, fall within the e-reporting scope. For dispatches, the French business is supplying to a VAT-registered customer in another member state under the intra-community supply rules, and the supply is zero-rated in France while the buyer accounts for VAT in their home country. For acquisitions, the French business self-assesses French VAT on the purchase. Both flows generate transaction data that the tax authority requires for VAT control and reconciliation purposes.

Operations Involving Overseas Territories

Transactions involving France`s overseas territories, which occupy a specific position in the EU VAT framework that differs from metropolitan France, are also within the e-reporting scope. The treatment of these transactions reflects the territorial complexity of French VAT law and the need for the tax authority to maintain oversight of commercial flows between metropolitan France and its overseas departments and territories.

How E-Reporting Works in Practice

The operational workflow for e-reporting runs through the same certified PDP infrastructure that handles domestic B2B e-invoicing. Businesses transmit their transaction data to their certified PDP, which performs the required verification checks mandated by the Direction Générale des Finances Publiques before reporting the validated data to the PPF. The PPF aggregates the reported data and forwards it to the tax authority. The OD route remains available for businesses using non-certified operators, with the OD preparing and forwarding data through a PDP or the PPF to complete t h e reporting chain.

The data transmitted in e-reporting must contain the same core transaction information as a structured e-invoice. This includes party identification, transaction amounts, applicable VAT rates, VAT amounts, and the relevant codes identifying the transaction type and the tax treatment applied. The requirement to use specific VAT codes for intra-community versus extra-EU transactions ensures that the reported data carries the classification information the tax authority needs to apply the correct legal analysis to each reported flow.

Reporting Frequency and Timing Requirements

E-reporting does not operate on the same real-time or near-real-time basis as B2B e-invoicing for all transaction types. The frequency of required reporting varies by transaction category and reflects the operational characteristics of each type.

For B2C transactions, the reporting obligation is periodic rather than transaction-by-transaction. The daily summary approach for POS-based businesses reflects a batch reporting model that is operationally practical for high-volume consumer sales environments. For businesses using other reporting methods, weekly or monthly summaries apply depending on the applicable IT infrastructure category.

For international B2B transactions, exports, and intra-community flows, reporting must be performed within specific deadlines established by the Direction Générale des Finances Publiques. Payment data, covering the status and timing of invoice settlements, must be reported monthly, creating a separate but related reporting obligation that tracks the payment lifecycle of reported transactions.

These timing requirements must be built into the e-reporting configuration within the business`s certified PDP to ensure automated reporting occurs within the required windows rather than being dependent on manual intervention.

The E-Reporting Lifecycle and Status Tracking

The e-reporting framework includes lifecycle tracking for reported data, in a manner analogous to the [invoice lifecycle status](insert blog 1) system used for B2B e-invoicing. The Direction Générale des Finances Publiques recommends that certified platforms maintain records of the following status events for each e-reporting submission: data receipt by the platform, acceptance by the platform, partial acceptance where some elements pass validation and others do not, rejection where the submitted data fails validation requirements, and provision to the administration confirming that the validated data has been transmitted to the PPF and onward to the tax authority.

This lifecycle tracking serves two purposes. It provides businesses with confirmation that their e-reporting obligations have been fulfilled for each reporting period, which is essential for demonstrating compliance in the event of a tax audit. It also provides the certified platform with the operational visibility needed to identify and resolve reporting failures before they accumulate into systemic compliance gaps.

Partial acceptance, as a distinct lifecycle status, is particularly relevant for complex e-reporting submissions that cover multiple transaction types within a single submission. Where some data elements pass validation and others do not, partial acceptance allows the compliant portion of the submission to proceed to the tax authority while flagging the non-compliant elements for correction and resubmission. This prevents a single data error from blocking an entire reporting period`s submission.

The Relationship Between E-Reporting and E-Invoicing

The distinction between e-invoicing and e-reporting is best understood through the dimension of transaction scope rather than technical process. E-invoicing governs the structured exchange of invoices for domestic B2B transactions between two French-established VAT-registered entities. The invoice itself is transmitted between the parties through the certified PDP network, with data simultaneously reported to the tax authority. E-reporting governs the transmission of transaction data for all other qualifying commercial flows, where the invoice, if one exists, may be issued in any format to the customer but the underlying transaction data must still reach the tax authority through the certified infrastructure.

This means e-reporting is not a fallback for businesses that cannot implement e-invoicing. It is a substantively different obligation that applies to a defined set of transaction types regardless of whether the business is also subject to e-invoicing. A business that makes only B2C sales and has no domestic B2B transactions would have no e-invoicing obligation but would still be fully subject to e-reporting for all its consumer sales. A business that makes domestic B2B sales, B2C sales, and cross-border supplies would be subject to both obligations simultaneously, with each applying to its respective transaction category.

The shared infrastructure means that a business using a certified PDP for e-invoicing can use the same platform for e-reporting, with the PDP handling both the B2B invoice transmission and the B2C and cross-border transaction reporting through a single integration. This operational consolidation is one of the practical arguments for selecting a certified PDP over an OD-based approach, since the PDP`s full-service capability encompasses both obligations within a single certified relationship.

Practical Preparation for E-Reporting Compliance

The preparation required for e-reporting compliance involves several steps that partially overlap profile to identify which transaction types generate e-reporting obligations alongside or instead of e-invoicing obligations. This mapping exercise should cover domestic B2C sales, cross-border B2B transactions with both EU and non-EU customers, exports, imports, and intra-community acquisitions.

For each transaction category identified, the business must confirm that its systems can extract the required transaction data in the format needed for transmission through its certified PDP. Where transaction data is generated by systems that are not currently integrated with the e-reporting infrastructure, data extraction and mapping configurations must be built and tested before the applicable compliance deadline.

The B2C reporting methodology decision, between POS-based daily summaries, electronic invoice-based reporting, or periodic operational summaries, must be made based on the business`s actual IT infrastructure and must be configured consistently with the methodology declared to the certified platform. Misalignment between the reporting methodology used in practice and the one configured in the platform is a source of validation failures that affect both the completeness and the accuracy of the reported data.

For businesses managing French e-reporting obligations alongside e-invoicing implementation and compliance requirements in other European jurisdictions, the operational complexity of maintaining accurate, timely, and complete structured data flows for multiple transaction categories across multiple regulatory frameworks is substantial. Platforms such as Accqrate provide the integrated infrastructure and specialist expertise needed to ensure that both France`s e-invoicing and e-reporting obligations are met accurately and within required timeframes, enabling businesses to focus on their commercial operations with confidence in their indirect tax compliance position.