You run a French company from London, New York, Dubai or Singapore. Your accountant in Paris writes that from 1 September 2026 every French business must be able to receive electronic invoices, and that the duty to issue them follows in two waves. You wonder whether a small SAS (société par actions simplifiée, the flexible French joint-stock company) owned from abroad is really concerned, which platform to use when you have no office in France, what happens to your business-to-consumer sales and your export invoices, and what a penalty notice received by post in Paris means when you live 6,000 kilometres away. This guide answers those questions for the foreign founder. It explains the French reform in plain English, gives the exact calendar published by the French tax administration, describes the authorised technical route, quantifies the fines with the statutory texts, and sets out a practical compliance and challenge roadmap that can be operated entirely from abroad. Every acronym is explained on first use, and every decisive legal statement is anchored to an official source you can open yourself.
I. What France now requires from your French company
A. Which companies, which transactions, and which dates trigger the duty
The starting point is simple and it surprises many foreign owners: the reception duty is general. The French tax administration states that from 1 September 2026, every business whatever its size must receive its invoices in electronic form whenever its supplier is itself required to issue in that format. Your French SAS, SARL (société à responsabilité limitée, the French limited liability company) or branch is therefore concerned even if it has one employee, even if its shareholder lives abroad, and even if its bookkeeping is done by an external firm. If you have not yet chosen between these vehicles, our companion guide on choosing between a SAS, a SARL, a branch or a subsidiary in France explains the consequences of each structure for liability, social security and taxation, and it remains the hub for this doing-business-in-France series.
The issuance duty arrives in two waves based on company size, measured under the French LME (loi de modernisation de l’économie, the 2008 business modernisation act) categories of headcount, turnover and balance sheet. From 1 September 2026, large companies and intermediate-sized companies (ETI, entreprises de taille intermédiaire) must issue their invoices electronically and transmit transaction and payment data to the administration. From 1 September 2027, issuance becomes compulsory for small and medium-sized businesses and for micro-businesses. In practice, most foreign-founded French companies are SMEs, so their issuance deadline is 1 September 2027, but their reception readiness deadline is 1 September 2026. That asymmetry matters: from September 2026 your company must already be reachable on an electronic invoicing channel, because your large suppliers will send structured invoices that a simple PDF inbox may not process correctly.
The substantive scope covers domestic business-to-business transactions subject to French VAT (TVA, taxe sur la valeur ajoutée). The Tax Code provides that “Tout assujetti est tenu de s’assurer qu’une facture est émise, par lui-même, ou en son nom et pour son compte, par son client ou par un tiers”, which means every taxable person must ensure an invoice is issued, by itself or in its name by the customer or a third party. It adds that “La facture est, en principe, émise dès la réalisation de la livraison ou de la prestation de services.” Commercial law mirrors this: “Tout achat de produits ou toute prestation de service pour une activité professionnelle fait l’objet d’une facturation.” and “L’acheteur est tenu de la réclamer.” Your company therefore sits on both sides of the duty: it must issue compliant invoices to its French business customers and demand compliant invoices from its French suppliers.
Three boundary cases deserve attention because foreign founders often misunderstand them. First, VAT registration and invoicing are linked to VAT liability, not to the nationality of the owner. A company registered in France with a SIREN number (the nine-digit business identifier issued by INSEE, the French statistics institute) and a Kbis extract (the official certificate of registration delivered by the greffe, the registry of the commercial court) is a French taxable person for its French operations. The rule that “La taxe sur la valeur ajoutée doit être acquittée par les personnes qui réalisent les opérations imposables” applies to it in the same way as to a company owned by French residents. Second, declarative duties start early: “Toute personne assujettie à la taxe sur la valeur ajoutée doit” file an identification declaration within fifteen days of starting operations, provide information on its activity, and keep numbered books recording each transaction day by day. An e-invoicing platform does not replace that registration; it builds on it. Third, transactions with private consumers and most cross-border transactions do not travel as e-invoices but fall under e-reporting (e-reporting, the periodic electronic transmission of transaction and payment data to the administration). A restaurant in Paris selling to tourists, a SaaS company billing American customers, or a French subsidiary re-invoicing its foreign parent will transmit structured data rather than a full domestic e-invoice for those flows. The practical consequence is that even a company with no domestic B2B sales still needs an e-reporting channel from the applicable date.
The calendar also interacts with the broader legal life of the company. Company law requires that “Toute personne physique ou morale ayant la qualité de commerçant doit procéder à l’enregistrement comptable des mouvements affectant le patrimoine de son entreprise.” and that “Elle doit établir des comptes annuels à la clôture de l’exercice au vu des enregistrements comptables et de l’inventaire.” Management must, “A la clôture de chaque exercice le conseil d’administration, le directoire ou les gérants dressent l’inventaire, les comptes annuels conformément aux dispositions de la section 2 du chapitre III du titre II du livre Ier et établissent un rapport de gestion écrit.” Clean structured invoicing feeds that accounting chain directly: each e-invoice carries coded data that the accounting software can ingest without retyping, which reduces year-end adjustments and supports the annual approval and filing with the greffe and publication cues in the BODACC (Bulletin officiel des annonces civiles et commerciales, the official gazette for company notices). A company that keeps paper habits while its counterparties switch to structured formats will feel the friction at closing time.
B. How a compliant invoice travels from your supplier to your books
France has chosen a platform model, not a simple email model. A compliant invoice is a structured dataset, not a scanned image. Three formats are accepted: Factur-X (a hybrid PDF with embedded structured data), UBL (Universal Business Language) and CII (Cross Industry Invoice). A PDF alone, without the structured layer, does not satisfy the reform for covered transactions. The invoice must contain the mandatory particulars fixed by decree: identity of the parties including SIREN and VAT numbers, invoice number and dates, precise description and quantity of goods or services, unit prices excluding VAT, applicable VAT rates and amounts, and payment terms. Those particulars overlap with commercial law, which requires the invoice to show the names and addresses of the parties, the date of sale or service, quantity, precise description, unit price excluding VAT, agreed price reductions, payment date, discount terms for early payment, the rate of late penalties and the fixed recovery fee. Keep every issued and received invoice and its doubles: the Tax Code requires the taxable person to retain a copy of all invoices issued, and commercial retention runs for years.
To circulate, the invoice passes through registered actors. The PPF (Portail public de facturation, the public invoicing portal operated by the administration) provides a directory and a backbone. A PA (plateforme agréée, a private platform registered with the administration for a renewable period) issues, transmits, receives and forwards e-invoices and sends the required data to the administration. An OD (opérateur de dématérialisation, a dematerialisation operator that is not registered) can prepare or receive invoices on behalf of a company but must connect through a PA or the public portal for the regulated exchange. For a founder living abroad, the concrete question is therefore which PA to appoint, not whether to buy a scanner. The PA holds your company directory entry keyed to its SIREN, routes incoming invoices to the right approval inbox, converts your sales data into the required format, and files the e-reporting for your consumer and export flows. Mandates matter here: invoices may be physically issued by the customer under self-billing or by a third party where the taxable person grants a mandate, and each invoice issued under mandate is then issued in the name and on behalf of the taxable person subject to its acceptance. Record that mandate in writing, define who validates before sending, and keep proof of acceptance, because a dispute about who authorised an invoice often decides a payment dispute later.
Reception readiness is the first milestone and it is operational, not theoretical. Concretely, by 1 September 2026 your company must have a declared electronic address on the directory, a PA or portal connection able to receive the three formats, an internal rule that no supplier invoice is paid unless it arrived through the channel, and an archive that stores the structured file plus its visual representation. Many foreign-owned companies fail this step because the Paris accountant receives PDFs by email while the PA inbox fills with structured invoices nobody opens. Align the two: instruct every French supplier to send to the PA address, disable payment of off-channel PDFs for covered transactions, and give your accountant access to the PA. For issuance, map your customer base now. Domestic B2B customers need full e-invoices through the channel. French private consumers, foreign customers and certain exempt operations need e-reporting of aggregated transaction and payment data. Your billing software must tag each flow correctly, because sending a full e-invoice where only e-reporting is due, or omitting e-reporting where it is due, creates the gaps the administration detects automatically.
Payment terms ride on top of invoicing and foreign founders underestimate their rigidity. Unless otherwise agreed, the balance is due thirty days after receipt of goods or performance of the service, since “le délai de règlement des sommes dues ne peut dépasser trente jours après la date de réception des marchandises ou d’exécution de la prestation demandée.” The agreed period may not exceed sixty days from the invoice date, with a possible forty-five days end-of-month arrangement where expressly stipulated and not abusive toward the creditor. Your general terms of sale (CGV, conditions générales de vente) must state the late-penalty rate applicable from the day after the due date and the fixed recovery fee. Structured invoicing makes these dates machine-readable, so late-payment interest and the recovery fee compute automatically. Update your templates before the switch: an e-invoice with missing payment-date or penalty mentions exposes you to a commercial fine as well as to customer pushback, and correcting hundreds of structured invoices after the fact costs more than fixing one template today.
II. What missed deadlines and wrong formats cost, and how to act from abroad
A. How much non-compliance costs, in fines and in business damage
The headline tax fine is calibrated per invoice. The Tax Code provides that “Le non-respect par l’assujetti de l’obligation d’émission d’une facture sous une forme électronique dans les conditions prévues à l’article 289 bis donne lieu à l’application d’une amende de 50 € par facture, sans que le total des amendes appliquées au titre d’une même année civile puisse être supérieur à 15 000 €.” Fifty euros per invoice with a 15,000 euro annual cap may look modest until it is multiplied across monthly recurring billing. A services company issuing two hundred domestic B2B invoices per month reaches the annual cap in less than two months of systematic breach. Platforms face their own scale: failures by a registered platform to transmit data expose the platform to 50 euros per invoice with a 45,000 euro annual cap. Where the administration finds that a taxable person persistently ignores the duty to use a registered platform for reception, it issues a formal demand to comply within three months, and continued breach opens further consequences. The message is graduated: fix reception now, fix issuance by your wave date, and do not assume that staying on PDF is a neutral option.
Tax fines are only the first layer. Commercial sanctions for defective invoices are heavier. The Code states that “Tout manquement au I est passible d’une amende administrative dont le montant ne peut excéder 75 000 € pour une personne physique et 375 000 € pour une personne morale.” with double maxima on repeat breach within two years of the first final sanction decision. The DGCCRF (Direction générale de la concurrence, de la consommation et de la répression des fraudes, the authority policing commercial invoicing and payment terms) enforces these amounts during inspections, and its agents read structured data faster than paper. Missing mandatory particulars, omitted penalty rates, absent recovery fee, or missing order-number references each count as defects. A company that migrates to structured format but ports a defective template multiplies the same defect across every invoice, which is why template review by counsel before mass issuance is cheaper than serial correction afterwards.
Parallel VAT risks compound the exposure. VAT is due from the persons carrying out taxable transactions, since “La taxe sur la valeur ajoutée doit être acquittée par les personnes qui réalisent les opérations imposables”, and the customer deducts input VAT only on valid supporting invoices. A missing, non-compliant or off-channel invoice gives the administration a clean reason to reject deduction, reassess, and add late interest. The general invoice-defect fine of 15 euros per omission or inaccuracy, capped at one quarter of the invoice amount, and the heavier 50 percent penalty for concealed identity, fictitious invoices or unrecorded transactions sit behind the e-invoicing fine as additional layers where the underlying invoice itself is wrong. In plain terms, a company that issues outside the channel risks paying a specific e-invoicing fine and still facing the classic invoice-defect and VAT-reassessment machinery on the same documents.
Business damage often exceeds the fines. Large French customers increasingly condition payment on receipt through the channel: no structured invoice, no payment run. A foreign-owned supplier that cannot deliver through a PA is pushed to the back of the queue, and its sixty-day payment clock never starts because the compliant invoice was never received. Disputes follow about when the period started, which version of the invoice counts, and whether penalties for late payment accrue. Labour and banking frictions add up too. URSSAF (the social-security collection network) audits, bank onboarding reviews and investor due diligence all ask for coherent sales ledgers; gaps between declared turnover, VAT returns and e-reporting data invite questions that a founder living abroad answers slowly. The reform therefore functions as a coherence test: the administration will compare what you declared, what your customers reported receiving from you, and what your platforms transmitted.
B. How to comply and how to challenge a penalty from abroad
Start with a four-week compliance sprint that can be run remotely. Week one, confirm your size category and your wave date with your accountant: LME thresholds on headcount, turnover and balance sheet decide whether your issuance duty starts in 2026 or 2027, while reception readiness is 1 September 2026 in all cases. Week two, appoint a PA and register your directory entry. Compare at least two registered platforms on English-language support, multi-entity handling for the foreign parent, connection to your billing tool, OD compatibility if you keep a preparatory operator, archiving with probative value, and e-reporting coverage for consumer and export flows. Sign a written mandate that states who may issue in your name, who validates, and how acceptance is recorded. Week three, fix templates and flows: mandatory particulars, SIREN and VAT numbers, Factur-X or UBL output, payment dates, penalty rates, recovery fee, order-number handling, self-billing clauses where used, and separate tagging of domestic B2B, consumer, intra-EU and export flows. Week four, run parallel: issue each domestic B2B invoice both through the channel and, during transition, as agreed with the customer, reconcile PA dashboards against accounting, and train the person who approves payments to reject off-channel invoices for covered transactions. Document each step, because proof of organised compliance supports later requests for leniency.
Governance from abroad needs explicit design. Designate one person in France, often the accountant or office manager, as channel administrator with authority to update the directory, manage user rights and download archives. Keep ultimate validation with the director: no mass issuance without release, no change of bank details on templates without dual control, and no supplier bank-detail change without callback on a known number. Store mandates, platform contracts, format choices and archiving certificates where the director can produce them within days. Update commercial documents consistently: CGV, order forms, self-billing agreements and intercompany service agreements with the foreign parent should all name the PA route, the accepted formats and the e-reporting responsibilities. Where the parent recharges management fees or shared costs to the French company, align the transfer-pricing file, the VAT treatment and the invoicing channel, since the administration reads those three together.
If a penalty or reassessment arrives, act within the deadlines rather than from memory of foreign procedures. French tax claims follow a written contentious path: “Les réclamations relatives aux impôts, contributions, droits, taxes, redevances, soultes et pénalités de toute nature, établis ou recouvrés par les agents de l’administration, relèvent de la juridiction contentieuse lorsqu’elles tendent à obtenir soit la réparation d’erreurs commises dans l’assiette ou le calcul des impositions, soit le bénéfice d’un droit résultant d’une disposition législative ou réglementaire.” In practice, file a formal claim (réclamation contentieuse) with the competent tax office, through the professional online account where possible, stating the tax, the year, the amount, the grounds and attaching the structured invoices, platform transmission logs, mandates and accounting extracts that prove compliance or explain the gap. Keep the registered letter or online filing receipt: time limits run strictly. If the administration rejects expressly or implicitly, appeal to the administrative court (tribunal administratif) within the stated period. Commercial fines from DGCCRF follow their own administrative challenge route with hierarchical appeal and then judicial review; do not mix the two tracks in one letter.
Three defences recur in e-invoicing disputes and each needs documents, not assertions. First, size and timing: prove your LME category with headcount records, filed accounts and tax returns to show that your issuance wave had not yet started, while demonstrating reception readiness from September 2026. Second, platform fault versus company fault: where a PA failed to transmit, produce the platform contract, incident tickets, transmission reports and the corrective re-send, and redirect liability discussion toward the platform where the facts support it. Third, good-faith correction: where an invoice was defective, show prompt corrective invoices referencing the original specifically and unequivocally, re-transmission through the channel, and accounting correction before any audit notice. Across all three, anchor every factual claim to a file: directory extract, structured invoice, transmission log, mandate, CGV version, bank proof of payment date. A founder living abroad who can produce that bundle by secure link within days stands differently from one who promises compliance orally.
Conclusion
France is not asking your company to buy new stationery. It is moving business-to-business invoicing into structured data exchanged through registered platforms, with reception compulsory for every business from 1 September 2026 and issuance following for large and intermediate companies in 2026 and for SMEs and micro-businesses in 2027, plus e-reporting for consumer and cross-border flows. The Tax Code keeps the classic duties, that “Tout assujetti est tenu de s’assurer qu’une facture est émise, par lui-même, ou en son nom et pour son compte, par son client ou par un tiers” and that “Tout achat de produits ou toute prestation de service pour une activité professionnelle fait l’objet d’une facturation.” The reform adds a channel fine of 50 euros per invoice capped at 15,000 euros per year, layered on commercial fines up to 375,000 euros for a legal entity and on VAT reassessment where deduction lacks valid support. The remedy is operational: confirm your wave date, appoint a registered platform, fix templates and flow tagging, run reception readiness by September 2026, and keep mandates and logs that prove compliance. With that backbone in place, a penalty notice becomes a file to answer with documents and deadlines, including the contentious claim path for taxes and penalties, rather than a crisis managed from an airport lounge.