Article about the 2026 French electronic invoicing reform, business obligations, accredited platforms, Factur-X EN16931, XSD, Schematron and PDF/A-3.
The electronic invoicing reform will progressively come into effect starting in September 2026. However, many SMEs, small businesses, and self-employed structures still believe they have plenty of time to prepare. In reality, the first obligations are arriving quickly and already concern all VAT-registered businesses, including companies that issue only a small number of invoices or still rely on simple processes.
This reform is not limited to invoice issuance. It also changes how companies will receive, transmit, and process invoices in their daily operations.
Starting on September 1st, 2026, all VAT-registered businesses in France will be required to receive electronic invoices through an approved platform. This obligation applies regardless of company size.
This means that an SME receiving invoices from suppliers must already have a compatible system in place in order to continue receiving invoices under the new framework.
Then, starting on September 1st, 2027, the obligation to issue electronic invoices will extend to SMEs, small businesses, and self-employed companies. At that stage, affected businesses will need to generate invoices using a structured format recognized by the reform.
Many companies assume they are not immediately affected because they issue only a limited number of invoices or still use standard PDF files. In practice, the first impact will often come from suppliers.
An SME regularly receives invoices from partners, service providers, or suppliers subject to VAT. From September 2026, those suppliers will be required to transmit invoices through an approved electronic invoicing platform.
Without a compatible receiving solution, those invoices may no longer be properly received within the framework defined by the reform. The reception obligation therefore concerns all VAT-registered businesses, including the smallest structures.
The reform does not impose a single format. Three formats are officially accepted: Factur-X, UBL, and CII.
In practice, Factur-X has progressively become the dominant standard for B2B invoicing in France. This hybrid format combines a human-readable PDF with a structured XML file embedded directly inside the document.
The advantage is twofold: the recipient can continue reading the invoice like a standard document, while accounting systems and software can automatically process the structured data for integration and automation purposes.
UBL and CII are primarily XML-only formats without a native visual representation. They are still used in certain international or technical environments, but remain far less common in everyday exchanges between French SMEs.
A standard PDF sent by email will no longer be considered compliant for B2B exchanges between VAT-registered businesses. Even a well-designed PDF containing all mandatory legal information is no longer sufficient on its own.
What now matters is the structure of the embedded data, its compliance with the EN16931 standard, and its transmission through an approved electronic invoicing platform.
Until July 2025, the official term used in France was “Partner Dematerialization Platforms” (PDP). The terminology has since changed: they are now officially called “Approved Platforms” (PA). The role remains the same, only the naming has evolved.
These platforms are officially registered by the French tax administration (DGFiP). As of February 16th, 2026, 108 platforms had obtained definitive registration after successfully completing interoperability testing with the Public Invoicing Portal infrastructure.
An Approved Platform receives the issued invoice, transmits it to the recipient’s platform, extracts fiscal data, and forwards the required information to the tax administration. It is responsible for ensuring interoperability between all participants in the electronic invoicing ecosystem.
In practice, the issuer does not need to know which platform the recipient uses. The invoice is simply transmitted to the issuer’s own platform, which automatically routes it to the correct destination through the centralized directory system.
Only one Approved Platform is required. Businesses do not need multiple providers. The decision should primarily be based on platform stability, API quality when automation or software integration is planned, and the pricing model proposed by the provider.
The Public Invoicing Portal initially announced as a free operational option will no longer serve as a direct issuance and reception channel. Using a private Approved Platform is now mandatory.
Generating a Factur-X file alone is not enough to guarantee compliance. To be considered compliant, the file must successfully pass three separate validation levels covering technical structure, semantic consistency, and fiscal conformity.
The XSD defines the structural schema of the embedded XML file inside the Factur-X document. It verifies that the structure follows the expected standard, that all mandatory fields are present, and that the data types used are valid.
This validation represents the first level of technical compliance. It is mandatory, but it does not guarantee by itself that a file is fully compliant and operational.
Schematron validates business rules and overall data consistency. It ensures that totals are coherent, that VAT rates match the declared calculations, and that all required legal identifiers are correctly provided.
A file can successfully pass XSD validation while still failing Schematron validation. This is often where functional inconsistencies are detected.
The PDF used in a Factur-X invoice must comply with the PDF/A-3 standard dedicated to long-term archiving. This standard guarantees that the document remains readable and usable over time, regardless of future software evolution.
It is also the standard that allows the structured XML file to be embedded directly inside the PDF in a compliant manner.
The first approach consists of generating the Factur-X directly from the business source data. The XML is created at the same time as the invoice itself, using the original invoicing data.
This is the cleanest and most reliable method because the data remains coherent by design. Invoice lines, totals, VAT calculations, and legal information all originate from the same source.
The second approach consists of analyzing an existing PDF in order to extract its content and rebuild a mirrored XML structure. While technically possible, this method is significantly more risky.
A single extraction error, misinterpreted value, or ambiguous field can cause the validation process to fail. This approach introduces multiple points of friction without guaranteeing a compliant result.
Generating a technically valid Factur-X file is not always enough to guarantee full compliance. Fiscal information and VAT rules applied to the invoice remain equally important.
Requirements may vary depending on the client’s country, VAT status, and invoicing context. An invoice issued to a French client, an EU business with a valid VAT number, or a customer located outside the European Union does not follow exactly the same fiscal rules.
Certain situations require specific legal mentions such as reverse charge VAT mechanisms, VAT exemption references related to article 293 B of the French Tax Code for micro-businesses, or export-related mentions for transactions outside the European Union.
EN16931 compliance and the presence of a structured XML file do not replace the fiscal obligations applicable to the transaction itself.
A file can successfully pass XSD, Schematron, and PDF/A-3 validations while still containing incorrect VAT mentions or fiscal information inconsistent with the client’s actual situation.
Real compliance therefore depends both on the technical structure of the document and on the accuracy of the fiscal information displayed on the invoice.
A professionally designed PDF containing all mandatory legal information is not automatically a Factur-X invoice. The difference is invisible to the human eye, but it is critical for approved electronic invoicing platforms.
Without an embedded and properly validated XML structure, the invoice will not be recognized as compliant under the reform requirements.
Many online invoicing platforms now advertise Factur-X compatibility. In practice, the actual level of compliance varies significantly from one solution to another.
Some tools generate only partial XML structures, while others have not yet finalized their integration with Approved Platforms. It is therefore essential to verify what the system actually generates, not simply rely on marketing claims.
XSD and Schematron validations must be tested using real-world invoice scenarios before any production deployment. A simple configuration error, missing field, or inconsistent total can invalidate the entire file.
In some cases, users may not even receive a clear error message. The file can be silently rejected during compliance verification processes.
The obligation for SMEs to issue electronic invoices officially begins in September 2027. However, the obligation to receive electronic invoices starts earlier, in September 2026.
An SME waiting until 2027 to begin preparing will therefore already be out of compliance one year earlier. Technical preparation, validation testing, and the selection of an Approved Platform should all be anticipated well before the official deadlines.
As SaaS invoicing platforms continue to multiply, some businesses are choosing a different approach: deploying the invoicing system directly on their own server infrastructure.
With an on-premises approach, invoicing data remains hosted on the client’s own infrastructure. Invoices are not generated or stored through an external third-party service.
The system operates autonomously without subscription fees tied to invoice generation volumes. This approach is particularly suitable for SMEs that already have server infrastructure, process high invoice volumes, or need stronger control over sensitive customer and financial data.
Using an Approved Platform remains mandatory for the regulatory transmission of invoices. The on-premises approach mainly concerns invoice generation, validation, and storage.
Both systems are complementary: the internal system generates a compliant Factur-X invoice, while the Approved Platform handles official routing and regulatory exchanges.
Reducing external dependencies also reduces potential points of failure. There are no imposed pricing changes, no forced software updates capable of breaking an existing workflow, and no service shutdowns blocking invoicing operations.
Once properly deployed, the system can operate autonomously and remain stable for many years.
Failing to comply with the reform requirements can create operational, administrative, and fiscal consequences.
The French Finance Law for 2026, published in February 2026, increased the penalty applied to non-compliant invoices. The amount was raised from €15 to €50 per invoice, with a maximum annual cap of €15,000.
At the time of writing, the penalties currently provided for by the regulatory framework notably include the following sanctions.
For businesses processing several hundred invoices per month, the financial impact can quickly become significant.
A company that fails to designate an Approved Platform may first receive a formal notice with a three-month compliance deadline.
If the situation is not corrected, a €500 penalty may apply, followed by additional €1,000 penalties every three months while the non-compliance continues.
An invoice transmitted outside the official regulatory channel may not be processed by the recipient’s accounting system. This can block accounting workflows, delay VAT recovery, and disrupt cash flow management.
The issue therefore affects not only the invoice issuer, but also the company receiving the invoice.
The recipient of a non-compliant invoice may also lose the ability to deduct the associated VAT. For companies processing large invoice volumes, the financial impact can be immediate and substantial.
Even before financial penalties apply, the most critical risk is the interruption of invoicing flows. Invoices that do not arrive, blocked payments, and disrupted commercial exchanges can quickly destabilize a company’s operations.
Compliance is therefore not only a regulatory obligation. It becomes an essential condition for maintaining smooth and reliable B2B transactions.
The reform will progressively take effect within the next few months. The preparation steps themselves are manageable, but implementing them correctly requires time and anticipation.
This is the immediate priority. Without a registered Approved Platform, a company will no longer be able to properly receive electronic invoices starting in September 2026.
The decision should be based on several factors: platform stability, pricing structure, and the ability to integrate correctly with the company’s existing invoicing system.
A software solution claiming Factur-X compatibility does not automatically guarantee real compliance. Businesses must concretely verify that generated files successfully pass all three validation levels: XSD, Schematron, and PDF/A-3.
Online validation tools can be used to perform these checks before any production deployment.
Generating a valid Factur-X invoice is only the first step. Ensuring that transmission through the Approved Platform works correctly is equally important.
Testing should cover the entire process: document generation, technical validation, regulatory transmission, and final reception by the recipient.
Technical providers and Approved Platforms will face heavy demand during the months leading up to September 2026. Businesses that prepare early will have a significant operational advantage compared to those waiting until the final months.
Anticipating the transition also helps avoid rushed deployments, configuration mistakes, and operational disruptions.
The electronic invoicing reform is neither optional nor distant. The first obligations will begin applying in September 2026.
Businesses that start preparing now will have enough time to select their Approved Platform, test their Factur-X generation workflow, and correct potential issues before they become operational blockers.
Those who wait too long will instead face delays, operational pressure, and the mistakes that often come with emergency deployments.
Technical compliance is not limited to large corporations. It applies to every business that issues or receives invoices in a VAT-subjected B2B environment.