How to Create, Validate and Transmit Invoices via PA & Peppol

Creating, transmitting, and validating e-invoices in France requires more than generating a PDF. Businesses must produce structured invoice data, route it through accredited platforms, comply with French VAT rules, and manage validation and reporting correctly.

Key takeaways:

• Classify each transaction first: domestic B2B, B2C, cross-border, and collection-based VAT flows have different reporting duties. 
• Use only accepted structured formats such as UBL, CII, or Factur-X; PDF email alone is not compliant. 
• Build invoices with mandatory structured tax, party, VAT, and legal fields, not free-text mentions. 
• Send invoices through accredited platforms linked by the annuaire; keep SIREN, SIRET, and routing data accurate. 
• Track validation results, invoice statuses, e-reporting deadlines, payment updates, and correction workflows continuously. 
• Keep invoice files, platform receipts, attachments, audit trails, and reporting evidence for ten years.

France’s E-Invoicing Framework

France’s model only becomes clear when the mandate, the routing architecture, and the reporting obligations are viewed together.

What the Reform Covers

French e-invoicing is not a single obligation. It is a three-part compliance model that applies differently depending on the transaction.

• E-Invoicing: This applies to domestic B2B supplies of goods and services where both parties are established in France and the transaction falls within French VAT scope, including businesses using the VAT franchise en base. 
• Transaction E-Reporting: This applies where a transaction is outside the domestic B2B e-invoicing perimeter, such as B2C transactions and many cross-border supplies. 
• Payment E-Reporting: This applies where VAT becomes due on collection, usually for services, unless the business has opted for VAT on debits or the transaction falls under reverse charge rules. 

Who Must Comply and When

The rollout calendar determines when businesses must receive and issue compliant e-invoices.

• September 1, 2026: All VAT-taxable entities established in France must be able to receive e-invoices. 
• September 1, 2026: Large enterprises and entreprises de taille intermédiaire (ETI) must begin issuing e-invoices. 
• September 1, 2027: SMEs and microenterprises must begin issuing e-invoices. 

e-Invoicing Platforms

France has moved away from a model where businesses exchange invoices directly with one another for the mandated domestic B2B flow.

The operational architecture now rests on three components:

• Accredited Platforms: Private platforms handle invoice issuance, transmission, reception, format conversion where needed, and the transmission of required tax data. 
• The Annuaire: This central directory identifies the platform managing each entity’s invoicing data and the relevant electronic invoicing addresses. 
• The PPF and DGFiP Concentrator: The state infrastructure is recentred around routing support through the annuaire and concentration of invoice, transaction, and payment data for tax administration purposes. 

For public-sector invoicing, Chorus Pro remains the reference environment. That means suppliers dealing with public entities still need to understand Chorus Pro statuses and workflow controls, even while the broader reform evolves around accredited private platforms.

How to Create, Transmit and Validate E-Invoices in France

A compliant workflow starts before the invoice is generated and continues after the invoice is sent.

Step 1: Classify the Transaction First

Correct classification determines whether you are creating an e-invoice, an e-reporting file, a payment update, or a combination of these.

• Domestic B2B in French VAT Scope: Create a structured e-invoice because the invoice itself becomes the source of data transmitted to the administration. 
• B2C or Cross-Border Transactions: Prepare transaction e-reporting because these flows are generally outside the domestic B2B e-invoicing perimeter. 
• Transactions Taxable on Collection: Prepare payment reporting because the business may need to transmit payment status and collected amounts after the invoice is issued. 

Step 2: Choose a Supported Invoice Format

Format choice determines what your platform can validate, convert, and route without manual correction.

Step 3: Populate Mandatory Invoice Data as Structured Fields

French invoice compliance still rests on mandatory invoice mentions, but under the reform those elements must sit in dedicated structured fields rather than loose text blocks.

The structured payload should capture at least the following data correctly:

• Parties and Identifiers: Supplier and customer names, addresses, business identifiers, and VAT identifiers where required. 
• Invoice Identity: Issue date and a unique invoice number based on a chronological, continuous sequence. 
• Commercial Content: Quantity, precise description, unit price excluding tax, discounts where relevant, and delivery or completion date when different from the issue date. 
• VAT Breakdown: Taxable amount, VAT amount, and VAT rate by rate band, plus total excluding VAT and total VAT. 
• Special Legal Mentions: Exemption references, reverse charge wording, self-billing wording, special regime statements, and other conditional mentions where applicable. 

France has also added reform-specific operational data points that matter for processing, such as customer SIREN and operation category. That means the invoice must be designed as a validated data object, not just a legally worded document.

Step 4: Build the Regulatory Dataset Alongside the Invoice

In France, the invoice is not only a document sent to the customer. It is also the source of tax administration data extracted by the accredited platform.

That data layer commonly includes:

• Core Identification Data: Supplier SIREN, customer SIREN, supplier and customer country, invoice date, invoice number, and invoice currency. 
• Transaction Classification Data: Whether the transaction concerns goods, services, or both. 
• VAT Data: Taxable base, VAT amount, and VAT rate by band, plus total amounts. 
• Conditional Regulatory Data: Reverse charge treatment, exemption reason, self-billing status, corrected invoice reference, VAT on debits option, VAT group information, and delivery or service date where relevant. 

If those data points are assembled only at transmission stage, businesses create reconciliation gaps between the commercial invoice, the ERP, and the reporting output. The safer approach is to generate the regulatory dataset as part of invoice creation.

Step 5: Apply Authenticity, Integrity, and Audit Controls

Structured e-invoicing does not remove the need for evidence. It changes where evidence is created and how it must be retained.

Businesses should still maintain controls around:

• Authenticity of Origin: The issuer must be identifiable throughout the workflow. 
• Integrity of Content: Invoice data must remain intact from issue to receipt and archive. 
• Readability: The invoice must remain understandable to humans throughout its retention period. 
• Auditability: Businesses should preserve the evidence trail that explains how invoice data was generated, validated, transmitted, corrected, and stored. 

Step 6: Route Through an Accredited Platform, Not Email

Transmission is a legal control point in France, not a delivery preference.

For the mandated domestic B2B flow:

• Use an Accredited Platform: The platform handles routing, receipt, possible format conversion, and transmission of required tax data. 
• Maintain Annuaire Data: Recipient legal identifiers, routing details, and invoicing addresses must be current. 
• Do Not Treat Email as Compliance: Email can still be used to send a courtesy copy or payment reminder, but it is not the compliant transmission channel for the reform. 

Step 7: Monitor Validation and Status Outcomes

Validation in France is a chain of controls, not a single yes-or-no check.

A mature workflow should monitor four layers:

• Technical Validation: Syntax, XSD, packaging, and permitted format checks. 
• Business Rule Validation: Field presence, codification, date logic, invoice numbering, VAT consistency, and legal mentions. 
• Recipient Workflow Validation: Acceptance, suspension, correction requests, or rejection by the receiving side. 
• Administration Readiness: Correct extraction and reporting of invoice, transaction, and payment data. 

Public-sector suppliers should pay particular attention to Chorus Pro lifecycle statuses:

• À recycler: Limited destination data can be corrected and resent without changing the invoice number. 
• Suspendue: Supporting documents are missing and must be added. 
• Rejetée: The invoice contains substantive invoicing errors and must be replaced with a new invoice number. 

Pre-Submission Validation Checklist

A short control layer before transmission prevents most avoidable failures.

• Confirm that the transaction has been classified correctly for e-invoicing, transaction e-reporting, and payment reporting. 
• Confirm that the invoice format is UBL, CII, or a compliant hybrid format such as Factur-X. 
• Confirm that mandatory invoice fields are populated in structured form, not only in free text. 
• Confirm that SIREN, SIRET, routing addresses, and public-sector reference data are current. 
• Confirm that VAT totals, VAT rates, exemption codes, and reverse charge wording reconcile across all levels. 
• Confirm that required attachments and supporting documents are linked before submission. 

Common Validation Errors and Fixes

Most failed transmissions in France fall into repeatable patterns that can be addressed through design, master data, and workflow controls.

E-Reporting Timing Must Be Built into the Process

Validation does not end when the invoice is accepted. Finance teams must also meet the reporting cadence attached to their VAT regime.

Transaction and payment reporting frequencies vary by regime. In broad terms:

For payment reporting on transactions already deposited as e-invoices, France also allows payment information to be transmitted by enriching invoice status, including the payment date and amounts collected by VAT rate. That means invoice lifecycle monitoring and cash collection monitoring must be connected operationally.

Record Retention and Audit Readiness

Retention rules matter because France’s reform increases the amount of structured evidence attached to each invoice.

Businesses should preserve:

• The structured invoice file and human-readable rendering where used. 
• Transmission evidence and receipt statuses from the accredited platform. 
• Supporting documents and attachments linked to the transaction. 
• Audit trail records explaining creation, approval, correction, and resubmission. 
• Reporting evidence for transaction and payment data where applicable. 

In practice, invoices should be retained for ten years under the longer accounting retention horizon. Tax control rules can create additional inspection expectations, but they do not reduce the need to keep invoice records and supporting evidence for the full accounting period.

Conclusion

France’s e-invoicing reform changes where invoicing risk sits. The biggest failures will not come from typing an invoice incorrectly, but from weak master data, poor format governance, disconnected reporting logic, and teams that still treat email and PDF as the operating model. Businesses that redesign invoicing as a structured, platform-routed, status-driven process will be far better positioned for compliance, faster exception handling, and cleaner VAT evidence when audits or customer disputes arise.