Interoperability between Certified Platforms in the e-invoicing reform
The e-invoicing reform introduces a new framework for exchanges between businesses, Certified Platforms, and the tax authorities.
At the heart of this system, interoperability between CP – Certified Platforms is an essential condition to ensure smooth transmissions, regulatory compliance, and the continuity of financial processes.
Specifically, a business must be able to send an e-invoice to its client even if the client uses a different Certified Platform. Without this interoperability, the system would quickly become unmanageable: each business would have to connect to every platform, leading to considerable costs, delays, and technical risks.
Interoperability is therefore one of the pillars of the reform. It allows businesses to choose their platform without hindering their exchanges with clients and suppliers.
With DEMATRUST, ICD International supports businesses in this transition with a Certified Platform designed to secure flows, manage statuses, facilitate ERP integration, and ensure compliance with the e-invoicing reform.
What is interoperability between Certified Platforms?
Interoperability refers to the ability of Certified Platforms to exchange e-invoices, statuses, and associated data in a fluid, secure, and compliant manner, even when operated by different providers.
An issuing CP must be able to transmit an invoice to a receiving CP:
- without loss of information;
- without format disruption;
- with the required data;
- in compliance with the reform's standards;
- with full traceability;
- ensuring the circulation of lifecycle statuses;
- enabling the transmission of data required by the administration.
This interoperability applies to document flows, tax data, processing statuses, and technical interactions between platforms.
You can find a complete definition of a PA's role on our dedicated page: PA – Approved Platform.
A practical example of exchange between two PAs
Let's take a simple case.
Company A issues an electronic invoice from its Approved Platform. Its client, Company B, uses another Approved Platform.
Interoperability must allow the invoice to flow smoothly between the two platforms.
The process must ensure:
- the possible conversion from the source format to a regulatory format;
- the verification of mandatory data;
- the identification of the recipient via the directory;
- the secure transmission of the invoice;
- receipt by the client's platform;
- the return of processing statuses;
- the transmission of mandatory data to the administration.
The objective is for Company A and Company B to be able to exchange without having to manage the technical complexity between their respective platforms.
Why is interoperability strategic?
Interoperability is strategic for several reasons.
First, it ensures the smooth flow of exchanges between companies. In an ecosystem where dozens of Approved Platforms coexist, it is essential for data flows to move without friction.
It also reduces operational risks. Poor interoperability can cause delays, rejections, status errors, or unreceived invoices.
It also strengthens the customer-supplier relationship. Companies must be able to track their invoices, understand their status, and quickly address anomalies.
Finally, it limits the risk of reliance on a single provider. Thanks to common standards, a company must be able to adapt its organization or change providers without rebuilding its entire technical architecture.
Interoperability therefore makes it possible to:
- ensure continuity of exchanges;
- reduce non-compliance risks;
- improve traceability;
- streamline the customer-supplier relationship;
- limit migration costs;
- avoid unnecessary custom development;
- protect companies against technological lock-in.
Interoperability and AFNOR API: What This Means for Businesses
Interoperability is not limited to exchanges between Approved Platforms.
It also applies to how companies connect their information systems to their platform.
This is the primary focus of the AFNOR API initiatives, particularly experimental standard XP Z12-013, which aims to standardize interfaces between company information systems and Approved Platforms.
For a company, the stakes are high.
If a company has developed a standardized integration with a first Approved Platform, it should be able to limit redevelopment in case of a provider change, provided that the new platform adheres to the same standards.
The goal is to enable better technical portability.
This allows for:
- reduce migration costs;
- limit specific developments;
- accelerate platform changes;
- secure ERP integrations;
- simplify maintenance;
- strengthen business independence.
This logic is essential to preserve businesses' freedom of choice in an ecosystem based on several Approved Platforms.
Regulatory formats at the heart of interoperability
For platforms to exchange efficiently, invoices must adhere to structured and common formats.
The main formats of the reform's minimum baseline are:
- Factur-X;
- UBL;
- CII.
These formats enable invoice data to be structured so that it can be automatically read, checked, transmitted, and integrated by systems.
The Factur-X format combines a human-readable PDF with structured data usable by systems.
UBL and CII formats are more geared towards automated exchanges between information systems.
Interoperability requires that Approved Platforms are capable of processing these formats, verifying mandatory data, and transmitting the necessary information without loss of business or fiscal meaning.
Peppol's role in exchanges between platforms
Peppol plays an important role in standardized electronic exchanges.
It is a secure exchange network based on certified Access Points. It allows organizations connected to the network to transmit and receive electronic documents according to common rules.
As part of the French reform, Peppol can contribute to interoperability between platforms, particularly to facilitate the flow of invoices and statuses.
However, interoperability should not be limited to Peppol alone.
The exchange framework can also rely on other mechanisms, such as bilateral agreements or network exchange protocols, depending on the arrangements adopted by the platforms and the applicable framework.
ICD International is a certified Peppol Access Point and supports companies in their projects for electronic exchanges, dematerialization, and e-invoicing.
The directory: a central element for routing invoices
Interoperability also relies on the national directory.
The directory allows identifying the platform chosen by a company to receive its electronic invoices.
When an invoice is issued, the directory helps determine which platform it should be sent to.
It therefore plays a key role in routing flows.
Incorrect directory configuration can lead to:
- an invoice sent to the wrong platform;
- a rejection;
- processing delays;
- loss of visibility;
- difficulty tracking statuses;
- strained relations with a client or supplier.
The quality of directory data is therefore a priority for businesses.
It is particularly important to ensure that identification information, billing addresses, and connections to the Approved Platform are correctly configured.
Lifecycle statuses: business interoperability
Interoperability does not only concern invoice transmission.
It also concerns lifecycle statuses.
These statuses allow tracking the progress of an invoice after its issuance.
They can indicate, for example, that an invoice is:
- submitted;
- transmitted;
- received;
- rejected;
- accepted;
- in dispute;
- pending payment;
- paid.
For financial departments, these statuses are essential.
They enable better management of collections, payments, disputes, and reminders.
But to be useful, these statuses must circulate correctly between Approved Platforms and companies' internal systems.
Interoperability must therefore ensure not only the exchange of invoices, but also the smooth flow of tracking information.
E-reporting and data transmission to the administration
Approved Platforms are not only used to transmit invoices between companies.
They also play a role in transmitting mandatory data to the tax authorities.
This data may include:
- billing data;
- transaction data;
- payment data where applicable;
- certain e-reporting operations.
The PPF is refocused on directory and data hub functions.
PAs transmit the necessary information in compliance with the regulatory framework.
Interoperability therefore also ensures consistency between business-to-business exchanges and the reporting of tax data expected by the administration.
Technical standards that make interoperability possible
Interoperability relies on a set of standards, norms, and protocols.
Among the important elements, these include:
- the minimum core invoice formats;
- AFNOR experimental standards;
- standardization APIs;
- secure exchange protocols;
- authentication mechanisms;
- status management rules;
- traceability requirements;
- compliance checks;
- interconnection mechanisms between platforms.
These standards help limit specific developments and ensure that platforms can communicate in a common language.
They are also essential to facilitate integration with ERPs, accounting software, invoicing tools, and business solutions.
The Role of Approved Platforms in the Reform
Accredited Platforms are central players in the reform.
They specifically ensure:
- issuing electronic invoices;
- receiving supplier invoices;
- transmitting invoices;
- potential format conversion;
- compliance checks;
- status management;
- transmitting mandatory data;
- interoperability with other platforms;
- traceability of exchanges;
- integration with business systems.
To be registered, platforms must meet the requirements set by the administration and demonstrate their ability to operate within the reform ecosystem.
The choice of an AP must therefore be made carefully.
It's not just about choosing an invoicing tool, but a partner capable of securing your flows, your data, and your regulatory obligations.
How to ensure your compliance?
To succeed in your transition to electronic invoicing, several best practices should be applied.
1. Choose a reliable Accredited Platform
Opt for an AP capable of demonstrating its compliance, its interoperability capabilities, its experience with B2B flows, and its ability to integrate with your information system.
The criteria to analyze include:
- registration;
- functional coverage;
- ERP integration;
- API compatibility;
- format management;
- security;
- archiving;
- status management;
- project support;
- support;
- adaptability.
With DEMATRUST, ICD International offers an Approved Platform designed to help companies achieve compliance and secure their electronic invoicing flows.
2. Choose an adaptable solution
Electronic invoicing obligations are becoming widespread in many countries.
Your solution must therefore be able to evolve with regulatory and technical changes.
An adaptable solution must be able to support:
- specification updates;
- format changes;
- new use cases;
- multi-entity needs;
- international flows;
- e-reporting;
- new national obligations;
- organizational changes.
This adaptability is essential to avoid having to change solutions with every regulatory change.
3. Train your teams
The reform affects several departments: finance, accounting, IT, purchasing, sales administration, collections, and sometimes the legal or tax department.
Teams must understand:
- the role of Approved Platforms;
- invoice formats;
- lifecycle statuses;
- rejection rules;
- how the directory works;
- e-reporting obligations;
- new internal processes;
- impacts on existing tools.
Good training limits errors and accelerates adoption.
4. Audit your flows before going live
Before the transition, it is essential to audit your flows.
This audit should identify:
- customer flows;
- supplier flows;
- current formats;
- the tools involved;
- missing data;
- specific cases;
- integration risks;
- non-compliance points;
- automation needs;
- status processing rules.
ICD International offers e-invoicing support to help you audit your flows, identify areas for attention, and secure your transition.
5. Test interoperability before widespread adoption
Testing is essential.
They ensure that invoices circulate correctly, that statuses are properly transmitted, and that mandatory data is accurately reported.
Tests should cover:
- issuance;
- receiving;
- formats;
- directory;
- statuses;
- rejections;
- e-reporting flows;
- specific cases;
- ERP connections;
- exchanges with partners.
This phase helps identify anomalies before going live and reduces operational risks.
DEMATRUST: an Approved Platform for secure exchanges
DEMATRUST supports companies in their transition to mandatory e-invoicing.
The solution allows for managing:
- issuing e-invoices;
- receiving supplier invoices;
- regulatory formats;
- lifecycle statuses;
- compliance checks;
- ERP integration;
- e-reporting;
- traceability;
- archiving;
- interoperability with the reform ecosystem.
DEMATRUST leverages ICD International's long-standing expertise in EDI, dematerialization, and B2B exchanges.
For businesses, the objective is simple: ensure compliance while streamlining exchanges with customers, suppliers, and partners.
Key takeaways
Interoperability between Certified Platforms is essential for the proper functioning of the e-invoicing reform.
It ensures that invoices, statuses, and mandatory data flow correctly between businesses, platforms, and the administration.
It also helps preserve businesses' freedom of choice by avoiding technical lock-in with a single provider.
To successfully manage your transition, it is essential to choose a reliable PA, prepare your data, audit your flows, train your teams, and test your exchanges before widespread implementation.
With DEMATRUST, ICD International supports you with a scalable solution, robust APIs, and expert support to ensure your compliance and streamline your exchanges.
Do you want to secure your flows and check your level of preparation? Discover DEMATRUST or contact our experts via the contact ICD Internationalpage.
