Invoicing & integrations
How we integrated compliant electronic invoicing for Pare-Brise Éco with Iopole
For Pare-Brise Éco, we developed a commercial management and invoicing module connected to Iopole. This brought compliant electronic invoicing flows into the business application alongside quotes, invoices, credit notes and case documents. The project illustrates a practical integration in the context of France’s 2026–2027 reform.
Understand the reform’s different stages
The French tax authority distinguishes receiving from issuing invoices. From 1 September 2026, affected businesses must receive electronic invoices from suppliers required to issue them. Large and intermediate-sized businesses also begin issuing then; smaller businesses follow on 1 September 2027. Transaction reporting depends on the operations concerned.
For business software, producing a PDF is therefore only one aspect. Applicable flows, entities and recipients need identifying before implementing the required channels. The software and transmission provider must have explicit responsibilities.
Use Iopole as a specialist transmission component
Iopole provides an API-based electronic invoicing service. It appears in the French tax authority’s approved-platform list and OpenPeppol’s certified access-point list, linked below.
We connected the business application to this specialist component. Custom development retains the activity-specific journeys while Iopole participates in the implemented invoicing channels. Provider approval complements the integration; it does not replace configuration and verification of the application’s particular flows.
Our Pare-Brise Éco implementation
The module developed for Pare-Brise Éco combines commercial management and invoicing within the business software. Quotes, invoices and credit notes are associated with cases and their accompanying legal documents, preserving the relationship between operational work and commercial records.
The Iopole integration covers Peppol exchanges and transmission to Chorus Pro for public-sector customers through the channels implemented in the project. This is how we supported electronic invoicing compliance: connecting the application’s business workflow to appropriate transmission services instead of placing invoicing in an unrelated tool.
Maintain continuity with the operational record
The custom work matters at this boundary. Cases provide context, commercial documents carry invoicing information and the integration passes them through the relevant channel. Shared references help staff locate the appropriate document.
For another implementation, first map entities, customer types and documents. Then specify required data, issuing permissions and correction or credit-note scenarios. These decisions define the integration without assuming every customer has identical obligations.
Include verification and ongoing follow-up
Prepare representative test examples: ordinary invoices, credit notes, incomplete recipients and rejected transmissions. Use appropriate supplier test environments before live exchanges. The team needs to distinguish a prepared document from one transmitted or processed.
Assign error monitoring, technical access and interface maintenance. Preserve references and supporting records needed to understand exchanges. Pare-Brise Éco illustrates integrating electronic invoicing into business operations through custom development and a specialist platform such as Iopole.
Your checklist
- Identify obligations for each entity and flow.
- Preserve case, quote, invoice and credit-note links.
- Verify the provider’s official status.
- Define implemented channels and rejection scenarios.
- Assign testing, access and monitoring responsibilities.
Frequently asked questions
What did we deliver for Pare-Brise Éco?
We developed a commercial management and invoicing module connected to Iopole within the business application. It links quotes, invoices and credit notes to cases and includes the Peppol and Chorus Pro channels described in the project.
Must the application itself become an approved platform?
It can rely on an approved provider such as Iopole for transmission. Data, permissions and exchange journeys still need implementing within the agreed scope. Business obligations and provider status remain separate responsibilities.
A project to explore
Pare-Brise Éco
Explore the Pare-Brise Éco project for the invoicing module, case documents and other integrations in the business application we developed for the network.
Explore the project