Automate e-invoice reception: processing supplier invoices in France with n8n

·11 min read

Picture a twenty-person trading company in France. It has chosen its approved e-invoicing platform (a "plateforme agréée" under French rules), and since September the invoices from its large and mid-sized suppliers have arrived there in electronic format. Its smaller suppliers still send PDFs by email. Every morning someone collects invoices from both places, looks for the purchase order, forwards them to a manager, waits for an answer, then keys in the bank transfer. The "to process" folder grows every time someone is away.

The French reform sets the channel and the formats. Organizing the processing is still up to each company, and there are now two entry points: structured data from the platform, where invoice number, supplier SIREN (the French company identification number), amounts and due date sit in dedicated fields, and PDFs that still have to be read. When you automate e-invoice reception, the useful work is to merge these two flows, check each invoice, route it for approval, prepare payment and pass it on to accounting.

This article describes an n8n workflow for a company of 5 to 50 people, from reception to payment, and what to prepare before the obligation to issue e-invoices in September 2027.

Where e-invoice reception stands in France in November 2026

The DGFiP practical getting-started guide (DGFiP is the French tax administration), dated July 2026, states that since 1 September 2026 every company covered by the reform must be able to receive electronic invoices through an approved platform (article 289 bis of the French tax code). The AIFE, the French state agency in charge of the system, states that this obligation applies whatever the size of the company.

Date Obligation Companies concerned
1 September 2026 Receive e-invoices All companies covered, whatever their size
1 September 2026 Issue e-invoices Large and mid-sized companies (ETI)
1 September 2027 Issue e-invoices SMEs, very small businesses and micro-businesses

Timeline according to the DGFiP practical guide and the AIFE, accessed on 11 November 2026.

What this means for reception: until their 2027 deadline, your SME, very small and micro-business suppliers may keep invoicing the way they usually do (DGFiP guide, question 20), for example with a PDF sent by email.

According to the guide (question 3), an invoice received by email, as a PDF or on paper must not be set aside for that reason alone, as long as it reflects a real transaction and contains the information needed to process it. It can be processed and paid, and the channel alone does not remove the right to deduct VAT.

If a supplier already subject to the issuing obligation sends a PDF, you can ask it to send the same invoice through the electronic channel. Under question 4, this request is optional, is not a condition for processing or payment, and must not be used to delay a payment that is due.

On formats, the DGFiP fact sheet on the reform and the impots.gouv.fr page Je découvre la facturation électronique list the three formats approved platforms must transmit: CII and UBL, which are fully structured, and Factur-X, which combines an XML file with a human-readable PDF. Their profiles are described in the AFNOR XP Z12-012 standard.

For an overview of the reform, see what companies should automate for France e-invoicing.

What structured data changes: less OCR, more business checks

With a PDF, the effort goes into extracting the amount, the date and the supplier. With a UBL, CII or Factur-X invoice, that information sits in identified fields, so extraction becomes a matter of reading a file, reliably and repeatably. In both cases, the effort moves to questions the platform does not ask:

  • Is this supplier known, and do its bank details match the ones we have on record?
  • Does this invoice match a purchase order, and does the amount match what was delivered?
  • Have we already received it, through the platform or another channel?
  • Who needs to approve it, and by what date must it be paid?

According to the DGFiP fact sheet on invoice statuses, a platform can reject an invoice for a non-compliant format or an inconsistency between the net amount, VAT and the gross total. It has no way of knowing whether you actually ordered the goods.

How to automate e-invoice reception in n8n, step by step

1. Retrieve invoices from the platform. A scheduled trigger, every hour for example, queries the approved platform. The AIFE refers to the XP Z12-013 standard for approved platform APIs, but ask yours what it actually exposes (API, notifications, export). Each invoice is recorded in a tracking table with its platform identifier, its reception channel and its internal status ("received", "to approve", "approved", "paid", "posted").

2. Retrieve invoices received by email. I recommend a mailbox dedicated to invoices. An n8n trigger reads new messages and records the attachments in the same tracking table, with the channel "email" (see the article on email triage with n8n).

3. Read the format. UBL and CII are XML files. For Factur-X, you take the XML part attached to the PDF, or request the data from the platform. For a plain PDF, OCR extracts the fields (see the article on Mistral OCR and n8n). The workflow converts every invoice into a single internal format: supplier SIREN, invoice number, date, net, VAT and gross amounts, due date, purchase order reference, line items, and bank details when present. All later steps read only this format, whatever the channel.

4. Check the supplier. The SIREN is looked up in the supplier master data. Unknown supplier: approval required. Different bank details: blocked.

5. Match against the purchase order. If the invoice carries a purchase order reference, the workflow looks it up and compares amounts within a tolerance set in advance. With no reference, the invoice goes to the budget owner.

6. Detect duplicates, including across channels. The key "supplier SIREN + invoice number" is unique in the tracking table. The same invoice can arrive as a PDF and later through the platform, after a regularization for example. The DGFiP guide (question 5) then asks you to compare number, supplier, customer, date and amounts, designate one reference copy and mark the others as copies, without rejecting the invoice. The tracking table keeps a record of the match. A looser check (same supplier, same amount, close dates) flags doubtful cases to a person.

At the end, each invoice sits in one of three queues: "compliant", "to approve" or "anomaly". The workflow pays nothing and rejects nothing on its own. Rejection is a lifecycle status that the DGFiP fact sheet reserves for the recipient. The DGFiP guide (question 12) specifies that this status must always state a reason and is limited to certain grounds, such as an invoice sent to the wrong recipient or a breach of contractual terms. I advise against letting a workflow set this status. A person decides, and n8n can then prepare the action.

Where AI is still useful

Suggesting the expense account. A model can suggest an accounting code based on line descriptions, the supplier and past entries. If it returns a category that is not on your list, the invoice goes to review.

Flagging unusual amounts. On top of fixed thresholds, a model can explain a gap: a subscription three times more expensive than usual, a line never seen before from this supplier. The decision stays with the approver.

Reading PDF invoices. For invoices received by email, OCR and a model extract the fields, then the workflow checks that net, VAT and gross amounts add up. An incomplete extraction goes to review.

Data sent to a model goes to that model's provider: send the description and the amount, and keep bank details out of the request.

Human approval before payment

The decision to pay stays with an identified person. I recommend writing these rules down before going live:

Situation Rule
Compliant invoice below the threshold set by management Quick one-click approval by the budget owner
Invoice above the threshold Approval by the managing director or finance lead
New supplier Supplier and bank details verified before the first invoice
Changed bank details Blocked, supplier called on a number already on file, then master data updated by an authorized person
Likely duplicate, unusual amount Manual review, reason logged in the tracking table

A change of bank details is a classic fraud scenario: a fake supplier, or a real one whose mailbox has been compromised, announces new account details. So the workflow never updates master data from an invoice or an email. It compares, blocks and alerts.

The approval request goes through the channel the team actually reads, with the supplier, amount, due date, check results and a link to the invoice. The response is logged with the person's name and the time. For where to place approval points, see the article on human approval for AI agents.

Payment with Qonto, accounting with Pennylane: avoiding double entry

After approval come payment and bookkeeping, here with two tools common in France: Qonto for banking and Pennylane for accounting. The main risk is double entry: an invoice created or paid twice.

One source for each piece of information. The tracking table for progress, the accounting tool for entries, the bank for payments. If your approved platform already forwards invoices to your accounting software, n8n must not create them there again.

n8n prepares, the authorized person pays. I recommend that n8n prepares the list of approved invoices, sorted by due date, and that the authorized person approves the transfers in the bank. For reconciliation afterwards, see the article on Qonto and n8n.

A unique key before every creation. Before creating anything in the accounting tool, the workflow checks that the invoice is not already there, whatever channel it came through. For the Pennylane API, see the article on Pennylane and n8n, and check the documentation for what the API currently allows for supplier invoices.

Errors and monitoring

The platform stops responding. Outage, expired credentials, API change: an error workflow alerts a named person (see the article on n8n error handling).

Silence. Set an alert threshold based on your own invoice volume, for example a number of working days without any invoice, channel by channel. A daily check tests it and raises an alert.

Invoices that never arrive. An invoice rejected by a platform does not reach you, and it is up to the supplier to fix it. When the supplier chases payment, the tracking table lets you answer quickly.

Checklist to get started and prepare for issuing in September 2027

For reception:

  • You know how to get invoices out of the approved platform (API, notifications, export).
  • Invoices received by email or as PDFs have their own entry path (OCR, same internal format, same checks) and are matched against copies received through the platform.
  • The supplier master data holds verified SIREN numbers and bank details, with someone responsible for it.
  • The tracking table has a unique key on SIREN and invoice number.
  • Approval thresholds and approvers are written down.
  • No bank detail change is applied without calling the supplier on a known number.
  • Rejecting an invoice is always decided by a person, with a reason.
  • An error workflow and a silence check are in place.

For issuing, mandatory for SMEs on 1 September 2027 according to the timeline above:

  • Check that your approved platform handles issuing, and in which formats.
  • Complete customer records with the SIREN and the delivery address when it differs: impots.gouv.fr lists them among the details to be entered in dedicated fields.
  • Check addressing with your platform: the directory is used to route invoices to the customer's reception platform (DGFiP guide, question 10). If routing fails, check the SIREN, SIRET and receiving establishment first.
  • Plan to track the statuses of your own invoices, rejections included.
  • Test issuing with a few customers well before the deadline.

Start with retrieval and the tracking log

The first piece of work is modest: get invoices out of the platform and the mailbox, record them in a tracking table, detect duplicates and alert someone when retrieval fails. Checks, approval, banking and accounting come next, one at a time. At Kirako, we build this kind of workflow in our n8n automation projects, with human approval wherever money leaves the company.

Sources

Accessed on 11 November 2026 (French-language pages):

Also available: Read in French