France’s new e-invoicing and e-reporting framework

France’s upcoming e-invoicing and e-reporting mandate represents a major transformation in VAT compliance. Built on a decentralized model that combines accredited private platforms with centralized oversight from the Direction Générale des Finances Publiques (DGFiP), the reform reshapes how transactional data is issued, transmitted, validated, and reported.

With phased enforcement beginning in September 2026, businesses must understand not only the deadlines, but also the architecture, formats, lifecycle rules, and master data requirements that will determine compliance success. To support this transition, the DGFiP has also introduced practical guidance tools to help businesses identify their specific obligations and prepare for compliance.

Why the French mandate is different

France is setting a new standard for digital VAT reporting in Europe, and it is not just following Italy or Poland. While Italy’s Sistema di Interscambio (SdI) and Poland’s KSeF rely on fully centralized clearance systems, France has chosen a hybrid Y-Schema model that combines central oversight with flexible access through government-accredited private platforms. This approach balances scalability, automation, and comprehensive tax visibility, making France’s system more sophisticated than its neighbors.

What truly sets France apart is its dual obligation: mandatory e-invoicing for domestic B2B transactions and mandatory e-reporting for B2C and cross-border transactions. Together, these requirements give the DGFiP, the French tax authority, end-to-end visibility over VAT-relevant economic activity. For businesses, this is more than digitalization: it is a structural redesign of transactional tax reporting, requiring new processes, master data discipline, and platform strategies.

The phased timeline in France

September 1, 2026: All companies must be able to receive electronic invoices; large and mid-size enterprises must begin issuing them.

September 1, 2027: SMEs and micro-businesses must begin issuing electronic invoices.

The e‑reporting deadlines align with the same phasing.

This staggered implementation reflects the scale of transformation and ensures operational stability before full enforcement.

France’s distinct e-invoicing jargon

• DGFiP (Direction Générale des Finances Publiques): France's tax authority overseeing the e-invoicing mandate.

• PPF (Portail Public de Facturation): The central business directory and tax data hub (no direct business‑to‑business exchange).

• PA (Plateforme Agréée): Private platforms accredited to exchange and report invoice data. These were previously known as Plateforme de Dématérialisation Partenaire, or PDP, but were officially renamed in February 2026 to Plateformes Agréées (PA), reflecting a terminological preference by the tax administration (DGFiP) as part of France’s 2026 Finance Act (Loi de Finances pour 2026).

• SC (Solution Compatible): In‑house or third‑party software that creates invoices and connects to one or more PAs; cannot connect directly to the PPF.

• SIREN: 9-digit unique identifier for French legal entities (company registration number).

• SIRET: 14-digit identifier for specific business establishments/sites (SIREN + 5-digit location code).

• Factur-X: France’s hybrid format combining a human-readable PDF with embedded XML for automated processing.

• UBL 2.1: International XML standard (Peppol-compatible), ideal for cross-border trade.

  CII (UN/CEFACT CII): Global cross-industry XML standard for complex B2B transactions.

• Dépôt - invoice status: Invoice successfully submitted and timestamped by the issuer's PA.

• Rejet/Refus - invoice status: Invoice rejected (platform validation failure or buyer refusal).

• Encaissée - invoice status: Payment data confirmed (date + amount received).

Know the players: PPF, Plateformes Agréées, and Solutions Compatibles

France’s e-invoicing system is built around a three-part ecosystem, where each actor has a specific role, and their interactions ensure compliance, automation, and VAT visibility. Understanding who does what is essential for businesses selecting platforms, software, and operational workflows. Businesses evaluating accredited platforms can explore jefacture.com, a compliant solution designed to manage validation, transmission, and automated reporting under the French mandate.

The architecture at a glance

The French model follows a hybrid, so-called “Y-Schema” architecture:

• Solution Compatibles (SCs) create the invoice.

• Plateformes Agréées (PAs) validate, transmit, and report invoices.

• Portail Public de Facturation (PPF) coordinates routing, maintains the central directory, and ensures the DGFiP receives the required data.

Operational flow:

The operational path is issuer’s EPR or (optionally) SC → issuer’s PA → receiver’s PA → receiver’s SC/ERP, with the PAs respectively reporting data to the PPF as required:

This structure balances central oversight with flexible private-platform access, allowing both large and small businesses to scale efficiently while keeping the tax authority fully informed.

What a French invoice looks like

Now that we understand the actors and the architecture of France’s e-invoicing system, it’s time to look inside the invoice itself, the payload that travels through SCs, PAs, and the PPF. The invoice is not just a PDF; it is a structured data file that must meet specific compliance requirements.

Supported formats (socle minimal)

France allows three interoperable formats, each with its own characteristics:

• Factur-X

  1. Hybrid format: a human-readable PDF with embedded XML for machines;

  2. Popular for both small and large businesses;

  3. Ensures readability while supporting automation.

• UBL 2.1

  1. International XML standard, widely used in the Peppol network;

  2. Ideal for cross-border trade.

• UN/CEFACT CII

  1. Global cross-industry XML standard for electronic data exchange;

  2. Common for international B2B transactions.

Invoice payload: Key data points

Every invoice sent in France must include mandatory information to pass validation:

Data mapping: Translating ERP to compliance

The challenge is not just the format, it’s mapping your internal ERP data to the DGFiP’s mandated schemas. Pursuant to the External Specifications (Specifications Externes) issued by the DGFiP, to ensure interoperability with the PPF, businesses must comply with the data structures defined in the Z12-012 and Z12-014 schemas, published by the Association Française de Normalisation (AFNOR) standard body.

• Ensure all mandatory fields are populated.

• Match internal codes to official classifications (goods/services, VAT regime).

• Validate SIRET/SIREN numbers against the central directory.

This step is crucial: France’s e-invoicing system does not tolerate incomplete or misformatted data. Unlike some countries where validation is optional, the DGFiP enforces strict compliance at the platform level.

Invoice lifecycle & e‑reporting

Understanding France’s e-invoicing system isn’t just about actors or data formats - it’s about what actually happens every time an invoice is sent. The operational workflow determines compliance, VAT accounting, and business efficiency.

Step-by-step invoice flow

When you issue an invoice, it travels through a structured lifecycle with mandatory status updates:

• Issuer → PA

  • Your ERP or SC generates the invoice and sends it to your designated PA.

  • The PA validates format and data completeness (SIRET, VAT, payment terms).

• PA → Recipient PA → PPF

  • The issuer's PA transmits the invoice to the recipient's PA.

  • The PA also automatically reports the necessary summary data to the DGFiP via the PPF data hub.

• Recipient PA → Recipient

  • The buyer’s PA receives the invoice and delivers it to their ERP/SC.

  • Mandatory statuses are updated throughout the PA-to-PA exchange.

For businesses, it’s important to understand that, while the PA handles the heavy lifting in the operational flow, the business remains responsible for the "final" status of the invoice.

Mandatory statuses

Each invoice generates traceable status updates that affect VAT processing, whereby PAs must support and make available to their customers at least the following four invoice statuses:

While the full lifecycle includes additional transitional states (e.g., Processed, Transmitted, Expired), those are more platform-specific. The four listed above are the core operational statuses that businesses track.

Status updates are critical for tracking invoice flow and ensuring timely VAT reporting, even though VAT chargeability still follows the underlying tax rules (e.g., delivery, performance, payment).

E‑reporting for B2C & cross-border transactions

For transactions outside domestic B2B invoicing (e.g., selling to a consumer in Lyon, purchasing services from a Frankfurt supplier, or exporting to New York), structured summary data must also be transmitted:

• Scope: B2C sales taxable in France, exports, and non-established taxpayers.

• Simplifications: Since September 2025, line-level details are no longer required in certain B2C scenarios, reducing administrative burden.

• Integration: PAs typically handle this automatically; SCs must ensure proper mapping and transmission.

Day-to-day implications for businesses

1. Monitoring statuses is essential: A “Rejected” or “Refused” status requires immediate correction and issuing a new invoice with corrected data (using a new invoice number). It is not possible to edit and resend the original XML.

2. Invoice errors can disrupt VAT reporting: Missing SIRETs, incorrect VAT rates, or incomplete payment info can delay compliance.

3. Automation is key: Using a PA that integrates with your ERP reduces manual intervention and ensures e-reporting is complete.

4. End-to-end visibility matters: Teams must track both invoice flow and reporting outcomes to avoid gaps.

Practical readiness: Master data and go‑live checklist

As the September 1, 2026, deadline approaches, preparing your systems, data, and processes is critical. France’s e-invoicing and e-reporting mandate is strict: even minor errors in data or routing can block invoices and delay VAT reporting. This section gives practical guidance for going live.

1. Audit your master data

The national e-invoicing ecosystem relies on a central directory (Annuaire) to route invoices. To avoid rejections, your master data must be impeccable:

Primary identifiers:

• Ensure you have the SIREN (9 digits) for every French B2B customer.

• While the SIRET (14 digits) identifies specific sites/branches, and can be stored by the directory if a company wants to route invoices to specific branches, the SIREN is the mandatory legal requirement for the new e-invoice format.

The "new four" fields:

Verify your ERP can capture and output four new mandatory data points:

• The customer's SIREN,

• the specific delivery address (if different from billing),

• the category of operation (Goods vs. Services),

• and the supplier's VAT payment regime (specifically "VAT on debits" status).

Practical steps:

If you’ve not already done so, now is the time to run a “data cleansing” project to fill any gaps in the required customer and supplier master data:

• Verify that all French customers and suppliers have correct and up-to-date SIREN and, if applicable, SIRET numbers in your ERP.

• Check that addresses, VAT numbers, and payment terms are complete and consistent. The central directory will reject invoices with invalid or missing geographic data.

• Run a test batch of invoices to identify missing or mismatched data before go-live.

Tip: Even a small mismatch between the data in your ERP and in the Annuaire registry will result in an immediate invoice rejection on the platform and block VAT reporting. The Annuaire will be the "source of truth" that every PA must query before sending an invoice.

2. Evaluate provider capabilities

Choosing the right platform or software is crucial for a smooth go-live:

• Confirm your PA supports Peppol interoperability (important for receiving invoices from foreign suppliers).

• Check that your PA can convert your ERP outputs into approved formats (Factur-X, UBL, or CII) without losing data integrity.

• Ensure the PA handles status updates automatically (Deposited, Refused, Accepted) and integrates with your accounting workflows.

Many companies opt for accredited private platforms such as jefacture.com to ensure automation, format validation, and secure PA-to-PA transmission.

Businesses that are still assessing how the French mandate applies to their operations can use the DGFiP's guided questionnaire, "Electronic invoicing: understand my obligations in 4 clicks". The tool provides tailored information based on company characteristics and helps identify applicable e-invoicing and e-reporting obligations.

3. Prepare for compliant electronic archiving

Beyond invoice transmission and e-reporting, businesses should also ensure compliant electronic archiving practices. In May 2026, AFNOR published FD Z42-029, practical guidance for the electronic archiving of invoices within the framework of France’s upcoming reform.

Key archiving objectives include:

• Preserving invoice integrity and authenticity throughout the retention period

• Ensuring long-term readability of structured invoice formats

• Maintaining evidential value for audit and legal purposes

• Securely storing invoices and associated status data

Practical steps:

• Confirm that your ERP, PA, or archiving provider supports compliant electronic retention

• Ensure structured invoices and status updates can be stored without data alteration

• Verify that archived invoices remain accessible and readable over time

4. Define routing logic

Large organizations often have multiple subsidiaries or departments. Proper routing is essential:

• Assign routing identifiers for each entity within your ERP.

• Make sure your PA or SC recognizes these codes and transmits invoices to the correct recipient.

• Test routing logic with a few pilot invoices to catch errors early.

5. Test end-to-end processes

Before go-live, perform full end-to-end simulations:

1. Create invoices in your ERP or SC.

2. Send them through the PA.

3. Confirm status updates (Deposited → Accepted/Refused).

4. Verify e-reporting is automatically generated and sent to the DGFiP via the PPF.

5. Correct any errors and resubmit as needed.

During onboarding, companies may also need to complete a formal mandate model authorizing the platform to transmit invoices and e-reporting data on their behalf.

Tip: This stress test ensures your teams and systems are ready for high-volume operations on Day 1.

Final checklist: Consolidation & risk mitigation before go‑live

As the go-live date approaches, it’s time for a final operational review. Even well-prepared businesses can run into last-minute issues if processes, data, or platforms are not fully aligned. This checklist focuses on consolidating readiness and mitigating risk before the September 1 launch.

1. Verify system readiness

• Ensure your ERP or SC is fully connected to your PA.

• Confirm that all platform credentials, certificates, and routing codes are active and correct.

• Test peak-volume processing if your business issues high numbers of invoices daily.

2. Validate master data one last time

• Cross-check all SIRET/SIREN numbers, addresses, VAT IDs, and payment terms.

• Run a final test batch through the PA to verify acceptance.

• Correct any errors immediately, as even small inconsistencies can trigger rejection.

3. Confirm format & data compliance

• Ensure invoices conform to approved formats: Factur-X, UBL, or CII.

• Double-check field mapping in your ERP: line items, VAT codes, payment terms, and transaction types.

• Validate that your PA correctly transforms and submits invoices without data loss.

4. Monitor status updates

• Ensure the Deposited → Refused/Accepted → Received feedback loop works end-to-end.

• Train your team to act on refused statuses immediately, correcting and resubmitting invoices without delay.

• Confirm that B2C and cross-border e-reporting flows are configured and tested.

5. Avoid common pitfalls

• Incomplete payment data: Ensure payment information is complete to avoid VAT exigibility issues.

• Format conversion issues: Validate that the PA can convert ERP outputs to approved formats without data loss.

• E-reporting oversight: Don’t neglect B2C or cross-border flows, as they are just as important as B2B invoices.

Conclusion: Preparing for France’s 2026 digital tax era

France’s 2026 e-invoicing and e-reporting mandate is more than a compliance requirement; it represents a strategic shift in how transactional finance and VAT reporting are managed. Unlike simpler systems in other countries, France combines mandatory B2B e-invoicing with B2C and cross-border e-reporting, creating a comprehensive framework that gives the DGFiP full visibility over economic activity.

For businesses, success relies on preparation and operational discipline. Accurate master data, including up-to-date SIRET/SIREN numbers, correct VAT information, and precise routing codes, is essential. Choosing the right platform or Solution Compatible (SC) and ensuring seamless integration with your ERP prevents disruptions and facilitates automatic status updates.

Early identification of errors allows for rapid correction and ensures VAT compliance from day one. To navigate this transition confidently, businesses should rely on a certified and scalable solution such as jefacture.com, which supports invoice validation, format compliance, automated e-reporting, and seamless ERP integration ahead of the September 2026 deadline.

Stay ahead of the mandates

Stay ahead of global e-invoicing mandates with our free monthly newsletter, delivered straight to your inbox with the latest regulatory updates across 50+ jurisdictions. Follow us on LinkedIn for daily compliance insights and expert analysis.