France E-Invoicing: Shopify Readiness Checklist
Prepare Shopify, ERP, and accounting workflows for France's September 2026 e-invoicing and e-reporting rollout.
Table of Contents
France's electronic invoicing reform reaches its first major operational deadline on September 1, 2026. The rollout affects receiving, issuing, and reporting on different schedules, summarized below from the official French tax authority timeline.
For Shopify merchants, this is a data and integration change rather than an invoice-template update. The practical question is how an order moves from Shopify into an ERP or accounting system, through an approved platform, and back into a traceable finance workflow when it is rejected, refunded, corrected, or paid later. Applicability can vary for foreign sellers and exempt transactions, so each entity should validate scope before implementation.
What Changes, for Whom, and When
The reform combines several operational streams. This single matrix separates the transaction scope, start date, and required route using the official scope and the French Ministry of Economy timeline.
| Obligation | Who or what | Start | Operational route |
|---|---|---|---|
| Receive e-invoices | All in-scope businesses | September 1, 2026 | Receive supplier invoices through an approved platform. |
| Domestic B2B e-invoicing | Sales between businesses established in France and subject to French VAT, subject to exclusions | Large enterprises and ETIs: September 1, 2026; SMEs and micro-businesses: September 1, 2027 | Issue a structured invoice through an approved platform. |
| Transaction e-reporting | Consumer sales and relevant transactions involving foreign operators | Same phased schedule as issuance | Transmit required transaction data through the approved-platform route. |
| Payment e-reporting | Transactions where VAT is due on collection, including certain services | Same applicable phased schedule | Transmit required collection or payment data. |
Why a Shopify PDF Is Not the Whole Solution
French guidance states that a compliant electronic invoice must use a prescribed structured format, contain mandatory information in dedicated fields, and travel through an approved platform. The accepted foundation includes UBL, CII, and mixed structured/image formats. An ordinary scanned invoice, standard PDF, or document sent by email will no longer satisfy the new transmission model.
Shopify can generate VAT invoices for eligible EU and UK orders, but that feature does not by itself prove that a French domestic B2B invoice has been routed through a French approved platform or that the appropriate e-reporting data has been transmitted. The Shopify document may remain useful to the customer, but the compliance workflow must be verified end to end.
Practical interpretation: Treat Shopify as the commerce source, not automatically as the final invoicing and reporting system. Decide explicitly whether the fiscal document is generated in Shopify, an invoicing app, the ERP, the accounting platform, or the approved platform, and ensure only one system owns invoice numbering and correction logic.
Design the Target Shopify-to-ERP Architecture
A reliable architecture separates order capture from fiscal-document ownership while keeping the records linked. The exact products will differ, but the control flow should look like this:
- Shopify captures the order, customer, company, address, product, discount, tax, payment, and fulfillment context.
- The integration classifies the transaction and passes it to the designated finance system, which owns numbering, tax logic, and document creation.
- An approved platform transmits, receives, and reports the data; statuses, rejections, refunds, corrections, and payments return to the finance workflow and remain linked to the Shopify order.
Inbound supplier invoices need the reverse path: approved platform to accounting or ERP, followed by validation, approval, posting, and payment. They normally should not be forced into Shopify unless the store has a genuine operational reason to surface them there.
Build a Field Map Before Coding
The French Ministry identifies new structured mentions including the buyer's SIREN, the transaction category, the VAT-on-debits option when applicable, and the full delivery address when it differs from the billing address. These sit alongside existing mandatory invoice data. The table below is an implementation starting point, not an exhaustive legal data dictionary.
| Data group | Example | Recommended owner |
|---|---|---|
| Parties | Seller and buyer legal names, SIREN, VAT IDs, company location | ERP/accounting and Shopify B2B master data |
| Addresses | Billing and delivery address; delivery address when different | Shopify checkout/company location, validated in ERP |
| Invoice identity | Invoice number, issue date, document type, related document | ERP/accounting or designated invoicing system |
| Commercial and tax | Items, quantities, discounts, shipping, taxable base, VAT rate and amount | Shopify, tax engine, and ERP/accounting |
| Payment | Terms, due date, collection status where reportable | Payment provider plus ERP/accounting |
| Traceability | Shopify order ID, ERP document ID, platform ID, correction links | Integration layer |
Questions to Ask Your ERP and Platform Providers
- Is the provider currently listed as an approved platform, or does it connect to one as a compatible solution?
- Which structured formats are supported, and which system owns invoice numbering and duplicate prevention?
- How are Shopify B2B fields, tax data, discounts, shipping, and addresses mapped and validated?
- Does the service cover inbound invoices, outbound invoices, transaction e-reporting, and payment e-reporting where applicable?
- How are lifecycle statuses, rejections, credit notes, and partial refunds returned to the ERP?
- Is there a sandbox with realistic rejection and outage scenarios?
- Can we export invoices, statuses, logs, and mappings, and what are the provider's security and recovery commitments?
The Minimum End-to-End Test Matrix
| Test case | Expected route | Verify |
|---|---|---|
| French domestic B2B sale | Electronic invoice | Buyer ID, tax, structured format, platform status, ERP posting |
| French consumer sale | Transaction e-reporting | Correct classification, totals, VAT, no domestic B2B invoice route |
| Cross-border B2B sale | Scope-dependent reporting/tax route | Entity, VAT treatment, country, customer data, adviser-approved logic |
| Service paid after invoice | Invoice plus possible payment e-reporting | Collection event, amount, timing, VAT treatment |
| Cancellation or partial refund | Controlled cancellation or credit workflow | No orphan record; correct amount, VAT, document link, and status |
| Subscription renewal | New order/invoice or reporting event | Contract, renewal date, payment, tax, failed-payment behavior |
| Platform or API outage | Queued and recoverable | Retry policy, idempotency, alerting, manual fallback, reconciliation |
Final Thoughts
The strongest implementation has one owner for each critical field, controlled document identifiers, tested failure paths, and a complete audit trail from Shopify order to ERP record to approved-platform status. That is the standard teams should use to judge readiness.
Frequently Asked Questions
Does a Shopify merchant need an ERP?
The reform does not make an ERP universally mandatory. A merchant may work directly in an approved platform or through compatible software. Larger or more complex stores often use an ERP or accounting system to control invoice numbering, tax, corrections, and reconciliation.
How should foreign Shopify merchants approach the French rollout?
They should first confirm establishment, VAT registration, transaction scope, and reporting obligations with a qualified adviser. A store selling to France is not automatically subject to exactly the same workflow as a French-established seller.
What invoice information should customer support be able to see?
Support should be able to view the document identifier, current platform status, rejection reference, and linked correction or credit note. Tax treatment and controlled invoice records should remain editable only by authorized finance or tax owners.