Briefing document & Podcast: France’s E‑Invoicing & E‑Reporting

1. Introduction and Country Context

1.1 Digitalisation journey

• France introduced mandatory electronic invoicing for public procurement progressively through Chorus Pro, with full B2G coverage achieved in 2020. The private-sector reform extends that experience to domestic B2B transactions and supplements it with transaction and payment reporting. [legifrance.gouv.fr], [aife.econo…ie.gouv.fr]
• The legal foundation was initially established by Ordinance No. 2021-1190 of 15 September 2021. Following several postponements and redesigns, the framework was consolidated through:
  • Article 91 of the Finance Law for 2024;
  • the Finance Law for 2025, which recast the public platform’s role;
  • Article 123 of Law No. 2026-103 of 19 February 2026;
  • Decree No. 2026-677 and the ministerial order of 27 July 2026. [impots.gouv.fr], [legifrance.gouv.fr], [legifrance.gouv.fr]

1.2 Policy objectives

The reform is intended to:

• reduce invoicing and administrative costs;
• improve invoice automation and payment monitoring;
• combat VAT fraud by giving the tax administration transaction-level visibility;
• improve economic-statistics data;
• support the eventual pre-filling of VAT returns. [economie.gouv.fr], [aife.econo…ie.gouv.fr], [impots.gouv.fr]

1.3 Position relative to EU developments

• France is an early adopter of a broad domestic digital reporting model, although its implementation now overlaps with the EU’s VAT in the Digital Age, or ViDA, implementation period.
• The French system is wider than ViDA’s future cross-border reporting framework because it already covers domestic B2B invoice exchange, B2C transaction reporting, international B2B reporting and certain payment data.
• France uses an interoperability model based on private accredited platforms rather than a single central government clearance portal. The model is generally referred to as the Y-model, although the redesign of the PPF means that businesses now exchange invoices exclusively through accredited platforms. [aife.econo…ie.gouv.fr], [legifrance.gouv.fr], [vatupdate.com]

1.4 EU authorisation

• France previously obtained an EU derogation permitting mandatory electronic invoicing without customer consent and departing from Articles 218 and 232 of the VAT Directive.
• Following adoption of ViDA, the long-term EU legal environment is changing. The July 2026 French decree and order also refer to notifications made to the European Commission under Directive (EU) 2015/1535 concerning technical regulations. [legifrance.gouv.fr], [legifrance.gouv.fr]

2. Regulatory Framework

2.1 Primary legislation

The principal provisions are contained in the French General Tax Code, particularly:

• Article 289 bis CGI: mandatory issuance, transmission and receipt of electronic invoices through accredited platforms;
• Article 289 E CGI: transmission of invoice data to the administration;
• Articles 290, 290 A and 290 B CGI: transaction reporting, payment reporting and platform rules;
• Article 1737 CGI: penalties relating to invoice violations, including electronic invoicing;
• Article 123 of Law No. 2026-103 of 19 February 2026, the Finance Law for 2026, which made the final legislative adjustments before implementation. [legifrance.gouv.fr], [legifrance.gouv.fr], [legifrance.gouv.fr]

2.2 Implementing instruments

The most important secondary legislation is:

• Decree No. 2022-1299 of 7 October 2022 and the corresponding ministerial order;
• Decree No. 2024-266 of 25 March 2024, including transitional platform-registration rules;
• Decree No. 2026-677 of 27 July 2026, published on 28 July and effective from 29 July 2026;
• the ministerial order of 27 July 2026, JORF No. 0174, text No. 27. [impots.gouv.fr], [legifrance.gouv.fr], [legifrance.gouv.fr], [legifrance.gouv.fr]

The July 2026 instruments notably:

• replaced “partner dematerialisation platform” terminology with plateforme agréée, or accredited platform;
• removed the PPF as a general invoice-exchange channel;
• formalised interoperability, platform-audit and platform-mobility requirements;
• specified the taxpayer authorisation needed for a platform to maintain routing information in the directory;
• aligned the regulatory provisions with the final 2026 legislative framework. [legifrance.gouv.fr], [legifrance.gouv.fr], [vatupdate.com]

2.3 Administrative guidance

The most current official guidance includes:

• the DGFiP implementation portal, updated on 1 September 2026;
• the start-up practical guide;
• the official FAQ;
• transaction and payment e-reporting fact sheets;
• the August 2026 transmission-frequency guidance;
• external technical specifications version 3.2, dated 30 April 2026;
• AFNOR experimental standards published and updated for the reform. [impots.gouv.fr], [impots.gouv.fr], [impots.gouv.fr], [impots.gouv.fr]

2.4 B2G legal framework

Electronic invoicing for public procurement remains governed by the French Public Procurement Code, especially Articles L.2192-1 to L.2192-7, and continues through Chorus Pro. The new framework provides interoperability between accredited platforms and the public-sector solution for cases involving a public buyer. [legifrance.gouv.fr], [impots.gouv.fr], [legifrance.gouv.fr]

3. Scope of the Mandate

3.1 Domestic B2B

Electronic invoicing applies to supplies of goods and services:

• between taxable persons established in France;
• where the transaction falls within the French VAT invoicing rules;
• including businesses benefiting from the French small-business VAT exemption, because they remain taxable persons even when they are not liable to charge VAT. [economie.gouv.fr], [impots.gouv.fr]

A compliant invoice must:

• contain structured data;
• use a legally supported syntax or profile;
• be transmitted through an accredited platform;
• contain the existing VAT invoice particulars and the additional reform-specific information.

A paper invoice, scanned invoice or ordinary PDF sent by email does not constitute a compliant electronic invoice for an in-scope transaction, except under the temporary business-continuity approach described in Chapter 5. [economie.gouv.fr], [impots.gouv.fr]

3.2 Domestic B2C

• B2C transactions are not subject to mandatory invoice exchange through the B2B network.
• Instead, the supplier reports transaction data, commonly on an aggregated daily basis and split by VAT rate.
• If VAT becomes chargeable on receipt of payment, relevant payment data must also be reported.
• Existing consumer invoicing or receipt requirements continue to apply independently. The reform does not establish a general mandatory consumer QR code. [impots.gouv.fr], [impots.gouv.fr], [impots.gouv.fr]

3.3 Domestic B2G

• Invoices addressed to French public bodies remain subject to B2G electronic invoicing through Chorus Pro.
• Accredited platforms may support B2G flows, but the public-sector solution remains the reference destination.
• The technical documentation expressly covers B2B, government-to-business and business-to-government use cases. [legifrance.gouv.fr], [impots.gouv.fr], [aife.econo…ie.gouv.fr]

3.4 Intra-EU and other cross-border B2B transactions

The following generally fall outside domestic B2B e-invoice exchange but inside transaction e-reporting:

• intra-Community supplies;
• intra-Community acquisitions;
• exports;
• cross-border services;
• transactions with taxable persons not established in France;
• transactions subject to French VAT performed by certain non-established suppliers for non-established or non-taxable customers. [impots.gouv.fr], [impots.gouv.fr]

For these transactions:

• the commercial invoice does not normally have to be routed to the foreign counterparty through the French accredited-platform network;
• prescribed invoice data must instead be submitted to the French administration through an accredited platform;
• the ordinary VAT invoice rules, including reverse-charge or exemption wording, remain applicable.

3.5 Imports

• Imports of goods are excluded from transaction e-reporting because the relevant information is already reported to French Customs and import VAT information is used for the pre-filled import-VAT section of the VAT return.
• Import-related services or other transactions should not automatically be treated in the same manner. Their treatment depends on the nature and VAT location of the supply. [impots.gouv.fr], [impots.gouv.fr]

3.6 Exempt transactions

• Transactions exempt under Articles 261 to 261 E CGI and for which the supplier is exempt from issuing invoices are excluded from e-invoicing and transaction e-reporting.
• The exclusion is tied to the underlying exemption and dispensing-from-invoicing conditions. It should not be interpreted as excluding every zero-rated or exempt transaction. Exports and intra-Community supplies, for example, are generally e-reportable even though no French output VAT is charged. [economie.gouv.fr], [impots.gouv.fr]

3.7 OSS and IOSS

B2C supplies reported through an EU OSS or IOSS scheme are normally excluded from French transaction e-reporting where the non-established operator uses that EU special scheme. This avoids duplicate reporting of information already submitted through the EU one-stop shop. [impots.gouv.fr]

3.8 Special regimes

• Margin-scheme, travel-agent, second-hand-goods and similar transactions are not subject to a general exclusion merely because a special VAT calculation regime applies.
• Their channel depends on the counterparties and place-of-establishment rules:
  • domestic B2B normally requires e-invoicing;
  • B2C or international transactions generally require e-reporting;
  • mandatory special-regime wording and VAT amount restrictions must remain correctly represented.
• Detailed mapping must therefore be performed against the applicable AFNOR use case and French invoice rules. No official publication identified in this review creates a blanket exclusion for these regimes. [impots.gouv.fr], [economie.gouv.fr]

4. Taxable Persons in Scope

4.1 Established entities

The regime covers taxable persons established in France, including:

• companies and partnerships;
• sole traders;
• independent professionals;
• micro-enterprises;
• taxable persons benefiting from the exemption from VAT registration thresholds or franchise en base;
• entities carrying out both taxable and exempt activities, to the extent that transactions fall within the mandate. [economie.gouv.fr], [impots.gouv.fr]

4.2 Fixed establishments

A foreign legal entity with a French fixed establishment can be within the e-invoicing regime where the French establishment intervenes in the transaction and the transaction qualifies as one between taxable persons established in France.

A foreign company’s French VAT number alone is not sufficient to transform it into a person established in France. Establishment and the involvement of the fixed establishment must be assessed under VAT principles.

4.3 VAT-registered but non-established entities

• A foreign taxable person merely registered for French VAT is generally outside the domestic B2B e-invoice exchange obligation.
• It may nevertheless have French transaction-reporting obligations when it performs transactions subject to French VAT with non-taxable customers or taxable customers not established in France.
• A French counterparty may likewise have to report its dealings with that foreign operator as international B2B activity. [impots.gouv.fr], [impots.gouv.fr]

4.4 Voluntary participation

• The legal receiving and issuing obligations are determined by status, establishment and implementation wave.
• Businesses could participate in the pre-launch pilot voluntarily.
• The current framework does not establish a general optional method allowing out-of-scope foreign entities to convert their transactions into mandatory French domestic e-invoices merely by election. Commercial platform services may nevertheless support voluntary structured exchange. [aife.econo…ie.gouv.fr]

5. Implementation Timeline

5.1 Legislative history

• 2017 to 2020: progressive mandatory B2G e-invoicing through Chorus Pro.
• 15 September 2021: Ordinance No. 2021-1190 established the B2B and reporting framework.
• 7 October 2022: initial decree and order.
• 2023: the originally intended 2024 rollout was postponed.
• 29 December 2023: Article 91 of the Finance Law for 2024 established the September 2026 and September 2027 dates.
• 25 March 2024: revised platform-registration decree.
• October 2024: the government announced that the PPF would be limited to the directory and administrative data-concentrator functions.
• 2025: directory and qualification environments opened.
• Early 2026: voluntary real-life pilot.
• 19 February 2026: Finance Law for 2026 enacted.
• 27 to 29 July 2026: final decree and order published and entered into force.
• 1 September 2026: first mandatory wave went live. [impots.gouv.fr], [aife.econo…ie.gouv.fr], [legifrance.gouv.fr], [legifrance.gouv.fr]

5.2 Mandatory dates

From 1 September 2026:

• every in-scope business must be capable of receiving electronic invoices through an accredited platform;
• large enterprises and intermediate-sized enterprises must issue electronic invoices;
• those large and intermediate-sized enterprises must perform applicable transaction and payment e-reporting. [economie.gouv.fr], [economie.gouv.fr]

From 1 September 2027:

• SMEs, very small businesses and micro-enterprises must issue electronic invoices;
• their corresponding transaction and payment e-reporting obligations begin. [economie.gouv.fr], [aife.econo…ie.gouv.fr]

5.3 Soft landing

• The statutory 1 September 2026 date was not postponed.
• The administration announced that no sanctions would be applied during 2026 to businesses encountering genuine implementation difficulties and following a serious compliance trajectory.
• The tolerance does not constitute an exemption. Businesses should continue processing genuine invoices, regularise non-platform invoices promptly and retain evidence of onboarding, testing, defects, remediation and governance. Inertia, deliberate avoidance or lasting refusal to comply may be treated differently. [impots.gouv.fr], [economie.gouv.fr], [presse.eco…ie.gouv.fr]

6. Operating Model

6.1 Architecture

France now operates a decentralised interoperability model involving:

• the supplier;
• the supplier’s accredited platform;
• the customer’s accredited platform;
• the customer;
• the public infrastructure operated for the administration.

The PPF no longer serves as a free general invoice-exchange portal. Its retained functions are:

• central directory management;
• routing information;
• concentration and transmission of fiscal data to the DGFiP. [aife.econo…ie.gouv.fr], [legifrance.gouv.fr], [vatupdate.com]

6.2 Invoice lifecycle

1. The seller creates an invoice in a supported structured or hybrid format.
2. The seller or its compatible software submits it to the seller’s accredited platform.
3. The platform validates syntax, mandatory data, business rules and recipient addressing.
4. Routing information is obtained from the central directory.
5. The invoice is delivered to the buyer’s accredited platform.
6. prescribed invoice data is transmitted to the administration.
7. Lifecycle statuses are exchanged and made available to the parties.
8. Transaction or payment data is reported separately where required.
9. The parties preserve the invoice and related audit evidence. [impots.gouv.fr], [impots.gouv.fr], [legifrance.gouv.fr]

6.3 Validation and rejection

• A technically invalid file may be rejected by a platform before successful delivery.
• Business or commercial rejection by the customer is distinct from technical rejection.
• The AFNOR standards and external specifications define invoice profiles, lifecycle-status messages, APIs and business use cases.
• Taxpayers should distinguish:
  • technical rejection;
  • recipient refusal;
  • disputed invoice;
  • suspended processing;
  • corrective or replacement document. [impots.gouv.fr], [economie.gouv.fr]

6.4 Authentication and platform designation

• Each business must designate an accredited platform.
• The platform requires formal authority to maintain the taxpayer’s routing addresses in the central directory.
• The July 2026 rules prescribe identification details, effective date, address perimeter, signature and record-retention requirements for this authorisation.
• API security, platform identity controls and ISO/IEC 27001-related certification form part of the platform framework. [legifrance.gouv.fr], [legifrance.gouv.fr]

6.5 Contingency arrangements

The start-up guidance prioritises continuity:

• genuine invoices received by PDF, email or paper should not be rejected solely because the platform channel temporarily failed;
• the alternative format does not become the compliant target method;
• affected invoices and tax data should be routed or regularised through the appropriate electronic process as soon as possible;
• evidence of the failure and remediation should be retained. [impots.gouv.fr], [economie.gouv.fr]

No general QR-code-based offline invoicing mechanism comparable to certain clearance jurisdictions has been identified in current French guidance.

6.6 Buyer acceptance

• Commercial acceptance by the buyer is not a condition for the invoice to exist as a VAT document.
• Buyer statuses support workflow visibility, dispute handling and payment monitoring.
• The reform changes the transmission channel but not the underlying rules on the existence of the transaction, the commercial debt, accounting, payment or VAT deduction. [impots.gouv.fr], [economie.gouv.fr]

7. Acceptable E-Invoice Formats

7.1 Core formats

The French minimum interoperability framework supports:

• UBL;
• UN/CEFACT Cross Industry Invoice, or CII;
• Factur-X, a hybrid PDF/A-3 file containing embedded structured XML.

The formats are aligned with EN 16931 and the French extended profile known as EXTENDED-CTC-FR. [impots.gouv.fr], [vatupdate.com]

7.2 Other formats

• Accredited platforms may exchange other structured formats bilaterally when they can preserve and convert all legally required data.
• Each platform must be capable of supporting the mandatory minimum semantic and interoperability framework.
• A plain PDF, image, Word file or spreadsheet is not a compliant electronic invoice for an in-scope transaction once the obligation applies, subject only to temporary continuity guidance. [economie.gouv.fr], [impots.gouv.fr]

7.3 Attachments

Attachments can accompany an electronic invoice where supported by the applicable syntax and platform. They do not replace mandatory structured invoice fields. Purchase orders, delivery evidence and supporting PDFs should therefore be treated as supplementary documents unless the applicable invoice specification expressly incorporates their data.

8. Technical and Functional Requirements

8.1 Invoice information

A French e-invoice must contain the ordinary mandatory VAT-invoice information, including as applicable:

• invoice date and unique sequential number;
• supplier name, address, VAT number and legal identification;
• customer name, address and VAT identification;
• description, quantity and date of supplies;
• unit price, discounts and taxable amount;
• VAT rate, VAT amount and totals;
• exemption or reverse-charge basis;
• payment terms and due date;
• references to advance invoices, credit notes or original invoices;
• special-regime wording.

Four additional data points highlighted for the reform are:

• customer SIREN;
• transaction category, namely goods, services or both;
• option for VAT payment on debits, where applicable;
• delivery address where different from the customer’s billing address. [economie.gouv.fr], [impots.gouv.fr]

8.2 Technical standards

The current authoritative framework includes:

• XP Z12-012: invoice and lifecycle-status formats and profiles;
• XP Z12-013: APIs connecting business information systems and accredited platforms;
• XP Z12-014: French B2B use cases;
• external specifications version 3.2, dated 30 April 2026, including schemas, examples, XSD files and Swagger documentation. [impots.gouv.fr], [aife.econo…ie.gouv.fr]

8.3 E-reporting content

For international B2B transactions, the information broadly corresponds to prescribed invoice data, excluding the domestic SIREN requirement where inappropriate.

For B2C transactions, reports generally contain aggregated daily turnover:

• reporting period;
• transaction date or aggregation date;
• taxable amount;
• VAT rate;
• VAT amount;
• transaction category;
• relevant currency or country information where required.

For payment reporting, required information includes:

• supplier SIREN;
• collection date;
• amount collected;
• reporting period;
• allocation by VAT rate;
• invoice reference where connected with an electronic invoice. [impots.gouv.fr], [impots.gouv.fr], [impots.gouv.fr]

8.4 E-reporting frequency

The frequency depends on the taxpayer’s VAT regime:

• normal monthly regime: transaction reporting by ten-day periods, with deadlines generally 10 days after each period;
• quarterly normal regime: generally monthly by the tenth day of the following month;
• simplified regime: generally monthly between the 25th and 30th of the following month;
• franchise-en-base businesses: generally every two calendar months, due between the 25th and 30th after the period;
• payment reporting is generally monthly or bimonthly according to the VAT regime. [impots.gouv.fr], [impots.gouv.fr]

This is a periodic near-real-time model, not universal invoice-by-invoice real-time clearance.

8.5 Signatures and integrity

• A qualified signature on every invoice is not generally mandatory under the reform.
• Authenticity, integrity and readability must nevertheless be guaranteed.
• The accredited-platform transmission process, structured exchange, lifecycle evidence and audit controls support those safeguards.
• Outside the mandatory platform process, French law continues to recognise reliable audit trails, qualifying electronic-signature methods and compliant EDI arrangements. [bofip.impots.gouv.fr], [impots.gouv.fr]

9. Corrections

9.1 Invoice corrections

After a legally issued invoice has been delivered, substantive tax or commercial errors should generally be corrected through:

• a credit note;
• a corrective invoice;
• cancellation and reissuance where legally and technically appropriate.

The corrective document should contain:

• its own unique number and issue date;
• an explicit reference to the original invoice;
• the reason and scope of correction;
• corrected taxable amounts and VAT;
• any mandatory VAT wording.

The correction must pass through the accredited-platform workflow if the underlying transaction is subject to domestic B2B e-invoicing.

9.2 Technical errors

• A file rejected before successful transmission should be corrected and resubmitted.
• A duplicate invoice number should not be reused merely because the first submission failed unless the technical rules clearly establish that the invoice was never issued.
• Businesses should reconcile ERP status, platform status and customer status to prevent duplicates or missing tax data.

9.3 E-reporting corrections

• Incorrect e-reporting should be corrected using the correction or replacement mechanisms defined in the platform and technical specifications.
• If the error also affected a VAT return, the e-reporting correction does not by itself replace the need to correct the VAT return.
• No separate universal paper form has been identified for e-reporting corrections. Corrections are transmitted electronically through the accredited platform.
• Detailed correction codes, message structures and validation rules are contained in the current specifications and Schematron rather than a single narrative government form. [impots.gouv.fr], [vatupdate.com]

10. Transmission and Workflow

10.1 Accredited platforms

Accredited platforms are responsible for:

• issuing, transmitting and receiving electronic invoices;
• format conversion without loss of mandatory data;
• extracting and transmitting fiscal invoice data;
• transmitting transaction and payment reports;
• updating routing information under taxpayer authority;
• exchanging lifecycle statuses;
• maintaining required security and audit controls. [impots.gouv.fr], [legifrance.gouv.fr]

The official register is published and regularly updated by the DGFiP through its e-invoicing portal. [economie.gouv.fr]

10.2 Compatible solutions

An ERP, billing tool, cash-register system or accounting application may connect to an accredited platform as a solution compatible. Such software is not itself an accredited platform unless formally registered as one. Legal transmission remains the responsibility of the accredited-platform layer. [economie.gouv.fr], [impots.gouv.fr]

10.3 Peppol

France’s legal architecture does not make Peppol the exclusive transmission network. An accredited platform may use Peppol or another qualified interoperability network, but it must still meet the French directory, data, status, security and platform obligations.

10.4 General invoicing deadlines

The reform changes the method of transmission, not the substantive French rules determining when an invoice must be issued. Existing VAT invoicing deadlines therefore continue to apply.

11. Self-Billing

11.1 Permissibility

Self-billing, or autofacturation, remains permitted under French VAT law where:

• a prior agreement exists between supplier and customer;
• an acceptance procedure applies to each invoice or invoice series;
• the supplier retains responsibility for VAT invoicing compliance.

11.2 Treatment under the mandate

• If the underlying transaction is domestic B2B and both parties are established in France, the self-billed invoice must follow the electronic-invoicing platform process.
• The invoice must be attributed to the supplier even though it is technically produced by the customer or its agent.
• The structured invoice must use the relevant self-billing indicator and contain the legally required“Autofacturation” wording.
• Routing, fiscal reporting and lifecycle statuses must reflect the legal supplier and customer roles rather than merely the party generating the file.

11.3 Foreign buyers

Where a foreign buyer issues an invoice on behalf of a French supplier:

• the domestic platform treatment depends on whether the underlying transaction qualifies as domestic B2B;
• if the buyer is not established in France, the transaction may instead fall within international B2B e-reporting;
• the self-billing agreement remains necessary.

The current public guidance does not establish a separate pre-notification form specifically for self-billing under the reform. Businesses should document the mandate, approval process and platform role carefully.

12. Triangulation and Special Scenarios

12.1 Triangulation

Each legal supply in a triangular transaction must be classified separately:

• supplier and customer establishment;
• place of supply;
• VAT identification used;
• exemption or reverse-charge mechanism;
• whether the leg is domestic B2B or international B2B.

A French VAT number alone does not necessarily turn an international triangular leg into a domestic French e-invoice. If a leg involves a non-established counterparty, it will generally be e-reported rather than routed as a domestic electronic invoice.

French invoice rules require specific references where the EU triangulation simplification is applied, including the relevant indication linked to Article 141 of Directive 2006/112/EC. [bofip.impots.gouv.fr]

12.2 Chain transactions

• The physical movement of goods does not determine the reporting channel by itself.
• Each invoicing leg must be assessed separately.
• Only a leg satisfying the domestic B2B conditions enters mandatory electronic invoice exchange.
• Other legs may require international transaction reporting, EC Sales List reporting, Intrastat or Customs reporting.

12.3 Reverse charge

• Outbound invoices subject to reverse charge must carry the required reverse-charge wording and appropriate structured tax-category code.
• International reverse-charge supplies are generally e-reported by the French-established supplier.
• For inbound services received from a foreign supplier, the French customer’s reporting treatment depends on the precise scope of the acquisition-reporting rules.
• Payment e-reporting is not required where the transaction is subject to reverse charge. [impots.gouv.fr], [impots.gouv.fr]

12.4 Zero-rated and exempt supplies

• Exports and intra-Community supplies are normally transaction-reportable and must carry the appropriate exemption code or legal reference.
• Transactions exempt under Articles 261 to 261 E and dispensed from invoicing are outside the reform.
• Businesses must therefore avoid using a single “zero-rate” classification for all non-taxed transactions. [impots.gouv.fr], [bofip.impots.gouv.fr]

12.5 VAT groups

VAT groups, fixed establishments, fiscal representatives and shared-service invoicing arrangements require entity-level mapping of:

• SIREN and SIRET;
• VAT identification;
• invoice issuer;
• legal supplier;
• invoice recipient;
• platform routing address;
• reporting responsibility.

The official standards contain specialised business cases, but the facts of each arrangement must be mapped individually against XP Z12-014. [impots.gouv.fr]

13. Archiving and Retention

13.1 Retention period

French tax records, including invoices, accounting documents and supporting evidence, must currently be retained for ten years under the version of Article L.102 B of the Tax Procedures Code effective from 27 June 2026. Electronic records must remain in electronic form throughout the applicable period. [legifrance.gouv.fr]

From 1 January 2027, Article L.102 B bis separately confirms that invoice storage must guarantee:

• authenticity of origin;
• integrity of content;
• readability throughout the retention period. [legifrance.gouv.fr]

13.2 Format

• The original structured invoice and associated legally relevant data should be retained.
• A human-readable PDF rendition alone should not replace the original structured data where the invoice was created or received electronically.
• Lifecycle statuses, correction documents, attachments forming part of the audit evidence and proof of platform transmission should also be preserved.

13.3 Platform storage

• Platform storage does not automatically discharge the taxpayer’s legal archiving responsibility.
• Contracts should address data export, retention, termination, platform mobility and access after provider failure.
• The directory-authorisation agreement must itself be retained by the accredited platform for three years after it ceases to have effect. [legifrance.gouv.fr]

13.4 Storage location and access

No general domestic-only storage requirement was identified in the current materials. Nevertheless:

• data must be rapidly accessible to the French tax administration;
• storage outside France must not prevent audit access, readability or production;
• GDPR, professional secrecy, cybersecurity and international-transfer requirements remain independently applicable.

14. Penalties and Enforcement

14.1 Failure to issue an electronic invoice

From 21 February 2026, Article 1737(III) CGI provides for:

• €50 per invoice for failure to issue an electronic invoice in accordance with Article 289 bis;
• an annual cap of €15,000. [legifrance.gouv.fr]

14.2 Invoice omissions and inaccuracies

Article 1737(II) CGI provides:

• €15 for each omission or inaccuracy in an invoice or equivalent document;
• the total for each invoice cannot exceed one quarter of the amount stated or that should have been stated. [legifrance.gouv.fr]

14.3 Fictitious invoices and failure to invoice

Article 1737 also contains materially higher sanctions for:

• invoices not corresponding to genuine supplies;
• concealed or fictitious supplier or customer identities;
• failure to issue and record transactions.

Depending on the violation, penalties may be calculated as a percentage of the invoice or transaction amount, with specific annual caps and possible customer joint liability. [legifrance.gouv.fr]

14.4 E-reporting and platform failures

Separate sanctions apply under the CGI for failure to transmit transaction, invoice or payment data and for platform non-compliance. The precise amount depends on the responsible person and obligation. Businesses should distinguish:

• taxpayer failure to report;
• incomplete or inaccurate reporting;
• platform failure to transmit data received from a customer;
• directory, registration or accreditation failures.

14.5 Enforcement approach in 2026

• The government announced no sanctions in 2026 for companies facing implementation difficulties while pursuing a serious compliance trajectory.
• This is an administrative tolerance, not a postponement or legislative repeal of penalties.
• Evidence should include project plans, platform contracts, test results, unresolved defects, fallback procedures, invoice regularisation and management oversight. [impots.gouv.fr], [presse.eco…ie.gouv.fr]

14.6 Archiving violations

Failure to retain or produce records can lead to procedural penalties, evidentiary consequences and potential challenges to VAT deductions. Fraudulent conduct remains subject to the wider French tax-penalty regime and cannot rely on implementation tolerance.

15. Pre-Filled VAT Returns

15.1 Current position

France does not yet offer a fully pre-filled periodic VAT return based comprehensively on the new e-invoicing and e-reporting flows.

A limited exception already exists for import VAT: information derived from Customs declarations is used to pre-fill relevant import-VAT amounts. [impots.gouv.fr]

15.2 Planned development

Pre-filling VAT returns is an explicit reform objective. Invoice, transaction and payment data are intended eventually to support:

• taxable amounts by rate;
• output VAT;
• VAT chargeability for services taxed on collection;
• certain cross-border transaction fields;
• consistency checks.

No complete official implementation date or definitive list of pre-filled fields for the general VAT return has been published in the sources reviewed. Taxpayers must therefore continue to calculate, review and submit their VAT returns independently. [aife.econo…ie.gouv.fr], [impots.gouv.fr]

15.3 Risk consideration

E-invoicing or e-reporting data will not necessarily equal VAT-return data because of:

• timing adjustments;
• partial payments;
• bad debts;
• imports;
• self-assessed VAT;
• corrections;
• mixed-use and deduction restrictions;
• transactions reported through OSS or IOSS.

Reconciliation controls will remain essential even after pre-filling becomes available.

16. ViDA Readiness

16.1 Alignment

France is broadly aligned with ViDA in several areas:

• structured electronic invoicing;
• reliance on EN 16931-compatible semantic data;
• transaction-level digital reporting;
• reduced dependence on buyer consent;
• interoperability rather than a single mandatory state clearance portal.

16.2 Areas requiring future adjustment

France may have to adjust:

• reporting deadlines for intra-EU transactions;
• the precise ViDA dataset;
• treatment of corrections and transaction statuses;
• interaction between French platforms and the future EU central VIES environment;
• removal or modification of national reporting elements that overlap with harmonised EU reporting.

The French system currently reports B2B international transactions according to national periodic frequencies, while ViDA’s cross-border DRR is designed around harmonised transaction-level reporting from 1 July 2030. The two regimes should not be assumed to be technically identical.

16.3 Business implications

Businesses should:

• separate France-specific and EU-common data in their architecture;
• use EN 16931-compatible canonical models;
• retain transaction-level detail even where France permits aggregation;
• avoid hard-coding French platform logic into core ERP systems;
• build reusable rules for establishment, place of supply, reverse charge and transaction classification.

17. Impact on SMEs and Startups

17.1 Phased onboarding

SMEs, very small businesses and micro-enterprises:

• had to be capable of receiving e-invoices from 1 September 2026;
• must issue e-invoices and perform e-reporting from 1 September 2027. [economie.gouv.fr], [aife.econo…ie.gouv.fr]

There is no general turnover exemption from the receiving obligation. Businesses under the franchise-en-base regime remain covered. [economie.gouv.fr]

17.2 Available support

Support includes:

• official guidance and FAQs;
• a public directory search service;
• the official register of accredited platforms;
• a national assistance number;
• guidance through accountants, chambers of commerce, professional federations and France Num advisers. [economie.gouv.fr], [aife.econo…ie.gouv.fr]

The redesigned model does not provide a universal free government invoice-creation and exchange portal for private B2B invoicing. A small business may therefore need to use a commercial accredited platform, although some providers may offer free or low-cost entry packages.

17.3 Costs

Likely one-off costs include:

• selecting and onboarding a platform;
• cleaning supplier and customer master data;
• adapting billing or accounting software;
• configuring tax and transaction codes;
• training employees;
• testing invoice, credit-note and e-reporting scenarios.

Ongoing costs may include:

• platform fees;
• integration and support;
• archive services;
• exception management;
• regulatory updates.

17.4 Benefits

Potential benefits include:

• reduced manual entry;
• fewer lost invoices;
• faster processing;
• better payment-status visibility;
• earlier error detection;
• improved cash collection;
• standardisation and automation. [economie.gouv.fr], [presse.eco…ie.gouv.fr]

17.5 Net assessment

For digitally mature SMEs, the reform can simplify invoicing and bookkeeping. For micro-enterprises with low invoice volumes, the fixed cost and need to choose a private platform may outweigh immediate efficiency gains. The one-year delay for issuance reduces implementation pressure but does not remove the need to receive invoices from 2026.

No general national subsidy or tax credit specifically covering accredited-platform costs was identified in the current official materials.

18. Official References and External Sources

18.1 Government portals

• [DGFiP e-invoicing implementation portal]
• French Ministry of Economy overview
• AIFE B2B e-invoicing page
• Official technical specifications and standards
• Official legal-document repository
• Accredited-platform information

18.2 Principal legislation

• Decree No. 2026-677 of 27 July 2026
• Ministerial order of 27 July 2026
• Article 1737 CGI, invoicing penalties
• Article L.102 B, tax-record retention
• Article L.102 B bis, invoice authenticity, integrity and readability
• Public Procurement Code e-invoicing provisions

18.3 Technical and reporting guidance

• External specifications, version 3.2 and AFNOR standards
• Official transaction e-reporting guidance
• Official payment e-reporting guidance
• Official reporting frequencies and deadlines
• Official start-up guide

18.4 Advisor and specialist commentary

• VATupdate July 2026 reform summary
• Esker France compliance overview

Some unofficial publications still describe the PPF as a free invoice-exchange channel or use obsolete rollout dates. Those statements should be treated as outdated where they conflict with the July 2026 legislation and September 2026 official guidance.

19. Summary and Key Takeaways

19.1 Scope

• Domestic B2B transactions between taxable persons established in France are subject to structured e-invoicing.
• B2C and international B2B transactions generally fall under e-reporting.
• Imports of goods and certain exempt, non-invoiced transactions are excluded.
• B2G invoicing continues through Chorus Pro.

19.2 Format

• The minimum formats are UBL, CII and Factur-X.
• The framework is based on EN 16931 and French AFNOR standards.
• A plain PDF is not the target-compliant format for mandatory domestic B2B e-invoicing.

19.3 Timeline

• 1 September 2026: universal receiving obligation; large enterprises and ETIs must issue and report.
• 1 September 2027: SMEs, very small businesses and micro-enterprises must issue and report.
• The administration applies a good-faith tolerance during the 2026 start-up period, but the legal obligations are already effective. [economie.gouv.fr], [presse.eco…ie.gouv.fr]

19.4 Operating model

• Invoices are exchanged through accredited private platforms.
• The public infrastructure provides the central directory and concentrates tax data.
• The PPF is not a general free B2B invoice-exchange portal.

19.5 Principal obligations

Businesses must be able to:

• receive and route structured invoices;
• issue compliant invoices when their wave applies;
• report B2C and international transactions;
• report collections where VAT is chargeable on payment;
• process lifecycle statuses and corrections;
• retain structured originals and supporting evidence for ten years.

19.6 Main risks

The principal risks are:

• incorrect establishment and scope determination;
• inaccurate platform routing;
• incomplete master data;
• failure to distinguish e-invoice, transaction-reporting and payment-reporting flows;
• inconsistent ERP, platform and VAT-return data;
• incorrect treatment of self-billing, chains and reverse charges;
• reliance on temporary enforcement tolerance;
• inadequate archiving or platform-exit arrangements.

19.7 Recommended next steps

• Confirm the accredited platform and every SIREN/SIRET routing address.
• Validate all invoice and credit-note scenarios against the latest standards.
• Map domestic B2B, B2C, international B2B and import flows separately.
• Reconcile platform fiscal data with ERP postings and VAT returns.
• Establish controls for payment reporting and partial settlements.
• Document fallback and retrospective regularisation procedures.
• Retain evidence demonstrating the compliance trajectory during the 2026 tolerance period.
• Maintain a regulatory workstream for the 1 September 2027 SME wave and 1 July 2030 ViDA cross-border reporting date.