E-Invoice Finder
Menu
Countries Compare software Deadlines Guides Checker Check obligation
ENFRDEPLNL
French software buying checklist

Sellsy e-invoicing in France: what buyers should verify

Check Sellsy’s official PA status, French rollout dates, CRM workflow, e-reporting scope, demo tests, hidden costs and contract questions before buying.

Quick verdict:
  • Score statutory coverage and workflow improvement as two separate buying tests.
  • Make exception recovery a pass-or-fail gate, not a post-launch task.
  • Require a clean, usable data export before awarding points for convenience.
Check your French e-invoicing readinessOfficial sources
Last checked: 22 July 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

Start with the business problem, not the PA badge

A buyer searching for Sellsy e-invoicing France usually needs to answer two questions: can the service support the French mandate, and will it improve daily sales and finance work? The official PA status matters, but suitability depends on your operating model. Map how quotations become invoices, where SIREN, SIRET and TVA/VAT data are maintained, who handles supplier invoices and credit notes, and which accounting system receives the final entries. Include B2B, B2C, export, intra-EU and public-sector sales because their reporting or routing needs differ. Sellsy may be attractive when CRM, invoicing, reminders, payments and reconciliation are currently fragmented. It may be less compelling if a group already has mature ERP controls or highly specialised international flows. Use a written requirements matrix and score the exact offer, not the brand in isolation.

Guide

Apply the official timetable to each entity

Service-Public confirms that every business within scope must be able to receive electronic invoices from 1 September 2026. Large companies and ETIs must also issue from that date, while SMEs and micro-enterprises begin mandatory issuance on 1 September 2027. Receiving is therefore not a reason for a smaller business to wait until 2027. Build a timetable by legal entity rather than using one group-wide date: record company size, SIREN, establishments, current billing system, customer types and expected invoice volumes. Allow time before the relevant deadline for master-data cleaning, supplier onboarding, user training, exception handling and parallel checks with accounting. Official dates describe legal milestones, not a safe project start date. Your practical deadline should be earlier, especially where several tools, advisers or entities must agree on ownership of invoice data and lifecycle statuses.

Guide

Separate Sellsy’s official PA status from your subscribed scope

The DGFiP page modified on 21 July 2026 links to the official list of operators satisfying all conditions, including interoperability tests; that list contains TeamSystem Sellsy. A Plateforme Agréée, formerly called a PDP, can emit, transmit and receive electronic invoices, extract required invoice data, and receive or transmit transaction and payment data. Registration examines tax compliance, infrastructure and data security, and interoperability. This establishes the operator’s PA status, but does not prove that every Sellsy package, module, connector, entity or workflow is included in your contract. Sellsy’s current French page says sending and receiving are available, although one FAQ retains older ‘pre-registered’ wording. Treat the DGFiP list as authoritative for status, then obtain written confirmation covering your edition, users, entities, volumes, API access, support, archive, migration, Peppol and Chorus Pro arrangements.

Guide

Trace the CRM, quotation and master-data flow

Sellsy promotes SIRENE enrichment, quote-to-invoice conversion, recurring invoices, automated reminders, purchases and margins, payment pages, bank reconciliation, accounting-production integrations and a marketplace of more than 100 applications. It also cites more than 50,000 users; these are current vendor claims, not official guarantees. In a France e-invoicing CRM workflow, convenience depends on data ownership. Decide whether Sellsy, another CRM or accounting software is the master for legal name, SIREN, SIRET, TVA/VAT number, billing address, contact, payment terms and routing information. Prevent users from creating near-duplicate customers or overwriting validated identifiers. Test amendments after a quotation, deposits, recurring charges, partial delivery, credit notes and cancelled invoices. The accounting export or connector should preserve references, tax codes, attachments and lifecycle statuses without manual re-keying. Define who approves master-data changes and how rejected directory matches are investigated.

Guide

Verify structured formats, receiving and exception handling

Ask Sellsy to demonstrate the formats and channels used for each flow, including Factur-X, UBL and CII aligned with EN 16931 where applicable. A normal PDF sent by email is not sufficient for mandated structured exchanges; a readable image alone does not provide the required machine-readable data. Even Sellsy Factur-X handling must be checked end to end: embedded data, visible document, mandatory fields, routing through the annuaire, status messages and accounting ingestion should agree. For receiving, prove how supplier invoices enter the workspace, how duplicates and malware are handled, and how staff code, approve, dispute, reject or place them on hold. Include missing purchase orders, incorrect SIRET, tax discrepancies, unreadable attachments and credit notes. Confirm archive duration, search, audit trail, bulk export and portability. Also clarify the B2G route through Chorus Pro and whether Peppol access is included, optional or handled by a partner.

Guide

Define e-reporting separately from e-invoicing

French e-reporting covers information that does not travel solely as a domestic B2B electronic invoice, including relevant B2C and international transaction data, plus payment data for certain services. Do not assume that a Sellsy approved platform label makes every source transaction complete or automatically reportable. Ask how Sellsy classifies domestic B2B, B2C, export and intra-EU activity; captures payment dates and amounts; applies corrections; consolidates point-of-sale or external billing data; and returns submission evidence and errors. Check whether the subscribed Sellsy e-reporting service accepts imports from other systems and how rejected records are repaired without double reporting. Assign responsibility between sales, finance, the accountant and the PA for data quality and deadlines. The demonstration should distinguish invoice lifecycle statuses from transaction and payment reporting, because they serve different purposes and may rely on different source fields.

Guide

Run a five-case live demonstration with your own data

Replace a polished slide presentation with five controlled cases. First, convert a quotation for a French B2B customer into a structured invoice, route it using validated SIREN/SIRET data and follow every lifecycle status. Second, receive a supplier invoice with a missing purchase order, correct it and post it to accounting. Third, issue a partial credit note against an invoice that has already been paid. Fourth, process a B2C service sale and show the related transaction and payment e-reporting evidence. Fifth, handle an export or intra-EU sale, explaining its classification and correction path. In every case, ask the presenter to switch user roles, expose the audit trail, show API or connector behaviour, export the record and recover from a deliberate error. Record expected and actual results, manual steps, elapsed time and unresolved dependencies. A trial is useful only if it reproduces your real controls.

Guide

Compare total cost, operational risk and contract fit

Sellsy advertises a 15-day free trial without commitment or card, but do not infer the final cost from that offer. Publicly indexed price figures conflict, and a verified live price should therefore come from a dated quotation. Ask whether Sellsy pricing includes the PA service, receiving, e-reporting, required CRM or invoicing modules, API calls, connectors, onboarding, migration, training, support levels, additional users, entities, invoice volumes, storage, archive and export. Model a three-year total cost and include internal process change, accountant work and fallback arrangements. Assess vendor claims such as French data hosting, ISO 27001 certification and GDPR alignment through current contractual and assurance documents. Key risks include ambiguous module scope, unsupported edge cases, manual exception queues, connector limits, data lock-in and weak support near statutory deadlines. Weight evidence from your demo and contract more heavily than feature counts.

Guide

Turn the shortlist into a documented go or no-go decision

Your next action is to send Sellsy or its reseller a one-page scope schedule listing legal entities, users, monthly volumes, source systems, formats, customer segments, payment flows and five demo cases. Request a written response that identifies included modules, PA responsibilities, e-reporting coverage, Chorus Pro and Peppol routes, API or connector limits, support service levels, data migration, archive, bulk export, portability and exit assistance. Re-check TeamSystem Sellsy on the current DGFiP list immediately before contracting, because platform information and product packaging can change. Then run the trial with representative but appropriately protected data, involve the person who posts supplier invoices and have your accountant review outputs. Approve only when mandatory flows, exceptions, ownership, costs and exit conditions have named evidence and owners. Keep unresolved points in the contract schedule rather than accepting verbal assurances or assuming they can be fixed after rollout.

Checklist

Confirm TeamSystem Sellsy remains on the current DGFiP list of Plateformes Agréées before signing.

Map every legal entity, SIREN/SIRET, user role, invoice source, customer type and applicable deadline.

Obtain a dated quotation showing modules, users, entities, volume bands, PA service and e-reporting inclusions.

Clean customer and supplier legal names, identifiers, TVA/VAT numbers, addresses and duplicate records.

Test Factur-X, UBL or CII creation, annuaire routing, lifecycle statuses, receiving and accounting ingestion.

Prove B2C, export, intra-EU and service-payment e-reporting, including rejection and correction procedures.

Document API/connectors, Chorus Pro, Peppol, support, security evidence, archive, export and migration responsibilities.

Run the five-case demonstration, cost the three-year scenario and record contractual owners for every gap.

FAQ

Is Sellsy officially a Plateforme Agréée in France?

Yes, on the facts checked on 22 July 2026. The DGFiP page modified on 21 July links to the official list of operators that satisfy all conditions, including interoperability tests, and the list contains TeamSystem Sellsy. That is stronger and more current evidence than legacy wording on a vendor page that still says ‘pre-registered’. Re-check the official list before contracting, and remember that operator approval does not define which modules, entities, volumes, connectors or services your particular Sellsy subscription includes.

Is Sellsy suitable for a small business?

It may be, particularly where a small business wants CRM, quotations, invoicing, reminders, payments and bank reconciliation in a more connected flow. Suitability still depends on transaction types, accounting integration, staff capacity and exception volume. Smaller firms must be able to receive electronic invoices from 1 September 2026 even though their mandatory issuance generally starts on 1 September 2027. Test the daily work with the employee and accountant who will actually resolve rejected invoices, supplier approvals and customer-data errors.

Does Sellsy pricing include electronic invoicing and the PA service?

Do not assume it does. No price is stated here because publicly indexed figures conflict and the live pricing page was not verified. Request a dated quotation that separately identifies the required plan, invoicing or CRM modules, PA sending and receiving, e-reporting, users, entities, invoice volumes, API access, connectors, onboarding, migration, support, archive and bulk export. Ask how overages and future package changes are handled. Compare the three-year total cost, not merely the introductory subscription or the availability of a 15-day trial.

Can Sellsy receive supplier invoices?

Sellsy’s current French electronic-invoicing page says sending and receiving are available, and a PA’s official functions include receiving electronic invoices. Verify the operational scope in your exact package. A live test should show annuaire routing, duplicate detection, attachments, approval roles, missing purchase orders, tax discrepancies, disputes, rejections, credit notes, lifecycle statuses and posting to accounting. Also ask where the original and structured data are archived, how staff search them, and whether records and audit history can be exported in bulk when you change systems.

Does Sellsy handle French e-reporting?

A PA can receive and transmit transaction and payment data, but your contract and source-data design determine whether the required Sellsy e-reporting flow is complete. Ask for separate demonstrations of B2C, export, intra-EU and relevant service-payment records, including corrections, rejection messages and submission evidence. Confirm whether sales created outside Sellsy can be imported, who classifies each transaction, and how duplicates are prevented. Do not confuse invoice transmission statuses with e-reporting of transactions and payments; both need defined fields, controls and owners.

Is a PDF or Factur-X invoice sent by email enough?

A normal PDF by email is insufficient for a mandated structured flow because it lacks the required machine-readable exchange and platform routing. Factur-X combines a readable PDF with embedded structured data, but simply attaching it to an email does not by itself prove compliant routing, mandatory content, directory lookup, lifecycle statuses or reporting. Ask Sellsy to demonstrate creation, validation, PA transmission, recipient delivery and accounting import. This page offers practical buying information, not legal or tax advice; confirm the treatment of unusual transactions with your accountant or adviser.

How should CRM and customer records be cleaned before migration?

Start with legal identity rather than contact names. Deduplicate customers, validate legal names, SIREN and SIRET, TVA/VAT numbers, billing addresses and establishment choices, then identify which system owns each field. Separate invoice recipients from operational contacts and flag B2B, B2C, public-sector, export and intra-EU relationships. Review tax codes, payment terms and bank details under controlled permissions. Test SIRENE enrichment without allowing it to overwrite reviewed data silently. Keep an exception queue for uncertain matches and assign a named approver before invoices are routed through the annuaire.

What must the demo and total-cost comparison prove?

The demo should complete five representative cases: domestic B2B quotation to invoice, problematic supplier receipt, partial credit note, B2C service e-reporting and export or intra-EU treatment. It should expose roles, statuses, audit history, connector behaviour, errors, corrections and exportability rather than only showing a clean happy path. The cost comparison should include modules, PA and e-reporting services, users, entities, volumes, API/connectors, Chorus Pro or Peppol needs, migration, training, support, archive, overages and exit assistance. Record manual steps and unresolved dependencies alongside the financial total.

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 tradeSellsy e-invoicing software checklist for France

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.