On September 1, 2026, every company in France will need to be able to receive electronic invoices. Not only large groups. Not only companies with an ERP. Every company subject to VAT.
For a small business with 5 to 50 employees, the comforting sentence is easy to find: "We have until 2027 to issue e-invoices."
That is true. SMEs and micro-businesses have until September 1, 2027 to issue electronic invoices. But it is a bad reason to wait.
Because from September 2026, your larger suppliers may already send invoices through the new circuit. Because your customer data needs to be clean. Because invoices will no longer move around as plain PDF attachments. And most importantly, because the reform does not only change the invoice format. It touches the full flow: quote, order, invoice, payment, reminder, accounting, reporting.
So the real question for an SME is not: "Which platform should we pick at the last minute?"
The real question is: "Which parts of our invoicing process are still too manual to survive cleanly once invoices become structured data?"
This article is written for that. Not to restate the entire tax doctrine. To translate the French e-invoicing reform into concrete automation work.
What actually changes in 2026
Electronic invoicing does not mean sending a PDF by email.
That is the first misunderstanding to remove. French public sources state it clearly: a scanned paper invoice, a plain PDF or a document sent by email will not match the expected electronic invoicing framework under the reform.
An electronic invoice will need to follow a standardized format. The formats mentioned by the administration include UBL, CII, or a mixed format combining structured data and a readable file, such as Factur-X. It will also need to include mandatory invoice information in structured fields, then move through a state-certified platform, directly or through a compatible solution.
In other words: the invoice becomes a traceable business object. It is no longer only an attachment stored in a folder.
The official calendar is:
| Date | Obligation |
|---|---|
| September 1, 2026 | All companies must be able to receive electronic invoices |
| September 1, 2026 | Large companies and mid-sized companies must issue electronic invoices |
| September 1, 2027 | SMEs and micro-businesses must issue electronic invoices |
The electronic transmission of data to the administration, known as e-reporting, follows the same calendar depending on company size. It will cover transactions that do not go through domestic B2B e-invoicing, for example certain sales to consumers or to customers established outside France.
This matters for SME owners: even if issuing invoices gives you one more year, receiving invoices starts in 2026. And receiving invoices properly already means choosing or validating a toolchain.
Why waiting until 2027 is the wrong move
In many SMEs, invoicing works because people know the habits.
A sales rep turns a quote into an invoice. An assistant checks the address. The owner validates discounts. The accountant collects documents at month-end. Reminders are sent from Pennylane, Sellsy, Axonaut, Sage, EBP, a homegrown CRM, sometimes a spreadsheet. And when something gets stuck, someone calls someone.
As long as the invoice is a PDF, this patchwork can survive. It is not ideal, but it works.
With electronic invoicing, the gaps become more visible. A missing SIREN number. A delivery address that differs from the billing address. A transaction category left blank. A business customer treated as a consumer. An international service invoice handled like a domestic B2B invoice. A payment status that never comes back.
Each small approximation becomes missing, inconsistent or poorly transmitted data.
That is not a reason to panic. It is a reason to prepare the system before the deadline.
The trap in 2026 will be to treat the reform as a software choice. "We will take the platform recommended by our accountant." Fine. But if your customer database is messy, if your quotes do not contain the right information, if your payment statuses are updated by hand, the platform will not fix the process.
A certified platform transports and processes data. It does not guess your organization.
Start by mapping the invoice flow
Before automating, look at the real path of an invoice.
Not the theoretical process written in a procedure. The actual path.
Who creates the quote? Who validates it? Where is customer information stored? When is the SIREN checked? Who decides that a quote can become an invoice? Who sends it? Who tracks payment? Who sends reminders? Who passes documents to the accountant? Who fixes the data when an address is wrong?
In an SME, the answer rarely lives in one tool. It lives across tools and people:
- invoicing software,
- a CRM,
- email,
- accounting software,
- a drive,
- a bank account,
- an internal channel such as Slack, Teams or WhatsApp,
- one or two people who know all the exceptions.
This is exactly where workflow automation becomes useful. Not to replace everyone. To avoid having every invoice move through the company like a small administrative investigation.
The goal is not to create the perfect system. The goal is to reduce fragile manual handling before the reform makes it more expensive.
The 7 automations to prepare now
These are the first areas I would inspect in an SME.
You do not need to build everything at once. But if one of these steps still depends on human memory, copy-paste work or isolated files, it deserves attention before September 2026.
1. Check and enrich customer records
The first automation is not spectacular. It is often the most useful one.
An electronic invoice needs clean customer data. For a business customer, the SIREN becomes central. The billing address must be clear. The delivery address must exist when it differs from the billing address. The VAT number must be present when required. The customer type must be reliable: French business, foreign business, consumer, public sector entity.
If this information is scattered across the CRM, quote software and accounting system, you already have a risk.
A simple automation can:
- detect B2B customers without a SIREN,
- compare addresses between CRM and invoicing software,
- flag records without a VAT number when one should exist,
- spot duplicates,
- create a correction list for the admin team.
This is not AI. It will not look impressive on LinkedIn. But it is the foundation.
An AI agent connected to poor customer data does not create compliance. It creates mistakes faster.
2. Secure the quote-to-invoice handoff
In many companies, the quote is richer than the invoice.
The sales rep adds context, options, delivery constraints, negotiated discounts or installation details. When the invoice is created, some of that information disappears or ends up in an internal note.
Electronic invoicing pushes companies to structure that handoff more carefully.
The useful automation is to transform an approved quote into a draft invoice, with the right fields, line items, VAT rates and mandatory information. A human keeps final approval, but does not start from a blank page.
That is the logic I followed in my article about automating Pennylane invoicing with n8n: the workflow does not merely "create an invoice". It prepares the customer, line items, amounts, delivery, alerts and follow-up.
For an SME, the right compromise is often:
- the signed quote creates a draft invoice,
- mandatory fields are checked,
- the team is alerted when blocking data is missing,
- someone approves before issuance.
Automation prepares. The human commits the company.
3. Check the new mandatory fields
The reform adds information that must be reliable on invoices. Public sources mention four new mandatory fields: the customer's SIREN, the delivery address when it differs from the billing address, the transaction category, and the VAT-on-debits option where applicable.
These fields should not be discovered at issuance time.
The right approach is to check them earlier:
- when creating the customer,
- when qualifying the quote,
- when turning the quote into an invoice,
- when transmitting the invoice to the platform or compatible software.
An automatic check can block or pause an invoice when important information is missing. That is less comfortable than immediate sending, but much healthier than fixing the issue after the fact.
For SMEs, the real benefit is not only compliance. It is fewer back-and-forth messages between sales, admin and accounting.
4. Track invoice statuses instead of tracking emails
Today, invoice tracking is still often done the old way: "Did you send the invoice?", "Did the customer receive it?", "Is it paid?", "Can you send a reminder?"
Electronic invoicing introduces a more structured lifecycle. Depending on the tools and available statuses, an invoice may be submitted, transmitted, received, rejected, set for payment, paid or reconciled.
The automation work is to bring these statuses back to the right place.
Not necessarily into ten tools. Into one place the team can read:
- a note in the CRM,
- an alert in Slack or Teams,
- a task for the admin assistant,
- an update in the tracking table,
- a notification to the owner only when the amount or delay crosses a threshold.
The goal is not to notify everyone about everything. The goal is that every invoice has a clear state, without asking someone to search through three interfaces.
5. Automate reminders without damaging the relationship
Payment reminders are a good example of automation done badly.
Automatically sending a cold email to every customer at D+7 may save time. It can also damage a commercial relationship if the customer is waiting for an invoice correction, if a credit note is in progress, or if the owner gave a verbal agreement.
The best system is not always full automatic reminders. It is often prepared reminders.
The workflow can:
- detect overdue invoices,
- exclude commercially sensitive customers,
- check whether a recent conversation exists,
- prepare a reminder message,
- ask for approval before sending,
- escalate only meaningful delays.
AI can help adapt the tone of a reminder. But the business rule must remain clear: who follows up, when, with what room for judgment, and when the owner should be notified.
6. Separate French B2B, B2C and international flows
The reform does not treat every flow the same way.
E-invoicing applies to domestic transactions between VAT-taxable businesses established in France. Sales to consumers, or certain transactions with customers established outside France, are more likely to fall under data transmission to the administration, known as e-reporting.
For an SME selling to businesses, consumers and foreign customers, this can become a source of errors.
The useful automation is a simple routing layer:
| Customer type | Treatment to prepare |
|---|---|
| French VAT-taxable business | Electronic invoice through a certified platform |
| Consumer | Invoice or receipt depending on the case, with e-reporting for relevant data |
| Foreign business customer | Usual channel depending on the case, with e-reporting where applicable |
| Public sector entity | Chorus Pro or the applicable public sector process |
This table is not a substitute for your accountant. It shows the operational point: the system must recognize the type of flow before deciding what to do.
If that qualification depends on "Marie knows how we do it", it needs to leave Marie's head before 2026.
7. Connect payment, invoice and accounting
Electronic invoicing does not stop when the invoice is sent.
An issued invoice lives until payment, then until accounting reconciliation. In small companies, this path is often manual: the owner checks the bank account, someone marks the invoice as paid, the accountant collects documents later.
A reasonable automation can connect:
- invoicing software,
- the certified platform or compatible solution,
- the bank,
- the CRM,
- the accounting system,
- the document storage folder.
The idea is not to close everything automatically. The idea is to create a clean chain: payment detected, invoice marked as paid, document filed, team notified, exception escalated.
Exceptions matter as much as the simple cases. Partial payment, overpayment, disputed invoice, credit note, grouped payment, customer paying without a reference. This is where naive workflows tend to break.
If you want to see the technical foundation I use for this kind of workflow, I wrote a detailed guide to my self-hosted stack with Hetzner, Coolify and n8n. It is not mandatory for every SME, but it is a strong base when you want to keep control of your automations.
Where AI fits
AI is not required to succeed with e-invoicing.
Many tasks are classic automation: field checks, tool synchronization, alerts, webhooks, APIs, reconciliation, routing.
AI becomes useful when information arrives unstructured.
For example:
- a sales rep describes a service in natural language,
- a customer emails a change request,
- a supplier invoice arrives with an anomaly to explain,
- an internal note needs to become a draft invoice,
- a reminder needs to match the commercial context.
In those cases, an AI agent can extract, summarize, classify or prepare an action. But it needs a clear frame: source data, business rules, human approval, logs and error handling.
Otherwise, you replace manual copy-paste with an opaque decision. That is not progress.
The right use of AI here is less "ChatGPT does my invoicing" and more "an assistant prepares the work, checks what is missing, and asks for approval before committing the company."
It is the same logic as in the field story about an AI agent that creates quotes from Telegram: AI is useful because it sits inside a business flow with rules, connected tools and human approval. Not because it replies nicely in a chat window.
What to do in the next 90 days
If you run an SME and have not started preparing the reform, I would not begin with a large project.
I would start with a short, concrete audit.
Week one: list every tool that touches invoices. CRM, quotes, invoicing, accounting, bank, drive, email, forms, e-commerce, point of sale, support tool.
Week two: pick 20 recent invoices and reconstruct their path. Where did the customer come from? Where is the quote? Who approved it? Which information was copied? Where is payment proof? How many times did the data move between people?
Week three: check customer data. SIREN, VAT numbers, addresses, emails, customer types, duplicates, inactive accounts, public sector clients, foreign clients.
Week four: choose one workflow to make reliable. Not the most impressive one. The most frequent and fragile one.
Only then should you choose tools.
An SME does not need a giant IT project to get ready. It needs a clear chain, clean data, and a few well-placed automations.
What I would do for a 5 to 50 person company
If I were helping a company on this topic, I would split the work into three levels.
Level 1: clean-up. Map the invoice flow, audit customer data, list missing fields, identify risks by customer type.
Level 2: safety automations. Pre-invoice checks, draft invoice creation, alerts on blocking data, CRM and invoicing sync, status tracking.
Level 3: advanced automations. Prepared reminders, bank reconciliation, e-reporting by flow type, AI agents for unstructured requests, owner dashboards.
The most important part is not to start with level 3.
Advanced automation on a messy process only accelerates the mess. The 2026 reform is a good occasion to do the opposite: create just enough order so the tools can work properly.
Official sources used
The regulatory points in this article are based on the following public sources, consulted on May 12, 2026:
- impots.gouv.fr, Je passe à la facturation électronique
- impots.gouv.fr, Je découvre la facturation électronique
- impots.gouv.fr, À partir de quand suis-je concerné par la réforme ?
- impots.gouv.fr, Liste des plateformes agréées
- economie.gouv.fr, Tout savoir sur la facturation électronique pour les entreprises
- economie.gouv.fr, Mentions obligatoires d'une facture
- AIFE, Facturation électronique interentreprises
Conclusion
France's 2026 e-invoicing reform is not only a compliance constraint. It is a revealer.
It will show which companies have a clear invoicing chain, and which still depend on emails, PDFs, human memory and late corrections.
For an SME, the right response is not to automate everything. It is to choose the right control points: customer data, quote-to-invoice handoff, mandatory fields, statuses, payment, reminders, e-reporting.
The rest becomes easier.
If you want to prepare this without turning your company into an ERP project, I can help you map your invoicing flow and identify the automations that actually matter. This is exactly the kind of work I cover on the Automation & Workflows page, using your existing tools and real constraints.
Also available: Read in French