Blog
Nov 17, 2026

Self-billing under France’s e-invoicing reform: Who issues invoices?

Ben Robinson

In French commercial trading, buyers frequently generate invoices on behalf of their suppliers. This process, known as self-billing or autofacturation, is standard practice in sectors where the customer determines settlement values, such as agricultural purchasing, recycling, logistics, and royalty management.

 

France’s e-invoicing reform preserves self-billing. However, moving away from unmanaged paper and PDF documents introduces standardised data codes, electronic platform routing, and specific administrative requirements. Understanding how delegated billing fits into the nationwide framework helps businesses maintain compliant operations.

Key takeaways

  • Self-billing remains fully legal under France’s e-invoicing reform. However, buyer-issued invoices can no longer be sent as paper or simple PDFs and must move as structured electronic documents through an approved platform.

  • The buyer acts as the operational issuer, but the supplier remains legally responsible for the tax. The vendor stays accountable to the French tax administration for invoice compliance and output value-added tax (VAT) declarations.

  • Dedicated type codes and text mentions are mandatory on every self-billed e-invoice. Files must carry the specific mention “Autofacturation” and use UNTDID type code 389 for invoices or code 261 for credit notes.

  • A valid prior agreement is mandatory before self-billing can commence. French tax law requires a written billing mandate (mandat de facturation) establishing delegated authority and an explicit acceptance procedure.

What is self-billing (autofacturation)?

What autofacturation means in French B2B invoicing

 

In French business-to-business (B2B) commerce, autofacturation is an arrangement where a customer issues an invoice in the name and on behalf of its supplier. This is distinct from third-party billing, where an external agency handles invoicing tasks. Under self-billing, the actual purchaser compiles the transaction details, calculates the payable balance, and creates the invoice document.

 

Why French businesses use self-billing

 

Companies implement self-billing when transaction data originates on the purchasing side. Examples include:

 

  • Agri-food: Processors determine final payments after measuring delivered volume and quality metrics.

  • Recycling and scrap metal: Buyers calculate payments using certified weighbridge logs and material grading.

  • Logistics and freight: Shippers generate invoices directly from agreed rate cards and completed proof-of-delivery data.

  • Digital platforms and royalties: Marketplaces compile periodic seller payouts from central transaction databases.

 

Does the e-invoicing reform change self-billing?

 

Self-billing remains legal under the reform. What changes is the formatting and transmission: self-billed invoices can no longer be sent as paper or simple PDFs by post or email. They must be created as structured electronic files and routed through approved platforms.

Self-billed invoice responsibilities

Can the buyer issue an invoice on behalf of the supplier?

 

Under Article 289 of the French General Tax Code, a buyer can issue invoices on behalf of a supplier, provided there is a prior agreement and an agreed acceptance procedure. The buyer acts as the operational creator of the file, but the document remains a sales invoice issued on behalf of the vendor.

 

Who is responsible for the invoice and the VAT?

 

Statutory liability does not shift under a self-billing arrangement:

 

  • The supplier remains legally accountable to the French tax administration (Direction générale des Finances publiques or DGFiP) for tax compliance and must account for output VAT on the sale.

  • The buyer is contractually liable to the supplier for the accuracy of the underlying transaction data and remains responsible for substantiating its own input VAT deductions.

  • Payment data reporting must also be completed for taxable services under statutory French e-reporting rules.

  • Cross-border sales data must also be reported correctly.

 

Who does what in a self-billing flow?

 

ActivitySupplierBuyerSupplier’s approved platformBuyer’s approved platform
Authorise self-billingSigns mandateSigns mandate——
Collect transaction dataVerifies deliveryGathers quantities and rates——
Create invoiceHolds tax liabilityGenerates electronic invoice—May validate format
Transmit invoiceAuthorises issuanceSubmits to platformReceives and deliversValidates and routes
Review invoiceApproves or disputesHandles queriesDelivers life-cycle statusRelays life-cycle status
Correct errorsApproves treatmentIssues self-billed credit noteDelivers credit noteRoutes credit note
Declare output VATDeclares to DGFiP———
Retain recordsRetains archiveRetains archiveOptional storageOptional storage

 

Can a French buyer self-bill a foreign supplier?

 

A French business can self-bill a foreign vendor, but the tax and invoicing rules depend on the supplier’s establishment status. If the non-French vendor has no permanent establishment in France, the transaction typically falls under e-reporting rather than domestic e-invoicing.

 

Self-billing must not be confused with deemed-supplier transactions, where an online intermediary acts as the principal seller for VAT purposes.

What must a self-billing mandate contain?

French tax doctrine requires prior agreement between the parties before self-billing can commence. While electronic agreements are legally valid, establishing a formal written mandate ensures both parties can prove delegated billing authority during a tax audit.

 

Self-billing mandate checklist

 

To satisfy statutory audit standards, a French billing mandate should define:

 

  1. Legal names, registered business addresses, SIREN (nine-digit business identification number), SIRET (14-digit facility identification number), and VAT numbers for both parties.

  2. Explicit authorisation empowering the buyer to issue invoices in the supplier’s name and on its behalf.

  3. Precise scope of covered transactions, product categories, or business units.

  4. Effective start date, contract duration, renewal terms, and termination procedures.

  5. Rules governing invoice numbering sequences and source-data verification.

  6. Validation standards for mandatory invoice fields and applied VAT rates.

  7. Technical transmission routes and designated electronic platforms.

  8. Acceptance mechanisms, review deadlines, and dispute escalation processes.

  9. Correction workflows, including mandatory issuance of self-billed credit notes.

  10. Responsibilities for submitting transaction and payment reporting data.

  11. Document retention periods, audit access rights, and data storage security.

Which approved platform issues a self-billed e-invoice?

Under the French mandate, businesses exchange e-invoices through an approved platform (the state-registered platform formerly referred to as a PDP). In a self-billing flow, the buyer uploads the invoice to its own approved platform. The buyer’s approved platform validates the file, routes it across the central directory, and delivers it to the supplier’s approved platform.

 

How a self-billed invoice travels between buyer, supplier, and platforms

 

  1. Data collection: The buyer compiles transaction details from warehouse receipts, metering systems, or enterprise resource planning (ERP) logs.

  2. Invoice generation: The buyer creates an e-invoice identifying the supplier as the seller and itself as the buyer.

  3. Platform validation: The buyer submits the invoice to its approved platform, which verifies syntax, checks mandatory tax mentions, and extracts core tax data for the DGFiP.

  4. Directory delivery: The buyer’s approved platform routes the structured invoice to the supplier’s approved platform, making it available in the supplier’s accounting software.

 

Can the buyer and supplier use different platforms?

 

Yes. The French framework relies on an interoperable directory. As long as both parties use registered platforms, files and life-cycle statuses route automatically between different systems.

Self-billing invoice mentions and type codes in France

What must appear on a self-billed invoice?

 

Self-billed invoices must contain all standard mandatory mentions required by CGI Article 289. The supplier must always be identified as the vendor/seller. Mandatory fields include legal company names, registered addresses, SIREN/SIRET numbers, intra-community VAT numbers, sequential invoice numbers, tax point dates, itemised descriptions, unit prices, applied VAT rates, and total payable amounts.

 

Is the mention of “Autofacturation” mandatory?

 

Yes. French law requires the specific text mention “Autofacturation” (or “Facture émise par le client pour le compte du fournisseur”) on the readable document. In structured data formats, this is matched by specific syntax qualifiers.

 

Which type codes apply to self-billed invoices?

 

Under the European EN 16931 standard (using UNTDID 1001 document type codes), self-billed documents must use specific technical identifiers:

 

  • Code 389 (self-billed invoice): Used instead of standard commercial invoice Code 380.

  • Code 261 (self-billed credit note): Used instead of standard commercial credit note Code 381.

 

Using incorrect type codes will cause automated rejection at the platform gateway.

How suppliers accept, refuse, or dispute self-billed invoices

Does the supplier have to approve every self-billed invoice?

 

The billing mandate governs how invoices are accepted. It may specify explicit approval (where the supplier reviews and signs off on every invoice) or tacit acceptance (where the invoice is considered approved if no objection is raised within an agreed window, such as 15 days).

 

What happens when a supplier disputes a self-billed invoice?

 

If a supplier identifies an error regarding quantities, rates, or VAT calculations:

 

  1. The supplier notifies the buyer in accordance with the dispute process in the mandate.

  2. The buyer issues a self-billed credit note using Type Code 261 to adjust or cancel the incorrect invoice.

  3. The buyer issues a corrected self-billed invoice (Type Code 389) referencing the original document.

 

How platform statuses fit with self-billing disputes

 

Suppliers can update life-cycle statuses (such as refusée or litige) through their platform. However, an electronic platform status merely indicates processing state; it does not replace the commercial and contractual dispute mechanisms established in the billing mandate.

Make self-billing compliance easier with Avalara

Managing self-billing under France’s e-invoicing mandate requires seamless ERP integration, correct document type classification, and certified platform transmission. Establishing clear mandates and automated validation ensures your business stays compliant while streamlining vendor payouts.

 

Avalara E-Invoicing and Live Reporting connects directly to your ERP, billing, and accounting systems, converting buyer-calculated transaction data into compliant French e-invoices, routing them across the national directory, and reporting required tax data to the DGFiP.

FAQ

Self-billing remains fully legal under the reform, but the transmission method changes. Rather than sending PDF or paper invoices directly to suppliers, buyers must issue structured e-invoices through an approved platform using dedicated self-billing type codes and mandatory mentions.

The supplier remains legally liable for the VAT due on the transaction and for declaring the output tax on its VAT return. While the buyer is contractually responsible for the accuracy of the data it inputs under the billing mandate, the statutory tax liability cannot be transferred away from the supplier.

Under the official French e-invoicing technical specifications, self-billed invoices must use electronic type code 389 (self-billed invoice) and credit notes must use type code 261 (self-billed credit note). In addition, the readable invoice must display the mandatory mention “Autofacturation”.

The billing mandate sets the acceptance procedure, whether through explicit sign-off or tacit approval within an agreed timeframe. If a supplier identifies an error in pricing, quantity, or VAT treatment, it can flag the invoice using platform dispute statuses such as refusée or litige, prompting the buyer to issue a matching self-billed credit note (code 261) to correct the transaction.

Sales tax rates, rules, and regulations change frequently. Although we hope you'll find this information helpful, this blog is for informational purposes only and does not provide legal or tax advice.

Ready to get started?

Start with a demo, a free nexus assessment, or a conversation with our team — and discover why millions of users trust Avalara.