If you’re a VAT-registered business in France trying to get your head around e-invoicing, you’ve almost certainly come across two names: Factur-X France and Peppol. They appear constantly in compliance discussions and DGFiP guidance — yet what each one actually does, and how they fit together, often isn’t explained clearly.
This guide cuts through the noise. We’ll look at both standards from a practical angle, walk through the Electronic Invoice Format rules that sit behind them, and flag what your business needs to have sorted before your compliance deadline arrives.
What Is Factur-X?
Factur-X France is best described as a smart PDF — and more specifically, a Hybrid Invoice Format. It looks like any other invoice on screen — your accounts team can open and read it without special tools. But inside that PDF sits a structured XML data file carrying all the invoice information in machine-readable form. That’s what your ERP or accounting software actually processes.
The XML layer in Factur-X France uses the Cross-Industry Invoice (CII) standard — one of three structured formats the DGFiP accepts alongside UBL and standalone CII. Every mandatory field must be present: SIREN numbers, VAT data, supplier and buyer identifiers, line-item detail, and payment terms. Missing or incorrectly mapped fields will fail validation.
Factur-X France was built as a joint Franco-German project and sits within the European EN 16931 standard. There are several compliance profiles, starting at Minimum and going up to the full EN 16931 level. Each step up adds more required fields, so picking the right profile for your transaction types isn’t something to leave to a default setting.
How Factur-X Supports E-Invoicing
One reason Factur-X France has been widely adopted is that it solves a real practical problem. Not every trading partner can process structured data automatically — some are still opening PDFs and keying invoices by hand. Factur-X France handles both: the PDF layer works for manual processes, while the XML feeds directly into automated systems.
What matters from a compliance standpoint is that the XML layer is actually there and correct. A regular PDF invoice, however neatly formatted, doesn’t meet the DGFiP’s structured data requirement. Factur-X France satisfies that requirement only when the embedded XML is complete and properly mapped — the visual PDF is essentially just packaging.
If your business uses FreshBooks Electronic Invoicing France, it’s worth checking specifically that Factur-X France output is enabled and generating valid XML — not just producing a PDF. The two are easy to conflate in software settings, and a PDF-only export won’t hold up when the DGFiP comes looking.
Once the invoice is ready, it goes through a certified PDP or Chorus Pro. The platform handles transmission and passes the required tax data to the DGFiP automatically.
Relationship Between Factur-X and Peppol
Here’s where a lot of businesses get confused. Factur-X France and Peppol aren’t alternatives to each other — they’re doing different jobs at different levels. Think of the format as describing what the invoice looks like. Peppol describes how it gets from one place to another.
Peppol is a pan-European exchange network built around a four-corner model: your system connects to an access point, which routes the document to your trading partner’s access point, and on to their system. In France, some certified PDPs run Peppol-compatible infrastructure. Peppol BIS Billing 3.0, based on UBL, is one of the accepted Electronic Invoice Format options under the mandate.
For businesses running Dynamics 365 Finance France E-Invoicing, the ERP configuration and transmission setup are separate concerns. Getting the invoice format right in D365 is only half the job — confirm your PDP integration routes it correctly too.
Technical Requirements for Businesses
Getting technically compliant requires going through each element carefully rather than assuming defaults cover everything. Here’s what needs to be confirmed before go-live:
- Format output: make sure your system can actually produce UBL, CII, or Factur-X France files — not just PDFs. Confirm this covers every document type you issue, including credit notes, debit notes, and advance payment invoices, not just standard sales invoices.
- Field completeness: every mandatory DGFiP field needs to be populated on every document. SIREN numbers are the most common gap — run a data quality check on both your customer and supplier master records before go-live.
- PDP connection: your integration with your chosen certified PDP needs to be tested end-to-end for every document type in scope. A clean test on a standard invoice tells you nothing about how credit notes will behave.
- Reception: regardless of when your own issuance deadline falls, you need to be able to receive structured invoices right now. If a large enterprise supplier sends you a structured invoice today and your system can’t handle it, that’s already a problem.
- Archiving: the DGFiP requires original transmitted files to be kept and retrievable for the full retention period. Double-check that your setup is storing the complete invoice file, not just a reference or summary.
Teams using Workday France E-Invoicing should work through this list against their specific configuration. Many settings require explicit setup, and the default configuration often won’t cover every scenario the French mandate requires.
Benefits of Structured Invoice Data
It’s easy to think of e-invoicing as purely a compliance exercise. But businesses that move to structured Digital Compliance invoicing often find genuine operational wins once the setup work is done.
The most immediate gain is fewer errors. When invoice data arrives as structured XML rather than a scanned PDF, there’s no manual re-keying. That alone cuts a significant source of mistakes in accounts payable — wrong amounts, mismatched purchase orders, supplier reference errors. Automated validation also catches issues like incorrect SIREN numbers before they reach the payment run.
For higher-volume businesses, reconciliation that used to take hours gets reduced when invoice data maps cleanly to PO records. Month-end reporting is faster when you’re pulling from structured data rather than extracting figures from PDFs.
For FreshBooks Electronic Invoicing France users, structured invoicing also simplifies VAT audits. You have a clean, retrievable archive of transmitted invoice files exactly as the DGFiP expects to see them — no hunting through email attachments.
Preparing Systems for Compliance
The businesses that struggle most with Digital Compliance deadlines usually aren’t the ones that misunderstood the rules — they’re the ones that left configuration work too late or tested too narrowly. Starting early and being systematic makes a real difference.
Start by mapping every document type your business issues and receives — not just the standard invoice. Credit notes, debit notes, advance payment invoices: each one needs to be in scope. Once you have that list, confirm each type is covered in your output configuration and PDP integration.
Then test each type through your PDP’s staging environment, not just internal validation. A document that passes your system’s own checks can still fail at the PDP if a required field is missing or formatted incorrectly.
Don’t skip the data quality work. SIREN number errors are the single biggest cause of transmission failures, and they’re almost always more widespread than businesses expect before they actually look.
If you’re using Dynamics 365 Finance France E-Invoicing, remember that e-reporting is a separate configuration from invoice transmission. Both need to be tested before your first reporting period closes — don’t assume a successful invoice transmission test means the reporting data flow is also working correctly.
It’s also worth looking at how comparable mandates work in other markets if your business operates across borders. The poland e invoice system, for example, follows similar principles around format requirements and platform routing, and the implementation lessons from one market transfer reasonably well to another.
Finally, Workday France E-Invoicing teams should have a rejection-handling process ready before go-live. Transmissions do get rejected. A documented process for identifying the cause, correcting it, and resubmitting is far easier to build before you need it than during a live billing cycle.
Conclusion
Factur-X and Peppol each play a distinct role in France’s e-invoicing setup. The format standards define what the invoice contains and how it’s structured. The network infrastructure determines how it gets transmitted. Both need to be right, and both need proper end-to-end testing before you go live — across all document types, not just the straightforward ones. Getting that foundation right from the start is what separates a clean compliance rollout from one that causes problems the moment it hits production.
FAQs
Q1: What is Factur-X and how does it apply in France?
A hybrid PDF and XML invoice format accepted under the French DGFiP mandate.
Q2: Is Factur-X mandatory in France?
It is one of three accepted structured formats alongside UBL and standalone CII.
Q3: How does Peppol relate to French e-invoicing?
Peppol is a transmission network; some certified PDPs use it to route invoices.
Q4: Do small businesses need to receive structured invoices now?
Yes. Reception obligations apply to all VAT-registered businesses from the start.
Q5: How long does a typical France e-invoicing implementation take?
Usually four to eight weeks, depending on system complexity and document types.
Source by:
Image by Gemini
