The electronic invoicing reform is fundamentally transforming the way French companies exchange invoices. This regulation is gradually mandating the use of Approved Platforms (PA, formerly known as Partner Dematerialization Platforms or PDP). These platforms serve a dual purpose: they transmit electronic invoices between businesses (this is known as electronic invoicing, or e-invoicing), and they ensure that data related to transactions excluded from the electronic invoicing system—such as sales to individuals or international sales—is transmitted to the tax authorities (e-reporting).
For SMEs and micro-enterprises, two deadlines define this timeline: as of September 1, 2026, all VAT-registered businesses must be able to receive electronic invoices; while the requirement to issue electronic invoices will take effect on September 1, 2027.
Between new formats, platform selection, lifecycle statuses, and handling special cases, practical questions are multiplying in the face of these new requirements. This practical guide provides point-by-point answers to the most frequently asked questions from executives and managers of SMEs and micro-businesses, helping them approach this transition methodically rather than in a rush.
Electronic invoicing refers to the issuance, transmission, and receipt of invoices in the form of structured data, rather than simple PDF files or paper documents. In practical terms, a compliant electronic invoice must be readable and processable automatically by management systems, which requires a standardized format rather than a simple image of the invoice.
This widespread adoption serves several objectives: simplifying business-to-business transactions, reducing payment times, combating VAT fraud, and providing tax authorities with a more detailed view of the economy through real-time data transmission. The expected impact therefore extends beyond the tax sphere alone: in the transportation sector, the entire management of commercial relationships is being modernized.
All VAT-registered businesses established in France are affected, regardless of their size. However, the implementation timeline varies depending on the type of business:
These two mechanisms are complementary but distinct. Electronic invoicing applies to domestic transactions between VAT-registered businesses (B2B): the invoice itself is transmitted via a platform, along with its structured data.
E-reporting, on the other hand, does not involve the transmission of any invoices: it consists of submitting summary data to the tax authorities via your PA. It covers two distinct requirements.
Transaction e-reporting applies to transactions that do not involve electronic invoicing: sales to consumers (B2C) and transactions with foreign businesses.
Payment e-reporting applies to services subject to VAT on receipts, including domestic B2B transactions: this involves reporting the date and amount of payments received, since it is the payment—not the invoice—that triggers the VAT liability.
A single taxpayer may therefore be subject to both obligations simultaneously, depending on the nature of their transactions.
Even if your obligation to issue electronic invoices does not take effect until 2027, you must be able to receive electronic invoices as of September 1, 2026. This involves three concrete steps: choosing a receipt address (by default, your company’s SIREN number), selecting a designated recipient (PA) to handle this process, and ensuring that your systems or your accountant can process invoices received in a structured format. This designation must not be delayed; otherwise, your suppliers—who are already subject to the electronic invoicing requirement—will not be able to send you their invoices through the expected channel, which could jeopardize your business relationships and the tracking of your payments.
For SMEs, very small businesses, and micro-enterprises, the requirement to issue electronic invoices takes effect on September 1, 2027. Until then, you may continue to invoice your business customers using your usual methods (paper, PDF, email), and no customer may require you to issue electronic invoices under the reform before that deadline. However, a large corporate client may contractually require an electronic invoice as early as 2026 (this is already the case with several shippers) to streamline their invoice processing and reconciliation. This additional time is therefore valuable for implementing the necessary tools, training your teams, and ensuring the reliability of your processes; however, early adoption provides peace of mind and can be a source of competitive advantage in customer service.
Yes, and it’s actually a recommended strategy for approaching 2027 with confidence. Nothing prevents an SME or microbusiness from voluntarily adopting the system before the legal deadline, provided they ensure that the relevant invoices are processed through a PA in one of the formats recognized by the reform. This proactive approach facilitates the gradual implementation of your system: start with certain customers or certain types of invoices, adjust your settings, and then expand the scope as the solution becomes more reliable. However, it’s important to inform the affected clients and avoid any confusion between an electronically transmitted invoice and a paper invoice that may be sent at the same time, which could create a risk of duplicate processing.
An Approved Platform (PA) is a service provider registered with the DGFiP to handle the issuance, transmission, and receipt of electronic invoices between businesses. Specifically, Article 289 bis of the General Tax Code requires the use of this type of intermediary for all exchanges falling within the scope of the reform: it is no longer possible to transmit an electronic invoice directly from one system to another without going through this regulated channel. The PA thus acts as a trusted third party: it verifies the compliance of invoices, routes documents to the correct destination, transmits processing statuses, and, where applicable, forwards the necessary data to the tax authorities. You can access it directly through a compatible solution integrated into your accounting software, your accountant, or any other service provider already connected to the system.
Each legal entity must have at least one receiving address; by default, this is its SIREN number. It is strongly discouraged to create multiple addresses per location or department without a genuine need: this practice complicates management for your suppliers, increases the risk of routing errors, and creates an unnecessary maintenance burden, particularly in the event of an internal reorganization. A single address per entity—possibly supplemented by a dedicated address for specific needs (business expenses, centralized processing outsourced to a third party)—remains the most robust configuration. When selecting a service provider, entering into a contract with a PA requires verification of the signatory’s identity and their authority to bind the company; this process can be delegated to a certified public accountant or an integrator authorized for this purpose.
Three structured formats are recognized as part of the reform’s minimum requirements:
Every accounting system is required to be able to process these three formats upon receipt, which ensures interoperability regardless of the format used by your supplier or customer.
When sending invoices, your invoicing software must be capable of generating one of these formats in compliance with the current standard, specifically adhering to VAT calculation rules and including all required information. Choosing software that meets these requirements greatly facilitates the integration of the reform into your existing processes.
The directory of the Public Invoicing Portal (PPF) lists all VAT-registered businesses, along with their associated electronic receiving addresses and the public administration (PA) responsible for them. It is this directory that allows your provider’s platform to automatically identify where to route an invoice intended for you, without requiring you to manually provide your receipt details to each of your business partners. In a sense, it serves as the “source of truth” for the system, continuously updated by the tax authorities as new contracts are established.
Throughout its processing, each electronic invoice is assigned statuses that track its journey from issuance to payment. Some statuses relate to the transmission itself (Submitted, Rejected, Made Available) and indicate whether the invoice has successfully reached its recipient. Others pertain to business-side processing on the buyer’s end: Accepted, when the invoice is acknowledged and will be processed for validation and payment; Rejected, when it does not correspond to any shipment or is non-compliant; In Dispute, in the event of a commercial disagreement; or Paid, which confirms that payment has actually been made. Two of these statuses, “Rejected” and “Paid,” have special implications since they are reported to the tax authorities: “Rejected” invalidates the data in the relevant invoice, and “Paid” determines the VAT due date for services subject to VAT on receipts. These statuses provide useful information for sales tracking, and managing them effectively—particularly through your accounting software or ERP system—ensures reliable tracking of your invoices in accounting without the need for manual re-entry.
The “Rejected” status must be accompanied by a reason, based on a strictly defined list of reasons: the invoice is not intended for you, there is no prior purchase order, or missing data prevents processing. This is by no means a refusal to pay, but rather a refusal to process the invoice as it stands. If the reason is valid, the solution is to issue a new invoice with a different number after correcting the issue; if the rejected invoice has already been posted, it must be reversed with a credit memo. If you dispute the rejection, it is best not to immediately generate a new invoice: first contact your customer to clarify the situation, as the “Rejected” status does not resolve a commercial dispute and does not replace contractual dispute resolution mechanisms. In any case, a disagreement regarding the substance of the invoice falls under the “In Dispute” status, which is distinct from a processing refusal (“Rejected”) and a technical rejection by the platform (“Rejected”).
At the start of the reform, it is common for the same invoice to arrive both electronically and through a traditional channel, sent “just in case” as a precaution. To avoid duplicate payments or double posting, best practice is to reconcile the received documents based on their identifying details: invoice number, amounts, supplier, and date. As soon as these details match, only one invoice should be retained as the reference for processing and payment, with the other copies identified as duplicates. Although this reconciliation process can be time-consuming at times during the transition phase, it remains essential for maintaining reliable accounting records.
Yes, and this is an important point to understand in order to navigate this transition without stress. An invoice received via email, PDF, or on paper after the reform takes effect should not be rejected for that reason alone, provided it corresponds to an actual transaction and includes the necessary information for processing. The reform changes the method of transmission but does not alter the substantive rules: the existence of the transaction, payment, accounting treatment, or the right to deduct VAT are still assessed according to the usual criteria. In practical terms, if your supplier is already subject to the electronic issuance requirement, you can ask them to correct the issue by resending the same invoice via the expected channel, since the failure is their responsibility, not yours. From the recipient’s perspective, this correction does not affect processing, payment, or—within the scope of the initial grace period—the right to deduct VAT.
A system failure or temporary unavailability—whether on your service provider’s end or your client’s—should never halt your business operations. The procedure to follow is always the same and helps minimize the impact of the disruption: identify the source of the problem, keep records of the incident (error messages, support tickets, correspondence with your service provider), and then use an alternative channel if necessary to ensure the continuity of payment and the business relationship. This backup transmission does not constitute a separate, new invoice: it must be clearly linked to the transaction in question, for example, by including the notation “duplicate” or “continuity copy.” As soon as operations return to normal, you should resend the same invoice electronically or arrange for its adjustment, without causing a duplicate payment or double-counting.
The DGFiP’s official position is clear: there are no automatic penalties, but there are no exemptions either. It is important to distinguish between two levels. Legally speaking, the timeline and penalties provided for by law take effect on September 1, 2026: no legislation postpones or suspends them. On a practical level, the administration published a starter guide in July 2026 in which it outlines its approach: companies acting in good faith that encounter a genuine difficulty, document it, and take the necessary corrective actions will not be penalized initially. The ministry refers to a “benevolent and tolerant” approach during the initial phase.
This tolerance is a guiding principle, not a right: it must be earned through an active and demonstrable path toward compliance. The administration will distinguish between companies engaged in a serious effort (currently finalizing a contract with an approved platform, communicating with a service provider, making gradual corrections) and those that demonstrate inaction or a persistent refusal to comply with the requirements. Keeping a record of every step taken (quotes, communications, deployment schedule) therefore remains the best safeguard.
While the transition period excludes automatic penalties for one-time difficulties, it does not exempt taxpayers from penalties for non-compliance that persists over time. The regulations provide for a specific penalty system for each obligation, which can be viewed on the official website impots.gouv.fr: failure to issue invoices electronically is punishable by a fine of €15 per invoice, capped at €15,000 per calendar year (Article 1737 of the General Tax Code); failure to comply with e-reporting obligations is subject to a fine of €250 per transmission, capped at €15,000 per calendar year (Article 1788 D of the same code). A specific mechanism is in place regarding the obligation to receive invoices: the tax authority first issues a formal notice, allowing a three-month period to come into compliance before any penalties are imposed. What truly puts a company at risk, therefore, is not an isolated incident, but a failure to take action, prolonged avoidance, or the deliberate maintenance of a parallel system without ever taking steps to rectify the situation.
The best protection remains traceability. In practical terms, this means retaining all documentation demonstrating active efforts toward compliance: contracts or correspondence with your payment service provider (PSP), schedules for system integration or configuration, incident tickets and their resolutions, and internal instructions provided to your billing or accounting teams. A digital tracking sheet, updated regularly, allows you to centralize this evidence and improve administrative efficiency. Should the authorities request information, it is these concrete, dated, and consistent elements that will help distinguish between a genuine initial difficulty and a simple refusal to participate in the system. There is no need to formalize everything immediately: a credible path is built gradually, provided it remains visible and documented at every step.
Anticipating the reform rather than merely enduring it makes all the difference. A few simple steps, taken now with the help of your accountant or software provider, will help ensure your path to compliance:
At Sinari, electronic invoicing isn’t limited to a TMS or a single solution. Thirteen Sinari software products are compatible with electronic invoicing, covering various business needs in transportation, logistics, fleet management, and even quarries.
This approach allows you to integrate the reform directly into the business tools you already use daily, without isolating electronic invoicing from the rest of your processes.
Are you already a Sinari customer? Contact your Sinari representative to verify your software’s compatibility and prepare for the implementation of electronic invoicing in your environment.
The electronic invoicing reform is fundamentally reshaping business-to-business transactions in France, but its phased implementation schedule gives small and micro-enterprises time to prepare without undue stress. Receive invoices starting September 1, 2026; issue them starting September 1, 2027: two clear deadlines, a grace period to overcome initial challenges, and a constant requirement (to document an active path toward compliance). Choosing the right platform, understanding lifecycle statuses, and planning ahead rather than reacting to problems remain the best strategies for turning this regulatory requirement into an opportunity to make your invoicing processes more reliable in the long term.
What is the deadline for electronic invoicing for SMEs?
SMEs and microbusinesses must be able to receive electronic invoices as of September 1, 2026, and must begin issuing them themselves as of September 1, 2027.
Do you have to pay for an Approved Platform?
Terms and rates vary by provider; some solutions already include this service through your management software or your accountant.
What are the risks if you’re late in getting started?
There are no automatic penalties as long as the difficulty is genuine, documented, and followed by corrective actions; however, the legal obligation remains fully enforceable.
Can we still send invoices by email after 2026?
When issuing invoices, small and micro-enterprises may continue to send invoices to their business customers via email or PDF until September 1, 2027. When receiving invoices, an invoice received via email or PDF remains valid if it corresponds to an actual transaction, but it does not exempt a supplier who is already subject to the requirement from their obligation to transmit invoices electronically.