PDF to E-Invoice in France: Factur-X, UBL & CII automation
PEDIF prepares PDF invoices as structured invoice data for the French target workflow, validates the defined output and prepares the handoff to the agreed platform route.
Technical process information, not legal or tax advice. The exact scope must be assessed for each company, transaction, recipient and platform.










Since 1 September 2026, businesses within the scope of the French reform must be able to receive e-invoices through an approved Plateforme Agréée (PA). Large companies and Entreprises de Taille Intermédiaire (ETIs) must issue e-invoices for covered transactions and transmit the required e-reporting data. SMEs, small businesses and micro-enterprises follow for issuing and e-reporting on 1 September 2027.
What is specific about the French e-invoicing process?
An approved platform is central
Under the French reform, statutory transmission and reception run through a platform approved by the DGFiP. A compatible solution may sit in front of it technically, but does not replace the approved platform.
Three core formats
UBL, CII and Factur-X form the core format set. Factur-X combines a human-readable PDF/A-3 representation with embedded structured CII XML data.
A PDF alone is not enough
A normal PDF sent by email is not an e-invoice under the reform. Covered B2B transactions require structured invoice data and the prescribed platform route.
French e-invoicing timeline
All businesses within the reform scope must be able to receive e-invoices through a Plateforme Agréée.
Large companies and ETIs must issue e-invoices for covered B2B transactions; e-reporting follows the same staged timeline.
SMEs, small businesses and micro-enterprises move to mandatory e-invoice issuance and the corresponding e-reporting obligations.
Target format, approved platform, recipient/directory data, mandatory fields, status handling and exception handling should be defined for the actual process.
When does the PEDIF approach fit?
- Your ERP, billing or specialist systems reliably produce PDF invoices but not the required structured French target output.
- Several recurring PDF layouts or satellite systems need to be connected without an immediate source-system rebuild.
- You need defined data mapping, validation and exception handling rather than a blind file converter.
- The structured output should be prepared for handoff into an existing e-invoicing, ERP, EDI or platform architecture.
- You want to start with selected layouts and expand the scope in a controlled way.
Factur-X, UBL and CII in the France workflow
| Format | Role in the French process | Type |
|---|---|---|
| Factur-X | Hybrid format: PDF/A-3 as the readable representation plus embedded structured CII XML data. Useful when a visual invoice should remain part of the target format. | PDF/A-3 + CII XML |
| UBL | Structured XML syntax within the French core format set for machine-processable invoice data. | Structured XML |
| CII | UN/CEFACT Cross Industry Invoice; structured XML syntax within the French core format set and the structured basis used by Factur-X. | Structured XML |
How PEDIF fits into the France process
PEDIF remains the technical bridge between a PDF-based source system and structured invoice output. Statutory transmission, reception and e-reporting are handled by the Plateforme Agréée.
PDF input
The existing ERP, billing or specialist system produces the recurring PDF invoice.
Recognize & map
PEDIF recognizes approved layouts and maps relevant header, line, tax, total and reference data.
French target structure
The data is prepared for the agreed Factur-X, UBL or CII target route and project rules.
Validate
Mandatory fields, syntax, totals, tax logic and document consistency are checked within the defined scope.
Prepare handoff
The validated output is prepared for the agreed platform or integration route to the Plateforme Agréée.
PEDIF and the Plateforme Agréée: clear responsibilities
PEDIF handles within the defined scope
- PDF layout recognition and data mapping
- Structuring into the agreed target route
- Technical validation and plausibility checks
- Exception handling and controlled handoff
The Plateforme Agréée handles
- Statutory invoice transmission and reception
- Routing between participating platforms
- Transmission of required data to the French administration
- Status, transaction and e-reporting functions within the platform scope
France production checklist
- Determine legal scope and covered transactions
- Select the Plateforme Agréée and technical integration route
- Define target format, profile and recipient requirements
- Review representative PDF layouts and available mandatory data
- Define mapping and validation rules
- Test status, error and exception handling
- Review regulatory content and dates regularly
The French reform in practice: data, statuses and preparation
The French e-invoicing reform changes more than the file format. It adds new mandatory invoice details, introduces status messages and separates e-invoicing from e-reporting. The following sections summarize what matters for companies whose invoices still start as PDFs.
New mandatory details on French invoices
With the reform, invoices between companies in France have to carry additional information that many PDF invoices do not show today:
- The SIREN number of the buyer
- The delivery address, if it differs from the buyer's address
- The category of the transaction: supply of goods, provision of services or both
- Whether VAT is paid on the basis of debits, if the supplier has chosen this option
Where the missing data comes from
If a value is not printed on the PDF, conversion alone cannot create it. PEDIF can add such values from rules or master data, for example the buyer's SIREN from your customer records or the transaction category from the type of invoice. Values that cannot be determined reliably are routed for review instead of being guessed, so the structured invoice does not contain assumptions.
E-invoicing and e-reporting: two different obligations
E-invoicing covers domestic transactions between companies subject to VAT in France. These invoices are exchanged in structured form through approved platforms.
E-reporting covers transactions that are not exchanged as French e-invoices, in particular sales to private consumers and international transactions, as well as certain payment data. For these, transaction and payment data are reported to the tax administration through the platform. A company can therefore be affected by both obligations at the same time.
Invoice lifecycle statuses
In the new system an invoice is not simply sent and forgotten. Platforms exchange status messages that show what happened to it, for example whether it was submitted, rejected, refused by the buyer or paid. Some of these statuses are mandatory. For the issuing company this means that exceptions become visible earlier, but it also means that invoice data has to be correct from the start, because a rejected invoice produces a status that has to be dealt with.
Choosing a Plateforme Agréée
The tax administration publishes the list of approved platforms. Companies choose one or more platforms for issuing and receiving invoices. Useful criteria are the supported formats, the connection options to your ERP or billing system, how statuses and e-reporting are handled, and support for international business partners.
PEDIF does not replace the platform. It prepares the structured invoice from your PDF and hands it to the platform route you have chosen, so the source system can stay as it is.
Companies invoicing in both Germany and France
Many companies with a German entity also invoice customers in France, or the other way round. The two systems use related standards but different formats and delivery routes: XRechnung or ZUGFeRD in Germany, Factur-X, UBL or CII through approved platforms in France.
If invoices come from the same billing system as PDFs, PEDIF can create the required output per recipient from the same layout. The rules for each country, such as mandatory details, target format and delivery route, are maintained once and applied automatically.
Invoices to customers outside France
Invoices to customers abroad are not exchanged as French e-invoices through the platforms. Instead, the transaction data is reported through e-reporting. Which invoice format the foreign customer accepts depends on that customer and on the rules in their country. If your billing system produces PDF invoices for French and foreign customers alike, PEDIF can route each invoice to the right output and channel.
Credit notes and corrections
Credit notes and corrected invoices follow the same rules as invoices and must also be exchanged in structured form within the scope of the reform. They have to be marked with the correct document type and should refer to the original invoice. Including them in testing early avoids surprises after go-live, because they often use slightly different layouts than regular invoices.
Common pitfalls
- Missing or outdated SIREN numbers in customer master data
- Delivery addresses that are printed inconsistently or not at all
- Unclear transaction category for invoices that combine goods and services
- Choosing the platform too late to test the connection properly
- Treating the reform as a pure format change and ignoring statuses and e-reporting
How to prepare your PDF invoices
- Check which of your invoices fall under e-invoicing and which under e-reporting
- Make sure SIREN numbers and delivery addresses are available in your master data
- Decide which approved platform you will use and which formats it accepts
- Collect sample invoices for each recurring layout, including credit notes
- Test the structured output with the platform before the deadline that applies to you
More questions about e-invoicing in France
- Do we need a French entity to be affected?
- The e-invoicing obligation applies to businesses established in France and subject to VAT there. Foreign companies should check their specific situation, for example if they are registered for VAT in France, with their tax advisor.
- Can we keep producing PDF invoices in our billing system?
- Yes. The billing system can continue to produce PDFs. What changes is that the invoice must be exchanged in a structured format through an approved platform. PEDIF creates that structured output from the PDF.
- Is Factur-X the same as ZUGFeRD?
- Factur-X and ZUGFeRD are technically aligned and share the same structure: a readable PDF with embedded XML data. Which profile and version is required depends on the French platform and recipient.
- Who sends the e-reporting data?
- E-reporting data is transmitted through the approved platform. PEDIF can prepare structured invoice data, but the transmission to the administration is part of the platform's role.
- When should we start testing?
- As early as possible before the deadline that applies to you. Testing early leaves time to fix master data, clarify transaction categories and check the connection to the chosen platform.
Frequently asked questions
Contact Us
Questions, need help choosing the right setup?
Book a Meeting
Prefer to talk directly? Pick a time that works for you.
The calendar is provided by Microsoft Bookings and loads when you click.