France's Mandatory B2B E-Invoicing Starts September 1, 2026: A US Small Business Survival Guide

You landed a French customer. You sent your usual polished PDF invoice by email, got paid by wire, and booked the revenue. Starting September 1, 2026, that PDF is no longer an invoice under French law — and your French customer's accounting system is legally required to reject it.

If you sell software, consulting, design services, wholesale goods, or anything else to a business customer in France, this change reaches you even if you have never set foot in France, have no French entity, and have no French VAT number. The burden shifts depending on your situation, but the invoice you send — and the data your customer must report — will change anyway. The good news: with a few weeks of preparation, most US small businesses can stay compliant with a simple backup plan, not a full ERP overhaul.

This guide explains what France is actually mandating, where a US seller fits in, what formats and platforms are now required, and the practical bookkeeping steps to avoid delayed payments and rejected invoices.

What France Is Actually Mandating (and What It's Not)​

France is not just "going paperless." It is replacing post-audit invoicing — where you send a PDF and the tax authority checks later — with continuous transaction controls. Invoices must be structured, machine-readable data that passes through certified platforms and is visible to the tax administration in near real time. A PDF without embedded structured data does not count.

Think of it as two parallel obligations that use the same pipes:

E-Invoicing vs. E-Reporting: Two Tracks, One System​

E-invoicing covers domestic B2B transactions where both seller and buyer are established in France and subject to French VAT. Those invoices must be issued in a structured format and transmitted through a certified platform. The buyer must be able to receive them the same way.

E-reporting covers everything else that French VAT-registered businesses do: sales to consumers (B2C) in France, cross-border B2B sales to or purchases from foreign businesses (including you), and intra-EU transactions where the French business is liable for VAT. Instead of sending a full e-invoice, the French business reports summary transaction and payment data through the same platform network.

For a US seller, the distinction matters: you may not have a direct e-invoicing obligation, but your French customer will almost certainly have an e-reporting obligation triggered by your invoice. If your invoice is missing the data their platform needs, you create work for them — and friction for your payment.

Who Has to Do What, and When​

France is rolling this out in two phases based on company size (measured by the French definitions tied to revenue, headcount, and balance sheet):

• September 1, 2026 — Phase 1:

  • All businesses established in France must be able to receive structured e-invoices.
  • Large enterprises and mid-cap companies (ETIs) must also issue domestic B2B e-invoices and perform e-reporting.
  • E-reporting for those large and mid-cap issuers begins at the same time.

• September 1, 2027 — Phase 2:

  • Small and medium enterprises (SMEs) and micro-enterprises must begin issuing domestic B2B e-invoices and performing e-reporting.

The government has signaled a soft-enforcement tolerance through December 31, 2026 for good-faith efforts, but the legal dates remain September 1. Do not plan around tolerance — plan around the platform requirement.

The Formats That Actually Count​

France accepts three structured formats that all map to the European semantic standard EN 16931:

• Factur-X — a hybrid PDF/A-3 with an embedded XML (UN/CEFACT CII) layer. It looks like a PDF to a human and reads like structured data to a machine. This is the most practical bridge for small businesses because your customer still sees a readable invoice.
• UBL 2.1 — pure XML, widely used across Europe and in Peppol networks.
• UN/CEFACT CII (Cross-Industry Invoice) — pure XML, common in Franco-German supply chains.

A flat PDF, a scanned image, or a Word document exported to PDF does not satisfy the mandate, even if it contains all the right numbers. The invoice must be one of the three formats above and must transit through the certified network. This is why "just email a PDF" stops working for domestic French B2B — and why your French customer will ask you for better data even when you are not directly in scope.

Where US Small Businesses Fit In​

Your exact obligation depends on whether you are established in France and whether you hold a French VAT number. Most US small businesses fall into one of three buckets:

If You Have No French Establishment and No French VAT Number​

This is the most common case for a US freelancer, SaaS founder, or exporter invoicing a French business customer from the US.

You have no direct French e-invoicing obligation. You are not required to register on a French platform or to issue a Factur-X invoice under French law.

But your French customer does have an obligation. Your cross-border B2B invoice is outside the domestic e-invoicing mandate, so they will e-report the transaction — including transaction data and payment status — to the French tax authority via their platform. They need clean, structured data from you to do that accurately: your business name and address, their VAT number and SIREN, invoice number and date, line-item amounts with VAT treatment, currency, and payment terms.

If you keep sending a bare-bones PDF with "Services - $5,000" and no VAT context, you force them to chase you for details or to misreport. Either way, your invoice ages longer. Provide the data up front, even if you still send a PDF.

If You Have a French VAT Number Without an Establishment​

Some US businesses register for French VAT to sell to consumers, hold inventory in France, or simplify EU sales. You may have a French VAT ID but no office or staff in France.

Current guidance from the French tax administration is that e-invoicing does not apply to companies with no establishment in France, even if they hold a French VAT number. You still face e-reporting obligations for certain transactions — for example, domestic B2C sales or purchases where you are liable for French VAT — on the timeline that matches your size classification once you are drawn into the reporting net. In practice, that means you will need a platform connection for e-reporting even though you are not issuing domestic B2B e-invoices.

If this is you, confirm your size classification and reporting scope with your VAT adviser now. Do not assume "no establishment" means "no action."

If You Sell Through a Marketplace or Platform​

If you sell goods through a marketplace that is the deemed supplier for VAT (common for online platforms handling passenger transport, short-term accommodation, or certain goods), the platform may carry the e-invoicing or e-reporting burden. Your contract and the platform's French compliance notice should spell out who issues the invoice of record. Even then, keep your own records aligned to the platform's invoice numbers and VAT treatment — your books still need to reconcile to what the French system sees.

The Plumbing: PPF, PDP, and Plateforme Agréée​

The architecture has changed, and outdated blog posts still describe the old plan. Here is the current reality:

The Free Public Portal Is No Longer the Exchange​

Originally, France planned a free public portal (PPF, built on Chorus Pro, which has handled B2G invoicing since 2020) as a universal exchange. In October 2024, that plan was narrowed. The PPF is now a directory and data concentrator: it hosts the national directory of businesses (who is reachable at which platform), receives extracted invoice data from certified platforms, and passes it to the tax authority. It is not a free inbox where every business can send and receive.

Actual invoice exchange happens through certified private platforms, now rebranded from PDP (Plateforme de Dématérialisation Partenaire) to Plateforme Agréée (PA) — the English term is Approved Platform. Every domestic B2B e-invoice must transit through a PA, which validates the format, extracts the required tax data, assigns lifecycle statuses, and routes the invoice to the buyer's PA and to the PPF.

For a US seller without a direct obligation, you do not need to register for a PA yourself. Your French customer will already be on one by September 1, 2026 (they must be able to receive). Your job is to make your invoice easy for their PA to ingest.

How to Think About Picking a Platform (If You Need One)​

If you are in the second bucket — French VAT number without establishment, or you plan to establish — you will need a PA for e-reporting. Evaluation criteria that matter for a small business:

• Coverage of the three formats, with a human-readable rendering for every invoice (a PA must be able to produce a legible version).
• EN 16931 validation before sending, with clear error messages, not a generic rejection.
• Lifecycle status handling — issued, deposited, received, accepted, refused, paid — with status flowing back to you.
• E-reporting support for B2C and cross-border transactions, including payment-status updates.
• US-friendly onboarding — English support, ability to onboard with a US business identity, and connectors for QuickBooks, Xero, or whatever you actually use.
• Archive that meets the French 10-year retention requirement, with audit export.

You do not need the most expensive enterprise platform. You need one that handles Factur-X correctly and does not charge you for every status ping.

What to Fix in Your Books Before September​

The biggest risk is not a fine — it is a rejected invoice that restarts your payment clock. These bookkeeping fixes prevent that.

Clean Your Master Data​

French systems are strict about identifiers. For domestic French companies, that means SIREN (9 digits) and SIRET (14 digits), plus the French VAT number (FR + 2 check digits + SIREN). For a US seller, you will supply your own identifiers — EIN, US address, and any VAT number you hold — but you must capture your customer's identifiers perfectly:

• Legal name exactly as registered
• Full address with postcode and country code
• French VAT number when they have one (validate via VIES)
• Their PA routing information if they provide it (often just their SIREN, which the directory maps to a platform)

One transposed digit on a VAT number or a missing postcode can cause a validation failure that bounces the invoice back to you. Reconcile your customer master file this month and confirm the details in writing.

Map Your Invoice Fields to EN 16931​

You do not need to become an XML expert, but your invoices need to carry the fields that structured formats require. At a minimum, every invoice you send to a French B2B customer should include:

• Your business name, address, and contact
• Customer business name, address, and VAT number (if applicable)
• Unique invoice number (sequential, no gaps, no reuse) and issue date
• Supply date or service period if different from the invoice date
• Line items with quantity, unit, description, net amount, VAT rate or exemption reason, and VAT amount
• Currency (EUR if you bill in euros, or USD with clear currency code)
• Payment terms, due date, and payment means
• For cross-border services where French VAT is not charged by you, the correct VAT treatment text (for example, reverse charge or outside scope, as advised by your tax professional)

If you use a template that lumps everything into one line — "Consulting services, €12,000" — break it out. French platforms validate at the line level, and your customer's e-reporting maps from those lines.

Separate Domestic French B2B From Everything Else​

In your chart of accounts or invoicing system, tag invoices by transaction type:

• Domestic French B2B (you are established in France — must be structured e-invoice)
• Cross-border B2B (US to French business — you send a normal invoice, they e-report)
• B2C (sales to French consumers — they e-report, you keep VAT-compliant evidence)
• Intra-EU B2B (if you have EU VAT registrations — follow the establishment and reverse-charge logic)

This tagging is not busywork. It determines which workflow applies and what your French customer must report. If you co-mingle everything as "international sales," you will struggle to answer a customer's question about why their platform flagged your invoice.

Close Faster: Lifecycle Statuses​

Structured e-invoicing introduces explicit statuses that both parties see: deposited, received, accepted, refused, and paid. A refusal comes with a reason code (missing mandatory field, VAT inconsistency, unknown buyer). That is actually better than a PDF that sits unread in an inbox. Build a simple weekly routine: check your sent invoices for refused or pending statuses, fix the data, and resubmit the same day. For US senders who are not on a PA, ask your French customer to forward the platform status — many will do so automatically once you ask.

A Practical Backup Plan for PDF-Based Sellers​

If you are a US small business with no French establishment and you currently email PDFs, you do not need to rebuild your stack before September 1. You need a backup plan that keeps you paid and keeps your customer's reporting clean:

1. Keep sending a human-readable PDF, but upgrade the template. Use the field list above. Add your customer's SIREN and VAT number to the header, itemize lines with VAT treatment, and include payment IBAN or wire details exactly as they should be paid.

2. Add a Factur-X or structured-data companion when your tool allows it. Many invoicing tools (including some QuickBooks and Xero connectors, and lightweight EU invoicing services) can now generate a Factur-X PDF — a normal-looking PDF with embedded XML. If your tool can do that with one click, turn it on for French customers. Your customer receives a single file that satisfies both human and machine readers, even though you are not legally required to send it.

3. Offer to send via their platform if they ask. Some French buyers will ask you to upload your invoice to their PA or to send it to a dedicated ingestion email that their PA monitors. Say yes. It is faster than arguing about scope.

4. Put the VAT treatment in words, not just numbers. "No French VAT charged — reverse charge applies; customer to account for VAT" or "Services supplied outside France — no French VAT" (as applicable) prevents the platform from inferring the wrong rate. Confirm the correct wording with your adviser once and save it as a template.

5. Number and date rigorously. No duplicate numbers, no future dates, no gaps you cannot explain. French archiving and audit trails are strict, and a clean sequence is the simplest way to look credible.

6. Track payment status and share it. E-reporting requires French businesses to report not just the invoice but when it is paid. When you receive payment, send a brief remittance note with the invoice number, amount, date, and currency. It helps them close the reporting loop and helps you reconcile faster.

7. Archive everything for 10 years in original form. French commercial and tax rules require 10-year retention of invoices in their original issued form. Store the exact file you sent (PDF or Factur-X), plus any delivery confirmations or platform receipts your customer shares.

This plan does not require you to register on a French PA today, but it leaves you ready if a customer or future establishment forces the issue. The cost is a better template and a 15-minute data cleanup per French customer, not a new ERP.

Pricing, Cash Flow, and Bookkeeping Impact​

The mandate changes the plumbing of getting paid, not the price of your work — but plumbing affects cash flow:

• Expect a one-time slowdown from first-invoice rejections. The most common causes are missing SIREN or VAT numbers, mismatched addresses, and single-line descriptions that fail line-level validation. Budget an extra week of DSO for your first few French invoices after September 1 and front-load your outreach to customers about their PA preferences.

• Do not bake platform fees into French invoices ad hoc. If you later need a PA subscription for e-reporting, treat it as an overhead software cost, not a per-invoice surcharge you pass through inconsistently. Your pricing should reflect the cost of EU compliance as part of your international tier, not as a surprise fee on one customer's invoice.

• Keep a reconciliation tie-out. French e-reporting data should tie to your own sales ledger for French customers. Monthly, reconcile: (a) invoices issued to French VAT-registered businesses, (b) amounts your French customers confirm as e-reported, and (c) cash received. A three-way match catches a misclassified B2C vs. B2B transaction before it becomes a VAT inquiry.

For bookkeeping, the practical move is to add a few fields to your customer and invoice records: customer SIREN/SIRET, VAT number and its VIES validation date, invoice currency, VAT treatment code, and a flag for "French counterparty — e-reporting relevant." Those fields feed both a Factur-X export and your customer's reporting without extra work later. If you use plain-text accounting, they map cleanly to metadata on your transaction postings and make your audit trail self-documenting — see your own docs for how to extend postings with custom fields.

Common Mistakes to Avoid​

• Assuming a US entity is automatically exempt from everything. You may be exempt from French e-invoicing, but your invoice still triggers your customer's e-reporting. Invisible does not mean irrelevant.

• Sending the same minimal PDF to every country. What passes in the US will be rejected by a French PA's validation. Localize the template for France even if you keep a simpler template elsewhere.

• Using the wrong format name as a buzzword. "Peppol" is not the French domestic B2B network for this mandate. Peppol is used for B2G via Chorus Pro and in other EU countries, but domestic French B2B flows through PA/PPF with Factur-X, UBL, or CII. Do not promise a French customer you will "send via Peppol" unless they explicitly ask for it.

• Forgetting payment-status reporting. E-reporting is not a one-and-done at invoice time. French businesses must also report payment data. If you credit, refund, or write off a French invoice, notify the customer promptly with a credit note that carries the same structured data quality as the original.

• Treating archiving as optional. A PDF in your email sent folder is not an archive. Keep the issued file, its structured companion if any, and the delivery or platform acknowledgment in a retention system that you can produce for 10 years.

Simplify Your Financial Management​

Whether you are adapting invoices for France's new e-invoicing rules or just keeping international sales reconciled at home, clear, structured financial records are what keep compliance from turning into chaos. Beancount.io gives you plain-text accounting that is transparent, version-controlled, and ready for automation — so your books stay accurate whether you are tagging cross-border sales, tracking platform fees, or reconciling foreign-currency receipts. Explore the Fava dashboard or get started for free at Beancount.io.