Cloud ERP in France: Mandatory E-Invoicing, Approved Platforms, FEC Files and Costs
France's B2B e-invoicing mandate has started, and the 2027 wave is close. Here's how to choose between ERP-native compliance and an approved platform, keep FEC exports audit-ready, and budget realistically.
Which French entities the e-invoicing mandate covers, and when
Before you pick or reconfigure a cloud ERP in France, settle two questions. Can your system send, receive and report invoices through an approved platform? And can it produce an FEC audit file that will hold up in a tax inspection? For a cloud ERP France rollout, those two tests matter more than any feature list.
Under the reform's phased timetable, from 1 September 2026 every VAT-registered business established in France must be able to receive e-invoices. Large and mid-sized companies must also issue them. Small and micro businesses follow on 1 September 2027. Confirm the dates with your adviser, because the calendar has shifted before.
The mandate covers domestic B2B transactions between taxable persons established in France. Consumer sales and cross-border B2B sales aren't e-invoiced through the French system. They fall under e-reporting: you send transaction and payment data to the tax administration (DGFiP) through your platform.
| Date | Receive e-invoices | Issue e-invoices and e-report |
|---|---|---|
| 1 September 2026 | All VAT-registered businesses established in France | Large enterprises (GE) and mid-sized enterprises (ETI) |
| 1 September 2027 | Already required | Small and medium enterprises (PME) and micro-enterprises |
Foreign groups often misjudge size. France uses INSEE's company categories, which look at the economic group, not just the French legal entity. Say a 30-person French sales subsidiary belongs to a multinational with 8,000 employees. It may be classed as part of a large enterprise, which puts it in the 2026 wave, not 2027. Check the category for each French SIREN before you assume you have another year.
A foreign company that holds a French VAT number but has no establishment in France is generally outside the e-invoicing obligation. Its e-reporting position is less clear, and finance laws have adjusted the scope more than once. Put that question to a French tax adviser rather than settling it internally.
What a compliant invoice flow looks like: formats, data fields and statuses
A PDF sent by email doesn't count as an e-invoice under the French reform. An invoice is compliant when it's issued in a structured format and routed through a plateforme agréée, an approved platform (formerly called a PDP). The government dropped its plan to run a free public invoicing portal. The public system now acts as a central directory and data hub, so every business needs at least one approved platform.
Accepted formats
- Factur-X: a hybrid PDF/A-3 with an embedded XML file. People can read it and systems can parse it, which suits smaller trading partners.
- UBL: a pure XML format used widely in Peppol networks in Europe and beyond.
- UN/CEFACT CII: the XML syntax Factur-X is built on, usable on its own.
Your ERP doesn't need to produce all three. It needs to produce one cleanly. Your platform should handle conversion and delivery to the buyer's platform.
New data your master data must carry
The reform adds invoice fields that many ERPs never stored in structured form:
- The customer's SIREN number
- A delivery address, where it differs from the billing address
- The type of transaction: goods, services or mixed
- Whether VAT is paid on a debit basis, where you've opted for that
This is where most projects lose time. The ERP often has a SIREN field, but half the customer records are blank or hold a SIRET (the 14-digit establishment number) where the 9-digit SIREN belongs. Clean the master data before anyone touches the integration.
Lifecycle statuses and e-reporting
Invoices move through lifecycle statuses that platforms exchange with each other and with the tax administration. Four are mandatory: submitted, rejected (by the platform), refused (by the buyer), and payment received. The last matters most for services, where VAT is due on collection. Your ERP or platform therefore has to send payment data back, not only outgoing invoices. Treasury, AR and tax must work together here. Finance teams that treat e-invoicing as an AR output problem get caught.
E-reporting follows a schedule tied to your VAT regime, and the frequency differs between regimes. Your B2C sales, cross-border B2B flows and related payment data all have to be extracted, aggregated and sent on that schedule. Confirm the exact calendar for your regime with your platform provider or adviser.
ERP-native compliance or a separate approved platform: how to decide
You have two architectures. In the first, your ERP vendor's own compliance service, or a platform the vendor owns, fills the approved-platform role. In the second, you connect your ERP to an independent plateforme agréée through an API or connector. Either way, an approved platform has to sit in the flow, because the ERP itself can't be one. The real choice is who owns that platform and how tightly it's tied to your ERP.
| Criterion | ERP-native or vendor-owned platform | Independent approved platform |
|---|---|---|
| Typical fit | Single-ERP companies, mainly French-focused mid-market | Multi-ERP groups, multi-country groups, high-volume AP |
| Integration effort | Low to moderate; prebuilt | Moderate to high; connector or API work |
| Multi-country reuse | Depends on the vendor's coverage | Often strong; many also cover other European countries and Peppol markets |
| Switching cost if you change ERP | High; compliance leaves with the ERP | Lower; the platform stays when the ERP changes |
| Who to call when a status fails | One vendor | Two parties; needs clear responsibility in the contract |
Vendors with French compliance offerings include French accounting and ERP suites such as Cegid and Sage, global ERPs such as SAP, Oracle and Microsoft Dynamics 365, and specialist e-invoicing providers such as Sovos, Pagero, Esker, Generix and Docaposte. Treat that as a starting list, not a confirmation of registration. The DGFiP publishes the official list of registered platforms. Check each vendor against it yourself, since a vendor saying it's "ready" isn't the same as being registered.
Our view: a French mid-market company on one ERP should usually take the vendor's native route, because the bigger risks are master data and statuses, not the connector. A foreign group running two or more ERPs, or facing e-invoicing mandates in several countries, should usually pick an independent platform and connect every ERP to it. You pay more for integration. In return, you avoid building a separate French compliance setup for each ERP, and you avoid redoing compliance when you consolidate ERPs in a few years.
FEC file export: the audit file your ERP must generate on demand
E-invoicing is the new obligation. The FEC file export (Fichier des Écritures Comptables) is the old one, and it still catches out foreign-built ERPs. A business that keeps computerized accounts in France must hand its accounting entries to the tax auditor in a prescribed flat-file format, and the request typically comes with little warning. A missing or non-compliant FEC can trigger a fixed penalty per financial year, or a percentage of any reassessed amount where that's higher. The bigger risk is indirect: an auditor who can't rely on your FEC can challenge your books as a whole.
What the FEC must contain
- Eighteen mandatory fields per entry line, including journal code and label, entry number and date, account number and label, auxiliary (customer or supplier) account, document reference and date, debit, credit, lettering (matching) reference and date, validation date, and foreign-currency amount and code
- Every entry for the financial year, including opening balances, in chronological order of validation
- A file name built from the SIREN, the letters "FEC" and the closing date
- Entries that can't be changed after validation
Where cloud ERPs go wrong
The usual failures are structural, not cosmetic:
- Group chart of accounts. If the French entity books to a global chart and maps to the French chart of accounts (Plan Comptable Général) only at reporting time, the FEC may show the wrong account numbers. The French ledger needs the local chart, or an alternate account held on each journal line.
- Editable posted entries. Some systems let users reverse and repost in ways that wipe out the original validation date. The FEC needs a clean, sequential audit trail.
- Missing lettering data. If payments are matched in a subledger that doesn't write the matching reference back to the general ledger, those FEC fields come out empty.
- Subledger summarization. If you post summarized AR or AP batches, the auditor sees totals where they expect individual invoice references.
Before go-live, run a full-year FEC from your test environment through the DGFiP's free validation tool (Test Compta Demat), then have your French chartered accountant (expert-comptable) review the output. A clean technical check doesn't prove the accounts are what an auditor expects to see. That's why the accountant's review matters.
Costs and timelines for French compliance on a cloud ERP
The figures below are indicative, typical 2026 market ranges in USD. Actual prices depend on contract terms, invoice volume and the number of entities. French vendors often quote in euros and per invoice, so get local quotes from each one and confirm before budgeting.
| Cost item | French SME, one entity | Mid-market, 1-3 French entities | Multinational group, multiple ERPs |
|---|---|---|---|
| Approved platform subscription (annual) | $500-$5,000 | $5,000-$30,000 | $30,000-$150,000+ |
| Per-invoice or per-transaction fees | Often bundled; $0.10-$0.60 above allowance | $0.05-$0.40 | Negotiated tiers, often under $0.15 |
| Integration and configuration (one-off) | $2,000-$15,000 | $20,000-$90,000 | $120,000-$450,000 |
| Master-data cleanup and testing | Internal effort, 2-4 weeks | $5,000-$30,000 | $30,000-$120,000 |
| FEC remediation, if not native | Usually native in French packages | $5,000-$25,000 | $20,000-$80,000 per ERP |
| Typical elapsed time | 1-3 months | 3-6 months | 6-12 months |
Three things drive cost more than anything else:
- The number of systems that issue invoices. Count billing engines, field-service tools and e-commerce platforms that bill outside the ERP.
- The share of volume that's e-reporting rather than e-invoicing. B2C retail and cross-border flows add extraction work.
- Whether payment-received statuses can be generated automatically from your cash application process.
Hypothetical worked example: say a German manufacturer has a French distribution subsidiary issuing 4,000 domestic invoices a month. Its ERP is a global SAP S/4HANA Cloud instance, and a separate subscription billing tool handles service contracts. It would likely need an approved platform connected to both systems. Plausible figures are roughly $40,000-$110,000 in one-off work, $15,000-$35,000 a year in platform fees, and a four-to-seven-month project. The billing tool is often the bottleneck, because it was never built to capture SIREN or transaction-type data.
Red flags and a rollout sequence for French subsidiaries
Watch for these warning signs when you evaluate vendors or review an existing setup:
- A vendor that calls itself "compliant" but can't name the registered platform its French flows actually go through
- Status support that covers outgoing invoices only, with no answer on receiving or on payment-received statuses
- No e-reporting coverage for B2C or cross-border transactions, which leaves you building extractions by hand
- An FEC export described as a "report" you configure yourself, with no reference to the official format
- Contracts that don't say who is responsible when the ERP and the platform disagree about an invoice's status
- Pricing that charges for received invoices at the same rate as issued ones, which inflates costs for AP-heavy businesses
For a foreign group with French entities, this sequence keeps the risk in the right order:
- Confirm the size category and e-invoicing scope for each French SIREN, plus any non-established VAT registrations, with a French tax adviser.
- List every system that issues invoices or records payments for French entities, not only the ERP.
- Fill gaps in customer SIREN, address and transaction-type data, and make these fields mandatory in master data governance.
- Choose the architecture: native if you run one ERP and operate mainly in France, independent platform if you run several ERPs or face mandates in several countries.
- Register in the national directory so invoices from suppliers' platforms reach you.
- Test issuing, receiving, rejections, refusals and payment statuses with real trading partners before cutover.
- Generate and validate a full-year FEC, then get your expert-comptable to sign off.
A simple decision rule: if your French entities already receive e-invoices but your FEC hasn't been validated in the last twelve months, fix the FEC first. If your 2027 issuing deadline is under nine months away and you haven't chosen a platform, start selection now. Either way, have a French tax adviser confirm the details, because penalties, scope and reporting frequencies have changed more than once since the reform was announced.
Common questions
Does a foreign parent company need its own approved platform for its French subsidiary?
The French subsidiary is the entity in scope, so it needs access to a plateforme agréée. That doesn't require a separate contract. Many groups sign one group-level agreement with a platform that serves several countries and connect the French entity to it. The parent's own position, particularly if it holds a French VAT number without being established in France, should be checked with a French tax adviser.
Is Factur-X enough, or do we also need UBL?
Factur-X is one of the three accepted formats, so issuing only Factur-X is compliant. Your approved platform should convert formats when a buyer's platform expects UBL or CII. Factur-X is often the practical choice for mid-market companies, because people can read it without special software and systems can parse it.
Does using a compliant e-invoicing platform also cover our FEC obligation?
No. The two obligations are separate. E-invoicing covers the exchange of invoices and transaction data. The FEC is an export of your accounting entries that you provide during a tax audit. Your ERP's accounting setup has to produce it, and it's worth validating each year with the DGFiP tool and your expert-comptable.
Written by the Logix Gridnode editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.