Integrating an existing ERP system with the upcoming French electronic invoicing framework involves much more than a simple technical connection, especially when considering the practical challenges and lessons learned from real-world projects.
In our previous articles, we explored the different aspects of the French electronic invoicing reform.
We first looked at what the reform means for businesses using custom ERP systems and why electronic invoicing is much more than a regulatory requirement. We then examined how to assess whether an existing ERP is truly ready, highlighting the importance of data quality, business processes, and application design. Finally, we walked through the practical steps companies should follow to prepare for implementation, from understanding their obligations to selecting an e-invoicing provider and planning the project.
At this point, one question naturally remains:
How do you integrate an existing ERP with French electronic invoicing?
Many companies assume this simply means connecting their ERP to an accredited provider. Our experience has shown that the real challenges lie elsewhere: in how data is modeled, how business processes evolve, and how software is designed to adapt to future changes.
This article explores the most common integration challenges we encountered across real-world projects and the engineering lessons they taught us.
Lesson #1: Every ERP Is Different
One of the first lessons we learned from electronic invoicing projects is that there is no such thing as a “typical ERP”.
Even when two companies use the same platform, their applications often reflect years of different business decisions, operational processes, and custom developments. Over time, every ERP evolves to support the specific way an organization works.
This is especially true for custom-developed systems such as FileMaker solutions, but the same applies to any bespoke ERP system.
As a result, two companies facing the same French electronic invoicing requirements may require completely different implementation projects.
The provider may be the same. The regulation is certainly the same. The ERP is not.
Understanding how the existing application has been designed is often the first and most important step of the entire project.
Lesson #2: Electronic Invoicing Starts with Your Data Model
Electronic invoicing is often viewed as a document exchange project. In reality, it is first and foremost a data project.
The invoice is simply the final result. What really matters is whether the ERP stores the required information in a structured, consistent, and reliable way.
Many integration projects reveal data that is missing, duplicated, calculated at runtime, or stored in ways that worked perfectly for the business but are difficult to map to an electronic invoicing standard.
Before integrating with any provider, it is worth understanding one simple question:
Does your ERP really contain the data that electronic invoicing expects?
Lesson #3: Integration Is About Processes, Not Documents
Sending an electronic invoice is only one step of a much larger process.
Invoices need to be received, validated, rejected, corrected, tracked, and synchronized with the ERP. Each event may trigger new business processes, user actions, or status updates.
A successful integration doesn’t simply exchange documents. It connects business processes across different systems.
Lesson #4: Design for Change, Not Just for Go-Live
Going live is not the end of an electronic invoicing project. It is the beginning.
Regulations evolve. Providers introduce new APIs and features. Businesses change their internal processes. A successful integration should be able to adapt without requiring continuous changes to the ERP itself.
The best integrations are not those that solve today’s requirements. They are the ones designed to accommodate tomorrow’s changes with the least possible impact.
Conclusions
Electronic invoicing is not about exchanging invoices. It’s about designing systems that can adapt to change.
Over the years, we’ve learned that successful projects don’t start with a provider or an API. They start with understanding how the business works, how the ERP has evolved, what information is already available, what is missing, and what the company expects from the new process.
This is why we don’t approach electronic invoicing as a “connect it and forget it” project.
Instead, we start by understanding the existing system, identifying what needs to change, and designing an integration that fits the business rather than forcing the business to fit the integration.
Because providers will evolve. Regulations will evolve. And your business will evolve too.
A well-designed integration should be able to evolve with them, without forcing you to redesign your ERP every time something changes.
Ready to Start Your Project?
Every ERP has its own history, its own processes, and its own challenges. That’s why there is no universal implementation recipe for French electronic invoicing.
If you’re planning your transition and would like to discuss your current ERP, your business processes, or the most effetive approach for your organization, we’d be happy to help.
Contact the DIS team for an initial conversation. Together, we’ll assess your current situation, identify the right next steps, and help you build an integration designed not only for today’s requirements, but for tomorrow’s changes as well.
