Skip to main content
Cabinet comptable

Factur-X / PDP: the 2026 schedule seen from the accounting firm

On 1 September 2026, large French companies must emit invoices in Factur-X via a PDP. For accounting firms, the real challenge is reception, not emission.

Équipe SwoftPôle veille sectorielle
Bureau d'expert-comptable avec écrans de saisie et factures dématérialisées

After two successive postponements, mandatory B2B electronic invoicing in France enters its active phase. The official schedule published by the French DGFiP in July 2024 confirms two milestones: 1 September 2026 for reception (all companies) and emission by large companies and mid-caps; 1 September 2027 for emission by SMEs and micro-businesses. For accounting firms, the topic is not so much emission — managed by clients via the public portal or a PDP — as reception and integration into the accounting chain.

The role of PDPs: what really changes

The Plateformes de Dématérialisation Partenaires (PDPs) are operators registered by the French tax authority to transport, validate and archive electronic invoices. The Public Invoicing Portal (PPF) remains the public fallback solution — free, but minimum service. PDPs offer value-added services: ERP integration, enriched controls, invoice lifecycle management (statuses), approval workflows.

For an accounting firm, the choice of PDP — for itself and for its clients — becomes structuring. A PDP that doesn't correctly handle statuses (rejected, paid, accounted) will generate endless client calls.

Factur-X, UBL, CII: the disorganizing trio

The reform mandates three accepted formats: Factur-X (PDF + XML, the French reference), UBL (Universal Business Language, the European format), and CII (Cross Industry Invoice, EDIFACT format). In practice, French ERP vendors favour Factur-X, international SaaS vendors push UBL, and large companies with legacy EDI often stick with CII. A firm will receive all three.

The trap: schemas are not all equivalent. Factur-X EN 16931 (the minimum profile) does not contain all the fields needed for VAT declaration. If the firm doesn't check the received profile, it can end up with an invoice compliant with the reform but unusable for VAT calculation — you have to ask for a re-issue at BASIC WL or EN 16931.

What legacy vendors don't say

OCR is no longer the right answer

For 10 years, vendors sold OCR to automate pre-accounting. With Factur-X, OCR becomes useless: data is in the XML, structured, reliable. Firms still paying €50 ex-VAT per client per month for an OCR option are paying for a service the reform makes obsolete. Vendors don't say so, because OCR represents 15-20% of their ARR per client.

The booking rule remains manual

Factur-X structures the data but doesn't classify it accounting-wise. A line "short-term vehicle rental" can go to 6135, 6155 or 6068 depending on client and context. This booking, today, remains manual — that's where firms lose most time. AI booking solutions (Receipt Bank, Pennylane, Tiime) are improving, but error rate stays around 3-5%, requiring systematic human review.

Payment status not yet connected

The reform plans for the PDP to feed back lifecycle statuses: received, refused, paid, settled. In practice, few PDPs handle the "paid" status correctly because it depends on bank reconciliation, which stays in the firm software. Result: statuses sent to the administration are incomplete, and collected/deductible VAT doesn't compute automatically.

The 2027-2028 scenario firms underestimate

From 1 September 2027, all companies (including micros) emit in Factur-X. Concretely, that means a 50-client accounting firm potentially receives 5,000-10,000 electronic invoices per month, in 3 formats, with 4-6 lifecycle statuses each. Without aggressive automation of reconciliation, consistency control and booking, entry time will not decrease — it will shift.

The topic is no longer whether to automate pre-accounting. It is whether you can build a control chain that detects anomalies (duplicates, VAT gaps, invoices not linked to a delivery note or order) before the client calls to flag a problem.

Sujets abordés

  • Factur-X
  • PDP
  • Réforme facturation électronique
  • Réglementation
  • Pré-comptabilisation
Tech translation

How Swoft turns this challenge into software

Le défi des cabinets en 2026, ce n'est pas la réforme, c'est de transformer la PDP en levier d'efficacité plutôt qu'en source de bruit. Voici comment Swoft équipe les cabinets et leurs clients pour absorber le flux Factur-X sans exploser l'effort de saisie.

  1. 01

    Connecteur PDP avec normalisation des 3 formats

    Réception unifiée Factur-X / UBL / CII : chaque facture entrante est normalisée vers un schéma interne stable, quel que soit le format source. Les profils non-conformes (BASIC sans TVA détaillée) sont automatiquement rejetés avec demande de renvoi structurée. Le collaborateur ne voit qu'un flux propre.

  2. 02

    Imputation IA avec apprentissage par client

    Le moteur d'imputation apprend du client (chaque correction collaborateur enrichit le modèle). Sur 1 000 factures traitées, le taux de correction descend de 30 % au mois 1 à 5-8 % au mois 6. Toutes les corrections sont traçables (qui a corrigé quoi, quand), utile pour les audits internes du cabinet.

  3. 03

    Cycle de vie de la facture rapproché du compte bancaire

    Statut PDP (reçue/refusée/payée) + statut compta (saisie/échue/lettrée) + statut bancaire (rapprochée) consolidés dans une vue unique par client. Les écarts (facture marquée payée par la PDP mais non lettrée en compta) remontent en alerte au collaborateur, avec proposition de rapprochement automatique.