France E-Invoicing Directory in 2026: Check SIREN, Platform and Routing Before Cutover
Published August 2026 by Solarc Labs
The official directory answers a routing question, not just an identity question
France's public electronic-invoicing directory is a practical cutover tool. The official service records businesses and public entities covered by the reform and can show whether an organisation is connected to a Plateforme Agréée and which electronic invoicing addresses are available. The Ministry of Economy explains that the search can start from a SIREN, SIRET, legal name or postal address. For finance and ERP teams, that makes the directory useful before a real invoice is sent: it gives an official place to check the counterparty and the receiving path instead of relying on an old email address, a spreadsheet note or a supplier questionnaire alone.
Verify the legal entity before you debug the integration
Start with the customer or supplier identifier held in your system of record. Confirm that the SIREN or SIRET resolves to the organisation you intended, then compare the legal name and address with your master data. If the identifier points to the wrong entity, changing XML mappings or retrying transmission will not fix the underlying addressing problem. Keep uncertain matches as exceptions for human review. Do not infer or auto-repair a legal identifier from a similar company name when the evidence is ambiguous.
Check receiving-platform status and the electronic invoicing address
The public directory can indicate whether the organisation has a receiving platform and expose its electronic invoicing address information. Record the result for the counterparties that matter most to the cutover, together with the date you checked it, because onboarding and routing state can change as companies complete their preparation. The directory is a lookup surface; the actual regulated transmission still belongs to the approved-platform path. Your integration should use the routing and addressing model agreed with the relevant Plateforme Agréée rather than turning a manual directory lookup into an unofficial substitute for that network.
Turn directory checks into a bounded exception queue
Do not try to solve the entire customer master in one opaque batch. Export a representative or commercially important set of counterparties and classify the results: identifier verified, receiving platform visible, electronic invoicing address available, mismatch requiring master-data correction, or unresolved and needing follow-up. That queue is more useful than a single readiness percentage because each unresolved row has an owner and a next action. It also lets the ERP team distinguish identity and routing problems from invoice-content problems such as missing mandatory fields or unsupported mappings.
Test routing evidence separately from invoice-data evidence
A directory lookup can support routing preparation, but it does not prove that a representative invoice corpus is technically clean. Conversely, a well-formed invoice does not prove that it will reach the correct recipient. Keep those two evidence streams separate: official directory and PA routing checks for addressing, and corpus-level preflight for structured invoice data. InvoiceBatch is a bounded readiness and corpus-preflight tool. Solarc is not a Plateforme Agréée and InvoiceBatch does not replace the official directory, approved-platform transmission, delivery or administration-reporting layer. Use the free readiness route to identify the preparation boundary, then test representative invoice data before the regulated handoff.
Primary sources
Sources used for this article
Continue the job