Business Central France E-Invoicing 2026: Configure Factur-X, UBL and E-Reporting

Tracked under Microsoft 365 Roadmap ID 576832 as part of the 2026 release wave 1 plan, this Country and Regional localization update entered public preview on June 5, 2026, and reached general availability on August 3, 2026, ahead of the initial September 2026 French regulatory milestone. While the feature is enabled automatically for end users on the web platform in Worldwide Standard Multi-Tenant cloud environments, turning that capability into actual legal compliance requires some deliberate architectural and master-data legwork from IT and finance administrators.

Here is a look at how Microsoft’s implementation works, how the DGFiP "five-corner" model separates ERP software from certified transmission platforms, and the exact steps required to configure UBL 2.1, Factur-X, and Transaction E-Reporting in Business Central.

Understanding the DGFiP Five-Corner Model and the September 2026 Mandate​

Before diving into Business Central's configuration pages, it is crucial to understand what Microsoft is—and is not—doing here. France's electronic invoicing reform operates on the DGFiP five-corner model, where suppliers and buyers exchange structured invoices and lifecycle statuses through registered intermediaries that simultaneously report tax data to the French administration.

Microsoft explicitly notes in its release documentation that it does not operate as a certified Partner Dematerialization Platform (PDP). According to guidance from the French tax authority on impots.gouv.fr, a registered platform (plateforme agréée / PDP) is an operator formally accredited by the DGFiP's registration service for a renewable three-year term. Only an accredited platform is legally authorized to transmit electronic invoices to a buyer's platform, receive invoices on a company's behalf, and forward invoice, transaction, and payment data to the government.

Instead of acting as the regulated intermediary, Business Central serves as the compliant ERP engine. It uses its standard E-Document module alongside the E-Reporting FR localization extension to generate the required semantic formats, enforce French validation rules, track mandatory invoice lifecycle statuses, and connect to your chosen third-party PDP (such as Pagero, Avalara, or another Marketplace connector) or the Public Invoicing Portal (PPF).

A Nuance on Regulatory Deadlines​

While Microsoft’s high-level roadmap summary broadly states that French e-invoicing and e-reporting mandates become mandatory for all VAT-registered businesses from September 2026, official guidance published by the French tax administration on impots.gouv.fr outlines a phased rollout:

• From September 1, 2026: All businesses operating in France must be capable of receiving electronic invoices. Simultaneously, large enterprises and intermediate-sized enterprises (ETIs) are required to issue electronic invoices and transmit e-reporting data through an approved platform.
• Later Phases: According to Microsoft Learn's French localization documentation, the reform is introduced in phases before ultimately applying to all domestic B2B transactions.

Regardless of whether your French entity is required to issue structured invoices on day one or primarily needs to receive and process incoming vendor bills while preparing its outbound pipeline, the underlying ERP plumbing is needed now.

Section Summary: Business Central provides the document generation, validation, and workflow engine for France's September 2026 e-invoicing reform, but organizations must still pair the ERP with a certified PDP connector to transmit data to customers and the DGFiP.

Two Semantic Formats: Peppol BIS 3.0 (UBL 2.1) vs. Factur-X​

Why settle for one standard when European e-invoicing can give you two? France's framework accepts multiple semantic syntaxes, and Microsoft’s E-Reporting FR extension supports the two heavyweights for both outbound sales and inbound purchase automation:

One helpful clarification for administrators comparing the Microsoft 365 Roadmap against Microsoft Learn documentation: the roadmap refers to the XML option simply as Peppol BIS3 (XML), while the technical setup guide titles it UBL 2.1 (PEPPOL BIS 3.0). They are the exact same option inside Business Central.

If you opt for Factur-X, Business Central uses report rendering extensions across standard sales and service documents—specifically Standard Sales - Invoice (10970), Standard Sales - Credit Memo (10971), Service - Invoice (10972), Service - Credit Memo (10973), Reminder (10974), and Finance Charge Memo (10975)—to inject the CII XML payload into the PDF during the OnPreRendering trigger when exported through the Factur-X workflow.

Section Summary: Administrators can configure Business Central to exchange pure XML files via UBL 2.1 (Peppol BIS 3.0) or hybrid human-and-machine-readable PDF/A-3 files via Factur-X, with automated import into purchase documents supported for both.

Step-by-Step Setup: Configuring French E-Invoicing in Business Central​

Getting Business Central ready for French e-invoicing is a great test of master-data hygiene. Because the E-Reporting FR extension enforces strict French business rules prior to export, missing a single registration number will halt an invoice in its tracks.

Prerequisites​

According to Microsoft Learn, before configuring the services, ensure that:

1. The E-Reporting FR extension is installed and enabled.
2. You have obtained a qualified electronic certificate, if required by your chosen PDP.
3. You have valid company SIREN (9-digit) and SIRET (14-digit) numbers.
4. You have collected electronic routing addresses for your customers.

Step 1: Populate Mandatory Company Information​

Open Company Information in Business Central and populate the fields enforced by French validation rules:

• Country/Region Code: Set to FR (enforced by rule BR-FR-DC; leaving this empty triggers an export error).
• Registration No.: Enter your 9-digit SIREN number. This maps to the seller legal organization identifier (BT-30, schemeID 0002) and is enforced by rule BR-FR-03.
• SIRET No.: Enter your 14-digit SIRET number. This maps to both the seller identifier (BT-29, schemeID 0009, enforced by BR-FR-02) and the seller electronic endpoint address (BT-34, enforced by BR-FR-07).
• IBAN and SWIFT Code: Enter your company bank account IBAN (used in payment means BT-84) and BIC/SWIFT code (used in BT-86).

Admin tip: Business Central checks both Registration No. and SIRET No. before exporting any document; if either is blank, the export fails immediately with an error message.

Step 2: Configure Customer and Vendor Routing Addresses​

Every customer receiving electronic invoices needs a routing endpoint for PDP delivery.

1. Open the Customers page and select a customer card.
2. On the Invoicing FastTab (located after the VAT Registration No. field), fill in the Electronic Address field (used for buyer electronic address BT-49, such as the customer's SIRET) and select the Electronic Address Scheme (0009 for SIRET, 0002 for SIREN, or EM for Email).
3. Under business rule BR-FR-12, BT-49 is mandatory. Microsoft’s documentation notes a built-in fallback mechanism: if Electronic Address is left blank, Business Central attempts to use the customer's Registration Number (or derive the SIREN from a French VAT registration number if neither is present). If none of those identifiers exist on the card, validation fails.
4. If you plan to import incoming electronic purchase invoices, open your Vendors cards and configure their Electronic Address and Electronic Address Scheme fields in the exact same manner.

Step 3: Create E-Document Services and Workflows​

Next, wire up the formats in the E-Document Services page:

1. Create a new service (for example, PEPPOL-FR for Peppol BIS 3.0 FR or FACTURX-FR for Factur-X FR).
2. Set the Service Integration field to your PDP integration connector, or leave it as No Integration if you are testing or performing manual exports.
3. Open the Workflows page to automate exporting and sending when an e-document is created.

Critical Workflow Warning: If your organization uses both Peppol and Factur-X for different customer segments, you must create a separate workflow for each format. Because all e-document workflows share the same EDOC category, Microsoft warns that you must select the On Condition field on the E-Document Created event line and filter the E-Document Service Code to the specific service (FACTURX-FR or PEPPOL-FR). Without these conditions, both workflows will fire simultaneously for every posted invoice, causing duplicate exports or processing errors.

Step 4: Link Document Sending Profiles and Verify Report Selections​

1. Go to Document Sending Profiles and create a profile for your electronic format (set Electronic Document to send through the workflow).
2. Assign that Document Sending Profile directly on the relevant Customer cards.
3. Check Report Selection - Sales to verify that standard sales mappings are in place for PDF rendering if using Factur-X.

Once configured, posting a sales invoice automatically generates the E-Document record, exports the compliant XML or hybrid PDF, and transmits it through your configured PDP integration. Administrators can track the Export, Send, and Clearance history—including the PDP's acceptance timestamp—directly from the E-Document Card and Document Logs.

Section Summary: Setting up French e-invoicing requires populating company SIREN/SIRET identifiers, adding buyer electronic routing addresses, configuring E-Document Services, and applying strict conditional filters to EDOC workflows.

Don't Forget the Other Half: Transaction E-Reporting in France​

What happens when a French business sells goods to a private consumer in Paris, ships products to a B2B client in Germany, or exports outside the European Union? Those transactions fall outside the domestic B2B structured e-invoicing loop, yet the DGFiP still wants visibility into the tax data.

That is where Transaction E-Reporting comes in. Supported in both Business Central online and Business Central on-premises (France), the E-Reporting FR document format generates structured XML payloads for out-of-scope operations and transmits them to the tax authority on a periodic (monthly or quarterly) or single/batch basis via a PDP connector such as Pagero or Avalara.

Configuring E-Reporting Transaction Types​

According to Microsoft Learn's E-Reporting documentation, the most common point of failure for e-reporting is uncategorized master data. Before posting documents, administrators must open relevant Customer Cards or Vendor Cards and set the E-Reporting Transaction Type on the Invoicing FastTab:

• (blank): Party is not in scope for e-reporting.
• Business-to-consumer: Sales to private individuals (B2C).
• Cross-border business-to-business: B2B transactions with parties outside France.
• Exports outside of EU: Goods or services exported outside the European Union.
• Intra-community deliveries and acquisitions: Intra-EU goods and services under the intra-community VAT regime.
• Transactions involving overseas territories: Transactions with French overseas territories (DOM/COM).

Because posted documents inherit the E-Reporting Transaction Type from the customer or vendor card at the exact moment of posting, failing to populate this field beforehand generates an uncategorized XML payload that the platform may reject.

When you create an E-Document Service with the Document Format set to E-Reporting FR, Business Central automatically registers six supported source document types: Sales Invoice, Sales Credit Memo, Purchase Invoice, Purchase Credit Memo, Service Invoice, and Service Credit Memo.

Tracking Tax Authority Acceptance​

After posting and sending e-reporting documents (either individually or in batches), administrators can monitor compliance on the E-Documents list page. The E-Reporting FR app adds an E-Reporting Acceptance Date column that reacts dynamically to the status returned by your PDP:

• If the PDP reports Approved or Cleared, Business Central stamps the exact date and time the transaction was accepted by the tax authority.
• If the status returns Rejected or Not Cleared, the acceptance date is cleared (left empty), signaling that an admin needs to inspect the PDP error log, fix the underlying issue (such as a missing transaction type), and resend the record.

Section Summary: For B2C, cross-border, and export transactions, Business Central's E-Reporting FR format automatically packages Sales, Purchase, and Service invoices and credit memos into structured XML for tax authority reporting, complete with acceptance-date tracking.

The Bottom Line for ERP Administrators​

Microsoft’s localization update for Dynamics 365 Business Central takes much of the sting out of France's transition to Continuous Transaction Controls. By embedding UBL 2.1, Factur-X, inbound invoice parsing, French BR-FR validation checks, and Transaction E-Reporting directly into the standard E-Document framework, businesses don't have to bolt on clumsy external file-conversion utilities.

However, ERP administrators should treat the "automatic" enablement label on Roadmap ID 576832 with healthy IT realism. Having the code live in your tenant does not mean your system is ready for a tax audit. Between auditing every customer and vendor card for SIRET/SIREN numbers and E-Reporting Transaction Types, preventing duplicate workflow triggers on the EDOC category, and contracting with a DGFiP-accredited PDP provider, there is plenty of configuration work to tackle. If you want to compare how other enterprise teams are handling European e-invoicing connectors and ERP migrations, check out our ongoing Dynamics 365 administration and enterprise compliance discussions right here on WindowsForum.com.