E-reporting

E-reporting is the French regulatory obligation requiring businesses to transmit transaction data to the tax administration for operations not covered by e-invoicing, such as B2C sales, cross-border transactions, and payment data. It works alongside e-invoicing as part of France's broader tax digitalization reform. Unlike e-invoicing, which moves structured invoices between businesses, e-reporting sends summarized transaction data directly to the state.

How it works

E-reporting covers three main categories of data: B2C transactions (sales to consumers, where no invoice typically circulates between businesses), international B2B transactions (sales or purchases involving a foreign party, where full e-invoicing doesn't apply), and payment data for services subject to VAT on collection.

Businesses must transmit this data either directly, through a certified PDP (Plateforme de Dématérialisation Partenaire), or via a registered intermediary platform. The data itself is less detailed than a full invoice: it typically includes amounts, VAT rates, transaction dates, and counterparty categories, but not full line-item detail. Transmission frequency depends on VAT regime (daily, weekly, or monthly for most businesses).

The practical challenge is extraction and classification. Companies need to pull the right fields out of sales records, POS systems, and accounting entries, then route them to the correct reporting category. Get the classification wrong (treating a domestic B2B sale as one requiring e-reporting, for instance) and the transmitted data won't reconcile with what tax authorities expect from the e-invoicing side.

E-reporting timelines follow the same rollout schedule as French e-invoicing, with large and mid-sized companies going first and smaller businesses following later.

Why it matters for document processing

E-reporting forces companies to build reliable pipelines from unstructured or semi-structured sales data (receipts, POS exports, foreign invoices) into a structured feed the tax authority can consume. This is a data extraction and document classification problem before it's a compliance problem: you can't report data correctly if you can't first identify which transactions fall under e-reporting versus e-invoicing.

Many businesses underestimate this. They treat e-reporting as a downstream IT integration issue, then discover their source documents (foreign supplier invoices, marketplace settlement reports, cash register tapes) are inconsistent enough that automated field extraction fails silently. Cross-checking e-reporting submissions against e-invoicing data also requires cross-document validation, since discrepancies between the two flows are exactly what auditors look for. Getting the extraction layer right early avoids costly reconciliation work later, and it's a smaller lift than most finance teams expect once the source documents are properly classified.

Related terms

• https://sygnet.ai/solutions/e-invoicing-france
• https://sygnet.ai/glossary/pdp-plateforme-dematerialisation-partenaire
• https://sygnet.ai/glossary/factur-x
• https://sygnet.ai/glossary/cross-document-validation
• https://sygnet.ai/blog/french-e-invoicing-hidden-costs-how-to-choose-a-platform

FAQ

Is e-reporting the same as e-invoicing?

No. E-invoicing applies to domestic B2B transactions and requires a structured invoice to pass through a PDP. E-reporting covers transactions outside that scope (B2C sales, cross-border deals, payment data) and only requires summarized transaction data to be sent to the tax administration, not a full invoice.

Who is required to comply with e-reporting?

Any business registered for VAT in France that carries out B2C sales, cross-border B2B transactions, or VAT-on-collection services must comply. The rollout follows the same phased schedule as e-invoicing, starting with larger companies and extending to smaller ones on later deadlines set by the tax authority.