● Business offer — E-invoicing compliance

E-invoicing: receiving is in force, issuing is what you prepare now

Since 1 September 2026, every company, whatever its size, must receive its invoices in electronic form as soon as its supplier is required to issue them that way; the obligation to issue follows company size — 1 September 2026 for large and mid-sized companies, 1 September 2027 for small, medium and micro-enterprises. Your AI agent prepares that work: recipient directory, format and mandatory-mention checks before every issue, statuses reconciled, e-reporting prepared. The regulated transmission itself is carried out by the approved platform you select: Blue Lemon Agent is not an approved platform and replaces neither that platform nor Chorus Pro. Hosted in France, through local inference or an isolated resource. The configuration itself is signed off with your chartered accountant.

Free audit (15 min) → See the prices

Hosted in France Invoicing data protected GDPR & AI Act: governed deployment Human oversight

Updated on 07/09/2026

Deployed in a few weeks

E-invoicing compliance assistant · hosted in France

Where do we stand on the e-invoicing project?

Receiving: ready. The connection to your approved platform is tested, 12 structured invoices received and integrated with no re-keying.
Issuing: 412 customers on file, 361 resolved in the directory (registration number and billing address verified). 51 still to settle — the same trading name across several establishments, or a closed registration number.
The 51 are sorted by revenue: the first 9 account for half of what you issue.
⛓ Sourced · customer file, platform directory, public company register

And will our invoices go through without being rejected?

I ran your last 190 invoices through the pre-issue check: 174 would be accepted as they stand, 16 would be rejected — 11 for a missing delivery address where it differs from the customer's address, 5 for a missing customer registration number.
I have prepared the 16 corrections, line by line, plus the rule that prevents them at source.
Bringing that rule into force is signed: your chartered accountant approves it in a single review.
✎ Proposal · 16 corrections ready — the configuration is signed off

Local inference · no data outside the EU

Data hosted in France

Sovereign by designLocal inference or hosting in France

GDPR & AI Act: governed deploymentTraceability & human oversight

TurnkeyDesigned, installed and run for you

The configuration is signed offWith your chartered accountant

✦ In brief

A Blue Lemon Agent e-invoicing compliance agent prepares the connection of your sales software to an approved platform, maintains the recipient directory, checks the structured format and the mandatory mentions before every issue, reconciles the lifecycle statuses and prepares the e-reporting. The official timetable: since 1 September 2026, every company, whatever its size, must receive its invoices in electronic form as soon as its supplier is required to issue them that way; on that same date, large and mid-sized companies must issue their invoices electronically and transmit their transaction and payment data; on 1 September 2027, that obligation extends to small and medium-sized companies and micro-enterprises — source: impots.gouv.fr, page updated on 16 January 2026, consulted on 7 September 2026; entry-into-force dates set by article 91 of French law no. 2023-1322 of 29 December 2023 (finance act for 2024). Blue Lemon Agent is not an approved platform: only an operator registered by the French tax administration is authorised to transmit your invoices and your data. Hosted in France, through local inference or an isolated resource, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity. The configuration is signed off with your chartered accountant.

100%

hosted in France in the target architecture

transfer outside the EU in the target architecture

legal deadlines tracked: 09/2026 and 09/2027

configurations put live without human sign-off

Benchmarks describing our offer, not results measured at a client. The size of the project is confirmed by a review of your customer file and your management software.

The context

Why e-invoicing is the most firmly dated project right now

Most company projects slip. This one carries dates set by law — article 91 of French law no. 2023-1322 of 29 December 2023 (finance act for 2024): since 1 September 2026, a company must receive its invoices in electronic form as soon as its supplier is required to issue them that way. Within the scope of the reform, a scanned paper invoice or an ordinary PDF sent by e-mail does not count as an electronic invoice; outside that scope, the earlier invoicing rules continue to apply.

! The stakes

This is not an IT project, it is a data project. It takes a clean customer file — registration number and billing address verified for every recipient —, sales software able to produce a structured format, a connection to an approved platform, and the ability to read what that platform sends back. Each of those four points is usually discovered at the first rejection, which is to say too late. And handing that data — prices, margins, customers, bank details — to a consumer tool hosted outside Europe would mean solving one regulatory constraint by creating another.

✓ Our answer

The agent takes the four points in the order they fall due. It resolves the directory and names the lines it could not settle rather than guessing; it checks the format and the mentions before issuing, on every invoice, not after the rejection; it reconciles every status returned by the platform with the original invoice; it assembles the e-reporting and checks it before transmission. It runs through local inference or an isolated resource hosted in France. The configuration — formats, mention rules, e-reporting scope — is laid out documented, dated, tested against your history, and signed off with your chartered accountant: that sign-off is what makes it defensible. What it does not do is stated as plainly as what it does: it transmits nothing in place of the approved platform, it decides no VAT rate, regime or exemption, and it reissues no corrected invoice without sign-off.

The decisive point

Your prices, your margins and your customers run through this flow: sovereignty & compliance

An invoice is not a neutral administrative document: it carries your pricing policy, your discounts, the list of your customers and your bank details. Here is how our agents' architecture protects it, invoice after invoice.

Local inference

The agent can run on a machine inside the company: no invoice, no price list leaves the network for a foreign cloud.

Hosting in France

Otherwise, a dedicated, isolated resource hosted in France under French law — your invoicing data: processing and access within the European Union targeted by the architecture.

Reduced extraterritorial exposure

Architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity for your prices and your customers: our architecture depends on a subcontracting chain and remote access documented for the configuration chosen.

An isolated resource per client

No pooling: an environment strictly dedicated to your company and its invoice flow.

Encryption & controlled access

Encryption in transit and at rest, role-based access (RBAC), strong authentication and logging of transmissions and statuses.

AI Act: governed deployment

Strictly a support agent; the configuration is signed off with your chartered accountant; traceability and human oversight end to end.

What depends on the architecture chosen These points are not general guarantees: they are settled deployment by deployment, in the quotation.

The applicable location is that of the architecture set out in the quotation and verified before commissioning.
Local execution is announced only for the configuration explicitly described and accepted in the quotation.
The applicable isolation depends on the deployment mode set out in the quotation; no dedicated isolation is presumed.
The encryption mechanisms in transit and at rest, their components and key management are those documented for the architecture chosen.
Roles and permissions are configured and accepted for the identities and systems actually connected.
The events logged, their content, their retention period and who may access them are defined for the deployment chosen.

For companies subject to heightened requirements, SecNumCloud and dedicated hosting options are available. A single architecture is designed to answer both the GDPR and extraterritorial exposure.

Demonstration

See the agent at work

5 real situations, taken from those that come up most often. Pick one: the exchange unfolds as it would in your organisation.

A scripted demonstration. These exchanges show how the agent behaves — its sources, its refusals, what it leaves to your teams. Nothing is sent from this page, no model is queried here, and the matters named are fictional. That is precisely what we promise your data.
The behaviours shown here — monitoring, automation rules, routing and reminders — are configured with you during deployment, from your tools, your rules and your thresholds.
The architecture points named in these exchanges — location, local execution, isolation, encryption, role-based access, logging — are not a guarantee attached to the demonstration: they are those of the architecture set out in your quotation, and verified before commissioning.

The company in this demonstration

Fictional company

Kerloas Systèmes — a French software consulting and development company (NAF 62.0)

Sector: Computer programming, consultancy and related activities: time-and-materials work on client sites, fixed-price development, application maintenance on subscription
Headcount: 45 employees, including 34 consultants and developers, 1 person in sales administration and 1 finance and administration director
Market served: 112 active recipients: 38 project clients (large accounts on time and materials, smaller companies on fixed price) and 74 subscription-only clients; 6 clients established outside France
Invoicing volume: 140 customer invoices issued per month — 34 time-and-materials lines from timesheets, 10 fixed-price milestones, 96 maintenance subscriptions — and 60 supplier invoices received
Tools in place: A timesheet tool that feeds invoicing, sales management software for milestones and subscriptions, accounts kept by the practice
Who decides: The finance and administration director arbitrates; the practice's chartered accountant signs off the configuration
The improvement points: 96 of the 140 monthly invoices carry a licence and a maintenance service on one and the same line, without distinguishing the nature of the operations; and the option for paying the tax on invoicing rather than on collection, exercised in 2019, appears on none of the invoices

Kerloas Systèmes is a French small company, and the obligations described here are French ones — no equivalent duty is implied for companies established elsewhere. Since 1 September 2026 it must receive its invoices in electronic form as soon as its supplier is required to issue them that way, and its own obligation to issue falls on 1 September 2027. Four of its time-and-materials clients are large accounts which have themselves been issuing since September 2026 — so receiving is not theoretical. The agent is connected to the timesheet tool, to the sales management software and to the approved platform the company selected; it prepares, it does not transmit in place of the platform, and the configuration goes through the practice's chartered accountant.

This company, its figures and the exchanges that follow were invented for the demonstration. They illustrate a common situation; they describe no real client.

E-invoicing compliance assistant · hosted in France

First week under the new regime: here is where you stand, and your problem is not the one you are preparing for.
· Receiving works: 9 structured invoices arrived this month from your four large time-and-materials accounts and were integrated without a single re-keying.
· Issuing is your project, and it falls in 2027: you are a small company, your obligation to issue lands on 1 September 2027. Twelve months — you need three, and not for the technology.
· The real subject is in your subscriptions: I put your 140 invoices for the month through the check the platform will apply. 27 would be rejected, and 19 of them for the same reason — a subscription line that invoices a licence and a maintenance service together, without saying which is a good and which is a service. The nature of the operations is one of the four new mandatory mentions, and as things stand it cannot be determined.
· Second reason, quieter: in 2019 you opted to pay VAT on invoicing rather than on collection. That is also one of the four new mandatory mentions, and it appears on none of your 140 invoices.
· What I propose this week: the rule that splits subscription lines. It settles 19 rejections out of 27, and it costs not one line of code in your timesheet tool. state-of-play_first-week.pdf140 invoices · 27 simulated rejections · 2 mentions at fault
⛓ Sourced · 140 invoices from 01/08 to 31/08, the platform's check set, the month's inbound flow

Hold on — when exactly does this concern us? Everyone keeps saying 2026.

Two dates, and only one of them gets quoted — that is where the confusion comes from.
Since 1 September 2026: every company, whatever its size, must receive its invoices in electronic form as soon as its supplier is required to issue them that way. You, like everyone else. That is done.
On that same date: large companies and mid-sized companies must issue their invoices electronically and transmit their transaction and payment data to the tax administration. That is not you — it is your four large time-and-materials accounts, and that is why 9 structured invoices have already arrived.
On 1 September 2027: that obligation to issue and transmit applies to small and medium-sized companies and to micro-enterprises. That is your date.
The category is read within the meaning of article 51 of the French law of 4 August 2008; the dates themselves come from article 91 of the finance act for 2024. These are French obligations, and they are described here as such. official-timetable_impots-gouv-fr.pdf3 deadlines · source cited and dated
⛓ Sourced · impots.gouv.fr, "From when does the e-invoicing reform concern me?", page updated on 16/01/2026, consulted on 07/09/2026

We picked our platform more or less at random, on the name. Was that a mistake?

No, and I checked rather than reassured you.
First point, and it is disqualifying: the administration publishes two separate lists — operators that are registered, having passed the interoperability tests, and those whose application is complete but whose registration is still pending. Yours is on the first list. Three of the four I compared are on it too; the fourth is only on the second, and I ruled it out for that reason alone.
Then, on the five criteria that matter to a services company: mixed-line invoices — a licence and a maintenance service on the same document —, status feedback, carrying the customer's purchase order number, connection to your sales software, hosting.
Yours comes first on three, second on one, last on one — and that last one counts: it only returns statuses in a daily batch, where two competitors return them as they come. At your volumes that delays a correction by a day. I am not going to sell you a platform change for that.
What I did instead: 8 dry runs, out and back, two of them deliberately faulty to check that the rejection really comes back to you. It does. And I collect statuses twice a day instead of once, which brings the delay down to half a day.
What I do not assert: that a format is "supported". The three formats your sales software can produce were tried on your own chain; the result of those trials is dated and it is in the attachment, and it is not a guarantee of acceptance. platform_comparison-and-tests.pdf4 operators · 5 criteria · 8 dry runs
⛓ Sourced · list of approved platforms (impots.gouv.fr, page updated on 03/09/2026), comparison of 4 operators on 5 criteria, 8 test transmissions on 11 and 12/08

And the recipients you could not resolve — what do we do about them?

There are 14 of them out of 112, and they do not pose the same problem — three pose none at all.
The 14, by cause:
· 5 are groups with several establishments: the registration number exists, but I do not know which of their sites holds your consulting contract. One question per customer, one line of answer.
· 4 carry the registration number of an absorbed company, usually after a buy-out. I found the acquirer for 3 in the public company database; I put them to you, you confirm.
· 3 are clients established outside France. They do not fall under e-invoicing between companies established in France, they fall under e-reporting. That is not a gap to close, it is a separate flow, and I handle it elsewhere.
· 2 are duplicates: same registration number, two records, two billing addresses — a project client that also holds a subscription. I propose the merge, you approve it.
Which gives: 3 lines leave the project because they were never part of it, 2 are settled by a merge, 3 by a confirmation, and 6 by a question to the customer. The 4 large accounts that carry 41% of what you issue are among those 6: I have drafted the 4 e-mails, for you to review and send under your own name. directory_14-lines-sorted.pdf4 causes · 4 e-mails ready
⛓ Sourced · 14 unresolved lines out of 112, public company database, customer file

Our invoices go out fine today. What would actually change?

They go out fine because nobody checks them. I ran the test.
I put your 140 invoices for the month through the pre-issue check, exactly the one the platform will apply. 113 would be accepted as they are. 27 would be rejected.
The 27, by reason:
· 19 for a nature of operations that cannot be determined — your subscription line invoices the licence and the maintenance together, and the mandatory mention requires you to say whether this is a supply of goods, a supply of services, or both. On a single line the answer is "both", and "both" is not usable by the customer's machine.
· 5 for a missing customer registration number — the 5 groups with several establishments.
· 3 for a total that does not add up: a year-end rebate keyed by hand at the foot of the invoice, net amount changed, tax not recomputed.
On the format: your sales software produces a laid-out PDF today. From the same data I produce a structured file, in whichever of the formats your software and your platform actually accepted during the trials — and I promise you none of them before that trial. Your layout does not move a millimetre.
What I have already written: the splitting rule — when a subscription line carries both a licence and a maintenance service, it becomes two lines, each with its own nature. I ran it over your 140 invoices: it corrects 19 out of 19 and breaks none of the other 113. And the mention of the option to pay the tax on invoicing is added at the foot, once, for good.
Putting it into force is signed: your chartered accountant approves it in one review, and that approval is what makes it defensible on the day of an audit. pre-issue-check_140-invoices.pdf113 accepted · 27 rejected · 1 rule tested
⛓ Sourced · 140 invoices issued from 01/08 to 31/08, the platform's check set, the four new mandatory mentions (service-public.gouv.fr, sheet F31808, verified on 11/08/2026)

And if the platform rejects an invoice anyway?

It will, and I will give you straight away the figure that does not suit me.
Out of the 8 dry runs, 3 invoices my check had declared good came back rejected. Reason: the recipient applies its own checks on top of the platform's — one of your large accounts requires the purchase order number in a specific field, and its supplier portal rejects at the door without it.
What that says, and it needs hearing: my check verifies what the regulation and the platform require. It cannot guess each customer's own requirements until a first rejection has revealed them.
What I do with it: every rejection is reconciled with the original invoice, its reason is read, and I derive a check rule specific to that recipient — here, the purchase order number becomes mandatory when the timesheet is entered, so six weeks before the invoice. The 3 rejections produced one rule, applied to the following 6 transmissions to that account: no rejection since.
The lifecycle I track: submitted, received, rejected, paid. An invoice that stays "submitted" for more than 48 hours is escalated, because an invoice that never became "received" is not a late-paying invoice: it is an invoice nobody has.
Over twelve months of your history, I found 9 consulting invoices paid after a phone chase where the customer said it had never received them — lost in its supplier portal. With statuses, those 9 would have shown up in 48 hours instead of seven weeks.
And a status that does not come back stays a status that does not come back: I infer neither acceptance nor rejection from it. lifecycle_statuses-and-rejections.pdf3 rejections · 1 rule produced · 9 cases found over 12 months
⛓ Sourced · 8 dry runs, statuses returned by the platform, 12-month history

E-reporting is yet another thing? We understood nothing of that part.

It is another thing, yes — and it is where the two flows get mixed up most often.
The distinction, in one sentence: e-invoicing covers your sales to companies established in France; e-reporting covers the rest — your sales outside France, your sales to private individuals — and payment data. Two complementary flows, not two competing formats.
What that means here, and what is established: 6 clients established outside France — 4 in the European Union, 2 outside it — the ones I took out of the directory work. For operations with clients established outside French territory there is no obligation to issue an electronic invoice; data on those operations must however be transmitted under e-reporting.
What I do not settle, and it is the point that would cost you: the scope of the payment data. Article 290 A of the French general tax code covers supplies of services falling under articles 289 bis and 290, excluding those where the tax is due by the recipient. Your option to pay the tax on invoicing rather than on collection touches exactly that scope. I have built the file for you — the article, your 140 lines sorted by when the tax becomes due, and both hypotheses with figures — and the qualification belongs to your chartered accountant, not to me.
The point your option changes: you opted to pay VAT on invoicing rather than on collection. That moves the date the tax becomes due, and it must be readable on the invoice — it is one of the four new mandatory mentions. I have carried it into the configuration; I have not checked that the option is still valid, and it is not mine to say: your chartered accountant confirms it.
What I have assembled: the data set, the scope, the frequency, and 4 consistency checks run before any transmission — one of which compares the total transmitted with the total in your sales journal. For August the difference is zero.
Your deadline on this flow is the one for issuing: 1 September 2027. So you can run it dry for months, and that is what I propose: one dry transmission a month from October. e-reporting_scope-and-checks.pdf6 clients outside France · 4 checks · zero difference in August
⛓ Sourced · August sales journal, 140 invoices, e-reporting scope identified

What will you do on your own, and what will wait for a decision?

Three actions without you, all reversible on a word. The rest waits for a signature.
What I do on my own:
· Split a subscription line that mixes licence and maintenance, and carry the right nature on each. And the reverse holds: if the contract does not allow the amount to be apportioned, I invent no key and the invoice is held with the question.
· Collect the platform's statuses twice a day and reconcile them with the invoices. An invoice stuck at "submitted" for more than 48 hours is escalated to the finance and administration director.
· Hold back an invoice my check says will certainly be rejected, with the reason and the correction already written. It is held, not cancelled: one click releases it as it stands if you judge the check to be wrong.
What waits for a decision: putting a check rule into force, merging two customer records, reissuing a rejected invoice, the scope of the e-reporting, and the whole configuration, signed off with your chartered accountant.
What is not mine, and will not be: the transmission itself. It is carried out by the approved platform you selected. Blue Lemon Agent is not an approved platform and is not applying to be.
What I measure and what I do not: every month I publish the acceptance rate, the rejection reasons and the status delays per customer. No per-person counter: a rejection rate per person in sales administration would become a target, and a target of zero rejections is met by not issuing at all — the indicator would destroy what it claims to measure. The only person named is the one who signs, and a signature is not a counter. who-decides-what.pdf3 automatic actions · 5 reserved decisions
✎ Framework · automatic actions and approval circuit to be settled with you

The platform has been down since this morning and I have 11 milestone invoices to get out before the close. Send them straight to our clients, we will sort it out afterwards.

That one I will not do — and it is the only case in our whole relationship where I answer you that way.
The reason, in the administration's own words: "only an approved platform is authorised to provide all the functions laid down by the reform for e-invoicing and e-reporting"; "failing registration by the tax administration, that operator will not qualify as an approved platform and will therefore not be authorised to transmit electronic invoices to the platforms of the company's customers". Blue Lemon Agent is not registered, and an invoice I sent out off-circuit would not be an issued invoice: it would have to be redone, and your customer would turn it down.
What I did while you were asking: the 11 milestone invoices are ready and checked — format, mentions, recipients resolved, totals verified — and each of them carries its own idempotency key. The day the platform answers, they go out in a single gesture, and none of them will go out twice.
And your closing date still holds: an invoice is drawn up on its own date, not at the moment the platform acknowledges it. All 11 are dated, numbered in sequence, and I have prepared the statement to file with the case if the incident drags on.
⛓ Sourced · impots.gouv.fr, "E-invoicing and approved platforms", consulted on 07/09/2026 · 11 invoices checked, 11 idempotency keys

And if the outage lasts three days? We are not going to sit still.

You will not sit still, and you have two ways out — I have already worked them up.
Way out 1, the fastest: your platform publishes a fallback deposit channel. I have checked that it is open and I have prepared the batch in the format it expects; it needs a sign-off from you, mine is not enough and must not be.
Way out 2, if the outage passes 48 hours: moving to a second registered platform. I do not commit to that on my own — it is a contract, so it is your signature — but the case is built: three operators from the registered list, the connection lead times they announce, and the formats each of them accepts. I only kept operators that appear on the registered list, not on the list of pending applications: that difference is exactly the one that would cost you the benefit of the operation.
What I watch in the meantime: the 11 case files stay pending transmission, no status is fabricated, and I conclude nothing from the platform's silence — a delay without an answer stays a delay without an answer, not a rejection.
⛓ Sourced · impots.gouv.fr, "I consult the list of approved platforms", page updated on 03/09/2026, consulted on 07/09/2026

Local inference · no data outside the EU

Your case is not here? That is exactly what a 15-minute conversation is for. Book the free audit →

Use cases

The six compliance workstreams, taken one by one

Each use case matches an agent we deploy. All of them work in support: the configuration is signed off with your chartered accountant.

Included in your agent The 6 capabilities essential to this promise are included, at no extra cost.

From 966 € excl. VAT / month

Connection to the approved platform

Building the selection case, preparing the flows from your sales software and running test batches before the switch. The connection itself and the regulated transmission are carried out by the approved platform you select.

Recipient directory

Checks each customer's French company identifier (SIREN) and billing address; identifies and classifies unresolved entries.

Structured format checks

Checks on the structured format produced by your sales software. The format used — Factur-X, UBL or CII — is the one your software and your platform actually accept: no format is announced as supported before it has been tested on your own chain.

Mandatory mentions verified

Supplier and customer registration numbers, issue date, delivery address when it differs from the customer's.

Lifecycle statuses

Submitted, received, rejected, paid: every status returned by the platform is reconciled with the original invoice.

E-reporting prepared

Transaction and payment data, scope, frequency and consistency checks before transmission.

Controls and safeguards These 4 controls are built into the agent: they frame what it does, whatever plan you pick. They are not chosen and are not added to your order.

Human validation, exceptions and escalation Status, safe closure and audit trail Reconcile supporting documents, rules and accounting entries with an audit trail Handle discrepancies and validations before any accounting entry or payment

What the agent must be connected to This connection is required for the agent to work. It concerns your information system and is scoped during the audit.

Integrate with accounting and banking software and with approved platforms (French e-invoicing)

Need to go further?

These agents handle a different business process, with their own owner and their own price. They are added to this one.

Bookkeeping

Entries, matching and anomalies: the accounting agent takes over once the invoice is compliant.

Accounting agent (summaries, anomalies) from 781 € excl. VAT / month Accounting agent →

Receivables collection

The other side of the cycle: chasing unpaid customer invoices, with the invoice status to hand.

Debt collection agent (multichannel sequences) from 587 € excl. VAT / month Collections →

Regulatory control

Beyond invoicing, keeping compliance up to date against a framework that keeps moving.

Compliance / regulatory control agent from 721 € excl. VAT / month Regulatory compliance →

Does your need fall outside this?

In 15 minutes we identify the most relevant agent — without oversizing the project.

Book the free audit → Build your agent

The gain

How much time does compliance take?

Most of the effort sits in the customer reference data and in the pre-issue checks — two repetitive jobs. By taking them on, the agent shifts human time towards arbitrating the unresolved cases. The size of the gain depends on the state of your customer file and your management software.

Customer reference data compliance (registration numbers, addresses)

Today · reworked line by line

Resolved, gaps arbitrated

Format and mention checks before issuing

Today · done by hand

Systematic

Reading statuses and preparing the e-reporting

Today · in a separate portal

Reconciled and checked

Qualitative, non-contractual comparison: the proportions shown illustrate how the work shifts towards arbitration, they represent no measurement. The configuration is signed off with your chartered accountant before go-live.

How it works

The stages of your AI agent project

Audit & scoping

15 minutes to target the use case with the best return.

Quote or direct sign-up

A catalogue offer is bought online; a specific need gets a costed quote.

Design

We design the agent and its guardrails.

Integration & testing

We connect your tools to the agent, which is itself hosted in France.

Rollout

Going live and training your team.

Operation

Continuous supervision and improvement.

Pricing

A compliance agent, installed and run for you

A level L3 agent: connection to the approved platform, directory, format and mention checks, statuses, e-reporting — plus the connection to your sales software. Connectors and maintenance included. Prices excluding VAT — annual subscription, so the gains have time to settle.

Agility

Setup + controlled subscription

12,770 € ^{excl. VAT} setup

then 966 € ^{excl. VAT}/month — you invest at installation and pay a reduced subscription. Ideal for keeping the cost under control over time.

Installation, configuration and training for your teams
Operation, human oversight, updates and support
Sovereign hosting in France, a dedicated and isolated resource

Order →

The simplest Serenity

All inclusive, no setup fee

1,676 € ^{excl. VAT} /month

all inclusive, immediate start. No upfront investment: a single subscription. Ideal for starting quickly and simply.

Setup included (installation, configuration, training)
Operation, human oversight, updates and support
Sovereign hosting in France, managed end to end

Order →

100% Sovereign

On site, you own it

17,395 € ^{excl. VAT} setup

then 1,187 € ^{excl. VAT}/month · + hardware from 2,491 € (one-off purchase, in addition) — a sovereign computer installed on your premises, maintained remotely. Models run locally, your data returned at the end of the contract. 36-month commitment.

Hardware installed on your premises (you own it)
French / European AI models run locally
Secure remote maintenance (Pro support included)

Order →

Not included in the packages: AI consumption (model tokens), re-invoiced at real cost with no margin, and tracked in real time in your client area. Maintenance and supervision subscription for an initial term of 12 months for the Agility package, 24 months for the Serenity package and 36 months for the 100% Sovereign package, renewable; support levels (SLA 72 h / 24 h / 4 h) optional. Bespoke development, additional integrations or exceptional volumes are quoted separately. Support Monday to Friday, 9am to 6pm. Prices exclude VAT.

AI model: none of the AI models offered currently carries a fixed surcharge. When the selected model carries a cost, that cost is shown when you choose it, before you order, and re-invoiced at the cost incurred, with no mark-up; usage is billed at the publisher's price. Publishers' prices are published in US dollars: the amount re-invoiced is the amount in euros actually borne by Blue Lemon Agent on the publisher's invoice, at that invoice's exchange rate, with no commission or mark-up.

Included components and additional components Components included in the base offer: the Blue Lemon Agent software foundation, the AI models listed in the order journey, the standard channels (Microsoft Teams, Slack, WhatsApp Business, email, website chat, calendars, Microsoft 365 / Google Workspace, file storage, market VoIP telephony, professional social-media pages and accounts, Google Business Profile), hosting in France for the package chosen, backups, supervision, updates and support. If adapting the AI agent to your constraints, your needs or your requests requires other paid components — a third-party publisher's software licence, paid API access to one of your applications, hosting of health data, for which French law requires an HDS-certified host (art. L. 1111-8 of the French Public Health Code), SecNumCloud-qualified hosting, a speech synthesis service, particular hardware —, they are offered to you as an option or on quotation and re-invoiced at the cost incurred; nothing is committed without your written agreement. Where the artificial intelligence model you choose entails an additional cost, that cost is shown to you before you order and re-invoiced to you at the cost incurred, with no margin.

What to expect

Go-live 2 to 3 weeks

Agent designed, channels connected, team trained.

Steady state 4 to 7 weeks

After a few weeks of real use, once the agent's behaviour matches what you expect. Indicative estimate, adjusted to the options you keep. It is not a delivery commitment.

See the full price list →

Estimate my gains in 1 minute →

Our commitment

Four guarantees that matter for your invoicing

Your prices and your customers never leaveLocal inference or an isolated resource hosted in France; no invoice, no price list entrusted to a foreign third party.

Data in France, under French lawYour invoicing data: minimised and located in France, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.

The configuration is signed off with your chartered accountantThe agent prepares it, documents it and tests it against your history; the sign-off that makes it defensible stays human.

Human oversight & traceabilityEvery transmission, every status and every correction is logged, with its timestamp and the identity of whoever took the decision.

Going further

Related resources

AI agents for business →Our full offer Sovereign AI hosted in France →Our confidentiality commitment AI for accounting firms →For practices supporting the deadline

Frequently asked questions

Your questions, our answers

When is my company concerned?

Two dates, and they are not the same. Since 1 September 2026, every company, whatever its size, must receive its invoices in electronic form as soon as its supplier is required to issue them that way; on that same date, large and mid-sized companies must issue their invoices electronically and transmit their transaction and payment data to the tax administration. On 1 September 2027, that obligation to issue and transmit applies to small and medium-sized companies and to micro-enterprises. Your company's category is read within the meaning of article 51 of the French law of 4 August 2008 on modernising the economy. Source: impots.gouv.fr, page updated on 16 January 2026 and consulted on 7 September 2026.

Is a PDF sent by e-mail enough?

No, not within the scope of the reform. A scanned paper invoice or an ordinary PDF sent by e-mail does not count as an electronic invoice there: invoices travel through a platform approved by the administration, in a structured format. Outside that scope — transactions with consumers, suppliers not yet subject to the obligation to issue — the earlier rules continue to apply. The agent produces the structured format from your sales software, without changing the way you invoice or your layout.

Does the agent choose the approved platform for me?

It builds the case and lays it out with figures: formats accepted, status feedback, connection to your management software, hosting, historical data migration. Signing the contract is yours, and the configuration that follows is signed off with your chartered accountant.

What does the agent do if the platform rejects an invoice?

It reconciles the returned status with the original invoice, names the reason for rejection, prepares the corrected invoice and proposes the rule that prevents that reason at source. You keep the decision to reissue. A rejection is never left without follow-up or without a readable reason.

Do we have to change sales management software?

In the vast majority of cases, no. The agent connects to the main ERPs and sales management tools as well as to the approved platform you selected; the integration scope is settled during framing, without forcing a migration.

How long does deployment take?

The lead time depends on the integrations to be built — sales software, accounting, approved platform — and on the state of your customer file. It is settled during framing, after a free audit that measures that state, then a design, integration and testing phase, and a configuration review by your chartered accountant before go-live. We do not announce a duration before that measurement.

Is Blue Lemon Agent an approved platform?

No. An approved platform is a dematerialisation operator registered by the French tax administration for a renewable three-year term; only a registered operator is authorised to issue, transmit and receive electronic invoices and to transmit data to the administration. Blue Lemon Agent is not registered and is not applying to be: the agent prepares your flows, checks them and hands them to the approved platform you have selected. The administration publishes two separate lists — operators that are registered, having passed the interoperability tests, and those whose application is complete but whose registration is still pending. Source: impots.gouv.fr, page updated on 3 September 2026 and consulted on 7 September 2026.

Which formats are actually supported?

Those your sales software produces and your platform accepts, observed on your own chain during the testing phase — Factur-X, UBL or CII as the case may be. We publish no list of guaranteed formats: a format is declared supported only after a dated test batch on your own invoices, and the result of that test batch is handed to you.

How do e-invoicing and e-reporting differ?

E-invoicing is the invoice itself, exchanged between two taxable companies through approved platforms. E-reporting is the transaction and payment data transmitted to the administration for operations that do not travel as an electronic invoice — sales to consumers, operations with clients established outside French territory. Payment data is added to that, and its exact scope depends on when VAT becomes due on your operations: the agent lays the question out, it does not settle it. The agent prepares both and keeps them explicitly apart in every case file; where the qualification of an operation is uncertain, it is flagged as such and is not settled on its own.

Does the agent transmit an invoice without sign-off?

No. The agent assembles the case file, runs its checks and prepares a submission draft carrying an idempotency key; releasing it for transmission requires sign-off by an authorised person, and the regulated transmission itself is carried out by the approved platform. A status returned by the platform is recorded as a dated observation: it is never inferred from an absence of reply.

Related use cases

Other agents in the financial cycle

Supplier invoice processing →The inbound flow, end to end Accounting agent →Entries, anomalies and summaries Compliance & regulatory control →A moving framework, kept up to date

Let's talk

Let us take stock before 1 September

15 minutes to measure the gap between your customer file and what the platform expects — hosted in France, supervised, no commitment.

Free audit (15 min) → Write to us