French electronic invoicing introduces new requirements for FileMaker-based ERPs.
Every FileMaker application is different. It has been designed around specific processes, workflows, and business rules. This flexibility is one of FileMaker’s greatest strengths, but it also means there is no universal answer to a simple question: is your FileMaker solution ready for French electronic invoicing?
The French reform introduces a new ecosystem for exchanging electronic invoices and related business information. For FileMaker developers, this means the application will no longer simply generate invoices, but will also need to exchange structured data with external platforms throughout the document lifecycle.
When Italy introduced mandatory electronic invoicing, our experience across dozens of FileMaker projects showed that generating an XML file was usually the easiest part of the project. Most of the work happened inside the ERP.
→ We’ve documented the key lessons from that experience in a dedicated article.
Although the French reform follows a different model, the same principle still applies: before discussing providers or integrations, the first step is to determine whether the ERP is ready.
Electronic Invoicing Starts Long Before the Invoice
At first glance, electronic invoicing may appear to be a document exchange project. In reality, it starts much earlier.
Electronic invoicing doesn’t simply change how invoices are sent. It changes the information your FileMaker ERP must store, the workflows it must support, and the way it communicates with external systems.
An invoice is only the final result of a business process. Long before it is generated, the ERP has already collected customer information, payment terms, tax data, products, services, and all the business rules that define the transaction. If any of this information is missing, incomplete, or stored in a way that only works for printed invoices, electronic invoicing quickly becomes much more than a simple integration project.
This is where many FileMaker solutions differ from standard ERP systems. Over the years, they have evolved to meet the specific needs of each organization. Features have been added as the business grew, workflows have been simplified where appropriate, and data structures have been shaped around day-to-day operations. What works perfectly for internal processes, however, is not always sufficient for a regulated exchange of structured electronic data.
Our experience has shown that the technical integration itself is often the simplest part of the project. The real challenge is understanding whether the existing ERP already contains everything required to support the new process, or whether it needs to evolve before any integration can begin.
What Should You Assess Before Starting an Electronic Invoicing Project?
Every FileMaker solution is different, but the questions to ask are often the same.
Before selecting an e-invoicing provider or planning the technical integration, it’s worth taking a step back and assessing whether the ERP is ready to support the new requirements.
In our experience, the assessment usually focuses on a few key areas.
Customer and company master data are usually the first area to review.
Does the ERP store all the information required for electronic invoicing? Customer records often contain everything needed for day-to-day operations, but regulated electronic exchanges may require additional identifiers, tax information, or mandatory fields that have never been necessary before.
Invoice structure
In some FileMaker solutions, invoices were originally designed only for printing, with little need to preserve the underlying business structure. Electronic invoicing requires that structure to exist.
Is the invoice built from structured data, or is it primarily designed for printing? Line items, taxes, discounts, totals, and references all need to be represented consistently if they are to be exchanged electronically.
Business workflows
Electronic invoicing introduces new events into the lifecycle of an invoice. The ERP may need to track transmission status, validation results, rejected invoices, or other information that previously didn’t exist.
Incoming invoices
The project isn’t only about issuing invoices. The ERP should also be prepared to receive electronic invoices and decide how they fit into existing purchasing or accounting workflows. Receiving invoices is only the first step. The ERP must also decide what happens next.
These are only some of the areas that should be reviewed before starting an electronic invoicing project.
In the next article, we’ll go through a practical assessment checklist to help you evaluate your own FileMaker ERP.
Conclusion
French electronic invoicing is often presented as a compliance project. For organizations using FileMaker, it is also an opportunity to review how the ERP has evolved over time and whether it is ready to support new regulatory workflows.
The success of an electronic invoicing project rarely depends on the ability to generate an electronic invoice. More often, it depends on the quality of the data, the consistency of the business processes, and the structure of the application that produces it.
Before evaluating providers or planning integrations, the first step is to understand the current state of your FileMaker ERP.
Every FileMaker application reflects the way a company works. That’s precisely why electronic invoicing projects cannot start with a provider or an integration.
They start with understanding the ERP itself.
In the next article, we’ll walk through a practical checklist to help you determine whether your FileMaker solution is ready for French electronic invoicing.
