E-Invoice Finder
Menu
CountriesCompare softwareDeadlinesGuidesCheckerCheck obligation
ENFRDEPLNL
France · PA pricing, contract and TCO

How to compare French approved-platform prices and contracts

Compare French approved-platform quotes by scope, volume, integration, support, contract and exit costs with a practical TCO worksheet.

Quick verdict:
  • • Compare three-year cost per shared demand baseline, not headline unit rates.
  • • Unbounded integration and change work is the largest hidden-cost risk.
  • • First, verify the legal PA entity and freeze the billable workload.
Get your France readiness reportOfficial sources
Last checked: 17 August 2026Based on official sourcesClear summaryBusiness guidance, not legal advice
Official sources prioritized
Last-checked dates visible
Free checker, no signup required

What you need to know

Guide

1. Confirm who is legally providing the regulated service

Start with the legal entity named in the proposal, not the product brand. Match the contracting and operating entities against DGFiP’s current PA list and record the date checked. DGFiP says affected businesses must use an approved platform to transmit and receive electronic invoices and send transaction and payment data from 1 September 2026. A PA can issue, transmit and receive invoices, preserve integrity, authenticity, readability and completeness during conversion, extract data, and transmit transaction and payment data. Only a registered PA can perform all regulated functions; a compatible but unregistered solution cannot do so itself. Registration lasts three renewable years, with definitive registration following real-condition interoperability tests. This proves regulatory status, not that every connector, workflow, archive or support tier is included. Require the quote to identify which registered entity performs each regulated function. Retain a dated copy of the official-list evidence with the procurement record so a later status change can be distinguished from the position assessed at award.

Guide

2. Build one billable demand baseline

Make every bidder price the same workload. List each legal entity, SIREN, relevant SIRETs and routing addresses; monthly inbound and outbound invoices; credit notes, growth and peaks; Factur-X, UBL, CII and other source formats; ERP, API and manual channels; B2C and cross-border e-reporting; payment-data reporting; users; accountant access; and test and production environments. Label estimates and ask how rejected, corrected, duplicate, test or reprocessed documents are counted. Require suppliers to state the assumptions behind their price. Attaching this baseline to the request for quote is a recommended procurement control, not an official list of mandatory data fields. It prevents one supplier pricing nominal invoice volume while another includes complex traffic.

Guide

3. Put every pricing model into the same comparison unit

Request separate lines for subscriptions, document or transaction charges, bundles, minimum spend, tiers, overage, environments and annual indexation. Define the denominator: invoices, status messages, e-reporting transmissions and payment updates may be different billable events. Confirm whether unused volume expires, tiers are incremental or retrospective, and entities can pool allowances. Prices are vendor-specific and must be confirmed in a dated quote. Build a normalisation table with columns for item, charging unit, included quantity, baseline quantity, rate, annual fixed and variable cost, one-off cost, indexation, exclusions and evidence. Use rows for access, inbound and outbound flows, reporting, payment updates, environments, archive, support and overage, ending with normalised three-year cost. This compares subscription and usage offers without treating unlike units as equivalent. Require suppliers to return the table without altering its definitions; any proposed alternative unit should appear in a separate reconciliation note.

Guide

4. Isolate implementation and production-start charges

Demand a work breakdown instead of one opaque setup fee. Price onboarding, annuaire or routing configuration, ERP and API connection, standard and custom connectors, mapping, conversion, testing, training, project management and production support separately. For each item, record whether it is fixed, time-and-materials, capped or conditional, plus ownership, acceptance criteria, included iterations and extra-work rates. Clarify who fixes source-data defects and failed mappings. Connector pricing may exclude ERP consultancy, middleware, certificate management, sandbox refreshes or upgrades. Request a responsibility matrix and sample plan. Include internal finance, tax, IT and procurement effort in TCO, and use a clearly labelled contingency variable rather than an invented standard percentage.

Guide

5. Separate regulated capability from package inclusions

PA status defines authorised regulated capability; it does not guarantee that a particular package bundles everything. Require each need to be marked included, metered, optional, third-party or unavailable. Cover sending and receiving, lifecycle statuses, corrections, e-reporting, payment data, format conversion, evidence and audit exports, archive access, dashboards, multi-entity administration and accountant access. Clarify whether archive means operational storage, an evidential service or downloadable files, without assuming a retention period. Request a sample export with its metadata. Ask whether inbound receipt, reporting-only traffic, payment updates, statuses and human support are charged separately. A signed package scope matrix is a recommended procurement control; use of an approved platform for applicable regulated exchanges is the official requirement. Do not confuse the two or assume surrounding services are free.

Guide

6. Test the contract, SLA and security evidence

Read the order form, service description, SLA, data terms and referenced online policies together. Record service hours, availability measurement, maintenance exclusions, incident severities, response and restoration targets, escalation, support languages and service credits. Request evidence for security controls, subprocessors, data and backup locations, access controls, encryption, continuity testing and incident notification. Address liability allocation, insurance evidence, audit support, regulatory or technical change control, price changes and document precedence. Check whether the SLA covers regulated exchange, portal, APIs and support equally. Prefer proof over questionnaire assertions on critical issues. These are recommended commercial and operational checks, not legal advice; qualified counsel should review liability, data protection and sector-specific terms before signature.

Guide

7. Price exit and reversibility before entry

France’s July 2026 mobility rules make provider change and continuity practical buying concerns. Consult the cited Decree and Order, and ask counsel how they apply rather than relying on an unverified sales summary. Price and document notice, transition assistance, export frequency and machine-readable formats, history and evidence, open invoices and statuses, connector decommissioning, annuaire cutover, read-only access, deletion and a deletion certificate. Define what continues during transition, who coordinates the incoming PA, and how pending corrections, reporting or payment updates are handled. Obtain sample exports before signing and test whether identifiers, timestamps, statuses and attachments remain intelligible outside the platform. Include internal remediation and parallel-operation effort. A promise of “full reversibility” is not enough: specify deliverables, responsibilities, assumptions and chargeable rates.

Guide

8. Calculate three-year TCO and stress the assumptions

Use fictional variables: F annual fixed subscription, V annual billable units, R weighted unit rate, I implementation, C annual connector cost, S annual support or archive cost, E expected exit cost, N internal labour and g annual indexation. Calculate TCO3 = I + N + (F + V×R + C + S) + (F + V×R + C + S)×(1+g) + (F + V×R + C + S)×(1+g)^2 + E. Use tier-by-tier calculations where needed; preserve minimums and overage. Run baseline, peak-month annualised, growth and low-volume scenarios, then stress an extra entity, custom mapping, heavier API traffic, premium support, delay, indexation and exit during the initial term. Show supplier cost, internal cost and contingency separately. This is a decision model, not a market-price claim; link every input to a dated quote, assumption or internal estimate. Document who owns each assumption and the date it was approved.

Guide

9. Score evidence, challenge the demo and act within 14 days

Use a 100-point scorecard: normalised TCO 30, functional scope 20, integration and implementation 15, contract and exit 15, SLA and support 10, security and evidence 10. Adjust these recommended weights before final bids, then score documented evidence and confidence. In demos, process realistic inbound, outbound, correction, reporting and export cases and show the billable events. Ask what is excluded, what may change after signature and what termination help costs. Red flags include an unidentified registered entity, undefined units, inconsistent volumes, undocumented inclusions, uncapped implementation, changeable online terms and no sample export. Avoid choosing on unit rate, ignoring minimums or internal ERP work, or treating registration as a package guarantee. Days 1–3: freeze demand. Days 4–6: issue the worksheet. Days 7–10: clarify and demo. Days 11–12: stress TCO. Days 13–14: obtain legal, security and budget approval and record the rationale.

Checklist

Match the contracting and operating entities to DGFiP’s current PA list.

Issue one volume, entity, format, reporting and environment baseline to all bidders.

Define every billable event, bundle, minimum, tier and overage rule.

Separate recurring platform charges from one-off implementation work.

Mark each workflow as included, metered, optional, third-party or unavailable.

Attach scope, assumptions, SLA and online terms to the signed contract set.

Request security, subprocessor, data-location and continuity evidence.

Price export, transition assistance, decommissioning and secure deletion.

Run three-year baseline, peak, growth and low-volume scenarios.

Score documented evidence and obtain legal, security and budget review.

FAQ

How much does a French approved platform cost?

There is no defensible universal price. Suppliers define different subscriptions, transaction units, bundles, implementation services and support levels. Ask for a dated quote against your entity count, flows, peaks, formats, reporting needs, environments and integrations, then calculate three-year TCO on identical assumptions.

Is price per invoice better than a subscription?

Neither model is inherently cheaper. Usage pricing may track activity but can expose peaks and ambiguous billable events; subscriptions may improve predictability but include minimums, volume caps or overage. Compare both under baseline, growth, peak and low-volume scenarios using the same defined unit.

Does PA registration mean every required service is included?

No. Registration establishes the provider’s regulatory status and capability to perform regulated functions. It does not establish that a specific commercial package includes every connector, workflow, archive, dashboard, support tier or multi-entity feature. Obtain a package-level scope matrix in the contract.

Can receiving invoices or e-reporting be charged separately?

Commercial packaging is supplier-specific, so ask explicitly. The quote should identify how inbound invoices, outbound invoices, statuses, B2C or cross-border transaction reporting and payment-data updates are counted, whether they consume a shared bundle, and what happens above the allowance.

Which hidden fees deserve the most attention?

Frequent blind spots include ERP-side work, custom mapping, additional entities or environments, minimum commitments, reprocessing, premium support, archive or evidence access, annual indexation, change requests and exit assistance. Treat any undefined item as an open commercial risk rather than assuming it is included.

What should an ERP or API integration quote contain?

Request connector licences, onboarding, configuration, mapping, authentication, testing, error handling, deployment, training, upgrades and production support as separate lines. State acceptance criteria, included iterations, responsibilities and extra-work rates, and confirm whether middleware or ERP consultancy comes from another supplier.

What exit clauses should a buyer request?

Seek clear terms for notice, continued service during transition, machine-readable exports, history and evidence, open-item handling, connector shutdown, directory cutover cooperation, transition assistance, deletion and certification. Check the July 2026 mobility texts with qualified counsel for your circumstances.

How can we choose without ranking named vendors?

Set weights before final evaluation, apply one demand baseline, normalise three-year costs and score only evidence. Combine TCO with functional fit, integration, SLA, security, contractual change control and reversibility. Record assumptions and confidence so decision-makers can see where further proof is needed.

Key regulations, formats and terms

FranceFrench tax administrationDGFiPimpots.gouv.frapproved platformplateforme agrééePDPFactur-XUBLCIISIRENVATe-reportingSMEmicro-enterpriseaccounting softwareEuropean CommissioneInvoicingEN 16931Directive 2014/55/EUstructured electronic invoiceVAT automationcross-border tradeFrance approved-platform pricing and contract comparison

France — Country hub

France

Open country hub →

Use the country hub to see every related deadline, checklist, format guide and software comparison for this market.

Continue reading

Official sources

We prioritize official government and EU sources where available and keep last-checked dates visible for mandate-sensitive pages.