E-Invoice Finder
Menu
CountriesCompare softwareDeadlinesGuidesCheckerCheck obligation
ENFRDEPLNL
France · last-minute readiness plan

Not ready for French e-invoicing? What to do before 1 September

A last-minute France e-invoicing plan to activate a PA, prove receiving, triage issuing duties and document blockers before 1 September 2026.

Quick verdict:
  • Obligation lens — secure structured inbound capacity for each affected entity; add outbound and reporting work where size rules bring it forward.
  • Greatest last-minute risk — an apparently completed purchase that leaves the wrong SIREN unaddressable or nobody watching exceptions.
  • First action — appoint an entity owner and demand timestamped activation, routing and test evidence from the selected PA.
Get your urgent France readiness reportOfficial sources
Last checked: 19 August 2026Based on official sourcesClear summaryBusiness guidance, not legal advice
Official sources prioritized
Last-checked dates visible
Free checker, no signup required

What you need to know

Guide

1. Run a 30-minute triage by entity, size and obligation

Start with a legal-entity list, not a software list. For every French entity in scope, record the legal name, SIREN, relevant SIRETs, VAT status, company-size category, accounts-payable owner, tax owner, accounting system and current invoice channels. Mark uncertain scope as a blocker requiring professional review; do not settle it by assumption. The DGFiP materials make the immediate split important: all affected businesses need the ability to receive electronic invoices through a plateforme agréée (PA) from 1 September 2026, while large enterprises and ETIs must also triage their issuance and e-reporting duties for that date. SMEs and micro-enterprises have a later issuance milestone, but that does not remove the September 2026 receiving requirement. Use the remaining minutes to assign each entity to one of three lanes. **Receiving lane:** identify the PA, directory status, receiving address and person who will monitor incoming documents. **Issuance and e-reporting lane:** for large enterprises and ETIs, identify covered flows, excluded or special flows, transaction-data handling, payment-data handling where applicable, formats and the production owner. **Scope-review lane:** place mixed activities, foreign establishments, VAT edge cases and disputed size classifications here for rapid tax or legal confirmation. The risk is losing the week to a group-wide debate while no entity has a working receiving path. A recommended internal control is to appoint one accountable owner and one deputy for each SIREN today, with a written decision time for unresolved questions. That ownership rule is operational guidance, not an official requirement. Keep the DGFiP practical guide open during triage and verify current guidance before relying on this page; it is practical information, not legal, tax or accounting advice.

Guide

2. Separate minimum viable readiness from later optimisation

Define a narrow launch condition. Minimum viable readiness means that the correct entity has a contracted and activated PA; its electronic receiving address is visible or otherwise confirmed in the official directory process; authorised users can access incoming invoices; a valid test reaches the intended queue; exceptions are visible; and AP can review, account for, export or archive the received record under a documented procedure. For a large enterprise or ETI, the launch condition must also cover the applicable issuance and e-reporting lane rather than reception alone. Do not confuse this with a mature target architecture. Automated three-way matching, perfect ERP master data, multi-entity dashboards, advanced approval routing, supplier self-service, bespoke analytics and full straight-through processing can be later optimisation if they are not required to create a safe legal and operational path on day one. Similarly, signing a PA contract is an input, not proof of readiness. Evidence must show the service is activated for the right entity and that an invoice can be found, understood and handled by the operating team. Write two columns: **must work by 1 September** and **controlled follow-up after launch**. Put every item in one column with an owner and decision reason. Recommended freeze windows, change approvals and evidence packs are internal controls, not statutory rules. This distinction prevents an unfinished ERP connector from masking a usable PA portal route, while also preventing a temporary manual process from being misrepresented as a complete integration. The risk is either overengineering too late or declaring success without an actual receiving chain.

Guide

3. Make a same-day PA decision using non-negotiable criteria

If an entity has no PA, use the current DGFiP list of approved platforms as the entry gate. A software product that is merely compatible with electronic invoicing is not authorised to perform transmissions reserved for a PA. Ask the provider to identify the exact approved legal entity on the DGFiP list and the platform covered by the proposed contract. Do not use a blog badge, marketplace claim or sales slide as the only evidence. Apply non-negotiable criteria before feature scoring: support for the entity and its required flows; a credible activation plan before the milestone; directory registration and receiving-address handling; formats relevant to counterparties and systems, such as Factur-X, UBL or CII; portal access if the ERP connector is delayed; user roles and audit trail; exception visibility; data export; support and escalation; security terms; exit/data-retrieval provisions; and coverage of issuance or e-reporting where the entity needs it. Verify ERP or accounting-software compatibility against the exact product version and connector scope, not a generic integration logo. Contract checks should name every covered legal entity, SIREN or agreed identifier, service scope, activation prerequisites, responsibilities, pricing events, support route and the provider's stated dates. Ask which steps depend on identity checks, mandate evidence, signatures, master data or a third party. There is no safe basis here to promise a universal PA onboarding time or SLA: require the candidate to commit to a fact-specific schedule and disclose blockers. If no candidate can evidence a viable path, escalate that fact immediately rather than lowering the approval criterion. Choose on documented capability and delivery risk, not a named-vendor ranking. The immediate commercial decision is the smallest contract and implementation scope that establishes the required path without creating a costly dead end. Confirm current DGFiP status and take tax or legal advice where the entity's obligations are uncertain.

Guide

4. Complete onboarding, authority checks and directory activation

Treat onboarding as a controlled sequence. Provide the legal name, SIREN, required SIRETs, VAT details and receiving-address choices exactly as requested by the PA, then reconcile them to authoritative company records. Confirm who has authority to bind the entity, who may administer the account and whether a mandate or additional verification is required. Record the PA implementation owner, the internal business owner, the AP operator, the security administrator and the escalation contact. Avoid sending identity or authority documents through unapproved channels. Activation is not complete when credentials arrive. Ask the PA to confirm in writing which entity is active, which service components are enabled and which electronic invoice address or routing arrangement has been registered. The Service-Public directory is designed to show whether a business has joined a PA and its electronic invoice receiving addresses. Check the relevant SIREN and addressability there when the status becomes available, and retain a dated record of what was seen. If the directory result is absent, stale or ambiguous, open a provider ticket and keep the reference; do not invent a receiving address or tell suppliers to guess. Build a compact evidence pack containing the executed contract or order, approval-status check, entity mapping, authority confirmation, activation notice, user-role list, directory evidence, receiving-address details, test records, operating procedure and open-blocker log. This evidence pack is a recommended internal control, not an official safe harbour. It helps management distinguish a completed task from a sales assurance and gives support teams the identifiers needed to investigate quickly. The common last-minute risk is an entity mismatch: a group signs once, but a subsidiary, branch routing rule or SIRET used by suppliers is not covered as expected. Test each required legal entity and routing variant rather than extrapolating from the parent company.

Guide

5. Establish the minimum receiving workflow into AP and accounting

Map one end-to-end operational path: PA receipt, validation or exception status, AP review, approval, accounting entry, payment control and retention or export. Name the queue, role and hand-off at every step. Enable service alerts where available, but do not rely on one person's mailbox as the control. At least two authorised users should know how to reach the PA portal, find an invoice, inspect its structured data and human-readable representation, identify its status and export the available records needed by the accounting process. If the ERP connector will not be ready, define a temporary human review procedure in the PA portal. An authorised operator can monitor receipts, compare supplier and amount data, record the accounting action and escalate exceptions under dual control where appropriate. This is an internal continuity measure; it does not turn an emailed PDF into compliant electronic-invoice reception. Email or a PDF attachment should not be described as a substitute for the structured route through a PA. Confirm how Factur-X, UBL or CII documents and any attachments appear, how rejected or technically invalid items are signalled, and what can be exported for downstream handling. Check access recovery, holiday coverage, alert recipients and the boundary between the PA's storage or export service and the business's own retention duties. Do not assume a portal archive satisfies every tax, accounting or records requirement without checking the contract and applicable rules. The minimum workflow should be short enough to operate under pressure and explicit enough to audit. Keep optimisation requests outside it until the receipt queue, exception queue and daily ownership are stable.

Guide

6. Prove readiness with three recorded acceptance tests

Use production-safe tests agreed with the PA; do not inject fabricated documents into production without authorisation. For a concrete fictional scenario, take **Atelier Rivage SAS**, using fictitious SIREN **123 456 78X** and fictitious establishment **123 456 78X 00012**, with supplier **Hexagone Components SAS**. These identifiers are deliberately invalid and must be replaced with authorised test identifiers supplied for the test environment or controlled production procedure. **Test 1 — valid invoice:** send or arrange an authorised Factur-X, UBL or CII invoice numbered `HC-2026-0042`, showing a fictional net amount of €1,200 and VAT of €240, to the agreed receiving address. Verify sender evidence, timestamp, intended entity, invoice identifier, key amounts, readable rendering, PA status, AP alert, queue placement, export and operator acknowledgement. Pass only when the document is traceable from transmission evidence through the receiving workflow; a provider dashboard saying “sent” is not enough. **Test 2 — wrong routing or identifier:** use the PA's safe test method to target a non-existent routing address or an unconfigured establishment variant. Confirm that the document does not silently land in the valid AP queue, that the sender or operator receives a useful status, and that support can trace the correlation identifier. The desired result is controlled detection and escalation, not a successful delivery. Never use a real third party's identifier for a negative test. **Test 3 — credit, correction or duplicate:** submit an authorised credit or correction referring to `HC-2026-0042`, or replay the original under the PA's approved test procedure. Confirm that AP can see the relationship, distinguish a duplicate from a new payable item and prevent double posting or payment. Record whether the PA rejects, flags or presents the item; do not assume universal behaviour. For every test, keep the script, permission, environment, identifiers, timestamps, screenshots or exports, observed result, expected result, defects, owner and retest decision. Redact unnecessary personal or confidential data. A failed negative test can be valuable evidence if it exposes a routing weakness and leads to a documented control before launch.

Guide

7. Use a blocker decision tree instead of improvising

**No PA selected:** restrict candidates to the current DGFiP list, apply the non-negotiable criteria, request a written activation path today and escalate if no candidate can cover the entity and required flows. Do not substitute a compatible accounting product for the PA role. **Contract pending:** identify the exact blocking clause, signer, identity check, payment or procurement approval. Ask the provider which technical steps can proceed without creating an unauthorised commitment. Set an internal decision time and record the consequence of missing it; a draft contract is not an activated service. **Directory entry or address absent:** reconcile legal identifiers, confirm the PA submitted or completed the required directory action, capture the provider ticket and recheck through the official directory process. Do not publish a guessed address, reroute to an unrelated entity or claim readiness from an account screenshot alone. **Invoice not arriving:** stop repeated sends. Compare the sender's destination, SIREN/SIRET or address, format, timestamp, message/correlation identifier and transmission status with the PA's logs. Check the exception queue and entity mapping, then open one traceable incident with both sides. A no-blind-retry rule is a recommended control because retries can create duplicates or obscure the original fault. **ERP connector late:** use the contracted PA portal and an authorised, documented manual AP process if the provider confirms that reception is active there. Limit users, reconcile daily, export evidence and schedule the integration follow-up. Do not label emailed PDFs as the fallback receiving solution. **Scope uncertain:** separate technical activation from the unresolved legal or tax question where possible. Obtain advice on the specific entity, transaction and reporting duty, document the question and avoid making irreversible mappings based on guesswork. For a large enterprise or ETI, uncertainty about issuance or e-reporting cannot be closed merely by proving receipt. At every branch, assign an owner, next evidence, escalation contact and decision time. Freeze windows and escalation thresholds are internal choices, not official tolerances or grace periods.

Guide

8. Operate the first week with visible controls

For the first operating week, hold a short daily reconciliation between PA receipts, AP intake, accounting entries and unresolved exceptions. Record counts, values where appropriate, duplicate indicators, missing supplier documents and ageing items. Review user access and alerts each morning, and keep an incident log with the original timestamp, entity, routing identifier, correlation reference, status, owner, actions and resolution evidence. These are recommended operational controls, not mandated evidence formats. Tell suppliers only what has been verified: the legal entity, the electronic receiving address or routing instruction confirmed through the PA process, the effective date and a monitored contact for delivery problems. Do not ask suppliers to treat ordinary email as equivalent to the structured channel. Tell the accountant or outsourced AP team which portal or integration they must monitor, how exceptions are assigned, who can approve master-data changes and how credit notes or duplicates are handled. Avoid distributing credentials in the communication. Adopt no blind retries: investigate an apparent failure before resubmission and link any authorised retry to the original reference. Keep human review for unexpected routing, changed bank details, duplicate numbers, unusual VAT treatment and documents that do not match a purchase or engagement. Daily reconciliation should surface gaps without blocking every valid invoice. Once the week is stable, move deferred connector, automation and analytics work into a prioritised backlog. Do not dismantle the manual control until the replacement has passed its own acceptance test and users know the changed procedure.

Guide

9. Follow a dated 12-day recovery plan from 19 to 31 August

Use this as a 12-action-day sequence across the 19–31 August window, with 23 August held as contingency rather than a dependency day. **Day 1, 19 August:** inventory entities, classify size and obligations, name owners and open the blocker log. **Day 2, 20 August:** confirm current DGFiP guidance, identify already-contracted PAs and send a focused request to approved candidates for uncovered entities. **Day 3, 21 August:** score non-negotiable capability, obtain contract and activation dependencies, and decide or escalate. **Day 4, 22 August:** complete authority, security and procurement inputs; prepare exact SIREN/SIRET mappings. **23 August:** contingency for missing documents or management decisions, without assuming vendor work will occur. **Day 5, 24 August:** submit onboarding data through approved channels and schedule directory/address confirmation. **Day 6, 25 August:** configure roles, portal access, alerts and the minimum AP workflow. **Day 7, 26 August:** verify activation and directory evidence for each entity; investigate any mismatch. **Day 8, 27 August:** run the valid-invoice acceptance test and trace it into AP. **Day 9, 28 August:** run the wrong-routing and credit/correction or duplicate tests; log defects and controls. **Day 10, 29 August:** retest material fixes, brief operators, suppliers and the accountant, and rehearse escalation. **Day 11, 30 August:** reconcile the evidence pack, review large-enterprise/ETI issuance and e-reporting status, and decide what remains launch-critical. **Day 12, 31 August:** hold the go/no-go review, freeze avoidable changes, publish the rota and leave every unresolved item with an owner, next action and escalation time. Ask the provider: Are you currently on the DGFiP approved-platform list under the contracting entity named here? Which of our legal entities and flows are covered? What must we supply before activation? Who controls directory registration and receiving addresses? What date and evidence will show that each entity is addressable? Can AP use the portal if our ERP connector is late? Which Factur-X, UBL and CII scenarios are supported for our scope? How are exceptions, duplicates, credits and corrections exposed? What exports, logs, access controls and escalation routes are included? Which issuance, transaction-data and payment-data services are active for our large-enterprise or ETI obligations? Ask for written, entity-specific answers; do not infer capability from a demonstration. Avoid five last-minute mistakes: treating signature as activation; testing only the happy path; mapping the group instead of each required entity; making an emailed PDF the supposed fallback; and repeatedly resending an untraced invoice. Also avoid inventing a grace period, penalty, tolerance, fallback channel or universal data checklist. Verify current official guidance and obtain fact-specific advice where needed. The go/no-go evidence should show approved PA status, executed scope, correct entity mapping, authorised administration, confirmed receiving address or directory status, successful valid test, controlled exception tests, working AP access, documented temporary process, incident route and trained owners. For a large enterprise or ETI, add evidence for the applicable issuance and e-reporting path. “No-go” does not mean doing nothing: it means escalating the precise gap, protecting valid controls and executing the provider or advisory recovery action without false claims. Convert the final evidence and unresolved risks into the France readiness report. That next action creates an entity-by-entity record of what is proven, what is temporary, what remains uncertain and which optimisation should follow after the milestone.

Checklist

List every affected French entity with its SIREN, relevant SIRETs, size category and accountable owner.

Separate universal receiving readiness from the issuance and e-reporting lane for large enterprises and ETIs.

Verify the chosen platform against the current DGFiP approved-platform list and the exact contracting entity.

Confirm contract scope, authority checks, activation prerequisites and provider dates for each legal entity.

Capture directory or receiving-address evidence and raise a traceable ticket for every mismatch.

Give two authorised operators working PA access, alerts and a documented AP hand-off procedure.

Run and record the valid, wrong-routing and credit/correction or duplicate acceptance scenarios.

Document an ERP-delay procedure inside the PA workflow without presenting email or PDF as compliant reception.

Brief suppliers and the accountant with verified routing details, escalation contacts and no-blind-retry instructions.

Hold the 31 August evidence review and assign every open risk an owner, next action and escalation time.

FAQ

What should a French business do first if it is not ready for 1 September 2026?

Start with an entity-by-entity obligation check and appoint one owner per SIREN. Confirm the receiving requirement, identify whether large-enterprise or ETI issuance and e-reporting also apply, then establish whether an approved PA is contracted, activated and able to address the entity. Prioritise proof of the minimum receiving path before optional integration features, while escalating uncertain legal or tax scope for professional review.

Is there an official grace period if the business misses the French e-invoicing milestone?

Do not plan on one. This guide does not assert an official grace period, tolerance, safe harbour or penalty amount. Check the latest DGFiP material and obtain advice for the entity's facts. Operationally, document the exact blocker, continue the fastest authorised remediation and avoid claiming compliance on the basis of an assumed concession.

Is receiving a PDF invoice by email enough?

It should not be treated as a substitute for the structured electronic-invoice route through a PA. A readable PDF may appear within some formats or workflows, but ordinary email delivery does not by itself prove compliant reception. Keep any human review inside the activated PA process, and verify format and flow support with the provider.

What must SMEs and micro-enterprises complete by 1 September 2026?

They should not confuse their later issuance milestone with the receiving deadline. For each affected entity, confirm a PA relationship, directory or receiving-address status, authorised access, a functioning AP hand-off and evidence from a controlled receipt test. Entity-specific VAT or transaction questions still require current official guidance or professional advice.

How quickly can an approved platform be activated?

There is no universal onboarding time that can safely be promised. Timing depends on the provider, entity checks, authority evidence, contract completion, directory work, integration choice and scope. Ask the PA for a written schedule naming prerequisites, dependencies, the activation evidence it will provide and the escalation route if a date slips.

Does signing a PA contract make the business ready?

No. A contract does not prove that the correct entity is activated, addressable or operational. Readiness evidence should connect approved status and contractual scope to user access, directory or address confirmation, a successful receipt, visible exceptions and a workable AP procedure. Large enterprises and ETIs also need their applicable issuance and e-reporting lane assessed.

Which last-minute acceptance tests matter most?

Run an authorised valid-invoice test, a safe wrong-routing or identifier test, and a credit/correction or duplicate scenario. Trace identifiers, timestamps, statuses, alerts, queue placement, exports and AP action. The goal is to prove both successful receipt and controlled failure handling without creating real third-party or duplicate-payment risk.

What evidence should be kept if the ERP connector is late?

Keep the PA approval and contract checks, entity mapping, activation and directory evidence, user roles, test results, provider tickets, incident log, daily reconciliation and the authorised temporary portal procedure. Label the evidence pack and freeze rules as internal controls, not an official safe harbour, and verify retention obligations separately.

Key regulations, formats and terms

FranceFrench tax administrationDGFiPimpots.gouv.frapproved platformplateforme agrééePDPFactur-XUBLCIISIRENVATe-reportingSMEmicro-enterpriseaccounting softwareEuropean CommissioneInvoicingEN 16931Directive 2014/55/EUstructured electronic invoiceVAT automationcross-border tradeFrance e-invoicing not-ready emergency action plan before 1 September 2026

France — Country hub

France

Open country hub →

Use the country hub to see every related deadline, checklist, format guide and software comparison for this market.

Continue reading

Official sources

We prioritize official government and EU sources where available and keep last-checked dates visible for mandate-sensitive pages.