France E-Invoicing 2026–2027: What Business Central Users Need to Prepare

If your company invoices French businesses and you run Microsoft Dynamics 365 Business Central, September 2026 is not a “nice to have” milestone — it’s the date the French tax authority (DGFiP) flips the switch on mandatory B2B e-invoicing. From 1 September 2026, paper invoices and plain PDFs stop being valid for domestic B2B transactions. Every VAT-registered company in France must be able to receive structured electronic invoices, and large and mid-sized companies must also issue them.

This is an article for BC users, consultants, and partners who need the practical picture — not the regulatory press release. We cover the mandate timeline, what formats France actually requires, exactly what Business Central’s 2026 Wave 1 French localization covers (and what it doesn’t), a step-by-step configuration guide, common pitfalls, costs, and what to do based on your company size.

This post is a deep-dive supplement to our EU-wide e-invoicing overview for BC users. If you operate in multiple EU countries, read that one first — it covers the full landscape. This article goes deep on France specifically.

---

The Mandate & Timeline

France’s e-invoicing reform has been years in the making. Originally slated for 2023, then pushed to July 2024, the DGFiP finally settled on a phased rollout beginning 1 September 2026. The law has now been formally adopted through the 2026 Finance Bill, and a voluntary pilot programme ran from February to August 2026, validating real-world invoice exchanges between certified platforms. This is happening.

Here’s the timeline that affects you:

Date	Who Is Affected	Obligation
1 Sep 2026	All VAT-registered businesses in France	Must be able to receive e-invoices
1 Sep 2026	Large enterprises (5,000+ employees or >€1.5B turnover)	Must issue e-invoices
1 Sep 2026	Mid-sized companies (ETI) (250–5,000 employees)	Must issue e-invoices
1 Sep 2027	SMEs and micro-enterprises	Must issue e-invoices
1 Sep 2027	Non-established taxpayers (foreign companies trading in France)	Must issue e-invoices (deferred from 2026)
From Jul 2030	All EU businesses	Intra-EU e-invoicing under ViDA

The key nuance: everyone receives from September 2026, even if you don’t have to send until 2027. If you’re an SME and your large-company customer sends you an e-invoice, you must be able to process it — no excuses. You need at minimum a receiving capability by that date.

Company Size Definitions (Official Categories)

The DGFiP defines sizes using standard French enterprise categories, which don’t always match the EU SME definition you’re used to:

• Large enterprise (Grande entreprise): more than 5,000 employees, or turnover exceeding €1.5 billion and balance sheet total above €2 billion
• Mid-sized (Entreprise de taille intermédiaire — ETI): 250 to 5,000 employees, turnover ≤€1.5 billion
• SME (PME): fewer than 250 employees, turnover ≤€50 million or balance sheet ≤€43 million
• Micro-enterprise: fewer than 10 employees, turnover or balance sheet ≤€2 million

A subsidiary of a large international group counts as large, even if the French entity itself is relatively small. If you’re the French subsidiary of a global company, you’re almost certainly in the September 2026 issuance group.

The Five-Corner Model

France uses a five-corner model (modèle en Y) for e-invoice exchange. Here’s how it works:

1. Supplier generates a compliant e-invoice in their ERP
2. Supplier’s PDP (Plateforme de Dématérialisation Partenaire — the certified provider) validates the format, enriches it if needed, and routes it
3. PPF (Portail Public de Facturation — the state hub) receives transaction metadata for tax reporting
4. Buyer’s PDP receives and validates the invoice
5. Buyer processes it in their own system

The PDPs are the commercial engine. The PPF functions as a data concentrator for the DGFiP — it collects reporting data but does not directly handle B2B invoice exchange. For B2G (public sector) invoicing, Chorus Pro remains the dedicated portal, as it has been since January 2020.

One important terminology update: the French authorities have formally renamed “Plateforme de Dématérialisation Partenaire (PDP)” to “Plateforme Agréée (PA)” in the 2026 Finance Bill. In practice, most documentation and providers still use “PDP” — we’ll use that term throughout this article, but know they mean the same thing.

PDPs: Your Mandatory Middleman

As of October 2024, the DGFiP confirmed that businesses cannot connect directly to the PPF for invoice exchange. You must use a certified PDP. The first wave of certified PDPs was published in April 2026 by the DGFiP, with more being added through a formal audit process.

Certified PDPs must support:

• Factur-X 1.0 (EN 16931 profile minimum) and UBL 2.1 invoice input
• Real-time reporting to DGFiP via the PPF API
• 10-year archive in legally compliant format (NF Z 42-026 standard)
• Peppol BIS 3.0 for cross-border EU invoice exchange (mandatory from 2027)

If your current provider isn’t certified yet, you have options: switch to a certified PDP, use the PPF as a bridge during transition, or wait for your provider’s certification to complete. Do not wait until August to start this conversation.

---

What Formats France Requires

France recognizes three EN 16931-compliant syntaxes. You don’t need to support all three — one will do, as long as it’s the right profile level.

Factur-X (the Hybrid Format)

Factur-X is France’s flagship format and the one most French businesses will use. It’s a PDF/A-3 file with an embedded XML attachment (always named factur-x.xml). A human opens the PDF and sees a normal invoice. A machine extracts the XML and processes it automatically. No OCR, no re-keying.

Factur-X was developed jointly by FNFE-MPE (the French e-invoicing standards body) and FeRD (its German counterpart). It is technically identical to ZUGFeRD 2.x — same PDF/A-3 container, same XML schema, same profile levels. The only difference is the branding. If your system can generate ZUGFeRD 2.x, it can generate Factur-X.

Critical: not all Factur-X profiles qualify for the French mandate. Factur-X defines five profiles:

Profile	French Name	Mandate-Compliant?
MINIMUM	Minimum	❌ No — missing mandatory fields
BASIC WL	Basique WL	❌ No — insufficient
BASIC	Basique	❌ No — still insufficient
EN 16931	Confort	✅ Yes — this is what you need
EXTENDED	Étendu	✅ Yes — EN 16931 plus supply-chain fields

For French compliance, you must generate EN 16931 (Confort) profile or higher. Minimum and Basic profiles are technically valid Factur-X but lack mandatory fields required by the European standard — and therefore by France.

The EN 16931 profile requires, at minimum:

• BT-1: Invoice number
• BT-2: Issue date
• BT-9: Payment due date
• BT-29: Seller identification (SIRET, schemeID 0009)
• BT-30: Seller legal organization identifier (SIREN, schemeID 0002)
• BT-31: Seller VAT identifier
• BT-48: Buyer VAT identifier (if VAT-registered buyer)
• BT-81: Payment means type code
• BT-84: Payment IBAN
• BT-112: Invoice total
• BT-115: Amount due for payment

Missing any of these — even one — will cause validation failure at the PDP. No exceptions.

UBL 2.1 (via Peppol)

UBL 2.1 is the XML format used on the Peppol network. It’s pure XML — no PDF wrapper. This is the preferred route for businesses that want full automation and are already using Peppol for cross-border invoicing (Belgium, Nordic countries, Germany).

Business Central’s French localization supports Peppol BIS 3.0 as an output format alongside Factur-X. This is useful if your French customers are also on Peppol — many large enterprises and international companies are.

CII (Cross-Industry Invoice)

CII is the UN/CEFACT XML format — technically what’s embedded inside Factur-X, but can also be exchanged as a standalone XML file. It’s less common in practice; most businesses choose either Factur-X or Peppol/UBL. France accepts all three, but if you’re configuring BC, you’ll pick Factur-X or Peppol BIS 3.

What Is NOT Acceptable

• Regular PDFs (no embedded XML)
• Paper invoices for in-scope B2B transactions
• Factur-X MINIMUM or BASIC profiles (too little data)
• Unstructured data formats (CSV, Excel, email body text)

Once the mandate is live for your company size, only structured e-invoices in one of the three approved formats are legally valid for in-scope domestic B2B transactions.

---

How Business Central Handles It

Microsoft announced native French e-invoicing support in the 2026 Wave 1 release (available from April 2026, GA by June 2026). Here’s exactly what you get — and what you don’t.

What BC Supports Natively

The French localization, delivered via the E-Reporting FR extension, enables:

• Two compliant output formats: Peppol BIS 3.0 (UBL 2.1 XML) and Factur-X (PDF/A-3 with embedded CII XML, EN 16931 profile)
• Send and receive: full e-invoice lifecycle for both sales and purchase processes
• Lifecycle status tracking: submitted, accepted, rejected, paid — all mandatory statuses
• Transaction e-reporting: for operations where structured invoices aren’t required but must still be reported to the DGFiP (B2C, cross-border, certain services)
• SIREN/SIRET integration: uses your Company Information fields for automatic population in the generated XML
• Customer/vendor electronic routing addresses: configurable per trading partner for PDP delivery
• Standard E-Document framework: same interface you’d use for German, Belgian, or Danish e-invoicing

Configuration happens through the standard E-Document module — the same one used for other countries. You create E-Document Services entries for each format you want to use, configure the service integration with your chosen PDP provider, and assign document sending profiles to customers.

What BC Does NOT Do

Microsoft is not a certified PDP. BC generates compliant e-invoices in the right format — it does not route them to the PPF, validate them against the national directory, or handle the PDP-to-PDP exchange. You still need:

• A contract with a certified PDP provider
• Configuration of the E-Document Service connector to that provider’s API
• Management of any PDP-specific requirements (some providers require qualified electronic certificates, additional metadata fields, or specific API authentication)

BC does not handle PDP onboarding. Registering your company in the national directory, selecting your PDP, and establishing connectivity between your PDP and the PPF is your responsibility.

BC does not manage the 10-year archive requirement. French law requires e-invoices to be archived for 10 years in a legally compliant format (NF Z 42-026 standard). Your PDP typically provides this — but confirm it explicitly. BC’s standard document storage is not a legally compliant e-invoice archive for French purposes.

The Architecture

Here’s how the pieces fit together:

Business Central (E-Reporting FR extension)
    │
    ├─ Generates Factur-X (PDF/A-3 + XML) or Peppol BIS 3 (XML)
    │
    ├─ E-Document Service connector
    │       │
    │       └─ Your PDP's API
    │               │
    │               ├─ Validates format
    │               ├─ Routes to customer's PDP
    │               ├─ Reports to PPF (DGFiP)
    │               └─ Returns lifecycle statuses
    │
    ├─ E-Document Incoming (purchase side)
    │       └─ Receives e-invoices from suppliers' PDPs
    │
    └─ E-Reporting FR
            └─ Transaction data for non-invoice operations

The E-Reporting FR extension must be installed and enabled before you can configure any of this. It’s available through the standard Extension Management page in BC.

---

Step-by-Step BC Configuration

This is the practical walkthrough. We’ll configure BC for French e-invoicing, assuming you already have:

• A Business Central online tenant (SaaS) or on-premises with 2026 Wave 1 update
• A SIREN number (9 digits) and a SIRET number (14 digits) for your company
• Your French VAT registration number (numéro de TVA intracommunautaire, format FR + 11 characters)
• A contract with a certified PDP provider

Step 1: Install the E-Reporting FR Extension

1. Search for Extension Management and select the related link
2. Choose Microsoft AppSource
3. Search for E-Reporting FR (or French e-invoicing)
4. Install and enable the extension
5. Verify installation: search for E-Document Services — the French-specific format options should now be available

If you’re on a 2026 Wave 1 BC version, this extension ships as part of the localization. If you’re on an older version, update your environment first — the e-invoicing functionality requires the Wave 1 platform.

Step 2: Complete Company Information

1. Search for Company Information and open the page
2. Fill in (or verify) these fields:

Field	What to Enter	Example
Name	Your legal company name exactly as registered	Contoso France SAS
Address / Post Code / City	Registered business address	10 Rue de Rivoli, 75001, Paris
Country/Region Code	Must be FR	FR
VAT Registration No.	Intracommunity VAT number	FR12345678901
Registration No.	9-digit SIREN number	123456789
SIRET No.	14-digit SIRET number	12345678901234

The Registration No. field maps to BT-30 (seller legal organization identifier, schemeID 0002) in the generated XML. The SIRET No. field maps to BT-29 (seller identification, schemeID 0009) and BT-34 (seller electronic endpoint address).

These fields are mandatory. If they’re empty, your e-invoices will fail validation.

Step 3: Configure Customer Electronic Addresses

Every customer who receives e-invoices must have an electronic routing address. Without this, your PDP can’t deliver the invoice.

1. Search for Customers and open the list
2. Open each French customer’s card
3. On the Invoicing FastTab, fill in:

Field	Value
Electronic Address	Customer’s SIRET number (most common) or SIREN
Electronic Address Scheme	SIRET (0009), SIREN (0002), or EM (email)

For French B2B customers, the SIRET is the standard routing address. You can find it on their invoices, their website legal notice (mentions légales), or by asking their accounts payable team directly.

Important: do this for vendors too. If your French suppliers will send you e-invoices, they need your electronic address, and you need theirs in your vendor master data for incoming invoice matching.

1. Search for Vendors and open the list
2. For French vendors, fill in Electronic Address and Electronic Address Scheme on the vendor card — same fields, same logic

Step 4: Create E-Document Services

You need separate E-Document Services entries for each format you intend to use. Most companies will configure both Peppol BIS 3 and Factur-X to support different customer requirements.

1. Search for E-Document Services and open the page
2. Select New to create a new service
3. Fill in:

Field	Peppol Configuration	Factur-X Configuration
Code	PEPPOL-FR	FACTURX-FR
Description	Peppol BIS 3.0 France	Factur-X France
Document Format	PEPPOL	FACTURX
Service Integration	Your PDP provider	Your PDP provider
Country/Region Code	FR	FR

4. Select Setup Service Integration and configure:

   • The PDP provider’s API endpoint
   • Authentication credentials (API key, certificate, OAuth — depends on your PDP)
   • Your company’s PEPPOL participant ID (if using Peppol)

5. Repeat for any additional formats or providers

The specific integration fields depend entirely on your PDP. Most providers publish a BC configuration guide — follow it. Some PDPs use the standard PEPPOL connector; others require a custom AppSource connector.

Step 5: Configure Document Sending Profiles

1. Search for Document Sending Profiles and open the page
2. Create a profile for French e-invoicing:

Field	Value
Code	FR-EINVOICE
Description	French e-invoice sending
E-Document Service	Your service code (e.g., FACTURX-FR)
Default	Select if this should be default for French customers

3. Assign the profile to French customers: open each customer card, go to the Invoicing FastTab, and set Document Sending Profile to your new profile

4. Configure the E-Document Workflow to automate status transitions (submitted → accepted → posted). The standard BC workflow templates include e-document steps — you can customize them for your approval process.

Step 6: Configure E-Reporting

The E-Reporting FR extension also handles transaction data reporting for operations outside the scope of structured e-invoicing:

1. Search for E-Reporting Setup (this page becomes available after installing the extension)
2. Configure:
   • Reporting frequency: monthly or quarterly (SMEs may qualify for quarterly)
   • Transaction types to report: B2C sales, cross-border transactions, certain services
3. Verify that your PDP handles the e-reporting transmission to the PPF

Step 7: Test End-to-End

Before going live:

1. Create a test sales invoice for a known French customer configured with an electronic address
2. Post the invoice and verify it appears in the E-Document Outgoing list
3. Check the status flow: Draft → Submitted → Accepted
4. For receiving: ask a test partner to send you an e-invoice and verify it appears in E-Document Incoming and can be converted to a purchase invoice

Allow 2–3 weeks for testing before your go-live date. End-to-end e-invoicing involves three systems (BC, PDP, PPF) and real-world network conditions. Things will break. Fix them before September.

---

Common Pitfalls

Based on what we’ve seen in pilot programmes and earlier mandate rollouts (Belgium, Italy, Romania), these are the mistakes that will cost you time and compliance:

Pitfall 1: Missing or Invalid SIREN/SIRET Data

The number one cause of e-invoice rejection in pilot testing has been incorrect or missing SIREN/SIRET numbers. Common variants:

• Entering the SIRET in the Registration No. field and the SIREN in the SIRET No. field (they’re swapped)
• Having no SIRET in the Company Information at all
• Customer SIRETs that don’t match the official registry — your PDP validates against the national directory, and a mismatch triggers rejection
• Old or closed SIRET numbers from customers who’ve changed legal structure

Fix it now: run a data audit on all French customers and vendors. Verify every SIREN (9 digits) and SIRET (14 digits) against the official source. Budget one full person-day per 100 French trading partners.

Pitfall 2: Wrong Factur-X Profile

Generating Factur-X at the MINIMUM or BASIC profile level will pass validation in your test environment but fail at the PDP — because the PDP checks for EN 16931-compliant field coverage. BC’s Factur-X output targets EN 16931 by default, but verify explicitly. If you’re using a third-party format converter, confirm it outputs the Confort profile.

Pitfall 3: Assuming “I’ll Just Use Peppol”

Peppol BIS 3 is a valid format for France, but your French customer’s PDP must accept it. Some smaller French companies may use PDPs that only accept Factur-X. If you go Peppol-only without verifying customer readiness, you’ll hit a wall with certain trading partners. The safe approach: configure both formats and let the customer’s capability determine which one you use.

Pitfall 4: Ignoring the Receiving Mandate

If you’re an SME that doesn’t have to issue until September 2027, the temptation is to do nothing. But you must receive e-invoices from September 2026. If a large supplier sends you a Factur-X invoice and you have no receiving capability, you’re non-compliant — and their invoices still need to be paid. Your accounts payable process breaks.

At minimum, configure BC’s incoming e-document flow and a PDP connection for receiving. You can defer the sending configuration, but receiving capability is non-negotiable from day one.

Pitfall 5: PDP Contract Delays

The PDP certification queue has been processing since early 2026, but onboarding new customers takes time. If you wait until August to select a PDP, you’ll join a queue of thousands of businesses doing exactly the same thing. Contract now. Configure the integration. Test in July.

Pitfall 6: Forgetting E-Reporting

The e-invoicing mandate covers structured invoices for B2B. But e-reporting covers everything else — B2C sales, cross-border transactions, certain intra-community supplies. If you only configure BC for e-invoicing and ignore e-reporting, you’ll be compliant on invoice format but non-compliant on transaction reporting. The e-reporting obligation begins on the same date as your issuance obligation.

Pitfall 7: Multi-Entity Complexity

If you run multiple French entities in one BC tenant, each entity needs its own SIREN/SIRET, its own E-Document Service configuration, and its own PDP relationship. Consolidated setups are possible but require careful segmentation — don’t assume one PDP contract covers all entities.

---

What About EPR and Packaging Compliance?

If you’re selling physical products in France, e-invoicing isn’t your only regulatory concern. France operates the most comprehensive Extended Producer Responsibility (EPR) framework in Europe. From 1 July 2026, a new professional packaging EPR scheme (EPRO) requires businesses to register with an approved eco-organism (Citeo Pro, Twiice, or Léko), declare packaging volumes by material, and pay eco-contribution fees.

Business Central does not track EPR obligations natively. It stores your product and sales data — the raw inputs for EPR reporting — but it won’t calculate what you owe, which PRO to register with, or when each declaration is due.

We built DutyScope to close this gap. It’s a standalone EPR compliance platform that:

• Maps your BC product/sales data to EPR categories across 14 EU countries
• Tracks registration status, reporting deadlines, and fee estimates
• Monitors regulatory changes and alerts you when rules change
• Handles packaging, WEEE, batteries, and textiles — the four waste streams under EU EPR

For companies doing business in France, e-invoicing compliance and EPR compliance are two sides of the same operational coin. Read our full breakdown: How Business Central Handles EU EPR Packaging Compliance (And What It Doesn’t).

---

Costs: What You’ll Actually Pay

Let’s talk money. Here’s what French e-invoicing compliance costs through Business Central, based on real-world implementations.

BC License Costs

The E-Document framework and French localization extension are included in your existing BC license — no additional Microsoft license fees. You need:

• Business Central Essentials ($80/user/month) or Premium ($110/user/month) for full users
• Team Member ($8/user/month) for light users who only need to view or approve e-documents

The E-Reporting FR extension is free from AppSource.

PDP Provider Costs

This is your main external cost. Pricing varies by provider, but expect:

• Setup fee: €500–€2,000 one-time
• Monthly subscription: €50–€300/month depending on invoice volume
• Per-invoice fee: €0.10–€0.50 per e-invoice sent or received (some providers bundle a volume allowance into the monthly fee)
• E-reporting: usually included in the monthly subscription, but verify
• Archiving: some PDPs include 10-year archive storage; others charge separately (€10–€50/month)

For a mid-sized company processing 500–2,000 invoices per month, budget €2,000–€6,000 per year for PDP services.

Implementation Costs

If you’re working with a BC partner:

• Basic configuration (single entity, one PDP, standard setup): 3–5 consulting days (€3,000–€7,500)
• Complex setup (multiple French entities, custom workflows, data migration for SIREN/SIRET across thousands of trading partners): 8–15 consulting days (€8,000–€20,000+)
• Data audit and cleanup: 1–3 days (€1,000–€4,500)

Total First-Year Budget Estimate

Company Profile	BC License	PDP	Implementation	Total First Year
Micro (1–2 users, <100 invoices/mo)	Already paying	€800–1,500	€1,500–3,000	€2,300–4,500
SME (5–10 users, 200–500 invoices/mo)	Already paying	€2,000–4,000	€3,000–7,500	€5,000–11,500
Mid-size (10–25 users, 500–2,000 invoices/mo)	Already paying	€3,000–6,000	€5,000–12,000	€8,000–18,000
Large (50+ users, 5,000+ invoices/mo)	Already paying	€6,000–15,000+	€15,000–30,000+	€21,000–45,000+

Budget note: the above assumes you’re already on Business Central. If you’re upgrading from an older ERP specifically because of the e-invoicing mandate, add BC licensing ($80–$110/user/month) and a full implementation project. See our BC Implementation Costs 2026 guide for a realistic estimate.

---

Action Plan by Company Size

If You’re a Large or Mid-Sized Company (September 2026 Issuance)

Now (July 2026):

• Select and contract a certified PDP (check the DGFiP registry — first wave published April 2026)
• Install E-Reporting FR extension in BC
• Complete Company Information with SIREN/SIRET/VAT
• Audit customer and vendor master data for all French trading partners
• Begin PDP integration configuration

August 2026:

• Configure E-Document Services for Factur-X and/or Peppol BIS 3
• Assign electronic addresses to all French customers
• Set up document sending profiles
• Configure e-reporting for non-invoice transactions
• Full end-to-end testing with at least 5 real trading partners
• Train finance team on new workflows (e-document status monitoring, rejection handling)
• Go-live no later than 25 August to allow a week of production experience before the mandate

September 2026 onward:

• Monitor e-document statuses daily for the first month
• Establish a rejection-handling process (who resolves rejected invoices, within what SLA)
• Configure incoming e-document flow for purchase invoices from French suppliers

If You’re an SME or Micro-Enterprise (September 2027 Issuance)

Now–August 2026:

• Install E-Reporting FR extension in BC
• Complete Company Information with SIREN/SIRET/VAT
• Select a PDP for receiving only (lighter contract, lower cost)
• Configure incoming e-document flow for purchase invoices
• Add electronic addresses to your top 20 French supplier records
• Test receiving with at least 2 suppliers

September 2026–August 2027:

• Monitor incoming e-invoices and refine the AP workflow
• Audit customer master data for SIREN/SIRET completeness
• Plan issuance configuration (budget for PDP upgrade, implementation time)
• Configure sending by June 2027 — don’t wait until August

If You’re a Non-French Company Trading in France

• Determine if you have a fixed establishment in France (triggers the domestic mandate) or are trading cross-border (triggers e-reporting only until September 2027)
• If you’re a non-established taxpayer, your issuance deadline is September 2027 (per the 2026 Finance Bill simplification measures)
• You still need receiving capability from September 2026 if you have French VAT registration
• E-reporting for intra-EU acquisitions was simplified in the August 2025 update — line-item detail no longer required for incoming international purchases
• ViDA will require full e-reporting for intra-EU transactions from July 2030

---

FAQ

Q: Can I just email a PDF and call it a Factur-X invoice?

No. A regular PDF is not Factur-X. Factur-X is a specific PDF/A-3 file with an embedded XML attachment that conforms to the EN 16931 semantic model. A standard PDF generated by your ERP does not contain embedded structured data and will be rejected by any PDP. You need BC’s E-Reporting FR extension to generate compliant output.

Q: Do I need both Factur-X and Peppol BIS 3, or can I pick one?

You can pick one. Both are accepted formats. However, some French businesses may only accept one or the other depending on their PDP capabilities. We recommend configuring both if possible — use Peppol for customers already on the Peppol network and Factur-X for customers who prefer the hybrid format. BC’s E-Document framework lets you assign different formats to different customers.

Q: What happens if I’m not compliant by 1 September 2026?

The French tax code provides for penalties — typically fines per non-compliant invoice — but the DGFiP has signalled a pragmatic approach during the initial months. That said: your invoices won’t be legally valid if not exchanged through the mandated channels, your customers may refuse to process them, and you’ll have no audit trail for VAT purposes. “Pragmatic” doesn’t mean “doesn’t matter.” Get compliant.

Q: Does Business Central require any additional licenses for e-invoicing?

No. The E-Reporting FR extension and the standard E-Document framework are included in your BC license. You pay for the PDP service separately.

Q: Can I use the same PDP for multiple European countries?

Many PDP providers are expanding to cover multiple EU mandates. Check if your French PDP also covers Belgium, Germany, or Spain. A single provider simplifies management, but verify their certification status for each country — certification is country-specific.

Q: I’m a BC partner. How do I deploy this for multiple French clients?

The E-Reporting FR extension and E-Document framework are tenant-level configurations. Each client needs their own PDP contract, their own master data setup, and their own E-Document Service configuration. Use configuration packages for the master data mapping (SIREN/SIRET fields on Customer, Vendor, and Company Information tables) and RapidStart for the E-Document Service and Document Sending Profile setups.

Q: What about intercompany transactions between French entities?

If both entities are VAT-registered in France, intercompany B2B invoices are in scope. Each entity must issue and receive through its own PDP — you can’t shortcut this with internal transfers. Even intercompany transactions must flow through certified PDPs.

Q: Does this apply to non-VAT-registered businesses?

The mandate applies to VAT-registered businesses. If you operate under the franchise en base de TVA (VAT exemption scheme for very small businesses), you’re still in scope — the DGFiP FAQ confirms that franchised businesses must comply. No sector exemptions exist for B2B e-invoicing.

Q: How long do I need to keep e-invoices?

10 years, with guaranteed authenticity, integrity, and legibility throughout the retention period. Most PDPs provide compliant archiving as part of their service. If yours doesn’t, you need a separate archiving solution that meets NF Z 42-026 or equivalent standards.

---

The Bottom Line

France’s e-invoicing mandate is real, the deadlines are fixed, and the pilot programme has already validated that the system works end-to-end. For BC users, the good news is that Microsoft has delivered native support that generates the correct formats and integrates with the standard E-Document framework you may already be using for Belgium or Germany.

The work that’s on you: selecting a PDP, cleaning up your master data, configuring the integration, and testing before the deadline. For large and mid-sized companies, that deadline is in six weeks. For SMEs, you have until September 2027 to issue — but you must be able to receive from September 2026.

Start with your SIREN/SIRET data. It’s the hardest part to clean up and the easiest thing to get wrong. Everything else follows from there.

---

Need help with French e-invoicing configuration in Business Central? Contact us to discuss your setup. If you also need EPR compliance coverage for packaging, batteries, or WEEE in France, check out DutyScope — our compliance platform built specifically for BC users selling physical products in the EU.