E‑Invoicing & E‑Reporting Mandate — Get yourself updated with developments in July 2026

1. France Approves 2026 E‑Invoicing and E‑Reporting Rules with Penalties

2 July 2026

• • France confirmed that mandatory B2B e‑invoicing and transactional e‑reporting start on 1 September 2026, adopted under the 2026 Finance Bill. All established businesses must be able to receive structured electronic invoices from day one, while obligations to issue invoices and transmit e‑reporting data phase in by company size, cementing the long‑anticipated timeline after years of legislative preparation, consultation, and successive postponements. [vatupdate.com]
  • The reform operates through the Y‑model, requiring taxable persons to route invoices via accredited Partner Dematerialisation Platforms rather than the withdrawn public portal. Accepted structured formats include Factur‑X, UBL, and CII for interoperability. Businesses must select and onboard a certified platform, align master data, and adapt ERP output to the mandated syntaxes well ahead of the go‑live to avoid transaction disruption and rejected invoices. [vatupdate.com]
  • A soft‑landing enforcement approach accompanies the launch, applying penalties leniently while systems stabilise. Sanctions nonetheless exist for failing to issue compliant invoices or submit e‑reporting data. Companies are urged to treat the transition seriously despite the tolerance, since the underlying legal obligations take full effect immediately and audit exposure grows once the initial ramp‑up window closes at the end of 2026. [vatupdate.com]

2. France E‑Invoicing Specifications Updated for 2026

10 July 2026

• • France released updated technical specifications, with AFNOR standards XP Z12‑012, XP Z12‑013, and XP Z12‑014 replacing the February 2026 versions. These norms define the semantic model, standardised APIs, and business use cases for compliant e‑invoicing, ensuring platforms and businesses work from a single current reference. The refresh reflects pilot feedback and tightens definitions ahead of the September go‑live to reduce interpretation gaps and divergence across operators. [vat-valida…atfaqs.com]
  • The revised standards govern how invoices are structured across accepted Factur‑X, UBL, and CII formats, covering mandatory fields, coding rules, and validation logic. Software vendors and platforms must align to the latest versions to guarantee interoperability. Businesses relying on third‑party platforms should confirm their provider has implemented the July 2026 specifications rather than deprecated drafts before completing conformance and acceptance testing. [vat-valida…atfaqs.com]
  • Because specifications changed close to go‑live, timing is a practical risk: teams must ensure ERP outputs, mapping tables, and validation routines reference the July 2026 norms. The update underscores the need to monitor official releases continuously, as late technical changes can invalidate earlier configurations. Companies should re‑run conformance tests against the newest standards to avoid rejected invoices once the mandate becomes active in September. [vat-valida…atfaqs.com]

3. France Confirms E‑Invoicing Mandate from 1 September 2026 with Soft‑Landing Enforcement

18 July 2026

• • The DGFiP’s 10 July guidance decisively dispels persistent rumours of a further deferral, confirming the 1 September 2026 start stands. What has softened is enforcement, not the timeline: authorities will apply penalties leniently during an initial period to let businesses stabilise. The message is unambiguous — companies should not interpret the flexibility as permission to delay their onboarding, platform selection, and system‑readiness work ahead of go‑live. [kpmg.com]
  • The guidance frames the soft‑landing as a pragmatic transition tool, acknowledging that platform onboarding and system integration take time. Minor errors and gaps are treated with tolerance during this window, provided businesses demonstrate genuine compliance efforts. However, the legal obligations to receive invoices, and progressively to issue and report, remain fully in force from the launch date, preserving the reform’s integrity, momentum, and audit‑trail foundations. [kpmg.com]
  • For finance teams, the confirmation removes planning uncertainty and validates continued investment in platform selection, ERP alignment, and staff training. The practical takeaway is to complete core readiness before September while using the grace period only for refinement. Businesses that treat the soft‑landing as a deadline extension risk falling behind once full enforcement begins and audit scrutiny intensifies from early 2027. [kpmg.com]

4. AIFE Finally Publishes a Schematron for Flux 10 (E‑Reporting)

27 July 2026

• • AIFE released the long‑awaited official Schematron validation tool for Flux 10, the e‑reporting flow covering B2C transactions, international sales, and payment data. This closes a significant gap, giving software vendors and businesses an authoritative reference to test their e‑reporting submissions against mandated rules. Until now, the absence of a validated Schematron created uncertainty around how Flux 10 data would be checked and accepted by Approved Platforms and the administration. [vatcalc.com]
  • The Schematron encodes the business and structural rules for Flux 10, enabling automated conformance checking before transmission. Platforms and ERP integrators can now validate field completeness, coding accuracy, and logical consistency, reducing the risk of rejected reports at go‑live. Its late arrival compresses testing timelines, so teams handling B2C or cross‑border flows must prioritise integrating and running these validations promptly to confirm compliant submissions. [vatcalc.com]
  • For businesses with significant B2C, export, or import activity, Flux 10 is the critical e‑reporting stream, making this tool essential to readiness. The publication signals the technical scaffolding for e‑reporting is maturing, but also highlights how close to the deadline key components are being finalised. Companies should incorporate the Schematron into their test cycles immediately to avoid failures once the reporting obligation applies. [vatcalc.com]

5. France Extends VAT Record Retention to 10 Years(Archiving)

29 July 2026

• • France will extend VAT and tax record retention from six to ten years starting 1 January 2027 under Law No. 2026‑534 of 25 June 2026 on combating social and tax fraud. Article 36 amends Article L.102 B of the Tax Procedures Code, aligning retention with the administration’s longer audit powers. The measure dovetails directly with the phased B2B e‑invoicing mandate, intensifying archiving demands on businesses and their systems. [vatupdate.com]
  • The rule applies to records still within the old retention period, extending their preservation to the full ten years — for example, a 2024 invoice must now be kept far longer than previously required. It covers invoices, accounting records, supporting evidence, reliable audit‑trail documentation, and digital archives, all of which must remain readable, searchable, and securely producible to the French tax authorities throughout the extended retention period. [vatupdate.com]
  • Non‑compliance or premature destruction can trigger penalties for missing or prematurely destroyed documents. Businesses must update ERP and document‑management systems to preserve original invoice data, formats, lifecycle status information, and audit evidence for a decade. As structured e‑invoicing generates richer datasets, archiving strategy becomes a core compliance workstream rather than an afterthought, requiring early alignment with platform and integration decisions. [vatupdate.com]

6. French Tax Authorities Publish Guidance on the September 2026 E‑Invoicing Mandate

29 July 2026

• • The DGFiP issued transitional guidance introducing pragmatic simplifications for the reform’s early phase. Notably, it confirms that PDF and paper invoices remain valid and VAT‑deductible during the ramp‑up period, easing pressure on businesses still completing platform onboarding. This tolerance acknowledges operational realities while preserving the mandate’s legal force, allowing trade to continue smoothly as structured e‑invoicing capabilities are progressively deployed across the French economy. [e-invoice.app]
  • The guidance details how legacy invoice formats are treated during transition, protecting buyers’ input‑VAT recovery where structured invoices are not yet fully operational. It sets expectations for how and when businesses should migrate to compliant formats, framing the simplifications as temporary bridges rather than permanent exemptions. Finance teams should document their transition approach to demonstrate good‑faith compliance during any subsequent tax review or audit. [e-invoice.app]
  • Practically, the guidance reduces the immediate risk of blocked VAT deductions and invoice disputes at go‑live, but does not remove the obligation to move to structured e‑invoicing. Businesses should use the window to finalise platform integration, validate formats, and phase out paper and unstructured PDFs. Relying on the transitional measures beyond their intended scope would expose companies to compliance gaps once full requirements apply. [e-invoice.app]

7. France’s E-Invoicing Rulebook Is Complete: Decree No. 2026-677 and the Order of 27 July 2026

29 July 2026

• • The two final texts completing France’s e‑invoicing reform — Decree No. 2026‑677 and the Order of 27 July 2026 — were published in the Journal officiel on 28 July 2026 and took effect on 29 July. They amend the texts of 9 October 2022 (as modified in March 2024) and bring secondary legislation into line with Article 123 of the 2026 Finance Law, delivering long‑awaited legal certainty just weeks before the 1 September Wave 1 go‑live. [vatupdate.com], [sovos.com]
  • Substantively, the texts formally abolish the PPF as an exchange route, moving to a fully Approved‑Platform‑centric ecosystem, and anchor the format baseline around EN 16931 and the EXTENDED‑CTC‑FR profile per XP Z12‑012, with explicit references to XP Z12‑013 (APIs) and XP Z12‑014 (use cases). The Order also updates deadlines, replacing 1 July 2024 with 1 September 2026, and 1 January 2026 with 1 September 2027. [sovos.com], [e-invoice.app]
  • The framework codifies platform mobility — formal switching agreements, binding deadlines, and one‑year minimum service continuity on the outgoing platform — plus directory‑information safeguards requiring signed taxpayer authorisation. A new mid‑cycle audit for Approved Platforms is introduced between registration and three‑yearly renewal, alongside adjusted registration requirements and refined invoice and e‑reporting data fields, strengthening governance and taxpayer protection across the ecosystem. [sovos.com], [kpmg.com]

8. France’s Mandatory E‑Invoicing Penalties Explained

1 August 2026

• • This post breaks down the penalty regime by obligation, distinguishing sanctions for failing to issue a compliant electronic invoice from breaches of e‑reporting duties, each subject to annual caps. It situates the fines within the reform’s legal architecture, clarifying that the amounts are designed to balance deterrence with proportionality while giving businesses a clear picture of their maximum financial exposure under the new rules. [ey.com]
  • The article situates penalties within the soft‑landing context, explaining that authorities exercise leniency during the initial transition while retaining power to sanction persistent or deliberate non‑compliance. It clarifies which party bears responsibility for each failure across the issuing, receiving, and reporting chain, helping businesses assign internal ownership and design controls that prevent the specific breaches triggering each category of fine. [ey.com]
  • For finance and tax leaders, the penalty structure reinforces the case for early, thorough preparation. Understanding the per‑transaction nature of certain fines highlights how quickly liabilities accumulate at scale for high‑volume businesses. The post recommends embedding validation, monitoring, and exception‑handling controls into invoicing and reporting workflows to minimise errors, demonstrate diligence, and limit both financial penalties and reputational risk. [ey.com]