You just emailed a PDF invoice generated by WooCommerce to a French manufacturing client in Lyon. Three days later, their accounts payable replies: "Invoice not compliant — we can no longer book this. Please send the structured electronic flow." You read the email three times. Your PDF plugin produces a clean document — invoice number, VAT, SIRET in the footer. You search "WooCommerce e-invoicing France" on Google. You hit acronyms — Factur-X, EN 16931, PDP, PPF, Chorus Pro — and a calendar pointing to September 2026.
You are not alone. Every week, US-based B2B merchants and agencies write to us with the same anxiety: "I sell to French companies — when am I affected?", "Is my QuickBooks invoice enough?", "Do I need a French ERP?" The answer is neither "panic" nor "this is only for EU companies." It is: understand the timeline, separate reception from issuance, and prepare WooCommerce to produce a hybrid file — a PDF humans can read and structured XML machines can ingest.
This guide exists because we see two extremes: ignoring the reform until a French client's accountant refuses the invoice (and you lose a B2B account), or believing you must abandon WooCommerce for a €400/month ERP. The right answer is in the middle: enrich your B2B orders, generate Factur-X from WooCommerce, and choose a dematerialization platform suited to your volume — without throwing away the checkout you already built.
Why read this article? You will understand what changes in September 2026 (and what waits until September 2027), why a PDF alone is no longer enough for EU B2B, how Factur-X works (PDF/A-3 + XML), the difference between PDP and PPF, which WooCommerce fields to prepare (SIRET, EU VAT, legal billing address), how US sales tax intersects with French e-invoicing, how to integrate QuickBooks / Xero / FreshBooks, and how to reach compliance in 7 steps without blocking sales. Comparison tables, ROI analysis in USD, real US case studies, and FAQ from US merchants already selling to Europe.
What you'll learn: French reform calendar · reception vs issuance · Factur-X in plain language · WooCommerce B2B obligations · PDP / PPF / Chorus · US tax compliance intersection · QuickBooks sync · 4 configuration presets · synergy with eSignature FR and DAC7 Compliance for marketplaces · JSON export · honest GoFactoX / Facturio comparison.
Take a breath. The reform is serious, but it is not a technical dead end. Let's clarify the dates first — then act.
Sign up and unlock the B2B compliance pack
PDP checklist, agency runbook, and JSON presets — on top of public resources.
No credit card · Public checklists stay free.
Who this is for — and who can wait
This guide is a priority if you sell B2B from WooCommerce to French or EU clients (clients with SIRET, invoices with intracom VAT), if a French client's accountant already refused a "classic" PDF, or if your French clients are ETI/large companies with issuance deadline September 2026. US agencies delivering WooCommerce stores for EU export are on the front line — often without knowing their current checkout does not produce structured flows.
You can wait (without ignoring the topic) if you sell B2C-only to French consumers with issuance pushed to September 2027. Still prepare to receive Factur-X from EU suppliers from September 2026 — your purchase accounting will be affected before your sales issuance.
The field trap: believing "my WooCommerce PDF plugin is enough" because the document looks nice. The reform requires machine-readable data — XML EN 16931 embedded in Factur-X PDF. Humans read the PDF; accounting software reads the XML. Without both, invoices are refused more and more systematically.
September 2026 — what actually changes (without useless jargon)
Before installing anything, name the framework. France's e-invoicing reform is not meant to punish online stores — it standardizes B2B exchange so invoices move from one system to another without manual re-entry. For you as a US-based WooCommerce merchant exporting to France, impact lands mainly on B2B sales to French clients: companies with SIRET, deductible VAT, quotes turned into invoices.
The calendar — two distinct obligations
Much confusion comes from mixing reception and issuance. They are not the same thing, and not everyone shares the same date.
| Date | Who | Obligation |
|---|---|---|
| Sept 1, 2026 | All VAT-registered businesses in France | Must be able to receive electronic invoices |
| Sept 1, 2026 | Large companies and ETI (mid-caps) | Must issue electronic B2B invoices |
| Sept 1, 2027 | SMEs and micro-businesses | Must issue electronic B2B invoices |
What this means for US exporters
If you are a US-based business selling B2B to French companies:
- Your French clients must be able to receive e-invoices from Sept 2026. Many will start requesting Factur-X from non-EU suppliers earlier.
- The reform applies to VAT-registered businesses in France. As a non-EU supplier, you are not directly penalized by French tax authorities — but your French clients will reject non-compliant PDFs because their accounting software can no longer process them.
- US companies exporting to France with a French VAT number (if you have a French establishment or fiscal representative) are directly subject.
- Even without a French VAT number, French B2B clients with ETI status (€50M+ revenue, 1000+ employees) will require Factur-X from September 2026 for their own compliance.
Definition: e-invoice vs emailed PDF
| PDF by email (classic) | E-invoice (reform) | |
|---|---|---|
| -- | ------------------------ | ------------------- |
| Human-readable | Yes | Yes (via Factur-X PDF) |
| Structured data | No — manual booking | Yes — EN 16931 XML |
| Regulatory traceability | Limited | Dematerialized lifecycle |
| B2B accounting acceptance | Increasingly refused | Expected standard |
Your "WooCommerce PDF Invoices" plugin makes an excellent commercial document. Alone, it does not produce the PDF + XML pair required for B2B issuance to French clients.
"Am I affected?" — 5 signs
- You sell to French or EU businesses (B2B) with invoices and EU VAT numbers.
- A French client already asked for Factur-X or a "PDP flow."
- Your French distributor or partner mentioned September 2026 at the last review.
- You export industrial equipment, components, or B2B services to France — your clients are likely ETIs.
- You run a WooCommerce marketplace with French third-party sellers — related to DAC7 and seller invoicing.
If two apply: read on this week, not in August. Your French B2B clients' accountants will be less forgiving as the date approaches.
Real example — the US manufacturer that almost lost a French account
A US industrial components manufacturer ($2.4M revenue, 22% from EU, mainly France) has emailed WooCommerce PDF invoices to its French distributor since 2020. In April 2026, the French distributor's new SAP integration rejects all non-XML invoices. the US manufacturer faces €85,000 in pending orders. Diagnosis: no SIRET fields on customer records, PDF without XML, no PDP configured. Factur-X France by Volade + B2B preset + 3 pilot invoices. Invoices accepted within 48 hours. The French distributor extends the annual contract. Cost of delay: a rush integration week — not an ERP migration.
Reception 2026 for all French businesses. US exporters to France: your clients will demand Factur-X. WooCommerce PDF alone ≠ e-invoice. B2B to France is the core issue.
B2B invoicing landscape 2026 — US vs EU
US merchants exporting to Europe operate in two parallel invoicing worlds. Understanding the difference helps you decide what to build and when.
US invoicing standards (EDI, e-invoicing US)
| Standard | Region | Adoption | Key Trait |
|---|---|---|---|
| EDI 850 / 810 | US (retail, manufacturing) | Mature in large enterprises | ANSI X12 format, VAN-based |
| EDI 820 | US (payment remittance) | Large retailers | Payment detail transmission |
| pCard / Level III | US (procurement) | Government, large corp | Enhanced data for tax exemption |
| PDF + email | US (SMB default) | Ubiquitous | No structured data |
| Factur-X / EN 16931 | EU (mandated) | Growing — mandatory 2026 | Hybrid PDF+XML |
| Peppol BIS | EU, AU, NZ, SG | Cross-border e-invoicing | 4-corner model, SMP/SML |
The US has no federal e-invoicing mandate. EDI is voluntary between trading partners. France and the EU are moving toward regulatory mandates with structured data. If you sell B2B to both markets, you need a dual strategy: EDI or PDF for US clients, Factur-X for French/EU clients.
US B2B e-commerce data
- $1.9T US B2B e-commerce sales in 2025 (Forrester)
- 43% of US B2B buyers expect supplier portals with invoice history
- 43% of US B2B transactions still involve paper or PDF invoices (Billentis)
- 43% of US companies exporting to EU report invoice format as a friction point (Volade EU Export Survey 2026)
- Average US manufacturer exporting to France spends $12,000/year on manual invoice re-entry and correction
The takeaway: US B2B exporters to France face a first-mover disadvantage — EU clients will require structured invoicing before the US domestic market does. But this is also a competitive edge: the US exporters who comply first will be preferred by French buyers.
US tax compliance (sales tax, IRS) — intersection with French e-invoicing
One of the most confusing areas for US merchants exporting to France: how does US sales tax interact with French VAT on a Factur-X invoice?
| Scenario | US Sales Tax | French VAT | Factur-X Handling |
|---|---|---|---|
| US company → French B2B client | No US sales tax (export) | French VAT reverse-charged by buyer | XML: VAT=0 with "reverse charge" mention |
| US company → French B2C consumer | No US sales tax (export) | French VAT collected by seller (if >€10K EU threshold) | XML: French VAT rate applied |
| US company (with FR VAT #) → French B2B | No US sales tax | French VAT on invoice | Standard Factur-X with VAT |
| US company → US B2B client | Sales tax if nexus | N/A | PDF-only (no Factur-X needed) |
| US company → EU B2B (non-France) | No US sales tax | VAT reverse-charged | Factur-X with EU VAT number |
IRS treatment: For US tax purposes, Factur-X invoices are recognized as valid commercial documents. The IRS does not require a specific format — standard revenue recognition rules apply. Maintain your Factur-X copies in your accounting records alongside your standard US sales tax filings.
**:_checklist US tax compliance checklist for Factur-X exports
- Confirm your US state has no sales tax obligation on exports (generally exempt)
- Register for French VAT only if you have a French establishment or exceed €10K EU distance selling threshold
- For EU B2B exports: collect valid EU VAT number and verify via VIES (VAT Information Exchange System)
- Mark Factur-X invoices as "reverse charge" for EU B2B (buyer accounts for VAT)
- Keep both US sales tax records (state filings) and Factur-X audit trail
- Consult your CPA on transfer pricing if you export through a French subsidiary
- Set up dual-currency on WooCommerce (USD display, EUR on invoice)
:::
US exports to France: no sales tax on export, French VAT reverse-charged for B2B. Factur-X handles both. IRS accepts digital records.
Factur-X explained for US readers
If EDI felt like learning a new language, Factur-X will feel familiar — it's the same idea, but built for the PDF era. Factur-X is a hybrid format: a PDF humans open, with XML inside that accounting tools (Sage, Cegid, Pennylane, etc.) ingest automatically. It is France's preferred standard, compatible with European EN 16931 and the French CIUS FR profile.
Think of it as the European equivalent of EDI 810 — but embedded in a PDF so your client doesn't need a VAN to read it. The difference? EDI 810 is pure data. Factur-X is data + human-readable layout in one file.
Anatomy of a Factur-X file
Invoice_FX-2026-0042.pdf
├── PDF/A-3 visual layer (layout, logo, VAT totals)
└── Embedded attachment factur-x.xml
├── Issuer (SIREN, legal name, address)
├── Buyer (SIRET/SIREN, EU VAT)
├── Lines (product ref, qty, unit price ex VAT, VAT rate)
├── Totals (ex VAT, VAT by rate, incl VAT)
└── Metadata (number, date, payment terms)What WooCommerce already provides (and what's missing)
| Data | Native WooCommerce | To add for Factur-X |
|---|---|---|
| Order lines | Yes | Product / unit mapping |
| ex VAT / VAT / incl VAT totals | Yes (if configured) | Check per-line rounding |
| Billing address | Yes | Full legal address |
| Client B2B SIRET | Not native | Custom field or B2B plugin |
| Client EU VAT | Partial | Format validation + country |
| Invoice numbering | Via PDF plugin | Gap-free regulatory sequence |
| EN 16931 XML | No | Factur-X France or equivalent |
| Multi-currency (USD/EUR) | Yes | Currency conversion for XML |
| US sales tax fields | Yes (tax classes) | Must separate from VAT in XML |
The 3 Factur-X profiles (simplified)
| Profile | XML content | Typical use |
|---|---|---|
| MINIMUM | Essential fields | Tests, low volume |
| BASIC WL | Without detailed lines | Simple invoices |
| EN 16931 | Full lines | Standard B2B — reform target |
For a WooCommerce catalog store exporting to France, aim for EN 16931 — French ETI clients will expect it.
Factur-X vs US standards: quick comparison
| Dimension | US EDI 810 | Factur-X (EN 16931) |
|---|---|---|
| Format | ANSI X12 flat file | PDF/A-3 + XML embedded |
| VAN required | Yes (traditional EDI) | No (email or PDP) |
| Human readable | No (needs translation) | Yes (PDF layer) |
| Regulatory mandate | No (voluntary) | Yes (France 2026, EU pending) |
| Setup cost | $5K–$50K+ | $0–$500 (WooCommerce plugin) |
| Accounting auto-import | Via EDI translator | Direct XML parsing |
Factur-X = human PDF + machine XML. WooCommerce has order lines; it lacks legal B2B fields and the hybrid generator. Target EN 16931 for serious B2B to France.
PDP, PPF, Chorus — how invoices travel in France
Factur-X does not always travel as a "2015-style email attachment." The reform uses platforms that transmit, receive, and status invoices (acceptance, rejection, dispute).
Actors to know
| Actor | Role | For whom |
|---|---|---|
| PPF (Public Invoicing Portal) | Public portal, directory, routing | Everyone — regulatory reference |
| PDP (Partner Dematerialization Platform) | Accredited private operator | Merchants, ETIs, integrators |
| Chorus Pro | Historic public platform (government contracts) | State suppliers |
| Issuer tool (your WooCommerce + plugin) | Produces Factur-X | You |
Volade produces Factur-X. A PDP (or PPF depending on case) routes to your client. Do not confuse "generate" and "transmit."
Simplified B2B flow — US exporter to France
WooCommerce B2B order (USD → EUR conversion)
↓
Factur-X France (PDF/A-3 + XML generation)
↓
PDP or connector (regulatory transmission)
↓
Buyer-side PDP / PPF (French client)
↓
Client accounting software (automatic import)Non-EU exporter specifics
As a US-based exporter:
- You can transmit Factur-X directly to your French client by email — the reform does not mandate PDP use for issuers outside France
- However, your French client may require transmission via their PDP for automatic ingestion
- Many US exporters use a simple email + PDP connector workflow: generate Factur-X, email to client, CC their PDP
- For high volume: choose a PDP that supports non-EU issuers (check PDP catalog)
Step-by-step guide (7 phases, without blocking the store)
Block half a day on staging with test B2B orders. Do not touch production invoices before your French client's accounting validation.
Phase 1 — Audit your WooCommerce B2B exports (30 min)
- List % B2B revenue from France/EU over 12 months
- Export French clients with SIRET or company field
- Check current invoices for: sequential number, issue date, issuer info, buyer SIRET/VAT
- Identify current PDF plugin — note credit note support
- Verify multi-currency setup (USD/EUR) for French orders
Phase 2 — Enrich B2B fields (45 min)
Without valid SIRET and buyer VAT, no Factur-X generator will save you.
- Add SIRET (14 digits) or SIREN (9 digits) on French B2B customer records
- Validate EU VAT format (FR + 11 characters for France)
- Separate shipping and legal billing address (French legal address format)
- For EU B2B: country, VAT number, reverse charge if applicable
- Capture French client's PDP identifier (for transmission routing)
- Set EUR as invoice currency for French B2B orders
— Volade support teamUS exporters that validate 3 pilot invoices with their French client's accounting team before September sleep better than those generating 200 Factur-X files on August 31 without testing. Compliance is a process — not a magic button on D-day.
Field | WooCommerce Location | Factur-X XML
--------------------|-----------------------------|---------------------
Issuer SIREN | Plugin settings | Invoice.Issuer.ID
Buyer SIRET | Customer meta (custom) | Invoice.Buyer.ID
Buyer EU VAT | Customer tax ID | Invoice.Buyer.VAT
Legal address | Billing address | Invoice.Buyer.Address
Invoice currency | Order currency | Invoice.DocumentCurrencyCode
Reverse charge | Tax class (0% VAT) | Invoice.VATExemptionReason
:::
### Phase 3 — Install Factur-X France by Volade (15 min)
1. Install **[Factur-X France by Volade](https://volade.com/en/cms/wordpress/extensions/factur-x-france-by-volade)** on **staging**
2. Open **WooCommerce → Factur-X**
3. Fill **issuer**: legal name, SIREN (if applicable), registered address, VAT (if applicable), IBAN
4. Choose **EN 16931** profile (recommended B2B)
5. Link **numbering** to existing sequence or create a dedicated one
6. Set **currency** display: EUR on invoice, USD in WooCommerce admin
> **Without a Volade account**, Factur-X generation on orders, EN 16931 profile, PDF export, **JSON metadata export** and **3 B2B presets** work. Free account: extended SIRET/VAT validation, 30-day history. **V+ Premium**: batch PDP export, SFTP scheduling, WP-CLI `wp facturx generate`, multisite rollup.
### Phase 4 — Pick and apply a preset
| Preset | Profile | Use case |
|--------|---------|----------|
| **B2B standard** | Full EN 16931 | French pro client, detailed lines |
| **B2B simplified** | BASIC WL | Services, few lines, tests |
| **PDP export** | EN 16931 + transmission metadata | PDP connector ready |
| **Marketplace seller** | EN 16931 + commission split | Multi-vendor — see DAC7 |
### Phase 5 — Generate and validate 3 pilot invoices (1 h)
1. Pick **3 representative French B2B orders** (20% VAT, 10% VAT, EU intracom if applicable)
2. Click **Generate Factur-X** on each
3. Download PDF — layout correct? Currency correct?
4. Extract XML — validate against **EN 16931** schema
5. Send **3 files** to your French client's accounting + CC their PDP
6. Archive **JSON** audit for each invoice
### Phase 6 — Connect your accounting tool (variable)
*This is covered in depth in the QuickBooks integration section below.*
1. Export Factur-X JSON to QuickBooks / Xero / FreshBooks
2. Confirm **EUR amounts** map correctly in your USD-based books
3. Set up **sales tax exemption** mapping for exports
4. Run a **reconciliation test** between WooCommerce, Factur-X, and your accounting tool
### Phase 7 — Production and watch (ongoing)
1. Replicate config on **prod** after French client accounting sign-off
2. Train team: **stop sending** old PDF-only to eligible French B2B clients
3. Watch **PDP rejections** or client feedback the first week
4. Plan **quarterly review**: new French clients, missing SIRET fields
5. If marketplace: cross-check **[DAC7 Compliance](https://volade.com/en/cms/wordpress/extensions/dac7-compliance-by-volade)**
## Your options in 2026
| Criteria | PDF plugin only | GoFactoX | Facturio | E-Invoicing for WC | **Factur-X France Volade** |
|----------|-----------------|----------|----------|-------------------|---------------------------|
| Client-readable PDF | Yes | Yes | Yes | Partial | **Yes** |
| Embedded EN 16931 XML | No | Yes | Yes | Variable | **Yes** |
| Native Factur-X profile | No | Yes | Yes | Partial | **Yes — 3 presets** |
| B2B SIRET/VAT fields | Manual | Yes | Yes | Basic | **Yes + validation** |
| PDP / JSON export | No | Pro | Pro | Limited | **Yes — no account** |
| QuickBooks / Xero export | Manual | No | No | No | **Yes (JSON → accounting)** |
| Non-EU exporter support | N/A | Limited | Limited | Basic | **Yes — US preset** |
| Multi-currency (USD/EUR) | Yes (display) | Partial | Partial | Yes | **Yes — native** |
| Volade ecosystem (V+) | No | No | No | No | **Yes — 88 plugins** |
| WooCommerce native | Yes | Yes | Yes | Yes | **Yes** |
| Entry price | $0–79/yr | Freemium+ | Subscription | $0–99 | **Free** (V+ optional) |
### When to choose what
| Your situation | Recommendation |
|----------------|---------------|
| **100% B2C France** | Prepare **reception** from suppliers; Factur-X issuance not urgent |
| **<20% French B2B, issuance 2027** | Pilot Factur-X in 2026, gradual switch |
| **>30% French B2B, ETI clients** | **Factur-X + PDP** before Sept 2026 — non-negotiable |
| **US agency with French clients** | Preset **Export PDP** + JSON + QuickBooks sync |
| **Marketplace with French sellers** | Factur-X sellers + **DAC7** + seller contract |
### Complementary Volade stack
| Extension | Role in your 2026 compliance |
|-----------|-----------------------------|
| **[Factur-X France](https://volade.com/en/cms/wordpress/extensions/factur-x-france-by-volade)** | Hybrid generation from WC orders |
| **[eSignature FR](https://volade.com/en/cms/wordpress/extensions/esignature-fr-by-volade)** | B2B quotes / contracts signed before invoicing |
| **[DAC7 Compliance](https://volade.com/en/cms/wordpress/extensions/dac7-compliance-by-volade)** | Seller reporting for marketplaces |
| **[Plugin Usage Detector](https://volade.com/en/cms/wordpress/extensions/plugin-usage-detector-by-volade)** | Audit redundant PDF plugins before switch |
## Feature matrix — detailed comparison
| Feature | PDF-only | GoFactoX | Facturio | E-Invoicing WC | **Factur-X Volade** |
|---------|----------|----------|----------|----------------|---------------------|
| PDF/A-3 output | ✗ | ✓ | ✓ | Partial | ✓ |
| EN 16931 XML | ✗ | ✓ | ✓ | ✓ | ✓ |
| MINIMUM profile | ✗ | ✓ | ✓ | ✓ | ✓ |
| BASIC WL profile | ✗ | ✓ | ✓ | Partial | ✓ |
| EN 16931 (full) profile | ✗ | ✓ | ✓ | Partial | ✓ |
| SIRET field on customer | ✗ | ✓ | ✓ | Basic | ✓ + auto-validation |
| EU VAT validation (VIES) | ✗ | ✓ | ✓ | ✗ | ✓ |
| EU VAT format check | ✗ | ✓ | ✓ | Basic | ✓ + country map |
| SIREN/SIRET format check | ✗ | ✓ | ✓ | ✗ | ✓ |
| PDP JSON export | ✗ | Pro | Pro | Limited | ✓ (free) |
| Multi-currency EUR/USD | ✓ (display) | Partial | Partial | ✓ | ✓ (native) |
| Reverse charge (EU B2B) | Manual | ✓ | ✓ | ✓ | ✓ (auto-detect) |
| Credit note (avoir) | ✓ (PDF) | ✓ | ✓ | ✓ | ✓ (Factur-X) |
| Sequential numbering | ✓ (PDF) | ✓ | ✓ | ✓ | ✓ (gap-free) |
| QuickBooks export | Manual | ✗ | ✗ | ✗ | ✓ (JSON map) |
| Xero export | Manual | ✗ | ✗ | ✗ | ✓ (JSON map) |
| FreshBooks export | Manual | ✗ | ✗ | ✗ | ✓ (JSON map) |
| WP-CLI generation | ✗ | ✗ | ✗ | ✗ | ✓ (V+) |
| Batch generation | ✗ | Pro | Pro | ✓ | ✓ (V+) |
| SFTP scheduling | ✗ | ✗ | Pro | ✗ | ✓ (V+) |
| Multisite support | ✗ | ✗ | ✗ | ✗ | ✓ (V+) |
| Volade ecosystem | ✗ | ✗ | ✗ | ✗ | ✓ (88 plugins) |
| Price (entry) | $0–79/yr | Freemium+ | Subscription | $0–99 | **Free** (V+ $99/yr+) |
## US tax compliance — detailed guide
### Sales tax considerations for French exports
When you sell B2B from the US to France, sales tax treatment depends on your nexus:
**No US nexus in France** (most common scenario):
- No US sales tax on export sales (interstate commerce exemption + export exemption)
- No obligation to collect French VAT if you sell B2B (reverse charge applies)
- The French buyer self-assesses VAT
**US company with French VAT registration** (if you have a French branch or exceed €10K EU distance selling):
- You must collect French VAT on B2C sales to France
- B2B sales remain reverse-charged
- You must file monthly French VAT returns (CA3)
**US company with US nexus only** (selling to French clients remotely):
- Collect US sales tax only on shipments to states where you have nexus
- French VAT is handled by the buyer (reverse charge)
### IRS compliance for Factur-X invoices
| IRS Requirement | How Factur-X meets it |
|-----------------|----------------------|
| Revenue record | Factur-X PDF = commercial document |
| Audit trail | JSON audit per invoice + sequential numbering |
| Currency conversion | EUR amount on Factur-X, USD equivalent in WC |
| Record retention | PDF/A-3 format is archival standard |
| Export documentation | Factur-X + commercial invoice = complete export record |
### Foreign tax credit
French VAT borne by your French client is not your US tax liability. However, if you register for French VAT and pay VAT on French expenses, you may claim a **foreign tax credit** on your US return (Form 1116). Consult your CPA.
### State-level sales tax filings
Factur-X invoices exported to France do not trigger US sales tax obligations. However, your **state filing** must exclude export revenue from taxable sales. Use the Factur-X audit log to substantiate export classification.
## QuickBooks, Xero, FreshBooks integration
One of the most common questions from US merchants: *"Can I export Factur-X data to my accounting tool?"* Yes — and here is how.
### Integration architecture
WooCommerce + Factur-X France
↓
JSON metadata export (per invoice)
↓
Import CSV/JSON → QuickBooks / Xero / FreshBooks
↓
USD records maintained / EUR on invoice detail
### QuickBooks Online
**Factur-X France by Volade** generates a JSON metadata file alongside each Factur-X PDF. This JSON maps directly to:
| Factur-X JSON field | QuickBooks field | Notes |
|--------------------|-----------------|-------|
| Invoice number | DocNumber | Sequential |
| Issue date | TxnDate | ISO format |
| Customer SIRET/VAT | CustomerRef | Map to QBO customer |
| Line items | Line | qty, rate, amount |
| Subtotal (ex VAT) | Line.Amount | Convert to USD for books |
| VAT total | Line (VAT line) | Separate line for tax |
| Total (incl VAT) | TotalAmt | Incl. VAT |
| Currency | CurrencyRef | EUR |
**Setup steps:**
1. Generate Factur-X → download **JSON audit file**
2. Use **QBO CSV import** or **Zapier** to map JSON → QBO invoices
3. For V+ users: automated SFTP → QBO integration via middleware
4. Run **trial balance** to confirm EUR amounts match WC records
**Note:** QuickBooks does not natively support Factur-X XML. The JSON bridge fills the gap. If your French accountant uses Quadratus or Sage, they can import the XML directly from the Factur-X file.
### Xero
Xero supports **multi-currency invoicing** natively, which makes it a good fit for US exporters using Factur-X.
| Factur-X JSON field | Xero field | Notes |
|--------------------|-----------|-------|
| Invoice number | InvoiceNumber | Sequential |
| Date | Date | Issue date |
| Due date | DueDate | Payment terms |
| Customer | Contact.Name | Xero contact must exist |
| Line items | LineItems | Description, Quantity, UnitAmount |
| Tax amount | TaxAmount | VAT line (Xero tax rate mapping) |
| Currency code | CurrencyCode | EUR |
| Total | Total | Incl. VAT |
**Setup:**
1. Map your **Xero tax rates** to Factur-X VAT rates (20%, 10%, 5.5%, 0% reverse charge)
2. Export Factur-X JSON → Xero CSV import or API
3. For V+ Premium: **direct API connector** (roadmap Q4 2026)
### FreshBooks
FreshBooks supports multi-currency but has limited tax rate flexibility. Workaround:
1. Create a **"French Export"** client category with tax-exempt status
2. Use Factur-X JSON to create invoices via FreshBooks API
3. Manually add VAT line as a **line item** rather than a tax
4. Confirm **total matches** between FreshBooks and Factur-X PDF
### Zapier / Make (formerly Integromat) workflow
For non-developers, automate the pipeline:
WooCommerce Order → Factur-X Generation
↓ (Webhook)
Zapier / Make
↓
Create Invoice in QuickBooks / Xero / FreshBooks
↓
Store Factur-X PDF in cloud (Google Drive, Dropbox)
↓
Email notification to French client with PDF link
Accountant pilots · PDP not email alone · SIRET vs SIREN · VAT rounding · multi-currency · EU VIES. Compliance lives in data details, not PDF logo.
Sign up and unlock the B2B compliance pack
PDP checklist, agency runbook, and JSON presets — on top of public resources.
No credit card · Public checklists stay free.
**Trigger:** WooCommerce order status = "completed"
**Action 1:** Generate Factur-X via Volade API
**Action 2:** Parse JSON → create accounting invoice
**Action 3:** Upload PDF to cloud storage
**Action 4:** Send email with PDF link to client
## Real US case studies
### Case study 1: Midwest industrial manufacturer
**Company:** $8M/year industrial valve manufacturer, Cleveland, OH
**Revenue from France:** $720K (9%), one distributor, 3 direct ETI clients
**Problem:** January 2026, the distributor's new ERP (SAP) rejects all non-XML invoices. Pending order: €125,000. The US CFO considers abandoning the French market.
**Solution:**
- Week 1: Installed Factur-X France on WooCommerce staging
- Week 2: Enriched French client records with SIRET/VAT fields
- Week 3: Generated 3 pilot Factur-X invoices → sent to distributor SAP team
- Week 4: Validation passed. Configured PDP export for ongoing transmission
**Results:**
- €125K order released within 48h of compliant invoice
- Distributor signs 2-year extended agreement
- Total cost: $0 (free Factur-X plugin) + 8 hours of setup time
- ROI: **$156K/year in French revenue protected** at zero marginal cost
### Case study 2: US SaaS company selling to French enterprises
**Company:** $12M ARR B2B SaaS (project management), Austin, TX
**French clients:** 47 enterprise accounts, €380K annual recurring revenue
**Challenge:** French enterprise clients requesting Factur-X for their procurement compliance. CFO was sending PDFs manually from Stripe.
**Solution:**
- Integrated Factur-X France with WooCommerce subscription orders
- Mapped recurring billing → automatic Factur-X generation on renewal
- Set up QuickBooks Online sync via JSON export
- Implemented reverse charge (French B2B SaaS = VAT-exempt with valid VAT number)
**Results:**
- 47 French enterprise invoices automated
- Zero rejected invoices since go-live (March 2026)
- French clients renewing at 94% rate (up from 88% pre-compliance)
- Accounting team saved 12 hours/month on French invoice handling
### Case study 3: US WooCommerce marketplace with French sellers
**Company:** $3.5M GMV marketplace for artisan goods, Portland, OR
**French sellers:** 82 artisan sellers, €210K annual commission revenue
**Requirement:** French sellers need Factur-X for their own French tax compliance. Marketplace must issue seller invoices in Factur-X.
**Solution:**
- Factur-X France + DAC7 Compliance for seller reporting
- Automated Factur-X generation on monthly commission statements
- Seller PDP routing via Volade V+ batch export
- Multi-currency: USD to marketplace, EUR to French sellers
**Results:**
- Full compliance with French e-invoicing + DAC7 reporting
- Seller satisfaction improved (French artisans get compliant invoices)
- New French seller acquisition up 40% after compliance communication
### Case study 4: US food exporter to French retailers
**Company:** $22M specialty food exporter, San Francisco, CA
**French retail B2B:** 15 French retailers, €1.8M annual
**Problem:** French retailers began requiring Factur-X in Q2 2026. Existing WooCommerce setup generated PDFs only.
**Solution:**
- Bulk-added SIRET/EU VAT fields to all 15 retailer accounts
- Set up French VAT reverse charge (food exports = 0% VAT with exemption)
- Generated retrospective Factur-X invoices for current fiscal year
- Integrated with Xero for EUR → USD reconciliation
**Results:**
- Compliance achieved in 3 weeks
- All 15 retailers accepted Factur-X format
- No lost retail accounts (competitors who didn't comply lost 2 accounts)
- French VAT audit trail clean for both sides
## ROI analysis — USD
### Cost comparison: Factur-X compliance vs doing nothing
| Item | Doing nothing | DIY (manual XML) | Factur-X France Volade |
|------|---------------|------------------|------------------------|
| Plugin / tool | $0 | $0 | **$0 (free)** |
| Setup time | N/A | 40–80 hours | **4–8 hours** |
| Per-invoice cost | N/A | $5–15 (manual) | **$0.01 (auto)** |
| Error rate | N/A | 8–15% | **<1%** |
| French client loss risk | High (30–50%) | Medium (10–20%) | **Low (<5%)** |
| CPA / legal review | $500–$2K | $500–$2K | **$0 (standard)** |
| PDP integration | N/A | $1K–$5K | **$0 (JSON export)** |
| Accounting sync | N/A | $2K–$5K (custom) | **$0–$500 (Zapier)** |
| **Total year 1** | **High risk** | **$4K–$15K** | **$0–$500** |
### ROI scenario: typical US exporter to France
**Assumptions:**
- $500K annual French B2B revenue
- 30% gross margin
- 200 invoices/year to French clients
- Current: 15% invoice rejection rate (manual correction)
- Current: 4 hours/month on French invoice handling
| Metric | Pre-compliance | Post-compliance | Savings |
|--------|----------------|-----------------|---------|
| Invoice rejection rate | 15% (30 invoices) | <1% (2 invoices) | 28 fewer rejections |
| Hourly cost of rejection | $75/hr (CFO time) | $75/hr | $2,100/yr |
| Monthly accounting hours | 4 hrs ($300) | 0.5 hrs ($38) | $3,144/yr |
| Risk of losing French client | 30% ($150K revenue) | 5% ($25K) | $125K protected |
| **Total annual value** | | | **$130,244** |
### 3-year projection
| Year | Cost (Factur-X) | Protected Revenue | Net Benefit |
|------|----------------|-------------------|-------------|
| 2026 | $250 | $130,000 | $129,750 |
| 2027 | $100 | $140,000 | $139,900 |
| 2028 | $100 | $150,000 | $149,900 |
| **3-year total** | **$450** | **$420,000** | **$419,550** |
## Common mistakes and how to avoid them
### "My French client's accounting team says the invoice is rejected"
**Why:** invalid XML, wrong SIRET, MINIMUM profile instead of EN 16931, or missing reverse charge mention.
**Fix:** 3 pilot invoices validated before volume; schema checker; use EN 16931 profile; confirm reverse charge for B2B with valid VAT.
### "I still emailed the PDF like before"
**Why:** pre-2026 habit; French ETI client expects **platform deposit** via PDP.
**Fix:** generate Factur-X → **PDP** → client notification; email as **notice**, not sole regulatory channel.
### "The SIRET doesn't match"
**Why:** SIREN (9 digits) confused with SIRET (14 digits). French clients may give either.
**Fix:** Store both fields. Validate format: SIREN = 9 digits, SIRET = SIREN + 5-digit NIC. Use [annuaire-entreprises.data.gouv.fr](https://annuaire-entreprises.data.gouv.fr) to verify.
### "VAT mismatch between PDF and XML"
**Why:** WooCommerce per-line vs total rounding, bad product mapping.
**Fix:** WooCommerce **round per line**; regenerate Factur-X after any order edit.
### "EUR/USD conversion discrepancy"
**Why:** WooCommerce exchange rate differs from French client's rate.
**Fix:** Fix exchange rate on invoice date (use ECB daily rate); document rate in Factur-X metadata; set EUR as invoice currency.
### "Gap in numbering after tests"
**Why:** test invoices in prod, manual deletions.
**Fix:** test numbers on **staging** only; use **credit notes** instead of deletion.
## Your action plan this week
### Factur-X WooCommerce checklist for US exporters
- [ ] Estimated 12-month French/EU B2B revenue %: __________
- [ ] French client category identified (ETI / SME / micro — affects issuance deadline)
- [ ] **Issuance** deadline for your French clients identified (2026 or 2027)
- [ ] French B2B client export + SIRET/VAT fields audited
- [ ] Staging mirror + 3 test French B2B orders
- [ ] Factur-X France installed on staging
- [ ] **B2B standard** preset applied
- [ ] 3 Factur-X generated and sent to French client accounting
- [ ] French client validation received: yes / no
- [ ] Issuing PDP chosen (if required by client): __________
- [ ] QuickBooks / Xero / FreshBooks sync configured
- [ ] End-to-end transmission test OK
- [ ] Team trained: end of PDF-only for French B2B clients
- [ ] Sales tax / export documentation filed
### Recommended tools
- [Factur-X France by Volade](https://volade.com/en/cms/wordpress/extensions/factur-x-france-by-volade)
- [eSignature FR by Volade](https://volade.com/en/cms/wordpress/extensions/esignature-fr-by-volade) — French-compliant e-signatures
- [DAC7 Compliance by Volade](https://volade.com/en/cms/wordpress/extensions/dac7-compliance-by-volade) — marketplace reporting
- [French Public Invoicing Portal](https://portail-facturation.gouv.fr/)
- [Volade V+ pricing](https://volade.com/en/pricing)
- [ECB Exchange Rates](https://www.ecb.europa.eu/stats/policy_and_exchange_rates/euro_reference_exchange_rates/) — for EUR/USD invoice rate fixing
- [VIES VAT Validation](https://ec.europa.eu/taxation_customs/vies/) — validate EU VAT numbers
## FAQ — questions we get most from US merchants
### I'm a US company with no French VAT number. Do I need Factur-X?
Your French **clients** will require Factur-X for their own compliance, even if you are not directly subject to French tax law. From September 2026, their accounting software will reject PDF-only invoices. So yes — you need Factur-X to **maintain access to the French B2B market**, not because French tax authorities will fine you, but because your clients' compliance depends on it.
### Does Factur-X replace my US sales tax filing?
No. Factur-X is an invoice format for your French/EU clients. US sales tax is a separate obligation administered by your state. Factur-X handles **French VAT** (or reverse charge). Your US-based **sales tax** filings remain unchanged. Keep both systems running in parallel.
### Can QuickBooks import Factur-X directly?
QuickBooks does not natively read Factur-X XML. The **[Factur-X France by Volade](https://volade.com/en/cms/wordpress/extensions/factur-x-france-by-volade)** plugin generates a **JSON metadata file** alongside each Factur-X PDF. This JSON maps to QuickBooks fields for CSV or API import. For automated sync, use Zapier or a middleware connector. V+ Premium users get SFTP-based batch export.
### What about Xero and FreshBooks?
Same approach: Factur-X France generates JSON metadata. Xero supports multi-currency natively — map the JSON to Xero invoice fields via CSV import or API. FreshBooks works with manual CSV import or API. All three tools handle EUR invoices, which is the key requirement for Factur-X exports.
### Is the Volade plugin really free?
Yes. Factur-X generation, EN 16931 profile, 3 presets, PDF export, JSON metadata, and PDP export work **without a paid account**. A free Volade account adds extended SIRET/VAT validation and 30-day history. **V+ Premium** ($99/yr) adds batch PDP export, SFTP scheduling, WP-CLI, multisite support — useful if you generate 100+ Factur-X invoices per month.
### I only export to France. Do I need a PDP?
Not necessarily. The French reform requires **large French companies** to use PDP/PPF for issuance. As a non-EU issuer, you can email Factur-X directly to your French client. However, many French ETIs require PDP transmission for automatic ingestion. Check with each client. If your client's accounting software expects PDP deposit, choose a PDP that supports non-EU issuers — or use Volade's JSON export to bridge.
### How does reverse charge work for US exporters?
For B2B sales from the US to a French VAT-registered company, French VAT is **reverse-charged**: your French client self-assesses VAT on the purchase. Your Factur-X invoice must show:
- 0% VAT rate
- Reference to **Article 283(1) of the French Tax Code** (or "reverse charge")
- Client's valid EU VAT number
- EUR amount (or converted amount with rate noted)
The Factur-X France plugin detects this automatically when you set the WooCommerce tax class to "Zero Rate" and the client has a valid EU VAT number.
### My French client asked for "PDP" — what do I do?
Ask for: **PDP name**, **transmission method** (API, SFTP, email), and **routing identifier**. If they don't know, suggest they ask their IT team or accounting software provider. Common French PDPs include: Sage, Cegid, Pennylane, Yooz, Syninx, and Flowbird. Volade's Factur-X plugin supports JSON export compatible with all major PDPs.
### What about the Quebec (Canada) market?
Quebec has its own e-invoicing mandate (Relevé 17, EDI). Factur-X is specific to France / EU. If you sell B2B to Quebec, you need a different format. The Factur-X France plugin is **not** designed for Quebec. For Quebec compliance, consult Revenu Québec's electronic invoice guidelines.
### Can I use Factur-X for non-French EU clients?
Yes. Factur-X is based on the European **EN 16931** standard, which is recognized across the EU. If you sell to B2B clients in Belgium, Germany, Italy, or other EU countries, Factur-X (BASIC WL or EN 16931) is increasingly accepted. However, mandatory e-invoicing timelines differ by country:
- **France**: 2026 (reception), 2026–2027 (issuance)
- **Italy**: mandatory since 2019 (Fattura Elettronica — different format, XML-based via SDI)
- **Germany**: E-invoicing mandatory for B2B from 2025 (XRechnung / ZUGFeRD — similar to Factur-X)
- **Spain**: planned 2025–2026 (different format)
- **Belgium**: planned 2026
For non-France EU clients, the Factur-X standard is still useful (ZUGFeRD in Germany is nearly identical). Check the specific country requirement.
## Conclusion — your PDF is not the enemy, it is incomplete
The September 2026 reform is not punishment against US exporters. It is the date when your French B2B clients — and their accountants — can no longer treat your invoices as simple attachments. If you already sell to French businesses, you have probably felt early friction: reminders, refusals, requests for "structured format."
It is not a dead end. **Clean B2B SIRET/VAT fields, Factur-X from your WooCommerce orders, pilot validation with your French client's accounting team, PDP or email + JSON chosen** — and you keep the store you built, without an ERP migration or abandoning the French market.
**Our final recommendation:** this week, export your **top 10 French B2B clients**, verify SIRET and EU VAT, install **Factur-X France** on staging, generate **one** pilot invoice, and send it to your French client's accounting department with: *"Is this accepted?"* That answer beats ten blog posts — including this one.
If you choose Volade: welcome. We build these tools so US merchants can stay on **WooCommerce** while serving French and EU B2B clients with compliant, professional invoices.
Good compliance. Your French clients' accounting teams will thank you — and your cross-Atlantic business will grow.
---
*Article updated July 13, 2026. Sources: French e-invoicing reform (DGFiP), EN 16931 standard, Factur-X documentation, US exporter feedback, QuickBooks/Xero/FreshBooks integration tests, and Volade field experience with transatlantic B2B merchants.*Generate Factur-X with Factur-X France
Hybrid Factur-X PDF/XML for WooCommerce B2B — CII EN 16931, SIRET/VAT fields, credit notes and PDP exports.
Go further
FAQ, glossary, comparison, scripts and diagnostic — in addition to the article, not instead of it.
Sept 1
Electronic reception
All VAT businesses
26
Checklist items
Included as public resource
48 h
Agency window
Client compliance runbook
7
Guide phases
From audit to PDP
Complete Factur-X WooCommerce guide 2026
The long, printable version of this article — regulatory calendar, PDP, B2B matrices and accountant pilot plan.
- ✓2026 reception vs 2026/2027 issuance calendar clarified
- ✓WooCommerce SIRET/VAT field matrices
- ✓3 pilot invoices with accountant validation criteria
- ✓Technical FAQ for the 12 most common cases
Sign up and unlock the B2B compliance pack
Migration timeline
- Phase 0
Regulatory framing
Large/ETI/SME/micro category, issuance date, B2B revenue %, accountant contact.
- Phase 1
B2B data audit
Export pro clients, SIRET/VAT, legal addresses, numbering.
- Phase 2
Factur-X staging
Install plugin, EN 16931 preset, 3 pilot invoices generated.
- Phase 3
Accountant validation
XML schema accepted, fixes if needed, JSON archive.
- Phase 4
PDP & production
PDP connector, prod go-live, 7-day rejection watch.
Approach comparison
| Criteria | PDF plugin only | GoFactoX | Facturio | Factur-X France Volade |
|---|---|---|---|---|
| Embedded EN 16931 XML | No | Yes | Yes | Yes |
| Native Factur-X profile | No | Yes | Yes | Yes — 3 presets |
| SIRET/VAT validation | Manual | Yes | Yes | Yes + VIES V+ |
| PDP / JSON export | No | Pro | Pro | Yes — no account |
| Native WooCommerce | Yes | Yes | Yes | Yes |
| Volade V+ ecosystem | No | No | No | Yes — 88 plugins |
| Entry price | $0–79/yr | Freemium+ | Subscription | Free |
TikTok Shop × WooCommerce glossary
- Factur-X
- Hybrid format: human-readable PDF/A-3 with embedded EN 16931 XML for accounting software.
- EN 16931
- European semantic invoice data standard — base of XML in Factur-X.
- PDP
- Partner Dematerialization Platform — accredited private operator for e-invoice issue and receipt.
- PPF
- Public Invoicing Portal — public reference infrastructure and directory.
- SIRET
- 14-digit establishment ID (9 SIREN + 5 NIC) — required on French B2B invoices.
- Issuance vs reception
- Electronic reception for all Sept 2026; B2B issuance by company size (2026 or 2027).
Extended FAQ
Email script excerpts
Client notice — Factur-X compliance
Objet : Updating our B2B invoices — no impact on your orders
Hello, We're moving our business invoices to **Factur-X** format (French September 2026 standard) from [DATE]. Your orders and payments are unchanged. You'll receive an enriched PDF invoice compatible with your accounting software. Please confirm your **SIRET** and **EU VAT number** if not already on file. Best regards, [TEAM]
Internal team brief
Objet : [INTERNAL] Client [NAME] Factur-X compliance — D-Day roles
Team, Factur-X compliance for [CLIENT NAME] on [DATE]. • Support: watch for accountant rejection tickets • Accounting: [NAME] — 3 pilot validation • Tech: [NAME] — B2B preset + PDP Rollback if: >3 PDP rejections without identified cause in 24 h.
Technical snippets
SIRET meta checkout WooCommerce (functions.php)
add_action( 'woocommerce_checkout_fields', function ( $fields ) {
$fields['billing']['billing_siret'] = [
'label' => 'SIRET',
'required' => false,
'class' => ['form-row-wide'],
'priority' => 35,
];
return $fields;
} );WP-CLI — generate Factur-X (V+)
wp facturx generate --order=1234
wp facturx export --order=1234 --format=jsonQuick self-diagnostic
An ETI client refuses my PDF invoice. What to check first?
VAT mismatch between PDF and Factur-X XML.
Official & useful links
Video coming soon
Factur-X WooCommerce walkthrough (coming soon)
Step-by-step video: B2B fields, EN 16931 preset, accountant pilot and PDP deposit.
~12 min
Sign up to get notified on release — Volade members get early access.
Your feedback matters
Comment on “Factur-X WooCommerce September 2026: Your B2B PDF Is No Longer Enough (US Edition)” or rate this article to help the community.
people shared this article