France software assessment

Qonto e-invoicing in France: approval, scope and buyer checklist

Assess Qonto for French e-invoicing: official PA status, free-offer limits, formats, e-reporting, accountant access, costs and a practical demo.

Quick verdict:
  • Best fit when invoice operations and financial workflows benefit from one connected workspace.
  • Require a successful exception test before trusting the no-cost plan for production.
  • Treat complete structured-data export as a go/no-go condition, not a future migration detail.
Last checked: 21 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 your invoice flows, not the brand name

A useful Qonto assessment begins with what your business actually sends and receives. Map domestic B2B sales, leveranciersfacturen, B2C receipts, exports, intra-EU transactions, credit notes, deposits, payment collection and any betalingsgegevens voor diensten. Record the legal entity, SIREN/SIRET, VAT status, monthly peaks, currencies, approval steps and systems involved. Then separate mandatory structured e-invoicing flows from transactions that may instead feed e-reporting. This prevents a common buying mistake: selecting a polished invoice editor while leaving gaps in receiving, exception handling or reporting. Qonto may be attractive if you want invoicing, expenses, banking and reconciliation close together, but suitability depends on your accounting stack and controls. Ask who corrects rejected invoices, who monitors levenscyclusstatussen, how duplicates are prevented, and whether every entity and user can work within the quoted plan. The right decision is the one that closes your complete operational loop, not merely the one with the simplest starting price.

Guide

The official French timetable and what it means

Service-Public confirms a two-stage timetable. From 1 September 2026, every business within scope must be able to receive electronic invoices; large companies and ETIs must also issue electronic invoices and perform e-reporting from that date. SMEs and micro-enterprises must begin issuing and e-reporting from 1 September 2027, although their receiving obligation starts a year earlier. Treat those dates as operating deadlines, not software-purchase dates. Supplier identity matching, routing, user permissions, accounting mappings, rejection handling and staff training all need testing beforehand. An SME waiting until 2027 to prepare may still fail to receive leveranciersfacturen correctly in 2026. Confirm your size category and transaction scope with qualified advisers where necessary, then work backwards from the applicable date. Allow time for a pilot across more than one customer and supplier, including a correction or credit-note scenario. The official timetable establishes obligations; it does not certify that any particular subscription or configuration covers every workflow your organisation needs.

Guide

Qonto’s PA status and the exact offer claims to verify

The DGFiP official list page, updated 17 July 2026, links to the operators satisfying all registration conditions, including interoperability tests; QONTO appears in that downloadable list. 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. Separately, Qonto’s current French product page describes Qonto as a fully operational PA and says compliant e-invoicing is included without limit in all Qonto offers. It also advertises Qonto Facturation at €0/month, with unlimited quotes and invoices, customer and leveranciersfactuur and expense centralisation, customer reminders, and external-bank synchronisation. These are vendor claims checked on 21 July 2026, not permanent regulatory guarantees. Re-check eligible legal entities, user and volume limits, support, PA activation, e-reporting scope, accountant access, integrations, export capabilities and exit terms before signing. Do not assume the free tier contains every advanced approval, automation or multi-entity workflow.

Guide

Structured formats, receiving and invoice lifecycle

French reform is about structured data, not simply replacing paper with a PDF attachment. Your test should cover Factur-X, UBL and CII, with data aligned to EN 16931 and readable by every system in the chain. Factur-X combines a human-readable PDF with embedded structured XML, but a normal PDF emailed to a customer is insufficient. Ask Qonto to show how it creates or ingests each format relevant to you, validates required identifiers and VAT fields, routes the invoice through the PA network, and records levenscyclusstatussen such as submitted, rejected, received or paid where applicable. Receiving deserves equal attention: demonstrate supplier matching by SIREN/SIRET, duplicate detection, attachments, approval routing, coding, credit-note linkage and accounting export. Deliberately use one malformed invoice and one disputed invoice to expose exception handling. Confirm where the legal record and controlespoor are kept, how long documents remain accessible, and how original structured files can be exported. A clean screen is useful; retrievable evidence and controlled corrections are essential.

Guide

E-reporting is a separate capability to prove

Do not treat e-reporting as an automatic by-product of sending B2B electronic invoices. Depending on your activities, reporting can involve B2C transactions, exports, intra-EU business and payment information for certain services. Build a transaction matrix showing which flows use structured e-invoicing, which require e-reporting, which data source supplies the values, and who resolves errors. Qonto’s PA status means the platform category can receive and transmit relevant transaction and payment data, while Qonto’s live commercial and implementation scope still needs confirmation for your account, offer and launch date. Ask for a demonstration using realistic B2C, export and service-payment cases, including corrections after a refund or late payment. Verify frequency, cut-off controls, VAT coding, status visibility and proof of successful transmission. If data originates in a checkout, CRM, ERP or external bank, test the actual API or integration rather than a slide presentation. Obtain written clarity on unsupported flows and the manual fallback, because unnoticed reporting gaps can persist even when customer invoices appear to process correctly.

Guide

Accountant and team roles must preserve control

A workable setup gives sales, finance, approvers and the accountant enough access without sharing credentials or weakening segregation of duties. Qonto advertises a professional account from €9/month excluding VAT, more than 2,000 integrations and speciale toegang voor de boekhouder; it also says the professional account has a one-month trial. Verify current pricing and the exact plan needed for each feature. During the trial or pilot, create representative roles: an employee who uploads an expense, a sales user who drafts an invoice, an approver, a finance administrator and an external accountant. Check who can change bank details, VAT treatment, customer identifiers, invoice numbering, payment status and exports. Confirm whether the accountant can retrieve original Factur-X, UBL or CII files, supporting documents, lifecycle history and reconciliation information without becoming an unrestricted administrator. Multi-entity groups should test entity switching and access boundaries explicitly. Ask how departed users are removed, actions are logged and emergency access is handled. Good collaboration should shorten month-end close while leaving a clear, reviewable controlespoor.

Guide

Run a five-case live demo before deciding

Insist on five van begin tot eind cases using a sandbox or controlled pilot and your own chart-of-accounts logic. Case 1: issue a domestic B2B invoice with valid SIREN/SIRET and VAT data, then follow its levenscyclusstatus. Case 2: receive a supplier Factur-X invoice, detect a duplicate, approve it and export it to accounting. Case 3: reject or correct an invoice, issue a linked credit note and retain the controlespoor. Case 4: process a B2C sale, an export or intra-EU transaction, plus betalingsgegevens voor diensten where relevant, and show the resulting e-reporting evidence. Case 5: reconcile payment through Qonto or an externally synchronised bank, give the accountant access, then export all records as if leaving the service. Score each case for automation, accuracy, exception visibility, permissions and manual effort. Do not accept a pre-recorded happy path. The demonstration should reveal who owns failures, whether integrations are genuinely live, and whether your team can recover without vendor intervention.

Guide

Compare total cost, operational risk and exit options

A €0/month headline can be valuable, but it is not a total-cost model. Qonto says registration for its free Qonto Facturation offer requires no bank card and advertises unlimited quotes and invoices; verify those terms at purchase and identify what triggers a paid account or add-on. Price the legal entities, active users, accountant seats, approval workflows, integrations, API usage, support level, migration, training, archive, reconciliation and exception handling over three years. Add internal time for manual e-reporting or exports if those functions are incomplete. Assess concentration risk if banking, invoices and evidence sit with one provider, along with downtime procedures and integration lock-in. Qonto says a business may later switch PA and that portability is handled between the new PA and Qonto. Still, request the live procedure, timing, responsibilities, archive access, complete data export and contractual exit conditions. Choose on proven coverage and controllability, not list price alone; a free plan that creates manual gaps can cost more than a paid plan that removes them.

Guide

Your next action: build a Qonto evidence pack

Create a one-page requirements matrix before opening an account or changing PA. List every French entity, invoice flow, structured format, source system, user role, accounting destination and reporting obligation. Attach a sample for each of the five demo cases, removing personal data where appropriate. Ask Qonto to mark each requirement as available now, configuration-dependent, integration-dependent, roadmap or unsupported, and request links to current contractual terms. Save evidence of Qonto’s DGFiP listing separately from vendor pricing and feature claims so regulatory status is not confused with commercial scope. Then run the live demo, record results, calculate three-year total cost and document remaining manual controls. Give unresolved tax-scope questions to your accountant or tax adviser and security questions to the responsible technical reviewer. If Qonto passes the essential cases, pilot one entity before a wider rollout. If it fails a mandatory receiving or e-reporting case, compare another PA rather than relying on an assumed future feature.

Checklist

Map domestic B2B, B2C, export, intra-EU, credit-note and service-payment flows for every French legal entity.

Confirm QONTO remains on the current DGFiP list and save dated evidence separately from Qonto’s commercial claims.

Test sending and receiving Factur-X, UBL or CII files, including validation, rejection, correction and levenscyclusstatussen.

Demonstrate supplier matching, duplicate detection, approvals, accounting export and uzgadnianie bankowe with real sample data.

Prove e-reporting for relevant B2C, export, intra-EU and service-payment cases, including a refund or correction.

Verify plan-specific limits for entities, users, volumes, support, accountant access, integrations, API use and PA activation.

Calculate three-year total cost, including migration, training, add-ons, manual work, support and exception handling.

Obtain written archive, structured-data export, portability, switching-time and contractual exit terms before rollout.

FAQ

Is Qonto officially an approved platform in France?

Yes, based on the official material checked on 21 July 2026. The DGFiP list page was updated on 17 July 2026, and QONTO appears in its downloadable list of operators satisfying all conditions, including interoperability tests. The current term is Plateforme Agréée, or PA; PDP is the former term. Approval covers regulatory, security and interoperability conditions for the operator. It does not mean every Qonto plan, integration or customer configuration automatically meets every business need. Re-check the live DGFiP list before contracting or going live, then separately validate the commercial offer and your required invoice and e-reporting workflows.

Is the free Qonto invoicing offer enough for compliance?

Possibly for a straightforward business, but the headline alone cannot answer that. Qonto currently advertises Qonto Facturation at €0/month with unlimited quotes and invoices, centralisation of customer and leveranciersfacturen and expenses, reminders, and external-bank synchronisation. It also says registration needs no bank card. Verify that the offer covers your entities, users, receiving activation, structured formats, e-reporting cases, approvals, accountant workflow, integrations, support and exports. Advanced controls may require a paid account or may not fit the free workflow. Test your five hardest cases and price any manual work before deciding that free means sufficient.

Do I need a Qonto business account to use its invoicing tools?

Qonto advertises a standalone Qonto Facturation offer at €0/month, so its public offer suggests that a paid Qonto business account is not always required to start invoicing. Its professional account is separately advertised from €9/month excluding VAT, with a one-month trial, more than 2,000 integrations and speciale toegang voor de boekhouder. The practical question is which functions depend on the paid account: banking, reconciliation depth, permissions, accountant access, integrations or support may differ. Ask Qonto to confirm the current eligibility, included PA services, entity and user limits, and upgrade triggers in writing for your exact legal form and workflow.

Can Qonto receive supplier electronic invoices?

A PA is authorised to emit, transmit and receive electronic invoices, and Qonto presents itself as a fully operational PA. For your implementation, go beyond a yes-or-no answer. Ask Qonto to receive a supplier Factur-X, UBL or CII invoice addressed to your SIREN/SIRET, display its structured data and levenscyclusstatus, identify a duplicate, route approval, link a credit note and export the original record to accounting. Also test an invalid identifier and a disputed invoice. Confirm activation steps, supported formats, archive access and who handles routing failures. Receiving becomes mandatory for all businesses in scope from 1 September 2026, including SMEs whose issuing deadline is later.

Does Qonto handle French e-reporting as well as e-invoicing?

Its status as a PA is relevant because a PA can receive and transmit transaction and payment data, and Qonto’s product claims compliant e-invoicing. Nevertheless, your exact e-reporting coverage is a changeable vendor and configuration question. Request live proof for the flows that apply to you, such as B2C sales, exports, intra-EU transactions and payment data for services. Check source integrations, VAT mappings, reporting frequency, corrections, transmission evidence and error ownership. Get written confirmation of what is included in your selected offer and what remains manual. This page provides practical information, not legal or tax advice; confirm uncertain scope with your accountant or qualified adviser.

Is sending a Factur-X PDF by email enough?

No. Factur-X is useful because it combines a readable PDF with embedded structured XML, but French electronic invoicing is not satisfied by treating the file as an ordinary email attachment. The structured data must move through the required e-invoicing framework using an approved platform, with validation and lifecycle handling. A plain PDF without the structured component is also insufficient. Test that Qonto creates or preserves valid Factur-X data, routes it through its PA service, records statuses and retains the original structured record. If you use UBL or CII elsewhere, verify conversion or native support without losing mandatory EN 16931 fields or audit evidence.

Can my accountant work directly in Qonto?

Qonto advertises speciale toegang voor de boekhouder with its professional account, but confirm the exact plan and permissions rather than assuming universal access. Your accountant should be able to review leveranciersfacturen, structured originals, supporting documents, VAT coding, reconciliation data, lifecycle history and exports needed for close and audit. They should not need shared credentials or excessive administrative rights. During a trial, test invitation, entity restrictions, read and approval permissions, export formats, action logs and removal of access. Ask whether standalone Qonto Facturation provides the same accountant workflow as a paid professional account, and include any extra seat, integration or support costs in your comparison.

What should the demo and total-cost comparison prove?

The demo should prove complete outcomes, not attractive screens. Run domestic B2B issuance, supplier receipt and approval, rejection plus credit note, e-reporting for a relevant non-B2B flow, and payment reconciliation followed by accountant access and full export. Include malformed data and a duplicate so exception controls are visible. Score accuracy, manual steps, permissions, recovery and audit evidence. Compare three-year costs for entities, users, paid plans, integrations, API use, migration, training, support, archive and internal labour. Finally, simulate leaving: request structured invoices, attachments, statuses and logs, and confirm PA switching timing, responsibilities and continued archive access.

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 tradeQonto e-invoicing France

France — Country hub

Continue reading

Official sources

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