10 Checks for France. Production Ready or Ready for Change?

Railway switch redirects electronic invoices from a faulty PA track towards production readiness for France e-invoicing.

Plateforme Agréée France E-Invoicing e-Reporting e-Invoicing Peppol

Aug 21, 2026

Your PA has been selected. Now you need to prove that the setup can work in production.

Choosing a Plateforme Agréée, or PA, does not automatically mean your organisation is ready to issue, receive and report real invoice flows. These ten checks will help you assess your France e-invoicing readiness and decide whether to fix the current setup or consider changing PA.

What changes on 1 September 2026?

France’s first e-invoicing deadline is now imminent:

All businesses within the scope of the reform must be able to receive electronic invoices from 1 September 2026.
Large enterprises and mid-sized enterprises, or ETIs, must also issue electronic invoices and meet their applicable e-reporting obligations from that date.
SMEs and micro-enterprises must begin issuing electronic invoices and meeting applicable e-reporting obligations from 1 September 2027.

The legal timetable remains in force. For large enterprises and ETIs, PA selection is no longer the main question. The priority is confirming that invoice, reporting and exception flows can operate from 1 September 2026.

Does choosing an accredited PA mean you are ready?

No. Selecting an accredited PA confirms who provides your regulated connection to France’s e-invoicing ecosystem. It does not confirm that your complete setup is ready for production.

A PA supports regulated functions such as:

Sending and receiving electronic invoices
Exchanging invoices with other PAs
Looking up the receiving PA via the national directory
Transmitting required invoice and e-reporting data
Managing relevant invoice lifecycle statuses

Accreditation is essential, but operational fit goes further. Accreditation confirms that a PA can operate within France’s model. Operational readiness depends on how well its integration, data handling, testing, support and service model fit your organisation.

These capabilities can vary significantly between providers. An accredited PA may therefore meet the regulatory requirements but still not be the right operational or strategic fit for your business.

10 checks for your France e-invoicing readiness

Use these questions to test the complete operating model, not only the technical connection.

Readiness check	What to confirm
1. Can you test real invoice flows end to end?	Test representative inbound and outbound invoices across entities, systems, customers, suppliers and formats. Confirm validation, routing, receipt, lifecycle statuses and statutory data transmission.
2. Is the route to production clear?	Confirm the remaining configuration, production access, responsibilities, dependencies, go-live criteria and escalation procedures. A working test connection alone does not establish production readiness.
3. Does the setup cover all your French obligations?	Check domestic B2B invoicing, relevant B2C and international transaction reporting, payment-data reporting and required lifecycle statuses. Assign and test responsibility for every applicable flow.
4. Does everyone understand their role?	Define what the ERP, integration layer, PA and internal teams each handle. Confirm ownership of data validation, reporting, routing and exception management.
5. Is your invoice data ready?	Verify mandatory invoice fields, business identifiers, tax information and France-specific data. Resolve mapping and master-data problems before production.
6. Can your teams manage exceptions?	Establish processes for rejected invoices, validation failures, missing data, routing problems, status errors and duplicates. Give every issue an owner and escalation path.
7. Can the setup support your organisation?	Test actual SIREN and SIRET structures, invoicing addresses, business units, shared-service centres, ERP environments and expected volumes.
8. Is the support model strong enough?	Assess response times, specialist access, escalation routes and support during testing, cutover and production incidents. Provider size alone does not guarantee sufficient implementation attention.
9. Can the PA support your international roadmap?	Determine whether each new mandate will require another provider and integration. Assess API consistency and connectivity across France, Peppol and other regulated markets.
10. Are security and continuity arrangements clear?	Review information security, availability, incident response, recovery and business continuity. Confirm what happens if the PA or integration becomes unavailable.

If you cannot answer several of these questions confidently, review the setup now. The next decision is whether the gaps can be fixed within the current model or whether the PA itself is no longer the right fit.

When should you reconsider your selected PA?

Reconsider your PA when the gaps are structural and there is no credible plan to close them before production.

Some issues can be resolved through configuration, clearer ownership, additional testing or a remediation plan with firm dates. Look more closely when:

Essential capabilities remain unavailable without a confirmed delivery date.
Representative end-to-end testing cannot be completed.
E-reporting responsibilities remain unclear.
Implementation milestones are repeatedly missed.
Technical documentation cannot support the required integration.
The service cannot accommodate your entities, volumes or invoice flows.
Support constraints are putting your readiness plan at risk.
The model cannot support your international requirements.
No credible escalation or continuity plan exists.

The decision is not whether the implementation has problems. Most complex implementations do. The question is whether those problems can realistically be resolved before they affect production.

Can you change PA in France?

Yes. You can change PA in France, and a business can use more than one PA when needed. France’s e-invoicing model supports provider choice, so changing PA should be a planned transition rather than a rebuild of your finance environment.

Why the French model supports switching

Three features make a controlled change possible:

The national directory identifies which PA is registered to receive invoices for each address. The Annuaire connects an organisation’s electronic invoicing addresses with its receiving PA. When changing PA, the relevant directory and routing information can be updated so invoices reach the new platform. Trading partners should not need to rebuild their PA connection, although routing and recipient information must still be validated before cutover.

More than one PA may support a phased transition. France allows businesses to use one or more PAs where needed. Using more than one PA may support a phased transition where the organisation’s entity, invoicing-address and routing structure permits it. For example, a business may test a new connection and introduce it across selected entities or invoice flows before completing the wider transition.

A multi-PA setup requires clear ownership. Define which PA handles each entity, invoicing address and flow, and keep the national directory information accurate throughout the transition.

Standardised invoice exchange reduces dependency.When the existing architecture uses recognised formats, documented APIs and a clear separation between the ERP and PA layer, the provider remains a connectivity component rather than becoming inseparable from the finance stack.

A multi-PA setup still needs clear ownership. Define which PA handles each entity, invoicing address and flow, and keep the national directory accurate. Clear allocation supports continuity. Unclear allocation adds complexity.

What makes switching PA in France straightforward?

The main obstacle is usually legacy lock-in, not the French regulatory model.

Switching is more straightforward when the existing setup includes:

Clear separation between the ERP and PA layer
Standard invoice formats such as Factur-X, UBL and CII
Documented APIs
Exportable configuration and routing data
Clean customer, supplier and entity master data
A production-like test environment
Clear access to historical invoices, statuses and audit evidence
Standards-based connectivity that can support requirements beyond France

Proprietary formats, limited data portability and tightly coupled integrations make a change harder. A standards-based PA architecture keeps the connectivity layer more portable and gives the organisation greater control over future provider decisions.

Changing PA follows a known path

A controlled PA transition normally follows six steps:

Assess the current architecture, entities, invoice flows and reporting requirements.
Separate gaps that can be fixed within the current setup from those requiring a different provider.
Review contract terms, including notice periods, data access and record retention.
Configure and test the new connection, using a phased approach where appropriate.
Update the relevant directory, invoicing-address and routing information.
Complete the cutover with contingency measures and preserve historical invoices, statuses and audit evidence.

Changing PA should be treated as a controlled infrastructure change, not an emergency replacement. Planned properly, it protects operational continuity and creates a setup that can support the organisation beyond 1 September 2026.

Choose a PA for long-term operational fit

The 1 September 2026 deadline is an immediate milestone, but your PA connection will remain part of your financial infrastructure long after it.

The right model should support growing invoice volumes, additional entities, regulatory changes and international expansion without taking control away from your existing systems. For software and service providers, it should also protect ownership of the product and customer relationship.

The question is not only whether your PA can meet the deadline. It is whether the setup gives you the flexibility to operate, scale and change direction after it.

How Arratech supports France e-invoicing readiness and PA switching

Arratech provides the regulated connectivity layer and leaves your existing business systems in control.

As an independent e-invoicing infrastructure provider and accredited Plateforme Agréée, we connect your software, ERP or platform to France’s e-invoicing ecosystem without replacing your accounting platform, finance processes or customer-facing product.

This independence also makes Arratech a natural option when changing PA in France. Our standards-based approach uses recognised invoice formats, documented APIs and Peppol connectivity to reduce dependency on proprietary architecture. The PA remains a connectivity layer around your systems, not a replacement for them.

Arratech supports organisations with:

API-based connectivity to France’s e-invoicing ecosystem
Integration, onboarding, testing and PA transition support
Multi-entity and multi-customer infrastructure
International Peppol and regulatory connectivity
White-label delivery for software and service providers
Specialist technical and operational support
ISO/IEC 27001-certified information security management
ISO 22301-certified business continuity management

The result is a France e-invoicing setup that supports compliance now while preserving control, portability and international scale for the future.

Discuss Switching PA with Arratech

If these checks reveal material gaps, determine now whether your current setup can be fixed in time or whether changing PA offers a more reliable path to France e-invoicing readiness.

Arratech is an accredited Plateforme Agréée built around a standards-based, API-first approach. We can help you understand what a transition to Arratech would involve, from integration and testing to routing, onboarding and cutover.

Whether you are actively considering a change or simply want to understand what an alternative setup could look like, talk to our team about your requirements.

GET IN TOUCH

FAQs

Does choosing an accredited PA mean my organisation is ready for France e-invoicing?

No. Accreditation confirms that a Plateforme Agréée can operate within France’s regulated e-invoicing model. Your production readiness still depends on system integration, invoice data, e-reporting coverage, end-to-end testing, exception handling and operational support.

How can I assess whether my PA is ready for production?

Test representative invoice and reporting flows from end to end. Confirm that your setup can handle validation, routing, lifecycle statuses, e-reporting, rejected invoices and production incidents across your actual entities, systems and transaction types.

When should I reconsider my selected PA?

Reconsider your PA when material gaps threaten production and there is no credible plan to resolve them. Warning signs include incomplete end-to-end testing, unavailable capabilities, unclear e-reporting responsibilities, repeated delays, insufficient support and an inability to accommodate your entities, volumes or international requirements.

Can I change PA in France?

Yes. You can change PA in France. The national directory allows the relevant invoicing addresses and receiving routes to be updated when moving to a new provider. The transition should include technical testing, routing updates, a controlled cutover and continued access to historical invoices and audit evidence.

Can a business use more than one PA in France?

Yes. A business can use one or more Plateformes Agréées if needed. Multiple PAs may support different entities, invoicing addresses or flows, but the organisation must define clear ownership and keep its national directory information accurate.

Is switching Plateforme Agréée difficult?

It does not have to be. Switching is more straightforward when the ERP and PA layers are clearly separated and the setup uses standard invoice formats, documented APIs, exportable data and clean routing information. Proprietary formats, limited data portability and tightly coupled integrations create greater complexity.

Will changing PA require my trading partners to change their systems?

Usually not. France's national directory tells the sending PA which PA is now registered for the relevant invoicing address, so it can deliver there directly. When you change PA, the directory and routing information can be updated without requiring trading partners to establish a new bilateral connection or rebuild their systems. However, you should validate recipient details, invoicing addresses and routing configuration before cutover to ensure invoice continuity.

What should a PA readiness review cover?

A PA readiness review should assess your architecture, invoice and e-reporting flows, data mappings, entity structure, directory configuration, testing status, exception handling, support model, security and business continuity. It should then determine whether identified gaps can be fixed within the current setup or require a PA transition.