E-Invoice Finder
Menu
CountriesCompare softwareDeadlinesGuidesCheckerCheck obligation
ENFRDEPLNL
France · foreign-company scope and VAT flows

Does a foreign company fall under French e-invoicing?

Determine French e-invoicing and e-reporting scope for a foreign company using establishment, VAT, counterparty and transaction facts.

Quick verdict:
  • Classification signal — follow the invoicing entity, intervening establishment, counterparty and supply.
  • Largest risk — treating a French VAT number as a universal domestic-scope flag.
  • First action — sample real flows and document the evidence behind each route.
Get your France readiness reportOfficial sources
Last checked: 16 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. A fast decision tree for each entity and flow

Start with the legal seller or buyer shown on the invoice, not the group name. Ask: Is that operator established in France for the transaction, potentially through a relevant fixed establishment? Is it liable for French VAT? What registrations does it hold? Is the counterparty a France-established taxable business, a non-taxable customer, or an operator established abroad? What happened: domestic goods, services, export, intra-Community flow, import or another case? DGFiP guidance places purchases and sales between France-established VAT-liable businesses in e-invoicing, including VAT-exempt businesses. Transactions with operators established abroad and sales or services to non-taxable entities enter transaction e-reporting. Treat VAT registration as evidence, not an automatic scope switch. Record one result per flow: e-invoicing, transaction e-reporting, payment overlay, apparently outside the cited rules, or adviser review. Apply that sequence invoice population by invoice population rather than once for the company. A useful scope matrix has rows for recurring commercial flows and columns for seller, buyer, intervening establishment, VAT identifiers, supply type, origin and destination, tax treatment, expected channel, payment-reporting relevance, decision owner and supporting evidence.

Guide

2. Prove who is established and why a VAT number is not enough

Build an entity file before configuring software. Include incorporation records, French registrations, SIREN and SIRET identifiers where applicable, intra-Community VAT numbers, contracts, premises, people and technical resources, invoice issuer, ordering party, accounting ownership, and evidence showing which establishment intervenes. A French VAT number does not settle whether the foreign operator is established in France for a transaction; describing every foreign-owned operation as non-established may also be wrong. Branch, subsidiary, permanent-establishment and fixed-establishment labels are not interchangeable conclusions. Ask French tax counsel to document mixed facts. Do not let one ERP country code, VAT registration or fiscal representative record classify every flow. Preserve dated advice, assumptions and samples so system rules remain auditable when the operating model changes. For each French footprint, write a one-page fact pattern covering who negotiates and signs contracts, who performs or receives the work, where relevant resources sit, which entity bears commercial risk, and whose books contain the receivable or payable. Link each conclusion to representative invoices and contracts. Set a review trigger for reorganisations, new premises, transferred staff, acquisition integration, a new fulfilment model or a change in invoice issuer, because an old scope memo may no longer fit the operating facts.

Guide

3. Classify sales by customer and transaction

Create four sales lanes. First, a sale between a seller and buyer established in France and liable for VAT is the core France-established B2B e-invoicing lane described by DGFiP, including VAT-exempt businesses. Second, a transaction with an operator established abroad belongs in the transaction e-reporting analysis; DGFiP examples include exports and intra-Community supplies. Third, sales or services to non-taxable entities, including relevant B2C activity, enter transaction e-reporting analysis rather than domestic B2B e-invoicing. Fourth, mark unusual, exempt, reverse-charge, marketplace, OSS/IOSS, stock or triangulation facts as outside the simple decision tree or needing review. Do not classify from billing address alone. Capture legal customer, establishment status, tax capacity, VAT identifiers, ship-from and ship-to countries, service facts, invoice issuer and reporting rationale. A customer-facing buying question should be explicit: ‘Which legal entity and establishment are purchasing, and what VAT identifier should support that status?’ Add that question to onboarding and renewal controls, but verify the answer against contracts and reliable master data. For goods, retain dispatch, delivery and customs evidence where relevant; for services, retain the service description, recipient and place-of-supply analysis. Build a controlled reason code for each lane, with an adviser-approved definition and named owner. This makes exceptions visible when one customer has both French and foreign establishments or purchases in different capacities.

Guide

4. Classify purchases without turning every invoice into e-invoicing

For purchases, identify the legal buyer, the establishment receiving or using the supply, the supplier’s establishment and the tax treatment. A domestic supplier invoice between qualifying France-established VAT-liable businesses may enter the e-invoicing chain. A foreign supplier invoice is not converted into a domestic e-invoice merely because the buyer quotes a French VAT number. Imports, intra-EU acquisitions, reverse-charge services, local acquisitions, customs movements and stock transfers require their own VAT and reporting analysis; DGFiP’s English examples place purchases among transactions relevant to e-reporting, but that does not justify one universal treatment for every purchase. Configure separate review codes instead of forcing uncertain flows into ‘domestic’. Reconcile supplier master data to contracts, purchase orders, customs evidence, VAT returns and ledgers. Ask suppliers which legal entity issues the invoice, which establishment intervenes, and whether their proposed approved-platform route reflects documented tax advice rather than a mailing address. Procurement should collect those answers before go-live, while Accounts Payable should flag conflicts between the purchase order, invoice identifiers and actual supply. Sample high-value suppliers, frequent cross-border vendors, intercompany charges and logistics providers first. Confirm how duplicate invoices, corrections and supplier master changes will be detected and evidenced across the ERP and approved platform.

Guide

5. Add payment e-reporting only where the VAT timing test is met

Payment e-reporting is a separate decision layer, not a synonym for transaction e-reporting. DGFiP states that it concerns transactions for which VAT is payable on collection, for example certain services, when the company has not opted for VAT on debit or issue and the transaction is not reverse-charged. The amount collected is used to determine output VAT payable. For each service family, document whether VAT follows collection or debit, whether an option has been exercised, whether reverse charge applies, and how partial payments, credits and allocation are represented in source systems. Finance should own the tax-timing rule; treasury or accounts receivable should supply reliable collection events; IT should transmit only approved classifications. Do not invent a frequency, field set or exception from this summary. Test cash receipts against invoices and output VAT, and send unresolved deposits, netting, factoring or mixed invoices to specialist review before automation. Map the full payment path, including payment service providers, bank files, suspense accounts and manual allocations, so the reported amount can be traced back to evidence. A monthly control should compare eligible invoice balances, collections assigned, transmitted records, platform acknowledgements and VAT workings. Any difference needs an owner, reason and resolution date rather than an unexplained spreadsheet adjustment.

Guide

6. Apply deadlines and size tests to the correct company

The official phased dates also apply to e-reporting: 1 September 2026 for large and mid-tier companies, and 1 September 2027 for small and micro businesses. Companies within reform scope must receive e-invoices from 1 September 2026. For a foreign group, do not copy the parent’s size label onto a French subsidiary, branch or registration. Identify the operation to which the French test applies, document the size conclusion and confirm any group or consolidation effect. Traps include treating the worldwide brand as the taxpayer, combining registrations into one population, or assuming a small French operation receives the later timetable. Keep separate records for headquarters, French entities and establishments under review. If classification is unclear, get French advice and plan to the earlier date until the conclusion is supportable. The readiness plan should therefore show two decisions: whether each entity or operation is within the relevant reform population, and which phase applies. Record the financial period, source accounts, thresholds or criteria used by the adviser, group assumptions and approval date; do not let the project team improvise a size test. Align contracts, platform onboarding, receiving capability, user training and support coverage to the documented date.

Guide

7. Translate scope into approved-platform and ERP requirements

Approved platforms transmit and receive e-invoices and transmit invoice, transaction and payment data. Ordinary compatible accounting, billing or ERP software cannot perform those regulated functions unless registered as an approved platform. Ask vendors to prove registration, explain identifier validation, separate each reporting channel, and handle rejections, corrections and evidence exports. Your ERP needs governed legal-entity, SIREN/SIRET and VAT identifiers where relevant, customer tax capacity, establishment attributes, supply and payment-tax codes, and traceable rule versions. Use a RACI: Tax is accountable for scope and VAT timing; Finance owns reconciliations; Sales and Procurement maintain counterparty evidence; IT owns integrations; the platform executes regulated exchange; advisers review exceptions. The evidence pack should hold decisions, advice, samples, mappings, platform status, tests, reconciliations and sign-offs. In the buying process, require a demonstration using your French and cross-border cases rather than a generic domestic invoice. Ask which party owns directory onboarding, identifier matching, status monitoring, data correction, archive access, incident response and exit support. Document the boundary between ERP, middleware and platform, including the system of record for each field and status. Operational acceptance should depend on end-to-end traceability and reconciliation, not merely a successful API connection or a vendor statement that the software is ‘France-ready’.

Guide

8. Run a 12-case acceptance test and prove completeness

Build twelve signed test cases: (1) domestic France-established B2B sale; (2) domestic qualifying purchase; (3) sale to a foreign-established business; (4) purchase from a foreign-established supplier; (5) French B2C sale; (6) export of goods; (7) intra-Community supply; (8) intra-EU acquisition; (9) customs import; (10) reverse-charge service; (11) service with VAT payable on collection; and (12) credit or correction linked to a prior case. For each, store the entities, establishments, VAT identifiers, contract, tax code, expected channel, payment overlay, platform response and accounting result. A tax reviewer must approve expected outcomes before IT calls the test successful. Reconcile source invoices and collections to platform acknowledgements, exception queues, sales and purchase ledgers, VAT working papers and retained evidence. Measure missing, duplicate, rejected and misclassified records. A technically accepted message is not proof that the tax classification or reporting population is correct. Use anonymised production-like data where possible and include one negative variation per case, such as an absent identifier, conflicting establishment evidence or an unexpected customer status. Test correction and resubmission paths, role permissions, cut-off handling and evidence retrieval as well as the happy path. The reconciliation design should prove population completeness from source to platform and back, with control totals by legal entity, channel and period. Assign thresholds, investigation steps and sign-off owners before launch so unresolved differences cannot quietly roll forward.

Guide

9. Work examples, red flags and the first 30 days

Example one: a foreign company with a French VAT number sells to a French customer. Do not infer domestic e-invoicing; establish which operation intervenes. Example two: a French subsidiary sells services to its foreign parent; foreign-counterparty e-reporting may apply, with payment reporting considered separately where VAT is payable on collection. Example three: a foreign supplier invoices a French branch; classify the buyer’s establishment role, supply and reverse-charge facts first. Red flags include one rule for all French VAT codes, no owner for customer status, unsupported platform claims and unreconciled cash. In days 1–10, inventory entities, flows and evidence. In days 11–20, obtain adviser decisions and assign the RACI. In days 21–30, shortlist platforms, repair master data and approve the twelve tests. Ask vendors and advisers to identify assumptions, unsupported cases, evidence outputs, dependencies and accountable owners. Add practical buying questions: Can the platform show its approved status and the legal entity providing the service? Will it demonstrate a non-established supplier, foreign customer, domestic purchase and VAT-on-collection service using your data? How are rule changes, failed transmissions, corrected classifications and exported evidence governed? Ask the tax adviser to state which facts would reverse each conclusion and which special flows remain outside the opinion. At day 30, the deliverable should be a signed scope matrix, evidence gaps, risk-ranked remediation backlog, platform requirements, test pack, reconciliation design and decision log—not a claim that every complex flow has been solved.

Checklist

List every invoicing legal entity, French operation and VAT registration separately.

Document which establishment intervenes in each representative transaction flow.

Verify customer and supplier legal identity, tax capacity and establishment evidence.

Assign each flow to e-invoicing, transaction reporting, payment reporting or review.

Record VAT-on-collection, debit-option and reverse-charge decisions for service families.

Confirm the applicable size category and deadline with documented French analysis.

Verify that the chosen provider is an approved platform, not merely compatible software.

Clean SIREN, SIRET, VAT, routing and counterparty master data before testing.

Approve all twelve acceptance cases and reconcile platform results to accounting records.

Retain advice, assumptions, mappings, exceptions, reconciliations and accountable sign-offs.

FAQ

Does having a French VAT number automatically trigger French e-invoicing?

No automatic conclusion should be drawn from the VAT number alone. The official e-invoicing scope described by DGFiP concerns transactions between companies established in France and liable for VAT. Determine the relevant entity and establishment, the counterparty and the transaction facts, then obtain French tax advice where the establishment analysis is uncertain.

Is every foreign company outside France’s e-invoicing reform?

No. A foreign-owned group may have a French subsidiary, branch or fixed-establishment question that changes the analysis, while another group entity may remain non-established. Review each invoicing entity and flow separately rather than relying on nationality, ownership or the address printed on an invoice.

How is a sale to a French business classified when the supplier is non-established?

Do not assume the French customer or VAT number makes it a domestic B2B e-invoice. Establish who supplies the transaction, whether a French establishment intervenes, the customer’s status and the VAT treatment. The result may involve transaction reporting or another reviewed treatment, depending on the facts.

What happens to invoices from foreign suppliers?

Classify the supplier, buyer, establishments and supply rather than importing all foreign invoices into the domestic e-invoicing lane. Imports, intra-EU acquisitions, reverse-charge services and local purchases can have different treatments. Preserve contracts, customs records and VAT analysis as evidence for the chosen route.

When does payment e-reporting matter for services?

It matters where VAT is payable on collection, such as certain services, provided the company has not opted for VAT on debit or issue and the transaction is not reverse-charged. Confirm those points by service family and ensure collected amounts can be reconciled to invoices and output VAT.

Does a foreign business need an approved platform?

That depends on the business’s documented scope and required exchanges. Where regulated transmission or receipt is required, approved-platform capability is central. An ERP or compatible solution cannot itself carry out regulated platform functions unless registered. Ask the vendor to prove registration and support for your exact flows.

Which deadline applies to a French branch or foreign group?

The e-reporting phases are 1 September 2026 for large and mid-tier companies and 1 September 2027 for small and micro businesses; in-scope receipt readiness begins 1 September 2026. The difficult part is applying the size and scope analysis to the correct operation, so document it with French advice.

What should be ready before platform integration begins?

Prepare the entity and establishment decision file, flow inventory, counterparty evidence, identifiers, VAT and payment-timing rules, RACI and expected test results. Platform connectivity should follow tax-approved classifications. Otherwise, successful message delivery can conceal missing populations, duplicates or incorrect reporting channels.

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 scope for foreign companies

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.