France e-invoicing went live on 1 September 2026: the enterprise operating guide

The live position: what changed on 1 September 2026

France’s business-to-business electronic-invoicing reform entered into force on 1 September 2026. From that date, all businesses in the domestic receiving population—regardless of size—must be able to receive electronic invoices through an approved platform. Large enterprises and entreprises de taille intermédiaire, or ETIs, also entered mandatory issuance and e-reporting on the same day. Small and medium-sized enterprises, including micro-businesses, enter those outgoing obligations on 1 September 2027.

Those duties are related, but they are not interchangeable. E-invoicing governs qualifying domestic B2B invoices between VAT-taxable persons established in France. E-reporting sends specified transaction and payment data to the tax administration for flows that do not travel as domestic B2B electronic invoices, including relevant business-to-consumer and international transactions. A group can therefore have three simultaneous states: mandatory receipt, mandatory domestic issuance and mandatory reporting of other flows.

The route is also prescribed. A compliant electronic invoice is not simply a PDF attached to an email. The DGFiP describes an electronic invoice as structured data that can be processed automatically and says the supported semantic formats include UBL, CII and Factur-X, the hybrid format combining structured data with a human-readable representation. Exchange and reporting take place through a plateforme agréée—an approved platform—or through a compatible business solution connected to one.

The reform does not rewrite the underlying commercial event. The Ministry’s launch guidance says existing VAT, invoicing and payment rules continue to apply. What changes is the data route, the evidence created by that route and the speed at which an error becomes visible. A weak customer identifier, an unmaintained SIREN, a duplicate supplier or a missing transaction classification can now prevent delivery or send the wrong data downstream before a period-end VAT team sees it.

One reform, several legal and operating dates

An implementation plan should separate adoption, publication, technical preparation and application. The original ordinance established the direction in 2021. Later legislation rescheduled the obligations to September 2026 and September 2027. In 2026, the administration moved from pilots and platform approval into production, then issued the July decree and order before the first mandatory date. None of those earlier steps was itself the date on which every business had to receive an electronic invoice.

The first application date now sits in the past. That changes the management question. Teams should no longer ask whether the mandate will be delayed; they should ask whether every in-scope entity is registered in the directory, whether its receiving platform is active, and whether the first live invoices can be reconciled from business document to platform status to accounting entry. For large enterprises and ETIs, the same test must cover outgoing invoices and e-reporting.

The Ministry described 1 September 2026 as a starting point rather than a cliff edge and announced an accompaniment-focused approach for the rest of 2026. Its practical guide prioritises continuity, preservation of the parties’ rights and later regularisation where the intended route was not immediately followed. That is valuable relief for a real transition. It does not move the statutory application date to 2027 or allow a business to postpone platform selection without an active compliance plan.

Who is affected: map entities before systems

The safest starting point is the legal entity and its establishment, not the ERP instance. Domestic e-invoicing generally concerns transactions between VAT-taxable persons established in France where an invoice is required. A group’s brand, shared-services centre or billing system does not decide scope. The relevant supplier, customer, establishment and transaction do. One ERP can therefore contain flows that belong in e-invoicing, flows that belong in e-reporting and flows outside both routes.

Company size determines the outgoing application date. Large enterprises and ETIs entered on 1 September 2026; SMEs and micro-businesses enter on 1 September 2027. The receipt obligation does not follow that split. A small French customer may receive a compliant platform invoice from a large utility or telecom supplier now, even though that customer can still issue its own qualifying invoices outside the mandatory electronic route until 2027.

Foreign businesses need a separate analysis. DGFiP guidance says a foreign business without a French fixed establishment is not subject to the domestic e-invoicing receipt and issue obligation merely because it has French VAT obligations. It can still have e-reporting duties for transactions located in France where it is liable for French VAT. The official timetable places large and mid-sized foreign sellers and service providers in e-reporting from 1 September 2026, with smaller sellers from 1 September 2027; specified acquisition and reverse-charge reporting for foreign businesses applies from 1 September 2027 regardless of size.

Do not turn those rules into an unsupported automatic classification. A VAT number, postal address or customer-selected dropdown cannot by itself prove establishment, participation in a supply or legal size category. Tax should approve the scope analysis. Data teams should then express it as versioned master data with an effective date, evidence reference and route—not as a permanent yes/no flag.

Route the transaction before you format the invoice

A formatting project asks how to produce Factur-X. An operating programme first asks what the transaction is. For a domestic B2B supply between established VAT-taxable persons, a qualifying invoice generally travels through approved platforms as e-invoicing. For a consumer sale or an international flow, invoice exchange may continue under the appropriate commercial route while specified transaction data goes to the administration through e-reporting. Payment data can also be required for relevant service transactions.

That classification should be made at order or billing initiation, not reconstructed from free-text at month end. Required inputs include the legal supplier and buyer, SIREN or other identifiers, establishment, customer status, supply type, place of supply, invoice requirement and VAT treatment. Where one input is missing or contradictory, the transaction should enter a named exception state. Silent defaulting to domestic B2B is dangerous because it can misroute both the invoice and the tax data.

A PDF deserves particular care. DGFiP’s September FAQ is explicit that an ordinary PDF sent by email is not an electronic invoice within this regime. A human-readable PDF can exist as a representation or outside the in-scope route, but it is not a substitute for the structured invoice and approved-platform transmission when Article 289 bis applies. Accounts payable should avoid booking the email image and then booking the later platform record as a second liability.

Credit notes, rejections and corrections need the same routing discipline. A buyer should not use a definitive refusal merely to fix a minor data defect when the operating model calls for a correction. The system should capture the reason, the business document being corrected and the relationship between the original and replacement. Reconciliation should show one economic event even if several technical messages were exchanged.

Approved-platform readiness is now an accounts-payable control

Since every in-scope business must receive, platform readiness cannot be left to the tax reporting workstream. The organisation must select at least one approved platform, complete the mandate or contractual setup, and ensure that the intended receiving address is recorded in the national directory. The official FAQ allows businesses to use one or several platforms and to choose different providers for issue, receipt and e-reporting. Flexibility makes governance more important, not less.

An approved platform is not merely a file-transfer vendor. DGFiP’s official list identifies providers registered by the State to issue, transmit and receive electronic invoices and to send mandatory data. Registration also involves technical and interoperability testing. The list can change, so procurement should verify the provider’s current official status and intended services directly against the live list, not a presentation or an old screenshot.

The national directory is the routing layer. A supplier needs to know where an invoice for the customer should be delivered; the customer needs control over which establishment, service or account consumes it. Enterprise groups should define who can change directory entries, how a change is approved and how suppliers are informed. A platform migration without directory and cutover governance can create missing invoices even when both platforms work correctly.

Existing ERP, procurement and accounting tools can remain in the architecture, but the official guidance distinguishes an approved platform from a compatible solution. If a software provider is not itself approved, it must connect through an approved platform for the regulated exchange. The buyer should document that chain, including which party owns transformation, directory lookup, government transmission, status messages, archiving and incident response.

• Verify the platform on the current DGFiP list and record the verification date.
• Reconcile the platform contract, mandate and national-directory entry for every French entity.
• Name separate business owners for receipt, issuance and e-reporting even when one vendor performs all three.
• Define the cutover and rollback path for platform or directory changes.
• Require exportable invoices, statuses, error messages and evidence rather than a portal-only audit trail.

Structured data is the product; the visual invoice is a view

DGFiP guidance identifies UBL, CII and Factur-X among the accepted semantic formats. The important word is semantic. Compliance depends on the meaning and quality of the fields, not only on producing syntactically valid XML. A schema can accept a supplier identifier that belongs to the wrong group company. It can also accept a mechanically valid invoice number that duplicates a document already sent through another channel.

The administration’s 2026 explanatory material says 34 invoice data points are transmitted in structured form, including the supplier SIREN, unique invoice number and VAT rate. That number is useful for programme scoping, but it should not be treated as the whole enterprise data model. A routing decision may need additional attributes; the commercial invoice may contain other lawful information; and an approved platform can create technical identifiers and lifecycle statuses that accounting systems must preserve.

Build a field-level data contract. For every mandatory item, name the source system, business definition, format, owner, validation rule, transformation and evidence. Mark derived values clearly. If a platform enriches a party identifier or changes a code, the source value and applied rule should remain traceable. If the platform rejects a message, the error should return to the team that can fix the underlying record—not stop in an integration queue.

Legal-entity resolution is the control under several of these fields. Supplier and customer names drift; establishments use local labels; mergers leave obsolete records; and one counterparty can have several accounts. Match the operational record to an authoritative entity before assigning the regulated identifier. A VIES result can support an EU VAT-number decision, but it does not by itself establish French e-invoicing scope or prove that the record belongs to the intended contracting party.

Use the 2026 start-up tolerance as a controlled fallback

France’s start-up guide recognises that the first months will include incomplete connections, routing problems and suppliers that do not immediately follow the intended circuit. It sets three principles: keep the legal calendar, protect economic continuity and preserve a real compliance trajectory. During start-up, a genuine invoice received through an ordinary channel should not be discarded solely because the new electronic route failed. Businesses should process the underlying transaction and regularise the channel where required.

That position protects trade, but it creates a reconciliation challenge. Accounts payable may see an emailed PDF today and a structured platform invoice later. Accounts receivable may need to deliver a customer copy while a platform incident is being resolved. Without one economic-event identifier, the fallback can create duplicate bookings, duplicate payments, contradictory receipt dates or a missing correction. The fallback register should connect every temporary document to the later compliant record.

The Ministry’s public launch communications state that no sanctions will be applied in 2026 during the accompaniment phase. Teams should describe that accurately: it is an announced administrative approach for the start-up period, not a repeal of the obligation and not a permanent safe harbour. The advanced DGFiP FAQ describes statutory fines, including per-invoice consequences and a separate consequence for failing to select a receiving platform after formal notice. Those rules make evidence of active remediation important even where the administration begins with support.

A defensible fallback therefore has an incident owner, start and end time, affected entities and flows, temporary delivery route, duplicate check, customer or supplier communication, required regularisation and closure evidence. ‘The platform was down’ is not enough if no one can show which invoice was affected, what was sent, when the target route resumed and whether the regulated message was ultimately accepted.

What accounts payable and procurement should do now

Accounts payable should treat the platform feed as a controlled intake channel, not an extra mailbox. Every incoming invoice needs a technical identity, supplier identity, lifecycle status, original structured payload and relationship to any visual representation. The intake record should be reconciled to purchase order, receipt and vendor master before posting. If the same invoice also appears by email or portal, the duplicate logic should recognise it even when filenames and renderings differ.

Procurement owns several upstream conditions. Supplier onboarding should confirm the contracting legal entity, French identifiers, intended billing entity and relevant platform contact. Contract language should specify electronic delivery, correction, business-continuity and change-notification expectations without claiming that a supplier’s platform choice shifts the buyer’s tax responsibility. Supplier campaigns should be segmented by actual transaction and mandate population, not sent as a generic request to every vendor worldwide.

Rejection policy is another joint control. A definitive refusal can affect the supplier’s collection and correction process, so reviewers need reason codes and authority. The official FAQ gives wrong-recipient information as an example of a reason for refusal, while other problems may call for a correction. Buyer workflow should separate suspected duplicate, wrong legal recipient, price dispute, missing purchase order and tax-data error. Those are different facts and should not all produce the same technical status.

Daily reconciliation is preferable during launch. Compare platform receipts, accepted accounting records, unmatched purchase orders, email fallbacks, rejections and invoices awaiting correction. Publish counts by exception category and ageing, not by individual supplier. The aim is to reveal routing and data defects early without exposing customer-level or identifiable VAT-validation information.

What billing, tax and data teams should do now

For sellers already in the September 2026 phase, the definition of done is an accepted regulated outcome—not ‘the ERP created a file’. Billing must know whether the customer can be resolved in the directory, which addressing information is used, whether the platform accepted the document and what the customer did with it. Failed delivery, platform rejection and buyer refusal require different queues and different owners.

Tax should govern transaction classification and the e-reporting population. Domestic B2B, B2C and cross-border flows need documented decision rules. Payment-data reporting should be tied to the relevant service flows and actual collection information, rather than copied indiscriminately from invoice issue. When a rule depends on establishment or VAT liability, the approval and effective date should be visible to the systems applying it.

Data teams should create an end-to-end event model. At minimum, connect order, supply, invoice, platform submission, platform acceptance or rejection, customer status, accounting entry, payment and correction. Preserve the original values and transformations at each handoff. This turns a vague complaint such as ‘the invoice disappeared’ into a traceable event chain and supports evidence when an ordinary-channel fallback must later be regularised.

SMEs with a 2027 issuing date should use the year as integration runway, not as permission to ignore the reform. They already need receipt. They can also adopt compliant issuance early, in whole or in part, according to the official FAQ. Early issuance does not automatically accelerate every e-reporting duty, so a voluntary pilot should state exactly which flows and obligations it covers.

Questions for approved platforms and software vendors

Vendor evaluation should begin with the official status and service boundary. Ask whether the legal entity selling the service appears on the current approved-platform list and which functions are live: directory lookup, issuance, receipt, lifecycle status, e-reporting, payment data and archiving. If the product is a compatible solution, identify the approved platform behind it and make that dependency visible in the contract and incident model.

Then move to evidence. A strong demonstration follows one difficult invoice from source record to regulated outcome. It shows the original party data, directory resolution, format transformation, validation, submission, authority or network status, customer response and correction. It also shows what happens when the supplier uses the wrong customer establishment, when the directory has no expected address or when a duplicate PDF arrives outside the platform.

Security and resilience matter because the platform becomes part of the invoicing control environment. Procurement should examine data location, privileged access, subcontractors, encryption, incident notification, recovery objectives, certificate and credential rotation, penetration testing, audit reports and termination assistance. The approved status is necessary; it is not a substitute for the enterprise’s supplier-risk process.

Finally, protect data portability. The customer should be able to export invoices, structured payloads, attachments, statuses, timestamps, routing decisions, error messages and corrections in a usable form. A platform switch is not complete when login access moves. It is complete when directory routing changes safely, historic evidence remains accessible and open transactions are reconciled across the cutover.

• Are you currently listed as an approved platform, or are you a compatible solution using another provider?
• Which 2026 functions are in production and which remain roadmap items?
• How do you resolve directory addresses and expose the evidence for that decision?
• How are rejected, refused, corrected and duplicate invoices represented?
• What is the fallback when your service, the directory or a connected system is unavailable?
• Can we export the full event history and structured source without losing identifiers or timestamps?

Eight implementation failures to catch in the first month

The fastest way to improve the launch is to name failure modes before they are normalised as manual work. Most are not exotic tax questions. They are ordinary identity, routing and ownership defects made visible by a regulated network. Each defect should have a detection query, business owner, permitted fallback and closure evidence.

Do not measure success only as the percentage of technical messages accepted. A platform can accept data that refers to the wrong group company; an invoice can reach the platform but never post to the ledger; an ordinary-channel fallback can be paid twice; and e-reporting can omit a transaction that did not require a domestic B2B invoice. The launch dashboard needs completeness, identity accuracy, timeliness, duplicate control and exception ageing together.

• The group selected a platform, but one French legal entity is missing or misrouted in the directory.
• A supplier’s emailed PDF and later structured invoice create two accounts-payable records.
• The invoice uses the correct brand but the wrong contracting legal entity or SIREN.
• Domestic B2B, B2C and international flows share one default route because customer status is incomplete.
• A technically valid message is marked complete before platform acceptance or buyer status is reconciled.
• A rejection remains in middleware because no tax, billing or master-data owner receives it.
• The business relies on 2026 tolerance but keeps no incident, regularisation or duplicate-prevention evidence.
• A vendor migration changes the interface but leaves the national directory or open transactions behind.

A practical 30-day enterprise checklist

The first month should prove control over the live perimeter, not redesign every finance process. Start with one inventory covering all French legal entities, establishments, company-size classifications, receiving platforms, directory addresses, issuing dates and e-reporting dates. Assign one accountable owner to every row and attach the official source or internal tax conclusion behind the classification.

Next, trace four real flows end to end: an incoming domestic invoice, an outgoing domestic B2B invoice, a consumer transaction requiring e-reporting and an international transaction. Use production-like edge cases, not only clean samples. Reconcile the legal parties, source data, platform event, accounting entry and any payment or correction status. Record the breakpoints and rank them by transaction volume and customer impact.

Finally, exercise the fallback. Simulate a platform connection failure, a missing directory entry, an email PDF arriving before the structured record and a buyer refusing the wrong-recipient invoice. The teams should know who communicates, whether trade continues, what data is preserved, how duplicate payment is prevented and what event closes the incident. A written plan that has not passed those four tests is still a hypothesis.

• Confirm every French entity’s platform contract, mandate and directory record.
• Document receipt, issue and e-reporting dates separately by population and flow.
• Reconcile the first live platform invoices to source systems and general ledger.
• Publish an exception taxonomy with named owners and service targets.
• Check master data for duplicate counterparties, obsolete entities and missing SIREN values.
• Test PDF-versus-platform duplicate detection before increasing automation.
• Maintain a start-up fallback register and evidence every regularisation.
• Review the official approved-platform list and DGFiP guidance on a controlled cadence.

The decision for enterprise leaders

France’s reform is now operational. The strongest response is not a last-minute file conversion and not a blanket freeze when the target channel fails. It is a governed event chain that identifies the parties and transaction, selects the correct route, exchanges structured data through an approved platform, monitors the result and preserves a narrow continuity path when start-up friction occurs.

That model gives each team a concrete role. Tax owns interpretation and the scope register. Finance owns invoice completeness, posting and reconciliation. Procurement owns supplier readiness and platform commercial risk. Data and technology own lineage, identity resolution, integration and observable failure states. Treasury contributes payment evidence where relevant. No one team can deliver the control alone.

For large enterprises and ETIs, the first priority is to measure the live process and close exceptions. For SMEs and micro-businesses, the priority is to stabilise receipt now and use the next twelve months to test issuance and e-reporting. Both groups should preserve dated evidence and verify the current official position as guidance evolves. The costliest failure will be mistaking a temporary absence of sanctions for an absence of operational responsibility.