Approved platform for publisher vs company: what are the differences?

The market for electronic invoicing has been structured into two main categories of Accredited Platforms (AP): those intended for end businesses and those specialized for software publishers. Understanding these differences is essential to choose the right option for your activity and to avoid hidden costs or competitive risks.

In this article, we focus on the specific features of platforms for businesses and for publishers, and on how IOPOLE, pure-play electronic invoicing provider, supports publishers in their compliance and digital transformation projects.

Segmentation of the electronic invoicing market

A Accredited Platform is a provider registered with the French tax authority, authorized to:

• issue, receive and transmit electronic invoices between organizations;
• ensure regulatory compliance of formats (e.g., Factur‑X, UBL, CII);
• transmit the tax and transaction data required by the reform ("e-reporting"). 

Without an Accredited Platform, an electronic invoice is not considered compliant, and no regulatory transmission is possible.

In parallel, a Compatible Solution is a software (accounting, ERP, invoicing, cash register...) that complies with the reform standards but is not registered: it must necessarily go through an Authorized Platform (PA) so that invoices and information reach the administration or clients. 

Concretely, a company or a software publisher can use compatible software, but the actual regulatory flow is ensured by a registered Authorized Platform.

On this basis, platforms have organized themselves according to two approaches:

PAs for end-user companies

1. Offered by accounting software or ERP vendors.
2. Goal: to offer an additional service to their clients.
3. Risks: initially low-cost, price increases after the reform, and customer base lock-in.

PAs for software publishers (B2B2B)

1. Designed to support publishers in bringing their clients into compliance.
2. They offer modular solutions via a full API, a sandbox for testing and POCs, and regulatory monitoring.
3. Allow the publisher to retain control of their service and clients while outsourcing the technical infrastructure.

Approved platform for businesses

Who is it for?

Business-oriented platforms often originate from long-established providers of management, accounting, orERP who added a PA to their offering to provide a complete service to their clients.

How do they work?

• They enable companies to issue and receive invoices.
• They ensure basic regulatory compliance.
• They generally target a broad audience without strong industry-specific customization.

What they don't do, or do poorly

• They do not always handle all complex business use cases (construction with retention and subcontracting, IT services companies with project billing, communication agencies, etc.).
• They are often sold as an add-on service to software, which can sometimes create dependence on the provider (vendor lock-in) rather than a strategic choice.
• Many offer a low-cost initial plan (or even free) which, once the reform is fully implemented, may be increased without transparency (post-reform pricing).

For an end company, it is often preferable to opt for:

• a specialized business software already labeled Solution Compatible in which the PA is integrated as a proxy (example: Summeo, Obat, Bill-Up…)
• directly a robust PA adapted to its sector (example: Axonaut, Yooz…)

In the case of a Compatible Solution well integrated with the business software, the company does not need to contract separately with a PA: transmission is managed via the agreement between the compatible software and the PA. 

Example An end user company using compatible software like Summeo or Obat does not have to subscribe directly to the Authorized Platform Iopole. Its billing business tool handles the routing. However, a two-click onboarding process will be required to verify identity and manage registration in the directory / the mandate.

Approved platform for software publishers: a strategic partner

Who is it for?

PAs specialized for business tools like Iopole are designed to:

• make the software Solution Compatible
• integrate technically via complete APIs
• support publishers with complex business use cases
• offer a stable, sustainable infrastructure aligned with regulatory developments.

This allows the software publisher to offer its clients electronic invoicing services without bearing the regulatory burden.

Why the publisher model is different

This is fundamentally a B2B2B model. Software publishers do not want to lose control of their offering and must above all not be dependent on a PA that could become a competitor:

• a PA that expands its industry offerings (accounting, management…) can become a direct competitor of the publishers it serves 
• an overly generic platform doesn't always understand the specific needs of a given publisher and its market
• The publisher must be able to monetize the billing services it offers

These points are essential to explore for business solutions that want to become a white-label PA or a Compatible Solution.

Electronic invoicing project: the real needs of publishers

For a software vendor that wants to bring its software into compliance, a PA must offer:

• A complete, documented API: to integrate feeds directly into the software without hacks.
• A powerful sandbox: to enable quick, reliable tests and POCs.
• Ongoing regulatory monitoring: because standards evolve rapidly (French regulations, technical formats, international e-reporting).
• Commercial neutrality: the partner must never compete with the publisher in the same business areas (functional components, business modules…).

That's exactly what IOPOLE offers: a 100% pure-play platform dedicated to electronic invoicing for software publishers, without extending into competing business features.

• Sandbox
• API documentation
• Swagger API
• Uptime

Comparison: Enterprise PA vs Publisher PA

Contact the partners of software publishers: Electronic invoicing compliance