Choosing an approved platform is not enough: you need a neutral, solid solution that is ready for regulatory changes, in order to avoid dependence, non-compliance and overhaul in the short term.
Last January, a list of more than 100 platforms officially approved to manage electronic invoicing was published. It should have reassured, but it could have created confusion within companies. Because: on what criteria should you choose? The real risk is not choosing an unapproved platform, but choosing an approved platform that will not meet your needs in a few months.
Let’s not forget: PA approval is only a minimum floor, it certifies that a platform has met the entry requirements, but does not guarantee its long-term compliance, nor its ability to cover all of your real needs. Regulatory compliance is played out in the technical, legal and organizational details: where the differences between solutions become significant. The problem is therefore not the lack of offers, but the absence of a reading grid to seriously evaluate them.
An update on the three questions that financial departments and IT departments must ask themselves. Because in this area, a bad decision not only costs time: it can expose the company to lasting tax, legal and operational risk.
1) Platform neutrality: a criterion often underestimated
There is a tension that few calls for tenders anticipate: some PAs belong to publishers who also market ERP, purchasing management or treasury solutions. In theory, no problem. In practice, the question of neutrality quickly arises.
A platform that has an interest in selling you other software bricks does not have exactly the same agenda as a PA whose sole business is compliance and interoperability. The companies we meet sometimes discover this late: their PA directs flows, complicates connections to competing third parties, or conditions certain functionalities on the adoption of complementary tools from the same publisher.
For IT departments, this is an architectural risk: a PA must be a reliable and neutral pipe, not a gateway to a closed ecosystem. For CFOs, it is a risk of commercial dependence which reduces the capacity for renegotiation and complicates any evolution of the IS in the medium term.
The question to ask: is your PA independent of any publisher with commercial interests in other segments of your IS? This is not a contractual detail: it is a strategic choice.
2) The ViDA directive: who already has its roadmap?
ViDA (VAT in the Digital Age) will impose real-time transactional reporting for intra-community operations by 2030, with requirements that go far beyond the framework of the French reform. What we observe at Docoon is an almost systematic blind spot in calls for tenders: ViDA does not appear there, or appears in the very last line as a marginal mention.
For CIOs, ignoring ViDA today means exposing themselves to a major overhaul in three years. For DAFs, this is a risk of tax non-compliance on intra-EU flows at a deadline that is quickly approaching. Ask the question “how does your solution anticipate ViDA?” remains one of the most effective maturity tests for evaluating a service provider.
3) Compliance governance: a team or an argument?
It is the least visible criterion in specifications and probably the most discriminating over time. Compliance is not a fixed state: it is a continuous process of adaptation to legislative developments, government decisions, and updates to data schemas. The companies we support often tell us the same thing: they did not anticipate that the compliance of their PA could become obsolete without them being informed. For IT departments, does your AP have a formalized regulatory update process, with clearly defined service commitments? For CFOs, the question is simpler: who, in your service provider’s organization, is responsible for your compliance in eighteen months? If no one can answer precisely, you have your answer.
Choosing an approved platform in 2025-2026 is not ticking a regulatory box. It’s making an infrastructure decision: a decision that will commit your organization for several years, in a field where the rules will continue to evolve. Not all approved platforms are equal. They will not be any more tomorrow, when ViDA comes into force or when the DGFiP refines its technical requirements. What differentiates them today is not their approval, it is their technical depth, their capacity for anticipation and the solidity of their internal organization. Regulatory compliance is verified in the details, in the questions you ask, and in the quality of the answers you receive.
Financial departments and CIOs who take the time to ask the right questions will gain more than a solution: they will gain the certainty of not having to start again in eighteen months.
