Electronic Invoice 2026: Mandatory Fields & Enhanced Compliance

The digital transformation of financial processes is an undeniable reality for businesses. At the heart of this revolution, electronic invoicing stands as a central pillar, not only to modernize exchanges but also to strengthen tax compliance and optimize management. The 2026/2027 reform, with its progressive timeline, goes beyond simply digitizing invoices: it profoundly redefines the very nature of “mandatory information.” What was once a list of details to be visually displayed on a document is now transforming into a requirement for structured, consistent, and controlled data.

Until now, an invoice was validated by the visual presence of certain information. With the advent of electronic invoicing, this approach becomes obsolete. The reform requires that this information not only be present but, more importantly, correctly structured, usable by information systems, and subject to automated controls from the moment of issuance. This evolution marks a paradigm shift: compliance moves from a post-facto verification to upfront validation, even before the invoice reaches its recipient.

This expert article from Weproc aims to decipher the impact of this reform on mandatory information. We will explore how “classic” requirements have transformed, what new information has become indispensable, and how businesses can anticipate these changes to ensure compliance, secure their payment flows, and ultimately, turn a regulatory constraint into a true driver of operational and financial performance.

Understanding the Reform: From PDF Invoice to Electronic Invoice

The electronic invoicing reform, set to progressively take effect from 2026, represents much more than simple digitalization. It’s a profound structural change that alters how businesses exchange, process, and declare their invoices. To grasp the full scope of this transformation, it’s essential to understand the fundamental distinction between the invoice as we knew it (often in PDF format) and the electronic invoice in the regulatory sense.

The Legal Framework: The Core of Mandatory Information (Fundamentally Unchanged)

Before delving into the new aspects, it’s crucial to remember that the foundation of mandatory information has not changed. Current legal requirements remain the basis for all invoicing, whether paper, PDF, or electronic.

In France, Article 289 of the French General Tax Code (CGI) is the cornerstone of invoicing obligations. This text, along with other provisions related to VAT law, exhaustively defines the information that must appear on an invoice issued by any VAT-registered company. The objective is clear: to guarantee transaction traceability, ensure tax transparency, and enable the administration to collect VAT and businesses to deduct it correctly.

An invoice is more than just a commercial or accounting document. Its tax role is paramount. It serves as proof for VAT application, for calculating taxable bases, and for justifying deductions. A non-compliant invoice can lead to significant consequences, ranging from refusal of VAT deduction to financial penalties in the event of an audit.

A crucial point, often misinterpreted, is that the legal validity of mandatory information is not intrinsically linked to the document’s format. Whether the invoice is printed on paper, sent as a PDF, or transmitted as structured data, the information to be provided remains, fundamentally, the same. The reform does not add new legal obligations in terms of informational content, but it radically changes how this information must be presented, transmitted, and controlled. This nuance is fundamental to understanding the upcoming transformations.

The Major Shift: From Unstructured Document to Data

The true disruption introduced by the reform lies in the transition from “document” to “data.” It is this evolution that gives a whole new dimension to mandatory information.

Until now, the PDF format, though digital, has remained an unstructured document from an information system perspective. The information it contains is primarily intended to be read and interpreted by a human. For it to be usable by a computer system, it requires additional processing (Optical Character Recognition – OCR, manual entry, etc.), often leading to errors and delays. In this model, the presence and consistency of mandatory information were verified retrospectively, manually, or during late tax audits, which left considerable room for corrections or disputes after issuance and sometimes even after payment.

Conversely, the electronic invoice, as defined by the 2026/2027 reform, is no longer a simple visual document. It is a true flow of structured data. Each piece of mandatory information is encapsulated in a precise, standardized, machine-readable data field. This data is transmitted via an official circuit and is subject to automated upfront controls, meaning even before reaching the final recipient or the tax administration. Missing, poorly formatted, or inconsistent information can now block the invoice from its attempted issuance.

This shift from visual compliance to data compliance is a radical change in logic. Previously, as long as the invoice “looked correct” and visually contained the required information, it was considered valid. Tomorrow, appearance will no longer suffice. It is the underlying data—its structure, accuracy, and consistency—that will determine the invoice’s validity. Errors will no longer be detected retroactively but prevented or flagged at the time of issuance, compelling businesses to adopt increased rigor from the source of their information.

“Classic” Mandatory Information: New Structuring Requirements

The foundation of mandatory information, as defined by the French General Tax Code, remains the reference. However, electronic invoicing introduces a new requirement: this information must not only be present but, more importantly, perfectly structured within the transmitted data. Information that is legible on the “image” part of a Factur-X invoice but absent or poorly coded in the “data” part will be considered missing, with potential rejection consequences.

Identification of Parties and Invoice References

Precise identification of the seller and buyer is the first cornerstone of any invoice. In the electronic context, this identification takes on an additional technical dimension.

The invoice must imperatively contain the complete identity of the seller (company name or individual name, legal form if relevant) as well as the complete identity of the buyer. The same applies to the address of the registered office or relevant establishment for each party. This information is not merely character strings; it must be structured into specific fields and be strictly consistent with official repositories, particularly SIREN/SIRET numbers. An error in these identifiers or a mismatch with the electronic invoicing directory can lead to the blocking of the invoice’s routing.

Each invoice must also have a unique number, based on a continuous chronological sequence, ensuring its integrity and traceability. The invoice issuance date, as well as the date of sale or service provision (if different from the issuance date), are essential pieces of information. They allow the operation to be linked to the correct tax period and ensure precise traceability of economic flows. Compliance with these dates is crucial for calculating payment deadlines and for tax declarations.

Details of Goods, Services, and VAT

The core of the invoice lies in the precise description of commercial operations. In electronic invoicing, this implies increased granularity and structuring.

The description of goods delivered or services rendered must be clear, unambiguous, and concise. Each invoice line must indicate the quantity billed and the unit price excluding tax. These elements not only allow for easy understanding of the operation but also automated reconciliation with purchase orders or contracts, thereby reducing disputes and data entry errors. In electronic formats, this information consists of distinct and mandatory fields for each billing line.

VAT, being a major tax, demands great rigor. The electronic invoice must indicate the VAT rate applicable to each product or service line, as well as the corresponding VAT amount. The total excluding tax and the total including all taxes (TTC) of the invoice must be calculated and presented accurately. In the case of specific VAT regimes, explicit and compliant information is required. This may include VAT exemption notices (Article 261 et seq. of the CGI), reverse charge mechanisms (for intra-community operations or subcontracting services in construction, for example), VAT basic exemption (for small businesses), or other specific regimes. These qualifications are directly utilized by the tax administration and must be rigorously coded according to the standards of electronic formats.

Payment Terms and Due Dates

Payment terms are a vital element for businesses’ cash flow management. The electronic invoice must integrate this information in a structured manner to facilitate controls and optimize financial processes.

The invoice must clearly indicate the payment terms agreed upon between the seller and the buyer. This includes payment methods (bank transfer, direct debit, check, etc.), payment deadlines granted (e.g., 30 days end of month, 45 days end of month, etc.), and any payment facilities. This information is crucial for receivables tracking and cash flow forecasting.

The payment due date, calculated according to the agreed terms, must be explicitly mentioned. This date is an essential legal and commercial benchmark. In case of non-compliance with this deadline, the invoice must also specify the applicable late payment penalty rate, in accordance with legal provisions (Article L441-10 of the French Commercial Code). Furthermore, the lump-sum indemnity for recovery costs, due in case of late payment in commercial transactions, must be cited. This information, while not new in substance, must be integrated in a structured manner to be fully usable in an electronic invoicing environment and to avoid disputes.

In summary, “classic” mandatory information does not disappear, but its nature evolves. It shifts from simple visual presence to a requirement for precise structuring, conditioning the technical validity of the invoice and its automated processing. This is a major challenge for businesses, which must review their information collection and management processes.

New Mandatory Information Essential for Electronic Format

Beyond the enhanced structuring of “classic” mandatory information, the electronic invoicing reform introduces new mandatory details. These details, often invisible on a traditional paper or PDF invoice, are nevertheless crucial for proper invoice routing, transaction qualification, and the functioning of e-reporting mechanisms. Their absence or inaccuracy will be a frequent cause of invoice rejection starting in 2026.

These four items are in addition to the traditional information required under the French Commercial Code and the French General Tax Code, all of which remains mandatory. On top of this, the data flow also carries technical routing and qualification information, detailed below.

Routing and Transaction Qualification

In an electronic invoicing ecosystem, invoice routing is no longer a matter of a simple email address. It relies on structured identifiers and precise qualifications.

The recipient identifier has become a paramount piece of information. Each electronic invoice must include a unique identifier allowing the invoice to be routed to the buyer’s platform. This is generally the client’s SIREN or SIRET number, or a specific identifier declared in the electronic invoicing directory (such as the Public Invoicing Portal – PPF directory). Without this precise identifier, the issuing platform simply cannot route the invoice to the correct recipient, thereby blocking the entire process. This is a significant departure from sending a PDF via email, where the email address sufficed.

Transaction category qualification is another key requirement. The invoice must indicate the nature of the commercial operation to determine its tax and reporting treatment. This qualification distinguishes whether the transaction falls under:

• Domestic B2B (between VAT-registered entities established in France): these invoices are subject to e-invoicing.
• B2C (between a VAT-registered entity and a private individual): these operations are not subject to e-invoicing but to e-reporting.
• International (with a VAT-registered entity not established in France or a non-VAT-registered entity): also subject to e-reporting.
• Or a specific case (e.g., entities benefiting from VAT exemption), also subject to e-reporting.

This information is essential because it determines the transmission circuit (e-invoicing via Approved Platforms or the PPF, or e-reporting directly to the PPF) and the type of tax data to be transmitted to the administration. Consistency between the declared transaction category and other invoice data (VAT, client identifier) is crucial.

Additional Information and Lifecycle

Other information, previously optional or implicit, becomes mandatory in specific contexts, thus complementing the structured invoice data.

When the delivery address differs from the billing address, this information must be explicitly provided in the structured invoice data. This detail is particularly important for businesses managing complex logistics flows or subject to specific VAT rules depending on the place of delivery. Its presence ensures data consistency and facilitates controls (intra-community VAT, goods flows, reconciliation with delivery notes).

The payment method, although not systematically mandatory for all transactions, may become expected data in certain scenarios, particularly when it impacts collection tracking or e-reporting requirements. For example, for B2C or international operations subject to e-reporting, collection dates and amounts must be declared. Knowing the payment method can be useful for linking this information and ensuring declaration compliance.

Electronic invoicing also introduces the concept of an invoice lifecycle. Precise statuses must be tracked and transmitted via platforms. These statuses, which are not always “visible” on the PDF rendering of the invoice, are an integral part of tracking and e-reporting obligations. These statuses include:

• Submitted: The invoice has been issued and transmitted to the platform.
• Rejected: The invoice has been refused by the platform or by the client due to non-compliance.
• Accepted: The client has validated the invoice.
• In Payment: The invoice is being processed for payment.
• Collected: Payment for the invoice has been received.

These statuses allow for real-time tracking of the status of receivables and payables, thereby improving businesses’ financial visibility and the fluidity of relationships with their partners.

Specific Data for E-reporting

Even when an invoice falls under e-invoicing (domestic B2B), certain additional information may be necessary to fulfill e-reporting obligations.

E-reporting is the mechanism for transmitting transaction data not covered by e-invoicing (B2C, international, certain specific operations) to the tax administration. VAT information is central to this mechanism. This can include total collected VAT amounts, collection amounts by VAT rate, or applicable specific regimes. This data enables the administration to pre-fill VAT declarations and exercise more effective control.

Collection amounts and dates are also key pieces of information for e-reporting. For B2C and international transactions, declarations are not based on the invoice issuance date but on the payment collection date. Therefore, it is essential to accurately collect and transmit this information for each relevant transaction.

In summary, new mandatory information is not always visible, but it is omnipresent in the data flow. Mastering it is a major technical compliance challenge, requiring a revision of internal information collection and management processes.

Electronic Formats and Controls: Technical Compliance

The transition to electronic invoicing is not limited to the mere presence of information; it demands rigorous structuring of that information. Mandatory information becomes “data fields,” and their compliance is now a technical matter, subject to standards and automated controls. This is where a crucial part of an invoice’s validity is determined.

Mandatory Information as Standardized Data Fields

In the world of electronic invoicing, mandatory information is no longer free-text elements but data coded according to international and national standards. This standardization is key to automating processing.

The electronic formats authorized in France — Factur-X (a hybrid format combining a readable PDF with structured XML data), UBL (Universal Business Language), and CII (Cross Industry Invoice) — are designed to structure invoicing data. Within these formats, every piece of mandatory information corresponds to a field precisely defined in a data schema. These fields are not free-form: they must follow a set name, a format (numeric, alphanumeric, date), a position, and consistency rules imposed by the standard.

The European standard EN 16931 is at the core of this structuring. It defines the “Core Invoice Usage Specification” (CIUS) — a minimum set of data and semantic rules for an electronic invoice. This standard ensures that, whatever technical format is chosen, the essential information is present and can be interpreted consistently. It specifies the list of mandatory data, the calculation rules (VAT, totals), the dependencies between fields, and the conditional cases (exemption, reverse charge, international transactions).

The major consequence of this approach is that a poorly structured piece of mandatory information is treated as if it were missing. A Factur-X invoice can display a visually flawless PDF; if the embedded XML file contains a formatting error, a missing field, or a data inconsistency (an incorrect SIREN, a non-compliant VAT rate), the invoice is technically non-compliant and can be rejected. It is the underlying data that governs, not the visual rendering.

The Crucial Role of Approved Platforms (PA)

To ensure this technical compliance, Approved Platforms (PA), formerly known as Partner Dematerialization Platforms (PDP), play a central role. They are the first line of control in the invoicing chain.

Approved Platforms are registered by the State to verify that electronic invoices comply with regulatory and technical requirements before being transmitted to the recipient and to the Public Invoicing Portal (PPF). In practice, they carry out automated, systematic checks on every invoice issued:

• Structural Checks: verification that all mandatory fields are present according to the format used (Factur-X, UBL, CII), and that the associated XSD schema is respected.
• Consistency Checks: verifying that amount calculations are correct (net amount, VAT, gross amount), that the VAT applied matches the declared rates, and that the seller’s and buyer’s details are consistent.
• Regulatory Checks: compliance with the rules of the EN 16931 standard and with specific requirements under French law (exemption notices, for example).

If a piece of mandatory information is missing, poorly structured, or inconsistent, the PA has the power to block or reject the invoice. This happens before the invoice even reaches the recipient’s information system.

It is essential to understand what an Approved Platform does not do: it does not correct the invoice. A PA does not fix erroneous data, does not fill in a missing field, and does not decide on the applicable VAT regime or the transaction category. Its role is to check the technical compliance of the data transmitted and to flag errors to the issuer. Responsibility for the quality and accuracy of the data remains entirely with the issuing company.

The Public Invoicing Portal (PPF), operated by the State, comes into play downstream of the PAs. It centralizes the invoicing data (e-invoicing) and transaction data (e-reporting) transmitted by Approved Platforms, and maintains the directory that enables routing. The DGFiP relies on this data to feed its VAT control mechanisms and pre-fill tax returns. The PPF does not validate each invoice individually: it uses data that has already been checked by the PAs.

This architecture shifts compliance upstream: it is no longer determined after the fact, but from the moment of issuance. It is therefore essential to secure the quality of mandatory information at the source, in your own invoicing systems and data repositories, rather than relying on the platform to correct it. The choice of Approved Platform matters, but it does not replace the quality of your data.

Risks of Non-Compliance: Rejections, Delays, and Penalties

The entry into force of e-invoicing has transformed the impact of errors or omissions in mandatory information. What used to be a matter of manual correction or a minor dispute now triggers automatic blocks and direct financial consequences.

Direct Consequences of Invoice Rejections

The main immediate risk for a non-compliant invoice is rejection by the Approved Platform, before the invoice even reaches the customer. This rejection is not a simple notification: it triggers a cascade of consequences.

• Blocked Flows: a rejected invoice is not transmitted to the customer and therefore cannot be entered into their accounting system. The invoicing chain is interrupted.
• Payment Delays: since the invoice is not valid or has not reached the buyer, payment is inevitably delayed. These delays affect the issuing company’s cash flow.
• Commercial Disputes: the back-and-forth needed to correct and reissue non-compliant invoices creates additional administrative work and can strain the business relationship.

Beyond the operational impact, tax penalties apply in the event of non-compliance. Article 1737 of the French General Tax Code (CGI), as amended by the 2026 Finance Act, provides for a fine of €50 per non-compliant invoice, capped at €15,000 per calendar year. In addition, for e-reporting failures, a fine of €500 per missing or non-compliant transmission also applies, capped at €15,000 per year (Article 1788 D of the CGI). A company that is not connected to any Approved Platform also faces a fine of €500, increased to €1,000 after a formal notice has gone unanswered for three months.

On July 10, 2026, the DGFiP announced a supportive approach for the rollout period: failures in the first few months will be met with guidance rather than immediate penalties, provided the company can demonstrate that it has already begun working toward compliance.

This context calls for a change in mindset: errors can no longer be corrected after the fact — they must be prevented upstream.

Securing Compliance at the Source

To avoid rejections and penalties, the most effective strategy is to ensure the compliance of mandatory information right from the source. This requires overhauling data management practices and greater involvement from information systems.

The reliability of mandatory information starts with the quality of the company’s data repositories. Information relating to customers, suppliers, items, VAT rates, and payment terms must be complete, accurate, and consistent. If this data is incorrect or incomplete in the ERP or CRM, the electronic invoices generated will inevitably be non-compliant. This is a necessary investment in data governance.

Digital tools play a decisive role in this effort:

• ERP and Invoicing Software: they are responsible for generating and structuring the data at the point of issuance. Their configuration must ensure that all mandatory information is collected and correctly formatted according to the EN 16931 standard and the chosen format.
• Procure-to-Pay (P2P) and E-Procurement Solutions: for receiving supplier invoices, they secure the integration of incoming invoices, automatically check their compliance against mandatory information and the related purchase orders, and orchestrate approval and payment workflows.
• Approved Platforms (PA): they verify the technical and regulatory compliance of the flows, but do not correct substantive errors.

One often underestimated point is the critical importance of invoice reception. In many organizations, the volume of incoming invoices is high, formats are heterogeneous, and suppliers’ compliance maturity varies. A non-compliant supplier invoice that is received immediately blocks the buyer’s payment cycle. The ability to automatically check mandatory information as soon as invoices are received, detect discrepancies, and manage exceptions therefore becomes a decisive operational advantage.

Structuring data at the source is the only way to turn a regulatory constraint into an operational advantage. The goal is no longer to manage non-compliance, but to eliminate it.

Toward Tool-Enabled Management of Mandatory Information

E-invoicing represents a challenge for finance departments. But beyond the constraint, it is an opportunity to modernize processes, improve data reliability, and unlock performance gains.

A Performance Lever for the Finance Function

Mandatory information is no longer just an administrative checkbox: it is becoming critical data that feeds a structured digital flow. Every piece of information on the invoice — the identity of the parties, transaction details, VAT, references, statuses — is used by automated systems and by the tax administration.

Making this information reliable is, first and foremost, about securing financial flows. By ensuring that every invoice is technically and fiscally valid from the moment it is issued or received, companies reduce the risk of rejections, payment delays, and supplier disputes. This smoother flow has a positive impact on cash flow, the predictability of collections, and relationships across the business ecosystem.

The reform offers an opportunity to turn a regulatory requirement into operational rigor. By ensuring the quality and structuring of data at the source, companies improve not only their compliance but also the reliability of their reporting, the accuracy of their financial analyses, and the efficiency of their accounting processes.

Adopting a Pragmatic, Tool-Enabled Approach

To navigate this landscape, companies need to combine a clear understanding of what is at stake with the adoption of suitable tools. The complexity inherent in electronic formats and regulatory requirements should not be underestimated.

Mastering the reception of incoming e-invoices is a critical point. This is often where difficulties concentrate, since the company depends on the compliance of the invoices issued by its suppliers. A Procure-to-Pay (P2P) solution like Weproc makes it possible to centralize the reception of all electronic invoice formats, convert them where necessary, and guarantee their compliance before any integration into the ERP.

Automatic data compliance checks are the second pillar. Using pre-configured, adaptable rules engines, a P2P solution verifies the presence and consistency of all mandatory information, VAT rates, SIREN/SIRET identifiers, and invoice statuses. Any discrepancy is detected and flagged early, allowing for quick correction before the invoice blocks the payment process.

Finally, reconciliation with purchasing commitments is a crucial step for operational efficiency and budget control. A received electronic invoice should be automatically reconciled with a purchase order or a contract, ensuring that only authorized spending is processed.

As a complete P2P solution, Weproc enables companies to manage their entire purchasing and invoicing process, from commitment through to payment. Weproc helps finance departments secure compliance with mandatory information requirements and turn this reform into a lever for streamlining operations.

E-invoicing, with its mandatory information requirements, is a defining step in the modernization of financial processes. By adopting a rigorous approach and relying on suitable tools, finance departments turn mandatory information into an asset: reliable data, checked at the source, that can be used across the entire financial chain.

Frequently Asked Questions About Mandatory Information

What are the new mandatory fields for electronic invoices?

Four: the customer’s SIREN or SIRET number, the delivery address for goods when it differs from the billing address, the transaction category (delivery of goods, supply of services, or a mixed transaction), and, where applicable, the option for VAT on debits. These come on top of the information already required under the French Commercial Code and the French General Tax Code.

Do the old mandatory fields disappear?

No. All the traditional information remains mandatory: identity of the parties, invoice number and date, description and quantity of the goods or services, unit price excluding tax, VAT rate and amount, payment terms, the late payment penalty rate, and the lump-sum indemnity for recovery costs. What changes is that this information must now appear in the structured data, not just in the visual layout.

What are the risks if a mandatory field is missing?

Two things. First, a technical rejection by the Approved Platform, which blocks the invoice before it reaches the customer — meaning a payment delay. Second, a fine of €50 per non-compliant invoice, capped at €15,000 per calendar year (Article 1737 of the French General Tax Code).

How can I check that my invoices include all the required information?

The most reliable check is the one carried out by your Approved Platform, which validates every invoice before it is transmitted. Upstream, check the quality of your data repositories: an incorrect customer SIREN or a missing delivery address in the ERP will consistently produce rejected invoices, regardless of the quality of the format.

Is the delivery address always mandatory?

No, only when it differs from the customer’s billing address. In that case, it must appear in a dedicated field within the structured data, not simply be mentioned as free text in the document.

Information verified on September 1, 2026 against official sources: Ministry of the Economy — Electronic invoicing between businesses, impots.gouv.fr — Electronic invoicing, and service-public.fr — Mandatory information on an invoice. DGFiP support: 0 806 807 807.