1 of 22

E-Invoicing in France : �the final steps

July 2026

C1 - Restreint (utilisateur habilité)

2 of 22

Decoding the �French ‘E-Invoicing’ reform

01

C1 - Restreint (utilisateur habilité)

3 of 22

3

Strengthen the competitiveness of companies by reducing the administrative burden of creating, sending and processing paper invoices and greater security of commercial transactions

1

Combat tax fraud and reduce the non declared VAT gap by means of automated cross-referencing

2

Enables ongoing information on companies’ activity so that economic policy measures introduced by the government can be effectively managed

3

Facilitate VAT returns completion with automated be pre-filling from the Tax authorities platform

4

The key objectives of making it mandatory

3

C1 - Restreint (utilisateur habilité)

4 of 22

Reform Timeline

  • Large companies: Headcount > 5,000 or revenue > €1.5 bn and balance sheet > €2 bn
  • Intermediate-sized companies: between Large and SME’s
  • SMEs (Small and Medium Enterprises): Headcount < 250 and revenue < €50 m or balance sheet < €43 m

Obligation to issue electronic invoices

Obligation to receive

electronic invoices

September 1, 2026

All companies (large and Intermediate-sized companies, SMEs and micro-enterprises)

SMEs and micro-enterprises

September 1, 2027

September 1, 2026

Large and Intermediate-sized companies

Planning per type of entity

C1 - Restreint (utilisateur habilité)

5 of 22

  • Penalties incurred in case of non-compliance

    • No penalty will be levied for the first infraction corrected within 30 days (either spontaneously or at the tax authority request)

Non-compliance

Penalties

Transmission (Issuing / receiving) electronic invoices via an agreed platform

Penalty of 500 € at first to be increased to 1 000 € every 3 months in case of persistence

Issuing electronic invoices

Penalty of 50 € per invoice with an annual ceiling of 15 000 €

E-reporting

Penalty of 500 € per instance with a ceiling of 15 000 € per year

Penalties

5

C1 - Restreint (utilisateur habilité)

6 of 22

Who is in scope, and for which transactions?

Seller

Taxable person established in France

Seller

Taxable person NOT established in France

Buyer

Taxable person established in France

Buyer

Non-taxable person (B2C)

Buyer

Taxable person NOT established in France

Other transactions

/!\ Applicable use cases – established for VAT ≠ registered for VAT in France

e-Invoicing

Mandatory, via an approved platform (PA)

Seller : Nothing

Buyer : e-Reporting

e-Reporting

Only if the foreign seller is liable for French VAT (unless One-Stop Shop)

e-Reporting

Except supplies exempt under Art. 261 to 261 E CGI – Art. 290 I CGI

Out of scope

Diagnosis of the obligations applicable to each transaction / flow, to be run at the boundaries of every business process and tool

Established = fixed establishment for VAT purposes (BOI-TVA-CHAMP-20-70), not a permanent establishment

The size test (large / intermediate / SME) applies to the French legal unit (SIREN), not to the group

6

C1 - Restreint (utilisateur habilité)

7 of 22

  • E-invoicing
    • B2B domestic transactions between French based taxpayers, irrespective of the VAT treatment
    • Limited formats of invoices authorized with strict content including new information :
      • SIREN
      • Sales type : Goods – Services – Combined
      • Option for paying VAT on debits
      • Delivery address, if different from the billing address
    • Obligation to use private agreed platforms (PA in French) to communicate with the Tax authorities and the client
    • Status of electronic invoices

  • E-reporting: Transactions to be VAT declared and not covered by e-invoicing
    • Sales transactions including B2B international (EU and non-EU) and B2C
    • Purchase transactions from EU (goods and services) and other countries (services only)
    • Payment status of e-invoices for companies paying VAT on collection
    • Aggregated information in a specific format

  • Timing
    • E-invoices are transmitted when issued
    • E-reporting should be performed every 10 days at d+10 for companies subject to normal VAT regime (monthly return)
    • Invoice Lifecyle – Realtime (deposit, technical rejection, customer refusal, payment collection)

Scope of the new regulations

7

C1 - Restreint (utilisateur habilité)

8 of 22

The imposed scope

  • The 138 declared AP must ensure a minimum scope of functionalities imposed by the Government.
  • They could offer many other functionalities such as the creation of invoices, the management of other required formats between supplier and customer, etc.
  • For our bookkeeping clients, we chose Generix Group for their experience, size and ability to provide us with their white-label services under the name PA full.

Issuing electronic invoices to the customer’s AP

Invoice lifecycle management

Connection to the PPF

Extraction and transmission of data required by the State

Compliance checks on all documents and data exchanged

Receipt of electronic invoices issued by the supplier’s AP

Support for 3 base formats (UBL/CII/Factur-X)

Connection and interoperability with all other APs

Retrieval and management of directory data

Secured hosting in-house or under the SecNumCIoud standard

ISO 27001 certification

Secure authentication

(and, at a later stage, ‘substantial’ authentication)

What is an AP for?

C1 - Restreint (utilisateur habilité)

9 of 22

  • Format
    • Electronic invoice will contain a minimal volume of data in a structured format
    • XML UBL (Universal Business Language) developed by OASIS
    • XML CII (Cross Industry Invoice) developed by the United Nations
    • Factur-X developed by the Tax authority and several experts
  • Content
    • 32 mandatory items of data to begin with: SIREN, VAT, dates, invoice No., amount excl. VAT, etc.
    • New information required : customer SIREN, VAT on accrual basis (“option pour les debits”), Nature of operations (Good/Service/Double + sub-categories), address where the goods are delivered
    • New detailed information’s per invoice line: price reduction, quantity, discount

E-invoicing - types of invoices

9

C1 - Restreint (utilisateur habilité)

10 of 22

  • B2B and B2C transactions
    • Transmission through AP
    • B2B sales to EU and non-EU clients (same data as for e-invoicing obligation)
    • B2B purchases from EU and non-EU suppliers
    • B2C transactions with invoices (same data as for e-invoicing obligations)
    • B2C transactions without invoices (aggregated daily data)

  • Status
    • There are several invoices status (15) tracking the invoices journey through the APs
    • 5 are mandatory: “submitted”, “rejected by supplier AP”, “rejected by client AP”, “collected” and “rejected by the client”
    • Others are recommended like “partially approved”, “approved” or “sent for payment”

E-reporting requirements

10

C1 - Restreint (utilisateur habilité)

11 of 22

E-invoicing / e-reporting / life-cycle statuses

  • The Public Portal (PPF) will only receive data from the Approved Platforms
  • It will manage the Directory of companies
  • It, of course, concentrates the data required by the tax authorities.
  • All companies must therefore enter into a contract with one or more AP’s for sending and receiving their invoices.

Invoice data (e-invoicing), transaction data (e-reporting) and payment data (e-reporting)

Invoices (e-invoicing), life-cycle statuses

How do the flows work?

Invoice flow

Supplier

Supplier

AP

Buyer

AP

Buyer

PPF - central directory

and data concentrator

Invoice, transaction

and payment data

French tax authorities

Issuers and recipients

Approved Platforms (AP)

C1 - Restreint (utilisateur habilité)

12 of 22

How to be�Prepared ?

02

C1 - Restreint (utilisateur habilité)

13 of 22

Why acting now: Risks and opportunities

1 September 2026 seven weeks away:

Every business established in France must be able to receive e-invoices.

Risks of not being ready

  • The deadline is weeks away: selecting an Approved Platform, registering in the central directory and mapping the ERP all take lead time.
  • Unable to receive means your French suppliers cannot invoice you: payments stall and your image with third parties suffers.
  • Fines: EUR 50 per invoice not issued electronically and EUR 500 per missing e-reporting transmission, each capped at EUR 15,000 a year.
  • A poorly configured AP complicates the supplier flow: duplicate invoices received twice (platform and PDF), life-cycle statuses left unread, rejections nobody notices.
  • Dirty master data (SIREN, routing codes, delivery addresses) means invoices bounce back before they ever reach your books.
  • No named owner: the reform cuts across finance, IT, procurement and tax at once.

Benefits once you are

  • Invoice status is known at every step: submitted, received, rejected, approved, cash collected. No more chasing.
  • No invoice left in a drawer: every supplier invoice arrives through one channel and is traceable end to end.
  • Compliance by construction: non-compliant invoices are rejected by the AP before they enter your accounts.
  • Shorter approval cycles, fewer disputes, and a firmer grip on DSO and DPO.
  • Manual re-keying disappears and archiving is secured for ten years.
  • The investment is reusable: the same structured data will feed EU-wide ViDA reporting from 2030.

13

C1 - Restreint (utilisateur habilité)

14 of 22

E-Invoicing : 4 strategies

Integrated solutions :

  1. Clients InexWebElectronic invoicing solution directly embedded and run by Ad Astra / In Extenso

  • Clients with their own accounting tool and simple invoice processingFor clients running a non-complex invoicing or accounting software:
    • Referral to their software vendor for its standard AP solution.
    • Ad hoc support from Ad Astra to clarify the stakes and ease the path to compliance.

  • Clients with complex tools or an ERP

For clients with several invoicing tools, high volumes or a complex ERP:

    • Tailor-made support (diagnostic, scoping, help selecting the AP, implementation).
    • Standard project approach (30 to 60 days)

Stand-alone solutions :

    • Clients whose accounting tool has no interface with an AP

For clients with low volumes and low complexity

    • Review of use cases and of the manual procedures to put in place
    • Walkthrough of the Inexcompta Full AP, plus training

Timing

14

C1 - Restreint (utilisateur habilité)

15 of 22

Strategy

03

C1 - Restreint (utilisateur habilité)

16 of 22

THE JOURNEY TO ELECTRONIC INVOICING STARTS NOW! - NOVEMBER 2025

One tool for:

  • Inbound invoices
  • Outbound invoices
  • e-reporting

Cases 1 & 4 : The Inexweb ecosystem

16

C1 - Restreint (utilisateur habilité)

17 of 22

Automated collection

A single channel to receive every invoice, e-invoicing and PDF alike

Suppliers send directly by email or through an AP.

Collectors automatically retrieve invoices from supplier portals.

0

Fast approval

Every invoice received must be approved before it enters your books.

New suppliers are detected and created on the fly.

This feeds the invoice life-cycle statuses and the e-reporting data.

10-year archiving

All approved invoices stay accessible for 10 years.

Built-in filters make any invoice easy to find.

Cases 1 & 4 :

Inex-ACHATS

C1 - Restreint (utilisateur habilité)

18 of 22

Issue invoices quickly

A simple, structured wizard that produces compliant electronic invoices and sends them automatically to an Approved Platform.

An Items file and a Customers file, filled in before or while drafting quotes, invoices and credit notes.

Descriptions and unit prices remain freely editable while drafting.

Discounts applied per line or on the total.

18

Send invoices effortlessly

Sending with a customised covering message.

Sent via an AP or by email, depending on the customer type held on their record.

A reminder for that invoice can be raised and sent just as easily.

Cases 1 & 4 :

Inex-FACT

C1 - Restreint (utilisateur habilité)

19 of 22

    • Assessment of organisational repercussions

    • Redefining of roles and responsibilities

Organisational challenges

    • Invoice lifecycle management, collection data

    • Flow management outside e-invoicing

Functional challenges

    • Alignment of third-party reference systems with new requirements
    • Process for continuous updating of third-party reference systems

Data management challenges

    • Change in current routine (i.e. rejections/refusals)
    • Internal and external communication (customers and suppliers)

Human challenges

Ad-Astra helps you identify the critical topics of an electronic invoicing compliance project, to handle them effectively and model a functional target in line with your future challenges.

Cross-functional prerequisites for implementation

Cases 2 & 3 : The challenges you need to take up... for successful compliance!

19

C1 - Restreint (utilisateur habilité)

20 of 22

Time and materials

Flat rate

Functional guidance

Decision support

Finance consulting engineers

Management

Change support

Study

Deployment

Change management

Operational support

Cases 2 & 3 : Our approach…� …Tailor-made support!

We are involved in every stage of project management, but only in the phases that are necessary for you.

What we do:

What we don’t do:

  • An accurate diagnosis of your ecosystem
  • A detailed roadmap to compliance
  • Support in implementing the necessary changes
  • No replacement of your system, but streamlining of IT developments
  • No technical work, but coordination
  • No responsibility for tax matters, but a clear understanding of the obligations

20

C1 - Restreint (utilisateur habilité)

21 of 22

Our

approach

Case 2 & 3 : Our approach…�

…aims to provide an exhaustive view of the existing system (process, system, stakeholders) while quickly anticipating the target to be deployed

Phase 2: Definition of the target

Phase 1: Analysis

of the existing system

Phase 3: validation

and rolling out of the roadmap

  • Qualify incoming and outgoing invoicing flows (volume, tool, stakeholder, process, tax specificities if applicable)

  • Highlight the impacts of the transition to e-invoicing/e-reporting (operational issues, need to adapt the process, adapt the invoicing IS, etc.)

  • Clarify the reform and the organisational and technological solution that makes it possible to conform to it

  • Gap analysis between the current operation and the reform prerequisites (VAT, structure and content of master data, etc.)

  • Suggest possible scenarios that take into account the issues associated with each invoicing flow

  • Construct the rationales necessary for arbitration

  • Qualify advantages/disadvantages

  • Illustrate with examples from similar assignments

  • Coordination with other related projects in progress

  • Details of the selected target (flow mapping, target operating mode)

  • Formalise the repository of functional requirements required by the RFP/integrator

  • Project plan

  • Suggested project governance

  • Consulting engineers for the deployment of the target solution

Mapping & impact analysis by flow

Scoring of existing tools

Description of the adopted scenarios

Project roadmap

Specifications

Description

Key deliverables

Collecting of information

Co-constructing of the target

Validating, planning and rolling out of the project

Flow/scenario application matrix

21

C1 - Restreint (utilisateur habilité)

22 of 22

Alban OERLEMANS

Associé

Finance transformation

Your Contact :

Thank You

Merci.

62 Rue François 1er,

75008 Paris

www.ad-astra.fr

C1 - Restreint (utilisateur habilité)