E-Invoice Finder
Menu
CountriesCompare softwareDeadlinesGuidesCheckerCheck obligation
ENFRDEPLNL
France · inbound readiness and AP testing

France e-invoicing receiving acceptance test for September 2026

Test your approved platform and accounts-payable flow before France’s 1 September 2026 e-invoice receiving deadline.

Quick verdict:
  • Scope — every affected entity’s inbound chain.
  • Biggest risk — PA receipt without AP delivery.
  • First action — trace a structured test end to end.
Get France readiness reportOfficial sources
Last checked: 11 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. Scope the deadline—and avoid the receiving-only trap

Official fact: every business concerned by France’s reform, regardless of size, must be able to receive electronic invoices from 1 September 2026 through a plateforme agréée (PA, formerly called a PDP). The phased issuing calendar is different: large and mid-sized businesses begin issuing on 1 September 2026, while SMEs and micro-enterprises begin on 1 September 2027. A small company that focuses only on its later issuing date therefore risks missing an earlier inbound obligation. Define the test population by legal entity, establishment, SIREN/SIRET, VAT/TVA identity, AP team, ERP or accounting system and expected supplier channels. Example: an SME that will not issue under the reform until 2027 should still prove in August 2026 that a supplier’s compliant invoice can reach its PA and enter AP. Recommended control: maintain a signed scope register showing included entities, owners, expected volumes and exclusions. Success means every in-scope entity has a named receiving route and test owner; an unsigned PA contract or a future integration plan is not evidence of operational reception.

Guide

2. Map the supplier-to-PA-to-AP route and responsibilities

Official fact: a PA may issue, transmit and receive electronic invoices, convert an invoice into a format suitable for the customer while preserving integrity, authenticity, readability and completeness, and transmit required data. A merely compatible solution cannot receive invoices on the customer’s behalf or exchange them with the supplier’s PA unless it is connected to a PA. Draw the real route: supplier system → supplier’s PA → your PA → AP intake or ERP → validation, booking and payment workflow. For each handoff, name the sending party, receiving party, identifiers used, expected output and evidence generated. Example evidence includes the supplier test reference, PA receipt timestamp, original structured payload, rendered view, ERP document ID and AP decision. Recommended control: assign a RACI for platform administration, directory data, integration, AP review and incident ownership, with service expectations for each handoff. The decision is whether one invoice can be traced across every boundary without relying on email as the reform reception route.

Guide

3. Verify the PA, directory and entity setup before testing

Official fact: reception under the reform uses a plateforme agréée, and the tax administration publishes a list of approved platforms. Check the current official list rather than relying on an outdated proposal or the former PDP label. Confirm with the PA which legal entities and establishments are activated, and validate the SIREN/SIRET and VAT/TVA data supplied for each. Review the public directory (annuaire) setup through the documented process provided by your PA; do not assume a routing rule that has not been confirmed. Ask for a testable explanation of how an inbound invoice addressed to each entity will be identified and delivered. Recommended control: use a four-eye review comparing corporate records, PA configuration, AP master data and the agreed test matrix. Record who checked each item and when. Do not test if the entity is ambiguous, the PA’s approval is unverified or the AP endpoint is unavailable.

Guide

4. Build a realistic multi-format test dataset

Official fact: France’s structured invoice environment includes Factur-X, UBL and CII, aligned with the applicable external specifications and EN 16931 requirements. Build test cases from the formats your suppliers and PA route will actually use; do not treat an arbitrary PDF attachment as compliant. Include a normal invoice in each relevant format, a credit note or correction scenario, and a deliberate duplicate. Vary commercially meaningful data such as supplier, buyer entity, invoice date, currency, VAT/TVA treatment, purchase-order reference and line count without inventing legal requirements. Example: verify that AP receives a Factur-X presentation and its embedded data consistently, then test UBL and CII through the agreed route. Recommended control: give every case a unique test ID and expected outcome, and remove or mask personal or production-sensitive data. The dataset is ready when expected values are documented field by field, duplicates are identifiable, and both positive and controlled negative scenarios can be repeated.

Guide

5. Run end-to-end acceptance tests and preserve evidence

Send each case through the supplier-side test route agreed with the participating PA; uploading a file directly into the ERP does not prove network reception. Capture the original file, transmission reference, PA event or acknowledgement made available by the service, receipt time, delivered representation, extracted fields, ERP or accounting-system record and AP workflow result. Compare supplier totals, tax amounts, invoice identity and buyer identity with what arrives downstream. Example pass criteria: the correct entity receives the document, structured values remain complete and accurate, AP can open the readable representation, the invoice enters the intended queue once, and the trace links supplier reference to AP record. Official fact: a PA can convert formats only while preserving integrity, authenticity, readability and completeness. Recommended control: retain a dated evidence pack for each case and have business and technical owners sign the results. Combine readable proof with identifiers, payloads and timestamps that reconstruct the journey.

Guide

6. Separate platform rejection, buyer refusal and internal AP hold

Official distinction: rejection is a technical, format or transmission outcome, whereas refusal is a buyer lifecycle status. A buyer refusal must be reasoned and used only for permitted grounds. An internal AP hold—for example, pending purchase-order matching or manager review—is a business control and should not automatically be presented as a platform rejection or buyer refusal. Design three separate test outcomes. First, use a controlled invalid or unsupported test agreed with the PA to observe technical handling without inventing a status code. Second, exercise a permitted refusal scenario with AP documenting the reason and evidence. Third, place a valid received invoice on internal hold and verify that it remains visible and owned. Recommended control: align a decision tree, accountable roles, rationale and escalation path with official specifications and PA documentation. Success means staff can classify each outcome consistently, preserve the invoice trail and avoid using refusal merely to clear an inconvenient AP queue. Seek professional advice for uncertain legal or tax treatment.

Guide

7. Monitor, reconcile and escalate inbound incidents daily

Receiving is an operational process, not a one-time connectivity demonstration. Recommended controls: monitor the PA inbound queue and AP destination each business day; reconcile PA-received items to ERP or accounting records using stable invoice references; flag duplicates; and investigate unmatched or delayed items. Define service expectations and escalation contacts for PA operations, integration support, AP, tax and suppliers, but label these as your controls rather than statutory deadlines. Example incident: the PA shows a received invoice, yet no ERP document exists. Preserve timestamps and references, check the delivery interface and AP queue, prevent an uncontrolled email workaround from becoming the primary intake route, and escalate to the integration owner and PA with the evidence pack. Measure received, delivered, unmatched and duplicate counts plus the oldest unresolved item. Base any failover drill on capabilities confirmed by your PA. A daily reconciliation passes when every PA receipt is linked to one AP outcome or an owned, time-bounded incident.

Guide

8. Make the go-live decision and execute a 21-day plan

Use evidence-based criteria: all in-scope entities are active with a verified PA; directory and identity setup has been reviewed; representative Factur-X, UBL and CII cases relevant to the business pass; credit or correction and duplicate handling are demonstrated; PA-to-AP reconciliation works; rejection, refusal and hold are distinguished; owners are trained; and critical incidents have no unresolved blocker. Recommended 21-day plan: days 1–5 confirm scope, PA status, identities, route and owners; days 6–12 prepare data and run end-to-end cases; days 13–17 correct defects and repeat failed tests; days 18–21 complete reconciliation, incident and failover exercises, sign evidence and decide go-live. Do not waive a failed route because smaller businesses issue later. Common mistakes include treating PA selection as readiness, testing a PDF by email, bypassing the real route, ignoring ERP delivery, confusing holds with official outcomes and keeping no evidence. This is practical information, not legal, tax or accounting advice.

Guide

Practical question summary

For France e-invoicing receiving acceptance test before September 2026: French SMEs usually need to know when the deadline applies, whether a PDF is still enough, which platform path to use, how Factur-X relates to UBL and CII, what data must be cleaned, and how the accountant will work with the new flow. This guide answers those questions from an SME workflow perspective.

Guide

Decision framework for SMEs

For France e-invoicing receiving acceptance test before September 2026: A good decision compares legal deadline, receiving readiness, issuing workflow, software integration, accountant access, archive/search and support. If two tools look similar, choose the one that can demonstrate your real invoice scenario end to end before the deadline.

Guide

How to use this guide

Use this guide to decide whether France e-invoicing receiving acceptance test before September 2026 affects your France workflow and which evidence is still missing. Start with approved platform path, Factur-X, UBL or CII data, SIREN/SIRET and VAT fields, then test receive a structured supplier invoice and issue a Factur-X or UBL/CII invoice before comparing software.

Guide

Data and terms to prepare

For France e-invoicing receiving acceptance test before September 2026, the important terms are France e-invoicing receiving acceptance test before September 2026, France, approved platform path, Factur-X, UBL or CII data, SIREN/SIRET and VAT fields, e-reporting cases, accountant handoff. Clean these fields in customer, supplier, tax and accounting records before rollout; otherwise validation and support issues appear during daily invoicing.

Guide

Software proof to request

For France e-invoicing receiving acceptance test before September 2026, ask vendors to show show French platform routing, structured format handling, e-reporting, archive and accountant access using your examples. The demo should cover receive a structured supplier invoice, issue a Factur-X or UBL/CII invoice, simulate an e-reporting case, correct customer master data and explain who handles errors, corrections, archive access and accountant handoff for approved platform path, Factur-X, UBL or CII data, SIREN/SIRET and VAT fields.

Guide

Evidence before rollout

Keep official links, screenshots, test invoices and the decision reason for France e-invoicing receiving acceptance test before September 2026. For France e-invoicing receiving acceptance test before September 2026, the implementation file should prove how approved platform path, Factur-X, UBL or CII data, SIREN/SIRET and VAT fields, e-reporting cases were checked, not just that a tool was selected.

Guide

Decision checkpoint

Do not close France e-invoicing receiving acceptance test before September 2026 until someone can explain France e-invoicing receiving acceptance test before September 2026 in France, name the workflow owner, show one tested invoice scenario and describe how the team avoids choosing software for France before proving the real France e-invoicing receiving acceptance test before September 2026 workflow.

Checklist

List each in-scope entity, establishment, SIREN/SIRET and VAT/TVA identity.

Verify the PA against the tax administration’s list.

Confirm each entity’s activation and documented annuaire setup with the PA.

Map the supplier-to-AP route, owners and handoff evidence.

Prepare relevant Factur-X, UBL and CII supplier cases.

Include a credit or correction scenario and a controlled duplicate in the dataset.

Trace each test from supplier reference to PA receipt and AP or ERP record.

Test and document technical rejection, permitted buyer refusal and internal AP hold separately.

Reconcile PA receipts to AP outcomes and assign every mismatch to an owner.

Sign the evidence pack and close critical defects before approving go-live.

FAQ

Must French SMEs and micro-enterprises receive e-invoices in September 2026?

Yes. Every business concerned by the reform must receive through a PA from 1 September 2026. The 1 September 2027 date for SMEs and micro-enterprises concerns issuing, not reception.

Is choosing a plateforme agréée enough to be ready?

No. Readiness also requires activated entities, verified identity and directory setup, a working AP delivery path, trained owners and end-to-end test evidence. Confirm actual configuration and capabilities.

How should we test e-invoice reception?

Send uniquely identified cases through the agreed supplier-side route and both PAs into AP. Compare the payload, PA receipt, delivered document, extracted fields and ERP record; record references and retest failures.

Which invoice formats should the receiving test cover?

Use Factur-X, UBL and CII where relevant to expected traffic and French specifications. Test structured content and readable presentation where applicable. Not every PDF is compliant.

What evidence should we keep from acceptance testing?

Keep expected values, original payload, supplier reference, available PA evidence, timestamps, delivered representation, AP or ERP outcome, reconciliation, defects, retest result and approval. Apply documented retention governance.

What is the difference between rejection and buyer refusal?

Rejection is a technical, format or transmission result. Refusal is a reasoned buyer lifecycle status used only for permitted grounds. An internal AP hold is separate and should remain visible.

What if the PA receives an invoice but it never reaches the ERP?

Treat it as an owned delivery incident. Preserve references, inspect the interface and AP queue, reconcile counts, prevent duplicates and escalate with evidence. Do not pass the route until delivery and recovery work.

Can email and PDF remain our main intake route under the reform?

No. Ordinary email or an arbitrary PDF does not satisfy PA-based reception. A compatible solution must connect to a PA for exchange on the customer’s behalf. Keep email handling separate and seek advice on specific arrangements.

What do French SMEs usually search for first?

For France e-invoicing receiving acceptance test before September 2026: They usually search for deadlines, whether PDFs are still valid, approved platforms, Factur-X, software choices and what their accountant needs.

What is the most practical risk?

For France e-invoicing receiving acceptance test before September 2026: The practical risk is choosing software that cannot handle receiving, issuing, corrections, archive or accountant access in the real workflow.

What should I test first for France e-invoicing receiving acceptance test before September 2026?

For France e-invoicing receiving acceptance test before September 2026, start with receive a structured supplier invoice, issue a Factur-X or UBL/CII invoice, simulate an e-reporting case because those scenarios reveal whether the workflow is practical.

What is the main risk for France e-invoicing receiving acceptance test before September 2026?

The main risk is choosing software for France before proving the real France e-invoicing receiving acceptance test before September 2026 workflow.

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 receiving acceptance test before 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.